Bug 138205 - USB ports do not work properly on Viper
USB ports do not work properly on Viper
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Zaitcev
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-05 12:37 EST by Larry Troan
Modified: 2016-04-18 05:45 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-27 19:10:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Larry Troan 2004-11-05 12:37:10 EST
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-22 21:18:23 EST
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-27 19:10:59 EST
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.

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