[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46B75DD4.5080709@redhat.com>
Date: Mon, 06 Aug 2007 13:43:48 -0400
From: Chuck Ebbert <cebbert@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Marcin Ĺšlusarz <marcin.slusarz@...il.com>,
Jarek Poplawski <jarkao2@...pl>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jean-Baptiste Vignaud <vignaud@...dmail.fr>,
linux-kernel <linux-kernel@...r.kernel.org>,
shemminger <shemminger@...ux-foundation.org>,
linux-net <linux-net@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: 2.6.20->2.6.21 - networking dies after random time
On 08/06/2007 03:03 AM, Ingo Molnar wrote:
>
> But, since level types don't need this retriggers too much I think
> this "don't mask interrupts by default" idea should be rethinked:
> is there enough gain to risk such hard to diagnose errors?
>
>
I reverted those masking changes in Fedora and the baffling problem
with 3Com 3C905 network adapters went away.
Before, they would print:
eth0: transmit timed out, tx_status 00 status e601.
diagnostics: net 0ccc media 8880 dma 0000003a fifo 0000
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Flags; bus-master 1, dirty 295757(13) current 295757(13)
Transmit list 00000000 vs. f7150a20.
0: @f7150200 length 80000070 status 0c010070
1: @f71502a0 length 80000070 status 0c010070
2: @f7150340 length 8000005c status 0c01005c
Now they just work, apparently...
So why not just revert the change?
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists