Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!gateway.dircsa.org.au!apanix!cleese.apana.org.au!cleese.apana.org.au!not-for-mail
From: newton@cleese.apana.org.au (Mark Newton)
Newsgroups: comp.os.386bsd.development
Subject: Re: FreeBSD 1.0R Kernel problems...
Date: 5 Jan 1994 19:47:47 +1030
Organization: cleese.apana.org.au public access UNIX +61-8-3736006
Lines: 33
Message-ID: <2ge0k9$d69@cleese.apana.org.au>
References: <2g5pv3$bnl@cruella.ee.pdx.edu>
NNTP-Posting-Host: cleese.apana.org.au
In article <2g5pv3$bnl@cruella.ee.pdx.edu> erich@cruella.ee.pdx.edu (Erich S. Boleyn) writes:
>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
>is very disturbing, and I don't trust my system to stay in this state
>without understanding what's going on (I'll probably try to run some
>tests to see if all FP is messed up, etc, but it is clearly a bug or
>overrun of a kernel table of some sort).
The error you describe is what you get if you run any programs which access
the kvm database if your customized kernel is not stored in the file
/386bsd.
During booting, kvm_mkdb walks through the symbol table in /386bsd and
stores what it finds into /var/run/kvm_386bsd.db. If the symbol table
read from /386bsd contains addresses which are invalid for the currently
running kernel, then you'll find that ps, uptime, w, swapinfo, vmstat,
iostat and any number of other commands will report "floating exceptions"
and dump core.
Solution:
# mv /386bsd /386bsd.old
# mv /386bsd.new /386bsd
# reboot
- mark
--
--------------------------------------------------------------------
I tried an internal modem, newton@cleese.apana.org.au
but it hurt when I walked. Mark Newton
----- Voice: +61-8-3735575 --------------- Data: +61-8-3736006 -----