On Fri, 2 Jun 2006, Rainer Becker wrote:

> I have difficulties with an USB repeater cable. It uses an USB hub as 
> repeater.
> Here are the error messages:
> 
> Jun  2 17:12:26 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 1.  Maybe the
> USB cable is bad?
> Jun  2 17:12:27 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 1.  Maybe the
> USB cable is bad?
> Jun  2 17:12:28 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 1.  Maybe the
> USB cable is bad?
> Jun  2 17:12:29 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 1.  Maybe the
> USB cable is bad?
> Jun  2 17:12:31 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 2.  Maybe the
> USB cable is bad?
> Jun  2 17:12:32 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 2.  Maybe the
> USB cable is bad?
> Jun  2 17:12:33 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 2.  Maybe the
> USB cable is bad?
> Jun  2 17:12:33 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 2.  Maybe the
> USB cable is bad?
> Jun  2 17:12:35 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 3.  Maybe the
> USB cable is bad?
> Jun  2 17:12:36 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 3.  Maybe the
> USB cable is bad?
> Jun  2 17:12:37 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 3.  Maybe the
> USB cable is bad?
> Jun  2 17:12:38 kwasir kernel: hub 5-2.4:1.0: Cannot enable port 3.  Maybe the
> USB cable is bad?
> Jun  2 17:12:39 kwasir kernel: hub 5-2:1.0: Cannot enable port 1.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:40 kwasir kernel: hub 5-2:1.0: Cannot enable port 1.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:41 kwasir kernel: hub 5-2:1.0: Cannot enable port 1.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:42 kwasir kernel: hub 5-2:1.0: Cannot enable port 1.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:43 kwasir kernel: hub 5-2:1.0: Cannot enable port 2.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:44 kwasir kernel: hub 5-2:1.0: Cannot enable port 2.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:45 kwasir kernel: hub 5-2:1.0: Cannot enable port 2.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:46 kwasir kernel: hub 5-2:1.0: Cannot enable port 2.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:47 kwasir kernel: hub 5-2:1.0: Cannot enable port 3.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:48 kwasir kernel: hub 5-2:1.0: Cannot enable port 3.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:49 kwasir kernel: hub 5-2:1.0: Cannot enable port 3.  Maybe the 
> USB
> cable is bad?
> Jun  2 17:12:50 kwasir kernel: hub 5-2:1.0: Cannot enable port 3.  Maybe the 
> USB
> cable is bad?
> ....
> 
> Every second an error and lsusb needs a long time.
> 
> This is the output of "lsusb"
> 
> [EMAIL PROTECTED](97): lsusb
> Bus 005 Device 065: ID 046a:0027 Cherry GmbH
> Bus 005 Device 066: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
> Bus 005 Device 040: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0
> "TetraHub"
> Bus 005 Device 015: ID 05e3:0606 Genesys Logic, Inc.
> Bus 005 Device 002: ID 05e3:0606 Genesys Logic, Inc.
> Bus 005 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
> 
> The Genesys Logic devices are the repeater hubs.
> 
> The following patch solves the problem:
> 
> --- drivers/usb/core/hub.c.orig 2006-05-26 19:40:46.000000000 +0200
> +++ drivers/usb/core/hub.c      2006-05-26 20:41:06.000000000 +0200
> @@ -1467,7 +1467,10 @@
> 
>                 /* bomb out completely if something weird happened */
>                 if ((portchange & USB_PORT_STAT_C_CONNECTION))
> +                       return -ENOTCONN;
> +/*
>                         return -EINVAL;
> +*/
> 
>                 /* if we`ve finished resetting, then break out of the loop */
>                 if (!(portstatus & USB_PORT_STAT_RESET) &&

I'm getting a little confused.  Is "the problem" that you have so many 
messages in the log and it takes a long time, or is "the problem" that the 
port cannot be enabled?  This patch won't allow the port to be enabled.

> But I don't know, whether this patch creates other difficulties. Has anybody 
> an
> answer?

It seems like a reasonable thing to do.  In fact you might as well 
combine this test with the preceding test, since they will both return 
-ENOTCONN.

Alan Stern



_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to