*BSD News Article 44928


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!ieunet!maths.tcd.ie!maths.tcd.ie!not-for-mail
From: tim@maths.tcd.ie (Timothy Murphy)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Slight flame from Linux user
Date: 3 Jun 1995 12:05:36 +0100
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.
Lines: 29
Message-ID: <3qpfm0$76j@bell.maths.tcd.ie>
References: <3ql3gd$je2@bell.maths.tcd.ie> <3qp02d$eqb@news1.best.com>
NNTP-Posting-Host: bell.maths.tcd.ie

cpage@best.com (Chad Page) writes:

>: Having had some problems ("fatal signal 11" syndrome)
>: on my Linux Pentium, I thought I'd try FreeBSD
>: to see if it behaved better.

>	Fatal signal 11 syndrome is almost always a HARDWARE PROBLEM - 
>usually a memory error.  Check your memory settings - set them to slower 
>settings, then disable the level 2 cache if you have to.

There has been a long (and ongoing) discussion on the Linux groups
about this.
While the general opinion (including mine) is that the problem
is hardware-based, a minority believe it is a problem with gcc.
[Even if it is a RAM problem, it is conceivable
that the kernel might pick it up and correct it.]

In my case -- and I think, for most people --
the problem only arises when re-compiling the kernel
or re-compiling gcc.
Some people claim that it only occurs when using gcc 2.6.?,
and that reverting to 2.5.8 will solve it.
So it is conceivable that the problem might not arise with FreeBSD.

-- 
Timothy Murphy  
e-mail: tim@maths.tcd.ie
tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland