linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Stian Jordet <liste@jordet.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mouse/Keyboard problems with 2.5.38
Date: Thu, 26 Sep 2002 13:37:25 +0200	[thread overview]
Message-ID: <20020926133725.A8851@ucw.cz> (raw)
In-Reply-To: <1033039991.708.6.camel@chevrolet>; from liste@jordet.nu on Thu, Sep 26, 2002 at 01:32:59PM +0200

On Thu, Sep 26, 2002 at 01:32:59PM +0200, Stian Jordet wrote:

> > > Second problem, if I press SHIFT+PAGEUP, my computer freezes. It spits
> > > out this message: "input: AT Set 2 keyboard on isa0060/serio0, and then
> > > it's dead. I have a Logitech cordless keyboard. 
> > > 
> > > Anyone else experienced this?
> > 
> > I fixed this in about 2.5.36. Please #define ATKBD_DEBUG in
> > drivers/input/keyboard/atkbd.c, and send me the kernel output just
> > before the crash, please. I'll try to reproduce it here meanwhile.
> 
> I'm added #define ATKBD_DEBUG right below all the other define's in
> atkbd.c, did a make clean; make dep; make bzImage and tried again. I
> can't see any difference. It still just prints "input: AT Set 2 keyboard
> on isa0060/serio0".

Hmm, have you looked into 'dmesg'? It prints the information with
KERN_DEBUG priority, which often won't make it on the screen or into the
logs ...

> I did, however, find out that if I press SHIFT+what
> ever of the buttons arrows, insert, home, page up/down, delete and end,
> I get just the same behaviour. It does not happen with CTRL or ALT.

Can you try passing 'i8042_direct' on the kernel command line to see if
it cures the problem? It looks like your keyboard is doing some very
strange 84-key-at-emulation, stranger than others do ...

> Thank you very much.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-09-26 11:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 23:31 Mouse/Keyboard problems with 2.5.38 Stian Jordet
2002-09-25 23:47 ` Brad Hards
2002-09-26  8:58 ` Vojtech Pavlik
2002-09-26 11:32   ` Stian Jordet
2002-09-26 11:37     ` Vojtech Pavlik [this message]
2002-09-26 15:30       ` Stian Jordet
2002-09-26 16:57         ` Vojtech Pavlik
2002-09-26 22:50           ` Stian Jordet
2002-09-27  7:10             ` Vojtech Pavlik
2002-09-27 11:51               ` Stian Jordet
2002-10-07 13:00                 ` Vojtech Pavlik
2002-10-07 19:55                   ` Stian Jordet
2002-10-07 20:01                     ` Vojtech Pavlik
2002-10-08  0:20                       ` Stian Jordet
2002-10-08  8:17                         ` Vojtech Pavlik
2002-10-08 17:18                           ` Stian Jordet
2002-10-08 17:25                             ` Vojtech Pavlik
2002-10-08 23:48                               ` Stian Jordet
     [not found]                                 ` <20021009082215.C1890@ucw.cz>
2002-10-09 10:42                                   ` Stian Jordet
2002-10-09  0:54                               ` Stian Jordet
2002-09-30 22:10               ` Stian Jordet
     [not found] <20021008085842.A4412@ucw.cz>
2002-10-08 17:14 ` Stian Jordet
2002-10-08 17:23   ` 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=20020926133725.A8851@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    /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;
as well as URLs for NNTP newsgroup(s).