> Here is part of the stack trace from the oops/panic in my first > message about this problem: > > >>EIP; c012ad65 <kfree+35/a0> <===== > Trace; c4817ee4 <[usbcore]usb_destroy_configuration+104/210> > Trace; c48171e2 <[usbcore]usb_free_dev+22/50> > Trace; c48288b5 <[usb-uhci]process_urb+1e5/200> > Trace; c4828991 <[usb-uhci]uhci_interrupt+c1/130> > > As can be seen from the above, usb_destroy_configuration is called > from interrupt context [...]
Always remember that on x86 there are no frame pointers, so the stack trace is dirty with unrelated stuff. Cross-check with a code path. -- Pete _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
