From: Volker Armin Hemmann <volkerarmin@googlemail.com>
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 [thread overview]
Message-ID: <1888184.U23JXUQFA5@localhost> (raw)
In-Reply-To: <j2rbj5$njq$1@dough.gmane.org>
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<realnc@arcor.de>
wrote:
> >> On 08/21/2011 06:33 PM, Mark Knecht wrote:
> >>> On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras<realnc@arcor.de>
> >>>
> >>> wrote:
> >>>> On 08/21/2011 02:19 PM, Francesco Talamona wrote:
> >> [...]
> >>
> >> 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...
>
> 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 warmth of
the air can change the temperature of the ram sticks by 5°C. So...
No, not 'laptop maybe'.
>
> When it does get warm is when there's GPU and disk load. Those suckers
> combined can raise the temp inside the box by 5-6 degrees.
those can raise it even more.
>
> The meaning of all this is that if memtest can't find any errors after 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
already hit errors after a few minutes.
--
#163933
next prev parent reply other threads:[~2011-08-21 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 10:27 [gentoo-user] Suspend to RAM caused crashes Mick
2011-08-21 11:19 ` [gentoo-user] " Francesco Talamona
2011-08-21 11:42 ` Mick
2011-08-21 11:57 ` [gentoo-user] " Pandu Poluan
2011-08-21 12:37 ` Mick
2011-08-21 15:12 ` [gentoo-user] " Nikos Chantziaras
2011-08-21 15:22 ` Volker Armin Hemmann
2011-08-21 15:33 ` Mark Knecht
2011-08-21 15:43 ` Nikos Chantziaras
2011-08-21 16:08 ` Mark Knecht
2011-08-21 16:26 ` Nikos Chantziaras
2011-08-21 17:27 ` Mark Knecht
2011-08-21 17:28 ` Volker Armin Hemmann [this message]
2011-08-22 4:54 ` Francesco Talamona
2011-08-21 12:53 ` [gentoo-user] " Volker Armin Hemmann
2011-08-21 15:30 ` meino.cramer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1888184.U23JXUQFA5@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox