From owner-freebsd-current  Sat Sep  4  4:18: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP
	id 28EB4151FA; Sat,  4 Sep 1999 04:17:53 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA21720;
	Sat, 4 Sep 1999 21:17:36 +1000
Date: Sat, 4 Sep 1999 21:17:36 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199909041117.VAA21720@godzilla.zeta.org.au>
To: bde@zeta.org.au, mike@smith.net.au
Subject: Re: early panics broken
Cc: current@freebsd.org, msmith@freebsd.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> panic() no longer works when called early.  E.g., after booting with -d,
>> typing `panic<newline>' at the debugger prompt produces no output and
>> hangs.
>> 
>> This may be because panic() now depends on uninitialized event handlers.

This is because no shutdown_final event handlers have been registered.
The loop at the end of boot() is reached and loops endlessly.

>That would only be an issue if panic() then calls boot() without 
>initialising it.  Until boot() has been told how to restart the 
>particular hardware it's running on in an appropriate fashion, it's 
>somewhat difficult to do this "right".
>
>Perhaps exit() needs to be implemented?

Initialisation just needs to be unobfuscated so that it doesn't trip over
its own boot.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message