From: "Andreas Färber" <afaerber@suse.de>
To: Reed Kotler <rkotler@mips.com>
Cc: Richard Sandiford <rdsandiford@googlemail.com>,
Khansa Butt <khansa@kics.edu.pk>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [target-mips] qemu on centos
Date: Fri, 23 Dec 2011 14:25:57 +0100 [thread overview]
Message-ID: <4EF48165.20905@suse.de> (raw)
In-Reply-To: <4EF477A1.2070205@mips.com>
Hi,
Am 23.12.2011 13:44, schrieb Reed Kotler:
> We have been seeing various problems running qemu for MIPS target on
> Centos 5.
> We are running linux user mode programs.
>
> Qemu segfaults.
>
> We recently tried upgrading to Centos 6 and the problem there is much
> worse, making it basically unusable.
>
> The same programs have no problem when running on Ubuntu.
They likely are using different QEMU versions, and distros may have
different patches applied on top.
Please provide some more info on what version, what ABI (which
executable), what -cpu parameter (if any), etc. you are using. Does a
gdb backtrace indicate any QEMU function or is it from translated code?
For n64 there were some patches in need of testing, review and fixing.
[cc'ing Khansa]
For n32 there's signal handling missing. (openSUSE for one ignores the
build warning and provides it non the less.)
No known issues specific to o32 that I'm aware of, but the two Richards
had patches for some instructions. Shouldn't lead to segfaults though.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2011-12-23 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 12:44 [Qemu-devel] qemu on centos Reed Kotler
2011-12-23 13:25 ` Andreas Färber [this message]
[not found] <4EF4B3C0.8030204@mips.com>
2011-12-23 18:05 ` [Qemu-devel] Fwd: Re: [target-mips] " Brendan Kirby
2011-12-23 22:57 ` Stefan Weil
2011-12-23 23:27 ` [Qemu-devel] " Stefan Weil
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=4EF48165.20905@suse.de \
--to=afaerber@suse.de \
--cc=khansa@kics.edu.pk \
--cc=qemu-devel@nongnu.org \
--cc=rdsandiford@googlemail.com \
--cc=rkotler@mips.com \
--cc=rth@twiddle.net \
/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).