public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mariusz Pękala" <skoot@qi.pl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc seg faults very often
Date: Mon, 22 Aug 2005 23:48:11 +0200	[thread overview]
Message-ID: <20050822214811.GA25045@cthulhu.sdi.tpnet.pl> (raw)
In-Reply-To: <18244.12.159.90.110.1124722667.squirrel@mail.utkalika.net>

On 2005-08-22 10:57:47 -0400 (Mon, Aug), R'twick Niceorgaw wrote:
> 
> I also had the same gcc segfault problem recently. After some observation,
> I found out whenever cpu temperature goes beyond 50 C I was getting
> segfaults. Took out the heat sink and cpu, cleaned them put some arctic
> silver between cpu and heat sink and put a fan in front of the box and did
> a emerge -Uv world  without any problem even though temperature reached
> 65. I believe, its the arctic silver that I put between cpu and heat sink
> fixed my problem.

I am in the middle of troubleshooting similiar (lockups, not segfaults) situation.
Maybe it will be of some use to somebody.

During some emerges my machine was getting locked up when cpu temperature got
above 55 C (AMD Athlon 2GB), but I decided (yeah - decided ;-) that CPU is not the
problem - 55 C is pretty low for CPU I think.

As a workaround I have limited the RAM amount available (I have 512 MB
physical) to 256 MB by kernel parameter mem=256M. No RAM errors were detected by
memtest, but limiting available RAM works - no lockups.

The 'sensors' utility (part of lm_sensors package) shows that one (out of two)
temperature sensor is a bit too hot: it has now (no emerge in progress)
61 C and warning threshold is on 48 C. I assume that it is not CPU that
gets too hot but that small, nice north bridge on my mobo.

May it be that the solution is to get some bigger heat sink and more
powerful fan not only for CPU.

HTH


-- 
No virus found in this outgoing message.
Checked by "grep -i virus $MESSAGE"
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-08-22 21:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 17:27 [gentoo-user] gcc seg faults very often Raphael Melo de Oliveira Bastos Sales
2005-08-22 18:42 ` Richard Fish
2005-08-22 19:29   ` Raphael Melo de Oliveira Bastos Sales
2005-08-22 14:57     ` R'twick Niceorgaw
2005-08-22 20:28       ` Raphael Melo de Oliveira Bastos Sales
2005-08-22 15:46         ` R'twick Niceorgaw
2005-08-22 20:53           ` Raphael Melo de Oliveira Bastos Sales
2005-08-22 20:37         ` Volker Armin Hemmann
2005-08-22 21:48       ` Mariusz Pękala [this message]
2005-08-23  2:01         ` Raphael Melo de Oliveira Bastos Sales
2005-08-22 19:51     ` Volker Armin Hemmann
2005-08-22 20:33       ` Raphael Melo de Oliveira Bastos Sales
2005-08-23 13:03       ` Raphael Melo de Oliveira Bastos Sales
2005-08-23 15:03         ` Eugene Rosenzweig
2005-08-23 16:49           ` Volker Armin Hemmann
  -- strict thread matches above, loose matches on Subject: below --
2005-08-23 21:24 Michael Kintzios
2005-08-24  0:16 ` Raphael Melo de Oliveira Bastos Sales
2005-08-24  2:53   ` Volker Armin Hemmann
2005-08-24 13:04     ` Raphael Melo de Oliveira Bastos Sales
2005-08-24 16:18       ` Raphael Melo de Oliveira Bastos Sales

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=20050822214811.GA25045@cthulhu.sdi.tpnet.pl \
    --to=skoot@qi.pl \
    --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