From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56965) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoRj9-0007qO-Lg for qemu-devel@nongnu.org; Tue, 02 Aug 2011 23:02:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoRj8-0006Ak-Ij for qemu-devel@nongnu.org; Tue, 02 Aug 2011 23:02:35 -0400 Received: from speedy.comstyle.com ([206.51.28.2]:12882 helo=mail.comstyle.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoRj8-0006Ae-GY for qemu-devel@nongnu.org; Tue, 02 Aug 2011 23:02:34 -0400 Message-ID: <4E38BA43.6090002@comstyle.com> Date: Tue, 02 Aug 2011 23:02:27 -0400 From: Brad MIME-Version: 1.0 References: <20110801003308.GA99@rox.home.comstyle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] OpenBSD/macppc and sparc64 failing to boot with similar error. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: The OpenBIOS Mailinglist , qemu-devel@nongnu.org On 01/08/11 5:35 PM, Blue Swirl wrote: > On Mon, Aug 1, 2011 at 12:33 AM, Brad 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.