From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarek Poplawski Subject: Re: [patch (testing)] Re: 2.6.20->2.6.21 - networking dies after random time Date: Fri, 10 Aug 2007 11:19:54 +0200 Message-ID: <20070810091954.GI1764@ff.dom.local> References: <20070810083720.GE1764@ff.dom.local> <20070810084841.GA11086@elte.hu> <20070810090318.GG1764@ff.dom.local> <20070810090833.GA15121@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jean-Baptiste Vignaud , "marcin\.slusarz" , tglx , torvalds , linux-kernel , shemminger , linux-net , netdev , akpm , alan To: Ingo Molnar Return-path: Received: from mx12.go2.pl ([193.17.41.142]:47602 "EHLO poczta.o2.pl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751783AbXHJJTS (ORCPT ); Fri, 10 Aug 2007 05:19:18 -0400 Content-Disposition: inline In-Reply-To: <20070810090833.GA15121@elte.hu> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, Aug 10, 2007 at 11:08:33AM +0200, Ingo Molnar wrote: > > * Jarek Poplawski wrote: > > > On 10-08-2007 10:05, Thomas Gleixner wrote: > > ... > > > But suppressing the resend is not fixing the driver problem. The > > > problem can show up with spurious interrupts and with interrupts on > > > a shared PCI interrupt line at any time. It just might take weeks > > > instead of minutes. > > > > Maybe I miss something but it's not the same! > > _now_ i finally understand what you probably meant: because sw-resend > worked and hw-resend didnt, it's hw-resend that is causing the breakage, > not any driver or irqflow bug - correct? All correct! There was also checked a possibility it can be not hw itself, but wrong way of handling after hw (acking too late). This was false idea (or bad implementation), so it looks like hw vs lapic problem. Jarek P.