Red Hat Bugzilla – Bug 206423
extensive amount of messages in message.log kernel: drivers/usb/input/hid-core.c: control queue full
Last modified: 2008-01-19 23:36:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:126.96.36.199) Gecko/20060728 Firefox/188.8.131.52
Description of problem:
I noticed, since my last kernel update, that in the /var/log/messagges file only the following entries appear
Sep 14 12:52:38 gateway kernel: drivers/usb/input/hid-core.c: control queue full
Sep 14 12:53:09 gateway last message repeated 3 times
Sep 14 12:54:19 gateway last message repeated 7 times
Sep 14 12:55:29 gateway last message repeated 7 times
This is just the last bit.
Searching I stumble uppon the following article
[PATCH] USB: hiddev HIDIOCGREPORT not blocking in 2.6
I've noticed in 2.6 kernels that HIDIOCGREPORT does not wait for io
completion before returning to the caller. This creates a few unpleasant
issues for userspace:
First, code sequences such as...
ioctl(fd, HIDIOCGREPORT, &rinfo);
ioctl(fd, HIDIOCGUSAGE, &uinfo);
ioctl(fd, HIDIOCGSTRING, &sdesc);
...that used to work in 2.4 now fail in 2.6 if the device takes more
than a few milliseconds to respond to HIDIOCGREPORT. (I'm seeing this
issue on APC UPSes, FWIW.)
Second, userspace code can easily flood the kernel with control messages
since the kernel provides no "backpressure". The result is a lot of
"hid-core.c: control queue full" errors and lost reports.
2.6 hid-core.c appears to submit the request and return immediately.
Although the 2.4 code differs significantly, I traced the call path to
usb-core.c, which seems to block with a timeout, so the code supports my
userspace observation. (Assuming I didn't misread it.)
>>>> So, Is this an bug that re-cycles ? <<<<
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start my Server
2. wait a few seconde
3. notice the log entry
Changed cable position from USB 2-2 to USB 1-2. Logging stopped.
Sep 18 15:17:37 gateway last message repeated 2 times
Sep 18 15:17:39 gateway kernel: usb 2-2: USB disconnect, address 2
Sep 18 15:18:20 gateway apcupsd: Communications with UPS lost.
Sep 18 15:18:20 gateway wall: wall: user root broadcasted 1 lines (46 chars)
Sep 18 15:18:49 gateway kernel: usb 1-2: new low speed USB device using uhci_hcd
and address 2
Sep 18 15:18:49 gateway kernel: usb 1-2: configuration #1 chosen from 1 choice
Sep 18 15:18:51 gateway kernel: hiddev96: USB HID v1.10 Device [American Power
Conversion Smart-UPS 1000 F
W:600.3.I USB FW:1.5] on usb-0000:00:10.0-2
Sep 18 15:18:55 gateway apcupsd: Communications with UPS restored.
Sep 18 15:18:56 gateway wall: wall: user root broadcasted 1 lines (42 chars)
Sep 18 15:18:58 gateway apcupsd: Battery reattached.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen