From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.28-rc4-mmotm1110 shift-lock oddness
Date: Mon, 17 Nov 2008 16:56:55 -0500 [thread overview]
Message-ID: <5397.1226959015@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Twice today, I've managed to get my laptop into an odd state where the keyboard
got quite confused:
1) For the characters [a-z] the shift bit was *inverted* - if the shift-lock
LED was off, you'd get UPPER-case, and if it was on, you'd get lower-case.
2) To add to the fun, the 0-9 keys were stuck shifted - I'd get the special
characters no matter what setting the shift or shift-lock key had. I suspect
that the special-char keys like [{ and ;: were also stuck in shifted state,
but can't totally confirm it.
The previous two issues combined meant that I wasn't able to su or login
as root to do much of anything about it (guess who has special chars in their
root password? ;)
3) ctl-alt-Fn to switch virtual consoles was spotty/erratic - one time
I was unable to use it at all, another time I was able to use c-a-F1 to get
to a green-screen console, but then F2 to get another one or F7 to get
back to the X server screen wouldn't work.
4) Fortunately for my sanity, alt-sysrq was still working as advertised,
so I was able to reboot and thus clear the problem.
I was thinking this might be a simple "missed a key press/released" event
for a shift key, except that doesn't explain the numerics getting stuck shifted.
Any suggestions/hints for instrumentation/etc, in case I can replicate it
again?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2008-11-17 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 21:56 Valdis.Kletnieks [this message]
2008-11-18 0:23 ` Andrew Morton
2008-11-18 0:26 ` Jiri Kosina
2008-11-18 2:36 ` Valdis.Kletnieks
2008-11-18 9:37 ` Jiri Kosina
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=5397.1226959015@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.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
all inboxes | Powered by JetHome®