<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RAMDISK: incomplete write in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778852#M3433</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Before it was 0x10008000/0x18000000, now is 0x20008000/0x28000000. RAM is 1G.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="" href="https://community.nxp.com/thread/495366" style="color: #2989c5; text-decoration: none;" title="https://community.nxp.com/thread/495366"&gt;https://community.nxp.com/thread/495366&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other suggestions please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Mihaita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Feb 2019 09:00:53 GMT</pubDate>
    <dc:creator>mihaitaivascu</dc:creator>
    <dc:date>2019-02-13T09:00:53Z</dc:date>
    <item>
      <title>RAMDISK: incomplete write</title>
      <link>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778849#M3430</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;when we use rootfs which was made ourself, the kernel boot successfully, but have error message,following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;usb usb1-port1: over-current condition&lt;BR /&gt;usb usb2-port1: over-current condition&lt;BR /&gt;&lt;STRONG&gt;RAMDISK: incomplete write (16883 != 32768)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;write error&lt;/STRONG&gt;&lt;BR /&gt;VFS: Mounted root (ext2 filesystem) on device 1:0.&lt;BR /&gt;devtmpfs: mounted&lt;BR /&gt;Freeing unused kernel memory: 252K (8055d000 - 8059c000)&lt;BR /&gt;INIT: version 2.88 booting&lt;BR /&gt;Starting udev&lt;BR /&gt;udevd[157]: starting version 182&lt;BR /&gt;EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended&lt;BR /&gt;random: dd urandom read with 7 bits of entropy available&lt;BR /&gt;Populating dev cache&lt;BR /&gt;hwclock: can't open '/dev/misc/rtc': No such file or directory&lt;BR /&gt;Mon Sep 4 03:24:31 UTC 2017&lt;BR /&gt;hwclock: can't open '/dev/misc/rtc': No such file or directory&lt;BR /&gt;Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...&lt;BR /&gt;Running postinst /etc/rpm-postinsts/101-inetutils-inetd...&lt;BR /&gt;Running postinst /etc/rpm-postinsts/102-inetutils-ftpd...&lt;BR /&gt;update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)&lt;BR /&gt; Removing any system startup links for run-postinsts ...&lt;BR /&gt;INIT: Entering runlevel: 5&lt;BR /&gt;Configuring network interfaces... done.&lt;BR /&gt;Starting OpenBSD Secure Shell server: sshd&lt;BR /&gt; generating ssh RSA key...&lt;BR /&gt; generating ssh ECDSA key...&lt;BR /&gt; generating ssh DSA key...&lt;BR /&gt; generating ssh ED25519 key...&lt;BR /&gt;done.&lt;BR /&gt;hwclock: can't open '/dev/misc/rtc': No such file or directory&lt;BR /&gt;Starting network benchmark server: netserver.&lt;BR /&gt;Starting system log daemon...0&lt;BR /&gt;Starting kernel log daemon...0&lt;BR /&gt;Starting internet superserver: xinetd.&lt;BR /&gt;Start watchdog daemon...&lt;/P&gt;&lt;P&gt;QorIQ SDK (FSL Reference Distro) 2.0 ls1021atwr /dev/ttyS0&lt;/P&gt;&lt;P&gt;ls1021atwr login: root&lt;BR /&gt;&lt;A href="mailto:root@ls1021atwr:~"&gt;root@ls1021atwr:~# &lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know why?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Feb 2018 04:07:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778849#M3430</guid>
      <dc:creator>shunpinglin</dc:creator>
      <dc:date>2018-02-28T04:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: RAMDISK: incomplete write</title>
      <link>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778850#M3431</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2018 11:27:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778850#M3431</guid>
      <dc:creator>j_wallace</dc:creator>
      <dc:date>2018-05-25T11:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: RAMDISK: incomplete write</title>
      <link>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778851#M3432</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A _jive_internal="true" data-content-finding="Community" data-userid="304303" data-username="shunpinglin" href="https://community.nxp.com/people/shunpinglin"&gt;shunping lin&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please add bootargs "ramdisk_size=10000000".&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jul 2018 12:49:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778851#M3432</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2018-07-02T12:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: RAMDISK: incomplete write</title>
      <link>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778852#M3433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Before it was 0x10008000/0x18000000, now is 0x20008000/0x28000000. RAM is 1G.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="" href="https://community.nxp.com/thread/495366" style="color: #2989c5; text-decoration: none;" title="https://community.nxp.com/thread/495366"&gt;https://community.nxp.com/thread/495366&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other suggestions please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Mihaita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2019 09:00:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/RAMDISK-incomplete-write/m-p/778852#M3433</guid>
      <dc:creator>mihaitaivascu</dc:creator>
      <dc:date>2019-02-13T09:00:53Z</dc:date>
    </item>
  </channel>
</rss>

