[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070730084925.GA12695@elte.hu>
Date: Mon, 30 Jul 2007 10:49:25 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Marcin Ślusarz <marcin.slusarz@...il.com>
Cc: 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
* Marcin Ślusarz <marcin.slusarz@...il.com> wrote:
> > Subject: x86: activate HARDIRQS_SW_RESEND
> > From: Ingo Molnar <mingo@...e.hu>
> >
> > activate the software-triggered IRQ-resend logic.
> This patch didn't help (tested on 2.6.22.1) - ne2k_pci timed out.
ok. This makes it more likely that the driver itself (or the card) gets
confused by the resend.
does the patch below fix those timeouts? It tests the theory whether any
POST latency could expose this problem.
Ingo
Index: linux/drivers/net/lib8390.c
===================================================================
--- linux.orig/drivers/net/lib8390.c
+++ linux/drivers/net/lib8390.c
@@ -375,6 +375,8 @@ static int ei_start_xmit(struct sk_buff
/* Turn 8390 interrupts back on. */
ei_local->irqlock = 0;
ei_outb_p(ENISR_ALL, e8390_base + EN0_IMR);
+ /* force POST: */
+ ei_inb_p(e8390_base + EN0_IMR);
spin_unlock(&ei_local->page_lock);
enable_irq_lockdep_irqrestore(dev->irq, &flags);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists