From owner-freebsd-stable Mon Sep 18 7:41:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id 7527837B424 for ; Mon, 18 Sep 2000 07:41:06 -0700 (PDT) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id CB5EC17C4F; Mon, 18 Sep 2000 16:41:03 +0200 (METDST) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id PAA09818; Mon, 18 Sep 2000 15:41:02 +0100 (BST) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id PAA28237; Mon, 18 Sep 2000 15:44:18 +0100 (BST) (envelope-from steve) Date: Mon, 18 Sep 2000 15:44:18 +0100 From: Steve Roome To: Greg Lehey Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Makeworld is dying... Message-ID: <20000918154418.P8111@moose.bri.hp.com> Mail-Followup-To: Steve Roome , Greg Lehey , freebsd-stable@FreeBSD.ORG References: <39C42DF4.978A63C@urx.com> <20000917160006.D67912@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000917160006.D67912@wantadilla.lemis.com>; from grog@lemis.com on Sun, Sep 17, 2000 at 04:00:06PM +0930 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 17, 2000 at 04:00:06PM +0930, Greg Lehey wrote: > What you *should* do before sending out a reply like this is to check > whether it's really in the FAQ or not. It is > (http://www.freebsd.org/FAQ/troubleshoot.html#AEN1570): There's a lot of people who are quick to step up to the podium and proclaim that all these signal elevens are caused by bad RAM, or bad RAM settings. It *could* be a pointer arithmetic problem. The FAQ ought to comment on this, and from recent personal experience, the number of people who respond to these just quoting the FAQ gets more annoying each time, mainly because it's something that doesn't need to be said on the mailing lists... again. In this case, it is possibly bad hardware, so maybes it's a fair call, then again it can be caused by, e.g. freaky optimizations in gcc... So could we change the text (something like, but better worded than the following) in the FAQ, e.g. : Q: My programs occasionally die with Signal 11 ( or 10 ). A: Signal 11 errors are caused when your process has attempted to access memory which the operating system has not granted it access to. This could be caused by a number of different circumstances : a) Most likely, if you're developing it yourself it's buggy code. (We've all been there!) b) If it's a problem with part of the base FreeBSD system, it might be buggy code, but more often than not these problems are found long before us general FAQ readers get to use these bits of code. If these problems are only affecting you, it's probably bad hardware. In the case of a) you can use a debugger and find the point in the program which is attempting to access a bogus address and then fix it. [ you probably already know this if you're a programmer! ] In the case of b) You need to verify the settings on your motherboard. Checking for hardware you might be running slightly out of spec, too fast, or mismatched hardware. Often setting memory wait states too short will trigger random signal 11's. An overclocked CPU will possibly also exhibit strange or similar symptoms. Try running some memory testing programs, or do a make buildworld if you have the full source available for FreeBSD (after a few successful buildworlds it's probably safe to say the hardware is okay.). See the SIG11 FAQ (LINK) for more information. That's my idea for a rough draft anyway. I'm clearly illiterate though, please don't flame me for that! Steve, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message