hub 2-0:1.0: connect-debounce failed, port 1 disabled

Bug #1177289 reported by Cristian Aravena Romero
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
High
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

[ 25.544059] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 28.104055] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 28.556081] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 31.132093] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 33.696081] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 36.256074] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 36.868097] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 39.440080] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 42.000070] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 44.560057] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 44.948067] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 47.524054] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 50.084061] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 52.644067] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 53.032095] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 55.616042] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 58.176054] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 60.736051] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 61.124089] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 63.836046] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 66.396052] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 68.956054] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 69.344064] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 71.928055] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 74.488093] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 77.048052] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 77.436070] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 80.008060] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 82.572138] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 85.140134] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 85.528131] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 88.124128] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 90.684078] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 93.244135] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 93.856110] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 96.428071] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 98.988116] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 101.548107] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 101.936161] hub 2-0:1.0: unable to enumerate USB device on port 4
[ 104.520098] hub 2-0:1.0: connect-debounce failed, port 1 disabled
[ 107.080134] hub 2-0:1.0: connect-debounce failed, port 2 disabled
[ 109.640068] hub 2-0:1.0: connect-debounce failed, port 3 disabled
[ 110.092153

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.30
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: caravena 2149 F.... pulseaudio
Date: Tue May 7 04:30:44 2013
HibernationDevice: RESUME=UUID=bbb4e1f8-ea0d-49c5-816e-06c632db022b
InstallationDate: Installed on 2013-04-27 (10 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Sony Corporation VGN-NS130FE
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fd1ecf0d-45eb-4378-8244-1da222181838 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0200Y3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0200Y3:bd08/27/2009:svnSonyCorporation:pnVGN-NS130FE:pvrC6U0B23E:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NS130FE
dmi.product.version: C6U0B23E
dmi.sys.vendor: Sony Corporation

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
minzaurralde@gmail.com (minzaurralde) wrote :

Hi: I have de same problem. I upgrade the kernel to 3.9 and the problem not dissapear. I´m run 12.04 on i486. Thanks.

Revision history for this message
svarog (varrkan82) wrote :

lubuntu 13.04 i386 with kernel version 3.8.0-29 - have a same bug!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.