From: Gleb Natapov <gleb@redhat.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: kvm@vger.kernel.org
Subject: Re: qemu-kvm-1.1.0 crashing with kernel 3.5.0-rc6
Date: Wed, 11 Jul 2012 10:22:55 +0300 [thread overview]
Message-ID: <20120711072255.GH23898@redhat.com> (raw)
In-Reply-To: <4FFD28B9.9040604@googlemail.com>
On Wed, Jul 11, 2012 at 08:18:17AM +0100, Chris Clayton wrote:
> On 07/11/12 08:12, Gleb Natapov wrote:
> >On Wed, Jul 11, 2012 at 08:09:42AM +0100, Chris Clayton wrote:
> >>Ping.
> >>
> >>Have I committed a bug-reporting sin in the mail below or is
> >>everyone simply too busy to look at this kvm-related crash?
> >>
> >Since you have good and bad points can you bisect the problem?
> >
>
> Yes, I can bisect, but since the crash occurs with only only one
> combination of qemu-kvm (1.1.0) and kernel (3.5.0-rc6), I'm not sure
> which of those I should bisect. Any ideas on how I could narrow that
> down.
>
Bisect qemu between qemu-kvm-1.0.1 & qemu-kvm-1.1.0.
> Thanks.
> >>On 07/09/12 11:57, Chris Clayton wrote:
> >>>Hi,
> >>>
> >>>When I run WinXP SP3 through qemu-kvm-1.1.0 on linux kernel 3.5.0-rc6, I
> >>>get a segmentation fault within 3 or 4 minutes maximum. In dmesg I see:
> >>>
> >>>qemu-kvm: sending ioctl 5326 to a partition!
> >>>qemu-kvm: sending ioctl 801c0204 to a partition!
> >>>qemu-kvm: sending ioctl 5326 to a partition!
> >>>qemu-kvm: sending ioctl 801c0204 to a partition!
> >>>qemu-kvm: sending ioctl 5326 to a partition!
> >>>qemu-kvm: sending ioctl 801c0204 to a partition!
> >>>qemu-kvm: sending ioctl 5326 to a partition!
> >>>qemu-kvm: sending ioctl 801c0204 to a partition!
> >>>qemu-kvm[860] general protection ip:b6abad77 sp:b52ff09c error:0 in
> >>>libc-2.16.so[b697d000+1b4000]
> >>>
> >>>The crash does not occur with qemu-kvm-1.0.1 on rc6. Nor does it occur
> >>>qemu-kvm-1.0.1 or qemu-kvm-1.1.0 on kernel 3.4.4. All three combinations
> >>>survive for 15 minutes or more
> >>>
> >>>When I try to get a backtrace with gdb, the screen on which konsole and
> >>>qemu are running locks up until I kill qemu in another console.
> >>>Consequently I can't get a full BT, but, although probably not very
> >>>helpful, what I did get is:
> >>>
> >>>Program received signal SIGSEGV, Segmentation fault.
> >>>[Switching to Thread 0xb6946b40 (LWP 506)]
> >>>0xb7705d77 in __strcmp_sse4_2 () from /lib/libc.so.6
> >>>(gdb) bt
> >>>#0 0xb7705d77 in __strcmp_sse4_2 () from /lib/libc.so.6
> >>>#1 0xb7e8d6e3 in g_str_equal () from /usr/lib/libglib-2.0.so.0
> >>>#2 0xb7e8c94c in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
> >>>Cannot access memory at address 0xb694610c
> >>>(gdb)
> >>>
> >>>Note that the gdb and dmesg outputs above are not from the same crash
> >>>instance.
> >>>
> >>>I'm not subscribed,so please cc me on any reply.
> >>>
> >>>Happy to provide any additional diagnostics (but may need help on how to
> >>>get them) or test patches, etc
> >>>
> >>>Thanks
> >>>
> >>>Chris Clayton
> >>
> >>
> >>--
> >>To unsubscribe from this list: send the line "unsubscribe kvm" in
> >>the body of a message to majordomo@vger.kernel.org
> >>More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> >--
> > Gleb.
> >
>
--
Gleb.
next prev parent reply other threads:[~2012-07-11 7:22 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 [this message]
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
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=20120711072255.GH23898@redhat.com \
--to=gleb@redhat.com \
--cc=chris2553@googlemail.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).