From: "Michael Frank" <mhf@linuxmail.org>
To: "Anton Blanchard" <anton@samba.org>
Cc: "kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x atkbd.c moaning
Date: Fri, 19 Mar 2004 01:03:38 +0800 [thread overview]
Message-ID: <opr42hoctn4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <20040318120114.GN28212@krispykreme>
On Thu, 18 Mar 2004 23:01:14 +1100, Anton Blanchard <anton@samba.org> wrote:
>
>> Why is this and should I investigate further?
> ..
>
>> mice: PS/2 mouse device common for all mice
>> serio: i8042 AUX port at 0x60,0x64 irq 12
>> input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
>> serio: i8042 KBD port at 0x60,0x64 irq 1
>> input: AT Translated Set 2 keyboard on isa0060/serio0
>> atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
>
> Did this happen recently? If so, does backing out the following patch help?
I think so but later than this changeset 1.34 of 19 December.
The patch has no effect.
Also the mouse screws up after a few hours and becomes unusable.
psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
I will test backwards which version inttroduced problems.
Regards
Michael
next prev parent reply other threads:[~2004-03-18 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 10:47 2.6.x atkbd.c moaning Michael Frank
2004-03-18 12:01 ` Anton Blanchard
2004-03-18 17:03 ` Michael Frank [this message]
2004-03-18 19:14 ` Michael Frank
2004-03-18 19:34 ` Michael Frank
2004-03-18 19:58 ` Vojtech Pavlik
2004-03-18 20:46 ` Michael Frank
2004-03-18 21:07 ` Vojtech Pavlik
2004-03-18 21:50 ` Michael Frank
2004-03-18 21:58 ` Michael Frank
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=opr42hoctn4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=anton@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox