From owner-freebsd-bugs  Tue May 16 14:41:52 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 73E4A37BB85; Tue, 16 May 2000 14:41:51 -0700 (PDT)
	(envelope-from hoek@FreeBSD.org)
Received: (from hoek@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id OAA82062;
	Tue, 16 May 2000 14:41:51 -0700 (PDT)
	(envelope-from hoek@FreeBSD.org)
Date: Tue, 16 May 2000 14:41:51 -0700 (PDT)
From: <hoek@FreeBSD.org>
Message-Id: <200005162141.OAA82062@freefall.freebsd.org>
To: schreib_mir_du_spacken@gmx.de, hoek@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: i386/11488
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Error while starting FreeBSD

State-Changed-From-To: open->closed
State-Changed-By: hoek
State-Changed-When: Tue May 16 14:38:29 PDT 2000
State-Changed-Why: 
I concur with Omachonu Ogali <oogali@intranova.net> analysis of the
problem.  The laptop hardware must not be resetting itself properly
and, if Omachonu is correct, nothing could be done even if FreeBSD
knew exactly what wasn't being initialised correctly.  A full power
cycle isn't too expensive a price to pay, and not a bad idea anyways.


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