From: "René Rebe" <rene@exactcode.de>
To: linux-kernel@vger.kernel.org
Subject: Re: gcc randomly crashes on my PowerBook with recent kernels...
Date: Thu, 13 Jan 2005 20:17:37 +0100 [thread overview]
Message-ID: <C93FAD39-6597-11D9-BBEE-000393AF911C@exactcode.de> (raw)
In-Reply-To: <20050113185453.GA10195@havoc.gtf.org>
Hi,
On 13. Jan 2005, at 19:54 Uhr, David Eger wrote:
> I apologize for the vagueness of the message, but for all ye TiBook
> users,
> over the last couple months of kernels, I've noticed gcc (various
> versions
> in the 3.0 series randomly), non-deterministically crashing on large
> builds.
>
> The builds tend to be fine and complete immediately after a reboot.
> I've replaced my RAM recently, and the problem happened before and
> after
> the replacement so I don't *think* it's the RAM.
>
> Has anyone seen this sort of weird corruption behavior? I don't know
> where or how to start debugging this. Could be anything... bad
> drivers,
> bad builds of gcc.. Any ideas? (and if you suggest d/ling a stock
> compiler, instructions for doing this in gentoo would be appreciated
> ;-) )
My T2 (www.t2-project.org) PowerPC systems tend to be rock solid - I
only once managed to get random memory corruption when I tried out
PREEMPTION. BenH mentioned PREEMPTION and ReiserFS (I use) might not
play that well - at least not on PowerPC.
I had yet no time to review the affected code myself - however without
PREEMPTION all is well.
Yours,
--
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://www.exactcode.de | http://www.exactcode.de/t2
+49 (0)30 255 897 45
next prev parent reply other threads:[~2005-01-13 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 18:54 David Eger
2005-01-13 19:17 ` René Rebe [this message]
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
2005-01-13 21:56 Nick Warne
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=C93FAD39-6597-11D9-BBEE-000393AF911C@exactcode.de \
--to=rene@exactcode.de \
--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
Powered by JetHome