Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760089AbXHGKIt (ORCPT ); Tue, 7 Aug 2007 06:08:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756330AbXHGKIh (ORCPT ); Tue, 7 Aug 2007 06:08:37 -0400 Received: from mx2.go2.pl ([193.17.41.42]:50203 "EHLO poczta.o2.pl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753384AbXHGKIg (ORCPT ); Tue, 7 Aug 2007 06:08:36 -0400 Date: Tue, 7 Aug 2007 12:09:05 +0200 From: Jarek Poplawski To: Chuck Ebbert Cc: Ingo Molnar , Marcin =?iso-8859-2?Q?=A6lusarz?= , Thomas Gleixner , Linus Torvalds , Jean-Baptiste Vignaud , linux-kernel , shemminger , linux-net , netdev , Andrew Morton , Alan Cox Subject: Re: 2.6.20->2.6.21 - networking dies after random time Message-ID: <20070807100905.GC3223@ff.dom.local> References: <20070726081326.GA3197@ff.dom.local> <1185437431.3227.21.camel@chaos> <20070726083120.GA26910@elte.hu> <20070726085523.GA3423@ff.dom.local> <20070726091254.GA8063@elte.hu> <4bacf17f0707300029g5116e70bq4808059dc8b069f1@mail.gmail.com> <20070731132037.GC1046@ff.dom.local> <4bacf17f0708060000n5a00bb77i74adc3b4b28ac42b@mail.gmail.com> <20070806070300.GA4509@elte.hu> <46B75DD4.5080709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46B75DD4.5080709@redhat.com> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1563 Lines: 40 On Mon, Aug 06, 2007 at 01:43:48PM -0400, Chuck Ebbert wrote: > 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? > Ingo has written about such possibility. But, it would be good to know which precisely place is to blame, as well. Since this diagnosing takes time, I think Chuck is right, and maybe at least this temporary patch for resend.c without this warning, should be recomended for stables (2.6.21 and 2.6.22)? Jarek P. - 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/