Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!udel!newsserv.cs.sunysb.edu!stark.UUCP!stark!stark!gene From: stark!gene@newsserv.cs.sunysb.edu (Gene Stark) Newsgroups: comp.os.386bsd.development Subject: Re: FreeBSD 1.0R Kernel problems... Date: 2 Jan 94 10:04:59 Organization: Gene Stark's home system Lines: 27 Message-ID: <STARK!GENE.94Jan2100459@stark.uucp> References: <2g5pv3$bnl@cruella.ee.pdx.edu> NNTP-Posting-Host: stark.uucp In-reply-to: erich@cruella.ee.pdx.edu's message of 1 Jan 1994 22:35:15 -0800 In article <2g5pv3$bnl@cruella.ee.pdx.edu> erich@cruella.ee.pdx.edu (Erich S. Boleyn) writes: I don't know who else has seen this before (or if it is a FAQ :-\, but I grabbed the source the other day, and tried compiling a different kernel for the FreeBSD 1.0 Release version (trying to add another ethernet card and use more than 2 serial ports). When booting the new kernel, the error (just after the savecore command) "Device /dev/wd0 not configured" appeared, and then a complaint from 'savecore' about a similar problem with the 'wd0' device. Then it would work fine but a 'ps -u' or 'ps -v' (or any combination displaying percentage displays) would dump with a floating-point exception. This This is a symptom of not having called your test kernel "/386bsd". Ps dumps because the kernel namelist database is built on boot for /386bsd, but you are running a different kernel, so it ends up getting bogus data and dividing by zero or something. I'm not sure about the "device not configured" messages, but I do know that "savecore" will complain if it thinks it has a core dump for a version of the system that doesn't match what is in /386bsd. Maybe this is what you are seeing. Also, make sure that you have your swap device (probably /dev/wd0b) in your /etc/fstab with "swap" as the FS type. - Gene Stark --