Re: Re: Slab corruption after unloading a module

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/12/06, Zhiyi Huang <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux