All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: vojtech@suse.cz
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>, linux-kernel@vger.kernel.org
Subject: Re: Another keyboard woes with 2.6.0...
Date: Tue, 7 Oct 2003 00:08:47 +0200	[thread overview]
Message-ID: <20031006220847.GA5139@vana.vc.cvut.cz> (raw)
In-Reply-To: <20030916232318.A1699@pclin040.win.tue.nl>

On Tue, Sep 16, 2003 at 11:23:18PM +0200, Andries Brouwer wrote:
> 
> I am especially interested in cases where people can reproduce
> an unwanted key repeat. The question is: is this a bug in our timer code
> or use of timers, or did the keyboard never send the key release code?
> 
> (#define DEBUG in i8042.c)

Hi,
  after three weeks running with DEBUG enabled I decided (well, I lost this patch
somewhere while patching my kernel sometime last week) to disable it - and kaboom, I
got (twice, but yesterday I rebooted box hard, as I thought that it is dead)
strange lockup, where box stoped reacting on keyboard. After playing with
mouse's cut&paste I was able to get at dmesg, and after 'setleds -V +num' keyboard
returned back to live.

  And it looks to me like a genuine race. When I was switching from console
with numlock enabled to console with numlock disabled, message below was printed
by kernel, and keyboard stopped working (probably waiting for second byte from
setleds command). I'll now reenable DEBUG in i8042, and problem will hopefully
disappear...

atkbd.c: Unknown key released (translated set 2, code 0x165, data 0xfa, on isa0060/serio0).

								Best regards,
									Petr Vandrovec
									vandrove@vc.cvut.cz

  parent reply	other threads:[~2003-10-06 22:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 16:50 Another keyboard woes with 2.6.0 Petr Vandrovec
2003-09-12 17:45 ` Zwane Mwaikambo
2003-09-16 21:23   ` Andries Brouwer
2003-09-16 22:45     ` Jamie Lokier
2003-09-16 22:49     ` Zwane Mwaikambo
2003-09-16 23:12       ` Zwane Mwaikambo
2003-09-16 23:18         ` Zwane Mwaikambo
2003-09-17  0:01         ` Andries Brouwer
2003-10-06 22:08     ` Petr Vandrovec [this message]
2003-10-14 18:16       ` Petr Vandrovec
2003-10-14 21:27         ` Andries Brouwer
2003-09-13 19:06 ` Pekka Pietikainen
2003-09-12 18:33 Petr Vandrovec
2003-09-13 18:52 ` Andries Brouwer
2003-09-13 21:40   ` Petr Vandrovec
2003-09-14 10:13     ` Andries Brouwer
2003-09-14 10:34       ` Andries Brouwer
2003-09-14 19:52         ` Petr Vandrovec
2003-09-14 22:10           ` Andries Brouwer
2003-09-19 11:38     ` Vojtech Pavlik

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=20031006220847.GA5139@vana.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    --cc=zwane@linuxpower.ca \
    /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.