From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: USB HID failure, 2.6.7-rc2
Date: Thu, 10 Jun 2004 20:32:55 -0400 [thread overview]
Message-ID: <40C8FDB7.5050102@blue-labs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
After some unknown event happens, I lose my USB mouse and dmesg starts
filling up with the following message:
drivers/usb/input/hid-core.c: control queue full
I'm moving to -rc3 this evening - hoping this bug is gone then. There
are no other messages prior to this other than the broken ALSA stuff,
but that happens since boot anyways. The machine had been up for almost
24 hours (random instant lockups/reboots, sometimes an hour, sometimes
two days) before this happened. I was away for the day so the machine
had been idle for almost 14 hours. Unplugging and replugging this mouse
has zero effect, the action isn't even noticed by the computer.
David
[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]
begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard
reply other threads:[~2004-06-11 0:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40C8FDB7.5050102@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox