From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected
Date: Fri, 22 Aug 2008 11:37:33 -0400 [thread overview]
Message-ID: <48AEDD3D.4060507@hp.com> (raw)
In-Reply-To: <20080819124602.9e8e69f7.akpm@linux-foundation.org>
Andrew Morton wrote:
>
> You could confirm/debug it with something along the lines of this:
>
> --- a/mm/vmalloc.c~a
> +++ a/mm/vmalloc.c
> @@ -214,7 +214,9 @@ __get_vm_area_node(unsigned long size, u
> unsigned long align = 1;
> unsigned long addr;
>
> - BUG_ON(in_interrupt());
> + if (preempt_count() > 10)
> + printk("%s: preempt_count()=%d\n", __func__, preempt_count());
> + WARN_ON(in_interrupt());
> if (flags & VM_IOREMAP) {
> int bit = fls(size);
>
> _
>
>
> But this bug could be in practically anywhere in the kernel and
> bisection is by far the best way to find it. It's sad and odd that
> bisection landed you on a merge commit. I'd suggest that you persist
> with the bisection (please).
> http://www.kernel.org/doc/local/git-quick.html#example might be useful.
Sorry, was off on other things for the last couple of days:
I /did/ bisect it down to the aforementioned merge, the question is: How
to crack open that merge into it's composite pieces? (Where do I go to
bisect within that?)
I'll try the patch above, and see what that reports.
Alan
next prev parent reply other threads:[~2008-08-22 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 23:03 Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected Alan D. Brunelle
2008-08-13 23:27 ` Alan D. Brunelle
2008-08-14 16:14 ` Rafael J. Wysocki
2008-08-14 19:21 ` Alan D. Brunelle
2008-08-14 20:29 ` Rafael J. Wysocki
2008-08-19 19:46 ` Andrew Morton
2008-08-22 15:37 ` Alan D. Brunelle [this message]
2008-08-22 16:25 ` Andrew Morton
2008-08-22 17:16 ` Petr Baudis
2008-08-22 17:51 ` Andrew Morton
2008-08-22 18:07 ` Alan D. Brunelle
2008-08-22 19:37 ` Björn Steinbrink
2008-08-22 19:47 ` Alan D. Brunelle
2008-08-22 20:17 ` Alan D. Brunelle
2008-08-22 19:48 ` Jeff King
2008-08-22 21:05 ` Junio C Hamano
2008-08-22 21:16 ` Andrew Morton
2008-08-22 21:21 ` Jeff King
2008-08-22 21:36 ` Björn Steinbrink
2008-08-25 18:14 ` Vegard Nossum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48AEDD3D.4060507@hp.com \
--to=alan.brunelle@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox