From: Aurelien Jarno <aurelien@aurel32.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] 'tcg fatal error' with qemu v2.6.0-rc3 (bisected)
Date: Wed, 27 Apr 2016 08:57:24 +0200 [thread overview]
Message-ID: <20160427065724.GA24455@aurel32.net> (raw)
In-Reply-To: <20160427031211.GA15548@roeck-us.net>
On 2016-04-26 20:12, Guenter Roeck wrote:
> Hi,
>
> when running qemu version 2.6.0-rc3, I get the following error message.
>
> /opt/buildbot/qemu/qemu/tcg/tcg.c:1769: tcg fatal error
>
> qemu command line is as follows.
>
> qemu-system-ppc64 -M mpc8544ds \
> -cpu e5500 \
> -m 1024 -kernel arch/powerpc/boot/uImage -initrd busybox-ppc.cpio \
> -nographic -vga none -monitor null -no-reboot \
> --append "rdinit=/sbin/init console=tty console=ttyS0" \
> -machine "dt_compatible=fsl,,P5020DS"
>
> Files are from my test suite at https://github.com/groeck/linux-build-test.
I have try to reproduce the issue with a kernel build with my toolchain
and your defconfig, but it worked for me. Could you please share the
binaries so that it is easier to reproduce the issue?
> Bisect points to commit 40ae5c62ebaaf7d9d3b93b88c2d32bf6342f7889 ("tcg:
> Introduce temp_load"). Bisect log is attached.
I look at this patch again quickly, and I don't think the bug is
actually introduced by this commit, it is just that it does more strict
tests on the value. I guess it was working before by chance by loading
a random value into the register. That said to look deeper into it, it
would be better to be able to reproduce the issue.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2016-04-27 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 3:12 [Qemu-devel] 'tcg fatal error' with qemu v2.6.0-rc3 (bisected) Guenter Roeck
2016-04-27 6:57 ` Aurelien Jarno [this message]
2016-04-27 13:27 ` Guenter Roeck
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=20160427065724.GA24455@aurel32.net \
--to=aurelien@aurel32.net \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.org \
--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).