From: Mike Galbraith <efault@gmx.de>
To: Michael Breuer <mbreuer@majjas.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Bisected rcu hang (kernel/sched.c): was 2.6.33rc4 RCU hang mm spin_lock deadlock(?) after running libvirtd - reproducible.
Date: Sun, 24 Jan 2010 08:19:44 +0100 [thread overview]
Message-ID: <1264317584.6446.9.camel@marge.simson.net> (raw)
In-Reply-To: <4B5BE96A.8000304@majjas.com>
On Sun, 2010-01-24 at 01:32 -0500, Michael Breuer wrote:
> That commit solves my crash. Was my first time bisecting... thought I
> got it right. With the referenced commit, the system crashed when
> libvirtd was started, at the previous commit, it didn't crash.
> Regardless, the commit in tip fixes the issue. Hopefully it'll solve
> some of the other reported RCU hangs as well. Looks like the change for
> freshly cloned tasks is key.
Great, and yeah, the freshly cloned bit is the fix for your scenario.
-Mike
next prev parent reply other threads:[~2010-01-24 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 22:21 2.6.33RC3 Sky2 oops - Driver tries to sync DMA memory it has not allocated Michael Breuer
2010-01-10 20:10 ` 2.6.33RC3 libvirtd ->sky2 & rcu oops (was Sky2 oops - Driver tries to sync DMA memory it has not allocated) Michael Breuer
2010-01-12 1:49 ` Paul E. McKenney
2010-01-13 18:43 ` 2.6.33rc4 RCU hang mm spin_lock deadlock(?) after running libvirtd - reproducible Michael Breuer
2010-01-13 18:58 ` Paul E. McKenney
2010-01-24 2:49 ` Bisected rcu hang (kernel/sched.c): was " Michael Breuer
2010-01-24 5:59 ` Mike Galbraith
2010-01-24 6:32 ` Michael Breuer
2010-01-24 7:19 ` Mike Galbraith [this message]
2010-01-25 16:03 ` Peter Zijlstra
2010-01-25 16:14 ` Michael Breuer
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=1264317584.6446.9.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mbreuer@majjas.com \
--cc=paulmck@linux.vnet.ibm.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