From: Wolfgang Denk <wd@denx.de>
To: "Stephen Williams" <612dlag102@sneakemail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel hangs in early_init
Date: Wed, 03 Mar 2004 00:56:27 +0100 [thread overview]
Message-ID: <20040302235632.341E4C0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 02 Mar 2004 10:48:42 PST." <4522-80798@sneakemail.com>
In message <4522-80798@sneakemail.com> you wrote:
>
> Good point, I missed that. However, that particular FAQ doesn't seem
> to apply. I'm using 2.4.24+ (>2.4.5), the CFG_IMMR value doesn't seem
> to apply (PPC405GPr, not a MPC8xx system) and I double-checked that
> the bd_t structure matches. Besides, it's nowhere neer trying to access
> any of the arguments yet.
I think it does access arguments. Linux will need parameters like
clock frequencies, memory sizes etc. Passing wrong paramteters is one
of the most frequent causes of that particular failure mode.
> The stack at the time is still where U-Boot left it, near the end of
> the 128Meg memory. Is this something I should address (pardon the pun)?
I don't think so.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
If a man had a child who'd gone anti-social, killed perhaps, he'd
still tend to protect that child.
-- McCoy, "The Ultimate Computer", stardate 4731.3
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-02 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 6:41 Kernel hangs in early_init Stephen Williams
2004-03-02 8:51 ` Wolfgang Denk
2004-03-02 18:48 ` Stephen Williams
2004-03-02 23:56 ` Wolfgang Denk [this message]
2004-03-03 0:14 ` Stephen Williams
2004-03-03 9:44 ` Andrei Konovalov
2004-03-03 20:16 ` Stephen Williams
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=20040302235632.341E4C0655@atlas.denx.de \
--to=wd@denx.de \
--cc=612dlag102@sneakemail.com \
--cc=linuxppc-embedded@lists.linuxppc.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).