From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: gcc randomly crashes on my PowerBook with recent kernels...
Date: Thu, 13 Jan 2005 21:56:13 +0000 [thread overview]
Message-ID: <200501132156.13504.nick@linicks.net> (raw)
I do not run said machine, but I did have GCC crashes under similar large
builds (notably the kernel) on one of my boxes.
It turned out the CPU was overheating and investigation revealed the heatsink
paste was dried out (it is an old box, circa 1998 since paste was applied).
As I only loaded the thing during GCC builds is why the problem revealed it's
self. A new heatsink and paste fixed it.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2005-01-13 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 21:56 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 18:54 gcc randomly crashes on my PowerBook with recent kernels David Eger
2005-01-13 19:17 ` René Rebe
2005-01-14 22:19 ` Denis Vlasenko
[not found] ` <9679B50C-6597-11D9-BBEE-000393AF911C@exactcode.de>
[not found] ` <20050116000756.GA11442@havoc.gtf.org>
[not found] ` <69DC51E6-6756-11D9-9044-000393AF911C@exactcode.de>
2005-01-23 21:51 ` David Eger
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=200501132156.13504.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.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