[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA67g_2u6YkYtOMKwZOzmmkHs7FhYUASSOQbDozFvrzp-A@mail.gmail.com>
Date: Thu, 19 Jan 2012 21:20:24 -0500
From: Josh Boyer <jwboyer@...il.com>
To: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
Cc: Catalin Marinas <catalin.marinas@....com>,
linux-kernel@...r.kernel.org
Subject: Re: [Problem] kernel hangs at boot (bisected 892d208bcf)
On Thu, Jan 19, 2012 at 3:52 PM, Dirk Gouders
<gouders@...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.
josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists