Curious, it BUG()s in the scheduler with a somewhat odd looking stack. What's at line 551 in that kernel? This could be a non-USB problem...
> kernel BUG at sched.c 551! > ... > >>EIP; c01125b0 <schedule+6c/31c> <===== > Trace; c01f404e <sohci_submit_urb+4f6/510> > Trace; c011251a <schedule_timeout+72/90> > Trace; c011245c <process_timeout+0/4c> > ... > Code; c01125b0 <schedule+6c/31c> > 00000000 <_EIP>: > Code; c01125b0 <schedule+6c/31c> <===== > 0: 0f 0b ud2a <===== > Code; c01125b2 <schedule+6e/31c> > 2: 83 c4 08 add $0x8,%esp > Code; c01125b4 <schedule+70/31c> > 5: 0b 4d f4 or 0xfffffff4(%ebp),%ecx > Code; c01125b8 <schedule+74/31c> > 8: c1 e1 05 shl $0x5,%ecx > Code; c01125ba <schedule+76/31c> > b: 81 c1 40 b5 2e c0 add $0xc02eb540,%ecx > Code; c01125c0 <schedule+7c/31c> > 11: 89 4d fc mov %ecx,0xfffffffc(%ebp) > > <0>Kernel panic: Aiee, killing interrupt handler! > _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
