public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis>
Subject: [BISECTED] Removing BKL causes stack trace during early bootup
Date: Thu, 12 Aug 2010 11:09:03 -0700	[thread overview]
Message-ID: <4C6438BF.9070608@gmail.com> (raw)

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!



             reply	other threads:[~2010-08-12 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 18:09 walt [this message]
2010-08-12 18:26 ` [BISECTED] Removing BKL causes stack trace during early bootup Frederic Weisbecker
2010-08-12 19:40   ` walt
2010-08-12 18:36 ` Nick Bowler

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=4C6438BF.9070608@gmail.com \
    --to=w41ter@gmail.com \
    --cc=arnd@arndb.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis \
    /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