From owner-freebsd-stable@FreeBSD.ORG Wed May 23 21:31:41 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1381916A46D for ; Wed, 23 May 2007 21:31:41 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id A8B6D13C4B8 for ; Wed, 23 May 2007 21:31:39 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from [127.0.0.1] (Q7d08.q.ppp-pool.de [89.53.125.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 438EE12883F; Wed, 23 May 2007 23:31:33 +0200 (CEST) Message-ID: <4654C0C4.2030405@vwsoft.com> Date: Wed, 23 May 2007 23:31:32 +0100 From: Volker User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, rmiranda@digitalrelay.ca References: <200705230717.l4N7HuPW010071@lurza.secnetix.de> <465408F9.6080302@vwsoft.com> In-Reply-To: <465408F9.6080302@vwsoft.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: Subject: Re: ghosthunting: machine freeze 6.2R 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, 23 May 2007 21:31:41 -0000 talking to myself... ;) On 2007-05-23 10:27, Volker wrote: > Currently I'm watching this machine over the distance and waiting for the freeze... ...and the machine freeze came this afternoon. I've had a good dump of the network traffic and haven't seen any strange network traffic. Unfortunately three hours later, the machine died completely. It has been a hardware failure which came quietly. Sorry for the noise I've put on this list but when experiencing things like that, one has to think in all possible directions (I first thought about a DoS attack). Thx! Volker