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 1QvAbJ-00045Z-Ua for garchives@archives.gentoo.org; Sun, 21 Aug 2011 16:10:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D337F21C266; Sun, 21 Aug 2011 16:10:03 +0000 (UTC) Received: from mail-qw0-f53.google.com (mail-qw0-f53.google.com [209.85.216.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 6F4FE21C03A for ; Sun, 21 Aug 2011 16:08:11 +0000 (UTC) Received: by qwb7 with SMTP id 7so3302408qwb.40 for ; Sun, 21 Aug 2011 09:08:11 -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=8hm0/RKuzs8IBwLWY8D/Np5XvRralSE0ZHtBIM+Yd4E=; b=tGqFvUWnR16y2tuUY8MBWZhsDM3ugQ+VT7Avcl++XS3IaokdtbjTFDn+8/dvNLMuzj NrJKdJzK7RtFeVUU9G35FtM6Str1mm2bMFR1fomenQpOXA0pCkGbRHGEH2dc/jqrlZ4+ XmMBCVtDGdjdGLbhCJw8+mV/UUn7pxwO0iE38= 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.200.3 with SMTP id eu3mr788016qab.279.1313942890733; Sun, 21 Aug 2011 09:08:10 -0700 (PDT) Received: by 10.224.74.13 with HTTP; Sun, 21 Aug 2011 09:08:10 -0700 (PDT) In-Reply-To: References: <201108211127.57077.michaelkintzios@gmail.com> <201108211319.40825.francesco.talamona@know.eu> Date: Sun, 21 Aug 2011 09:08:10 -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: 116c45dad9330a63ff6bd4eb6b5f261d On Sun, Aug 21, 2011 at 8:43 AM, Nikos Chantziaras wrote: > On 08/21/2011 06:33 PM, Mark Knecht wrote: >> >> On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras >> =C2=A0wrote: >>> >>> 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 wh= en >>>> 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 C= PU >>> has a fault. >> >> Unless the CPU loading causes excessive heat and the RAM has problems >> only when it gets hot. > > The RAM gets hot when there's RAM load (meaning being used heavily), not > when there's CPU load :*) Do you feel heat when your PC is turned on and running hard? Of course you do. The whole machine heats up. The CPU under load heats the machine so the RAM and drives and everything else heats up also. Not as hot as the CPU, but it heats up. So I might agree with you - the RAM might not be 'hot', but it would certainly be 'warmer'. I'm not suggesting that this would cause a normal DRAM stick to go bad, but only that if he had a very marginal bit of RAM that it might go out of spec... - Mark