BUG: Soft Lockup - CPU#0 stuck for 22s! [qemu-system-x86: 31867]
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| QEMU |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Environment:
-------------------
* Upstream git version: qemu-kvm-
* 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-
* Qemu-command line:
/usr/local/
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 syslogd@phx3 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

Thanks for the bug report, but please report kernel bugs in the kernel bug tracker, not in the QEMU bug tracker (see http:// www.linux- kvm.org/ page/Bugs for details). So if the problem still persists with recent kernels, you should open a ticket there instead.