Bug 8705 - "Cannot enable port 3. Maybe the USB cable is bad?" - When 'is bad' doesn't disable, causing problems
"Cannot enable port 3. Maybe the USB cable is bad?" - When 'is bad' doesn't d...
Status: REJECTED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: USB
All Linux
: P1 normal
Assigned To: Greg Kroah-Hartman
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2007-07-02 10:30 UTC by Dave Walker
Modified: 2007-10-06 14:17 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.22
Tree: Mainline
Regression: ---


Attachments

Description Dave Walker 2007-07-02 10:30:11 UTC
Most recent kernel where this bug did not occur: N/A
Distribution: Known on Ubuntu feisty/gutsy and Fedora
Hardware Environment: DM-140GINK Demo / HMC-2K53A
Software Environment: N/A
Problem Description: "Cannot enable port 3. Maybe the USB cable is bad?"

This bug occurs when a PCB module that provides the following internal
features:
* Generic 4 port Hub (Genesys GL850A) - problems with port 3!
    => Futaba "DM-140GINK Demo", (usbhid driver) - VFD (LCD) & Panel
Buttons
    => Ralink RT2571WF

This is all encased within the PCB, so there is no extra access to the
hub.

When the devices is connected:
  [ 699.188000] usb 4-8: new high speed USB device using ehci_hcd and
address 39
  [ 699.320000] usb 4-8: configuration #1 chosen from 1 choice
  [ 699.320000] hub 4-8:1.0: USB hub found
  [ 699.320000] hub 4-8:1.0: 4 ports detected
  [ 699.624000] usb 4-8.1: new high speed USB device using ehci_hcd and
address 40
  [ 699.852000] usb 4-8.1: configuration #1 chosen from 1 choice
  [ 700.056000] usb 4-8.2: new full speed USB device using ehci_hcd and
address 41
  [ 700.152000] usb 4-8.2: configuration #1 chosen from 1 choice
  [ 700.152000] hiddev96: USB HID v1.10 Device [DM-140GINK Demo
DM-140GINK Demo] on usb-0000:00:13.5-8.2
  [ 700.156000] input: DM-140GINK Demo DM-140GINK Demo
as /class/input/input7
  [ 700.156000] input: USB HID v1.10 Device [DM-140GINK Demo DM-140GINK
Demo] on usb-0000:00:13.5-8.2
  [ 701.116000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
is bad?
  [ 701.948000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
is bad?
  [ 702.780000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
is bad?
  ...(continues)
  [ 549.984000] usb 6-8.2: reset full speed USB device using ehci_hcd
and address

I believe this bug may be caused due to USB standard not being followed
on the hardware. This usb module does work under Windows but complains
of an extra (4th) "Unknown Device" (that doesn't really exist).

When this device is connected, 'lsusb' no longer functions.  This bug is
in kernel's as recent as 2.6.22.  Bug is also visible in mainline vanilla kernel.  There is no known workaround at this stage, stops host booting and limits performance of machine when connected.

Maybe the kernel should detect something _is bad_, then disable it? Rather than keep trying.

Steps to reproduce:
Connect the device to USB headers.
Comment 1 Andrew Morton 2007-07-02 11:59:18 UTC
Subject: Re: [Bugme-new]  New:
 "Cannot enable port 3. Maybe the USB cable is bad?"

On Mon,  2 Jul 2007 10:25:58 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8705
> 
>            Summary: "Cannot enable port 3. Maybe the USB cable is bad?"
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.22
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: davewalker@ubuntu.com
> 
> 
> Most recent kernel where this bug did not occur: N/A
> Distribution: Known on Ubuntu feisty/gutsy and Fedora
> Hardware Environment: DM-140GINK Demo / HMC-2K53A
> Software Environment: N/A
> Problem Description: "Cannot enable port 3. Maybe the USB cable is bad?"
> 
> This bug occurs when a PCB module that provides the following internal
> features:
> * Generic 4 port Hub (Genesys GL850A) - problems with port 3!
>     => Futaba "DM-140GINK Demo", (usbhid driver) - VFD (LCD) & Panel
> Buttons
>     => Ralink RT2571WF
> 
> This is all encased within the PCB, so there is no extra access to the
> hub.
> 
> When the devices is connected:
>   [ 699.188000] usb 4-8: new high speed USB device using ehci_hcd and
> address 39
>   [ 699.320000] usb 4-8: configuration #1 chosen from 1 choice
>   [ 699.320000] hub 4-8:1.0: USB hub found
>   [ 699.320000] hub 4-8:1.0: 4 ports detected
>   [ 699.624000] usb 4-8.1: new high speed USB device using ehci_hcd and
> address 40
>   [ 699.852000] usb 4-8.1: configuration #1 chosen from 1 choice
>   [ 700.056000] usb 4-8.2: new full speed USB device using ehci_hcd and
> address 41
>   [ 700.152000] usb 4-8.2: configuration #1 chosen from 1 choice
>   [ 700.152000] hiddev96: USB HID v1.10 Device [DM-140GINK Demo
> DM-140GINK Demo] on usb-0000:00:13.5-8.2
>   [ 700.156000] input: DM-140GINK Demo DM-140GINK Demo
> as /class/input/input7
>   [ 700.156000] input: USB HID v1.10 Device [DM-140GINK Demo DM-140GINK
> Demo] on usb-0000:00:13.5-8.2
>   [ 701.116000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
> is bad?
>   [ 701.948000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
> is bad?
>   [ 702.780000] hub 4-8:1.0: Cannot enable port 3. Maybe the USB cable
> is bad?
>   ...(continues)
>   [ 549.984000] usb 6-8.2: reset full speed USB device using ehci_hcd
> and address
> 
> I believe this bug may be caused due to USB standard not being followed
> on the hardware. This usb module does work under Windows but complains
> of an extra (4th) "Unknown Device" (that doesn't really exist).
> 
> When this device is connected, 'lsusb' no longer functions.  This bug is
> in kernel's as recent as 2.6.22.  Bug is also visible in mainline vanilla
> kernel.  There is no known workaround at this stage, stops host booting and
> limits performance of machine when connected.
> 
> Maybe the kernel should detect something _is bad_, then disable it? Rather than
> keep trying.
> 
> Steps to reproduce:
> Connect the device to USB headers.
> 
> 
> -- 
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.

Comment 2 Alan Stern 2007-07-03 14:02:43 UTC
Please build a kernel with CONFIG_USB_DEBUG turned on and attach the debugging log showing what happens when the device is connected.
Comment 3 Adrian Bunk 2007-10-06 14:17:46 UTC
Please reopen the bug if you can provide the requested information.

Note You need to log in before you can comment on or make changes to this bug.