From owner-freebsd-stable@FreeBSD.ORG Wed May 25 15:20:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A647816A41C for ; Wed, 25 May 2005 15:20:01 +0000 (GMT) (envelope-from jpp@cloudview.com) Received: from skipjack.no-such-agency.net (skipjack.no-such-agency.net [64.142.114.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B60643D53 for ; Wed, 25 May 2005 15:20:01 +0000 (GMT) (envelope-from jpp@cloudview.com) Received: from skipjack.no-such-agency.net (localhost [127.0.0.1]) by skipjack.no-such-agency.net (Postfix) with ESMTP id 10A4D34DA11; Wed, 25 May 2005 08:20:01 -0700 (PDT) Received: from [192.168.2.120] (blackhole.no-such-agency.net [64.142.103.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skipjack.no-such-agency.net (Postfix) with ESMTP id D16C734D435; Wed, 25 May 2005 08:20:00 -0700 (PDT) Message-ID: <429497A0.7020402@cloudview.com> Date: Wed, 25 May 2005 08:20:00 -0700 From: John Pettitt User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Filip Lenaerts References: <20050525072122.GA7569@xor.obsecurity.org> In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AV-Checked: by skipjack Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_5_4 panic 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: Wed, 25 May 2005 15:20:01 -0000 Filip Lenaerts wrote: > > hi all, > > tnx very much for reply, kris, stefan and thomas. i was also > thinking/fearing for a hardware error. the reason why i didn't > investigate sooner is that over the past two years i was running > 5.0-RC2 and after that followed current. i always assumed that that > could be the reason, but when i reverted a month ago to 5.4-RELEASE > and now RELENG_5_4 aka stable, the problem stayed ... plus my kernel > debugging skills are very limited - hence learned again :) > > so HW failure. now the only thing to do is convince our IT dep that > it is broken and ask a new one. the problem is that they only support > windows and they go frantic when they see linux, let alone BSD :) so > the probably want to put the blame on the OS iso the HW. wish me luck :) > > tnx again guys! > > filip > Get a copy of memtest86 (see http://www.memtest86.com/ for a bootable ISO) - it'sd a stand along memory diagnostic that ahppens to put a reasonable load on the cpu too - with some luck it will show up the problem and they won't be able to blame BSD (plus it's a good tool to have anyway). John