From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LYro8-0004Vz-0w for garchives@archives.gentoo.org; Mon, 16 Feb 2009 00:58:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E5EFFE032A; Mon, 16 Feb 2009 00:57:58 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 507D5E032A for ; Mon, 16 Feb 2009 00:57:58 +0000 (UTC) Received: from zaphod.digimed.co.uk (zaphod.digimed.co.uk [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id EB0B2470D3F for ; Mon, 16 Feb 2009 00:57:53 +0000 (GMT) Date: Mon, 16 Feb 2009 00:57:48 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] spontaneous reboots.. what to look for Message-ID: <20090216005748.19d4c858@zaphod.digimed.co.uk> In-Reply-To: <87wsbrs1vv.fsf@newsguy.com> References: <87wsbrs1vv.fsf@newsguy.com> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.0cvs64 (GTK+ 2.14.7; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 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: multipart/signed; boundary="Sig_/+..LA0QfCt67h8lZG0s.Yu3"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 548c9599-f9e6-40fd-92cf-fb162d0e8815 X-Archives-Hash: 5ddd43256d9b564c8604110c2b984b10 --Sig_/+..LA0QfCt67h8lZG0s.Yu3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 15 Feb 2009 17:42:44 -0600, Harry Putnam wrote: > 2) checking how hot the cpu is getting (Doesn't appear to be a > problem) But now running a cron job recording temperatures every 10 > minutes. So that may turn up something. You could also check disk temperatures with app-admin/hddtemp. I've had random crashes due to an overheating drive before. I'd also run smartctl (emerge smartmontools) over the drive, just to be sure. memtest is a must, bad RAM can easily cause crashes, and take Volker's advice on PSUs. --=20 Neil Bothwick What if there were no hypothetical situations? --Sig_/+..LA0QfCt67h8lZG0s.Yu3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEARECAAYFAkmYuhAACgkQum4al0N1GQMXLACgsWXoH1zKy7p//la2Yu9uWfld dU0AoKGbzxU1wMNfXD+aU/oPxrTp0FxG =6N6d -----END PGP SIGNATURE----- --Sig_/+..LA0QfCt67h8lZG0s.Yu3--