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 1QvBqL-0000lf-Qm for garchives@archives.gentoo.org; Sun, 21 Aug 2011 17:29:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1F41221C39D; Sun, 21 Aug 2011 17:29:34 +0000 (UTC) Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A274421C38A for ; Sun, 21 Aug 2011 17:28:11 +0000 (UTC) Received: by bkd1 with SMTP id 1so4490145bkd.40 for ; Sun, 21 Aug 2011 10:28:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:content-type; bh=fOrEK8MMhPJxvqfp60nn4FpKbcsFrJhJK4dvqRGyrWw=; b=mYDZUpAOGGjHa+eI9qq1bHdZE06S9qTUvR+y8XoA5ZSTdeUKik0AB6wTGZO+UJNb+o d9miRIiPCAZ08Jn34F6zCG7/Bg8FjCBfx98VZ1bHb/SJDXywEJFhHThhPscJAWXupKpf 2Sbi+qyEOrPCRh2sdy4ewCxCMTzDaXHz51KAc= Received: by 10.204.152.218 with SMTP id h26mr547009bkw.196.1313947690836; Sun, 21 Aug 2011 10:28:10 -0700 (PDT) Received: from localhost.localnet (p4FC74ED1.dip0.t-ipconnect.de [79.199.78.209]) by mx.google.com with ESMTPS id y8sm1656655bks.21.2011.08.21.10.28.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Aug 2011 10:28:10 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Suspend to RAM caused crashes Date: Sun, 21 Aug 2011 19:28:02 +0200 Message-ID: <1888184.U23JXUQFA5@localhost> User-Agent: KMail/4.7.0 (Linux/3.0.1; KDE/4.7.0; x86_64; ; ) In-Reply-To: References: <201108211127.57077.michaelkintzios@gmail.com> 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 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-15" X-Archives-Salt: X-Archives-Hash: 9e3790458f0c6de5431eb4027f97074a Am Sonntag 21 August 2011, 19:26:47 schrieb Nikos Chantziaras: > On 08/21/2011 07:08 PM, Mark Knecht wrote: > > On Sun, Aug 21, 2011 at 8:43 AM, Nikos Chantziaras= =20 wrote: > >> On 08/21/2011 06:33 PM, Mark Knecht wrote: > >>> On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras > >>>=20 > >>> wrote: > >>>> On 08/21/2011 02:19 PM, Francesco Talamona wrote: > >> [...] > >>=20 > >> The RAM gets hot when there's RAM load (meaning being used heavily= ), > >> not > >> when there's CPU load :*) > >=20 > > Do you feel heat when your PC is turned on and running hard? Of cou= rse > > 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. No= t > > 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'. > >=20 > > 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 mig= ht > > go out of spec... >=20 > On a laptop maybe. On a desktop, the air around the RAM modules get > maybe 1 degree C warmer (I know because I have temp sensor there, > connected to the front panel). me too - and the direction of air flow from the cpu cooler plus the war= mth of=20 the air can change the temperature of the ram sticks by 5=B0C. So... No, not 'laptop maybe'. >=20 > When it does get warm is when there's GPU and disk load. Those sucke= rs > combined can raise the temp inside the box by 5-6 degrees. those can raise it even more. >=20 > The meaning of all this is that if memtest can't find any errors afte= r a > full run (which can take an hour), the chances of getting an > error = that > is really related to RAM under CPU stress are very slim. a full run is more than 24h. Everything shorter is only of worth if you= =20 already hit errors after a few minutes. --=20 #163933