From owner-freebsd-current@FreeBSD.ORG Thu Aug 12 19:46:20 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 9BB5616A4CE for ; Thu, 12 Aug 2004 19:46:20 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7704743D39 for ; Thu, 12 Aug 2004 19:46:20 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.12.11/8.12.11) with ESMTP id i7CJkKEB065324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 12 Aug 2004 12:46:20 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i7CJkKL6065323 for current@freebsd.org; Thu, 12 Aug 2004 12:46:20 -0700 (PDT) (envelope-from jdc) Date: Thu, 12 Aug 2004 12:46:20 -0700 From: Jeremy Chadwick To: current@freebsd.org Message-ID: <20040812194619.GA65076@parodius.com> Mail-Followup-To: current@freebsd.org References: <411BB2EC.1020903@he.iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <411BB2EC.1020903@he.iki.fi> User-Agent: Mutt/1.5.6i Subject: Re: boot loader crashes 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: Thu, 12 Aug 2004 19:46:20 -0000 This sounds related to the "boot2" madness we went through about a week ago. There's too many threads to point you to, but as it stands now, things work. I can confirm that at one time there was a problem with the loader breaking (i.e. when boot2 loaded, it would quickly panic/spit out exceptions, then immediately reboot the machine), but that was taken care of as well. I would recommend rebuilding the bootblocks and re-applying them. In addition, reinstall the boot0 blocks as well, just to be safe. A quick walkthrough: # cd /usr/src/sys/boot # make clean # make # make install # disklabel -B (i.e. "ad0s1") # boot0cfg -B (i.e. "ad0") -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Thu, Aug 12, 2004 at 09:11:56PM +0300, Petri Helenius wrote: > > I updated a machine with ABIT VP6 (dual S370) motherboard from -CURRENT > in May to recent -CURRENT and since then the boot crashes with a message > which is visible for only a fraction of a second until the BIOS message > shows again. This is reproduceable with recent CD's. Iīm able to boot > the system using 5.2.1 release CD and then just switching over to the HD. > > The bootloader seems to gone through multiple changes so I couldnīt > immediately locate a place which could be at fault. > > Any ideas or suggestions would be appreciated, I would hate to have to > ditch the board. > > Pete > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"