From owner-freebsd-questions@FreeBSD.ORG Mon Apr 5 21:34:13 2010 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 4CAE11065672; Mon, 5 Apr 2010 21:34:13 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.freebsd.org (Postfix) with ESMTP id CA8BA8FC22; Mon, 5 Apr 2010 21:34:12 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c122-106-253-149.belrs3.nsw.optusnet.com.au [122.106.253.149]) by mail18.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o35LY7sA012308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Apr 2010 07:34:09 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id o35LY6xr044391; Tue, 6 Apr 2010 07:34:06 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id o35LY5E0044390; Tue, 6 Apr 2010 07:34:05 +1000 (EST) (envelope-from peter) Date: Tue, 6 Apr 2010 07:34:05 +1000 From: Peter Jeremy To: Jeremie Le Hen Message-ID: <20100405213404.GA44109@server.vk2pj.dyndns.org> References: <20100404082033.GW40253@felucia.tataz.chchile.org> <20100404215455.GZ40253@felucia.tataz.chchile.org> <20100405004034.GB2915@server.vk2pj.dyndns.org> <20100405102012.GA40253@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: <20100405102012.GA40253@felucia.tataz.chchile.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-CMAE-Score: 0 Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Intel D945GSE vs Zotac ION ITX (was: Support for Zotac MB with nVidia ION chipset) 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: Mon, 05 Apr 2010 21:34:13 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Apr-05 12:20:12 +0200, Jeremie Le Hen wrote: >Nonetheless I'm a little worried by what you said about the lack of ECC. >Computers has been used for years before ECC came out and obviously they >worked :). Not really. Most early computers had fairly extensive error detecting hardware. Early microprocessors didn't because the novelty of getting an entire on a CPU on a chip was enough. Most 486 based PCs supported parity RAM but maufacturers and end-users found they could save pennies by leaving the parity bits off. ECC support was a requirement for building servers with microprocessors and some support has trickled down to the desktop. It hasn't been really popular because wider memory costs more and most people want the fastest, cheapest system possible to make their games render faster. Occasional glitches don't matter. With the current generation of CPUs, Intel appear to have made a marketing decision to not support ECC on their desktop CPUs - if you want ECC, you need to user a server-grade CPU (with a much greater profit margin). AMD have gone the other way and have have ECC support in all their x64 chips except mobile ones. You are still at the mercy of motherboard manufacturers who decide to not include the tracks between the DIMM sockets and the CPU. > Do you really think it might happen to be a problem? There's no way to know. Definitely, the added error checking in ZFS have resulted in a number of "ZFS kept reporting errors and I found I actually had bad hardware even though I've been using it for years" reports. > Would an Intel board would compensate for this? No. The memory controller is embedded in the Atom and doesn't support ECC. If you decide to go the ECC path, you need to pick a different CPU. --=20 Peter Jeremy --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAku6V0wACgkQ/opHv/APuIc7rwCgtGJTBH/KLDxbx7OoDl7LhDdA OmMAn1CISDdxUcvzap7y+GGckmRDIOx/ =h9ys -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--