*BSD News Article 46360


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!decwrl!pagesat.net!calweb!web1.calweb.com!rdugaue
From: rdugaue@web1.calweb.com (Robert Du Gaue)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.0.5 Problems?
Date: 4 Jul 1995 01:05:53 GMT
Organization: Calweb Communications, Sacramento's affordable Internet provider.
Lines: 51
Message-ID: <3ta45h$quq@calweb.calweb.com>
References: <3t7464$hg4@calweb.calweb.com> <3t8ufp$4ee@bonnie.tcd-dresden.de>
NNTP-Posting-Host: web1.calweb.com
X-Newsreader: TIN [version 1.2 PL2]

: >a day. No warning as far as I can tell and nothing in the log file
: >other then the startup messages that tells me a reboot occurred.

: Do you have ppp connections?  I think there's a problem if a ppp
: connection drops but the (stale) route is still existent.

Nope, no PPP connections handled through the machine. All PPP stuff
is handled at the PortMaster level.


: >Also, I've just noticed this new error that I haven't seen
: >before:
: >
: >------
: >Jul  2 09:16:11 web2 /kernel: vnode_pager_input: I/O read error
: >Jul  2 09:16:11 web2 /kernel: vm_fault: pager input (probably hardware) error, PID 2699 failure
: >------
: >What's up with this? Never seen this until I upgraded. Do I have a hardware
: >problem????

: Looks like.  Note that pager IO errors for critical data (important
: processes) might also cause serious trouble.

So what hardware first to check/swap?

: >Jul  1 18:30:26 web2 /kernel: 1 3C5x9 board(s) on ISA found at 0x300
: >Jul  1 18:30:27 web2 /kernel: ep0 at 0x300-0x30f irq 10 on isa
: >Jul  1 18:30:27 web2 /kernel: ep0: aui/bnc/utp[*UTP*] address 00:20:af:26:bf:be irq 10

: Your kernel is rather bloated, and i think the ep-style cards can be
: offended by other device drivers probing address 0x300.  This is
: described somewhere in the hardware documentation, followed by the
: advice to disable all other drivers at address 0x300 -- didn't you
: read this?

Yep, and disabled conflicting NICs already.

: You can un-bloat the kernel by building a custom kernel and removing
: all the non-existent device drivers.

I did the disable, but I'll unbloat the kernel for good measure...

: >Jul  1 18:30:29 web2 /kernel: sd0s2: rejecting partition in BSD label: it isn't entirely within the slice
: >Jul  1 18:30:29 web2 /kernel: sd0s2: start 32, end 2056007, size 2055976
: >Jul  1 18:30:29 web2 /kernel: sd0s2d: start 0, end 2056007, size 2056008
:                                    ^
: This is the slice number.  (FreeBSD ``slice'' == FDISK ``partition'')

How do I setup a new HD? Seems the only way I see is via sysinstall, but that wants you to do alot of other stuff. Is there an easier way simular to 
sysinstall that doesn't require me to learn all about disks drives and internal
formats? (IE Fdisk by itself is abit complex).