[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1004408] Re: BUG: Soft Lockup - CPU#0 stuck for 22s! [
From: |
Prem Karat |
Subject: |
[Qemu-devel] [Bug 1004408] Re: BUG: Soft Lockup - CPU#0 stuck for 22s! [qemu-system-x86: 31867] |
Date: |
Fri, 25 May 2012 09:48:06 -0000 |
** Attachment added: "screenshot.tgz"
https://bugs.launchpad.net/bugs/1004408/+attachment/3162361/+files/screenshot.tgz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1004408
Title:
BUG: Soft Lockup - CPU#0 stuck for 22s! [qemu-system-x86: 31867]
Status in QEMU:
New
Bug description:
Environment:
-------------------
* Upstream git version: qemu-kvm-1.1-rc2-4-g3fd9fed
* Host Kernel: Mainline Kernel - 3.4.0 x86_64 GNU/Linux (Arch: x86_64)
* CPU model: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz
* Guest OS: Red Hat Enterprise Linux Server release 6.2
* Guest Kernel: 2.6.32-220.el6.x86_64
* Qemu-command line:
/usr/local/bin/qemu-system-x86_64 -name 'vm1' -nodefaults -monitor
unix:'/tmp/monitor-humanmonitor1-20120525-214210-Zua6',server,nowait -serial
unix:'/tmp/serial-20120525-214210-Zua6',server,nowait -device
ich9-usb-uhci1,id=usb1 -drive
file='/tmp/kvm_autotest_root/images/rhel62-64.qcow2',index=0,if=ide,cache=none
-device rtl8139,netdev=idvVySvg,mac='9a:6d:16:b9:b5:06',id='idiX1NmG' -netdev
tap,id=idvVySvg,fd=21 -m 7198 -smp 2 -device
usb-tablet,id=usb-tablet1,bus=usb1.0 -vnc :0 -vga std
The qemu is started through autotest.
Description:
-----------------
While running the cgroup test through autotest, the host was hung and
was not responding. When viewed through serial console, found the
error "BUG: Soft lockup" error as attached in the screenshot 1.
There are no errors displayed in /var/log/messages (no call trace) and in
dmesg.*
There is a call trace seen in serial console, which is show in screenshot 2.
Steps to reproduce:
----------------------------
Currently am not able to consistently reproduce this error. However when I
tried to reproduce it again by running the cgroup test, found another error
from syslogd as shown below
"Message from address@hidden at May 25 21:56:04 ...
kernel:Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 3"
So this time I got a hard Lockup error. Attached is the screenshot of
the same. (screenshot-3, see the message at the bottom of the screen).
This time the cgroup test had completed.
Please let me know if you require more info on this.
-prem
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1004408/+subscriptions
- [Qemu-devel] [PULL 00/10] Block patches for 1.1, Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 01/10] qcow2: don't leak buffer for unexpected qcow_version in header, Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 02/10] qemu-img: Explain how rebase operation can be used to perform a 'diff' operation., Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 03/10] sheepdog: mark image as snapshot when tag is specified, Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 04/10] sheepdog: return -errno on error, Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 06/10] qcow2: Check qcow2_alloc_clusters_at() return value, Kevin Wolf, 2012/05/25
- [Qemu-devel] [PATCH 05/10] sheepdog: use heap instead of stack for BDRVSheepdogState, Kevin Wolf, 2012/05/25