From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QvA4B-0005uW-9a for garchives@archives.gentoo.org; Sun, 21 Aug 2011 15:36:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EE1C821C23D; Sun, 21 Aug 2011 15:35:54 +0000 (UTC) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.216.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 89B4421C262 for ; Sun, 21 Aug 2011 15:33:48 +0000 (UTC) Received: by qyk38 with SMTP id 38so962483qyk.19 for ; Sun, 21 Aug 2011 08:33:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=4ng36ugOu4re8SYC0ilFy25iczYgaJ+hQZ+aG4I/6n0=; b=soWGQlnjDgKnOS/aYkjD1eY6l50cf/QX7NJGYDHYorgn27Vneos1IIQ2CtKpHzLNQ6 vxJKMig6e9+hEBw6LPcuT3WvJAxCFgCTKJKc5x05jQjCwlYNWcSIIPTZHtFOSlE3E+Ol tsDTIicq3VsprvrtGI3V6rdqJIGU8RnP4m5YQ= 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.224.210.132 with SMTP id gk4mr895919qab.79.1313940827913; Sun, 21 Aug 2011 08:33:47 -0700 (PDT) Received: by 10.224.74.13 with HTTP; Sun, 21 Aug 2011 08:33:47 -0700 (PDT) In-Reply-To: References: <201108211127.57077.michaelkintzios@gmail.com> <201108211319.40825.francesco.talamona@know.eu> Date: Sun, 21 Aug 2011 08:33:47 -0700 Message-ID: Subject: Re: [gentoo-user] Re: Suspend to RAM caused crashes From: Mark Knecht To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 997dcabd185bbf22ecff2abdacc381b8 On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras wrote: > On 08/21/2011 02:19 PM, Francesco Talamona wrote: >> >> =C2=A0I wish yours it's not a RAM >> issue, it could be tricky to spot, because memtest is not putting any >> load to the machine, so it's very useful when it reports error, but when >> it doesn't you can't be sure if RAM modules are in good health. > > CPU load doesn't affect RAM errors. =C2=A0CPU load affects CPU errors. = =C2=A0If you > only get RAM errors during heavy load, the RAM is just fine, but your CPU > has a fault. Unless the CPU loading causes excessive heat and the RAM has problems only when it gets hot. In general semiconductor speeds slow down as temperature increases so a RAM that's barely in spec at room temp could be out of spec at high temp. Just an idea. - Mark