> >>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, and I don't see how a kernel thread could > serialize interrupt processing, unless it is preventing the interrupts > from triggering. > ... > Maybe the dec_and_test is not supposed to ever return true when called > from interrupt context.
Exactly. > That would indicate there is a reference > counting bug somewhere. Yes, such bugs do crop up from time to time. OHCI reports calls to the "free device" routine in_interrupt() as errors, it might be helpful if the UHCIs did the same thing. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
