All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alain Fauconnet <alain@cscoms.net>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org, lve@ns.aanet.ru
Subject: Re: UPD: Frequent/consistent panics in 2.4.19 at ip_route_input_slow, in_dev_get(dev)
Date: Tue, 22 Oct 2002 10:24:45 +0700	[thread overview]
Message-ID: <20021022102444.C2361@cscoms.net> (raw)
In-Reply-To: <200210211640.UAA07235@sex.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Mon, Oct 21, 2002 at 08:40:16PM +0400

On Mon, Oct 21, 2002 at 08:40:16PM +0400, kuznet@ms2.inr.ac.ru wrote:
> Hello!
> 
> > much   yet).   My   next   plan is to implement LKCD on the 2.4.17 box
> > (not available for 2.4.19 yet as it  seems)  and  capture  a  complete
> > crash dump. Would that help tracking down?
> 
> I do not think that this will help.
> 
> Try better to enable slab poisoning in slab.h. If it that thing
> which I think of, it would provoke crash.

Thanks for your reply,

Does that mean just enabling CONFIG_DEBUG_SLAB  in  kernel  config  or
more?

I see:

#define SLAB_POISON             0x00000800UL    /* Poison objects */

in slab.h, but there's nothing settable in there.

Anyway I've recompiled the 2.4.19 kernel with CONFIG_DEBUG_SLAB=y.
Let's see what happens.

Greets,
_Alain_

  reply	other threads:[~2002-10-22  3:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  3:02 UPD: Frequent/consistent panics in 2.4.19 at ip_route_input_slow, in_dev_get(dev) Alain Fauconnet
2002-10-21 16:40 ` kuznet
2002-10-22  3:24   ` Alain Fauconnet [this message]
2002-10-28 10:19   ` Alain Fauconnet
2002-10-29  1:30     ` kuznet
2002-10-29  4:13       ` Alain Fauconnet
2002-10-29  4:31         ` kuznet

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=20021022102444.C2361@cscoms.net \
    --to=alain@cscoms.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lve@ns.aanet.ru \
    /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.