<?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 OOM cause of reboot in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292699#M34274</link>
    <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I hv got the oom error (attached in this case) which caused the rebooot the controller.&lt;BR /&gt;&lt;BR /&gt;could you please suggest where is the exact problem?&lt;BR /&gt;&lt;BR /&gt;is this kernel issue? i m using 2.6.10 version.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;-mks&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 23 Oct 2008 09:07:24 GMT</pubDate>
    <dc:creator>monu_1</dc:creator>
    <dc:date>2008-10-23T09:07:24Z</dc:date>
    <item>
      <title>OOM cause of reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292699#M34274</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I hv got the oom error (attached in this case) which caused the rebooot the controller.&lt;BR /&gt;&lt;BR /&gt;could you please suggest where is the exact problem?&lt;BR /&gt;&lt;BR /&gt;is this kernel issue? i m using 2.6.10 version.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;-mks&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Oct 2008 09:07:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292699#M34274</guid>
      <dc:creator>monu_1</dc:creator>
      <dc:date>2008-10-23T09:07:24Z</dc:date>
    </item>
    <item>
      <title>Re: OOM cause of reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292700#M34275</link>
      <description>The problem is lack of memory. &lt;BR /&gt;This process oom-killer is from kernel and it is used to free some memory by killing processes. &lt;BR /&gt;See more here: &lt;BR /&gt;&lt;A href="http://www.wlug.org.nz/OomKiller" target="_blank"&gt;http://www.wlug.org.nz/OomKiller&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.win.tue.nl/~aeb/linux/lk/lk-9.html" target="_blank"&gt;http://www.win.tue.nl/~aeb/linux/lk/lk-9.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Thu, 23 Oct 2008 14:46:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292700#M34275</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2008-10-23T14:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: OOM cause of reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292701#M34276</link>
      <description>&amp;gt;&amp;gt; could you please suggest where is the exact problem?&lt;BR /&gt;&lt;BR /&gt;Lack of RAM causes this, but RAM can be real or swap.&lt;BR /&gt;&lt;BR /&gt;Now why does this happen?  The issue is with the app not being able to access RAM beyond real 4 GB.  It is not even able to access swap and swap out.  This happens because the kernel/OS port is for x86 and not for that particular arch, maybe the x86_64/amd64 port should be installed instead.&lt;BR /&gt;&lt;BR /&gt;Before you upgrade your real RAM, check for RAM errors.  Then install the x86_64/amd64 port instead.&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Ragu</description>
      <pubDate>Fri, 24 Oct 2008 06:46:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/oom-cause-of-reboot/m-p/4292701#M34276</guid>
      <dc:creator>Ragu_3</dc:creator>
      <dc:date>2008-10-24T06:46:55Z</dc:date>
    </item>
  </channel>
</rss>

