Sorry that I asked again but is there still someone
tracking this bug? I really would love to get this working.

Thanks a lot Fabian

On Wed, Sep 18, 2002 at 09:10:54PM +0200, Fabian Sturm wrote:
> Hello!
> 
> Sure I can provide you with more information.
> Just tell me what else I can do to track it down.
> 
> Now with klogd -x started and pasted from dmesg I get.
> 
> Initializing USB Mass Storage driver...
> usb.c: registered new driver usb-storage
> scsi2 : SCSI emulation for USB Mass Storage devices
> usb-uhci.c: interrupt, status 3, frame# 935
> usb-uhci.c: interrupt, status 3, frame# 697
> usb.c: USB disconnect on device 00:1f.4-1 address 2
> Unable to handle kernel paging request at virtual address 01100112
>  printing eip:
> d09508b7
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<d09508b7>]    Not tainted
> EFLAGS: 00010246
> eax: 01100112   ebx: 00000004   ecx: 00000004   edx: 01100112
> esi: cc54c0cc   edi: 01100112   ebp: cc54c000   esp: c003df54
> ds: 0018   es: 0018   ss: 0018
> Process scsi_eh_2 (pid: 834, stackpage=c003d000)
> Stack: 00000286 cc54c400 00000000 cc54c600 00000000 01100112 d09622ad cc54c000 
>        00000286 cc54c600 00000000 cc54c600 cc54c544 c01f3927 cc54c600 00002003 
>        00000000 c01f3f97 cc54c600 c003dfe0 cbc03160 cbc03160 cc54c4ac 00000000 
> Call Trace:    [<d09622ad>] [<c01f3927>] [<c01f3f97>] [<c01f443b>] [<c0106ec0>]
> 
> Code: f3 a6 0f 84 c1 00 00 00 52 e8 37 9b 7d ef 55 e8 f9 d1 ff ff 
>  <6>hub.c: new USB device 00:1f.4-1, assigned address 3
> 
> 
> 
> and here goes the output of ksymoops
> 
> 
> ksymoops 2.4.5 on i686 2.4.20-pre7.  Options used
>      -V (default)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.4.20-pre7/ (default)
>      -m /boot/System.map-2.4.20-pre7 (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 01100112
> d09508b7
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<d09508b7>]    Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010246
> eax: 01100112   ebx: 00000004   ecx: 00000004   edx: 01100112
> esi: cc54c0cc   edi: 01100112   ebp: cc54c000   esp: c003df54
> ds: 0018   es: 0018   ss: 0018
> Process scsi_eh_2 (pid: 834, stackpage=c003d000)
> Stack: 00000286 cc54c400 00000000 cc54c600 00000000 01100112 d09622ad cc54c000 
>        00000286 cc54c600 00000000 cc54c600 cc54c544 c01f3927 cc54c600 00002003 
>        00000000 c01f3f97 cc54c600 c003dfe0 cbc03160 cbc03160 cc54c4ac 00000000 
> Call Trace:    [<d09622ad>] [<c01f3927>] [<c01f3f97>] [<c01f443b>] [<c0106ec0>]
> Code: f3 a6 0f 84 c1 00 00 00 52 e8 37 9b 7d ef 55 e8 f9 d1 ff ff 
> 
> 
> >>EIP; d09508b7 <[usbcore]usb_reset_device+1af/311>   <=====
> 
> >>eax; 01100112 Before first symbol
> >>edx; 01100112 Before first symbol
> >>esi; cc54c0cc <_end+c220250/104ec184>
> >>edi; 01100112 Before first symbol
> >>ebp; cc54c000 <_end+c220184/104ec184>
> >>esp; c003df54 Before first symbol
> 
> Trace; d09622ad <[usb-storage]bus_reset+5d/150>
> Trace; c01f3927 <scsi_try_bus_reset+3b/88>
> Trace; c01f3f97 <scsi_unjam_host+357/72c>
> Trace; c01f443b <scsi_error_handler+cf/130>
> Trace; c0106ec0 <kernel_thread+28/38>
> 
> Code;  d09508b7 <[usbcore]usb_reset_device+1af/311>
> 00000000 <_EIP>:
> Code;  d09508b7 <[usbcore]usb_reset_device+1af/311>   <=====
>    0:   f3 a6                     repz cmpsb %es:(%edi),%ds:(%esi)   <=====
> Code;  d09508b9 <[usbcore]usb_reset_device+1b1/311>
>    2:   0f 84 c1 00 00 00         je     c9 <_EIP+0xc9> d0950980 
><[usbcore]usb_reset_device+278/311>
> Code;  d09508bf <[usbcore]usb_reset_device+1b7/311>
>    8:   52                        push   %edx
> Code;  d09508c0 <[usbcore]usb_reset_device+1b8/311>
>    9:   e8 37 9b 7d ef            call   ef7d9b45 <_EIP+0xef7d9b45> c012a3fc 
><kfree+0/b0>
> Code;  d09508c5 <[usbcore]usb_reset_device+1bd/311>
>    e:   55                        push   %ebp
> Code;  d09508c6 <[usbcore]usb_reset_device+1be/311>
>    f:   e8 f9 d1 ff ff            call   ffffd20d <_EIP+0xffffd20d> d094dac4 
><[usbcore]usb_destroy_configuration+0/1b4>
> 
> 
> 1 warning issued.  Results may not be reliable.
> 
> Hope that helps, 
> 
> Sincerly fabian
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: AMD - Your access to the experts
> on Hammer Technology! Open Source & Linux Developers, register now
> for the AMD Developer Symposium. Code: EX8664
> http://www.developwithamd.com/developerlab
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to