Date: Sat, 3 Jun 2006 23:46:52 -0400 (EDT) From: Brian Tao <taob@risc.org> To: FREEBSD-STABLE <freebsd-stable@freebsd.org> Subject: Re: 6.1 kernel unable to find /dev ? Message-ID: <20060603233625.C15261-100000@as2.dm.egate.net> In-Reply-To: <20060603181136.C40001@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Jun 2006, Doug White wrote:
>
> 1. Capture the boot output from both the working 6.0 kernel and your
> broken 6.1 kernel and compare the two. If there are differences or errors
> being returned from the ATA controller or disks then those will need to be
> addressed.
My serial console logs only go back as far as April 25, but here
are the list of kernels I've attempted to boot. These kernels may or
not have a matching world, since I haven't been able to always
successfully boot the new kernel prior to doing an installworld:
SUCCESSFUL BOOT:
FreeBSD 6.1-RC2 #151: Thu May 4 12:46:25 EDT 2006
FreeBSD 6.0-RELEASE-p6 #1: Sat Apr 15 19:59:37 EDT 2006
CRASH BEFORE REACHING INIT:
FreeBSD 6.1-RELEASE #203: Fri May 12 18:41:03 EDT 2006
FreeBSD 6.1-RELEASE #204: Thu May 25 14:05:40 EDT 2006
FreeBSD 6.1-RC2 #151: Thu May 4 12:46:25 EDT 2006
FreeBSD 6.1-PRERELEASE #1: Mon Apr 3 22:18:55 EDT 2006
FreeBSD 6.1-RELEASE-p1 #206: Thu Jun 1 03:30:38 EDT 2006
FreeBSD 6.1-RELEASE-p1 #207: Sat Jun 3 20:19:46 EDT 2006
Notice how 6.1-RC2 #151 is on both lists. I'm guessing there
isn't anything wrong with the kernels at all, and there is something
about the root filesystem or a file outside of the kernel (maybe a
kernel module, or a shared lib) that is somehow preventing post-6.0
kernels from seeing any filesystems.
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060603233625.C15261-100000>