From owner-freebsd-current@FreeBSD.ORG Tue Aug 16 19:15:51 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84F4D1065740 for ; Tue, 16 Aug 2011 19:15:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5A66F8FC15 for ; Tue, 16 Aug 2011 19:15:51 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 0B6A846B43; Tue, 16 Aug 2011 15:15:51 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9ADFB8A02F; Tue, 16 Aug 2011 15:15:50 -0400 (EDT) From: John Baldwin To: Christoph Hoffmann Date: Tue, 16 Aug 2011 15:15:50 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <9B96176A-7550-4B60-8F4D-0B667EEF7A15@me.com> In-Reply-To: <9B96176A-7550-4B60-8F4D-0B667EEF7A15@me.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201108161515.50127.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 16 Aug 2011 15:15:50 -0400 (EDT) Cc: freebsd-current@freebsd.org Subject: Re: gptzfsboot error using HP Smart Array P410i Controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2011 19:15:51 -0000 On Tuesday, August 16, 2011 1:46:48 pm Christoph Hoffmann wrote: > Setting high_heap_size to zero ends with an error: > > Attempting Boot From CD-ROM > Attempting Boot From Hard Drive (C:) > 474: high_heap_size=0x0; dsk=0x1a000; &bootinfo=0x8694 > malloc failure Hmm, I am really at a loss for what is trashing 'dsk'. You could possibly try adjusting bios_getmem() to force it to use high_heap_size from bios_extmem (that is at the bottom of the function) perhaps. However, that is mostly a bit of a guess that some part of your BIOS is randomly zero'ing dsk. I'm at a loss as to how the assignments to bootinfo would trash 'dsk'. :( -- John Baldwin