To: linux-kernel@vger.kernel.org
From: walt <w41ter@gmail.com>
Subject: [BISECTED] Removing BKL causes stack trace during early bootup
Date: Thu, 12 Aug 2010 11:09:03 -0700
Message-ID: <4C6438BF.9070608@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Arnd Bergmann <arnd@arndb.de>, Frederic Weisbecker <fweisbec@gmail.com>,
        Steven Rostedt <rostedt@goodmis>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4pre) Gecko/20100809 Shredder/3.2a1pre
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 746
Lines: 15

Hi guys.  This commit produces a non-fatal call trace very early during boot
on my dual-CPU amd64 machine (but not on my single-CPU x86):

commit 5e3d20a68f63fc5a310687d81956c3b96e488b84
Author: Arnd Bergmann <arnd@xxxx.de>
Date:   Sun Jul 4 00:02:26 2010 +0200

     init: Remove the BKL from startup code

The trace whizzes by so fast that I can't read it, and the trace doesn't appear
in any of the logs.  Is there a way to capture such a trace, like maybe changing
it to a fatal error?

Thanks!


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/