From: Ralf Baechle <ralf@linux-mips.org>
To: Peter Watkins <treestem@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: SGI Origin 200 (ip27) with DEBUG_SPINLOCK
Date: Fri, 29 Sep 2006 00:59:37 +0100 [thread overview]
Message-ID: <20060928235937.GF3394@linux-mips.org> (raw)
In-Reply-To: <451C134C.6010806@gmail.com>
On Thu, Sep 28, 2006 at 02:24:12PM -0400, Peter Watkins wrote:
> Greetings SGI Origin wizards,
>
> I'm doing some SMP testing on an SGI Origin 200 (ip27).
>
> I started with a 2.6.15 vintage kernel and added changes from here:
> ftp://ftp.linux-mips.org/pub/linux/mips/people/ralf/ip27/
There have been a few significant fixes to the Origin code IP27 since
2.6.15 ...
> It boots both processors and runs OK.
>
> Then I turn on CONFIG_DEBUG_SPINLOCK and CONFIG_DEBUG_SPINLOCK_SLEEP,
> and get lots of lockup messages. A typical one is below.
>
> Anyone seen this? Some of the low-level lock code has R10000_LLSC_WAR
> versions, but I don't see anything wrong there.
The R10000_LLSC_WAR is a workaround for a CPU bug in certain relativly
old version of the R10000 processor. Version 2.6 or older were affected
but the cutoff version number could have been 2.7. Anyway, the sympthom
was that possibly multiple processors were taking a able to grab a
spinlock which obvious is the way to disaster. I originally found the
problem when analyzing why rebuilding a MD RAID array was resulting in a
crash.
Even with that fix applied I found a MD RAID 5 / 6 not very stable as of
last week; it seems this instability is limited to IP27 and IP30 and it
seemed like the various kernel debuging options I tried were aggrevating
the problem significantly.
Ralf
prev parent reply other threads:[~2006-09-28 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:24 SGI Origin 200 (ip27) with DEBUG_SPINLOCK Peter Watkins
2006-09-28 23:59 ` Ralf Baechle [this message]
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=20060928235937.GF3394@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=treestem@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