lkml.org 
[lkml]   [2006]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Re: Slab corruption after unloading a module
On 4/12/06, Zhiyi Huang <zhiyi6@xtra.co.nz> wrote:
> Thanks for help. I already configured the kernel with CONFIG_DEBUG_SLAB=y,
> but I changed the current log level from 7 to 8. I got similar messages below.
> I still have no clue. The messages show nothing about my module. Any more
> suggestions?

2.6.8 is an old kernel, you could very well be hitting a kernel bug
that has been fixed already. Can you reproduce this with 2.6.16? Also,
you're not including sources to your module so it's impossible to tell
whether you're doing something wrong.

Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-12 08:44    [W:0.025 / U:1.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site