RAMDISK: incomplete write

cancel
Showing results for 
Search instead for 
Did you mean: 

RAMDISK: incomplete write

3,417 Views
shunpinglin
Contributor III

when we use rootfs which was made ourself, the kernel boot successfully, but have error message,following:

usb usb1-port1: over-current condition
usb usb2-port1: over-current condition
RAMDISK: incomplete write (16883 != 32768)
write error
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 252K (8055d000 - 8059c000)
INIT: version 2.88 booting
Starting udev
udevd[157]: starting version 182
EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
random: dd urandom read with 7 bits of entropy available
Populating dev cache
hwclock: can't open '/dev/misc/rtc': No such file or directory
Mon Sep 4 03:24:31 UTC 2017
hwclock: can't open '/dev/misc/rtc': No such file or directory
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
Running postinst /etc/rpm-postinsts/101-inetutils-inetd...
Running postinst /etc/rpm-postinsts/102-inetutils-ftpd...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Removing any system startup links for run-postinsts ...
INIT: Entering runlevel: 5
Configuring network interfaces... done.
Starting OpenBSD Secure Shell server: sshd
generating ssh RSA key...
generating ssh ECDSA key...
generating ssh DSA key...
generating ssh ED25519 key...
done.
hwclock: can't open '/dev/misc/rtc': No such file or directory
Starting network benchmark server: netserver.
Starting system log daemon...0
Starting kernel log daemon...0
Starting internet superserver: xinetd.
Start watchdog daemon...

QorIQ SDK (FSL Reference Distro) 2.0 ls1021atwr /dev/ttyS0

ls1021atwr login: root
root@ls1021atwr:~#

I don't know why? 

Labels (1)
0 Kudos
3 Replies

1,098 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello shunping lin,

Please add bootargs "ramdisk_size=10000000".


Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

1,098 Views
mihaitaivascu
Contributor III

Hello,

    I have the same issue but increasing the ramdisk_size did not helped. For me it appeared once I changed the load/entry addresses for kernel and ramdisk in the device tree.

    Before it was 0x10008000/0x18000000, now is 0x20008000/0x28000000. RAM is 1G.

https://community.nxp.com/thread/495366

Any other suggestions please?

Thanks,

      Mihaita

0 Kudos

1,098 Views
j_wallace
Contributor II

I got similar error when running a custom Linux distro on LS1043ARDB. I solved the issue by increasing the RAM block device size setup in the kernel configuration: CONFIG_BLK_DEV_RAM_SIZE

0 Kudos