Red Hat Bugzilla – Bug 209154
High speed USB HID devices not working in RHEL3
Last modified: 2007-11-16 20:14:46 EST
Description of problem:
High speed (USB 2.0) HID devices aren't working. Specifically this was seen
with a new USB 2.0 Avocent KVM dongle.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect Avocent USB 2.0 KVM dongle.
2. Boot system (booting to install CD shows problem, too).
3. Note that keyboard & mouse don't work.
Keyboard & mouse don't work .
Keyboard and mouse should work.
The problem is that the usbhid driver (in hid-core.c) is _not_ modifying the
interrupt URB interval for high speed devices before calling
FILL_INT_URB, which causes the interval to be too low, and the ehci driver
won't schedule the URB. The attached patch fixes the issue.
RHEL4 has a similar problem, except that RHEL4 does the calculation to modify
the URB interval _twice_, while RHEL3 doesn't do it at all... :)
Stuart, please make sure to open an I-T ticket or ask Matt to get this into
our PM machine somehow. First, I completely forgot that you filed this, so just
found it in today's rescan... Sorry. Second, I'll need a ticket anyway to
integrate anything into RHEL 3. It's going to see a really-really-really
last release very soon (actually it has already, but we're thinking about
Also, you didn't attach the patch, although you mentioned "attached patch".
Created attachment 148584 [details]
patch to fix high speed HID device interval
Here's the patch that I should have attached earlier, sorry. I tried to work
an extra semaphore into it somehow... :)
Created IT#114448 to correspond to this issue.
The patch is good. I have verified it locally. I need a word from Linda
to post it.
A fix for this problem has just been committed to the RHEL3 U9
patch pool this evening (in kernel version 2.4.21-47.6.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.