From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] SPARC64: unable to boot OpenBIOS from git master
Date: Mon, 27 Feb 2012 06:36:32 +0000 [thread overview]
Message-ID: <4F4B2470.3080604@ilande.co.uk> (raw)
Hi all,
I've been experimenting with SPARC64 under QEMU, and with current git
master I am unable to boot OpenBIOS at all with the following error:
OpenBIOS for Sparc64
Unhandled Exception 0x0000000000000032
PC = 0x00000000ffd19d84 NPC = 0x00000000ffd19d88
Stopping execution
Using git bisect indicates that the problem lies with the following commit:
commit d5f27e88699f14c802d66c01de70e5ea37b7153a
Author: Michael S. Tsirkin <mst@redhat.com>
Date: Tue Feb 21 15:57:58 2012 +0200
pci: set memory type for memory behind the bridge
As we make upper bits in IO and prefetcheable memory
registers writeable, we should declare support
for 64 bit prefetcheable memory and 32 bit io
in the bridge.
This changes the default for apb, dec, but I'm guessing
they got the defaults wrong by accident.
Alternatively, we could let bridges declare lack of
64 bit support and make the upper bits read-only zero.
With this applied, we can drop these bits
from express code.
Reported-by: Gerd Hoffmann <kraxel@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Could someone familiar with apb,dec ack this please?
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Does anyone have an idea as to whether this is something that needs to
be fixed in QEMU or OpenBIOS?
Many thanks,
Mark.
next reply other threads:[~2012-02-27 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 6:36 Mark Cave-Ayland [this message]
2012-03-03 15:09 ` [Qemu-devel] SPARC64: unable to boot OpenBIOS from git master Blue Swirl
2012-03-04 9:43 ` Michael S. Tsirkin
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=4F4B2470.3080604@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.