[13250] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Flaw in 3c59x.c or in Kernel?

daemon@ATHENA.MIT.EDU (David Malone)
Wed Jan 5 16:08:21 2000

Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-Id:  <20000105104253.A31162@walton.maths.tcd.ie>
Date:         Wed, 5 Jan 2000 10:42:53 +0000
Reply-To: dwmalone@MATHS.TCD.IE
From: David Malone <dwmalone@MATHS.TCD.IE>
X-To:         Sonny Parlin <parlin@STARBURSTSOFTWARE.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <000e01bf56bf$027c3520$b96021ce@starburstcom.com>; from
              parlin@STARBURSTSOFTWARE.COM on Tue, Jan 04,
              2000 at 09:21:36AM -0500

On Tue, Jan 04, 2000 at 09:21:36AM -0500, Sonny Parlin wrote:

> eth1: Too much work in interrupt, status e481. Temporarily disabling
> functions(7b7e).

We saw this with some Linux machines in college that were connected
to busy 100Mb/s ethernet. Bill Paul is right when he says ifconfiging
down and then up fixes the hang. To work around the problem we changed
max_interrupt_work from 20 to 200 and I don't think they've seen any
hangs since. (You can find this in the .c file for the driver).

These machines were also seeing hard lockups - keyboard stopped
responding. This seemed to stop too when we upped this variable.

	David.

home help back first fref pref prev next nref lref last post