Bug 146183

Summary: [RHEL3U4] chicony usb keyboard fails, with side effects
Product: Red Hat Enterprise Linux 3 Reporter: Stuart Hayes <stuart_hayes>
Component: kernelAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: petrides, riel
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: 2007-10-19 19:08:44 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:
Attachments:
Description Flags
patch to add this keyboard to the blacklist with "noget" quirk
none
A cleaned version suitable for application none

Description Stuart Hayes 2005-01-25 20:23:53 UTC 
Description of problem:

We have a Dell Chicony USB keyboard (model KU-9985) which fails to 
work when plugged in.  There are ugly messages in /var/log/messages, 
and "lsusb" will hang.

It turns out that this keyboard says that it has both a keyboard and 
a mouse, though there really is no mouse at all (no PS/2 port, no 
mouse).  When Linux issues a "get_report" for the mouse reports, the 
keyboard stalls, and things go downhill.

This keyboard works fine if we add it to the blacklist with 
the "NOGET" quirk.

Version-Release number of selected component (if applicable):


How reproducible:
Very easy.

Steps to Reproduce:
1. Boot up system.
2. Plug in KU-9985 Chicony usb hub keyboard.
3. 
  
Actual results:
Keyboard doesn't work, there are ugly messages, and "lsusb" will hang.

Expected results:
Keyboard should work, lsusb should work normally.

Additional info:
I will attach the patch.
Comment 1 Stuart Hayes 2005-01-25 20:25:15 UTC 
Created attachment 110212 [details]
patch to add this keyboard to the blacklist with "noget" quirk
Comment 2 Pete Zaitcev 2005-03-21 23:55:50 UTC 
Created attachment 112198 [details]
A cleaned version suitable for application

Stuart forgot to diff for patch -p1 and also swapped arguments. Tsk tsk :-)
This ought to work a little better.
Comment 3 Stuart Hayes 2005-03-22 16:15:20 UTC 
How embarrassing!

Thank you.
Comment 4 Pete Zaitcev 2006-04-13 06:12:04 UTC 
I swear this was committed long time ago. I just verified -40.6.EL,
the fix is present. Stuart, could you check if U7 has the fix and
close the bug?
Comment 5 Stuart Hayes 2006-04-13 18:48:35 UTC 
It doesn't appear to be in U7 (2.4.21-40.EL).  I guess it didn't bother too 
many people, because I never heard anything else about it...
Comment 6 Ernie Petrides 2006-04-13 19:38:52 UTC 
Pete, the patch in comment #2 has never been committed to the RHEL3 kernel,
and there is no reference to USB_VENDOR_ID_CHICONY in any of my patch tracking
files (across all updates).
Comment 7 Pete Zaitcev 2006-04-13 21:35:35 UTC 
Oh yuk, it appears that I made Stuart to work for nothing, because
I confused unpacked trees locally. I very, very sorry.
Comment 8 Stuart Hayes 2006-04-14 14:30:11 UTC 
:)  It was really no problem.
Comment 9 RHEL Program Management 2007-10-19 19:08:44 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.