Pls see the hand-copied decoded backtrace.
It happens when I connect a Seagate 160 GB external USB
hard disk. (I dont have access to this particular drive
just now but under Windows I have seen it as an ST3316002 3A
USB Device) - Oops happens reliably just after I plug the
drive in.
When connecting a Maxtor USB disk there is no Oops however.
Kernel is 2.4.30-pre4 (same as 2.4.30) with the
TNG NTFS patches from Anton Altaparmakov but it is not
in use when it happens. There are no hotplug, automount etc.
scripts on this system.
suggestions from the USB experts are welcome.
Greetings,
Karl
ksymoops 2.4.11 on i686 2.6.10-1.770_FC3. Options used
-v vmlinux (specified)
-k ksyms.out (specified)
-l modules.out (specified)
-o /lib/modules/2.4.30-rc4 (specified)
-m System.map (specified)
Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
Error (pclose_local): find_objects pclose failed 0x100
Warning (compare_ksyms_lsmod): module Module is in lsmod but not in ksyms, probably no symbols exported
Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique module object. Trace may not be reliable.
Oops: 0000
CPU: 0
EIP: 0010:[<f0089d42>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010207
eax: 00000000 ebx: eed8c200 ecx: ee9f9100 edx: 00000000
esi: 00010011 edi: ee9ae2e0 ebp: ee9f9100 esp: c029fe98
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c029f000)
Stack: ee9f7180 eed8c200 f00890e3 eed8c200 ee9f9100 2e9f7180 00018148 ee9f914c
01d8c200 00000000 00000001 00000001 ee9f914c ee9f7120 00000000 00000000
dd9f9100 000017f8 f008b3fb eed8c200 ee9f9100 c029ff8c 00000000 ee9f6bfc
Call Trace: [<f00890e3>] [<f008b3fb>] [<f008bcdc>] [<f0049d4a>] [<c010a5d5>]
[<c010a754>] [<c010cc78>] [<c0110018>] [<c0106fb3>] [<c0114c9c>] [<c0114b60>]
[<c0107042>] [<c0105000>]
Code: 8b 40 48 39 c8 75 f7 8b 01 89 02 8b 41 48 89 42 48 8b 83 00
>>EIP; f0089d42 <[ehci-hcd]start_unlink_async+32/e0> <=====
>>ebx; eed8c200 <_end+2ea8f728/2fd10588>
>>ecx; ee9f9100 <_end+2e6fc628/2fd10588>
>>edi; ee9ae2e0 <_end+2e6b1808/2fd10588>
>>ebp; ee9f9100 <_end+2e6fc628/2fd10588>
>>esp; c029fe98 <init_task_union+1e98/2000>
Trace; f00890e3 <[ehci-hcd]qh_completions+1f3/2d0>
Trace; f008b3fb <[ehci-hcd]scan_periodic+1cb/230>
Trace; f008bcdc <[ehci-hcd]ehci_work+4c/d0>
Trace; f0049d4a <[usbcore]hcd_irq+2a/60>
Trace; c010a5d5 <handle_IRQ_event+45/70>
Trace; c010a754 <do_IRQ+64/a0>
Trace; c010cc78 <call_do_IRQ+5/d>
Trace; c0110018 <pci_conf2_write_config_byte+8/60>
Trace; c0106fb3 <default_idle+23/40>
Trace; c0114c9c <apm_cpu_idle+13c/160>
Trace; c0114b60 <apm_cpu_idle+0/160>
Trace; c0107042 <cpu_idle+52/70>
Trace; c0105000 <_stext+0/0>
Code; f0089d42 <[ehci-hcd]start_unlink_async+32/e0>
00000000 <_EIP>:
Code; f0089d42 <[ehci-hcd]start_unlink_async+32/e0> <=====
0: 8b 40 48 mov 0x48(%eax),%eax <=====
Code; f0089d45 <[ehci-hcd]start_unlink_async+35/e0>
3: 39 c8 cmp %ecx,%eax
Code; f0089d47 <[ehci-hcd]start_unlink_async+37/e0>
5: 75 f7 jne fffffffe <_EIP+0xfffffffe>
Code; f0089d49 <[ehci-hcd]start_unlink_async+39/e0>
7: 8b 01 mov (%ecx),%eax
Code; f0089d4b <[ehci-hcd]start_unlink_async+3b/e0>
9: 89 02 mov %eax,(%edx)
Code; f0089d4d <[ehci-hcd]start_unlink_async+3d/e0>
b: 8b 41 48 mov 0x48(%ecx),%eax
Code; f0089d50 <[ehci-hcd]start_unlink_async+40/e0>
e: 89 42 48 mov %eax,0x48(%edx)
Code; f0089d53 <[ehci-hcd]start_unlink_async+43/e0>
11: 8b 83 00 00 00 00 mov 0x0(%ebx),%eax
<0>Kernel panic: Aiee, killing interrupt handler!
2 warnings and 3 errors issued. Results may not be reliable.
lspci output:
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (CNR) Ethernet Controller (rev 81)
01:0c.0 Bridge: PLX Technology, Inc. PCI <-> IOBus Bridge (rev 0a)
01:0f.0 VGA compatible controller: Chips and Technologies F65550 (rev c6)
--
Karl Kiniger mailto:[email protected]
GE Medical Systems Kretztechnik GmbH & Co OHG
Tiefenbach 15 Tel: (++43) 7682-3800-710
A-4871 Zipf Austria Fax: (++43) 7682-3800-47
You may try to unload the ehci-hcd driver and load only uhci and check if
it still happens. I guess from the trace that the problem lies in the ehci
driver itself.
Regards,
willy
On Tue, Apr 12, 2005 at 07:39:11PM +0200, Kiniger wrote:
> Pls see the hand-copied decoded backtrace.
>
> It happens when I connect a Seagate 160 GB external USB
> hard disk. (I dont have access to this particular drive
> just now but under Windows I have seen it as an ST3316002 3A
> USB Device) - Oops happens reliably just after I plug the
> drive in.
>
> When connecting a Maxtor USB disk there is no Oops however.
>
> Kernel is 2.4.30-pre4 (same as 2.4.30) with the
> TNG NTFS patches from Anton Altaparmakov but it is not
> in use when it happens. There are no hotplug, automount etc.
> scripts on this system.
>
> suggestions from the USB experts are welcome.
>
> Greetings,
> Karl
>
> ksymoops 2.4.11 on i686 2.6.10-1.770_FC3. Options used
> -v vmlinux (specified)
> -k ksyms.out (specified)
> -l modules.out (specified)
> -o /lib/modules/2.4.30-rc4 (specified)
> -m System.map (specified)
>
> Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
> Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
> Error (pclose_local): find_objects pclose failed 0x100
> Warning (compare_ksyms_lsmod): module Module is in lsmod but not in ksyms, probably no symbols exported
> Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique module object. Trace may not be reliable.
> Oops: 0000
> CPU: 0
> EIP: 0010:[<f0089d42>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010207
> eax: 00000000 ebx: eed8c200 ecx: ee9f9100 edx: 00000000
> esi: 00010011 edi: ee9ae2e0 ebp: ee9f9100 esp: c029fe98
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 0, stackpage=c029f000)
> Stack: ee9f7180 eed8c200 f00890e3 eed8c200 ee9f9100 2e9f7180 00018148 ee9f914c
> 01d8c200 00000000 00000001 00000001 ee9f914c ee9f7120 00000000 00000000
> dd9f9100 000017f8 f008b3fb eed8c200 ee9f9100 c029ff8c 00000000 ee9f6bfc
> Call Trace: [<f00890e3>] [<f008b3fb>] [<f008bcdc>] [<f0049d4a>] [<c010a5d5>]
> [<c010a754>] [<c010cc78>] [<c0110018>] [<c0106fb3>] [<c0114c9c>] [<c0114b60>]
> [<c0107042>] [<c0105000>]
> Code: 8b 40 48 39 c8 75 f7 8b 01 89 02 8b 41 48 89 42 48 8b 83 00
>
>
> >>EIP; f0089d42 <[ehci-hcd]start_unlink_async+32/e0> <=====
>
> >>ebx; eed8c200 <_end+2ea8f728/2fd10588>
> >>ecx; ee9f9100 <_end+2e6fc628/2fd10588>
> >>edi; ee9ae2e0 <_end+2e6b1808/2fd10588>
> >>ebp; ee9f9100 <_end+2e6fc628/2fd10588>
> >>esp; c029fe98 <init_task_union+1e98/2000>
>
> Trace; f00890e3 <[ehci-hcd]qh_completions+1f3/2d0>
> Trace; f008b3fb <[ehci-hcd]scan_periodic+1cb/230>
> Trace; f008bcdc <[ehci-hcd]ehci_work+4c/d0>
> Trace; f0049d4a <[usbcore]hcd_irq+2a/60>
> Trace; c010a5d5 <handle_IRQ_event+45/70>
> Trace; c010a754 <do_IRQ+64/a0>
> Trace; c010cc78 <call_do_IRQ+5/d>
> Trace; c0110018 <pci_conf2_write_config_byte+8/60>
> Trace; c0106fb3 <default_idle+23/40>
> Trace; c0114c9c <apm_cpu_idle+13c/160>
> Trace; c0114b60 <apm_cpu_idle+0/160>
> Trace; c0107042 <cpu_idle+52/70>
> Trace; c0105000 <_stext+0/0>
>
> Code; f0089d42 <[ehci-hcd]start_unlink_async+32/e0>
> 00000000 <_EIP>:
> Code; f0089d42 <[ehci-hcd]start_unlink_async+32/e0> <=====
> 0: 8b 40 48 mov 0x48(%eax),%eax <=====
> Code; f0089d45 <[ehci-hcd]start_unlink_async+35/e0>
> 3: 39 c8 cmp %ecx,%eax
> Code; f0089d47 <[ehci-hcd]start_unlink_async+37/e0>
> 5: 75 f7 jne fffffffe <_EIP+0xfffffffe>
> Code; f0089d49 <[ehci-hcd]start_unlink_async+39/e0>
> 7: 8b 01 mov (%ecx),%eax
> Code; f0089d4b <[ehci-hcd]start_unlink_async+3b/e0>
> 9: 89 02 mov %eax,(%edx)
> Code; f0089d4d <[ehci-hcd]start_unlink_async+3d/e0>
> b: 8b 41 48 mov 0x48(%ecx),%eax
> Code; f0089d50 <[ehci-hcd]start_unlink_async+40/e0>
> e: 89 42 48 mov %eax,0x48(%edx)
> Code; f0089d53 <[ehci-hcd]start_unlink_async+43/e0>
> 11: 8b 83 00 00 00 00 mov 0x0(%ebx),%eax
>
> <0>Kernel panic: Aiee, killing interrupt handler!
>
> 2 warnings and 3 errors issued. Results may not be reliable.
>
> lspci output:
> 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
> 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
> 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller (rev 01)
> 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller (rev 01)
> 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
> 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
> 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
> 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
> 01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (CNR) Ethernet Controller (rev 81)
> 01:0c.0 Bridge: PLX Technology, Inc. PCI <-> IOBus Bridge (rev 0a)
> 01:0f.0 VGA compatible controller: Chips and Technologies F65550 (rev c6)
>
>
> --
> Karl Kiniger mailto:[email protected]
> GE Medical Systems Kretztechnik GmbH & Co OHG
> Tiefenbach 15 Tel: (++43) 7682-3800-710
> A-4871 Zipf Austria Fax: (++43) 7682-3800-47
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
On Thu, Apr 14, 2005 at 07:02:44AM +0200, Willy Tarreau wrote:
> You may try to unload the ehci-hcd driver and load only uhci and check if
> it still happens. I guess from the trace that the problem lies in the ehci
> driver itself.
Your guess is right. With only uhci loaded it works (dog slow of course).
When I then insmod the ehci-hcd driver: instant Oops.
Today I tried with another USB 2.0 enclosure w/o crash - it seems
to dislike especially the Seagate enclosure.
perhaps the output of cat /proc/bus/usb/devices gives some hint?
(BTW: what does the asterisk in the 'C:' lines mean?)
On the two "GE Med. Kretz" USB<>IDE devices there is
a DVD recorder and a Maxtor HD connected, both are working fine
as long as nobody tries to plug in this particular Seagate.
What to do next? I have no clue about the innards of ehci-hcd....
Regards and thanks for trying to help,
Karl
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0bc2 ProdID=0500 Rev= 0.00
S: Manufacturer=Seagate
S: Product=Seagate Mass Storage
S: SerialNumber=3JS461VN0000
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04b4 ProdID=6560 Rev= 0.08
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04ce ProdID=0002 Rev= 0.01
S: Manufacturer=GE Med. Kretz
S: Product=USB to IDE
S: SerialNumber=DEF107F12FAB
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04ce ProdID=0002 Rev= 0.01
S: Manufacturer=GE Med. Kretz
S: Product=USB to IDE
S: SerialNumber=DEF107F12FC6
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>
> Regards,
> willy
>
> On Tue, Apr 12, 2005 at 07:39:11PM +0200, Kiniger wrote:
> > Pls see the hand-copied decoded backtrace.
[ deleted ]
--
Karl Kiniger mailto:[email protected]
GE Medical Systems Kretztechnik GmbH & Co OHG
Tiefenbach 15 Tel: (++43) 7682-3800-710
A-4871 Zipf Austria Fax: (++43) 7682-3800-47
On Fri, Apr 15, 2005 at 02:50:48PM +0200, Karl Kiniger wrote:
> On Thu, Apr 14, 2005 at 07:02:44AM +0200, Willy Tarreau wrote:
> > You may try to unload the ehci-hcd driver and load only uhci and check if
> > it still happens. I guess from the trace that the problem lies in the ehci
> > driver itself.
>
> Your guess is right. With only uhci loaded it works (dog slow of course).
> When I then insmod the ehci-hcd driver: instant Oops.
>
> Today I tried with another USB 2.0 enclosure w/o crash - it seems
> to dislike especially the Seagate enclosure.
Fine, it may not be an important bug.
> perhaps the output of cat /proc/bus/usb/devices gives some hint?
> (BTW: what does the asterisk in the 'C:' lines mean?)
I don't remember at all...
> On the two "GE Med. Kretz" USB<>IDE devices there is
> a DVD recorder and a Maxtor HD connected, both are working fine
> as long as nobody tries to plug in this particular Seagate.
>
> What to do next? I have no clue about the innards of ehci-hcd....
You should CC the ehci-hcd the usb-storage maintainers, they probably
will have more clues or ideas about what you encounter. A post to the
linux-usb-users list would be a good idea too. Also, if you can test
2.6 and find that it is broken only on 2.4, it will be easier for them
to send you some code to try.
Regards,
Willy
On Sat, Apr 16, 2005 at 07:53:05AM +0200, Willy Tarreau wrote:
> On Fri, Apr 15, 2005 at 02:50:48PM +0200, Karl Kiniger wrote:
> > On Thu, Apr 14, 2005 at 07:02:44AM +0200, Willy Tarreau wrote:
> > > You may try to unload the ehci-hcd driver and load only uhci and check if
> > > it still happens. I guess from the trace that the problem lies in the ehci
> > > driver itself.
> >
> > Your guess is right. With only uhci loaded it works (dog slow of course).
> > When I then insmod the ehci-hcd driver: instant Oops.
> >
> > Today I tried with another USB 2.0 enclosure w/o crash - it seems
> > to dislike especially the Seagate enclosure.
>
> Fine, it may not be an important bug.
To you :) - it is annoying for me.
>
> > perhaps the output of cat /proc/bus/usb/devices gives some hint?
> > (BTW: what does the asterisk in the 'C:' lines mean?)
>
> I don't remember at all...
>
> > On the two "GE Med. Kretz" USB<>IDE devices there is
> > a DVD recorder and a Maxtor HD connected, both are working fine
> > as long as nobody tries to plug in this particular Seagate.
> >
> > What to do next? I have no clue about the innards of ehci-hcd....
>
> You should CC the ehci-hcd the usb-storage maintainers, they probably
tks for advice.
> will have more clues or ideas about what you encounter. A post to the
> linux-usb-users list would be a good idea too. Also, if you can test
> 2.6 and find that it is broken only on 2.4, it will be easier for them
> to send you some code to try.
I will try to boot something like knoppix or RIP with a 2.6 kernel
and see what happens.
Thanks anyways,
Karl
>
> Regards,
> Willy
--
Karl Kiniger mailto:[email protected]
GE Medical Systems Kretztechnik GmbH & Co OHG
Tiefenbach 15 Tel: (++43) 7682-3800-710
A-4871 Zipf Austria Fax: (++43) 7682-3800-47