Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!cs.uoregon.edu!usenet.ee.pdx.edu!not-for-mail
From: erich@cruella.ee.pdx.edu (Erich S. Boleyn)
Newsgroups: comp.os.386bsd.development
Subject: FreeBSD 1.0R Kernel problems...
Date: 1 Jan 1994 22:35:15 -0800
Lines: 65
Message-ID: <2g5pv3$bnl@cruella.ee.pdx.edu>
NNTP-Posting-Host: cruella.ee.pdx.edu
X-Newsreader: NN version 6.5.0 #2 (NOV)
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
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).
After toying with it for two days, it turns out that every build that is
not *identical* to the distribution build will have this problem (well,
a minor parameter change might have worked at one point... I didn't
really isolate this until a bit later... the 1.0.2 source patches
just didn't work well at all... they had this problem with even the
default compile!). It doesn't even have to have the hardware physically
present to act this way, just the different compile will do it... quite
frustrating. Is there something that I am supposed to do to a new build?
I run the configuration stuff and it works great with the "GENERICBT" that
I use, but even changing the 'ident' parameter to 'FAUSTUS', my machines's
name, has caused this problem (The file name of the configuration file was
also FAUSTUS, I had just copied it over, changed the 'ident' parameter, and
tried to make a clean build). Yes, I tried just copying the file and
configuring from there. It worked fine, but then the 'ident' parameter
made it give those errors.
The only thing that hasn't caused a problem is the one line of code
I added to fix an NFS bug (something previously posted in one of
the 'comp.os.386bsd.*' newsgroups).
Examples of single-point changes I tried were changing the number of
'pty' pseudo-devices from 12 to 16, changing the IRQ of one of the
serial ports to {11,12,15}, commenting out an 'sio' device driver,
adding the 'GATEWAY' define to the file (I need that for my application),
etc.
Oh, yes. I did do a complete re-load of all the base software and
compiler, etc. and it does exactly the same thing!
My hardware is an UltraStor 34F LB SCSI controller + SMC Elite 16-bit
ethernet adapters, running on a 486DX2/66 LB motherboard, all the
consistent results were with the 1.0-RELEASE source tree (as mentioned
I tried the 1.0.2 sources, but couldn't even get the default distribution
to work right).
At this stage I can live with the default distribution, but I of course
can't configure any of the devices at all, which basically limits me
to two serial ports, one ethernet card, and no GATEWAY forwarding,
which is painful to put it lightly. Help!
Thanks for your time.
Erich Boleyn
--
"I haven't lost my mind; I know exactly where it is."
/ -- Erich Stefan Boleyn -- \ --=> *Mad Genius wanna-be* <=--
{ Honorary Grad. Student (Math) }--> Internet E-mail: <erich@cs.pdx.edu>
\ Portland State University / WARNING: INTERESTED AND EXCITABLE