From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 55201] host panic when "creating guest, doing scp and killing QEMU process" continuously
Date: Thu, 14 Mar 2013 02:57:30 +0000 (UTC) [thread overview]
Message-ID: <20130314025730.0981011FA28@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55201-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55201
--- Comment #1 from Jay Ren <yongjie.ren@intel.com> 2013-03-14 02:57:29 ---
also, I got some info in the console when this bug happens.
-------------
Message from syslogd@vt-snb9 at Mar 4 15:37:26 ...
kernel:BUG: soft lockup - CPU#15 stuck for 23s! [python:57408]
Message from syslogd@vt-snb9 at Mar 4 15:37:30 ...
kernel:BUG: soft lockup - CPU#4 stuck for 22s! [qemu-system-x86:57338]
Message from syslogd@vt-snb9 at Mar 4 15:38:02 ...
kernel:BUG: soft lockup - CPU#4 stuck for 21s! [qemu-system-x86:57338]
Message from syslogd@vt-snb9 at Mar 4 15:38:02 ...
kernel:BUG: soft lockup - CPU#15 stuck for 23s! [python:57408]
Message from syslogd@vt-snb9 at Mar 4 15:38:06 ...
kernel:BUG: soft lockup - CPU#6 stuck for 23s! [qemu-system-x86:57320]
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-03-14 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:54 [Bug 55201] New: host panic when "creating guest, doing scp and killing QEMU process" continuously bugzilla-daemon
2013-03-14 2:57 ` bugzilla-daemon [this message]
2013-03-14 2:58 ` [Bug 55201] " bugzilla-daemon
2013-03-14 10:37 ` bugzilla-daemon
2013-03-15 2:26 ` bugzilla-daemon
2013-03-15 2:27 ` bugzilla-daemon
2013-03-15 2:45 ` bugzilla-daemon
2013-03-18 13:02 ` bugzilla-daemon
2013-04-07 2:19 ` bugzilla-daemon
2013-04-07 2:19 ` bugzilla-daemon
2013-04-22 14:14 ` bugzilla-daemon
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=20130314025730.0981011FA28@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.