All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: "Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard \"Georg
	C. F. Greve\"" <greve@fsfeurope.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Fri, 31 Dec 2004 12:46:45 +0100	[thread overview]
Message-ID: <41D53C25.4030402@colorfullife.com> (raw)

>
>
>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. 
>
>  
>
It was a crash in free_block - this means control structures of the slab 
allocator were corrupted.

You wrote that enabling everything caused a hard crash without anything 
on the console. Could you try what happens if slab debugging is enabled, 
but page alloc debugging is off? You should get a verbose BUG_ON() with 
kmem_cache_free/kmem_cache_alloc caller addresses and similar stuff.

> EFLAGS: 00010002   (2.6.10)
> EIP is at free_block+0x45/0xd0
> eax: 46484849   ebx: df2b1000   ecx: df2b1050   edx: df2ab000
> esi: c183cd80   edi: 00000001   ebp: 00000018   esp: c188fef8
> ds: 007b   es: 007b   ss: 0068

Could you compile your kernel without debug and send me mm/slab.o? The 
%eax value is odd: FHHI or IHHF.

Btw, if it's still too slow for you without page alloc debug: remove the 
forced poisoning:

  if ((size < 4096 || fls(size-1) == fls(size-1+3*BYTES_PER_WORD)))
          flags |= SLAB_RED_ZONE|SLAB_STORE_USER;
- if (!(flags & SLAB_DESTROY_BY_RCU))
-         flags |= SLAB_POISON;
 #endif

--
	Manfred



             reply	other threads:[~2004-12-31 11:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 11:46 Manfred Spraul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-30 10:21 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Nick Warne
2004-12-30  0:31 Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
2004-12-30 17:39   ` Peter T. Breuer
2004-12-30 17:53     ` Sandro Dentella
2004-12-30 18:31       ` Peter T. Breuer
2004-12-30 19:50     ` Michael Tokarev
     [not found]       ` <41D45C1F.5030307-XAri/EZa3C4vJsYlp49lxw@public.gmane.org>
2004-12-30 20:54         ` berk walker
2004-12-30 20:54           ` berk walker
2005-01-01 13:39         ` Helge Hafting
2005-01-01 13:39           ` Helge Hafting
2004-12-30 21:39       ` Peter T. Breuer
2005-01-07  6:21     ` Clemens Schwaighofer
2005-01-07  9:39       ` Andy Smith
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
2005-01-01 20:06       ` Alan Cox
     [not found]     ` <m3zmzvl9x1.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2005-01-02 20:11       ` Linus Torvalds
2005-01-02 20:11         ` Linus Torvalds
     [not found]         ` <Pine.LNX.4.58.0501021147260.2280-gWtpgVMusWVb5UGfqNBoRg@public.gmane.org>
2005-01-02 20:32           ` Dave Jones
2005-01-02 20:32             ` Dave Jones

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=41D53C25.4030402@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=greve@fsfeurope.org \
    --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 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.