From: Peter Maydell <peter.maydell@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PPC: Regression booting NetBSD
Date: Tue, 10 Dec 2013 14:40:02 +0000 [thread overview]
Message-ID: <CAFEAcA_26JC36XoXJFTaftk1pRuUSbRkBeUaAvKiByWitDPCbw@mail.gmail.com> (raw)
In-Reply-To: <52A72413.9090901@ilande.co.uk>
On 10 December 2013 14:24, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> 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.
>
>
> build@kentang:~/rel-qemu-git/bin$ ./qemu-system-ppc -cdrom
> /home/build/src/qemu/image/ppc/macppccd-5.0.2.iso -boot d -bios
> /home/build/src/openbios/openbios-git/openbios-devel/obj-ppc/openbios-qemu.elf.nostrip
> 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
[etc]
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 :-)
thanks
-- PMM
next prev parent reply other threads:[~2013-12-10 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 14:24 [Qemu-devel] PPC: Regression booting NetBSD Mark Cave-Ayland
2013-12-10 14:40 ` Peter Maydell [this message]
2013-12-10 20:43 ` Mark Cave-Ayland
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=CAFEAcA_26JC36XoXJFTaftk1pRuUSbRkBeUaAvKiByWitDPCbw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).