Red Hat Bugzilla – Bug 169844
'hub 1-0:1.0: connect-debounce failed, port 3 disabled' ad infinitum.
Last modified: 2007-11-30 17:11:14 EST
My machine (AMD-768 dual Athlon) seems to be saying this repeatedly:
hub 1-0:1.0: connect-debounce failed, port 3 disabled
hub 1-0:1.0: connect-debounce failed, port 4 disabled
With 2.6.12-1.1456_FC4smp it seems to be relatively harmless, but
2.6.13-1.1526_FC4smp doesn't finish booting. The hid2hci tool gets stuck (as
does anything else using libusb, including lsusb):
hid2hci D 00000003 2400 2630 2623 (NOTLB)
c1a23ed4 00000086 001136d5 00000003 f7ee6334 00000000 c017a1a0 870e7341
00000021 00000000 c1a23000 c0171f66 0000035e c1ab6148 c1ab6020 c036bc00
c1807160 870f5507 00000021 c1a23000 00000000 0000001c c1a23000 bfd2388a
Ports 3 and 4 are the internal ports. The header on the motherboard isn't
connected to anything. If I disconnect ports 1 and 2 which are the external
ports, I see similar complaints about debouncing those, too.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.
It still persists, but it's probably broken hardware. I no longer use USB on the
offending box, and just blacklist the ohci_hcd module.