[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [Qemu-devel] PPC: Regression booting NetBSD

From: Mark Cave-Ayland
Subject: Re: [Qemu-ppc] [Qemu-devel] PPC: Regression booting NetBSD
Date: Tue, 10 Dec 2013 20:43:13 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12

On 10/12/13 14:40, Peter Maydell wrote:

On 10 December 2013 14:24, Mark Cave-Ayland
<address@hidden>  wrote:
I've been running my OpenBIOS test suite on a recent git (commit a1d22a) and
have encountered a QEMU process segfault in 2 out of 3 of my NetBSD 5.0.2
boot attempts. Does anyone have an idea what could be causing this? Other
OSs don't seem to be affected.

address@hidden:~/rel-qemu-git/bin$ ./qemu-system-ppc -cdrom
/home/build/src/qemu/image/ppc/macppccd-5.0.2.iso -boot d -bios
qemu: fatal: Trying to execute code outside RAM or ROM at 0x0a64696c

NIP 0a64696c   LR 0a64696d CTR 00000000 XER 00000000
MSR 00009030 HID0 00000000  HF 00000000 idx 1


This isn't a QEMU process segfault -- it's just that the guest
has attempted to jump to a memory location which is neither
RAM nor ROM (you can see the guest NIP is the same address
the message prints). This is probably because something has
gone wrong some distance further back in guest execution;
identifying exactly what that was might require some tedious
debugging :-)

Well after some fiddling today, it seems that subtle changes in the memory layout between different revisions of OpenBIOS cause NetBSD to crash with the default 128M of RAM provided by QEMU. With 256M specified on the command line then everything works as before.

My guess is that in the case where QEMU doesn't crash, we're just lucky in that whatever memory corruption is occurring doesn't manage to trigger the assertion in the emulator.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]