From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 16 00:35:27 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AE4516A4CE for ; Tue, 16 Mar 2004 00:35:27 -0800 (PST) Received: from smtp.octapharma.se (smtp.octapharma.se [195.198.168.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F28243D2D for ; Tue, 16 Mar 2004 00:35:26 -0800 (PST) (envelope-from Mikael.Gunnarsson@octapharma.se) Received: from sestosrv004p.ad.octapharma.se ([195.198.13.61] RDNS failed) by smtp.octapharma.se with Microsoft SMTPSVC(5.0.2195.6713); Tue, 16 Mar 2004 09:38:31 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Tue, 16 Mar 2004 09:35:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Multiprocessor system VS one processor system Thread-Index: AcQLJdnxaxqxsWUrSaCB73U3PGaT1AACwz4w From: "Gunnarsson, Mikael" To: X-OriginalArrivalTime: 16 Mar 2004 08:38:31.0906 (UTC) FILETIME=[10115C20:01C40B32] Subject: RE: Multiprocessor system VS one processor system X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2004 08:35:27 -0000 > With our Servers (dual and quad), if a CPU becomes defective > and ca= uses > a crash, when the Server reboots, it will mark the CPU > off-l= ine and use > the other CPU. That makes it redundant. And that is, for= anyone > considering their Server to be of prime importance, a hell of= > lot better > than waiting for a replacement of the same cpu with t= he same stepping. Is CPUs breaking down a real problem? During my 20+ = years of fiddling with computers (professionally and hobby-wise) I don't = think I've ever had a CPU spontaneously become defective when it was runn= ing under normal conditions.. Then again, maybe I've just been lucky. = MG This email and any files transmitted with it are confidential and i= ntended solely for the use of the individual or entity to whom they are a= ddressed. If you have received this email in error please notify the syst= em manager. This message contains confidential information and is intende= d only for the individual named. If you are not the named addressee you s= hould not disseminate, distribute or copy this e-mail.