From: Cole Robinson <crobinso@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: qemu-devel@nongnu.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] sending SEGV to qemu crashes host kernel in Fedora 19
Date: Tue, 09 Jul 2013 08:26:22 -0400 [thread overview]
Message-ID: <51DC016E.9070900@redhat.com> (raw)
In-Reply-To: <CAPM=9tzT3EaZm=BRxxQe8+u-VtE8_F72-6X9ZJbLgnX7XMV7Vw@mail.gmail.com>
On 07/08/2013 09:11 PM, Dave Airlie wrote:
> On Tue, Jul 9, 2013 at 10:35 AM, Dave Airlie <airlied@gmail.com> wrote:
>> Hi,
>>
>> F19
>> kernel-3.9.8-300.fc19.x86_64
>> qemu-kvm-1.4.2-4.fc19.x86_64
>>
>> If I start a complete F19 install in the guest and send the qemu
>> process a SEGV signal, the host kernel starts giving me random kmalloc
>> errors soon after, if I send a normal kill signal things seem fine.
>>
>> CPU is Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, on a HP 220z workstation.
>>
>> I initially blamed bad RAM but this reproduces everytime, and I
>> swapped DIMMs around
>>
>> I haven't tested with upstream kernel/qemu yet, but I wondered if
>> anyone else has seen this.
>>
>> I noticed this because some work I was doing was segfaulting my qemu
>> and then my machine would die a few mins later.
>
> Of course now I read my fedora kernel emails and notice vhost_net does
> bad things,
>
> disabling vhost_net seems to make it work fine, hopefully the next
> Fedora kernel will bring the magic fixes.
>
That issue and another nasty crasher are being tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=980254
- Cole
prev parent reply other threads:[~2013-07-09 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 0:35 [Qemu-devel] sending SEGV to qemu crashes host kernel in Fedora 19 Dave Airlie
2013-07-09 1:11 ` Dave Airlie
2013-07-09 11:24 ` Josh Boyer
2013-07-09 12:26 ` Cole Robinson [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=51DC016E.9070900@redhat.com \
--to=crobinso@redhat.com \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).