From: Dan Foster <dsf@gblx.net>
To: Tim Wojtulewicz <Tim.Wojtulewicz@NAU.EDU>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Panic while building XFree86
Date: Wed, 19 Jul 2000 12:18:42 -0400 [thread overview]
Message-ID: <20000719121842.A17734@frontiernet.net> (raw)
In-Reply-To: <p04301800b59b829649df@[209.147.134.139]>; from Tim.Wojtulewicz@NAU.EDU on Wed, Jul 19, 2000 at 09:07:37AM -0700
Hot Diggety! Tim Wojtulewicz was rumored to have wrote:
>
> I've been trying to compile XFree86 4.0.1 recently (tried 4 times
> already) and my computer keeps throwing kernel panics whenever I do
> so. It usually happens after the compile has been going for a while.
> I think it has something to do with the fan coming/not coming on, but
Sounds exactly like it. Run, don't walk, and fix that :)
kernel panics due to compiler failure tend to indicate either a flaky
motherboard (found one with substandard traces, VRM, etc) or more commonly,
an overheated CPU; fan failure is a real common cause for this. Tends to
get exercised with compiling large stuff - kernel, XFree86, mozilla, etc
as it heats up and experiences bit flips. (hence, invalid locations,
instruction pointer running in wrong places, insta-crash)
This isn't a Linux specific problem per se; I've seen it with BSD boxes, too.
-Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-19 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 16:07 Panic while building XFree86 Tim Wojtulewicz
2000-07-19 16:18 ` Dan Foster [this message]
2000-07-19 16:31 ` Benjamin Herrenschmidt
2000-07-19 19:31 ` Tim Wojtulewicz
2000-07-20 3:05 ` Chris Leishman
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=20000719121842.A17734@frontiernet.net \
--to=dsf@gblx.net \
--cc=Tim.Wojtulewicz@NAU.EDU \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).