Skip site navigation (1)Skip section navigation (2) 
Date:      Mon, 18 Sep 2000 10:45:26 -0400
From:      James Housley <jim@thehousleys.net>
To:        Steve Roome <steve@sse0691.bri.hp.com>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: Makeworld is dying...
Message-ID:  <39C62A86.3F7108F7@thehousleys.net>
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>
next in thread | previous in thread | raw e-mail | index | archive | help 

[-- Attachment #1 --]
Steve Roome wrote:
> 
> 
> 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!
> 
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?"
[-- Attachment #2 --]
0	*H
010	+0	*H
00-0
	*H
010	UZA10UWestern Cape10UDurbanville10
U
Thawte10UCertificate Services1(0&UPersonal Freemail RSA 1999.9.160
000831112533Z
010831112533Z0E10UThawte Freemail Member1"0 	*H
	jim@thehousleys.net00
	*H
032jƮNAM݂^o7۠FĄPYe	&p-Rj*D\:#IԄgI
'fťܾ)@gGcdɳ4Fq85b0]0qkR{Q0O0U0jim@thehousleys.net0U00U#0`fUXFa#Ì0
	*H
MM9Y’)rjyx\mI}JL"55.3$yQ[^6nڲY9)	t&]8?F@pMxM8a7H8[T9*b00}0
	*H
010	UZA10UWestern Cape10U	Cape Town10U
Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0)	*H
	personal-freemail@thawte.com0
990916140140Z
010915140140Z010	UZA10UWestern Cape10UDurbanville10
U
Thawte10UCertificate Services1(0&UPersonal Freemail RSA 1999.9.1600
	*H
0iZz]!#rLK~r$BRW{azr98e^eyvL>hput,O	1ArƦ]D.Mօ>lx~@эWs0FO7050U00U#0rIs4Uvr~wƲ0
	*H
kY1rr`HU{gapm¥7؝(V\uoƑlfq|ko!6-	-mƃRt\~
orzg,ksnΝc)	~U100010	UZA10UWestern Cape10UDurbanville10
U
Thawte10UCertificate Services1(0&UPersonal Freemail RSA 1999.9.16-0	+0	*H
	1	*H
0	*H
	1
000918144527Z0#	*H
	14g3R~! 6Hq=0R	*H
	1E0C0
*H
0*H
0+0
*H
@0
*H
(0
	*H
@r}E*8:(7z1o,4>tbeO%:%~U1pI'Ϥp=/M	#KYAr!<Kxg}C1]!8LCx;t8"

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C62A86.3F7108F7>