From: Avi Kivity <avi@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Adam Huffman <adam.huffman.lkml@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter@vger.kernel.org
Subject: Re: KVM related crash
Date: Sun, 13 Dec 2009 12:15:24 +0200 [thread overview]
Message-ID: <4B24BEBC.2020207@redhat.com> (raw)
In-Reply-To: <20091212191101.669ba881.akpm@linux-foundation.org>
On 12/13/2009 05:11 AM, Andrew Morton wrote:
> (networking cc's added)
>
> On Wed, 9 Dec 2009 14:00:04 +0000 Adam Huffman<adam.huffman.lkml@gmail.com> wrote:
>
>
>> Have seen multiple crashes on a new Dell Precision T7500 workstation,
>> seemingly related to KVM:
>>
> Looks like a networking crash to me - that CPU just happened to be
> running some KVM code when the interrupt happened.
>
Yes - and I've seen a similar report earlier (also with kvm).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-12-13 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ec55d96f0912090600u4ff02e06m1506530d4161f280@mail.gmail.com>
2009-12-13 3:11 ` KVM related crash Andrew Morton
2009-12-13 10:15 ` Avi Kivity [this message]
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=4B24BEBC.2020207@redhat.com \
--to=avi@redhat.com \
--cc=adam.huffman.lkml@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).