From owner-freebsd-stable Mon Jun 19 5:42:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id 9D70337BCEE for ; Mon, 19 Jun 2000 05:42:23 -0700 (PDT) (envelope-from lowell@world.std.com) Received: from world.std.com (lowell@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id IAA26082 for ; Mon, 19 Jun 2000 08:42:21 -0400 (EDT) Received: (from lowell@localhost) by world.std.com (8.9.3/8.9.3) id IAA12359; Mon, 19 Jun 2000 08:42:21 -0400 (EDT) To: freebsd-stable@freebsd.org Subject: Re: Desperate : make buildworld NEVER works!!!!! References: <200006190031.e5J0Vun21038@ptavv.es.net> From: Lowell Gilbert Date: 19 Jun 2000 08:42:21 -0400 In-Reply-To: "Kevin Oberman"'s message of Sun, 18 Jun 2000 17:31:56 -0700 Message-ID: Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin Oberman" 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