Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 101803

Summary: gentoo-sources 2.6.12-r7 and usb connect-debounce port problem with USB hub
Product: Gentoo Linux Reporter: Jacobo Cabaleiro <obmun>
Component: [OLD] Core systemAssignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status: RESOLVED UPSTREAM    
Severity: major    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Complete 2.6.12 kernel dmesg (from boot till some of the USB hub errors)
lspci -v output of my system
cat of /proc/bus/usb/devices proc fs entry
Complet 2.6.12 .config
Summarized 2.6.13-rc6 dmesg output

Description Jacobo Cabaleiro 2005-08-08 14:29:17 UTC
USB powered hub of a Sony 17'' CRT display. Hub is correctly recognized when
plug to the USB port of the computer. But any USB device plugged to any port of
the hub is not correctly recognized and the USB hub port is disabled due to
connection-debounce errors. In some older kernel if I had luck the device could
work in some of the USB hub ports.

Reproducible: Always
Steps to Reproduce:
1.Try to connect any USB device to one port of the USB hub connected to the
computer USB port
2.
3.

Actual Results:  
The USB device is not connected and kernel disables the USB hub port where it
was connected

Expected Results:  
USB device (in my case a HID mouse) should be properly recognized by the kernel

Kernel version:
Linux titan 2.6.12-gentoo-r7 #1 Mon Aug 8 21:16:27 CEST 2005 i586 AMD-K6(tm) 3D
processor AuthenticAMD GNU/Linux
Hardware:
AMD k6-2 400 MHz procesor, on an OLD Asus P5A (with probably not a shiny ACPI
BIOS implementation, and a problematic ALi chipset (south and northbrigde)).

2.6.11 also never worked. I don't remember what was the last kernel version
without problems, but I can tell you for sure this worked in 2.6 series till
some version.

Important dmesg lines:
---------------------------------
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 2 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: hub_port_status failed (err = -110)
hub 1-1:1.0: connect-debounce failed, port 4 disabled
hub 1-1:1.0: cannot disable port 4 (err = -110)
hub 1-1:1.0: hub_port_status failed (err = -110)
usb 1-1: USB disconnect, address 3
usb 1-2: new full speed USB device using ohci_hcd and address 4
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
---------------------------------
Actions for that dmesg text:
1.- Connect the USB hub
2.- Try to connect a Logitech USB mouse first to one of the USB ports. No luck.
3.- Try to connect the same Log mouse to other USB port. No luck.
4.- Reconnect the USB hub.

More details follow (complete dmesg, proc/bus/usb/devices, lspci -v, .config).

NOTE: I was thinkig about posting this to kernel mailing list (I'm subscribed to
it) but preferred to use you, Gentoo developers, as a previous filter :) and
this bugzilla entry to see if someone else was experiencing this problem. If you
want I can send this bug to kernel bugzilla or kernel mailing list.
Comment 1 Jacobo Cabaleiro 2005-08-08 14:30:43 UTC
Created attachment 65472 [details]
Complete 2.6.12 kernel dmesg (from boot till some of the USB hub errors)
Comment 2 Jacobo Cabaleiro 2005-08-08 14:31:15 UTC
Created attachment 65473 [details]
lspci -v output of my system
Comment 3 Jacobo Cabaleiro 2005-08-08 14:31:48 UTC
Created attachment 65474 [details]
cat of /proc/bus/usb/devices proc fs entry
Comment 4 Jacobo Cabaleiro 2005-08-08 14:33:12 UTC
Created attachment 65475 [details]
Complet 2.6.12 .config

I don't think anything is wrong with my kernel .config, but in case... here it
is
Comment 5 Daniel Drake (RETIRED) gentoo-dev 2005-08-09 02:44:20 UTC
Please try and reproduce on vanilla-sources-2.6.13_rc6 and enable USB debug
messages. Then please attach a new dmesg output after trying to use the hub.,
Comment 6 Jacobo Cabaleiro 2005-08-09 08:08:32 UTC
Created attachment 65534 [details]
Summarized 2.6.13-rc6 dmesg output

emerged vanilla 2.6.13-rc6, made oldconfig and retested

This dmesg output correspondes with the following actions:
1.) On boot, an USB mouse (let's call it mouse_A) is connected to the computer
mainboard.
2.) After boot, the display hub is connected to the other computer USB port
3.) Another USB mouse (mouse_B) is connected and disconnected to every port of
the USB hub (4 consecutive connection - disconnection). Mouse is recognized
properly. I thought the issue was solved in kernel 2.6.13 but then I tried
mouse_A again ...
4.) Disconnected mouse_A from computer and tried it in the hub. The debounce
error appeared! So it's USB device dependent. Tried two different ports, same
results.

I have to test it with another hardware (maybe later with a Canon 20D, to see
what happens).

If anyone interested, I have the full dmesg log (more than 100 KBytes).
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2005-08-14 03:43:01 UTC
I think we need the upstream developers to look at this. Please file a bug
report for this at http://bugzilla.kernel.org against 2.6.13-rc6 and post the
new bug URL here.