Hi Greg,
I got the following oops with 2.5.8. Everything worked fine under 2.5.7.
-Udo.
ksymoops 2.4.4 on i686 2.5.8. Options used
-V (default)
-K (specified)
-l /proc/modules (default)
-o /lib/modules/2.5.8/ (default)
-m /boot/System.map-2.5.8 (specified)
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address 71596198
c0249608
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0249608>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 71596180 ebx: c1318000 ecx: c03457e0 edx: 71596180
esi: cfd2dac0 edi: c03457e0 ebp: 00000000 esp: cff3df24
ds: 0018 es: 0018 ss: 0018
Stack: c02592dd 71596180 cf89fb40 c03457c0 c024a451 cfce1600 c1318000 cfce15b8
cfd2d9c0 c03452c0 0000000f 00000000 cfce1600 c024a4c3 cfce15b8 00000100
00000004 00000002 c1369c00 000000c4 cfce1400 c024c76e c1369dbc 00000001
Call Trace: [<c02592dd>] [<c024a451>] [<c024a4c3>] [<c024c76e>] [<c024c44d>]
[<c024caf9>] [<c024ccb7>] [<c0105668>]
Code: 8b 42 18 85 c0 74 21 8b 80 cc 00 00 00 85 c0 74 17 8b 40 18
>>EIP; c0249608 <usb_unlink_urb+8/40> <=====
Trace; c02592dd <hid_disconnect+1d/90>
Trace; c024a451 <usb_disconnect+91/160>
Trace; c024a4c3 <usb_disconnect+103/160>
Trace; c024c76e <usb_hub_port_connect_change+4e/2c0>
Trace; c024c44d <usb_hub_port_status+6d/80>
Trace; c024caf9 <usb_hub_events+119/2a0>
Trace; c024ccb7 <usb_hub_thread+37/90>
Trace; c0105668 <kernel_thread+28/40>
Code; c0249608 <usb_unlink_urb+8/40>
00000000 <_EIP>:
Code; c0249608 <usb_unlink_urb+8/40> <=====
0: 8b 42 18 mov 0x18(%edx),%eax <=====
Code; c024960b <usb_unlink_urb+b/40>
3: 85 c0 test %eax,%eax
Code; c024960d <usb_unlink_urb+d/40>
5: 74 21 je 28 <_EIP+0x28> c0249630 <usb_unlink_urb+30/40>
Code; c024960f <usb_unlink_urb+f/40>
7: 8b 80 cc 00 00 00 mov 0xcc(%eax),%eax
Code; c0249615 <usb_unlink_urb+15/40>
d: 85 c0 test %eax,%eax
Code; c0249617 <usb_unlink_urb+17/40>
f: 74 17 je 28 <_EIP+0x28> c0249630 <usb_unlink_urb+30/40>
Code; c0249619 <usb_unlink_urb+19/40>
11: 8b 40 18 mov 0x18(%eax),%eax
On Mon, Apr 15, 2002 at 09:45:10AM +0200, Udo A. Steinberg wrote:
>
> Hi Greg,
>
> I got the following oops with 2.5.8. Everything worked fine under 2.5.7.
What USB devices and drivers are you using?
Which USB device did you remove when the oops happened?
thanks,
greg k-h
Hello,
Greg KH wrote:
> What USB devices and drivers are you using?
devices:
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=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=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=058f ProdID=9254 Rev= 1.00
S: Manufacturer=ALCOR
S: Product=Generic USB Hub
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=01 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=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0110 Rev= 1.10
S: Manufacturer=EPSON
S: Product=EPSON Scanner
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 5
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04cc ProdID=1122 Rev= 1.10
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=01 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=056d ProdID=0002 Rev= 3.86
S: Manufacturer=EIZO
S: Product=EIZO USB HID Monitor
S: SerialNumber=23710050
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=1ms
drivers:
usbfs
hub
96-111: hiddev
hid
48- 63: usbscanner
I'm using the "normal" UHCI driver, not the JE one. I believe the
oops is related to USB HID device support, which I didn't use in 2.5.7
but enabled for 2.5.8, after which the oops happened.
> Which USB device did you remove when the oops happened?
The HID device in question is the Eizo monitor which has a builtin USB
hub, which disconnects when the monitor is turned off and produces
the oops.
Regards,
Udo.
On Mon, Apr 15, 2002 at 06:28:50PM +0200, Udo A. Steinberg wrote:
> I'm using the "normal" UHCI driver, not the JE one. I believe the
> oops is related to USB HID device support, which I didn't use in 2.5.7
> but enabled for 2.5.8, after which the oops happened.
Could you test out 2.5.7 and the HID device support in that version to
see if this is a new problem or not?
thanks,
greg k-h
Greg KH wrote:
> Could you test out 2.5.7 and the HID device support in that version to
> see if this is a new problem or not?
Hello,
2.5.7 + HID support enabled produces the exact same oops.
Regards,
-Udo.
On Mon, Apr 15, 2002 at 07:37:44PM +0200, Udo A. Steinberg wrote:
> Greg KH wrote:
>
> > Could you test out 2.5.7 and the HID device support in that version to
> > see if this is a new problem or not?
>
> Hello,
>
> 2.5.7 + HID support enabled produces the exact same oops.
Good. Well, not good, but nice in that it doesn't look like the more
recent changes to the USB tree caused this. Can you send this oops and
info to the HID maintainer?
thanks,
greg k-h
Greg KH wrote:
> Good. Well, not good, but nice in that it doesn't look like the more
> recent changes to the USB tree caused this. Can you send this oops and
> info to the HID maintainer?
Sure, I'll send it to Vojtech.
Regards,
-Udo.