Bug#477576: linux-image-2.6.24-1-amd64: external disks stopping without any messages
I have a workaround for me: I'll not use any AMD64-kernel with my
motherboard...
But the story first:
Maximilian Attems critizized my high severity rating. I must say: for
me it's one of the biggest catastrophes ever when I'm not able to boot
from USB devices or connect my external disks. 99% of my data is at
USB disks at the moment. For me this is a very critical point. Without
USB everything is lost.
He also gave me hints for experimental kernels to try:
http://wiki.debian.org/DebianKernel
I tried 2 kernels:
2.6.25~rc8-1~experimental.1~snapshot.11067
2.6.25-1~experimental.1~snapshot.11112
The 2.6.24-1-amd64 has been very silent about connecting devices but
those both told a lot. Without any boot options I got a strange message
plus some kind of oops:
Apr 24 22:14:33 disorder kernel: [ 21.302703] irq 19: nobody cared
(try booting with the "irqpoll" option)
Apr 24 22:14:33 disorder kernel: [ 21.302746] Pid: 2435, comm:
modprobe Not tainted 2.6.25-trunk-amd64 #1
Apr 24 22:14:33 disorder kernel: [ 21.302787]
Apr 24 22:14:33 disorder kernel: [ 21.302788] Call Trace:
Apr 24 22:14:33 disorder kernel: [ 21.302864] <IRQ>
[<ffffffff8026c933>] __report_bad_irq+0x30/0x72
Apr 24 22:14:33 disorder kernel: [ 21.302969] [<ffffffff8026cb72>]
note_interrupt+0x1fd/0x23f
Apr 24 22:14:33 disorder kernel: [ 21.303013] [<ffffffff8026d3ff>]
handle_fasteoi_irq+0xa5/0xc8
Apr 24 22:14:33 disorder kernel: [ 21.303058] [<ffffffff8020f414>]
do_IRQ+0x6d/0xd9
Apr 24 22:14:33 disorder kernel: [ 21.303099] [<ffffffff8020c33d>]
ret_from_intr+0x0/0x19
Apr 24 22:14:33 disorder kernel: [ 21.303139] <EOI>
[<ffffffff80212845>] native_read_tsc+0xb/0x18
Apr 24 22:14:33 disorder kernel: [ 21.303223] [<ffffffff8031ab58>]
__delay+0x14/0x1f
Apr 24 22:14:33 disorder kernel: [ 21.303284] [<ffffffff881fd92a>]
:snd_hda_intel:azx_get_response+0xc9/0x190
Apr 24 22:14:33 disorder kernel: [ 21.303344] [<ffffffff881fe674>]
:snd_hda_intel:snd_hda_codec_read+0x54/0x79
Apr 24 22:14:33 disorder kernel: [ 21.303406] [<ffffffff88212afe>]
:snd_hda_intel:snd_hda_codec_new+0x11e/0x4af
Apr 24 22:14:33 disorder kernel: [ 21.303474] [<ffffffff8821248b>]
:snd_hda_intel:azx_probe+0x60f/0x884
Apr 24 22:14:33 disorder kernel: [ 21.303530] [<ffffffff881fd77d>]
:snd_hda_intel:azx_send_cmd+0x0/0xe4
Apr 24 22:14:33 disorder kernel: [ 21.303588] [<ffffffff881fd861>]
:snd_hda_intel:azx_get_response+0x0/0x190
Apr 24 22:14:33 disorder kernel: [ 21.303648] [<ffffffff881fd72b>]
:snd_hda_intel:azx_power_notify+0x0/0x52
Apr 24 22:14:33 disorder kernel: [ 21.303697] [<ffffffff802e10ca>]
sysfs_create_link+0xb6/0x104
Apr 24 22:14:33 disorder kernel: [ 21.303742] [<ffffffff80322edd>]
pci_device_probe+0xb3/0xfd
Apr 24 22:14:33 disorder kernel: [ 21.303785] [<ffffffff8037e717>]
driver_probe_device+0xd9/0x156
Apr 24 22:14:33 disorder kernel: [ 21.303828] [<ffffffff8037e836>]
__driver_attach+0x0/0x92
Apr 24 22:14:33 disorder kernel: [ 21.303869] [<ffffffff8037e890>]
__driver_attach+0x5a/0x92
Apr 24 22:14:33 disorder kernel: [ 21.303911] [<ffffffff8037dac5>]
bus_for_each_dev+0x44/0x6f
Apr 24 22:14:33 disorder kernel: [ 21.303955] [<ffffffff8037e314>]
bus_add_driver+0xb4/0x204
Apr 24 22:14:33 disorder kernel: [ 21.304000] [<ffffffff8037ea9a>]
driver_register+0x59/0xcd
Apr 24 22:14:33 disorder kernel: [ 21.304046] [<ffffffff8032313c>]
__pci_register_driver+0x47/0x7b
Apr 24 22:14:33 disorder kernel: [ 21.304091] [<ffffffff802555c2>]
sys_init_module+0x1887/0x1a1d
Apr 24 22:14:33 disorder kernel: [ 21.304155] [<ffffffff881db3ee>]
:snd_pcm:snd_pcm_format_width+0x0/0x20
Apr 24 22:14:33 disorder kernel: [ 21.304205] [<ffffffff80318ba3>]
__up_read+0x13/0x8a
Apr 24 22:14:33 disorder kernel: [ 21.304249] [<ffffffff80225c94>]
cstar_do_call+0x1b/0x65
Apr 24 22:14:33 disorder kernel: [ 21.304296]
Apr 24 22:14:33 disorder kernel: [ 21.304334] handlers:
Apr 24 22:14:33 disorder kernel: [ 21.304373] [<ffffffff8038885c>]
(usb_hcd_irq+0x0/0x51)
Apr 24 22:14:33 disorder kernel: [ 21.304484] Disabling IRQ #19
Apr 24 22:14:33 disorder kernel: [ 21.354626] input: ImExPS/2
Generic Explorer Mouse as /class/input/input5
Apr 24 22:14:33 disorder kernel: [ 22.022735] hda_intel:
azx_get_response timeout, switching to polling mode: last
cmd=0x000f0000
After this message, IRQ 19 was dead and so was USB. With irqpoll it
got slightly better. The devices will be recognized. The disk even
starts fast, becomes slower until it reached USB1-speed and at the end
the device ran in a timeout:
Apr 25 00:40:57 disorder kernel: [ 655.041945] hub 1-9:1.0: cannot
reset port 3 (err = -110)
Apr 25 00:40:58 disorder kernel: [ 656.117168] hub 1-9:1.0: cannot
reset port 3 (err = -110)
Apr 25 00:40:59 disorder kernel: [ 657.189433] hub 1-9:1.0: cannot
reset port 3 (err = -110)
Apr 25 00:41:00 disorder kernel: [ 658.260125] hub 1-9:1.0: cannot
reset port 3 (err = -110)
Apr 25 00:41:01 disorder kernel: [ 659.326074] hub 1-9:1.0: cannot
reset port 3 (err = -110)
Apr 25 00:41:01 disorder kernel: [ 659.326079] hub 1-9:1.0: Cannot
enable port 3. Maybe the USB cable is bad?
This time the USB system stays alive but just with USB1-speed, almost
useless. I thought: maybe a motherboard-BIOS-update helps? After this
Update: no change at all. I read about the Intel-kernels can also cope
with the AMD stuff, the only problem might be that some features are
not usable. I tried 2.6.24-1-686 and everything works perfectly now.
I'd say: It's absolutely no Debian problem, it's obviously a very
strange kernel problem. I'd say we can close this bug here. It's more
useful if the kernel guys chasing these problems. But I'm really
wondering, why an Intel-kernel runs more stable than a kernel which is
fitted for an AMD-CPU...
Thanx for your help, Maximilian!
Mermgfurt,
Udo
--
Udo Wolter
email: uwp@dicke-aersche.de | ! english pages !
www: http://www.dicke-aersche.de | http://www.big-asses.de
news: http://blog.dicke-aersche.de | http://blog.big-asses.de
pics: http://gallery.dicke-aersche.de | http://gallery.big-asses.de
Reply to: