From: Aurelien Jarno <aurelien@aurel32.net>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] tcg/tcg.c:1892: tcg fatal error
Date: Sun, 10 Apr 2011 15:24:15 +0200 [thread overview]
Message-ID: <20110410132415.GA6719@volta.aurel32.net> (raw)
In-Reply-To: <BANLkTi=NRjw8Md+PU+JcvkZ-cTeJO+zP-A@mail.gmail.com>
On Sun, Apr 10, 2011 at 02:29:59PM +0200, Artyom Tarasenko wrote:
> Trying to boot some proprietary OS I get qemu-system-sparc64 crash with a
>
> tcg/tcg.c:1892: tcg fatal error
>
> error message.
>
> It looks like it can be a platform independent bug though, because
> when a '-singlestep' option IS present, qemu doesn't crash and seems
> to translate the code properly.
>
> (gdb) bt
> #0 0x00000032c2e327f5 in raise () from /lib64/libc.so.6
> #1 0x00000032c2e33fd5 in abort () from /lib64/libc.so.6
> #2 0x000000000051933d in tcg_reg_alloc_call (s=<value optimized out>,
> def=0x89d340, opc=INDEX_op_call, args=0x10acc98, dead_iargs=3) at
> qemu/tcg/tcg.c:1892
> #3 0x000000000051a557 in tcg_gen_code_common (s=0x10b8940,
> gen_code_buf=0x40338b60 "I\213n@H\213] 3\355I\211\256\220") at
> qemu/tcg/tcg.c:2099
> #4 tcg_gen_code (s=0x10b8940, gen_code_buf=0x40338b60 "I\213n@H\213]
> 3\355I\211\256\220") at qemu/tcg/tcg.c:2142
> #5 0x00000000004d38f1 in cpu_sparc_gen_code (env=0x10cce10,
> tb=0x7fffe91bc218, gen_code_size_ptr=0x7fffffffd9b4) at
> qemu/translate-all.c:93
> #6 0x00000000004d1fd7 in tb_gen_code (env=0x10cce10, pc=18868776,
> cs_base=18868780, flags=15, cflags=0) at qemu/exec.c:989
> #7 0x00000000004d4029 in tb_find_slow (env1=<value optimized out>) at
> qemu/cpu-exec.c:167
> #8 tb_find_fast (env1=<value optimized out>) at cpu-exec.c:194
> #9 cpu_sparc_exec (env1=<value optimized out>) at qemu/cpu-exec.c:556
> #10 0x0000000000408868 in tcg_cpu_exec () at qemu/cpus.c:1066
> #11 cpu_exec_all () at qemu/cpus.c:1102
> #12 0x000000000053c756 in main_loop (argc=<value optimized out>,
> argv=<value optimized out>, envp=<value optimized out>) at
> qemu/vl.c:1430
>
> I inspected ts->val_type causing the abort() case and it turned out to be 0.
>
> The last lines of qemu.log (without -singlestep)
> IN:
> 0x00000000011fe9f0: rdpr %pstate, %g1
> 0x00000000011fe9f4: wrpr %g1, 2, %pstate
> --------------
> IN:
> 0x00000000011fe9f8: ldub [ %o0 ], %o1
> 0x00000000011fe9fc: mov %o1, %o2
> 0x00000000011fea00: rdpr %tick, %o3
> 0x00000000011fea04: cmp %o1, %o2
> 0x00000000011fea08: be %icc, 0x11fea00
> 0x00000000011fea0c: ldub [ %o0 ], %o2
>
> Search PC...
> Search PC...
> Search PC...
> Search PC...
> Search PC...
> Search PC...
> --------------
> IN:
> 0x00000000011fe9f8: ldub [ %o0 ], %o1
> 0x00000000011fe9fc: mov %o1, %o2
> 0x00000000011fea00: rdpr %tick, %o3
> 0x00000000011fea04: cmp %o1, %o2
> 0x00000000011fea08: be %icc, 0x11fea00
> 0x00000000011fea0c: ldub [ %o0 ], %o2
>
> 110521: Data Access MMU Miss (v=0068) pc=00000000011fe9f8
> npc=00000000011fe9fc SP=000000000180ae41
> pc: 00000000011fe9f8 npc: 00000000011fe9fc
>
> IN:
> 0x00000000011fea00: rdpr %tick, %o3
> 0x00000000011fea04: cmp %o1, %o2
> 0x00000000011fea08: be %icc, 0x11fea00
> 0x00000000011fea0c: ldub [ %o0 ], %o2
> --------------
> IN:
> 0x00000000011fea10: brz,pn %o2, 0x11fe9f8
> 0x00000000011fea14: mov %o2, %o4
> --------------
> IN:
> 0x00000000011fea18: rdpr %tick, %o5
> 0x00000000011fea1c: cmp %o2, %o4
> 0x00000000011fea20: be %icc, 0x11fea18
> 0x00000000011fea24: ldub [ %o0 ], %o4
> --------------
> IN:
> 0x00000000011fea28: brz,pn %o4, 0x11fe9f4
> 0x00000000011fea2c: wrpr %g0, %g1, %pstate
> <EOF>
>
> The crash is 100% reproducible and happens always on the same place,
> so it's probably a pure TCG issue, not related on getting the
> external/timer interrupts.
>
> Do you need any additional info?
>
What would be interesting would be to get the corresponding TCG code
from qemu.log (-d op,op_opt).
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2011-04-10 13:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 12:29 [Qemu-devel] tcg/tcg.c:1892: tcg fatal error Artyom Tarasenko
2011-04-10 13:24 ` Aurelien Jarno [this message]
2011-04-10 14:09 ` Artyom Tarasenko
2011-04-10 14:44 ` Blue Swirl
2011-04-10 17:48 ` Artyom Tarasenko
2011-04-10 17:57 ` Blue Swirl
2011-04-10 18:35 ` Artyom Tarasenko
2011-04-10 18:52 ` Igor Kovalenko
2011-04-10 19:37 ` Artyom Tarasenko
[not found] ` <BANLkTik2NChYi8hADjCSbjdZeyP_oo8_Qg@mail.gmail.com>
2011-04-10 20:00 ` Artyom Tarasenko
2011-04-11 3:16 ` Igor Kovalenko
2011-04-11 17:53 ` Artyom Tarasenko
2011-04-12 2:14 ` Igor Kovalenko
2011-04-21 14:57 ` Artyom Tarasenko
2011-04-21 15:44 ` Laurent Desnogues
2011-04-21 19:45 ` Igor Kovalenko
2011-04-21 22:39 ` Laurent Desnogues
2011-04-22 14:14 ` Igor Kovalenko
2011-04-25 20:29 ` Aurelien Jarno
2011-04-26 3:34 ` Igor Kovalenko
2011-04-26 16:26 ` Artyom Tarasenko
2011-04-26 18:07 ` Igor Kovalenko
2011-04-26 17:02 ` Artyom Tarasenko
2011-04-26 18:36 ` Blue Swirl
2011-04-26 19:07 ` Igor Kovalenko
2011-04-26 20:07 ` Blue Swirl
2011-04-26 21:35 ` Igor Kovalenko
2011-04-27 17:40 ` Blue Swirl
2011-04-27 16:29 ` Artyom Tarasenko
2011-04-27 17:41 ` Blue Swirl
2011-04-10 14:59 ` Peter Maydell
2011-04-10 17:31 ` Artyom Tarasenko
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=20110410132415.GA6719@volta.aurel32.net \
--to=aurelien@aurel32.net \
--cc=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@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).