All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: ornati@fastwebnet.it, linux-kernel@vger.kernel.org
Subject: Re: Random GCC segfaults -- Was: [2.6.16] slab error in slab_destroy_objs(): cache `radix_tree_node'...
Date: Tue, 28 Mar 2006 00:41:37 -0800	[thread overview]
Message-ID: <20060328004137.607e51db.akpm@osdl.org> (raw)
In-Reply-To: <20060328095521.52ea3424@localhost>

Paolo Ornati <ornati@fastwebnet.it> wrote:
>
>  On Sun, 26 Mar 2006 21:53:46 +0200
>  Paolo Ornati <ornati@fastwebnet.it> wrote:
> 
>  > PS: I've got another "gcc segfault" trying to build Qt again after a
>  > reboot but I don't think this is a memory problem (actually I have
>  > a memory problem (single bit error) but it should be cured with
>  > memmap=1K$214014K ;).
> 
>  I've got others NON reproducible gcc segfaults, usually compiling some
>  huge CPP source.

If those errors had no corresponding kernel messages then what you have is
a classic symptom of failing memory hardware.  Suggest you grab memtest86,
run it for 24 hours.


  reply	other threads:[~2006-03-28  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 19:53 [2.6.16] slab error in slab_destroy_objs(): cache `radix_tree_node' Paolo Ornati
2006-03-28  7:55 ` Random GCC segfaults -- Was: " Paolo Ornati
2006-03-28  8:41   ` Andrew Morton [this message]
2006-03-28  9:22     ` Paolo Ornati
2006-03-28 11:48       ` Paolo Ornati
2006-03-28 13:23       ` Pavel Machek
2006-03-28 14:30         ` Paolo Ornati
2006-03-28 14:38           ` Paolo Ornati
2006-03-31 14:55           ` Random GCC segfaults --> Just Bad Memory Paolo Ornati

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=20060328004137.607e51db.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ornati@fastwebnet.it \
    /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.