Bug 138205

Summary: USB ports do not work properly on Viper
Product: Red Hat Enterprise Linux 3 Reporter: Larry Troan <ltroan>
Component: kernelAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: ichute, jbaron, jparadis, petrides, riel, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-28 00:10:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Larry Troan 2004-11-05 17:37:10 UTC 
Using a USB key, I find that the Viper U4 beta kernel does not always
recogize the key properly when inserted.  This is especially true of
the front ports.

I see an error message printed upon insertion which reads:
"usb.c: USB device not accepting new address=2 (error=-71)
usb.c: USB device not accepting new address=3 (error=-71)"
----------
Action by: jeff.burrell
Issue Registered
----------
Action by: jeff.burrell


Status set to: Waiting on Tech
Comment 9 Pete Zaitcev 2005-03-23 02:18:23 UTC 
Please test kernel 2.4.21-31.EL.usbserial.3 by selecting a suitable
architecture from the following URL:
 ftp://people.redhat.com/zaitcev/rhel3usb/

I do not have my hopes high, but it may work, by adding the 10ms TRSTRCY
delay as the 2.6.12-rc1 does.
Comment 10 Pete Zaitcev 2006-01-28 00:10:59 UTC 
Closing due to inactivity - apparently Larry forgot about this bug...
I am, however, moving forward with bug 165246 (DO NOT DUP!),
which _may_ fix this symtom.