Date: 19 Jun 2000 08:42:21 -0400 From: Lowell Gilbert <lowell@world.std.com> To: freebsd-stable@freebsd.org Subject: Re: Desperate : make buildworld NEVER works!!!!! Message-ID: <rd67lblkfki.fsf@world.std.com> In-Reply-To: "Kevin Oberman"'s message of Sun, 18 Jun 2000 17:31:56 -0700 References: <200006190031.e5J0Vun21038@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kevin Oberman" <oberman@es.net> writes:
> It seems odd that we have had at least a half dozen reports of signal
> 11s during buildworld over the past 3 days. I have the same problem
> with my K6-2 system. The hardware has been rock solid for months, but
> I now can't buildworld without a "signal 11" exactly as has been
> reported here. Very suspicious, at least.
Well, some of those cases were the known (and documented -- and, for
that matter, fixed) bugs in 3.4-R's install procedure. When you
discount those, I don't think we've seen an unusual number of such
reports. If the segv's were occuring in the same place, that could
indicate a problem with FreeBSD itself, but if they occur in different
places on each run through a buildworld, you have pretty conclusive
proof that it's a question of flaky hardware.
A lot of FreeBSD installs are on cheap hardware. In fact, it's hard
to buy PC-class hardware that qualifies as dependable by traditional
server standards. So we're stuck with a pretty high rate of reports
of hardware problems. It's one thing for my Windows game box to be
tolerant of memory problems, but I don't *want* my FreeBSD machines to
do the same.
Be well.
Lowell Gilbert
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?rd67lblkfki.fsf>