On Mon, Jun 30, 2003 at 04:27:41PM -0700, David Brownell wrote: > > >>usb_disconnect() is never getting called from looking at the log. > >>Any other place you want me to put a message to see if it gets called? > >>With just CONFIG_USB_DEBUG enabled, I don't see any USB messages at all > >>before these start to loop. > > > > > >It looks like from the messages you pasted that uhci-hcd is seeing the > >device is detached. > > > >Maybe the hub driver thread is stuck somewhere? > > What I've usually seen in similar cases is that khubd can be > prevented from running by having too much debug output. > > So it's not that khubd would be stuck, it's just that it > would be starved out ...
That looks like what is happening here. khubd is at the RW state, so it really wants to run, but can't. I just tried building a UP kernel, and got the same problem... Off to try no serial debug... thanks, greg k-h ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
