From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Suspend to RAM caused crashes
Date: Sun, 21 Aug 2011 18:43:16 +0300 [thread overview]
Message-ID: <j2r91i$7et$1@dough.gmane.org> (raw)
In-Reply-To: <CAK2H+ecLFPeJbtn9VWfSxY88+XkKypFr-x0ptyy3-WWRSTuvJA@mail.gmail.com>
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:
>>>
>>> I 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. CPU load affects CPU errors. If 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.
The RAM gets hot when there's RAM load (meaning being used heavily), not
when there's CPU load :*)
next prev parent reply other threads:[~2011-08-21 15:45 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 [this message]
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
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='j2r91i$7et$1@dough.gmane.org' \
--to=realnc@arcor.de \
--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