[BISECTED] Removing BKL causes stack trace during early bootup

[walt]

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@xxxxxxx>
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/