<?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>i.MX Processorsのトピックi.mx28 and large kernel with initramfs = oom killer</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296476#M36810</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm trying to use kernel combined with initramfs which is 8MB big (uncompressed ~25MB), but when kernel is booting some oom-killer actions are taken (output attached). I have 128MB of RAM so size of memory is not an issue. I suspect that problem is that uncompressed initramfs + kernel overlaps some memory region which should not be touched. Is the size of memory for uncompressed kernel along with initramfs limited somehow? Could anybody help me? I can add that when kernel and initramfs image are separated then system works fine.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-335950"&gt;initramfs.fail.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 May 2014 09:51:08 GMT</pubDate>
    <dc:creator>oskiercz</dc:creator>
    <dc:date>2014-05-13T09:51:08Z</dc:date>
    <item>
      <title>i.mx28 and large kernel with initramfs = oom killer</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296476#M36810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm trying to use kernel combined with initramfs which is 8MB big (uncompressed ~25MB), but when kernel is booting some oom-killer actions are taken (output attached). I have 128MB of RAM so size of memory is not an issue. I suspect that problem is that uncompressed initramfs + kernel overlaps some memory region which should not be touched. Is the size of memory for uncompressed kernel along with initramfs limited somehow? Could anybody help me? I can add that when kernel and initramfs image are separated then system works fine.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-335950"&gt;initramfs.fail.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 May 2014 09:51:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296476#M36810</guid>
      <dc:creator>oskiercz</dc:creator>
      <dc:date>2014-05-13T09:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: i.mx28 and large kernel with initramfs = oom killer</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296477#M36811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi oskiercz&lt;/P&gt;&lt;P&gt;for initramfs configuring please look link below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/305045"&gt;https://community.freescale.com/thread/305045&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 03:01:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296477#M36811</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-05-14T03:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: i.mx28 and large kernel with initramfs = oom killer</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296478#M36812</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi chipexpert,&lt;/P&gt;&lt;P&gt;I forgot to add that I have to use u-boot as a bootloader, which as far as I understand, doesn't allow me to use&lt;EM&gt; imx28_(ivt_)linux.sb &lt;/EM&gt;file (because it's booted itself, without any external bootloader), so second method from link you provided is not for me (third also because it's about separated images).&lt;/P&gt;&lt;P&gt;What I found out, that there is a size limit for kernel image (if initramfs is built in then overall size), here's a topic: &lt;A href="http://comments.gmane.org/gmane.linux.ports.arm.kernel/90067" title="http://comments.gmane.org/gmane.linux.ports.arm.kernel/90067"&gt;Discussing the Linux ARM kernel.&lt;/A&gt; I think that the actual cause of my problems.&lt;/P&gt;&lt;P&gt;Any opinion would be welcomed.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 06:27:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-mx28-and-large-kernel-with-initramfs-oom-killer/m-p/296478#M36812</guid>
      <dc:creator>oskiercz</dc:creator>
      <dc:date>2014-05-14T06:27:20Z</dc:date>
    </item>
  </channel>
</rss>

