From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nloyv-0002WC-HT for qemu-devel@nongnu.org; Sun, 28 Feb 2010 14:39:13 -0500 Received: from [199.232.76.173] (port=49873 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nloyv-0002Vb-2T for qemu-devel@nongnu.org; Sun, 28 Feb 2010 14:39:13 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nloyt-0001E5-HF for qemu-devel@nongnu.org; Sun, 28 Feb 2010 14:39:12 -0500 Received: from mail-vw0-f45.google.com ([209.85.212.45]:63642) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nloyt-0001DX-53 for qemu-devel@nongnu.org; Sun, 28 Feb 2010 14:39:11 -0500 Received: by vws19 with SMTP id 19so246977vws.4 for ; Sun, 28 Feb 2010 11:39:07 -0800 (PST) Date: Sun, 28 Feb 2010 14:39:04 -0500 From: Kevin O'Connor Subject: Re: [Qemu-devel] SeaBIOS error with Juniper FreeBSD kernel Message-ID: <20100228193904.GA15352@morn.localdomain> References: <20100221040555.GA16455@morn.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brandon Bennett , Gleb Natapov Cc: seabios@seabios.org, qemu-devel@nongnu.org On Sun, Feb 21, 2010 at 04:18:38PM -0700, Brandon Bennett wrote: > > On Sat, Feb 20, 2010 at 9:05 PM, Kevin O'Connor wrote: > >> Should a kernel fail during boot, I'd suspect it doesn't like one of > >> the apm/pcibios callbacks, or it doesn't like one of the > >> smbios/mptable/acpi tables.  You could try compiling the SeaBIOS code > >> (see http://seabios.org/Download ) and increasing the debugging by > >> modifying src/config.h.  Specifically, you could increase > >> CONFIG_DEBUG_LEVEL, and set DEBUG_HDL_pcibios32 and DEBUG_HDL_apm to > >> 1.  Also, you could try disabling some of the features to see if that > >> prevents the fault (eg, disabling CONFIG_ACPI / CONFIG_SMBIOS / > >> CONFIG_MPTABLE). > > > > I have narrowed it down to SMBIOS. If I disable CONFIG_SMBIOS the > image boots up fine. Gleb, have you seen this thread? Some of the recent changes to smbios that look like possible culprits are: Make SMBIOS table pass MS SVVP test Use MaxCountCPUs during building of per cpu tables. Add malloc_high/fseg() and rework bios table creation to use them. There were other changes, but the comments indicate they were only ports of changes already in bochs. I suppose it's also possible the lack of smbios is turning off some other feature in the guest (eg, acpi) that's the real culprit. -Kevin