From: "Jason S. Wagner" <jasonswagner@gmail.com>
To: kvm@vger.kernel.org
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 [thread overview]
Message-ID: <1394568102.2849.1@smtp.gmail.com> (raw)
In-Reply-To: <1394567978.2849.0@smtp.gmail.com>
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.
next parent reply other threads:[~2014-03-11 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394567978.2849.0@smtp.gmail.com>
2014-03-11 20:01 ` Jason S. Wagner [this message]
2014-03-12 14:08 ` Linux 3.13: BUG: soft lockup - CPU#1 stuck for 22s! [qemu-kvm:2653] Paolo Bonzini
2014-03-12 19:38 ` Jason S. Wagner
2014-04-14 8:06 ` Jason S. Wagner
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=1394568102.2849.1@smtp.gmail.com \
--to=jasonswagner@gmail.com \
--cc=kvm@vger.kernel.org \
/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).