Bug 227598 - HID causes BUG assertion on startup
HID causes BUG assertion on startup
Status: CLOSED DUPLICATE of bug 228755
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Zaitcev
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-02-06 18:33 EST by Bastien Nocera
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-22 05:45:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bastien Nocera 2007-02-06 18:33:46 EST
kernel-2.6.19-1.2895.fc6 on x86-64

I get plenty of those:
BUG: warning: (value > m) at drivers/usb/input/hid-core.c:793/implement() (Not

Call Trace:
 [<ffffffff8026999a>] show_trace+0x34/0x47
 [<ffffffff802699bf>] dump_stack+0x12/0x17
 [<ffffffff803e9ef0>] hid_output_report+0x1b5/0x221
 [<ffffffff803e9fb8>] hid_submit_ctrl+0x5c/0x1f8
 [<ffffffff803ea349>] hid_submit_report+0x15f/0x18c
 [<ffffffff803ec9c8>] hiddev_ioctl+0x34f/0x8f8
 [<ffffffff8024032d>] do_ioctl+0x55/0x6b
 [<ffffffff8022ff2b>] vfs_ioctl+0x256/0x26f
 [<ffffffff8024a989>] sys_ioctl+0x59/0x78
 [<ffffffff8025c11e>] system_call+0x7e/0x83

On bootup. I have no idea what this is supposed to be, and happens after:
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts

and before:
Bluetooth: Core ver 2.11
NET: Registered protocol family 31

The only USB input device on the machine is:
Bus 005 Device 008: ID 046d:0b02 Logitech, Inc. 
Bus 005 Device 010: ID 046d:c70a Logitech, Inc. 
Bus 005 Device 009: ID 046d:c70e Logitech, Inc. 

a "Bluetooth" mini-receiver from Logitech (a USB no wires adapter for kbd/mouse
combo that can switch to being a Bluetooth dongle).
Comment 1 Pete Zaitcev 2007-02-15 15:15:49 EST
Bastien, this looks like a dup of bug 228755. Can you get me the full dmesg,
to see if hid2hci is involved? There should be a process name in it, I think.
Comment 2 Bastien Nocera 2007-02-22 05:45:00 EST
hid2hci is definitely involved. It's the same hardware as reported at


*** This bug has been marked as a duplicate of 228755 ***

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