Linux Stops at "Freeing init memory: 204K"

cancel
Showing results for 
Search instead for 
Did you mean: 

Linux Stops at "Freeing init memory: 204K"

Jump to solution
4,037 Views
PaulDeMetrotion
Senior Contributor I

I have a custom device that boots a Linux kernel built with LTIB. I am trying to boot the Freescale kernel L3.0.35_1.1.0_oneiric and it will not finish the boot. It stops displaying to the console or a selected video device after "Freeing init memory: 204K". Here is the bottom of the console output. Any ideas why the display stops?

regulator_init_complete: VDDIO: incomplete constraints, leaving on

regulator_init_complete: VDDA: incomplete constraints, leaving on

regulator_init_complete: vddpu: incomplete constraints, leaving on

snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)

eth0: Freescale FEC PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=1:

07, irq=-1)

usb 2-1: new high speed USB device number 2 using fsl-ehci

hub 2-1:1.0: USB hub found

hub 2-1:1.0: 7 ports detected

usb 2-1.4: new low speed USB device number 3 using fsl-ehci

input: Dell Dell USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.4/2-1

.4:1.0/input/input0

generic-usb 0003:413C:2105.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Del

l USB Keyboard] on usb-fsl-ehci.1-1.4/input0

usb 2-1.3: new low speed USB device number 4 using fsl-ehci

input: Microsoft Basic Optical Mouse as /devices/platform/fsl-ehci.1/usb2/2-1/2-

1.3/2-1.3:1.0/input/input1

generic-usb 0003:045E:0084.0002: input,hidraw1: USB HID v1.10 Mouse [Microsoft B

asic Optical Mouse] on usb-fsl-ehci.1-1.3/input0

PHY: 1:07 - Link is Up - 1000/Full

IP-Config: Guessing netmask 255.0.0.0

IP-Config: Complete:

     device=eth0, addr=124.0.0.0, mask=255.0.0.0, gw=255.255.255.255,

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

     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=

EXT3-fs: barriers not enabled

kjournald starting.  Commit interval 5 seconds

EXT3-fs (mmcblk0p1): using internal journal

EXT3-fs (mmcblk0p1): recovery complete

EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode

VFS: Mounted root (ext3 filesystem) on device 179:1.

Freeing init memory: 204K

***** STOPS HERE - THE CUSTOM KERNEL CONTINUES BOOTING TO A PROMPT *****

starting pid 1319, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
Starting the hotplug events dispatcher udevd
udevd (1328): /proc/1328/oom_adj is deprecated, please use /proc/1328/oom_score_
adj instead.
Synthesizing initial hotplug events
Setting the hostname to freescale
Mounting filesystems
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
Running sysctl
Setting up networking on loopback device:
Setting up networking on eth0:
udhcpc (v1.20.2) started
Sending discover...
Sending select for 192.168.0.178...
Lease of 192.168.0.178 obtained, lease time 691200
Deleting routers
adding dns 192.168.0.4
starting pid 2432, tty '': '/etc/rc.d/rc_gpu.S'
starting pid 2438, tty '': '/etc/rc.d/rc_mxc.S'

arm-none-linux-gnueabi-gcc (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/
10 09:20) 4.6.2 20110630 (prerelease)
root filesystem built on Wed, 20 Feb 2013 15:12:01 -0600
Freescale Semiconductor, Inc.

freescale login:

0 Kudos
1 Solution
199 Views
PaulDeMetrotion
Senior Contributor I

Solved - when I was copying the file system to the SD card, I did not perfrom a sync operation. Obviously this was required to complete the proper transfer of files to the SD card. After adding this step, I was able to boot past the freeing memory display. On to the next bug.....

View solution in original post

0 Kudos
6 Replies
199 Views
deepakbhagat
Contributor II

hi Paul,

on our custom board we have used ksz9031interface to imx6solo. can you help me in uboot  changes that are need to be done as i am getting mac id 00:00:00:00:00:00 in uboot but its working fine when kernel is booted up. i am able to see mac address as well as communicated over the ksz9031 after the kernel is booted up. I want setup nfs for our custom board. We are also using ltib build system and uboot ver 2009.08 while linux kernel is 3.0.35.

thanks in advance.

Regards,

Deepak.

0 Kudos
200 Views
PaulDeMetrotion
Senior Contributor I

Solved - when I was copying the file system to the SD card, I did not perfrom a sync operation. Obviously this was required to complete the proper transfer of files to the SD card. After adding this step, I was able to boot past the freeing memory display. On to the next bug.....

View solution in original post

0 Kudos
199 Views
reshmimarimgant
Contributor I

Dear Xiaoli Zhang,

                          can you explain what has to be done for imx6sololite. we are also getting the same freeing init memory issue while booting using the SDcard.

0 Kudos
199 Views
lily_zhang
NXP Employee
NXP Employee

Are you flashing image well by sync operation?

0 Kudos
199 Views
reshmimarimgant
Contributor I

we have an freescale i.MX6 Sololite kit. we downloaded BSP and compiled it. we partitioned the SD card as per freescale user guide(running script) and copied the images. while booting it is showing  an error and hanging. the error is clearly mentioned in the attached log file. can you please guide us  why the error is coming and how to resolve the issue?

 

Please find the attached log file.

Regards,

Reshmi

0 Kudos
199 Views
lily_zhang
NXP Employee
NXP Employee

Do you know which profile your customer select to build LTIB rootfs?

The build instructions into the document is like:

1. Remove all previously-installed packages in /opt/freescale/pkgs/.

2. Install the LTIB package, not as root, in a location such as /home/user/:

tar zxvf L3.0.35_1.1.0_121218_source.tar.gz

./L3.0.35_1.1.0_121218_source/install

This command installs LTIB to your directory.

3. Build LTIB:

cd <LTIB directory>.

./ltib -m config

4. Select platform to Freescale iMX reference boards and exit, saving the changes. At

the next menu, select platform type as imx6q and package profile. Exit and save the

new configuration. Please note that only the profiles of Min profile, FSL gnome

release packages, and mfg firmware profile pass build tests.

NOTE

You can use the ./ltib -m selectype command to change the

profile after the first selection.

5. To build U-Boot for i.MX 6Dual/6Quad SABRE-SD board, select "Choose your

board for U-Boot" as "mx6q_sabresd". Please note this option is only for U-Boot.

For the kernel image, the current default kernel configuration builds a single image

that works for all i.MX6 boards except i.MX 6SoloLite boards.

--- Choose your board

board (mx6q_sabresd) --->

7. Close the configuration screen saving the changes.

8. Run the following command:

./ltib

When this procedure is completed, the kernel image and the U-Boot images are

located at: rootfs/boot/