From: Avi Kivity <avi@redhat.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: qemu-kvm-1.1.0 crashing with kernel 3.5.0-rc6
Date: Thu, 26 Jul 2012 15:07:07 +0300 [thread overview]
Message-ID: <501132EB.6060705@redhat.com> (raw)
In-Reply-To: <501130CF.5050207@googlemail.com>
On 07/26/2012 02:58 PM, Chris Clayton wrote:
>> It looks like general memory corruption. Is this repeatable? What's
>> the guest uptime when it happens (i.e. is it immediate?)
>
> I've just done 10 runs of WinXP SP3 and 5 of them crashed. Three crashed
> early as XP was starting up - well before the desktop would have
> appeared. The other two crashed as XP was closing down, having been
> running for a few minutes (but not doing much).
>
> The error messages seen through dmesg are:
>
> qemu-kvm[12778] general protection ip:b6c43d77 sp:b5e800fc error:0 in
> libc-2.16.so[b6b06000+1b4000]
> qemu-kvm[12813] general protection ip:b6bf6d77 sp:b54ff0fc error:0 in
> libc-2.16.so[b6ab9000+1b4000]
> qemu-kvm[12986] general protection ip:b6cd3d77 sp:b55ff0fc error:0 in
> libc-2.16.so[b6b96000+1b4000]
> qemu-kvm[13045] general protection ip:b6c91d77 sp:b54ff0fc error:0 in
> libc-2.16.so[b6b54000+1b4000]
> qemu-kvm[13225] general protection ip:b6c5bd77 sp:b54ff0fc error:0 in
> libc-2.16.so[b6b1e000+1b4000]
>
> The other 5 were OK, although I only did a bit of web browsing for few
> minutes with IE.
Failures always in the same place (I'm guess the variations are due to
PIE -- please configure with --disable-pie for future tests).
Please generate a core and look around, esp. in frame 3
(type_table_lookup). Also try to dissect type_table (you may need to
install the glib debug symbols for this).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-26 12:07 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 10:57 qemu-kvm-1.1.0 crashing with kernel 3.5.0-rc6 Chris Clayton
2012-07-11 7:09 ` Chris Clayton
2012-07-11 7:12 ` Gleb Natapov
2012-07-11 7:18 ` Chris Clayton
2012-07-11 7:22 ` Gleb Natapov
2012-07-15 19:52 ` Chris Clayton
2012-07-19 12:14 ` Chris Clayton
2012-07-19 12:17 ` Avi Kivity
2012-07-19 18:23 ` Chris Clayton
2012-07-26 9:52 ` Chris Clayton
2012-07-26 10:01 ` Avi Kivity
2012-07-26 10:29 ` Jan Kiszka
2012-07-26 10:45 ` Avi Kivity
2012-07-26 10:49 ` Jan Kiszka
2012-07-26 11:04 ` Jan Kiszka
2012-07-26 11:58 ` Chris Clayton
2012-07-26 12:07 ` Avi Kivity [this message]
2012-07-26 23:22 ` Chris Clayton
2012-07-27 10:46 ` Chris Clayton
[not found] ` <CAG7+5M2y8gJvDCNuWsSB3zH=r75H0Mn=JNV+4DBc5xYjM+BJWA@mail.gmail.com>
2012-07-27 19:04 ` Chris Clayton
2012-07-29 12:42 ` Avi Kivity
2012-07-29 14:03 ` Chris Clayton
2012-07-29 14:18 ` Avi Kivity
2012-07-29 14:48 ` Avi Kivity
2012-07-29 15:21 ` Chris Clayton
2012-07-29 15:47 ` Avi Kivity
2012-07-29 16:34 ` Avi Kivity
2012-07-29 17:50 ` Chris Clayton
2012-07-29 17:54 ` Gleb Natapov
2012-07-29 19:10 ` Chris Clayton
2012-07-30 14:00 ` Chris Clayton
2012-07-30 14:03 ` Avi Kivity
2012-07-30 14:07 ` Chris Clayton
2012-07-30 16:39 ` Avi Kivity
2012-07-30 23:36 ` Marcelo Tosatti
2012-07-31 9:11 ` Avi Kivity
2012-07-31 16:29 ` Marcelo Tosatti
2012-07-31 16:46 ` Avi Kivity
2012-08-01 13:11 ` Avi Kivity
2012-07-26 12:09 ` Jan Kiszka
2012-07-26 11:10 ` Xiao Guangrong
2012-07-26 13:49 ` Chris Clayton
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=501132EB.6060705@redhat.com \
--to=avi@redhat.com \
--cc=chris2553@googlemail.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--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 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).