From: Avi Kivity <avi@redhat.com>
To: Nate Custer <nate@cpanel.net>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: kvm deadlock
Date: Wed, 14 Dec 2011 16:28:49 +0200 [thread overview]
Message-ID: <4EE8B2A1.8060603@redhat.com> (raw)
In-Reply-To: <7E2A4D2C-68BD-47E8-8079-37AE152D77B4@cpanel.net>
On 12/14/2011 04:17 PM, Nate Custer wrote:
> On Dec 14, 2011, at 8:06 AM, Marcelo Tosatti wrote:
> > I don't know. Its a hang ? It could be memory corruption (of the timer
> > olist) instead of a bogus NMI actually, the second.
>
>
> What is pasted in the second paste is what came scrolling across the console right before the end of all responsiveness. It came from a dmesg dump, the next dmesg command was not accepted via ssh and the console attached showed the same stack trace. At that point the system refused to respond to any direct keyboard input, including the SysRq commands that I expected to work after a core dump.
>
> The issue happened with two servers (same hardware, same build group so there is a chance of a bad hardware batch). Switching to an older kernel/kvm setup in RHEL 6.2 has corrected the issue, which suggests a software issue to me.
>
If you can, please set up netconsole, which should give us complete
dmesg captures.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-14 14:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:48 kvm deadlock Nate Custer
2011-12-14 12:25 ` Marcelo Tosatti
2011-12-14 13:43 ` Avi Kivity
2011-12-14 14:00 ` Marcelo Tosatti
2011-12-14 14:02 ` Avi Kivity
2011-12-14 14:06 ` Marcelo Tosatti
2011-12-14 14:17 ` Nate Custer
2011-12-14 14:20 ` Marcelo Tosatti
2011-12-14 14:28 ` Avi Kivity [this message]
2011-12-14 14:27 ` Avi Kivity
2011-12-14 16:03 ` Jens Axboe
2011-12-14 17:03 ` Vivek Goyal
2011-12-14 17:09 ` Jens Axboe
2011-12-14 17:22 ` Vivek Goyal
2011-12-14 18:16 ` Tejun Heo
2011-12-14 18:41 ` Vivek Goyal
2011-12-14 23:06 ` Vivek Goyal
2011-12-15 19:47 ` [RFT PATCH] blkio: alloc per cpu data from worker thread context( Re: kvm deadlock) Vivek Goyal
[not found] ` <E73DB38E-AFC5-445D-9E76-DE599B36A814@cpanel.net>
2011-12-16 20:29 ` Vivek Goyal
2011-12-18 21:25 ` Nate Custer
2011-12-19 13:40 ` Vivek Goyal
2011-12-19 17:27 ` Vivek Goyal
2011-12-19 17:35 ` Tejun Heo
2011-12-19 18:27 ` Vivek Goyal
2011-12-19 22:56 ` Tejun Heo
2011-12-20 14:50 ` Vivek Goyal
2011-12-20 20:45 ` Tejun Heo
2011-12-20 12:49 ` Jens Axboe
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=4EE8B2A1.8060603@redhat.com \
--to=avi@redhat.com \
--cc=axboe@kernel.dk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nate@cpanel.net \
/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.