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 1QvACy-0007pj-8l for garchives@archives.gentoo.org; Sun, 21 Aug 2011 15:45:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9F27D21C035; Sun, 21 Aug 2011 15:44:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 45E3021C253 for ; Sun, 21 Aug 2011 15:43:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id B53FC1B4035 for ; Sun, 21 Aug 2011 15:43:05 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Score: -4.954 X-Spam-Level: X-Spam-Status: No, score=-4.954 required=5.5 tests=[AWL=1.645, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvWmqk1TRLsP for ; Sun, 21 Aug 2011 15:42:58 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id EFA881B401D for ; Sun, 21 Aug 2011 15:42:55 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QvAAo-0005XC-2c for gentoo-user@gentoo.org; Sun, 21 Aug 2011 17:42:54 +0200 Received: from athedsl-378610.home.otenet.gr ([79.131.30.240]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 21 Aug 2011 17:42:54 +0200 Received: from realnc by athedsl-378610.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 21 Aug 2011 17:42:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: Suspend to RAM caused crashes Date: Sun, 21 Aug 2011 18:43:16 +0300 Organization: Lucas Barks Message-ID: References: <201108211127.57077.michaelkintzios@gmail.com> <201108211319.40825.francesco.talamona@know.eu> 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-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: athedsl-378610.home.otenet.gr User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110705 Thunderbird/5.0 In-Reply-To: X-Archives-Salt: X-Archives-Hash: 51ed8a96511aa703b9c47f064ce75718 On 08/21/2011 06:33 PM, Mark Knecht wrote: > On Sun, Aug 21, 2011 at 8:12 AM, Nikos Chantziaras 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 :*)