From: Dave Hansen <dave.hansen@intel.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Cc: kernel@gentoo.org, kvm@vger.kernel.org,
Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 3.13 hangs when I tried to start a KVM at a 32 bit stable Gentoo
Date: Thu, 23 Jan 2014 11:33:23 -0800 [thread overview]
Message-ID: <52E16E83.6060301@intel.com> (raw)
In-Reply-To: <52E165B7.6020506@intel.com>
On 01/23/2014 10:55 AM, Dave Hansen wrote:
> On 01/21/2014 08:38 AM, Toralf Förster wrote:
>> Jan 21 17:18:57 n22 kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=60001 jiffies g=18494 c=18493 q=183951)
>> Jan 21 17:18:57 n22 kernel: sending NMI to all CPUs:
>> Jan 21 17:18:57 n22 kernel: NMI backtrace for cpu 2
>> Jan 21 17:18:57 n22 kernel: CPU: 2 PID: 6779 Comm: qemu-system-x86 Not tainted 3.13.0 #3
>> Jan 21 17:18:57 n22 kernel: Hardware name: LENOVO 4180F65/4180F65, BIOS 83ET75WW (1.45 ) 05/10/2013
>> Jan 21 17:18:57 n22 kernel: task: e921c370 ti: e5f36000 task.ti: e5f36000
>
> I'm seeing a very similar hang with an ubuntu guest and a custom kernel.
> I'm on commit 0dc3fd0249a, and it's 100% reproducible every time I run KVM.
Did a little more LKML digging and found this:
http://marc.info/?l=linux-kernel&m=139038631607917&q=raw
Peter's fix works for me. I'm also running a CONFIG_PREEMPT_VOLUNTARY=y
config.
next prev parent reply other threads:[~2014-01-23 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52DEA270.60803@gmx.de>
2014-01-23 18:55 ` 3.13 hangs when I tried to start a KVM at a 32 bit stable Gentoo Dave Hansen
2014-01-23 19:33 ` Dave Hansen [this message]
2014-01-23 19:50 ` Toralf Förster
2014-01-24 12:36 ` Paolo Bonzini
2014-01-25 9:48 ` Toralf Förster
2014-01-26 10:40 ` Toralf Förster
2014-02-09 16:38 ` Toralf Förster
2014-02-08 8:30 ` Toralf Förster
2014-02-24 20:39 ` Toralf Förster
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=52E16E83.6060301@intel.com \
--to=dave.hansen@intel.com \
--cc=gleb@kernel.org \
--cc=kernel@gentoo.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=toralf.foerster@gmx.de \
/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).