<?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 ProLiant BL460c G1 server with RHEL rebooting in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748249#M43533</link>
    <description>Hi Folks,&lt;BR /&gt;&lt;BR /&gt;One of our server which is installed with Red Hat Enterprise Linux AS release 4 (Nahant Update 4) is repeatedly getting rebooting. In the var log messages below call trace is found.&lt;BR /&gt;&lt;BR /&gt;kernel: Call Trace:&lt;FFFFFFFF8015DE30&gt;{__alloc_pages+768} &lt;FFFFFFFF8015DEC9&gt;{__get_free_pages+11}&lt;BR /&gt;kernel:        &lt;FFFFFFFF80161004&gt;{kmem_getpages+36} &lt;FFFFFFFF8016179C&gt;{cache_alloc_refill+612}&lt;BR /&gt;kernel:        &lt;FFFFFFFF80161467&gt;{__kmalloc+123} &lt;FFFFFFFFA03B2AC1&gt;{:psfs:fix_nodes+294}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03ADBA2&gt;{:psfs:psfs_insert_item+147} &lt;FFFFFFFFA03C7AA2&gt;{:psfs:psfs_new_inode+1473}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03C34E9&gt;{:psfs:psfs_create_inode_common+359}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F2DBD&gt;{:psfs:psfs_linvfs_create_inode+270}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F2C29&gt;{:psfs:psfs_linvfs_create_followup+0}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F56D0&gt;{:psfs:psfs_linvfs_permission+114}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F4685&gt;{:psfs:psfs_linvfs_mkdir+411} &lt;FFFFFFFF801878E9&gt;{vfs_mkdir+200}&lt;BR /&gt;kernel:        &lt;FFFFFFFF801879CD&gt;{sys_mkdir+154} &lt;FFFFFFFF801EA029&gt;{__up_read+16}&lt;BR /&gt;kernel:        &lt;FFFFFFFF8012592F&gt;{sysenter_do_call+27}&lt;BR /&gt;kernel: Mem-info:&lt;BR /&gt;&lt;BR /&gt;please let me know if any one has any suggestion on these frequent reboots&lt;/FFFFFFFF8012592F&gt;&lt;/FFFFFFFF801EA029&gt;&lt;/FFFFFFFF801879CD&gt;&lt;/FFFFFFFF801878E9&gt;&lt;/FFFFFFFFA03F4685&gt;&lt;/FFFFFFFFA03F56D0&gt;&lt;/FFFFFFFFA03F2C29&gt;&lt;/FFFFFFFFA03F2DBD&gt;&lt;/FFFFFFFFA03C34E9&gt;&lt;/FFFFFFFFA03C7AA2&gt;&lt;/FFFFFFFFA03ADBA2&gt;&lt;/FFFFFFFFA03B2AC1&gt;&lt;/FFFFFFFF80161467&gt;&lt;/FFFFFFFF8016179C&gt;&lt;/FFFFFFFF80161004&gt;&lt;/FFFFFFFF8015DEC9&gt;&lt;/FFFFFFFF8015DE30&gt;</description>
    <pubDate>Thu, 03 Feb 2011 17:17:46 GMT</pubDate>
    <dc:creator>Kaps_2</dc:creator>
    <dc:date>2011-02-03T17:17:46Z</dc:date>
    <item>
      <title>ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748249#M43533</link>
      <description>Hi Folks,&lt;BR /&gt;&lt;BR /&gt;One of our server which is installed with Red Hat Enterprise Linux AS release 4 (Nahant Update 4) is repeatedly getting rebooting. In the var log messages below call trace is found.&lt;BR /&gt;&lt;BR /&gt;kernel: Call Trace:&lt;FFFFFFFF8015DE30&gt;{__alloc_pages+768} &lt;FFFFFFFF8015DEC9&gt;{__get_free_pages+11}&lt;BR /&gt;kernel:        &lt;FFFFFFFF80161004&gt;{kmem_getpages+36} &lt;FFFFFFFF8016179C&gt;{cache_alloc_refill+612}&lt;BR /&gt;kernel:        &lt;FFFFFFFF80161467&gt;{__kmalloc+123} &lt;FFFFFFFFA03B2AC1&gt;{:psfs:fix_nodes+294}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03ADBA2&gt;{:psfs:psfs_insert_item+147} &lt;FFFFFFFFA03C7AA2&gt;{:psfs:psfs_new_inode+1473}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03C34E9&gt;{:psfs:psfs_create_inode_common+359}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F2DBD&gt;{:psfs:psfs_linvfs_create_inode+270}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F2C29&gt;{:psfs:psfs_linvfs_create_followup+0}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F56D0&gt;{:psfs:psfs_linvfs_permission+114}&lt;BR /&gt;kernel:        &lt;FFFFFFFFA03F4685&gt;{:psfs:psfs_linvfs_mkdir+411} &lt;FFFFFFFF801878E9&gt;{vfs_mkdir+200}&lt;BR /&gt;kernel:        &lt;FFFFFFFF801879CD&gt;{sys_mkdir+154} &lt;FFFFFFFF801EA029&gt;{__up_read+16}&lt;BR /&gt;kernel:        &lt;FFFFFFFF8012592F&gt;{sysenter_do_call+27}&lt;BR /&gt;kernel: Mem-info:&lt;BR /&gt;&lt;BR /&gt;please let me know if any one has any suggestion on these frequent reboots&lt;/FFFFFFFF8012592F&gt;&lt;/FFFFFFFF801EA029&gt;&lt;/FFFFFFFF801879CD&gt;&lt;/FFFFFFFF801878E9&gt;&lt;/FFFFFFFFA03F4685&gt;&lt;/FFFFFFFFA03F56D0&gt;&lt;/FFFFFFFFA03F2C29&gt;&lt;/FFFFFFFFA03F2DBD&gt;&lt;/FFFFFFFFA03C34E9&gt;&lt;/FFFFFFFFA03C7AA2&gt;&lt;/FFFFFFFFA03ADBA2&gt;&lt;/FFFFFFFFA03B2AC1&gt;&lt;/FFFFFFFF80161467&gt;&lt;/FFFFFFFF8016179C&gt;&lt;/FFFFFFFF80161004&gt;&lt;/FFFFFFFF8015DEC9&gt;&lt;/FFFFFFFF8015DE30&gt;</description>
      <pubDate>Thu, 03 Feb 2011 17:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748249#M43533</guid>
      <dc:creator>Kaps_2</dc:creator>
      <dc:date>2011-02-03T17:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748250#M43534</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;You may need a newer version of RH AS to run on these blades.&lt;BR /&gt;&lt;BR /&gt;I suggest update 7 or newer.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 03 Feb 2011 17:55:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748250#M43534</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2011-02-03T17:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748251#M43535</link>
      <description>the thing is that we cant upgrade the OS as we are using polyserve on the server. So uprading the server is not a feseable option.</description>
      <pubDate>Thu, 03 Feb 2011 18:09:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748251#M43535</guid>
      <dc:creator>Kaps_2</dc:creator>
      <dc:date>2011-02-03T18:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748252#M43536</link>
      <description>What preceding activities were done to your server that started the issue?&lt;BR /&gt;&lt;BR /&gt;Did it just start all of a sudden with regularity?&lt;BR /&gt;&lt;BR /&gt;Things just do not start happening without a precedent activity done to it -- i.e. patching, firmware, etc.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Feb 2011 15:18:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748252#M43536</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-02-04T15:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748253#M43537</link>
      <description>as far as I am aware there was no change done to this server</description>
      <pubDate>Fri, 04 Feb 2011 16:12:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748253#M43537</guid>
      <dc:creator>Kaps_2</dc:creator>
      <dc:date>2011-02-04T16:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748254#M43538</link>
      <description>I suggest you perform Diagnostics if it is indeed true there was nothing done prior on this environment. &lt;BR /&gt;&lt;BR /&gt;What about performance historicals if youhave any? Are there any indications of new loading patterns, increased load, applications changes, etc?&lt;BR /&gt;&lt;BR /&gt;As far as Diagnostics - I'd start with Memory diagnostics -- Linux or the Proliant if it has one.&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Feb 2011 16:20:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748254#M43538</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-02-04T16:20:56Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748255#M43539</link>
      <description>Is there any inbuild dignostics in linux which I an use to perform memory check without taking a downtime?</description>
      <pubDate>Fri, 04 Feb 2011 16:24:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748255#M43539</guid>
      <dc:creator>Kaps_2</dc:creator>
      <dc:date>2011-02-04T16:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant BL460c G1 server with RHEL rebooting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748256#M43540</link>
      <description>I know of none unfortunately. And I don;t think it will be non-intrusive if there is.&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Feb 2011 16:27:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-bl460c-g1-server-with-rhel-rebooting/m-p/4748256#M43540</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-02-04T16:27:01Z</dc:date>
    </item>
  </channel>
</rss>

