From: "Stephen Williams" <612dlag102@sneakemail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel hangs in early_init
Date: Wed, 03 Mar 2004 12:16:03 -0800 [thread overview]
Message-ID: <29987-51510@sneakemail.com> (raw)
In-Reply-To: <4045A8FC.1090303@ru.mvista.com>
Andrei Konovalov akonovalov-at-ru.mvista.com |PPC Linux Embedded| wrote:
> Stephen Williams wrote:
>> Humm... The MMU comment makes me think. U-Boot is running with the
>> MMU off. The head_4xx.S entry code sets up a temporary MMU mapping
>> that includes the linked kernel address space, but that is only 32meg.
>> 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)?
>>
>
> Just a suggestion. Check that the whole data cache is invalidated.
> The kernel often relies on the bootloader to initialize dcache properly.
> And there is a chance that the bootloader was written for 405GP, but
> 405GPr's data cache is two times bigger.
BINGO!
I am using U-Boot, and in my JSE.h I had mis-set the CFG_DCACHE_SIZE
to 8K, as it was copied from another config file that I used as a
starting point. U-Boot does some cache management, but obviously
made a mess when it was told the wrong thing:-)
I set it properly, and I'm farther along.
--
Steve Williams "The woods are lovely, dark and deep.
steve at XXXXXXXXXX But I have promises to keep,
http://www.XXXXXXXXXX and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-03-03 20:16 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
2004-03-03 0:14 ` Stephen Williams
2004-03-03 9:44 ` Andrei Konovalov
2004-03-03 20:16 ` Stephen Williams [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=29987-51510@sneakemail.com \
--to=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).