> Before I round up the ksymoops log (it requires setting up a serial
> console), should I try testing with a later version of usbtest? Is this a
> known issue?

The log was easier to get than I expected. It's attached.

On second glance, it looks like an issue in uhci-hdc. I may be able to
test this at home with an OHCI controller, but before I do, any other
tips? Should I look at usbtest.c from one of the BK trees?

-- 
Charles Lepple <[EMAIL PROTECTED]>
http://www.ghz.cc/charles/
ksymoops 2.4.5 on i686 2.6.0-test1.1.  Options used
     -v /home/charles/dl/linux-2.6.0-test1/vmlinux (specified)
     -K (specified)
     -l /proc/modules (default)
     -o /lib/modules/2.6.0-test1.1/ (default)
     -m /boot/System.map-2.6.0-test1.1 (default)

No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address 6b6b6b6f
c025a7aa
*pde = 00000000
Oops: 0002 [#1]
CPU:    0
EIP:    0060:[<c025a7aa>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010083
eax: c60bf194   ebx: 6b6b6b6b   ecx: 6b6b6b6b   edx: c037e000
esi: c037e000   edi: 6b6b6b6b   ebp: c7ecbb38   esp: c037fe9c
ds: 007b   es: 007b   ss: 0068
Stack: 00000296 c7ecbb30 00000000 0000fce0 c7ecb94c c037ff2c c025a8c3 c7ecb94c 
       c010b048 c7ecb94c 00000003 00000000 c037ff2c c024e07f c7ecb94c c037ff2c 
       c7e72d34 04000001 c010c919 0000000a c7ecb94c c037ff2c c037e000 0000000a 
 [<c025a8c3>] uhci_irq+0xa3/0x160
 [<c010b048>] common_interrupt+0x18/0x20
 [<c024e07f>] usb_hcd_irq+0x2f/0x60
 [<c010c919>] handle_IRQ_event+0x49/0x80
 [<c010cca9>] do_IRQ+0xa9/0x170
 [<c010b048>] common_interrupt+0x18/0x20
 [<c011f4ce>] do_softirq+0x3e/0xa0
 [<c010cd17>] do_IRQ+0x117/0x170
 [<c0108b70>] default_idle+0x0/0x40
 [<c0108b70>] default_idle+0x0/0x40
 [<c010b048>] common_interrupt+0x18/0x20
 [<c0108b70>] default_idle+0x0/0x40
 [<c0108b70>] default_idle+0x0/0x40
 [<c0108b94>] default_idle+0x24/0x40
 [<c0108c2a>] cpu_idle+0x3a/0x50
 [<c0105000>] rest_init+0x0/0x60
 [<c038073d>] start_kernel+0x16d/0x1a0
 [<c0380470>] unknown_bootoption+0x0/0x120
Code: 89 4f 04 89 39 89 40 04 89 00 c7 43 18 98 ff ff ff c7 40 20 


>>EIP; c025a7aa <uhci_remove_pending_qhs+4a/c0>   <=====

>>eax; c60bf194 <__crc_fsync_bdev+17b408/2f4208>
>>ebx; 6b6b6b6b <__crc___ide_dma_on+d44f5/144a23>
>>ecx; 6b6b6b6b <__crc___ide_dma_on+d44f5/144a23>
>>edx; c037e000 <init_thread_union+0/2000>
>>esi; c037e000 <init_thread_union+0/2000>
>>edi; 6b6b6b6b <__crc___ide_dma_on+d44f5/144a23>
>>ebp; c7ecbb38 <__crc_strspn+4f11/2ec817>
>>esp; c037fe9c <init_thread_union+1e9c/2000>

Code;  c025a7aa <uhci_remove_pending_qhs+4a/c0>
00000000 <_EIP>:
Code;  c025a7aa <uhci_remove_pending_qhs+4a/c0>   <=====
   0:   89 4f 04                  mov    %ecx,0x4(%edi)   <=====
Code;  c025a7ad <uhci_remove_pending_qhs+4d/c0>
   3:   89 39                     mov    %edi,(%ecx)
Code;  c025a7af <uhci_remove_pending_qhs+4f/c0>
   5:   89 40 04                  mov    %eax,0x4(%eax)
Code;  c025a7b2 <uhci_remove_pending_qhs+52/c0>
   8:   89 00                     mov    %eax,(%eax)
Code;  c025a7b4 <uhci_remove_pending_qhs+54/c0>
   a:   c7 43 18 98 ff ff ff      movl   $0xffffff98,0x18(%ebx)
Code;  c025a7bb <uhci_remove_pending_qhs+5b/c0>
  11:   c7 40 20 00 00 00 00      movl   $0x0,0x20(%eax)

 <0>Kernel panic: Fatal exception in interrupt

Reply via email to