From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: marvell kirkwood / openrd-base kernel freeze on bootup with PICe->PCI bridge
Date: Thu, 29 Oct 2009 09:52:36 +0100 [thread overview]
Message-ID: <20091029085236.GN14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <200910290936.40397.dk-arm-linux@gmx.de>
On Thu, Oct 29, 2009 at 10:36:40AM +0200, Dieter Kiermaier wrote:
> ## Booting kernel from Legacy Image at 00800000 ...
> Image Name: Linux-2.6.32-rc5-00081-g964fe08-
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2390056 Bytes = 2.3 MB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux............................................................................................................................................................ done.
The problem most probably is that your kernel dies before the console is
enabled, and hence you're not pointed to the actual problem.
Try the patch below - printk() messages are not buffered but sent out
directly to the lowlevel UART functions with this hack. CONFIG_DEBUG_LL
must be enabled for this.
Daniel
diff --git a/kernel/printk.c b/kernel/printk.c
index b4d97b5..7919751 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -686,6 +686,7 @@ asmlinkage int vprintk(const char *fmt, va_list args)
printed_len += vscnprintf(printk_buf + printed_len,
sizeof(printk_buf) - printed_len, fmt, args);
+{ extern void printascii(const char *); printascii(printk_buf); }
p = printk_buf;
next prev parent reply other threads:[~2009-10-29 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 8:36 marvell kirkwood / openrd-base kernel freeze on bootup with PICe->PCI bridge Dieter Kiermaier
2009-10-29 8:35 ` Simon Kagstrom
2009-10-29 8:50 ` Dieter Kiermaier
2009-10-29 8:52 ` Daniel Mack [this message]
2009-10-29 8:59 ` Simon Kagstrom
2009-10-29 9:14 ` Dieter Kiermaier
2009-10-29 9:36 ` Dieter Kiermaier
2009-10-29 10:33 ` Ronen Shitrit
2009-10-29 10:57 ` Dieter Kiermaier
2009-10-29 11:33 ` Ronen Shitrit
2009-10-29 15:11 ` Dieter Kiermaier
2009-10-29 15:16 ` Russell King - ARM Linux
2009-10-29 22:47 ` saeed bishara
2009-10-30 8:55 ` Dieter Kiermaier
2009-11-03 14:36 ` Dieter Kiermaier
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=20091029085236.GN14091@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).