Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!newshost.marcam.com!usc!math.ohio-state.edu!howland.reston.ans.net!xlink.net!zib-berlin.de!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: freebsd and parity errors
Date: 18 Jul 1995 11:22:34 +0200
Organization: Private U**x site, Dresden.
Lines: 17
Message-ID: <3ufugq$7mc@bonnie.tcd-dresden.de>
References: <3ubksg$rmv@agate.berkeley.edu>
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
john doe #1 <jdoe@fusion.net> wrote:
>freebsd 2.0 gives me annoying parity errors quite a bit. 2.0.5 gives me
>them so early on in the install process that i cannot even install. none
>of my dos/win software seems to have a problem using the memory, and yet
>bsd seems to. i have 8 megs and an 8 meg swap drive, and it sometimes
>crashes with me doing fewer things than edit a couple of files in vi and
>logging in from another console.
dos/win doesn't count. Parity errors _are_ hardware. Relax your
memory timing, or swap your SIMMs.
Sorry, certainly not the kind of help you've expected to get...
--
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. ;-)