From: Brad <brad@comstyle.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OpenBSD/macppc and sparc64 failing to boot with similar error.
Date: Tue, 02 Aug 2011 23:02:27 -0400 [thread overview]
Message-ID: <4E38BA43.6090002@comstyle.com> (raw)
In-Reply-To: <CAAu8pHt2KxtBvuWbVnFfEcAB_1dHRz4T-AahO16UkVpaxEPFvg@mail.gmail.com>
On 01/08/11 5:35 PM, Blue Swirl wrote:
> On Mon, Aug 1, 2011 at 12:33 AM, Brad<brad@comstyle.com> wrote:
>> I know sparc64 had little chance of actually working but
>> I thought I'd take it for a spin with 0.15.0-rc1 and
>> see how it fared in addition to macppc which has a good
>> chance of working nowdays with modern QEMU. Lets see
>> what QEMU and related bugs are left..
>>
>> I noticed the bootblocks for each respective arch are
>> failing in a very similar manner. I would guess that
>> this is most likely a bug with the OpenBIOS Open Firmware
>> implementation?
>>
>> Any assistance with this? Blue?
After a little playing around I have found this is definitely
a bug in QEMU. Turning on the OpenBSD malloc S flag which is
what I run on all of my systems triggered this behavior in QEMU
and trying to narrow it down further since S is a combination
of other flags I found it was the J flag specifically that is
triggering this behavior.
From malloc(3)..
J ``Junk''. Fill some junk into the area allocated.
Currently junk is bytes of 0xd0 when allocating; this
is pronounced ``Duh''. :-) Freed chunks are filled
with 0xdf.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2011-08-03 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 0:33 [Qemu-devel] OpenBSD/macppc and sparc64 failing to boot with similar error Brad
2011-08-01 21:35 ` Blue Swirl
2011-08-03 3:02 ` Brad [this message]
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=4E38BA43.6090002@comstyle.com \
--to=brad@comstyle.com \
--cc=blauwirbel@gmail.com \
--cc=openbios@openbios.org \
--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 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).