From owner-freebsd-questions@FreeBSD.ORG Wed Jul 21 15:02:22 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CF681065673 for ; Wed, 21 Jul 2010 15:02:22 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id EC7C78FC08 for ; Wed, 21 Jul 2010 15:02:21 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o6LF2LJJ061408; Wed, 21 Jul 2010 08:02:21 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C470BFD.5060600@rawbw.com> Date: Wed, 21 Jul 2010 08:02:21 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100708 Thunderbird/3.0.5 MIME-Version: 1.0 To: Peter Holm References: <4C46A956.3080700@rawbw.com> <20100721145618.GA35893@x2.osted.lan> In-Reply-To: <20100721145618.GA35893@x2.osted.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Are kernel stress test results displayed online? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2010 15:02:22 -0000 On 07/21/2010 07:56, Peter Holm wrote: > There's not much to report, but if you have spare time you could run > the test your self. Different HW is always a good test parameter. > Does this mean that there were no failures at all for years? The reason why I asked was because I started getting system freezes on 8.1-PRERELEASE under heavy use. Before, 8.0-STABLE was very stable under the same load. So I remembered about kernel stress tests in case they might have higher failure rate after some recent 8.1 changes. But of course there are other factors like, possible NVidia driver updates or maybe memory getting bad, etc. Yuri