Date: Sun, 21 Jan 2001 19:38:10 -0500 From: "Donald J . Maddox" <dmaddox@sc.rr.com> To: Kris Kennaway <kris@FreeBSD.ORG> Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, Alex Zepeda <jazepeda@pacbell.net>, current@FreeBSD.ORG Subject: Re: HEADS UP: Strange booting lockups Message-ID: <20010121193810.B15459@cae88-102-101.sc.rr.com> In-Reply-To: <20010121152922.C74407@citusc17.usc.edu>; from kris@FreeBSD.ORG on Sun, Jan 21, 2001 at 03:29:22PM -0800 References: <20010121023238.S69199@canonware.com> <20010121025457.A396@zippy.pacbell.net> <20010121060520.A396@cae88-102-101.sc.rr.com> <20010121152922.C74407@citusc17.usc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010121193810.B15459>