From: Nick Bowler <nbowler@elliptictech.com>
To: walt <w41ter@gmail.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis>
Subject: Re: [BISECTED] Removing BKL causes stack trace during early bootup
Date: Thu, 12 Aug 2010 14:36:59 -0400 [thread overview]
Message-ID: <20100812183659.GA24008@elliptictech.com> (raw)
In-Reply-To: <4C6438BF.9070608@gmail.com>
On 2010-08-12 11:09 -0700, walt wrote:
> 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?
There are a couple options. First, the message _should_ appear in
'dmesg' output since you say the system boots: however if there was a
lot of _other_ output it is possible that it got pushed off the end of
the log. In this case, the easiest way to get it is to simply increase
the log buffer size, CONFIG_LOG_BUF_SHIFT, found under 'General Setup'
in menuconfig.
Another option is to use a serial console or netconsole to capture the
output on another machine.
Yet another option is to use the kernel command line option, boot_delay,
which lets you slow down the printing of messages at boot.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
prev parent reply other threads:[~2010-08-12 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 18:09 [BISECTED] Removing BKL causes stack trace during early bootup walt
2010-08-12 18:26 ` Frederic Weisbecker
2010-08-12 19:40 ` walt
2010-08-12 18:36 ` Nick Bowler [this message]
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=20100812183659.GA24008@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis \
--cc=w41ter@gmail.com \
/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