From owner-freebsd-stable@FreeBSD.ORG Mon Jul 28 19:52:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A4B3106566B for ; Mon, 28 Jul 2008 19:52:46 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 717658FC08; Mon, 28 Jul 2008 19:52:44 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <488E238D.5010807@FreeBSD.org> Date: Mon, 28 Jul 2008 21:52:45 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Kostik Belousov References: <488CACD9.7060002@queldor.net> <488CBB02.1020105@FreeBSD.org> <488CBBAC.7040507@queldor.net> <488CC13F.1020204@FreeBSD.org> <20080727190742.GF97161@deviant.kiev.zoral.com.ua> <488CD9AB.8040401@queldor.net> <20080727204339.GG97161@deviant.kiev.zoral.com.ua> <488CFCC3.2030504@queldor.net> <20080728101840.GK97161@deviant.kiev.zoral.com.ua> <488DFEF7.5000802@queldor.net> <20080728194024.GM97161@deviant.kiev.zoral.com.ua> In-Reply-To: <20080728194024.GM97161@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Michael Toth , Michael toth Subject: Re: 7.0 Crashing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2008 19:52:46 -0000 Kostik Belousov wrote: > On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote: >> I had someone run a Dell Diags CD on the machine and it passed all tests. >> >> Before that it core'd again; here is the backtrace from that one. >> >> Is there any other want (maybe in freebsd) to test the hardware better? >> and/or should I submit a bug report for this? > Sure, you can submit bug report. From my POV, there is actually no > data to resolve it. i.e. you should have no expectation that anyone else will be able to resolve it either. Note that diagnostics can tell you when a machine has failed, but can never tell you when a machine is working perfectly. Kris > > You may use memtest86 (Google for it) for memory/chipset/cpu cache > test.