And yes, OHCI also causes problems with a full backup of a Visor, or
even with a simple listing of the files in the Visor.
Running 2.4.0-test1-ac4 usb-ohci driver:
When the Visor completes whatever it was told to do, it disconnects from
the usb bus, this causes the attached oops which looks suspiciously like a
slab poisoning error.
This does not happen with either of the UHCI drivers (see my other email
message about the problems with UHCI...)
Anyone have any ideas?
thanks,
greg k-h
greg@(kroah|wirex).com
ksymoops 0.7c on i686 2.4.0-test1-ac4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test1-ac4/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Unable to handle kernel paging request at virtual address 5a5a5a5e
d0c16967
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<d0c16967>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0000002e ebx: 5a5a5a5a ecx: cf2c6800 edx: 5a5a5a5a
esi: 00030100 edi: 00000000 ebp: 00000001 esp: cee51f68
ds: 0018 es: 0018 ss: 0018
Process khubd (pid: 665, stackpage=cee51000)
Stack: 00000000 00030100 00000000 00000001 00000064 00000000 cf2c6800 d0c18529
cf2c6ae4 00000000 00000001 cf2c6a00 00030100 00000000 cee51fa8 00000064
00030100 d0c187bd cf2c6a00 00000000 cee50000 d0c1eb87 cee5022c d0c15048
Call Trace: [<d0c18529>] [<d0c187bd>] [<d0c1eb87>] [<d0c15048>] [<d0c20003>]
[<d0c180a1>] [<d0c18955>]
[<c01074a7>] [<d0c15000>]
Code: 80 7a 04 00 0f 84 f6 00 00 00 c7 44 24 10 00 00 00 00 8d b4
>>EIP; d0c16967 <[usbcore]usb_disconnect+4b/1bc> <=====
Trace; d0c18529 <[usbcore]usb_hub_port_connect_change+b9/2b8>
Trace; d0c187bd <[usbcore]usb_hub_events+95/1f4>
Trace; d0c1eb87 <[usbcore].rodata.start+1f87/3014>
Trace; d0c15048 <_end+10954898/109548a0>
Trace; d0c20003 <[usbcore].rodata.end+328/5c5>
Trace; d0c180a1 <[usbcore]hub_irq+cd/d4>
Trace; d0c18955 <[usbcore]usb_hub_thread+39/5c>
Trace; c01074a7 <kernel_thread+23/30>
Trace; d0c15000 <_end+10954850/109548a0>
Code; d0c16967 <[usbcore]usb_disconnect+4b/1bc>
00000000 <_EIP>:
Code; d0c16967 <[usbcore]usb_disconnect+4b/1bc> <=====
0: 80 7a 04 00 cmpb $0x0,0x4(%edx) <=====
Code; d0c1696b <[usbcore]usb_disconnect+4f/1bc>
4: 0f 84 f6 00 00 00 je 100 <_EIP+0x100> d0c16a67
<[usbcore]usb_disconnect+14b/1bc>
Code; d0c16971 <[usbcore]usb_disconnect+55/1bc>
a: c7 44 24 10 00 00 00 movl $0x0,0x10(%esp,1)
Code; d0c16978 <[usbcore]usb_disconnect+5c/1bc>
11: 00
Code; d0c16979 <[usbcore]usb_disconnect+5d/1bc>
12: 8d b4 00 00 00 00 00 lea 0x0(%eax,%eax,1),%esi
1 warning issued. Results may not be reliable.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
