From: Stian Jordet <liste@jordet.nu>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mouse/Keyboard problems with 2.5.38
Date: 27 Sep 2002 00:50:40 +0200 [thread overview]
Message-ID: <1033080648.593.12.camel@chevrolet> (raw)
In-Reply-To: <20020926185717.B27676@ucw.cz>
tor, 2002-09-26 kl. 18:57 skrev Vojtech Pavlik:
> Great. So, the problem is in i8042.c untranslating the keycodes. Please
> also enable #define I8042_DEBUG_IO in drivers/input/serio/i8042.h, don't
> start X, enable maximum console loglevel by "echo 16 16 16 16 >
> /proc/sys/kernel/printk", and press the killing key combination.
> (without i8042_direct, of course). Then send me the ten last or so lines
> printed. This should allow me to fix the problem. Thanks.
Ok, I did as prescribed. I did press SHIFT+PAGEUP, and it came quite a
lot of output, more than one page. I'm not sure if this is enough, but
it was all I could see. When I booted, I looked in the syslog, but none
of what I wrote off the screen was there. I guess that's because it
froze. Ok, here come. This is writeoff, so might be some small errors.
I don't know, but I guess I must have touched the mouse to get the four
last lines? I guess so, but I'm including them to be sure.
i8042.c: fa <- i8042 (interrupt, kbd, 1) [60519]
atkbd.c: Received fa flags 00
atkbd.c: Sent: 02
i8042.c: 02 -> i8042 (kbd-data) [60519]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [60523]
atkbd.c: Received fa flags 00
atkbd.c: Sent: f0
i8042.c: f0 -> i8042 (kbd-data) [60523]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [60527]
atkbd.c: Received fa flags 00
atkbd.c: Sent: 00
i8042.c: 00 -> i8042 (kbd-data) [60527]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [60531]
atkbd.c: Received fa flags 00
i8042.c: 41 <- i8042 (interrupt, kbd, 1) [60532]
atkbd.c: Received 02 flags 00
input: AT Set 2 keyboard on isa0060/serio0
i8042.c: b6 <- i8042 (interrupt, kbd, 1) [60599]
atkbd.c: Received f0 flags 00
atkbd.c: Received 59 flags 00
i8042.c: 38 <- i8042 (interrupt, aux, 12) [104472]
i8042.c: fd <- i8042 (interrupt, aux, 12) [104473]
i8042.c: fe <- i8042 (interrupt, aux, 12) [104474]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [104475]
I hope you get something out of this, I don't, for sure. The input:...
line is the same as I get without any debug info when it locks.
Oh well, time for some schoolwork.
Thanks.
Best regards,
Stian Jordet
next prev parent reply other threads:[~2002-09-26 22:45 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
2002-09-26 15:30 ` Stian Jordet
2002-09-26 16:57 ` Vojtech Pavlik
2002-09-26 22:50 ` Stian Jordet [this message]
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=1033080648.593.12.camel@chevrolet \
--to=liste@jordet.nu \
--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;
as well as URLs for NNTP newsgroup(s).