[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48B2A91F.8000302@hp.com>
Date: Mon, 25 Aug 2008 08:44:15 -0400
From: "Alan D. Brunelle" <Alan.Brunelle@...com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected
Linus Torvalds wrote:
>
> On Sat, 23 Aug 2008, Linus Torvalds wrote:
>> This one makes no sense. It's triggering a BUG_ON(in_interrupt()), but
>> then the call chain shows that there is no interrupt going on.
>
> Ahh, later in that thread there's another totally unrelated oops in
> debug_mutex_add_waiter().
>
> I'd guess that it is really wild pointer corrupting memory, quite possibly
> due to a double free or something like that. Alan - it would be good to
> run with DEBUG_PAGE_ALLOC and SLUB debugging etc if you don't already do
> that?
With /just/ DEBUG_PAGE_ALLOC defined, I have seen two general panic types:
o A new double fault w/ SMP_DEBUG_PAGEALLOC problem (prob4.txt)
o The NULL pointer dereference @ 0x858 (prob4a.txt)
Enabling SLUB debugging to see what that shows
Alan
View attachment "prob4.txt" of type "text/plain" (4170 bytes)
View attachment "prob4a.txt" of type "text/plain" (21643 bytes)
Powered by blists - more mailing lists