linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Freeing unused kernel memory: 56k init
Date: Mon, 21 Feb 2005 08:37:30 +0100	[thread overview]
Message-ID: <200502210837.31174.david.jander@protonic.nl> (raw)
In-Reply-To: <EF9B29C78F41FA488927FCBC7750AF0E011DA65E@hyd-mdp-msg.wipro.com>

On Sunday 20 February 2005 16:25, srinivas.surabhi@wipro.com wrote:
> When I tried to debug for the reason of  "Freeing unused kernel memory:
> 56k init " hang problem  the following is the printk outputs...
>
> Entering kernel_read
>
> Entering elf_map
>
> map_addr was 0x30026000

Heh? Weired address. I'd expect something above 0xc0000000

> Failed due to bad address

No wonder....

> >From the above can anything be concluded ?
>
> One more doubt was, is it mandatory that the Virtual memory has to
> enabled while building the Mounta Vista linux kernel ? Why because there
> was an option to enable the kernel base address and if it is enabled it
> asks for what is the address for the Kernel Virtual base address? If I
> give 0x0 it works otherwise the Kernel itself is not at all booting.

Ok, don't say no more! Do not ever change that address unless you know exactly 
what you are doing. It should be 0xc0000000 usually.
If the kernel doesn't boot, something else is wrong.
The linux kernel uses virtual memory, that's why it needs an MMU for instance. 
That way, the memory the kernel uses and runs in is always mapped at address 
0xc0000000.

> Till the statement "Freeing unused kernel memory: 56k init"  is coming
> only if and if the 0x0 was given for the kernel virtual base address.

That's actually pretty funny. I'd never thought about doing such an experiment 
and expecting it to do something :-)

Greetings,

-- 
David Jander
Protonic Holland.

  reply	other threads:[~2005-02-21  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20 15:25 Freeing unused kernel memory: 56k init srinivas.surabhi
2005-02-21  7:37 ` David Jander [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-18  9:11 srinivas.surabhi

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=200502210837.31174.david.jander@protonic.nl \
    --to=david.jander@protonic.nl \
    --cc=linuxppc-embedded@ozlabs.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).