Bug 6298
| Summary: | USB keyboard makes hid-core.c return "input irq status -32 received" | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Jeffrey Vandenbroucke (jeffrey) |
| Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | ace, bunk |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.15.5 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5089 | ||
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? This is on 2.6.16-ck6 by-the-way. 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. 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. Gabriel, can you answer Jeffreys question? 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. Sorry, closed too early. :-( This happens when a bug contains two different problems... Jeffrey, what is the status of your patch? 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. |
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 },