On Tuesday, January 9, 2018 5:29:07 PM EST Peter Maydell wrote:
> The abort cares about all kinds of CPU interrupts (which includes
> some kinds of internal things). These are not supposed to happen
> unexpectedly when in icount mode. If you run under gdb you can
> get a backtrace of what it was that caused the call that made
> this assert fire. That will help in figuring out what's happened.
Peter,
Here is a backtrace to cpu_abord. I have been rebasing my changes on top of
the master branch at git://git.qemu-project.org/qemu.git.
Thread 3 "qemu-system-ppc" hit Breakpoint 1, tcg_handle_interrupt
(cpu=0x7ffff7fc2010, mask=4)
at qemu/accel/tcg/tcg-all.c:58
58 cpu_abort(cpu, "Raised interrupt while not in I/O
function");
(gdb) bt
#0 tcg_handle_interrupt (cpu=0x7ffff7fc2010, mask=4) at qemu/accel/tcg/tcg-
all.c:58
#1 0x0000555555962aa4 in cpu_interrupt (cpu=0x7ffff7fc2010, mask=4) at qemu/
include/qom/cpu.h:859
#2 0x0000555555962e55 in cpu_interrupt_exittb (cs=0x7ffff7fc2010) at qemu/
target/ppc/helper_regs.h:105
#3 0x0000555555964505 in do_rfi (env=0x7ffff7fca2b0, nip=197460, msr=4096)
at qemu/target/ppc/excp_helper.c:998
#4 0x0000555555964555 in helper_rfi (env=0x7ffff7fca2b0) at qemu/target/ppc/
excp_helper.c:1008
#5 0x00007fffe7c124b9 in code_gen_buffer ()
#6 0x000055555583ff2e in cpu_tb_exec (cpu=0x7ffff7fc2010, itb=0x7fffe7c12340
<code_gen_buffer+365334>)
at qemu/accel/tcg/cpu-exec.c:169
#7 0x0000555555840ccd in cpu_loop_exec_tb (cpu=0x7ffff7fc2010,
tb=0x7fffe7c12340 <code_gen_buffer+365334>, last_tb=0x7fffe7bb7a28,
tb_exit=0x7fffe7bb7a20) at qemu/accel/tcg/cpu-exec.c:623
#8 0x0000555555840fdc in cpu_exec (cpu=0x7ffff7fc2010) at qemu/accel/tcg/cpu-
exec.c:732
#9 0x00005555558059bc in tcg_cpu_exec (cpu=0x7ffff7fc2010) at qemu/cpus.c:
1300
#10 0x0000555555805beb in qemu_tcg_rr_cpu_thread_fn (arg=0x7ffff7fc2010) at
qemu/cpus.c:1396
#11 0x00007ffff0989617 in start_thread () from /lib64/libpthread.so.0
#12 0x00007ffff06c8bdf in clone () from /lib64/libc.so.6
