2.6.34-rc1: kernel BUG at mm/slab.c:2989!
Américo Wang
I triggered an mm bug today, the full backtrace is here:
I am using yesterday's Linus tree.
It's not easy to reproduce this, I got this very randomly.
Some related config's are:
CONFIG_SLAB=y
CONFIG_SLABINFO=y
# CONFIG_DEBUG_SLAB is not set
Please let me know if you need more info.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Pekka Enberg
> Hello, mm experts,
>
> I triggered an mm bug today, the full backtrace is here:
>
> http://pastebin.ca/1831436
>
> I am using yesterday's Linus tree.
>
> It's not easy to reproduce this, I got this very randomly.
>
> Some related config's are:
>
> CONFIG_SLAB=y
> CONFIG_SLABINFO=y
> # CONFIG_DEBUG_SLAB is not set
>
> Please let me know if you need more info.
Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
Anyway, it seems very unlikely that it's caused by the SLAB changes in
-rc1 so I'm CC'ing scheduler and fs folks in case the oops rings a bell.
Pekka
Christoph Lameter
> > Please let me know if you need more info.
>
> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
command line to have all allocations checked.
Américo Wang
<c...@linux-foundation.org> wrote:
> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>
>> > Please let me know if you need more info.
>>
>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>
> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
> command line to have all allocations checked.
>
>
Ok, I will try it today.
Américo Wang
> On Wed, Mar 10, 2010 at 10:33 PM, Christoph Lameter
> <c...@linux-foundation.org> wrote:
>> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>>
>>> > Please let me know if you need more info.
>>>
>>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>>
>> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
>> command line to have all allocations checked.
>>
>>
>
> Ok, I will try it today.
>
Sorry, I can't trigger it today, either with SLAB or SLUB.
Pekka Enberg
> On Thu, Mar 11, 2010 at 10:42 AM, Américo Wang <xiyou.w...@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 10:33 PM, Christoph Lameter
>> <c...@linux-foundation.org> wrote:
>>> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>>>
>>>>> Please let me know if you need more info.
>>>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>>> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
>>> command line to have all allocations checked.
>>>
>>>
>> Ok, I will try it today.
>
> Sorry, I can't trigger it today, either with SLAB or SLUB.
Is it the exact same version or is it a new git snapshot?
Américo Wang
> Américo Wang kirjoitti:
>> On Thu, Mar 11, 2010 at 10:42 AM, Américo Wang <xiyou.w...@gmail.com> wrote:
>>> On Wed, Mar 10, 2010 at 10:33 PM, Christoph Lameter
>>> <c...@linux-foundation.org> wrote:
>>>> On Wed, 10 Mar 2010, Pekka Enberg wrote:
>>>>
>>>>>> Please let me know if you need more info.
>>>>> Looks like regular SLAB corruption bug to me. Can you trigget it with SLUB?
>>>> Run SLUB with CONFIG_SLUB_DEBUG_ON or specify slub_debug on the kernel
>>>> command line to have all allocations checked.
>>>>
>>>>
>>> Ok, I will try it today.
>>
>> Sorry, I can't trigger it today, either with SLAB or SLUB.
>
> Is it the exact same version or is it a new git snapshot?
No, I did a git pull, but it looks like only some btrfs updates...