Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uchinews!vixen.cso.uiuc.edu!howland.reston.ans.net!xlink.net!rz.uni-karlsruhe.de!news.uni-ulm.de!news.belwue.de!fu-berlin.de!cs.tu-berlin.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.0.5 Problems?
Date: 3 Jul 1995 16:22:49 +0200
Organization: Private U**x site, Dresden.
Lines: 56
Message-ID: <3t8ufp$4ee@bonnie.tcd-dresden.de>
References: <3t7464$hg4@calweb.calweb.com>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Robert Du Gaue <rdugaue@web2.calweb.com> wrote:
>The main problem still is that I'm getting spontanous reboots, about 3-4 times
>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.
>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.
>Jul 2 00:29:54 web2 /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice
>Jul 2 00:29:55 web2 /kernel: sd0: start 32, end 2056007, size 2055976
>Jul 2 00:29:55 web2 /kernel: sd0d: start 0, end 2056007, size 2056008
You cannot use the `d' partition since it points to outside the BSD
slice. You have to refer to the whole disk by the slice notation now
(sd0s2 in your case), see also the slice.hlp file on the boot floppy.
>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?
You can un-bloat the kernel by building a custom kernel and removing
all the non-existent device drivers.
>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'')
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)