On Tue, 23 Jan 2007, Oliver Neukum wrote: > I got you into the loop precisely because the bug is related to autosuspend > and the log is unclear. > > The facts as far as I can tell are: > > With CONFIG_USB_SUSPEND > -the device binds to the driver > -disconnects itself as as soon as there's IO to the device > > Without CONFIG_USB_SUSPEND it does not. > > In fact it just looked so much like a dmesg of those devices that fail > with autosuspend that I requested a recompile without autosuspend. > It is a mystery to me why this would matter with a driver that does not > support autosuspend.
I don't see how it could make any difference, since the log did not show any suspends at all, auto or otherwise (except for the OHCI-internal suspend before the Treo was connected). > However, as it seems to, it is important that > you know of it. Is it possible that the reference count is not properly > propagated through the tree? No -- in fact, the 2.6.18 kernel used in that log doesn't include USB autosuspend support at all. Maybe Dirk should try using 2.6.20-rc5 and see if it makes any difference. Also try attaching the Treo to a different computer. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
