From owner-freebsd-questions@FreeBSD.ORG Tue Jun 2 15:22:23 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F55A106566C for ; Tue, 2 Jun 2009 15:22:23 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id B9F6D8FC16 for ; Tue, 2 Jun 2009 15:22:22 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n52FMJed001453; Tue, 2 Jun 2009 17:22:19 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n52FMIl0001450; Tue, 2 Jun 2009 17:22:19 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Tue, 2 Jun 2009 17:22:18 +0200 (CEST) From: Wojciech Puchar To: Chris Nicholls In-Reply-To: <20090602115602.GA29137@atsuko> Message-ID: References: <20090601185419.GA92199@atsuko> <54837285@bb.ipt.ru> <20090602115602.GA29137@atsuko> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: IBM x345 Dual 2.8Ghz Xeon poor performance X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 15:22:23 -0000 >> constantly doing ECC that's why it was damn slow. >> >> anyway - can hardware give any info for OS about how often ECC corrects >> errors? > This feels like the right track, I'll run memtest86 on it later tonight. > if i'm right memtest86 will not detect anything as too - all errors get corrected. for example - on your DIMM with 72-bit bus (64+8) one pin is dirty and is not connected well. then you'll get a single bit error every few reads/writes, and all will be corrected. If you can disable ECC - do it, and then run memtest so it will detect errors. If you can't, remove all but one DIMM, check if speed improved, if so, remove this and put other DIMM etc.. until you'll find what is bad. Or maybe it will then work fine because it's just contact problem.