From owner-freebsd-current Sun Jan 21 16:37:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from Mail6.sc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 16E3F37B401; Sun, 21 Jan 2001 16:37:12 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by Mail6.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 21 Jan 2001 19:37:11 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f0M0cAB15727; Sun, 21 Jan 2001 19:38:10 -0500 (EST) (envelope-from dmaddox) Date: Sun, 21 Jan 2001 19:38:10 -0500 From: "Donald J . Maddox" To: Kris Kennaway Cc: "Donald J . Maddox" , Alex Zepeda , current@FreeBSD.ORG Subject: Re: HEADS UP: Strange booting lockups Message-ID: <20010121193810.B15459@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: Kris Kennaway , "Donald J . Maddox" , Alex Zepeda , current@FreeBSD.ORG References: <20010121023238.S69199@canonware.com> <20010121025457.A396@zippy.pacbell.net> <20010121060520.A396@cae88-102-101.sc.rr.com> <20010121152922.C74407@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010121152922.C74407@citusc17.usc.edu>; from kris@FreeBSD.ORG on Sun, Jan 21, 2001 at 03:29:22PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 03:29:22PM -0800, Kris Kennaway wrote: > On Sun, Jan 21, 2001 at 06:05:20AM -0500, Donald J . Maddox wrote: > > > 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? > > This is a different problem. If you don't have device hints available > at boot (statically compiled into the kernel or loaded from /boot) > then the console driver doesn't get its hints, and doesn't work in the > manner you describe. Yeah, I know what my problem was... I was just suggesting that if something trashed the area of memory where these hints live at boot time, it could possibly cause the problem being described. That wasn't the problem, but hey, I was trying to help :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message