From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 6 Sep 2010 08:25:12 +0200 (CEST) Date: Mon, 6 Sep 2010 08:25:12 +0200 From: Heinz Diehl Message-ID: <20100906062512.GB7939@fancy-poultry.org> References: <4C80F647.9080500@gmail.com> <4C80FEE7.3030508@redhat.com> <20100903181429.GA11768@tansi.org> <4C822A32.8080308@gmail.com> <4C838E6E.9010303@gmail.com> <4C83C874.2030103@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C83C874.2030103@redhat.com> Subject: Re: [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 06.09.2010, Milan Broz wrote: > welcome to the club - this is at least 5th report which was caused > by broken RAM :-) A lot of new Gigabyte boards have something called "dynamic overclocking". It's difficult to discover at this is enabled by default. This leads to higher voltage for the CPU and RAM, and of course more GHz, which can give the same symptoms as bad RAM (and get the memtest86 to fail in the same way). I have a Gigabyte MA770-UD3 myself, and it's a quite fantastic board, rockstable and reliable, AFTER I set the clockspeed and voltage for both CPU and RAM to "manual" :-) I had the same symptoms before...