From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>, Jeff Garzik <jgarzik@pobox.com>
Cc: Brad Campbell <brad@wasp.net.au>,
Manfred Spraul <manfred@colorfullife.com>,
Andi Kleen <andi@firstfloor.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG() in 2.6.28-rc8-git2 under heavy load
Date: Mon, 22 Dec 2008 13:24:33 +0100 [thread overview]
Message-ID: <20081222122433.GA27124@elte.hu> (raw)
In-Reply-To: <19f34abd0812220406i36d5df21ka321e3eb4993c54c@mail.gmail.com>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Mon, Dec 22, 2008 at 9:14 AM, Brad Campbell <brad@wasp.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
next prev parent reply other threads:[~2008-12-22 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 8:14 BUG() in 2.6.28-rc8-git2 under heavy load Brad Campbell
2008-12-22 12:06 ` Vegard Nossum
2008-12-22 12:24 ` Ingo Molnar [this message]
2008-12-23 0:30 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081222122433.GA27124@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=brad@wasp.net.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox