Re: Fw: [Bugme-new] [Bug 8104] New: kernel floods console with "connect-debounce failed"

On Mon, 5 Mar 2007, Cristian Mammoli wrote:

> On lun, 2007-03-05 at 11:28 +0100, Oliver Neukum wrote:
> 
> > please try unloading and reloading the ehci driver.
> > 
> > 	Regards
> > 		Oliver

> When the device is NOT working:
> on rmmod:
...
> [ 5956.663402] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.670761] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.674488] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.677960] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.681442] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.692156] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.696040] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5956.699525] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
> [ 5956.703081] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
...
> [ 5957.168584] hub 4-0:1.0: debounce: port 2: total 1500ms stable 0ms
> status 0x101
> [ 5957.168590] hub 4-0:1.0: connect-debounce failed, port 2 disabled
> [ 5957.168608] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
> [ 5957.193671] hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0004
> [ 5957.193693] uhci_hcd 0000:00:1d.2: port 2 portsc 0082,00
> [ 5957.193707] hub 4-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
> [ 5957.202877] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
> [ 5957.208461] uhci_hcd 0000:00:1d.2: port 2 portsc 0093,00
>  [many more lines]
> 
> on modprobe:
...
> [ 5999.369962] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.376666] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
> POWER sig=se0 CSC
> [ 5999.380818] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.399452] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.403801] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.408386] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT
> [ 5999.414546] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001002
> POWER sig=se0 CSC
> [ 5999.420914] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803
> POWER sig=j CSC CONNECT

This is different from what I thought before.  It's clear there's 
something wrong with the Bluetooth hardware, or the hardware the connects 
the Bluetooth device to the USB bus.  It constantly connects and then 
disconnects, over and over again.

There's no way for the EHCI controller to ignore this kind of activity.  I 
don't know what can be done about it.

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
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel