From: Paolo Ornati <ornati@fastwebnet.it>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@osdl.org>,
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 16:38:46 +0200 [thread overview]
Message-ID: <20060328163846.272af289@localhost> (raw)
In-Reply-To: <20060328163027.1e755745@localhost>
On Tue, 28 Mar 2006 16:30:27 +0200
Paolo Ornati <ornati@fastwebnet.it> wrote:
> I'm re-testing with 2.6.15.6 --> it is compiling by some hours without
> a single segfault.
Maybe I've exagerated here, it is finished now:
real 106m35.548s
user 56m11.111s
sys 33m48.371s
No problems as expected.
--
Paolo Ornati
Linux 2.6.15.6 on x86_64
next prev parent reply other threads:[~2006-03-28 14:37 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
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 [this message]
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=20060328163846.272af289@localhost \
--to=ornati@fastwebnet.it \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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