From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Nico -telmich- Schottelius
<nico-linux-ipw3945-devel@schottelius.org>,
"John W. Linville" <linville@tuxdriver.com>,
Nico Schottelius <nico-linux-20090313@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>,
ipw3945-devel@lists.sourceforge.net
Subject: Re: Strange reboots on 2.6.29-rc6-wl
Date: Tue, 17 Mar 2009 14:57:53 +0000 [thread overview]
Message-ID: <20090317145753.GA1651@silver.sucs.org> (raw)
In-Reply-To: <20090317075424.GD8777@denkbrett.schottelius.org>
On Tue, Mar 17, 2009 at 08:54:24AM +0100, Nico -telmich- Schottelius wrote:
>
> Has anyone a clue on howto debug the build environment or
> debugging the kernel before it's getting booted?
If you have a serial console you can probably get output on that. If you
have flipped EMBEDDED to Y then you might also have to enable
EARLY_PRINTK. Another trick might be to turn set
BOOT_PRINTK_DELAY (Kernel hacking -> Delay each boot printk message by N
milliseconds) to something like 2000 and see if you can read/catch the
messages before the kernel reboots...
Failing that start a git bisection (
http://www.kernel.org/doc/local/git-quick.html#bisect or
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf )
from the last good kernel...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-03-17 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 20:06 Strange reboots on 2.6.29-rc6-wl Nico Schottelius
2009-03-13 20:41 ` John W. Linville
2009-03-17 7:54 ` Nico -telmich- Schottelius
2009-03-17 14:57 ` Sitsofe Wheeler [this message]
2009-03-20 10:21 ` Nico -telmich- Schottelius
2009-03-21 13:03 ` Sitsofe Wheeler
2009-03-24 16:47 ` [ipw3945-devel] " Nico -telmich- Schottelius
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=20090317145753.GA1651@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nico-linux-20090313@schottelius.org \
--cc=nico-linux-ipw3945-devel@schottelius.org \
/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