Alan Stern wrote: > ... > The hang is almost certainly caused by the device's driver. Apparently > its disconnect method is not returning. Since that routine is called by > the main hub driver and with a lock held, this means that most other major > activities of the USB stack will be blocked as well.
Interesting, will have a look at the driver's disconnect routine. Maybe some printks or the driver's debugging stuff can give more hints. > > To get more information when you see these messages in the log and things > are hung up, get a stack trace with Alt-SysRq-T. The entry for khubd is > of particular interest; others may be important also depending on the > driver. > Thanks, noted for the next event. Jan
signature.asc
Description: OpenPGP digital signature
