From owner-freebsd-current  Sun Jan 21  3: 4:56 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mail8.sc.rr.com (fe8.southeast.rr.com [24.93.67.55])
	by hub.freebsd.org (Postfix) with ESMTP id 10BD937B401
	for <current@freebsd.org>; Sun, 21 Jan 2001 03:04:35 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail8.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Sun, 21 Jan 2001 06:02:31 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id f0LB5KS00450;
	Sun, 21 Jan 2001 06:05:20 -0500 (EST)
	(envelope-from dmaddox)
Date: Sun, 21 Jan 2001 06:05:20 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Alex Zepeda <jazepeda@pacbell.net>
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP: Strange booting lockups
Message-ID: <20010121060520.A396@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Alex Zepeda <jazepeda@pacbell.net>, current@FreeBSD.ORG
References: <20010121023238.S69199@canonware.com> <20010121025457.A396@zippy.pacbell.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010121025457.A396@zippy.pacbell.net>; from jazepeda@pacbell.net on Sun, Jan 21, 2001 at 02:54:57AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Jan 21, 2001 at 02:54:57AM -0800, Alex Zepeda wrote:
> On Sun, Jan 21, 2001 at 02:32:38AM -0800, Jason Evans wrote:
> 
> > Several of us have started experiencing problems with kernels that won't
> > boot.  The symptom is hard to miss: the machine locks up at the spinner
> > just before printing the copyright message at the beginning of the boot
> > sequence.
> 
> Hmm.  I've recently tried to boot a kernel off of a CDRW, and it got
> through the loader, printed the copyright and blinked the keyboard leds,
> and froze.
> 
> The lsdev command causes the loader to panic when booted from the CD.
> 
> Could this possibly be related?

It may have absolutely nothing to do with either of these cases, but
I found out the hard way recently that booting with no device.hints
in /boot will exhibit symptoms that appear identical to this.  Is it
possible that something is trashing the device list, or not initializing
it properly at kernel load time?


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