From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: 2.6.8-rc2, usb HID is broken
Date: Wed, 21 Jul 2004 13:39:07 -0400 [thread overview]
Message-ID: <40FEAA3B.5010306@blue-labs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
uhci_hcd 0000:00:10.0: host controller process error, something bad
happened!
uhci_hcd 0000:00:10.0: host controller halted, very bad!
uhci_hcd 0000:00:10.0: host controller process error, something bad
happened!
uhci_hcd 0000:00:10.0: host controller halted, very bad!
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
At this point the usb mouse is dead, there isn't any other dmesg
information and the control queue full line repeats forever, apparently
when packets from the mouse are received.
Linux Scott 2.6.8-rc2 #1 Tue Jul 20 23:02:45 EDT 2004 x86_64 5 GNU/Linux
Gnu C 3.4.1
Gnu make 3.80
binutils 2.15.91.0.1
util-linux 2.12
mount 2.12
module-init-tools 3.0
e2fsprogs 1.35
Linux C Library 2.3.4
Dynamic linker (ldd) 2.3.4
Procps 3.2.2
Net-tools 1.60
Kbd 1.12
Sh-utils 5.2.1
Modules Loaded nvidia ipt_REJECT iptable_filter iptable_mangle
ipt_MASQUERADE iptable_nat ip_conntrack ip_tables
[-- 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-07-21 17:38 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=40FEAA3B.5010306@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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