From: Benjamin LaHaise <bcrl@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: usb keyboard stuck?
Date: Mon, 24 Feb 2003 11:53:34 -0500 [thread overview]
Message-ID: <20030224115334.A17410@redhat.com> (raw)
Hello folks,
I've just had an odd occurance with a USB keyboard setup where the
shift / alt / control keys became stuck. The only way to get sane
control of the system back was to unplug the usb keyboard and plug
it back in. Note that upon plugging it back in, the system logged
a few unknown scancode messages, which seems a bit odd. Any ideas
if this is the fault of the keyboard or the driver? Info on any
experiences might be helpful, especially if someone else is using a
Logitech iTouch keyboard. Cheers,
-bben
--
Junk email? <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
application bug: xterm(9022) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
usb.c: USB disconnect on device 02:06.1-2.1.2 address 4
usb.c: USB disconnect on device 02:06.1-2.1.2.1 address 6
usb.c: USB disconnect on device 02:06.1-2.1.2.3 address 7
hub.c: new USB device 02:06.1-2.1.2, assigned address 8
hub.c: USB hub found
hub.c: 3 ports detected
hub.c: new USB device 02:06.1-2.1.2.1, assigned address 9
input0: USB HID v1.10 Keyboard [LOGITECH USB Keyboard] on usb3:9.0
input1: USB HID v1.10 Pointer [LOGITECH USB Keyboard] on usb3:9.1
hub.c: new USB device 02:06.1-2.1.2.3, assigned address 10
input2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb3:10.0
keyboard: unknown scancode e0 3a
keyboard: unknown scancode e0 1e
keyboard: unknown scancode e0 1e
keyboard: unknown scancode e0 0e
keyboard: unknown scancode e0 2e
keyboard: unknown scancode e0 2e
keyboard: unknown scancode e0 0e
keyboard: unknown scancode e0 0e
keyboard: unknown scancode e0 13
keyboard: unknown scancode e0 33
keyboard: unknown scancode e0 33
keyboard: unknown scancode e0 23
reply other threads:[~2003-02-24 16:43 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=20030224115334.A17410@redhat.com \
--to=bcrl@redhat.com \
--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