From owner-freebsd-stable Fri Sep 22 9: 8:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cmh-dial.columbus.rr.com (cmh-dial.columbus.rr.com [204.210.252.23]) by hub.freebsd.org (Postfix) with ESMTP id 9F57E37B42C; Fri, 22 Sep 2000 09:08:05 -0700 (PDT) Received: from columbus.rr.com (dhcp16466029.columbus.rr.com [24.164.66.29]) by cmh-dial.columbus.rr.com (8.9.3/8.9.3) with ESMTP id MAA25561; Fri, 22 Sep 2000 12:07:14 -0400 (EDT) Message-ID: <39CB8507.F9F786BB@columbus.rr.com> Date: Fri, 22 Sep 2000 12:12:55 -0400 From: Bill Moran X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-smp@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Whats is this? FBSD 4.1 isn't stable! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 20-Sep-00 O. Hartmann wrote: > > not happen! I think not to have faulty hardware, because this server runs now > > for about 2 and a half year without any hardware fault! > > So? Hardware goes bad. I.e., it works fine for a while, and then > *wham* it breaks one day. In fact, your hardware could have already been > somewhat marginal to begin with, and the stress of making world may have > caused something to overheat and cause the hardware to break, esp. memory > or CPU. Bad memory and CPU's often cause Sig 11's. To add my $.02 to this. We generally consider hardware suspect after 2 years of heavy use (servers, for example) simply because it's seen 17000 hours of use. Equipment does wear out, and depending on the actual usage, a 2 year old server can easily be scrap (especially when it's plugged into the same circuit as the air conditioning ... stupid clients - I didn't say that!) -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message