Date: Mon, 18 Sep 2000 18:16:59 +0100 From: Mark Ovens <marko@freebsd.org> To: James Housley <jim@thehousleys.net> Cc: Steve Roome <steve@sse0691.bri.hp.com>, freebsd-stable@freebsd.org Subject: Re: Makeworld is dying... Message-ID: <20000918181659.F567@parish> In-Reply-To: <39C62A86.3F7108F7@thehousleys.net>; from jim@thehousleys.net on Mon, Sep 18, 2000 at 10:45:26AM -0400 References: <39C42DF4.978A63C@urx.com> <Pine.LNX.4.10.10009170918240.13465-100000@shark.harmonic.co.il> <20000917160006.D67912@wantadilla.lemis.com> <20000918154418.P8111@moose.bri.hp.com> <39C62A86.3F7108F7@thehousleys.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 18, 2000 at 10:45:26AM -0400, James Housley wrote: > Steve Roome wrote: > > > > > > So could we change the text (something like, but better worded than > > the following) in the FAQ, e.g. : > > You should submit it as a PR. Ideally we'd like the SGML diffs, but the plain text will do if you can't provide SGML. > > 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! > > > I like it because it also give some simple, usefully ways to verify the > problem. > > Jim > -- > microsoft: "where do you want to go today?" > linux: "where do you want to go tomorrow?" > BSD: "are you guys coming, or what?" -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000918181659.F567>