From: Vojtech Pavlik <vojtech@suse.cz>
To: Michael Frank <mhf@linuxmail.org>
Cc: akpm@osdl.org, anton@samba.org,
kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x atkbd.c moaning
Date: Thu, 18 Mar 2004 20:58:19 +0100 [thread overview]
Message-ID: <20040318195819.GB4248@ucw.cz> (raw)
In-Reply-To: <opr42nq0a24evsfm@smtp.pacific.net.th>
On Fri, Mar 19, 2004 at 03:14:50AM +0800, Michael Frank wrote:
> On Fri, 19 Mar 2004 01:03:38 +0800, Michael Frank <mhf@linuxmail.org> wrote:
>
> >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 Unknown key release msg is introduced in 2.6.1 with i8042
> changesets from 1.33 to 1.35 (likely 1.34 as Anton suggested). Guess i
> did not think much of it as it was "smaller" but "blaming xfree"
> during boot since 2.6.2 caught my attention.
XFree86 was fixed (post 4.4) thanks to this message. kbdrate is also
fixed in the current version. With latest XFree86 and latest kbd package
you shouldn't be getting this message anymore.
> >The patch has no effect.
> >
> >Also the mouse screws up after a few hours and becomes unusable.
> On 2.6.4
>
> On 2.6.[012] the mouse does not sync at all (even after power up).
>
> On 2.4.18-26 mouse never had problems.
Can you give details on the mouse and the machine? I seem to have missed
them.
> >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.
>
> Could also be load dependent. Will do more testing on 2.6.4 to reproduce.
>
> The serious issue with the mouse is that it does not recover and stays
> out of sync and interprets further movement as random coordinates/button
> clicks.
Does unloading and reloading the psmouse module help?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-03-18 19:57 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
2004-03-18 19:14 ` Michael Frank
2004-03-18 19:34 ` Michael Frank
2004-03-18 19:58 ` Vojtech Pavlik [this message]
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=20040318195819.GB4248@ucw.cz \
--to=vojtech@suse.cz \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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