From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 18ABE1381F3 for ; Wed, 14 Nov 2012 02:33:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83BAB21C065; Wed, 14 Nov 2012 02:32:58 +0000 (UTC) Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F40DE21C061 for ; Wed, 14 Nov 2012 02:29:29 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id k31so24522qat.19 for ; Tue, 13 Nov 2012 18:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=9gbxBu6VU2kQkN8ikQa3qVqI9nDx3Yf9ih1O0WXUXLY=; b=Upwgg86iPPwyyBYfng5HbtKEFCZd7kPS4Itchzh2zNcsLtjDU5mXW9NfxZysAGzfSE zcKf0yO+qZYKAbBBt/tGvnkJznAolA9BnZcP5MD0N8MkeCiZbX0v653BeXpOMBR7Omj1 xrekobIn+jGtKc2eLNvmNFG6XP/4e67edPc42ayi3pK4NvdHmpsURBpYnany9S/3xyM4 ZKY/n2q0QLo+4S24i+6NNHOgznupEgq+Zh14T1NDtMWGiJHNq+09zIainBKlIUlTfvpH vdPcZ0Iqsa6LH4cW9FDKQGum9nHXcuvWcsdkmz0ygsVD5ylTZKnEI2P5AZQ5x6oI21i8 OPNw== Received: by 10.229.136.140 with SMTP id r12mr5832342qct.90.1352860169131; Tue, 13 Nov 2012 18:29:29 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.49.75.74 with HTTP; Tue, 13 Nov 2012 18:28:48 -0800 (PST) In-Reply-To: <3565939.551UseeY9y@blacky> References: <50A2EF85.4040301@gmail.com> <3565939.551UseeY9y@blacky> From: Willie Date: Tue, 13 Nov 2012 18:28:48 -0800 Message-ID: Subject: Re: [gentoo-user] Unexpected Power Loss! To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=00248c711781cfd71104ce6b4df3 X-Archives-Salt: 33e710a7-4b7a-440b-b336-49b6b7e703f6 X-Archives-Hash: 28a12ff5962ad7c9957447bfd935d26a --00248c711781cfd71104ce6b4df3 Content-Type: text/plain; charset=ISO-8859-1 I thought about that one also. I didn't have any errors. On Tue, Nov 13, 2012 at 5:28 PM, Sascha Cunz wrote: > > > I'm sure you will get lots of ideas on this one tho. There can be a lot > > of causes. > > RAM failure could be another one, which "could randomly vanish for a while > when using another memory layout" (like in using another operating system). > > So, I'd suggest to boot up a memory tester and let it run over night. > > Sascha > > -- Willie Matthews matthews.willie@gmail.com --00248c711781cfd71104ce6b4df3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I thought about that one also. I didn't have any errors.

On Tue, Nov 13, 2012 at 5:28 PM, Sascha Cunz <s= ascha-ml@babbelbox.org> wrote:

> I'm sure you will get lots of ideas on this one tho. =A0There can = be a lot
> of causes.

RAM failure could be another one, which "could randomly vanish f= or a while
when using another memory layout" (like in using another operating sys= tem).

So, I'd suggest to boot up a memory tester and let it run over night.
Sascha




--
Willie Matthews
matthews.willie@gmail.com
--00248c711781cfd71104ce6b4df3--