From: linas@austin.ibm.com (Linas Vepstas)
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Hard hang in hypervisor!?
Date: Tue, 9 Oct 2007 16:28:10 -0500 [thread overview]
Message-ID: <20071009212810.GN4350@austin.ibm.com> (raw)
In-Reply-To: <20071009211819.GR29559@localdomain>
On Tue, Oct 09, 2007 at 04:18:19PM -0500, Nathan Lynch wrote:
> Linas Vepstas wrote:
> >
> > I was futzing with linux-2.6.23-rc8-mm1 in a power6 lpar when,
> > for whatever reason, a spinlock locked up. The bizarre thing
> > was that the rest of system locked up as well: an ssh terminal,
> > and also an hvc console.
> >
> > Breaking into the debugger showed 4 cpus, 1 of which was
> > deadlocked in the spinlock, and the other 3 in
> > .pseries_dedicated_idle_sleep
> >
> > This was, ahhh, unexpected. What's up with that? Can
> > anyone provide any insight?
>
> Sounds consistent with a task trying to double-acquire the lock, or an
> interrupt handler attempting to acquire a lock that the current task
> holds. Or maybe even an uninitialized spinlock. Do you know which
> lock it was?
Not sure .. trying to find out now. But why would that kill the
ssh session, and the console? Sure, so maybe one cpu is spinning,
but the other three can still take interrupts, right? The ssh session
should have been generating ethernet card interrupts, and the console
should have been generating hvc interrupts.
Err .. it was cpu 0 that was spinlocked. Are interrupts not
distributed?
Perhaps I should IRC this ...
--linas
next prev parent reply other threads:[~2007-10-09 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:37 Hard hang in hypervisor!? Linas Vepstas
2007-10-09 21:18 ` Nathan Lynch
2007-10-09 21:28 ` Linas Vepstas [this message]
2007-10-09 23:22 ` never mind .. [was " Linas Vepstas
2007-10-11 0:04 ` Paul Mackerras
2007-10-11 20:30 ` Linas Vepstas
2007-10-11 21:35 ` Milton Miller
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=20071009212810.GN4350@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.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;
as well as URLs for NNTP newsgroup(s).