From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alan D. Brunelle" Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected Date: Mon, 25 Aug 2008 08:03:07 -0400 Message-ID: <48B29F7B.6080405@hp.com> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Linus Torvalds Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Andrew Morton , Arjan van de Ven , Rusty Russell 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? > > Linus > I'll add those in - as to the repeatability: The "bad" kernels seem to repeat quite reliably - not only in terms of counts (5 or 6 times in a row before trying something else), but also in terms of the "what" - either the original issue () or the other kernel with the later issue (debug_mutex_add_waiter). That's /goodness/ in that it should help narrow it down. I'll make sure the kernel is still failing this morning, and then add in DEBUG_PAGE_ALLOC and if that doesn't help, SLUB debugging... Alan