From owner-freebsd-current Sun Mar 8 22:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14255 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:29:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14224 for ; Sun, 8 Mar 1998 22:29:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA13511; Sun, 8 Mar 1998 22:27:06 -0800 (PST) Message-Id: <199803090627.WAA13511@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Mike Smith , FreeBSD current users Subject: Re: Latest -current kernel panics on boot In-reply-to: Your message of "Mon, 09 Mar 1998 16:39:16 +1030." <19980309163916.42581@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 22:27:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 March 1998 at 21:41:57 -0800, Mike Smith wrote: > >> before the swap partition gets mounted, so I don't have a dump. I > >> wrote down a trace, but I'm assuming that we don't need that level of > >> detail, so I won't type it in unless somebody wants it. > > > > What does the 'config' line in your kernel look like? It's possible > > that some of the static configuration code can't deal with the slice > > number in the minor. > > Yes, I thought of that too. Nothing spectacular: > > config kernel root on wd0 *mumble* Where does the trace go back through? Is it still in configure()? > >> This doesn't seem to be problem, though: it doesn't work either way. > >> The old kernel only works with wd0a, and the new kernel doesn't work > >> with either fstab entry. > > > > You should receive a "changing root device to ..." message after your > > device probes with the new kernel. > > That's where it dies. Before or after the message? The message won't get emitted until setroot() is called. (This part of the system is a pile of rubble.) What is the root device that it's nominating? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message