Kernel panic - not syncing: Out of memory and no killable processes...

Could you post your U-Boot arguments (printenv)? My first guess would be some typo in the bootargs that is not allocating you enough memory (MEM=88M not existing or something).

Thankyou  for  your suggestion,

Actually I have changed it to mem=128M and got rid of out of memory problem
but this time I am getting a message as
"Kernel panic - not syncing: No init found.  Try passing init= option to kernel"
Actually I am little bit confused with the procedure for updating flash image
I have just installed SDK software in my windows PC and
started to download it,as written in "5.2 Preparing to install" section in
dvsdk_gettingstarted guide page 41.
I didn't understand the 3 & 4 part of "5.1 Requirements" section.

I appreciate if you could explain me the difference between SDK and DVSDK
software(I thought that DVSDK is meant for video demo).

Below is the part of log file from hyperterminal window.

IP-Config: Complete:

device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=192.168.1.1,

host=192.168.1.10, domain=, nis-domain=(none),

bootserver=192.168.1.20, rootserver=192.168.1.20, rootpath=

RAMDISK: Compressed image found at block 0

RAMDISK: incomplete write (-28 != 32768) 41943040

invalid compressed format (err=2)

VFS: Mounted root (ext2 filesystem).

Freeing init memory: 136K

/sbin/init exit code: -20

EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #4097: rec_len is smaller than minimal - offset=0, inode=1089793, rec_len=0, name_len=62

/etc/init exit code: -2

/bin/init exit code: -20

/bin/sh exit code: -20

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Thankyou for all your support,it means a lot for me.

Chakra said:

Actually I have changed it to mem=128M and got rid of out of memory problem

I am glad to hear it, my mem=88M suggestion was for the DVSDK, the smaller value is there so that there is DDR space left for the DSP, if you are just using the SDK than 128M is fine.

Chakra said:

I didn't understand the 3 & 4 part of "5.1 Requirements" section.

Assuming you are using the current version of the DVSDK getting started guide than these represent the need to copy the DVSDK and SDK files to your Windows PC, is this what you are referring to? In this case the reason they have you do this is because the getting started guide uses PumpKIN in Windows as the TFTP server for loading new images on to the board, you could skip this and use a TFTP server running on a Linux machine though I have only tried the PumpKIN myself.

Chakra said:

I appreciate if you could explain me the difference between SDK and DVSDK software(I thought that DVSDK is meant for video demo).

You are correct, the SDK is just a basic Linux install for the EVM, the DVSDK adds on to the SDK giving you access to the DSP on the OMAP3 in the form of video demos and supporting software.

Chakra said:

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

This error indicates that your kernel was not able to find a valid filesystem, because it could not find a valid filesystem it could not find init. The errors above seem to indicate some sort of corruption of your RAMdisk image. For starters I would not worry about reflashing the board, this should not matter much until you need to have stand alone operation, for development I would suggest setting up the board to boot over TFTP/NFS so that you have more control and quicker access to the board, setting up TFTP and NFS are discussed in section 7.2 and section 4.4.5 of the getting started guide respectively.

hi dear ,

           Right now i am also have a same problem . if you know how do solve this problem . please give me a instruction for me . this is very use ful to me

                                                    thanking you