From: Brendan Kirby <bkirby@mips.com>
To: Reed Kotler <rkotler@mips.com>,
afaerber@suse.de, qemu-devel@nongnu.org, khansa@kics.edu.pk,
rth@twiddle.net, rdsandiford@googlemail.com
Cc: ahatanaka@mips.com
Subject: Re: [Qemu-devel] Fwd: Re: [target-mips] qemu on centos
Date: Fri, 23 Dec 2011 10:05:48 -0800 [thread overview]
Message-ID: <1324663548.5778.3.camel@linux-bkirby.mips.com> (raw)
In-Reply-To: <4EF4B3C0.8030204@mips.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
Attached are three MIPS binaries that I have seen segfault
intermittently on CentOS 6 machines. Just run them with no arguments
several times.
Brendan
On Fri, 2011-12-23 at 09:00 -0800, Reed Kotler wrote:
>
> Please work with this guy.
>
> If possible, submit some test cases to them of some code that causes
> segfaults on Centos 6, even if intermittent.
>
> Reed
>
> -------- Original Message --------
> Subject:
> Re: [Qemu-devel] [target-mips] qemu
> on centos
> Date:
> Fri, 23 Dec 2011 14:25:57 +0100
> From:
> Andreas Färber <afaerber@suse.de>
> Organization:
> SUSE LINUX Products GmbH
> To:
> Reed Kotler <rkotler@mips.com>
> CC:
> <qemu-devel@nongnu.org>, Khansa
> Butt <khansa@kics.edu.pk>, Richard
> Henderson <rth@twiddle.net>,
> Richard Sandiford
> <rdsandiford@googlemail.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
[-- Attachment #2: ReedSolomon.mipsgcc --]
[-- Type: application/x-executable, Size: 16759 bytes --]
[-- Attachment #3: bisort.llc.mips32r2 --]
[-- Type: application/x-executable, Size: 12406 bytes --]
[-- Attachment #4: bisort.mipsgcc --]
[-- Type: application/x-executable, Size: 13350 bytes --]
next parent reply other threads:[~2011-12-23 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EF4B3C0.8030204@mips.com>
2011-12-23 18:05 ` Brendan Kirby [this message]
2011-12-23 22:57 ` [Qemu-devel] Fwd: Re: [target-mips] qemu on centos Stefan Weil
2011-12-23 23:21 ` Brendan Kirby
2011-12-23 23:27 ` [Qemu-devel] " Stefan Weil
2012-01-16 21:38 ` [Qemu-devel] Fwd: " Andreas Färber
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=1324663548.5778.3.camel@linux-bkirby.mips.com \
--to=bkirby@mips.com \
--cc=afaerber@suse.de \
--cc=ahatanaka@mips.com \
--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).