Am Sonntag, 4. März 2007 23:16 schrieb Alan Stern:
> On Sun, 4 Mar 2007, Oliver Neukum wrote:
>
> > > I noticed that the message occurs if the device is active BEFORE
> > > uhci-hcd gets loaded.
> > > e.g.
> > >
> > > boot with bluetooth on: debounce failed
> > > switch off/on bluetooth: device recognized and working
> > > rmmod uhci-hcd then modprobe uhci-hcd: debounce failed again
> > >
> > > and of course
> > > boot with bt off then switching on: device recognized and working
> > > rmmod uhci-hcd then modprobe uhci-hcd: debounce failed
> >
> > This makes it likely that some device initialisation code is not severe
> > enough. It is important to find out why one kernel works and the other
> > does not.
>
> On the contrary, this indicates the problem has nothing to do with the
> kernel version at all. Probably it's just an accident of timing that one
> system ends up loading uhci-hcd before the device is active and other
> systems don't.
Cristian,
please try unloading and reloading the ehci driver.
Regards
Oliver
-------------------------------------------------------------------------
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
