On Mon, 2 May 2005, David Brownell wrote: > On Monday 02 May 2005 8:27 am, Alan Stern wrote: > > On Sun, 1 May 2005, David Brownell wrote: > > > > > On Sunday 01 May 2005 1:43 pm, Glenn Maynard wrote: > > > > We're hitting the "connect-debounce failed" message on a remote system, > > > > in 2.6.12-rc3 (no changes). > > > > > > Which among other things is an "infinite loop during enumeration" > > > problem. > > > > No it's not. When debouncing fails the hub driver turns off the > > POST_STAT_C_CONNECTION feature and leaves the port disabled. There > > shouldn't be any looping. > > Well, there _are_ such infinite-loop cases, and that transcript seemed > to be spending quite a lot of time on debounce attempts. Maybe I > just extrapolated too far ... ;)
Admittedly, there _could_ be an infinite-loop type of behavior. If the connection kept getting made and broken, over and over, it would seem to khubd that someone was plugging and unplugging the device over and over. After debouncing failed, the next disconnect-connect sequence would appear to be a new device and would cause a new round of debouncing. I suppose this sort of thing must be common to all hotpluggable buses. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
