From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:50:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4453B16A4CE for ; Tue, 16 Nov 2004 19:50:59 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25E6E43D46 for ; Tue, 16 Nov 2004 19:50:59 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 1029272DF4; Tue, 16 Nov 2004 11:50:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0DE8372DD4; Tue, 16 Nov 2004 11:50:59 -0800 (PST) Date: Tue, 16 Nov 2004 11:50:59 -0800 (PST) From: Doug White To: ALeine In-Reply-To: <200411110104.iAB149kv097307@marlena.vvi.at> Message-ID: <20041116114809.S13866@carver.gumbysoft.com> References: <200411110104.iAB149kv097307@marlena.vvi.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3-RELEASE boot failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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 Nov 2004 19:50:59 -0000 On Wed, 10 Nov 2004, ALeine wrote: > Doug White wrote: > > > Hm... we'll need to disassemble the code there, but typically > > these types of crashes are caused by BIOS bugs. Try upgrading > > your BIOS. > > When I try to boot directly the machine reboots too quickly for > me to be able to catch the error message. The register dump is > from VMWare trying to boot the said FreeBSD 5.3-RELEASE as guest > OS using the mentioned disk in raw disk mode on a friend's > machine. FreeBSD 4.10-STABLE runs just fine that way on his > system. This makes me think it might not be BIOS related. Well VMware isn't the same hardware so thats a totally unrelated problem :) I'd suggest setting up a serial console and capturing the output that way. Connect another machine via null-modem cable to COM1 on the crashing system. At the first spinning bar hit a key and you'll get a boot: prompt. At that prompt enter "-h" and press Return and that should cause the loader (and the error output) to go to the serial port. > > What brand/model machine is this? > > i386, Athlon XP CPU, Chaintech 7SID (Sis 735 chipset) motherboard > with the latest official BIOS. So something fairly recent ... hm. > > Other things you might try: > > > > . Turn off 'Legacy USB' if you don't have a USB keyboard > > . Disable DMA on IDE disks (Known issue on older compaqs) > > I've tried it with USB on and off, it makes no difference. > I'll look into the DMA issue. Thanks for your quick reply. > > > ALeine > ___________________________________________________________________ > WebMail FREE http://mail.austrosearch.net > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org