[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081222122433.GA27124@elte.hu>
Date: Mon, 22 Dec 2008 13:24:33 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Vegard Nossum <vegard.nossum@...il.com>,
Jeff Garzik <jgarzik@...ox.com>
Cc: Brad Campbell <brad@...p.net.au>,
Manfred Spraul <manfred@...orfullife.com>,
Andi Kleen <andi@...stfloor.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: BUG() in 2.6.28-rc8-git2 under heavy load
* Vegard Nossum <vegard.nossum@...il.com> wrote:
> On Mon, Dec 22, 2008 at 9:14 AM, Brad Campbell <brad@...p.net.au> wrote:
> > I got a number of BUG()s in my kernel log during a RAID expansion. I did not
> > notice any ill effects, the system recovered well and has been ok since.
> > I've not had the opportunity to reboot as yet, but I thought them worth
> > reporting.
> >
> > I'm really unsure as to the relevant details on this one, so I've attached
> > everything just in case.
> >
> > I'm also seeing *loads* of [158921.049256] eth0: too many iterations (6) in
> > nv_nic_irq.
>
> This might be related. You may try to change the max_interrupt_work
> module parameter to something greater, e.g.
> forcedeth.max_interrupt_work=50 on the kernel command line or "modprobe
> forcedeth max_interrupt_work=50" in the terminal.
btw., that default limit of 6 is ridiculously low - i see it trigger on
all forcedeth boxes i have, under benign load situations - all the time.
Could someone please send a patch to Jeff that raises it to 50 ?
Ingo
--
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