Date: Sun, 30 Oct 2005 22:01:24 +0100 From: Roland Smith <rsmith@xs4all.nl> To: freebsd-questions@FreeBSD.ORG Subject: Re: Canonical upgrade procedure for 6.0? Message-ID: <20051030210124.GA25121@slackbox.xs4all.nl> In-Reply-To: <20051030202320.GO739@crom.vickiandstacey.com> References: <20051030102835.GK739@crom.vickiandstacey.com> <20051030110604.GA75601@slackbox.xs4all.nl> <20051030114424.GL739@crom.vickiandstacey.com> <20051030155240.GA5825@slackbox.xs4all.nl> <20051030175509.GN739@crom.vickiandstacey.com> <20051030195005.GA23835@slackbox.xs4all.nl> <20051030202320.GO739@crom.vickiandstacey.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 08:23:20PM +0000, Stacey Roberts wrote: > > There were some messages about this on the mailing lists recently. > >=20 > > Apparently some options and devices were moved into DEFAULTS (which is > > combined with the chosen kernel configuration by config(8).), so that > > people wouldn't leave them out by accident, such as 'mem' and 'io' > > (important for running X). >=20 > I saw those posts today, but DEFAULTS don't appear to have the regular > WITNESS / INVARIANTS entries either.., Moot at this point, though, as > the host is now unable to do much more than sit there - keeps > panicking whenever I try to build a custom kernel, or even cvsup a > fresh source (using either standard-supfile, or stable-supfile) :-( Does it work with the backup kernel in /boot/kernel.old? BTW, one of the first things I do after install is to copy /boot/kernel to /boot/kernel.generic, so I have a working kernel at hand in case something is FUBAR. > >=20 > > My system (recently installed from 6.0-RC1 CD's) doesn't have the chang= es > > yet. They must have been implemented after RC1 was released. It does lo= ok > > somewhat like a kludge to me. >=20 > Hrmph.., >=20 > Looks like this machine (previously running 5-Stable since 5.3) is > completely hosed now. I have a think about what I can do here..,=20 Reinstall the base system from CD, I guess. If you have /usr on a separate slice, you won't lose the ports you've installed, I think. > I've attached info.0 from the crash dir, if anyone cares to look at > it, please. > Dump header from device /dev/ad0s1b > Architecture: i386 > Architecture Version: 2 > Dump Length: 200867840B (191 MB) > Blocksize: 512 > Dumptime: Sun Oct 30 19:32:34 2005 > Hostname: omni.vickiandstacey.com > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 6.0-RC1 #0: Sun Oct 30 16:09:08 GMT 2005 > stacey@omni.vickiandstacey.com:/usr/obj/usr/src/sys/GENERIC > Panic String: ffs_valloc: dup alloc Looks like the panic occurred in the filesystem code, and it has to do with memory allocation. If you really want to know what caused it, read the chapter on kernel debugging in the developers handbook. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZTSkEnfvsMMhpyURAr+cAJ9SZGkycpC9oSOi23U9T9jZ8ObmCQCghYLs FEA9lHysymFUQJgKNOYEl2Y= =RRpO -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051030210124.GA25121>