From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] ide-test fails on PPC64 big-endian host
Date: Fri, 25 Sep 2015 15:22:16 -0400 [thread overview]
Message-ID: <56059EE8.7030708@redhat.com> (raw)
In-Reply-To: <CAFEAcA9JnMnb_n25PDGOvy=3H_RYeQXLpX=Ms05VgYJzF+rfWw@mail.gmail.com>
On 09/25/2015 03:20 PM, Peter Maydell wrote:
> Hi. I was looking at adding ppc64be to the set of machines I do build
> tests on before merging patches, but right now "make check" fails on
> this host.
>
> ERROR:/home/pm215/qemu/tests/ide-test.c:721:cdrom_pio_impl: assertion
> failed ((data) & (DRQ | DRDY) == (DRQ | DRDY)): (0x00000040 ==
> 0x00000048)
> GTester: last random seed: R02S58b8c55d2bcc2ad0ddd605d5ce8483ee
> **
> ERROR:/home/pm215/qemu/tests/ide-test.c:721:cdrom_pio_impl: assertion
> failed ((data) & (DRQ | DRDY) == (DRQ | DRDY)): (0x00000040 ==
> 0x00000048)
> GTester: last random seed: R02S3bf67d6406a1f4ea5d8ca81bff345065
> **
> ERROR:/home/pm215/qemu/tests/ide-test.c:788:test_cdrom_dma: assertion
> failed (memcmp(pattern, rx, len) == 0): (1 == 0)
> GTester: last random seed: R02S2732ddb1755a1620a021eb6c59bd6281
>
> The obvious guess is that something in the IDE code or its test
> harness has an accidental little-endian dependency. Would anybody
> care to investigate? :-)
>
> thanks
> -- PMM
>
Sigh, sorry. I'm a habitual offender of breaking ppcBE with my IDE
tests. I'll fix it.
:(
prev parent reply other threads:[~2015-09-25 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 19:20 [Qemu-devel] ide-test fails on PPC64 big-endian host Peter Maydell
2015-09-25 19:22 ` John Snow [this message]
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=56059EE8.7030708@redhat.com \
--to=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).