Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!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: compiling on 2.0.5/950622-SNAP reboots my pc
Date: 10 Jul 1995 10:02:31 +0200
Organization: Private U**x site, Dresden.
Lines: 20
Message-ID: <3tqmqn$bsj@bonnie.tcd-dresden.de>
References: <3tiflh$ra2@uuneo.neosoft.com> <3tj5nv$qrq@bonnie.tcd-dresden.de> <3tk874$c7j@uuneo.neosoft.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
Chris Origer <ctoriger@starbase.neosoft.com> wrote:
>Not sure. Don't think this is the problem. Even with the cache disabled
>the machine will still reboot. I was hoping maybe it was the soundcard, nope.
>My setup works perfectly under Linux (and dos for that matter). Everything
>has been deconflicted.
Weird. Looks similar to the problem somebody had with Linux. He's
getting constantly SIGSEGV's when compiling under Linux but not under
FreeBSD. Anyway, all this looks like RAM problems, even though it's
weird. Hellmuth Michaelis has been reporting similar weird things
recently. For an HP Vectra, he could succesfully boot the FreeBSD
installation floppy, but somewhere in the installation process, the
box simply froze. After disabling and pulling almost everything
except the RAM and the mainboard, he finally decided to change the
SIMMs, too, and this helped. (Dos and Windoze ran fine, of course. :)
--
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. ;-)