From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org, agraf@suse.de, qemu-ppc@nongnu.org
Subject: [Qemu-devel] ppc64-linux-user broken since "PPC: Unify dcbzl code path" ?
Date: Mon, 22 Apr 2013 09:37:13 +0300 [thread overview]
Message-ID: <20130422063713.GA12462@afflict.kos.to> (raw)
Hi,
While testing my linux-user smoke-testing setup, I noticed that
with current qemu head:
./ppc64-linux-user/qemu-ppc64 ../../qemu-smoke/ppc64/busybox ls
busybox: malloc.c:3096: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted (core dumped)
With a bisect run, the following commit appear breaks this:
8e33944f8c648e579a2827ae6f30e4d66ee87f96
PPC: Unify dcbzl code path
Indeed, after reverting the same command runs fine.
./ppc64-linux-user/qemu-ppc64 ../../qemu-smoke/ppc64/busybox ls
Makefile coroutine-ucontext.d qapi-generated
....
The same commit appears to break running 32bit static busybox with qemu-ppc64abi32,
But I guess I am supposed to use qemu-ppc instead (which works both before and
after the commit).
The static busybox binary is from debian/ppc64,
BusyBox v1.20.2 (Debian 1:1.20.0-6) multi-call binary.
I've also uploaded it to:
http://people.linaro.org/~riku.voipio/busyboxen.tgz
Riku
next reply other threads:[~2013-04-22 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 6:37 Riku Voipio [this message]
2013-04-26 6:56 ` [Qemu-devel] ppc64-linux-user broken since "PPC: Unify dcbzl code path" ? Alexander Graf
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=20130422063713.GA12462@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=agraf@suse.de \
--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).