From: David Miller <davem@davemloft.net>
To: paulmck@linux.vnet.ibm.com
Cc: mroos@linux.ee, linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: RCU detected CPU 0 stall after panic on sparc64
Date: Mon, 14 Dec 2009 21:02:01 +0000 [thread overview]
Message-ID: <20091214.130201.144162604.davem@davemloft.net> (raw)
In-Reply-To: <20091214202556.GC6679@linux.vnet.ibm.com>
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date: Mon, 14 Dec 2009 12:25:56 -0800
> Hmmm... At first glance, it looks like RCU should put a notifier onto
> the panic_notifier_list to disable this check. Or is there some global
> variable that I can check?
Probably the notifier works just fine.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: paulmck@linux.vnet.ibm.com
Cc: mroos@linux.ee, linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: RCU detected CPU 0 stall after panic on sparc64
Date: Mon, 14 Dec 2009 13:02:01 -0800 (PST) [thread overview]
Message-ID: <20091214.130201.144162604.davem@davemloft.net> (raw)
In-Reply-To: <20091214202556.GC6679@linux.vnet.ibm.com>
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date: Mon, 14 Dec 2009 12:25:56 -0800
> Hmmm... At first glance, it looks like RCU should put a notifier onto
> the panic_notifier_list to disable this check. Or is there some global
> variable that I can check?
Probably the notifier works just fine.
next prev parent reply other threads:[~2009-12-14 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 8:54 RCU detected CPU 0 stall after panic on sparc64 Meelis Roos
2009-12-12 8:54 ` Meelis Roos
2009-12-12 9:40 ` David Miller
2009-12-12 9:40 ` David Miller
2009-12-14 20:25 ` Paul E. McKenney
2009-12-14 20:25 ` Paul E. McKenney
2009-12-14 21:02 ` David Miller [this message]
2009-12-14 21:02 ` David Miller
2009-12-14 23:15 ` Paul E. McKenney
2009-12-14 23:15 ` Paul E. McKenney
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=20091214.130201.144162604.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.