Re: [Qemu-ppc] kvm qemu-system-ppc crash if macos 9x

[luigi burdo]

Hi Balaton,

noting more than  this was reported.

something kick the kvm module.

here is the gbd trace.

Reading symbols from ./qemu-system-ppc...done.
(gdb) run
Starting program: /home/amigaone/src/qemu-dbg/qemu/ppc-softmmu/qemu-system-ppc -cpu G3 -m 256 -drive file=/mnt/SDA6/machdd,id=disk0,format=raw,index=0,media=disk,cache=none -display sdl -machine mac99 -net nic,model=rtl8139 -net user --enable-kvm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x3fffb426ba60 (LWP 14526)]
[New Thread 0x3fffb3762a60 (LWP 14527)]
[New Thread 0x3fffb2be5a60 (LWP 14528)]
[Thread 0x3fffb2be5a60 (LWP 14528) exited]
[New Thread 0x3fffb2be5a60 (LWP 14589)]
[New Thread 0x3fff87a7da60 (LWP 14590)]
KVM: unknown exit, hardware reason 80020070
NIP 00000700   LR fbf15910 CTR 00000000 XER 20000100 CPU#0
MSR 00000000 HID0 00000000  HF 00000000 iidx 3 didx 3
TB 00000000 00000000 DECR 00000000
GPR00 0000000000000000 000000000fbfe000 0000000000000000 0000000068fff000
GPR04 0000000068080000 000000000fee6000 0000000000000000 0000000000000000
GPR08 0000000000000000 0000000000000000 000000006806e908 000000000002d032
GPR12 000000006806e8b8 0000000000000000 0000000000000000 0000000000004010

GPR16 0000000000a80000 0000000049610008 0000000068ffffac 0000000068ffffb0
GPR20 0000000000000000 0000000000000000 0000000000f15fb8 00000000fbf15910
GPR24 000000000fbfe360 0000000000f15944 0000000000000051 0000000068ffffac
GPR28 0000000000f15fb8 000000000fbfe000 00000000b0000023 000000000fbff112
CR 24202851  [ E  G  E  -  E  L  GO -O ]             RES ffffffff
FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR 00000000
 SRR0 00f13578  SRR1 00000000    PVR 00080301 VRSAVE 00000000
SPRG0 0fbfe000 SPRG1 0fbfe000  SPRG2 00f15fb8  SPRG3 0fbfe4e0
SPRG4 00000000 SPRG5 00000000  SPRG6 00000000  SPRG7 00000000
 SDR1 0fc0001f   DAR 68ffffac  DSISR 42000000
[Thread 0x3fff87a7da60 (LWP 14590) exited]

Ciao

Luigi

You don't need the -gdb dev at the end, the gdb --args at the front is
enough. Then start it from the (gdb) prompt with 'run' and when the
segfault happens type 'where' which should print a backtrace. Not sure if
this will help but may provide some additional info.

Regards,
BALATON Zoltan