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 Failed due to bad address Entering padzero ... >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. 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. Thanks & Regards -SS ________________________________ From: [EMAIL PROTECTED] [mailto:linuxppc-embedded-bounces at ozlabs.org] Sent: Friday, February 18, 2005 2:42 PM To: linuxppc-embedded at ozlabs.org Subject: Freeing unused kernel memory: 56k init The latest update is that the init was also found in one of the packages. So now I am not facing init not found problem . But there was a hung problem, once the init is invoked .. Please find the output below... RAMDISK: Compressed image found at block 0 Freeing initrd memory: 1235k freed kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 56k init < there is no output after the above statement.....> Thanks & Regards Surabhi Srinivas ________________________________ From: Wolfgang Denk [mailto:[EMAIL PROTECTED] Sent: Thu 2/17/2005 5:12 PM Subject: Re: Mounta Vista Linux prompt on serial console In message <EF9B29C78F41FA488927FCBC7750AF0E08DA14 at hyd-mdp-msg.wipro.com> you wrote: > > But the problem is that it was stopping at > > "No init found. Try passing init= option to kernel". Before that there > were no errors. Everthing looks fine Mounted VFS root file system was also Fine. So you can mount the root filesystem, but it obviously does not contain all the required files. > seen. >From the net I understood is that the fstab file was the cause. So > edited the filesytem parameter for / as /dev/ram earlier it used to be > /dev/root. No. /etc/fstab has absolutley nothing to do with your problem. The kernel cannot start the init porocess - make sure init is in the filesystem, plus all required libraries. > So please tell me whether the given fstab file will suffice? The filesystem This is completley unrelated. > 2. I have one more doubt /sbin/init utility comes with what package? > Because in /sbin directory although the init binary is present, not shown > in the file system heirarchy view. For eg. if I select DHCPD package then > able to see dhcpd related binary in the /sbin similarly my question was > which package has to be selected to have init included. Please contact MV support. I have no idea how they package their distribution, or how their config tools might work. You paid for their stuff, so ask _them_. Best regards, Wolfgang Denk -- See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310 Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" (I found it!) but "That's funny ..." -- Isaac Asimov Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately and destroy all copies of this message and any attachments. Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately and destroy all copies of this message and any attachments. Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately and destroy all copies of this message and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050220/9521055f/attachment.htm
