From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarek Poplawski Subject: Re: 2.6.20->2.6.21 - networking dies after random time Date: Thu, 26 Jul 2007 11:11:57 +0200 Message-ID: <20070726091157.GB3423@ff.dom.local> References: <20070629150759.GC2771@ff.dom.local> <4bacf17f0707222244p664e7a6ap850b3357a57d73c@mail.gmail.com> <20070724080534.GC18740@elte.hu> <20070724094202.GA11610@elte.hu> <20070724200431.GA22190@elte.hu> <1185322771.4175.102.camel@chaos> <4bacf17f0707260016x14fc1c92s628ae64353663833@mail.gmail.com> <20070726081326.GA3197@ff.dom.local> <1185437431.3227.21.camel@chaos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Marcin =?iso-8859-2?Q?=A6lusarz?= , Ingo Molnar , Linus Torvalds , Jean-Baptiste Vignaud , linux-kernel , shemminger , linux-net , netdev , Andrew Morton , Alan Cox To: Thomas Gleixner Return-path: Content-Disposition: inline In-Reply-To: <1185437431.3227.21.camel@chaos> Sender: linux-net-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Jul 26, 2007 at 10:10:31AM +0200, Thomas Gleixner wrote: > On Thu, 2007-07-26 at 10:13 +0200, Jarek Poplawski wrote: ... > > PS: Now, it seems to me Thomas could be the nearest. BTW, could somebody > > give me some tip, how these re-triggered interrupts are skipped on dev's > > reset before enable_irq? > > I think the correct solution is really not to resend level type > interrupts. If the interrupt line is still active, then the interrupt > comes up by itself. I'm cooking a patch for that. > > The other question is: > > Is the driver confused by the resent irq or is the chip-set unhappy > about the resend ? > > We could figure the latter out by activating the software based resend > method. Probably I miss something, but isn't there any problem with level type, when APIC re-triggers an interrupt, which is not acked by driver nor card (after some hw reset/clear)? Jarek P.