From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus
Date: Mon, 10 May 2010 10:41:53 +0300 [thread overview]
Message-ID: <4BE7B8C1.9060807@redhat.com> (raw)
In-Reply-To: <4BE32178.2090103@msgid.tls.msk.ru>
On 05/06/2010 11:07 PM, Michael Tokarev wrote:
> There was a bug recently fixed in vnc code. Apparently
> there's something similar in the cirrus emulation as well.
> Here it triggers _always_ (including old versions of kvm)
> when running windows NT and hitting "test" button in its
> display resolution dialog. Here's what gdb is to say:
>
> Program received signal SIGFPE, Arithmetic exception.
> [Switching to Thread 0xf76cab70 (LWP 580)]
> 0x080c5e45 in cirrus_do_copy (s=0x86134dc, dst=960000, src=0, w=2, h=9)
> at hw/cirrus_vga.c:687
> 687 sx = (src % ABS(s->cirrus_blt_srcpitch)) / depth;
> (gdb) p depth
> $1 = 2
> (gdb) p s->cirrus_blt_srcpitch
> $2 = 0
>
>
> This qemu-kvm-0.12.3 - actually a debian package of it,
> but there's no patches relevant to video applied.
>
> Anything can be done with it?
Well, it's trivial to check for the condition, but how to handle it?
Need to find the spec for the chip.
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2010-05-10 7:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BE32178.2090103@msgid.tls.msk.ru>
2010-05-10 7:41 ` Avi Kivity [this message]
2010-05-10 8:15 ` [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus Avi Kivity
2010-05-12 12:20 ` Stefano Stabellini
2010-05-12 12:36 ` Avi Kivity
2010-05-12 13:45 ` Stefano Stabellini
2010-05-12 14:27 ` Avi Kivity
2010-05-12 15:57 ` Stefano Stabellini
2010-05-12 16:07 ` Avi Kivity
2010-05-12 16:55 ` Stefano Stabellini
2010-05-12 16:57 ` Avi Kivity
2010-05-12 17:07 ` Jamie Lokier
2010-05-12 18:11 ` Stefano Stabellini
2010-05-12 19:12 ` Michael Tokarev
2010-05-13 6:49 ` Avi Kivity
2010-05-13 13:48 ` Stefano Stabellini
2010-05-13 14:13 ` Michael Tokarev
2010-05-13 18:03 ` Stefano Stabellini
2010-05-13 16:04 ` Jamie Lokier
2010-05-28 20:51 ` Michael Tokarev
2010-05-30 8:24 ` Avi Kivity
2010-05-13 7:36 ` Paolo Bonzini
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=4BE7B8C1.9060807@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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).