From: "Jeff Rollin" <jeff.rollin@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Help - system reboots while compiling
Date: Mon, 12 Feb 2007 18:03:56 +0000 [thread overview]
Message-ID: <8a0028260702121003p299c445bnb1caf441d10d3d73@mail.gmail.com> (raw)
In-Reply-To: <200702121924.40966.alan@linuxholdings.co.za>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
On 12/02/07, Alan McKinnon <alan@linuxholdings.co.za> wrote:
>
> On Monday 12 February 2007, Matt Richards wrote:
> > I wouldn't of thought it would be the RAM not from behavior like that
> > but it does sound like a overheating issue, I have had computers just
> > power off because they get too hot.
>
> The thing with memtest is that it does (mostly) predictable tests, which
> can detect consistent errors with memory chips, or somewhat random
> errors with memory.
>
> BUT, it doesn't help at all with detecting didgy hardware in other
> areas. It doesn't give you any valid tests for what happens when the
> machine gets hot for example. Compiling a kernel (or openoffice.org) 10
> times in a loop does do that.
It does look like it's a problem with the PSU or (God forbid) the cpu. ("God
forbid" because new CPU means new motherboard also).
So, I would say that you have shown that your memory chips are not
> likely to be faulty, but you have not yet proven that the cpu (or the
> rest of the machine) isn't getting hot and overloading.
>
> Jeff, if you were paying me to diagnose your problem, I'd be telling you
> to swap out the psu and test some more, then disassemble the
> cpu/heatsink combination and replace the thermal grease and test some
> more. If it then fails, the tests are still not conclusive so I would
> want to forcefully cool the machine (with an external fan etc) while
> putting it through some stress tests (like a looooooong compile).
Well at the moment it doesn't even survive the early stages of a short
compile (the ./configure stage) so hopefully if any progress at all is made
at diagnosing the problem, it'll be quick. Unfortunately if I were paying
you to diagnose the problem I'd also have enough money to buy spare PSU's -
but I'm not!
Jeff
--
Now, did you hear the news today?
They say the danger's gone away
But I can hear the marching feet
Moving into the street
Adapted from Genesis, "Land of Confusion"
http://latedeveloper.org.uk
[-- Attachment #2: Type: text/html, Size: 2663 bytes --]
next prev parent reply other threads:[~2007-02-12 18:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 8:36 [gentoo-user] Help - system reboots while compiling Jeff Rollin
2007-02-11 8:57 ` William Kenworthy
2007-02-11 9:34 ` Philip Webb
2007-02-11 14:10 ` Andrey Gerasimenko
2007-02-11 11:11 ` Hemmann, Volker Armin
2007-02-11 20:00 ` Jeff Rollin
2007-02-11 15:32 ` Kent Fredric
2007-02-11 19:57 ` Jeff Rollin
2007-02-11 20:15 ` Hemmann, Volker Armin
2007-02-12 7:42 ` Alan McKinnon
2007-02-12 8:57 ` Mark Kirkwood
2007-02-12 9:13 ` Dave Rea
2007-02-12 10:16 ` Alan McKinnon
2007-02-12 10:34 ` Mark Kirkwood
2007-02-12 15:37 ` Dan Farrell
2007-02-12 15:43 ` Jeff Rollin
2007-02-12 16:12 ` Matt Richards
2007-02-12 17:24 ` Alan McKinnon
2007-02-12 18:03 ` Jeff Rollin [this message]
2007-02-12 16:46 ` Hemmann, Volker Armin
2007-02-12 17:09 ` Andrey Gerasimenko
2007-02-12 18:07 ` Jeff Rollin
2007-03-27 0:05 ` Jeff Rollin
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=8a0028260702121003p299c445bnb1caf441d10d3d73@mail.gmail.com \
--to=jeff.rollin@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