From: Dave Jones <davej@redhat.com>
To: Tommy Faasen <tommy@zwanebloem.nl>
Cc: linux-kernel@vger.kernel.org, linux-gcc@vger.kernel.org
Subject: Re: BUG: 2.6.0 non fatal recoverable errors crash gcc
Date: Fri, 2 Jan 2004 00:52:24 +0000 [thread overview]
Message-ID: <20040102005224.GA18361@redhat.com> (raw)
In-Reply-To: <3FF4B3E7.9050309@zwanebloem.nl>
On Fri, Jan 02, 2004 at 12:57:27AM +0100, Tommy Faasen wrote:
> I'm not subscribed to this newsgroup, but i'll try to read the follow-up
> messages if any.
>
> When my machine is doing big compiles like the kernel or mythtv ,
> gcc/g++ crashes.
> This happens after syslog tell me that there is a recoverable error
> (see output below).
> This happened several times but I don't know why and what I can do about
> it ..
> The machine seems to be very stable, but it could be a hardware problem
> i guess.
It is. MCE's are an early sign of hardware going flaky.
Inadequate power, poor cooling etc can also trigger them.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2004-01-02 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 23:57 BUG: 2.6.0 non fatal recoverable errors crash gcc Tommy Faasen
2004-01-02 0:52 ` Dave Jones [this message]
2004-01-02 1:27 ` Eric
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=20040102005224.GA18361@redhat.com \
--to=davej@redhat.com \
--cc=linux-gcc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tommy@zwanebloem.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.