Bug 6298 - USB keyboard makes hid-core.c return "input irq status -32 received"
Summary: USB keyboard makes hid-core.c return "input irq status -32 received"
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks: USB
  Show dependency tree
 
Reported: 2006-03-28 13:53 UTC by Jeffrey Vandenbroucke
Modified: 2006-08-23 05:41 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.15.5
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jeffrey Vandenbroucke 2006-03-28 13:53:41 UTC 
Most recent kernel where this bug did not occur: N/A

Distribution: Debian 3.1

Hardware Environment: x86

Software Environment: GNU/Linux

Problem Description: When using a Silvercrest USB-keyboard (type 12015),
hid-core returns a "input irq status -32 received"-message.
This happens with 2.6.15.5 and possibly later kernel versions too on x86.
The problem is that the keyboard needs to make use of HID_QUIRK_NOGET.

Steps to reproduce: Plug in the keyboard, watch the kernel-log get flooded.

Workaround: Following lines need to be added to drivers/usb/input/hid-core.c
(lines 1452 to 1453)
#define USB_VENDOR_ID_SILVERCREST       0x062a
#define USB_DEVICE_ID_SILVERCREST_KB    0x0201
(line 1570)
{ USB_VENDOR_ID_SILVERCREST, USB_DEVICE_ID_SILVERCREST_KB, HID_QUIRK_NOGET },
Comment 1 Gabriel A. Devenyi 2006-04-26 11:42:25 UTC 
I guess I'm having a similar problem with a different keyboard,

drivers/usb/input/hid-core.c: input irq status -71 received

lsusb reports the keyboard as:
Bus 002 Device 002: ID 03f9:0100 KeyTronic Corp.

Would the same fix apply to this?
Comment 2 Gabriel A. Devenyi 2006-04-27 10:45:55 UTC 
This is on 2.6.16-ck6 by-the-way.
Comment 3 Greg Kroah-Hartman 2006-05-08 14:58:37 UTC 
Can you make up a patch, as per Documentation/SubmittingPatches and send
it to the linux-usb-devel mailing list and to me?  That way we can include
this fix in the kernel tree for others.
Comment 4 Jeffrey Vandenbroucke 2006-05-08 16:19:15 UTC 
A patch for the Silvercrest keyboard has already been submitted; 
I need more info on the other keyboard though e.g.: does it still work when you
get flooded with those messages? The -71 message can be generated by numerous
types of problems, even faulty hardware could generate this.
Comment 5 Adrian Bunk 2006-08-22 15:05:45 UTC 
Gabriel, can you answer Jeffreys question?
Comment 6 Gabriel A. Devenyi 2006-08-22 17:31:26 UTC 
Ugh, this was a while ago, the issue has resolved itself, i.e., I don't have 
these messages spamming dmesg anymore, but from what I recall, the Keyboard 
was still working with the errors.
Comment 7 Adrian Bunk 2006-08-22 17:43:58 UTC 
Sorry, closed too early.  :-(

This happens when a bug contains two different problems...

Jeffrey, what is the status of your patch?
Comment 8 Jeffrey Vandenbroucke 2006-08-23 05:41:18 UTC 
Well, the patch for the silvercrest keyboard is OK and is already in the kernel
tree. Seeing that Gabriel doesn't have the problem anymore, I think this matter
is resolved for this type of keyboard.
Note You need to log in before you can comment on or make changes to this bug.