(no subject)

[logic]

Good morning,

I am experiencing a bug i think. I am running a 2.6.19.2 kernel on a 3Ghz
Intel with HT activated, 1 gb ram, and noname motherboard. Here is the
output of the hang:
------------[ cut here ]------------

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: kernel BUG at mm/slab.c:607!

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: invalid opcode: 0000 [#1]

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: CPU:    1

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: EIP:    0060:[<c0155ebb>]    Not tainted VLI

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: eax: 1af3a451   ebx: c89ba000   ecx: 4a5ffc80   edx: c214bfe0

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: EIP is at free_block+0x44/0xda

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: PREEMPT SMP
mail kernel: EFLAGS: 00010046   (2.6.19.2 #1)

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: Call Trace:

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel:  =======================

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: Process events/1 (pid: 9, ti=c19b6000 task=c1983a90
task.ti=c19b6000)

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel: Stack: 00000000 0000001e c196d018 c196d018 0000001e c196d000
00000000 c015664d

Message from syslogd@mail at Fri Feb  2 22:47:32 2007 ...
mail kernel:        00000000 00000000 c196fc80 c19485c0 c196fc80 c19485c0
c194b140 00000213



-- 
--
Va salut,
Alexandru Gheorghita
Technical Manager
Think.Net
phone: 0788.700.842
mail: logic@thinknet.ro

Re: your mail

[Joerg Roedel]

On Mon, Feb 05, 2007 at 05:41:29PM +0200, logic@thinknet.ro wrote:
> Good morning,
> 
> I am experiencing a bug i think. I am running a 2.6.19.2 kernel on a 3Ghz
> Intel with HT activated, 1 gb ram, and noname motherboard. Here is the
> output of the hang:

Hmm, this seems to be the same issue as in [1] and [2]. A page that is
assumed to belong to the slab but is not longer marked as a slab page.
Could this be a bug in the memory management?

Joerg

[1] http://lkml.org/lkml/2007/2/4/77
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406477

-- 
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG

Re: your mail

[Pekka Enberg]

Hi Joerg,

On 2/5/07, Joerg Roedel <joerg.roedel@amd.com> wrote:
> Hmm, this seems to be the same issue as in [1] and [2]. A page that is
> assumed to belong to the slab but is not longer marked as a slab page.
> Could this be a bug in the memory management?

The BUG_ON triggers whenever you feed an invalid pointer to kfree() or
kmem_cache_free() so I am guessing the caller is simply broken. Note
that kernels prior to 2.6.18 would quietly corrupt the slab unless
CONFIG_SLAB_DEBUG was enabled which might explain why this hasn't been
noticed before.

                               Pekka

Re: your mail

[Joerg Roedel]

On Mon, Feb 05, 2007 at 04:01:23PM +0200, Pekka Enberg wrote:
> Hi Joerg,
> 
> On 2/5/07, Joerg Roedel <joerg.roedel@amd.com> wrote:
> >Hmm, this seems to be the same issue as in [1] and [2]. A page that is
> >assumed to belong to the slab but is not longer marked as a slab page.
> >Could this be a bug in the memory management?
> 
> The BUG_ON triggers whenever you feed an invalid pointer to kfree() or
> kmem_cache_free() so I am guessing the caller is simply broken. Note
> that kernels prior to 2.6.18 would quietly corrupt the slab unless
> CONFIG_SLAB_DEBUG was enabled which might explain why this hasn't been
> noticed before.

Ok. I was not aware of that. Thanks for clarification.

Joerg

-- 
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG