From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 250D3138CCF for ; Sat, 23 May 2015 23:11:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 369A9E094E; Sat, 23 May 2015 23:11:18 +0000 (UTC) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0457AE0932 for ; Sat, 23 May 2015 23:11:16 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so18798163wic.0 for ; Sat, 23 May 2015 16:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=nAGpgUP0uz/L5lfvcnDKY50pC+t/+qkNyikX15nrTBg=; b=plnHO1zFkg9eGd3blvPfe00rw7PnQPSTyYgnBe3Y2VoNH93WDI3ft+x37InA29klaJ /nRC+0fnuTrQvv0KBGt12WccwEdyqHNXyoQZgN3f5Q2NimFoxqiuVt/v7Xfp/dspU4V+ XKSscSYBf2ECocxtFDZd04TgzQvoshVoD8EMOalPT7h5N3Nr5Z7RHo6ZlRN/UqzKI3yR 4ov5kwnNSKVpYTil9QEBSJ5XzbLREgnY4fhZ2UTqu4BPp64qLOE1LHfCdjey1eEFMrj7 hOIFTdH75EbOZVhmvW668cFY7MopVGvZYJzuEmirAPTbCBaF5tvRywSEs3frmr2mwW4W F1aQ== X-Received: by 10.194.122.105 with SMTP id lr9mr27519245wjb.153.1432422675943; Sat, 23 May 2015 16:11:15 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id o5sm5066156wia.0.2015.05.23.16.11.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 May 2015 16:11:15 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Computer turn itself off Date: Sun, 24 May 2015 00:11:09 +0100 User-Agent: KMail/1.13.7 (Linux/3.18.12-gentoo; KDE/4.14.3; x86_64; ; ) References: <20150523212442.GC2096@syscon7> <5560FA71.8020501@yahoo.com.br> <20150523225332.GH2096@syscon7> In-Reply-To: <20150523225332.GH2096@syscon7> 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="nextPart9489861.0DhHqU3pD6"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201505240011.11465.michaelkintzios@gmail.com> X-Archives-Salt: e787f9ec-7ca1-4d28-bbf4-53cb556f78e4 X-Archives-Hash: e78743c01c21bddcb37ce2dfbcd4c233 --nextPart9489861.0DhHqU3pD6 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Saturday 23 May 2015 23:53:32 Joseph wrote: > On 05/23/15 18:08, Zhu Sha Zang wrote: > >On 05/23/2015 05:24 PM, Joseph wrote: > >> I have a box in a remote location (8-core CPU) and it turn itself off > >> during compiling > >>=20 > >> The box it connected to UPS. Is it power supply? > > > >Maybe. I have a problem like that when using high processing simulation > >with nvidia-cuda and the power supply protection was unable to keep a > >safe energy level then the system goes off. > > > >But, if the failure happens during compilation time can be a heat > >problem. Install lm_sensors and use something like that: "watch -n 1 > >sensors". > > > >If not, if the temperature stay at safe levels, maybe you have a RAM > >corruption. In this case, you'll need to use memtest86++ to check. > > > >Good Luck >=20 > I tried to read the lm-sensors again and the compupter turn crash with the > readings: >=20 > fan1: 0 RPM (min =3D 10 RPM) ALARM > fan2: 0 RPM (min =3D 0 RPM) > fan3: 0 RPM (min =3D 0 RPM) > fan5: 0 RPM (min =3D 0 RPM) > temp1: +47.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D +127.0=C2= =B0C) sensor =3D > thermistor temp2: +106.0=C2=B0C (low =3D +127.0=C2=B0C, high =3D = +70.0=C2=B0C)=20 > sensor =3D thermal diode temp3: +106.0=C2=B0C (low =3D +127.0=C2= =B0C, high =3D > +127.0=C2=B0C) sensor =3D thermistor cpu0_vid: +1.250 V >=20 > I'm suspecting it is power supply. I wouldn't trust these numbers. You probably need a different/correct driv= er=20 in your kernel to measure your CPU and MoBo chipset readings and/or a later= =20 BIOS firmware. Whenever I had such problems they were down to bad memory (some PCs are rat= her=20 particular in only accepting matching memory modules) and also down to a si= ck=20 power supply. Memetest86+ should tell you after some hours if something is amiss. The power supply problem will require opening it up and checking for domed= =20 capacitors. A few cents later and with a soldering iron in hand you should= be=20 able to fix any cheap capacitor induced failure. Of course if the machine is hundreds of miles away, attending to it is more= of=20 a problem. =2D-=20 Regards, Mick --nextPart9489861.0DhHqU3pD6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJVYQkPAAoJELAdA+zwE4YeM2wH/jK27FWxqN1ca5nt3ZPcJTCK YFuXX05nltmrNEVINDeK/3L+KVzQUN1+TYzJZtDnPTe3ugqism6pRccW58DLpJjH KvVfDU3pxti8hnLF01HXNolwTYwN4N4R7FgnLFOJWnW6BLxi/nE9H9uDev5K1FBJ QNIJ3DS0fGt5QoeQJiVH3yOzvqg9EQ2W7a2/szoMTCRCQ8Ox1oxb9tUa5p0V0JOc Na7uU06dzElTSYYgEKz7wHQKczEsSNh9JATVDtXqnvn84ZUk/OO7IJH/8ThvuWlx KRYYhnt2hIel8RQAMaeKjSXalhTxXDxiKBVCdMJhwV3u88ge2hdvjkPAFAVou8Y= =idHJ -----END PGP SIGNATURE----- --nextPart9489861.0DhHqU3pD6--