All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Re:Re: Linux 2.6.0-test4
Date: Sat, 30 Aug 2003 16:59:00 +0200	[thread overview]
Message-ID: <20030830145900.GB6862@charite.de> (raw)
In-Reply-To: <20030830095858.0895.CHRIS@heathens.co.nz>

* Chris Heath <chris@heathens.co.nz>:
> > I still have issues with the keyboard -- sometimes when typing in the
> > frambuffer console I get an "unknown scancode" and after that the CTRL
> > key is stuck forever, which forces me to reboot.
> 
> Please post the full error message.  Does the error message always
> contain the same scancode?

I'll do that.

Aug 27 18:53:41 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
Aug 27 19:15:14 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0xb9, on isa0060/serio0) pressed.
Aug 27 19:42:50 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
Aug 28 10:14:14 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.

Basically, CTRL was stuck. Even when I switched to X11.

> My guess is you can get out of that without a reboot.  Next time it
> happens, try this:
>    1. Press and release each Ctrl key. (This makes sure the key_down
>       array is correct.)
>    2. Switch to another console and back again. (This executes the
>       compute_shiftstate function, which recalculates the shift
>       state from the key_down array.)

Ah, good idea.

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   Ralf.Hildebrandt@charite.de
Charite Campus Mitte                            Tel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
AIM: ralfpostfix

  reply	other threads:[~2003-08-30 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-30 14:13 Re:Re: Linux 2.6.0-test4 Chris Heath
2003-08-30 14:59 ` Ralf Hildebrandt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31 16:22 Chris Heath
2003-09-01 16:01 ` Ralf Hildebrandt
2003-09-02  8:07 ` Ralf Hildebrandt

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=20030830145900.GB6862@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.