On dom, 2007-03-04 at 12:27 +0100, Oliver Neukum wrote: > > Please check your boot log for the compiler used in the working kernel > binary compared to the compiler you are using.
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 I also noticed that even if I disable bluetooth in the system bios I get debounce failed anyway depending on the position of the switch at boot time. dmesg with usb debug available if needed. ------------------------------------------------------------------------- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
