From: Andrew Morton <akpm@digeo.com>
To: Vojtech Pavlik <vojtech@ucw.cz>
Cc: linux-yoann@ifrance.com, linux-kernel@vger.kernel.org,
vojtech@suse.cz, acahalan@cs.uml.edu
Subject: Re: another must-fix: major PS/2 mouse problem
Date: Wed, 4 Jun 2003 01:14:13 -0700 [thread overview]
Message-ID: <20030604011413.16787964.akpm@digeo.com> (raw)
In-Reply-To: <20030604100017.A5475@ucw.cz>
Vojtech Pavlik <vojtech@ucw.cz> wrote:
>
> > Has this problem been observed in 2.4 kernels?
>
> No, since 2.4 doesn't have the re-sync code in the mouse driver which is
> triggering in this case. But problems with the machine being flooded
> with interrupts from the NIC so hard that it actually cannot do anything
> are quite common.
So is the resync code doing more good than harm?
next prev parent reply other threads:[~2003-06-04 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 1:46 another must-fix: major PS/2 mouse problem Albert Cahalan
2003-06-04 5:47 ` Yoann
[not found] ` <20030603232155.1488c02f.akpm@digeo.com>
2003-06-04 7:47 ` Vojtech Pavlik
2003-06-04 7:53 ` Andrew Morton
2003-06-04 8:00 ` Vojtech Pavlik
2003-06-04 8:14 ` Andrew Morton [this message]
2003-06-04 8:40 ` Vojtech Pavlik
2003-06-04 19:20 ` Yoann
2003-06-04 23:09 ` Albert Cahalan
[not found] ` <3EDCF47A.1060605@ifrance.com>
[not found] ` <1054681254.22103.3750.camel@cube>
[not found] ` <3EDD8850.9060808@ifrance.com>
2003-07-23 0:44 ` Albert Cahalan
2003-07-24 17:30 ` Andrew Morton
2003-07-25 1:46 ` Albert Cahalan
2003-07-26 3:19 ` Andrew Morton
2003-07-26 15:16 ` Zwane Mwaikambo
2003-07-29 2:55 ` Albert Cahalan
2003-07-29 3:14 ` Andrew Morton
2003-07-29 12:40 ` Albert Cahalan
2003-07-29 18:58 ` Andrew Morton
2003-07-29 19:36 ` Zwane Mwaikambo
2003-07-29 19:43 ` Chris Friesen
2003-07-30 5:08 ` Pavel Machek
2003-07-30 6:32 ` Andrew Morton
2003-07-30 12:29 ` Albert Cahalan
2003-07-30 19:18 Mikael Pettersson
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=20030604011413.16787964.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-yoann@ifrance.com \
--cc=vojtech@suse.cz \
--cc=vojtech@ucw.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).