Stop for ever in "Freeing init memory: 144K"

Hello,

Can you share thee source of filesystem and kernel source?

This issue can occur due to EABI incompatibility between filesystem and kernel. Please see this post:

http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg11911.html

Thanks,

Sekhar

    Why I cann't open this web :http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg11911.html？？？？？？？？

    please tell me.

can you tell me how to do,please donn't give me the web.it cann't be opened.

I copy pasted the URL into browser and was able to access the page. Here are the contents of the page

davinci-linux-open-source   
 Thread   Date     RE: Freeing init memory hang
Young, Joseph
Fri, 24 Apr 2009 04:39:33 -0700

Caglar, 

Thank you very much for your quick reply. I set CONFIG_AEABI=n, and I am now 
able to boot my ramdisk filesystem.

Thanks for your help!
Regards,
Joe 

-----Original Message-----
From: Yusuf Caglar AKYUZ [mailto:caglarak...@gmail.com] 
Sent: Friday, April 24, 2009 11:14 AM
To: Young, Joseph
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: Freeing init memory hang

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Young, Joseph wrote:
> Hello,
> 

Hello,

> So I am attempting to boot the current Davinci Linux kernel for the Davinci 
> DM644x EVM board, and am running into some problems. I have compiled the 
> uImage, and am using the ramdisk.gz provided by TI, but when I attempt to 
> load the kernel, it hangs indefinitely at "Freeing init memory: 124K".
> 
> I have tried Davinci linux kernel versions 2.29 and 2.30-rc2, and both 
> experience the hang.
> I have also built a minimal kernel by following SPRAAH2A, and that also 
> experienced the hang.
> 
> The same boot parameters work correctly with the montavista Linux image 
> provided by TI.
> I thought the problem was with mounting busybox, so I wrote a "Hello World" 
> program, and attempted to run that. My kernel still hangs, while the 
> montavista linux kernel will display my program, so I think the problem is 
> with my kernel configs setup.
> I also thought it was a tool chain problem, and have rebuilt the kernels with 
> the GNU C arm compiler, as well as the RidgeRun DM6446x SDK kit, and both 
> experienced the hang.
> 
> The interesting thing is that when I unplug the cord from my TFTP server, the 
> hung kernel will output "PHY: 1:01 - Link is Down" and when I plug it back in 
> "PHY: 1:01 - Link is Up - 100/Full". This means that the kernel is still 
> somewhat responsive, just not doing what I want it to do, display the shell.
> 
> I'm out of ideas at this point. Has anyone run into this issue, or can anyone 
> point me in the right direction?
> 

My guess:

Kernel is running, but there is something wrong with filesystem /dev nodes. 
AFAIK, this point is where control passes to init and console is redirected to 
/dev/console(or /dev/console must be present). This is also the same for your 
own application. Maybe your file system is not EABI?

If I were you, I would try an NFS file system.

Regards,
Caglar

can you tell me the details?

How to change the CONFIG_AEABI=n?

"set CONFIG_AEABI=n " ?

it is rebuilt ramdisk?

Hello,

This relates to re-building the kernel. You need to edit this in the .config file that gets created in kernel top level directory that gets created after you configure the kernel.

Thanks,

Sekhar

I changed .config, but after few steps linux hang up second time:

Freeing init memory: 144K

INIT: version 2.85 booting

0
Mounting a tmpfs over /dev...done.
Creating initial device nodes...done.
0
Mounting local filesystems: mount none on /var/run type tmpfs (rw)
none on /tmp type tmpfs (rw)
Starting hotplug subsystem:
pci
pci [success]
usb
usb [success]
isapnp
isapnp [success]
ide

ide [success]
input
input [success]
scsi
scsi [success]
done.

could you tell me what is wrong ?

Sekhar Nori said:

My guess:

Kernel is running, but there is something wrong with filesystem /dev nodes.
AFAIK, this point is where control passes to init and console is redirected to
/dev/console(or /dev/console must be present). This is also the same for your
own application. Maybe your file system is not EABI?

If I were you, I would try an NFS file system.

Regards,
Caglar

John A