Date: Wed, 4 Jun 2003 01:14:13 -0700
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
Message-Id: <20030604011413.16787964.akpm@digeo.com>
In-Reply-To: <20030604100017.A5475@ucw.cz>
References: <1054431962.22103.744.camel@cube>
	<3EDD87FD.6020307@ifrance.com>
	<20030603232155.1488c02f.akpm@digeo.com>
	<20030604094737.C5345@ucw.cz>
	<20030604005302.41f3b0b8.akpm@digeo.com>
	<20030604100017.A5475@ucw.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 635
Lines: 16

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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/