From owner-freebsd-doc  Tue Sep 19 10:59:57 2000
Delivered-To: freebsd-doc@freebsd.org
Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8C3C437B42C; Tue, 19 Sep 2000 10:59:51 -0700 (PDT)
Received: (from nik@localhost)
	by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8JHtw612268;
	Tue, 19 Sep 2000 18:55:58 +0100 (BST)
	(envelope-from nik)
Date: Tue, 19 Sep 2000 18:55:52 +0100
From: Nik Clayton <nik@freebsd.org>
To: Steve Roome <steve@sse0691.bri.hp.com>
Cc: freebsd-doc@freebsd.org, James Housley <jim@thehousleys.net>,
	Mark Ovens <marko@freebsd.org>
Subject: Re: signal 11 faq entry
Message-ID: <20000919185552.B12114@canyon.nothing-going-on.org>
References: <20000919165723.D8111@moose.bri.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20000919165723.D8111@moose.bri.hp.com>; from steve@sse0691.bri.hp.com on Tue, Sep 19, 2000 at 04:57:23PM +0100
Organization: FreeBSD Project <URL:http://www.freebsd.org/>
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Sep 19, 2000 at 04:57:23PM +0100, Steve Roome wrote:
> Following a recent discussion on -stable, I've got a revised entry for
> the signal 11 section in the FAQ, and I'm asking for a bit of
> feedback, I've not cc'd to -stable for fear of things getting out of
> hand, again, which is what I was hoping to avert in the future.

Not bad.  I'd probably expand I couple of sections.

   [...]
   bits of code.

   In particular, a dead giveaway that this is *not* a FreeBSD bug is if
   you see the problem when you're compiling a program, but the activity
   that the compiler's carrying out changes each time.

   For example, suppose you're running "make buildworld", and the
   compile fails trying to compile ls.c in to ls.o.  If then run "make
   buildworld" again, and the compile fails in the same place then this
   is a broken build -- try updating your sources and try again.  If the
   compile fails elsewhere then this is almost certainly hardware.

   [...]

   In the case of b) you will need to verify that it's not your hardware
   that's at fault.

   Common causes of this include:

     1.  Hard disks running too hot.  Check the fans in your case.

     2.  The processor running too hot.  This might be because you've 
	 overclocked the processor (in which case, stop doing that).  Or
	 the fan on the processor might have died.

     3.  Dodgy memory, and/or motherboards.  If you have multiple memory
	 SIMMS installed then pull one out and try again.  If everything
	 works now then you've got a bad SIMM.  If it fails again, pull
	 out another chip, and so on, until you identify the SIMM.

	 Some motherboards are also known to have problems if you fill
	 up all the memory banks.

   [...]

What do you think?

N
-- 
Internet connection, $19.95 a month.  Computer, $799.95.  Modem, $149.95.
Telephone line, $24.95 a month.  Software, free.  USENET transmission,
hundreds if not thousands of dollars.  Thinking before posting, priceless.
Somethings in life you can't buy.  For everything else, there's MasterCard.
  -- Graham Reed, in the Scary Devil Monastery


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message