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 1MCwH3-0000DC-7L for garchives@archives.gentoo.org; Sat, 06 Jun 2009 13:49:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6B10AE0212; Sat, 6 Jun 2009 13:49:27 +0000 (UTC) Received: from puchmayr.linznet.at (puchmayr.linznet.at [80.66.46.165]) by pigeon.gentoo.org (Postfix) with ESMTP id E622DE0212 for ; Sat, 6 Jun 2009 13:49:26 +0000 (UTC) Received: (qmail 11403 invoked by uid 210); 6 Jun 2009 13:49:26 -0000 Received: from zeus.puchmayr.linznet.at by hephaestos (envelope-from , uid 201) with qmail-scanner-2.05st (clamdscan: 0.94.2/9433. spamassassin: 3.2.1. perlscan: 2.05st. Clear:RC:1(192.168.1.2):. Processed in 0.103623 secs); 06 Jun 2009 13:49:26 -0000 Received: from zeus.puchmayr.linznet.at (192.168.1.2) by hephaestos.puchmayr.linznet.at with SMTP; 6 Jun 2009 13:49:25 -0000 From: Alexander Puchmayr To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel freezes Date: Sat, 6 Jun 2009 15:49:24 +0200 User-Agent: KMail/1.9.10 References: <200906061033.53197.alexander.puchmayr@linznet.at> <200906061242.38397.alexander.puchmayr@linznet.at> <200906061302.07353.volkerarmin@googlemail.com> In-Reply-To: <200906061302.07353.volkerarmin@googlemail.com> Organization: Fa Linznet 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="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906061549.24837.alexander.puchmayr@linznet.at> X-Archives-Salt: 1f0db83c-cad8-4345-8625-868670272542 X-Archives-Hash: 56204368f934d35a65fae2445c782b7f Am Samstag 06 Juni 2009 schrieb Volker Armin Hemmann: > > > > If the problem persists, start testing your hardware. > > > > How? I don't have access to special test equipment to test hardware. > > This is the only AM2(+) board and the only AM2 CPU I have. The RAM is > > also unique to this machine. > > > > > I would suspect the PSU. > > > > The Powersupply? What makes you think that the PSU can be the cause of > > a system crash? > > experience. A PSU gone bad can cause all kind of bad behaviour. Crash > under load. Crash when temps rise. Sudden reboots, harddisk damage. Mobo > dead. CPU dead. Seriously I have seen so many problems caused by PSUs > over the years that the PSU is always the first thing I check.... > > Ram is the easiest: get systemrescuecd, boot from cd, run memtest for a > couple of hours. If it finds errors, bingo, you found the probable > culprit. In that case raising the memory voltage a tine bit (0.05 or > 0.1Volt) could be all that is needed (I have such a memory stick myself. > 1.80V and I have crashes. 1.85V and everything works). > But memory errors also can be caused by bad PSU. So.. ask a friend for a > psu or your local hardware dealer if they can lend you one - if your > problems go away with a different PSU you found the real source. > Also, cleaning all parts (even the psu's inside) might solve the problem, > maybe it is still heat related. > > While your box is open, check all capacitor's for bulges, especially on > the top, discolorment and stuff around their base. Also remove all cards > and addons and put them back, make sure that they really sit correctly. > > You are running the latest bios, of course? > Luckily the PSU of my desktop was new enough to fit to that board -- I've tried, and after roughly half an hour it crashed again. Same symptoms. Nothing changed :-( Memtest86+ has already been running for one night lately -- no errors found. The caps are all OK and the board is clean, as I bought it just one week ago. Maybe its best to talk with my hardware dealer about it, as there is warranty on it. Thanks for your help Alex