Question:
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
Answer:
I've disabled all third party modules (this happens when I boot in
safe mode too). The modules that are being loaded are whatever
modules are installed after a:
I usually perform those steps after I've rebooted to ensure that my
system will boot off the new kernel, as per the instructions in the
FreeBSD handbook.
How well does simply upgrading with the CD work (as opposed to wiping
clean)? I've upgraded several times to new releases simply by
rebuilding world, it has never failed me in the past. I don't doubt
what you are saying here, but since I will have to change how I work,
assuming that I can boot off of the 6.2 CD, I'd appreciate any
general upgrade tips that don't involve wiping the disk clean (which
is not really an option).
For instance, is rebuilding world between point releases (e.g. 5.4 to
5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)?
I'll do my own homework regarding this too, but I appreciate any
nuggets of wisdom you might have! As far as me being an expert, I
guess I'd categorize me somewhere in between complete newb and
FreeBSD developer =)
My production system is backed up daily to two different sites,
that's not an issue. The system I'm thinking of upgrading to 6.2 is
my test server I run out of my house that stores movie files and
other non-essential files. Technically, wiping it clean *would* be an
option if it came down to it, just an inconvenience. Perhaps I should
invest in another HD to use for instances such as this.
My system does boot off of disc 1 of the FreeBSD 6.2 CD. However,
even when copying the /boot directory from the CD to my machine, it
still produces the same kernel panic, even when starting in safe
mode. I've run a memtest, and it checked out fine.
There must be something in my user space or world that it barfs on. I
guess I will try a clean install and rebuild at some point...
If you have any other ideas, I'm all ears!
