From: Peter Zijlstra <peterz@infradead.org>
To: NeilBrown <neilb@suse.de>
Cc: fengguang.wu@intel.com, "Li, Shaohua" <shaohua.li@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: kernel BUG at drivers/md/raid5.c:693!
Date: Tue, 26 Nov 2013 10:42:50 +0100 [thread overview]
Message-ID: <20131126094250.GH10022@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20131126153106.6ae734c0@notabene.brown>
On Tue, Nov 26, 2013 at 03:31:06PM +1100, NeilBrown wrote:
> The stack trace in the previous email seemed to suggest that a process was
> blocking inside a wake_up call, but it wasn't at all conclusive. And I've
> seen a few wake_ups in other stack traces which seem to be connected with
> other deadlock. Probably some sort of co-incidence.
It appears stuck in some paravirt clock layer.. or just a lucky hit.
I never run on (para)virt if I can help it, so I'm not much help there.
prev parent reply other threads:[~2013-11-26 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 3:22 kernel BUG at drivers/md/raid5.c:693! fengguang.wu
2013-11-24 23:35 ` NeilBrown
2013-11-25 1:29 ` Fengguang Wu
2013-11-25 9:53 ` Peter Zijlstra
2013-11-26 4:31 ` NeilBrown
2013-11-26 9:42 ` Peter Zijlstra [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=20131126094250.GH10022@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=neilb@suse.de \
--cc=shaohua.li@intel.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