From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jason S. Wagner" <jasonswagner@gmail.com>
Subject: Re: Linux 3.13: BUG: soft lockup - CPU#1 stuck for 22s!
 [qemu-kvm:2653]
Date: Tue, 11 Mar 2014 19:54:42 -0007
Message-ID: <1394568102.2849.1@smtp.gmail.com>
References: <1394567978.2849.0@smtp.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-pa0-f43.google.com ([209.85.220.43]:50146 "EHLO
	mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755607AbaCKUBp (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 11 Mar 2014 16:01:45 -0400
Received: by mail-pa0-f43.google.com with SMTP id bj1so25940pad.30
        for <kvm@vger.kernel.org>; Tue, 11 Mar 2014 13:01:44 -0700 (PDT)
Received: from [192.168.1.50] (50-46-143-51.evrt.wa.frontiernet.net. [50.46.143.51])
        by mx.google.com with ESMTPSA id ha11sm114876pbd.17.2014.03.11.13.01.43
        for <kvm@vger.kernel.org>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 11 Mar 2014 13:01:43 -0700 (PDT)
In-Reply-To: <1394567978.2849.0@smtp.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi all,

Over the weekend, Linux 3.13.6 was installed on my machine. When I 
started gnome-boxes on Monday morning, my VM halted during boot. Only a 
portion of the VESA BIOS init output was displayed on-screen before the 
halt. Backtraces occasionally appeared in dmesg 
(http://pastebin.com/uUiNLmJ6). Some other programs were prevented from 
performing some tasks while the VM was running.

While investigating, I was directed to an earlier KVM bug report 
(https://lkml.org/lkml/2014/2/11/487). I downgraded to Linux 3.12.9 and 
rebooted, and now my VM is starting. Unfortunately, I'm very new to 
Linux, so I'm not sure what the next steps would be.

Host system info:
Arch Linux (current with updates), 64-bit with UEFI boot
Intel Haswell CPU (i5-4670K)
32GB RAM
Intel 240GB SSD
GNOME 3.10.x
gnome-boxes 3.10.x

Guest OS info:
Windows 7, 64-bit
2GB of RAM allocated
Beyond setting disk and RAM sizes when initializing the VM, I have 
trusted the gnome-boxes defaults and have not altered the machine 
configuration in any way.

Let me know if there is any additional logging that would be useful. I 
can certainly re-install the problematic kernel outside of business 
hours.