From: Mike Houston <mikeserv@bmts.com>
To: linux-kernel@vger.kernel.org
Subject: Re: psmouse.c, throwing 3 bytes away
Date: Fri, 6 Feb 2004 02:15:22 -0500 [thread overview]
Message-ID: <20040206021522.12dfd362.mikeserv@bmts.com> (raw)
In-Reply-To: <20040205171028.652a694c.mikeserv@bmts.com>
On Thu, 5 Feb 2004 17:10:27 -0500
Mike Houston <mikeserv@bmts.com> wrote:
> I am using ACPI and IO-APIC. Next time my mouse acts up, I will consider trying
> 2.6.2 without ACPI and IO-APIC (though I'd hate to lose that functionality).
> Trouble is it might take a long time for the mouse glitch to occur.
Ok, shortly after posting earlier today, it did indeed happen again with 2.6.2. I was just clicking on mails in my sylpheed client. There wasn't much load, I wasn't doing anything but reading mails.
So I built another 2.6.2 with acpi and io-apic disabled and ran it for about 5 hours and the problem reoccurred. I was just chatting on IRC and moved my mouse and it happened. Again, I was doing nothing else so load wasn't a factor.
psmouse.c: MX Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Gee whiz, it just happened again while composing this mail :-)
So it doesn't have anything to do with acpi, or being under load for that matter, on my system, anyway.
Mike
next prev parent reply other threads:[~2004-02-06 7:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 2:20 psmouse.c, throwing 3 bytes away Walt Nelson
2004-02-05 4:54 ` Claudio Martins
2004-02-05 10:20 ` Isaac Claymore
2004-02-09 6:15 ` Isaac Claymore
2004-02-09 9:09 ` Vojtech Pavlik
2004-02-09 9:49 ` Isaac Claymore
2004-02-09 9:52 ` Vojtech Pavlik
2004-02-05 13:40 ` Michael Buesch
2004-02-05 15:31 ` johann lombardi
2004-02-05 5:05 ` Mike Houston
2004-02-05 17:24 ` Murilo Pontes
2004-02-05 20:38 ` Vojtech Pavlik
2004-02-05 18:14 ` Murilo Pontes
2004-02-05 19:08 ` Murilo Pontes
2004-02-05 21:06 ` Michael Buesch
2004-02-05 22:10 ` Mike Houston
2004-02-06 7:15 ` Mike Houston [this message]
2004-02-06 8:06 ` Walt Nelson
2004-02-07 5:47 ` Mike Houston
2004-02-07 9:11 ` Murilo Pontes
2004-02-08 21:59 ` Vojtech Pavlik
2004-02-08 22:19 ` aeriksson
2004-02-08 22:32 ` Vojtech Pavlik
2004-02-08 23:03 ` Bernd Schubert
2004-02-08 23:30 ` Vojtech Pavlik
[not found] ` <40278077.5070409@free.fr>
2004-02-09 22:25 ` Bernd Schubert
2004-02-09 0:48 ` [patch] " Vojtech Pavlik
2004-02-09 1:13 ` Claudio Martins
2004-02-09 1:23 ` Vojtech Pavlik
2004-02-10 2:56 ` Greg Norris
2004-02-10 7:07 ` Vojtech Pavlik
2004-02-10 7:39 ` Walt Nelson
2004-02-10 19:48 ` Greg Norris
2004-02-10 20:08 ` Vojtech Pavlik
2004-02-10 7:33 ` johann lombardi
2004-02-10 21:11 ` Murilo Pontes
2004-02-11 4:44 ` Claudio Martins
2004-02-06 0:33 ` Pete Clements
2004-02-06 22:44 ` Kronos
2004-02-07 2:35 ` Jamie Lokier
2004-02-07 4:19 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 6:18 Bob Gill
2004-02-05 21:56 Luis Miguel García
2004-02-05 19:33 ` Murilo Pontes
2004-02-06 7:02 ` Claudio Martins
2004-02-06 10:12 ` Christian Unger
2004-02-06 17:52 ` Adrian Bunk
2004-02-06 18:03 ` Michael Buesch
2004-02-06 21:49 ` Claudio Martins
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=20040206021522.12dfd362.mikeserv@bmts.com \
--to=mikeserv@bmts.com \
--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