Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsfeeds.sol.net!news.maxwell.syr.edu!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Can hardware problems result in SIGSEGV and SIGBUS? Date: 16 Feb 1997 20:58:08 GMT Organization: Private BSD site, Dresden Lines: 27 Message-ID: <5e7sd0$qo0@uriah.heep.sax.de> References: <33074023.41C67EA6@gusw.dialup.fu-berlin.de> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:35620 Gunther Schadow <gunther@gusw.dialup.fu-berlin.de> wrote: > can you imagin a broken hardware as the cause of busy processes getting > killed rather randomly with SIGSEGV and SIGBUS? For some days now, I get Of course. Some Linux guy even setup a ``Sig 11 home page'' for this. > I am completely stucked! Do I have to replace > hardware components? A new processor? How can I test this, I mean, I do > not have the mony to buy a new i586/133 just to see that the new one > does not help. It's most likely not the CPU. The best test so far is still a ``make world'' of a FreeBSD source tree. It's very often bad RAM, RAM timing problems, bad cache problems, or (with older boards) problems with write-back cache policy on broken chipsets when using a busmaster DMA controller. You aren't perchance overclocking your CPU? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)