From: "Christopher M. Penalver" <christopher.m.penalver@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 977391] Re: BUG: soft lockup - CPU#8 stuck for 61s! [kvm:*] in lucid
Date: Mon, 02 Sep 2013 13:58:33 -0000 [thread overview]
Message-ID: <20130902135834.30404.69760.malone@gac.canonical.com> (raw)
In-Reply-To: 20120409175510.18682.56652.malonedeb@wampee.canonical.com
Rahul, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest server release of
Ubuntu? ISO images are available from http://releases.ubuntu.com/raring/
.
If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:
apport-collect -p linux <replace-with-bug-number>
Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER
where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc7
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing
If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER
As well, please remove the tag:
needs-upstream-testing
Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.
** Tags added: needs-kernel-logs needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/977391
Title:
BUG: soft lockup - CPU#8 stuck for 61s! [kvm:*] in lucid
Status in QEMU:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Status in “qemu-kvm” package in Ubuntu:
Confirmed
Bug description:
Two days back my KVM base machine got hung up all of a sudden.
Not sure what exactly happened.
cat /proc/version_signature
Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12
-Rahul N.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/977391/+subscriptions
next prev parent reply other threads:[~2013-09-02 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120409175510.18682.56652.malonedeb@wampee.canonical.com>
2012-05-07 3:41 ` [Qemu-devel] [Bug 977391] Re: BUG: soft lockup - CPU#8 stuck for 61s! [kvm:*] in lucid arun gathiya
2013-09-02 13:58 ` Christopher M. Penalver [this message]
2016-10-24 21:34 ` Thomas Huth
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=20130902135834.30404.69760.malone@gac.canonical.com \
--to=christopher.m.penalver@gmail.com \
--cc=977391@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.