From: "Mr. Berkley Shands" <bshands@exegy.com>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23 spinlock hang in kswapd under heavy disk write loads
Date: Thu, 11 Oct 2007 11:23:30 -0500 [thread overview]
Message-ID: <470E4E02.4000504@exegy.com> (raw)
With DEBUG_SLAB on, I can run only a very short time under 2.6.23
before a kernel panic.
[ 626.028180] eth0: too many iterations (6) in nv_nic_irq.
[ 626.167583] eth0: too many iterations (6) in nv_nic_irq.
[ 626.206729] eth0: too many iterations (6) in nv_nic_irq.
[ 626.400171] eth0: too many iterations (6) in nv_nic_irq.
[ 626.446374] eth0: too many iterations (6) in nv_nic_irq.
followed by the crash at
forcedeth:nv_nic_irq_optimized+0x89
handle_IRQ_event+0x25
handle_edge_IRQ+0xe3
do_IRQ
berkley
This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.
next reply other threads:[~2007-10-11 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 16:23 Mr. Berkley Shands [this message]
2007-10-11 10:32 ` 2.6.23 spinlock hang in kswapd under heavy disk write loads Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2007-10-10 15:33 Berkley Shands
2007-10-10 5:31 ` Nick Piggin
2007-10-12 0:56 ` Berkley Shands
2007-10-10 10:52 ` Nick Piggin
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=470E4E02.4000504@exegy.com \
--to=bshands@exegy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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