[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52E165B7.6020506@intel.com>
Date: Thu, 23 Jan 2014 10:55:51 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Toralf Förster <toralf.foerster@....de>,
Linux Kernel <linux-kernel@...r.kernel.org>
CC: kernel@...too.org, kvm@...r.kernel.org,
Gleb Natapov <gleb@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: 3.13 hangs when I tried to start a KVM at a 32 bit stable Gentoo
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.
Cc-ing a few more folks...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists