Hi Folks.

I'm running a RH8.0 system, custom kernel on an Abit KA7 mobo. Trying to
use a Microtek V6USL scanner over USB. I've had the same problem on an
older kernel -- 2.4.7, I think.

Based on the web and mailing list archives I've searched, it appears to be
a common problem, but I haven't found any mentions of whether there's a
patch available, or if it's fixed in newer 2.4.x kernels.

I've transcribed the console output, and run it through ksymoops, but I
don't see the details in the oops report typical of other bug reports I've
read -- probably the bad transcription on my part. I did make sure I had
the same modules loaded when I ran ksymoops. Nonetheless ...

[console output]

usb-uhci.c: interrupt, status 3, frame # 893
unable to handle kernel paging request at virtual address b48d83f7
printing eip: c0133bab
#pde = 00000000
Oops: 0000
cpu: 0
eip: 0010[<c0133bab>] Not tainted
eflags: 00010016
eip is at (2.4.18-14custom)
eax: 00d00000 ebx: ffff3f4c ecs: b48d83eb edx: 00000000
esi: 000000a3 edi: cf3bb5c0 ebp: cd113400 esp: cef4dd8c
ds: 0018 es: 0018 ss: 0018

Process usb.agent (pid: 1815, stackpage=cef4d000)
Stack:
  c1aa0a80 00000206 00000000 c01335a3 ffff3f4c 000000a3 cd113400 d08f5d2b
  000000a3 00000086 00000296 cefc1ea0          cd113400 00000000 cf3bb5c0
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
        any of these could be shifted right one position
        obviously, I dropped a word here ;-(
  cd113400 cd113400 00000000 cf3bb5c0 cd113400 d08f5157 cd113400 00000000

Call Trace:
  [<c01335a3>] (0xcef9dd98))
  [<d08f5d2b>] (0xcef9dda8))
  [<d08f5157>] (0xcef9dde0))
  [<d08caba4>] (0xcef9ddec))
  [<d08cad33>] (0xcef9de18))
  [<c010a335>] (0xcef9de44))
  [<c010a4c5>] (0xcef9de64))
  [<c010ca98>] (0xcef9de84))
  [<c012d6a2>] (0xcef9deb0))
  [<c012a39d>] (0xcef9dec0))
  [<c012ac64>] (0xcef9dee0))
  [<c0117796>] (0xcef9df0c))
  [<c011a11a>] (0xcef9df38))
  [<c0107350>] (0xcef9df44))
  [<c011a99c>] (0xcef9df5c))
  [<c013ca6d>] (0xcef9df98))
  [<c0117670>] (0xcef9dfb0))
  [<c0108e20>] (0xcef9dfb8))

Code: 2b 71 0c 89 f0 f7 73 18 89 c6 86 41 14 89 44 b1 18 8b 51 10
<0> Kernel Panic: Aiee, killing interrupt handler!
In interrupt handler, not syncing

[ksymoops output]

ksymoops 2.4.5 on i686 2.4.18-14custom.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.18-14custom/ (default)
     -m /boot/System.map-2.4.18-14custom (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 b48d83f7
Oops: 0000
cpu: 0
eip: 0010[<c0133bab>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
eflags: 00010016
eax: 00d00000 ebx: ffff3f4c ecs: b48d83eb edx: 00000000
Warning (Oops_set_regs): garbage 'ecs: b48d83eb edx: 00000000' at end of
register line ignored
esi: 000000a3 edi: cf3bb5c0 ebp: cd113400 esp: cef4dd8c
ds: 0018 es: 0018 ss: 0018
Process usb.agent (pid: 1815, stackpage=cef4d000)
  c1aa0a80 00000206 00000000 c01335a3 ffff3f4c 000000a3 cd113400 d08f5d2b
  000000a3 00000086 00000296 cefc1ea0 ffffffff cd113400 00000000 cf3bb5c0
  cd113400 cd113400 00000000 cf3bb5c0 cd113400 d08f5157 cd113400 00000000
  [<c01335a3>] (0xcef9dd98))
  [<d08f5d2b>] (0xcef9dda8))
  [<d08f5157>] (0xcef9dde0))
  [<d08caba4>] (0xcef9ddec))
  [<d08cad33>] (0xcef9de18))
  [<c010a335>] (0xcef9de44))
  [<c010a4c5>] (0xcef9de64))
  [<c010ca98>] (0xcef9de84))
  [<c012d6a2>] (0xcef9deb0))
  [<c012a39d>] (0xcef9dec0))
  [<c012ac64>] (0xcef9dee0))
  [<c0117796>] (0xcef9df0c))
  [<c011a11a>] (0xcef9df38))
  [<c0107350>] (0xcef9df44))
  [<c011a99c>] (0xcef9df5c))
  [<c013ca6d>] (0xcef9df98))
  [<c0117670>] (0xcef9dfb0))
  [<c0108e20>] (0xcef9dfb8))
Code: 2b 71 0c 89 f0 f7 73 18 89 c6 86 41 14 89 44 b1 18 8b 51 10


>>EIP; c0133bab <kmem_cache_free_one+2b/97>   <=====

>>eax; 00d00000 Before first symbol
>>ebx; ffff3f4c <END_OF_CODE+2f6ed52d/????>
>>edi; cf3bb5c0 <_end+f0cff28/1055a9e8>
>>ebp; cd113400 <_end+ce27d68/1055a9e8>
>>esp; cef4dd8c <_end+ec626f4/1055a9e8>

Code;  c0133bab <kmem_cache_free_one+2b/97>
00000000 <_EIP>:
Code;  c0133bab <kmem_cache_free_one+2b/97>   <=====
   0:   2b 71 0c                  sub    0xc(%ecx),%esi   <=====
Code;  c0133bae <kmem_cache_free_one+2e/97>
   3:   89 f0                     mov    %esi,%eax
Code;  c0133bb0 <kmem_cache_free_one+30/97>
   5:   f7 73 18                  divl   0x18(%ebx)
Code;  c0133bb3 <kmem_cache_free_one+33/97>
   8:   89 c6                     mov    %eax,%esi
Code;  c0133bb5 <kmem_cache_free_one+35/97>
   a:   86 41 14                  xchg   %al,0x14(%ecx)
Code;  c0133bb8 <kmem_cache_free_one+38/97>
   d:   89 44 b1 18               mov    %eax,0x18(%ecx,%esi,4)
Code;  c0133bbc <kmem_cache_free_one+3c/97>
  11:   8b 51 10                  mov    0x10(%ecx),%edx

<0> Kernel Panic: Aiee, killing interrupt handler!

2 warnings issued.  Results may not be reliable.

Any advice appreciated. There's a remote possibility I can run a serial
console, if I can find a null-modem cable -- unfortunately, I tossed out
nearly all my DB9/DB25 stuff a while ago, and any of it which remains is
in a box -- somewhere ...

jed

-- 
... it is poor civic hygiene to install technologies that could someday
facilitate a police state. -- Bruce Schneier


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to