From: berkley@cse.wustl.edu (Berkley Shands)
To: linux-kernel@vger.kernel.org
Subject: 2.6.23 spinlock hang in kswapd under heavy disk write loads
Date: Wed, 10 Oct 2007 10:33:32 -0500 (CDT) [thread overview]
Message-ID: <20071010153332.71479CECBD@tamarack.cse.wustl.edu> (raw)
2.6.23 with CONFIG_DEBUG_SPINLOCK on does not hang under very high write loads
to either an LSI8888ELP (write rate 1.1GB/Sec) or to a highpoint RR2340 (write rate 1.0GB/Sec).
With CONFIG_DEBUG_SPINLOCK off however, the system hangs with kswapd getting
100% of the cpu and most if not all other processes are locked out. Sometimes even the
keyboard is locked out.
This is seen on a supermicro H8DM3-2 and H8DMi-2 motherboards, 16 GB RAM, 2222 SE or 2216 processors.
Not seen on a Uniwide 3546ES, or on a Supermicro H8DM8 with 8222 CPUS.
kswapd sits at (according to KDB)
__spinlock_irqsave + 0x15
prepare_to_wait + 0x15
kswapd + 0xe3
kthread + 0x47
berkley
next reply other threads:[~2007-10-10 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 15:33 Berkley Shands [this message]
2007-10-10 5:31 ` Nick Piggin
2007-10-12 0:56 ` Berkley Shands
2007-10-10 10:52 ` Nick Piggin
2007-10-11 16:23 Mr. Berkley Shands
2007-10-11 10:32 ` 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=20071010153332.71479CECBD@tamarack.cse.wustl.edu \
--to=berkley@cse.wustl.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®