Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!Germany.EU.net!nntp.gmd.de!nntp.darmstadt.gmd.de!news.th-darmstadt.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: 5 Jul 1995 09:31:01 +0200
Organization: Private U**x site, Dresden.
Lines: 38
Message-ID: <3tdf3l$e4l@bonnie.tcd-dresden.de>
References: <3t7464$hg4@calweb.calweb.com> <3t8ufp$4ee@bonnie.tcd-dresden.de> <3ta45h$quq@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@web1.calweb.com> wrote:
>: >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?
Some disk? Have you ever seen disk error notifications in the syslog?
>: Your kernel is rather bloated, and i think the ep-style cards can be
>: offended by other device drivers probing address 0x300.
>
>Yep, and disabled conflicting NICs already.
Not only NICs. Everything probing at 0x300 (i think the Mitsumi CDROM
driver is a know offender).
>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).
I don't know any. Jordan is going to improve sysinstall to make it
ready for all such stuff. Last time i've setup a new disk, i also had
to fiddle around allot with fdisk and disklabel, and i think it didn't
go off the ground without setting up an entry in /etc/disktab.
--
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. ;-)