public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Keyboard dead on bootup on -test6.
Date: Tue, 30 Sep 2003 16:32:01 -0500	[thread overview]
Message-ID: <200309301632.01498.rob@landley.net> (raw)

Since I switched to test6, my stuck-key problems went away.  (Thank you.  Good 
work.  Judging by the repeat speed, it's back to using hardware repeat.)

However, a problem I'd seen before resurfaced.  Sometimes when I boot up the 
keyboard is completely dead.  It just did this to me (had to use the power 
button, because of course ctrl-alt-del did nothing), and I compared the boot 
logs:

This is what it looks like when it works normally:

Sep 30 16:18:28 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Sep 30 16:18:28 localhost kernel: input: AT Translated Set 2 keyboard on 
isa0060/serio0
Sep 30 16:18:28 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1

This was the failure:

Sep 30 16:17:31 localhost kernel: atkbd.c: Unknown key pressed (raw set 0, 
code 0xfc, data 0xfc, on isa0060/serio1).
Sep 30 16:17:31 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Sep 30 16:17:31 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1

Under -test5, that failure would have left me with a stuck key endlessly 
repeating (and an otherwise dead keyboard).  Now at least the stuck key part 
has gone away, but the keyboard is still dead until I power cycle the 
machine.

I continue to be using a thinkpad iSeries, I believe it's a 1200C...

Rob



             reply	other threads:[~2003-09-30 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 21:32 Rob Landley [this message]
2003-10-01  0:52 ` Keyboard dead on bootup on -test6 Andries Brouwer
2003-10-01  1:21   ` Rob Landley
2003-10-01 18:36     ` Andries Brouwer
2003-10-01 21:17       ` Rob Landley

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=200309301632.01498.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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