From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Victor Hahn <victorhahn@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Really annoying bug in the mouse driver
Date: Wed, 2 Feb 2005 01:26:37 -0500 [thread overview]
Message-ID: <200502020126.37621.dtor_core@ameritech.net> (raw)
In-Reply-To: <42006E79.7070503@web.de>
On Wednesday 02 February 2005 01:08, Victor Hahn wrote:
> Dmitry Torokhov wrote:
>
> >Any luck with the patch?
> >
>
> I'm using 2.6.11rc2 with the patch for some hours now and it seems as if
> it doesn't throw away bytes any more which makes linux 2.6 useable for
> me again - thanks a lot!
It still complains in dmesg about throwing away bytes, right? Please try
loading the box some more to make sure mouse survives some abuse.
> I just encountered one smaller issue (this
> really is much better than before): The mouse just "jumped" once and
> then got back to normal immediately. This gives me the following message
> in /var/log/messages:
>
> kernel: psmouse.c: bad data from KBC - bad parity
>
Your keyboard controller reported that the byte transmitted from the mouse
was mangled somehow and we should not trust it. I am not sure why it would
make mouse jump.. was there any mention of "reconnect" in the logs? Did it
happen just once?
--
Dmitry
next prev parent reply other threads:[~2005-02-02 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 13:16 Really annoying bug in the mouse driver Victor Hahn
2005-01-28 7:06 ` Dmitry Torokhov
2005-02-01 8:54 ` Victor Hahn
2005-02-01 13:56 ` Dmitry Torokhov
2005-02-01 14:19 ` Victor Hahn
2005-02-01 23:19 ` Dmitry Torokhov
2005-02-02 6:08 ` Victor Hahn
2005-02-02 6:26 ` Dmitry Torokhov [this message]
2005-02-02 10:22 ` Victor Hahn
2005-02-02 15:44 ` Dmitry Torokhov
2005-02-03 15:05 ` Victor Hahn
2005-02-03 15:17 ` Dmitry Torokhov
2005-02-01 13:29 ` zhilla
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=200502020126.37621.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=victorhahn@web.de \
/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