From: Berkley Shands <berkley@cse.wustl.edu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.23 spinlock hang in kswapd under heavy disk write loads
Date: Thu, 11 Oct 2007 19:56:44 -0500 [thread overview]
Message-ID: <470EC64C.10402@cse.wustl.edu> (raw)
In-Reply-To: <200710101531.26944.nickpiggin@yahoo.com.au>
100% reproducible on the two motherboards in question.
Does not happen on any other motherboard I have in my possession
(not tyan, not uniwide, not socket 940...)
No errors, no dmesg, nothing with debug_spinlock set.
<sysrq> shows lots (when it works), but by then too many things are
locked up to be of much use. I can get into KDB and look around
(2.6.22 for kdb - it hangs there too). Even access to the local disk is
blocked.
Processes in core and running remain there (iostat, top, ...).
I personally think the bios are suspect on the PCIe, as symptoms change with
the bios rev. I did a major paper on SAS performance with one H8DMi,
but it got a bios rev, and now crashes. Missed interrupt? APIC sending
an interrupt to multiple cpus? I don't know.
Tell me what to look at, and I can get you the info. It usually takes 20
seconds
to go bang, using either the LSI8888ELP or the rocket raid 2340. Other
controllers
are too slow. 2.6.20 does not lock up. It is also 200MB/Sec slower in
writing :-)
thanks for the response.
berkley
next prev parent reply other threads:[~2007-10-11 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 15:33 2.6.23 spinlock hang in kswapd under heavy disk write loads Berkley Shands
2007-10-10 5:31 ` Nick Piggin
2007-10-12 0:56 ` Berkley Shands [this message]
2007-10-10 10:52 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
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=470EC64C.10402@cse.wustl.edu \
--to=berkley@cse.wustl.edu \
--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