public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard dead on bootup on -test6.
Date: Tue, 30 Sep 2003 20:21:56 -0500	[thread overview]
Message-ID: <200309302021.56614.rob@landley.net> (raw)
In-Reply-To: <20031001005214.GC1520@win.tue.nl>

On Tuesday 30 September 2003 19:52, Andries Brouwer wrote:
> On Tue, Sep 30, 2003 at 04:32:01PM -0500, Rob Landley wrote:
> > 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 suppose this is the kernel trying to set LEDs on the mouse,
> and the mouse complains.
>
> Andries

It's a laptop nipple mouse, a miniature joystick between the G and H keys.  
There are no LED's anywhere near it.  So I'm not surprised it complains.  But 
why does that kill my keyboard?  (You'll notice that the keyboard 
identification line goes missing when this error occurs...)

Rob

  reply	other threads:[~2003-10-01  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 21:32 Keyboard dead on bootup on -test6 Rob Landley
2003-10-01  0:52 ` Andries Brouwer
2003-10-01  1:21   ` Rob Landley [this message]
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=200309302021.56614.rob@landley.net \
    --to=rob@landley.net \
    --cc=aebr@win.tue.nl \
    --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