Cannot enable port 3. Maybe the USB cable is bad? - DM-140GINK Demo / HMC-2K53A

Bug #122102 reported by Dave Walker
4
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

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?
  ...
  [ 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. This usb module does work under Windows but complains of an extra "Unknown Device".

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

Dave Walker (davewalker)
description: updated
Changed in linux:
status: Unknown → Confirmed
Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Changed in linux:
status: Confirmed → Invalid
Revision history for this message
Dave Walker (davewalker) wrote :

Fixed in 2.6.23+

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Based on the last comment I'm marking this Fix Release for Hardy's 2.6.24 kernel. Against 2.6.20 this will be closed as the Feisty Fawn 7.04 release has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . Additionally against 2.6.22 this will be closed as it does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

Changed in linux:
status: New → Fix Released
Changed in linux-source-2.6.20:
status: New → Won't Fix
Changed in linux-source-2.6.22:
status: Triaged → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Changed in linux:
importance: Unknown → Medium
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.