From owner-freebsd-current Mon Nov 25 15:52:37 2002 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 4B8BD37B401; Mon, 25 Nov 2002 15:52:35 -0800 (PST) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ACE843EBE; Mon, 25 Nov 2002 15:52:34 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0340.cvx40-bradley.dialup.earthlink.net ([216.244.43.85] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18GT0z-0002Q3-00; Mon, 25 Nov 2002 15:51:45 -0800 Message-ID: <3DE2B740.4206206E@mindspring.com> Date: Mon, 25 Nov 2002 15:50:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Marcin Dalecki Cc: Kris Kennaway , Robert Watson , Mikhail Teterin , current@FreeBSD.ORG Subject: Re: -current unusable after a crash References: <200211250959.39594.mi+mx@aldan.algebra.com> <20021125172445.GA8953@rot13.obsecurity.org> <3DE29DE6.CDD96F3F@mindspring.com> <3DE2AF65.9000502@gmx.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Marcin Dalecki wrote: > > I don't think this is really possible. > > > > I went looking for a generic "application use" CMOS are for this > > sort of thing a while back, and I was unable to find one. > > Well you should please take a look at the "fast boot" option > of moderately modern BIOS-es. Somthing along those lines went right now > in to the linux kernel. Seems pretty adequate to me, since you would > be even able to controll it through the BIOS setup... Is there documentation available for this anywhere? The BIOS vendor documentation, not the Linux source code. My gut feeling is that this isn't going to be too helpful, without AC failure notification with a DC holdup time. The problem is that the best case is power failure, and the worst case is a corrupted GDT and a double panic off a trap 12 in the trap 12 handler (such that you would get a trap 12 when you tried to write back to the CMOS that this was the worst case, not the best case). Basically, you are still stuck needing power failure notification, so you can write the cause of the failure back. At startup, you have to set the saved state to "worst possible failure: no way to update cause of failure in CMOS", and then back off to softer failure modes from there. I think this "Fast boot" stuff is useful, but the way it's useful is if your main memory is reflected to a seperate area of the disk, so that you can bring up the system image very quickly. Basically, it means that it's not at all useful for the problem at hand, unless it provides for power fail notification. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message