From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Fri, 31 Dec 2004 10:58:29 +0100 [thread overview]
Message-ID: <m3hdm2lrga.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <Pine.LNX.4.58.0412301418521.22893@ppc970.osdl.org> (Linus Torvalds's message of "Thu, 30 Dec 2004 14:23:01 -0800 (PST)")
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
|| On Thu, 30 Dec 2004 14:23:01 -0800 (PST)
|| Linus Torvalds <torvalds@osdl.org> wrote:
lt> Ok. This is apparently a slab cache corruption issue.
So we're one step further, it seems.
lt> Can you compile with SLAB_DEBUG and DEBUG_PAGEALLOC turned on,
lt> since that may well catch something in the act (or it may make
lt> the machine so unusably slow that it's not funny - who knows..)
Did that last night. You are right -- it is so slow that it is no fun
at all. So I started the test run last night and went to bed.
This morning, the machine had crashed again, but unlike the noisy
crashes, when there was output on the console, this time, with
debugging compiled in, it crashed entirely silently. There was no info
on the console and none in the syslog, it just stopped.
Anything else I can try to help?
Anyone else willing to join the slab corruption bug hunt? :)
Regards,
Georg
--
Georg C. F. Greve <greve@fsfeurope.org>
Free Software Foundation Europe (http://fsfeurope.org)
GNU Business Network (http://mailman.gnubiz.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-31 10:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:31 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King
2004-12-31 9:58 ` Georg C. F. Greve [this message]
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 10:21 Nick Warne
2004-12-31 11:46 Manfred Spraul
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=m3hdm2lrga.fsf@reason.gnu-hamburg \
--to=greve@fsfeurope.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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