From: Catalin Marinas <catalin.marinas@arm.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Problem] kernel hangs at boot (bisected 892d208bcf)
Date: Fri, 20 Jan 2012 09:22:22 +0000 [thread overview]
Message-ID: <20120120092222.GA30612@arm.com> (raw)
In-Reply-To: <CA+5PVA67g_2u6YkYtOMKwZOzmmkHs7FhYUASSOQbDozFvrzp-A@mail.gmail.com>
On Fri, Jan 20, 2012 at 02:20:24AM +0000, Josh Boyer wrote:
> On Thu, Jan 19, 2012 at 3:52 PM, Dirk Gouders
> <gouders@et.bocholt.fh-gelsenkirchen.de> wrote:
> >> I did some more testing and it turns out that I have to revert a single
> >> line of commit b66930052abf2 to make the kernel boot:
> >>
> >> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> >> index c833add..d8bbb68 100644
> >> --- a/mm/kmemleak.c
> >> +++ b/mm/kmemleak.c
> >> @@ -1710,6 +1710,7 @@ static void kmemleak_disable(void)
> >> return;
> >>
> >> /* stop any memory operation tracing */
> >> + atomic_set(&kmemleak_early_log, 0);
> >> atomic_set(&kmemleak_enabled, 0);
> >>
> >> /* check whether it is too early for a kernel thread */
> >>
> >> I started that kernel with initcall_debug and attach the dmesg output.
> >
> > Hi Catlin,
> >
> > I want to note that in my config CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is
> > set which causes kmemleak_disable() to be called in kmemleak_init().
>
> I also had CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y in my .config. Disabling that
> option allowed the machine to boot just fine. Dirk seems to be onto something
> here.
It definitely looks like a kmemleak problem with
CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y. I managed to reproduce it on ARM as
well.
I'll have a look and get back shortly.
Thanks.
--
Catalin
next prev parent reply other threads:[~2012-01-20 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 19:32 [Problem] kernel hangs at boot (bisected 892d208bcf) Dirk Gouders
2012-01-19 11:01 ` Catalin Marinas
2012-01-19 12:16 ` Dirk Gouders
2012-01-19 14:00 ` Catalin Marinas
2012-01-19 14:38 ` Dirk Gouders
2012-01-19 15:37 ` Catalin Marinas
2012-01-19 17:43 ` Dirk Gouders
2012-01-19 19:58 ` Dirk Gouders
2012-01-19 20:52 ` Dirk Gouders
2012-01-20 2:20 ` Josh Boyer
2012-01-20 9:22 ` Catalin Marinas [this message]
2012-01-20 11:01 ` Catalin Marinas
2012-01-20 12:14 ` Dirk Gouders
2012-01-20 14:16 ` Josh Boyer
2012-01-20 14:21 ` Catalin Marinas
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=20120120092222.GA30612@arm.com \
--to=catalin.marinas@arm.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=jwboyer@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.