From owner-freebsd-stable@FreeBSD.ORG Mon Jun 26 22:28:27 2006 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 9D67A16A406 for ; Mon, 26 Jun 2006 22:28:27 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38D1944673 for ; Mon, 26 Jun 2006 22:03:00 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id B63C4C3BC; Mon, 26 Jun 2006 18:02:59 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id C5DC0C45D; Mon, 26 Jun 2006 18:02:55 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 595EDC43F; Mon, 26 Jun 2006 18:02:55 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:In-Reply-To:X-MimeOLE; b=hP4dw4bhIixvcUzRHAsYhNuIoPPkYjEuDIcIt7moStTsPm+B4MYZrXRuPERbrEbr2dmbc6UaY+j4FIW2ZLnPVVLy9tEIxLGEa5HoavhbfQ5ga+KNe5kfVHllr6wXbXRz; Received: from toshi (unknown [216.76.76.143]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by aaron.protected-networks.net (Postfix) with ESMTP id 7782BC3BC; Mon, 26 Jun 2006 18:02:54 -0400 (EDT) From: "Michael Butler" To: "'Wilko Bulte'" , "'M.Hirsch'" Date: Mon, 26 Jun 2006 18:02:38 -0400 Message-ID: <000001c6996c$3eab9df0$ad0d510a@toshi> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcaZaoQwOAXJPgLiRByNDv05oqNvLwAARXEw In-Reply-To: <20060626214535.GA94015@freebie.xs4all.nl> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Cc: freebsd-stable@freebsd.org Subject: RE: FreeBSD 6.x CVSUP today crashes with zero load ... 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, 26 Jun 2006 22:28:27 -0000 > Of course not. You only panic once you have no other options left. > Proper hardware with ECC give you these options. I am not talking > consumer grade crap here of course. I agree that no panic should occur if the error was correctable and it should when it isn't. However, *real* equipment will log a corrected error .. from an aging Dell 1-U server .. Handle 0x0024, DMI type 15, 33 bytes System Event Log Area Length: 4096 bytes Header Start Offset: 0x0000 Header Length: 16 bytes Data Start Offset: 0x0010 Access Method: Memory-mapped physical 32-bit address Access Address: 0xFFF33000 Status: Valid, Not Full Change Token: 0x00000000 Header Format: Type 1 Supported Log Type Descriptors: 5 Descriptor 1: POST error Data Format 1: POST results bitmap Descriptor 2: Parity memory error Data Format 2: Multiple-event Descriptor 3: I/O channel block Data Format 3: Multiple-event Descriptor 4: Single-bit ECC memory error Data Format 4: Multiple-event Descriptor 5: Multi-bit ECC memory error Data Format 5: Multiple-event .. So the logs are there, all that's required is a utility to read them and, optionally, alert the administrator to the event, Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net