From owner-freebsd-alpha Mon Feb 18 0: 0:15 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id F034237B405 for ; Mon, 18 Feb 2002 00:00:07 -0800 (PST) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g1I802f04907; Mon, 18 Feb 2002 00:00:02 -0800 (PST) (envelope-from mjacob@feral.com) Date: Mon, 18 Feb 2002 00:00:02 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: current boot block doesn't halt cleanly all the time In-Reply-To: <20020218084445.A46039@freebie.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You can see Inconsistent Driver state. But usually it means you unexpectedly halted and then rebooted. This is the first I'd seen where a halt and a boot *of a different device* caused that Inconsistent boot driver state message. On Mon, 18 Feb 2002, Wilko Bulte wrote: > On Sun, Feb 17, 2002 at 07:37:08PM -0500, Andrew Gallatin wrote: > > > > Matthew Jacob writes: > > > HALT instruction executed > > > PC = 2000c04c > > > P00>>b dkb0 -fl 0 > > > > > > Inconsistent boot driver state. > > > System will be reset prior to boot. > > > > > > Initializing... > > > > My XP1000 does this with -stable. It sometimes does this for tru64 > > too. > > I have seen this on multiple Alpha machines running Tru64 too. > > -- > | / o / /_ _ wilko@FreeBSD.org > |/|/ / / /( (_) Bulte Arnhem, the Netherlands > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message