From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Computer turn itself off
Date: Sun, 24 May 2015 00:11:09 +0100 [thread overview]
Message-ID: <201505240011.11465.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20150523225332.GH2096@syscon7>
[-- Attachment #1: Type: Text/Plain, Size: 2180 bytes --]
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
> >>
> >> 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
>
> I tried to read the lm-sensors again and the compupter turn crash with the
> readings:
>
> fan1: 0 RPM (min = 10 RPM) ALARM
> fan2: 0 RPM (min = 0 RPM)
> fan3: 0 RPM (min = 0 RPM)
> fan5: 0 RPM (min = 0 RPM)
> temp1: +47.0°C (low = +127.0°C, high = +127.0°C) sensor =
> thermistor temp2: +106.0°C (low = +127.0°C, high = +70.0°C)
> sensor = thermal diode temp3: +106.0°C (low = +127.0°C, high =
> +127.0°C) sensor = thermistor cpu0_vid: +1.250 V
>
> I'm suspecting it is power supply.
I wouldn't trust these numbers. You probably need a different/correct driver
in your kernel to measure your CPU and MoBo chipset readings and/or a later
BIOS firmware.
Whenever I had such problems they were down to bad memory (some PCs are rather
particular in only accepting matching memory modules) and also down to a sick
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
capacitors. A few cents later and with a soldering iron in hand you should be
able to fix any cheap capacitor induced failure.
Of course if the machine is hundreds of miles away, attending to it is more of
a problem.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-23 23:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 21:24 [gentoo-user] Computer turn itself off Joseph
2015-05-23 22:08 ` Zhu Sha Zang
2015-05-23 22:41 ` Joseph
2015-05-23 22:53 ` Joseph
2015-05-23 23:11 ` Mick [this message]
2015-05-24 0:52 ` Zhu Sha Zang
2015-05-24 1:12 ` [gentoo-user] [SOLVED] " Joseph
2015-05-24 9:09 ` Mick
2015-05-24 9:25 ` Dale
2015-05-24 9:50 ` Neil Bothwick
2015-05-24 10:01 ` Peter Humphrey
2015-05-24 10:11 ` Mick
2015-05-24 10:45 ` Peter Humphrey
2015-05-24 11:32 ` Mick
2015-05-24 11:37 ` Peter Humphrey
2015-05-24 19:19 ` Ed Martinez
2015-05-24 23:53 ` [gentoo-user] " James
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=201505240011.11465.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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