From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected
Date: Thu, 14 Aug 2008 22:29:28 +0200 [thread overview]
Message-ID: <200808142229.28624.rjw@sisk.pl> (raw)
In-Reply-To: <48A485A8.8010803@hp.com>
On Thursday, 14 of August 2008, Alan D. Brunelle wrote:
> Rafael J. Wysocki wrote:
> > On Thursday, 14 of August 2008, Alan D. Brunelle wrote:
> >> I ran into this trying 2.6.27-rc3 today:
> >>
> >> [6.461876] kernel BUG at mm/vmalloc.c:217!
> >>
> >> (full boot log attached)
> >>
> >> I bisected it to:
> >>
> >> git-bisect bad 1c89ac55017f982355c7761e1c912c88c941483d
> >>
> >> which is:
> >>
> >> commit 1c89ac55017f982355c7761e1c912c88c941483d
> >> Merge: 88fa08f... b1b135c...
> >> Author: Linus Torvalds <torvalds@linux-foundation.org>
> >> Date: Tue Aug 12 08:40:19 2008 -0700
> >>
> >> Merge
> >> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus
> >
> > This is a merge commit that introduced several changes into the
> > kernel. It would be helpful to search through these changes.
>
> I came in this morning, and did a 'git bisect reset' and 'git pull'
> built, and everything booted fine. I don't know if some fix came in for
> something else, or if the problem got "hidden" (some sort of timing
> thing, so the problem still lurks). If you feel it's important to track
> this down, if you could give me instructions on how to break apart that
> one merge, I could then try individual kernels from there...
I have created a Bugzilla entry at
http://bugzilla.kernel.org/show_bug.cgi?id=11342
for this problem. I'll close it now, but please reopen if if the problem
reappears.
Thanks,
Rafael
next prev parent reply other threads:[~2008-08-14 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 23:03 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 [this message]
2008-08-19 19:46 ` Andrew Morton
2008-08-22 15:37 ` Alan D. Brunelle
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=200808142229.28624.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Alan.Brunelle@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome