David Brownell wrote:
> 
> > > > usb-ohci.c: USB OHCI at membase 0xd3874000, IRQ 11
> > > > usb-ohci.c: usb-00:07.4, Advanced Micro Devices [AMD] AMD-756 [Viper]
> > > > USB
> > >
> > But 2.4.0-ac12, 2.4.1-ac18, and 2.4.2-ac1->ac3 worked fine
> > (I'm not sure on the 2.4.2 series, Alan's been releasing patches
> > faster than I can grab, patch, build, and boot them :)
> 
> I don't remember seeing those -ac5 patches go by linux-usb-devel,
> and the "thread wakeup scheduling" one was the only one you listed
> that sounded like it might have mattered.

I finally checked, and ac4 works, ac5 oopses.
The oops is in kfree called from usb-ohci

Here's the oops from 2.4.2-ac5 when booting
with the mouse plugged in. The oops looks similar
if I plug the mouse in after the system is up.
I have the ac4-ac5 diff if it might help,
the whole kernel and just drivers/usb/

        -Thomas
ksymoops 2.3.7 on i686 2.4.2-ac5.  Options used
     -v linux-2.4.2-ac5/vmlinux (specified)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.2-ac5/ (default)
     -m /boot/System.map-2.4.2-ac5 (specified)

Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not 
found in vmlinux.  Ignoring ksyms_base entry
Warning (compare_maps): mismatch on symbol partition_name  , ksyms_base says c01d9520, 
vmlinux says c0153060.  Ignoring ksyms_base entry
EIP: 0010 [<c012ac0c>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010866
eax: 0000001b   ebx: c14dcf50   ecx: 00000001   edx: c027a288
esi: c14dc000   edi: c14dcf84   ebp: c14470c0   esp: c0299e10
 ds: 0018        es: 0018        ss: 0018 
Process swapper ( pid:0, stackpage=c0299000 )
Stack: c022f76f c022f80f 00000576 cff1b6c4 d14dcf4c 00000086 c14dcf94 00000000
       c14dcf84 c14dcf84 d386e08c c14dcf50 c018e08d c030e20c c146918c 00000286
       cfefc3f4 c14dcf84 00000000 d386e0fd cfc9d194 c14dcf84 00000297 c14dcf84
Call Trace: [<d3874000>] [<c018e08d>] [<d386e0fd>] [<d386e12e>] [<d386e238>] 
[<d386fd97>]
       [<d387400c>] [<d3874000>] [<d3870e6a>] [<d3874014>] [<d3871af7>] [<c010a359>]
       [<c010a4c8>] [<c0109120>] [<c01d416a>] [<c01c720e>] [<c01c6e65>] [<c01c6a74>]
       [<c01d53a0>] [<c01d5644>] [<c01d5410>] [<c01072e2>] [<c0105000>] [<c0100191>]
CODE: 0f 0b 83 c4 0c 8b 54 24 04 b8 71 f0 2c 5a 03 55 0c 87 42 fc

>>EIP; c012ac0c <kfree+18c/2a0>   <=====
Trace; d3874000 <[usb-ohci].data.end+1f21/3f81>
Trace; c018e08d <ide_dma_intr+6d/a0>
Trace; d386e0fd <[usb-ohci]urb_rm_priv_locked+4d/70>
Trace; d386e12e <[usb-ohci]urb_rm_priv+e/20>
Trace; d386e238 <[usb-ohci]sohci_return_urb+f8/110>
Trace; d386fd97 <[usb-ohci]dl_done_list+a7/100>
Trace; d387400c <[usb-ohci].data.end+1f2d/3f81>
Trace; d3874000 <[usb-ohci].data.end+1f21/3f81>
Trace; d3870e6a <[usb-ohci]hc_interrupt+ba/1b0>
Trace; d3874014 <[usb-ohci].data.end+1f35/3f81>
Trace; d3871af7 <[usb-ohci].rodata.start+317/7ec>
Trace; c010a359 <handle_IRQ_event+39/60>
Trace; c010a4c8 <do_IRQ+68/b0>
Trace; c0109120 <ret_from_intr+0/20>
Trace; c01d416a <acpi_os_out16+a/10>
Trace; c01c720e <acpi_hw_low_level_write+fe/190>
Trace; c01c6e65 <acpi_hw_register_write+145/240>
Trace; c01c6a74 <acpi_hw_register_bit_access+2c4/380>
Trace; c01d53a0 <acpi_sleep_on_busmaster+10/20>
Trace; c01d5644 <acpi_idle+234/290>
Trace; c01d5410 <acpi_idle+0/290>
Trace; c01072e2 <cpu_idle+52/70>
Trace; c0105000 <empty_bad_page+0/1000>
Trace; c0100191 <L6+0/2>
Code;  c012ac0c <kfree+18c/2a0>
00000000 <_EIP>:
Code;  c012ac0c <kfree+18c/2a0>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c012ac0e <kfree+18e/2a0>
   2:   83 c4 0c                  add    $0xc,%esp
Code;  c012ac11 <kfree+191/2a0>
   5:   8b 54 24 04               mov    0x4(%esp,1),%edx
Code;  c012ac15 <kfree+195/2a0>
   9:   b8 71 f0 2c 5a            mov    $0x5a2cf071,%eax
Code;  c012ac1a <kfree+19a/2a0>
   e:   03 55 0c                  add    0xc(%ebp),%edx
Code;  c012ac1d <kfree+19d/2a0>
  11:   87 42 fc                  xchg   %eax,0xfffffffc(%edx)


2 warnings issued.  Results may not be reliable.

Reply via email to