<?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: Unexpected SHUTDOWN in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725785#M49840</link>
    <description>Hi,&lt;BR /&gt;see this link :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=990814" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=990814&lt;/A&gt;&lt;BR /&gt;Best regards</description>
    <pubDate>Tue, 07 Feb 2006 03:46:10 GMT</pubDate>
    <dc:creator>ALIOUA</dc:creator>
    <dc:date>2006-02-07T03:46:10Z</dc:date>
    <item>
      <title>Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725784#M49839</link>
      <description>HI ALL..&lt;BR /&gt;I AM USEING DL 380 AND DL 360 SERVERS. SOME OF THOSE MACHINES GET RESTART, WITHOUT GIVING ANY ERROR IN EVENT LOG. ONLY IN "ILM" I CAN FIND LOGED AS "ASR Detected by System ROM". WHAT COULD BE THE POSSILE REASON.. PLZ IF ANY BODY CAN TELL ME ABOUT THIS PROBLEM.&lt;BR /&gt;&lt;BR /&gt;CHEERS....&lt;BR /&gt;&lt;BR /&gt;ASIM MINHAS</description>
      <pubDate>Tue, 07 Feb 2006 03:33:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725784#M49839</guid>
      <dc:creator>Minhas</dc:creator>
      <dc:date>2006-02-07T03:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725785#M49840</link>
      <description>Hi,&lt;BR /&gt;see this link :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=990814" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=990814&lt;/A&gt;&lt;BR /&gt;Best regards</description>
      <pubDate>Tue, 07 Feb 2006 03:46:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725785#M49840</guid>
      <dc:creator>ALIOUA</dc:creator>
      <dc:date>2006-02-07T03:46:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725786#M49841</link>
      <description>dear ALIOUA,&lt;BR /&gt;&lt;BR /&gt;i have gone through all those.. but still the problem is there..</description>
      <pubDate>Tue, 07 Feb 2006 06:01:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725786#M49841</guid>
      <dc:creator>Minhas</dc:creator>
      <dc:date>2006-02-07T06:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725787#M49842</link>
      <description>Could be overheating?&lt;BR /&gt;Does the ASR occur during backup?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Matthijs</description>
      <pubDate>Tue, 07 Feb 2006 15:28:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725787#M49842</guid>
      <dc:creator>Matthijs Wijers_1</dc:creator>
      <dc:date>2006-02-07T15:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725788#M49843</link>
      <description>Automatic Server Recovery (ASR)&lt;BR /&gt;              The  Automatic Server Recovery is implemented using&lt;BR /&gt;              a "heartbeat" timer that continually  counts  down.&lt;BR /&gt;              The  driver  frequently reloads the counter to pre-&lt;BR /&gt;              vent it from counting down to  zero.   If  the  ASR&lt;BR /&gt;              counts  down to 0, it is assumed that the operating&lt;BR /&gt;              system is locked up and  the  system  automatically&lt;BR /&gt;              attempts to reboot.  Events which may contribute to&lt;BR /&gt;              the operating system locking up include:&lt;BR /&gt;&lt;BR /&gt;       *      A peripheral device (such as a PCI adapter) failing&lt;BR /&gt;              in such a way that numerous spurious interrupts are&lt;BR /&gt;              generated.&lt;BR /&gt;&lt;BR /&gt;       *      A high priority software application  consumes  all&lt;BR /&gt;              the  available  CPU  cycles  and does not allow the&lt;BR /&gt;              operating system scheduler to  run  the  ASR  timer&lt;BR /&gt;              reset process.&lt;BR /&gt;&lt;BR /&gt;       *      A  software  or  kernel  application  consumes  all&lt;BR /&gt;              available memory including the virtual memory space&lt;BR /&gt;              (i.e.  swap).   This may cause the operating system&lt;BR /&gt;              scheduler to cease functioning.&lt;BR /&gt;&lt;BR /&gt;       *      A critical operating system  component  such  as  a&lt;BR /&gt;              file  system  fails and causes the operating system&lt;BR /&gt;              scheduler to cease functioning.&lt;BR /&gt;&lt;BR /&gt;       *      Any other event besides an ASR timeout which causes&lt;BR /&gt;              a Non-Maskable Interrupt (NMI) to be generated.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;       The  ProLiant ASR feature is a hardware based timer.  If a&lt;BR /&gt;       true hardware failure occurs, the ProLiant Advanced Server&lt;BR /&gt;       Management  driver might not be called but the server will&lt;BR /&gt;       be reset as if the power switch was pressed.  The ProLiant&lt;BR /&gt;       ROM  code may log an event to the ProLiant Integrated Man-&lt;BR /&gt;       agement Log (IML) when the server reboots.&lt;BR /&gt;&lt;BR /&gt;       The ProLiant Advanced Server Management driver is notified&lt;BR /&gt;       via  a  Non-Maskable  Interrupt  (NMI).   If possible, the&lt;BR /&gt;       driver will attempt to perform the following actions:&lt;BR /&gt;&lt;BR /&gt;       *      Displays a message on the console stating the prob-&lt;BR /&gt;              lem&lt;BR /&gt;&lt;BR /&gt;       *      Makes  an  entry in the ProLiant Integrated Manage-&lt;BR /&gt;              ment Log (IML).&lt;BR /&gt;&lt;BR /&gt;       *      Attempts to gracefully shutdown the operating  sys-&lt;BR /&gt;              tem to close the file systems.&lt;BR /&gt;&lt;BR /&gt;       There  is  not  a guarantee that the operating system will&lt;BR /&gt;       gracefully shutdown. This depends on the type (software or&lt;BR /&gt;       hwardware)  and severity of the error condition.&lt;BR /&gt;&lt;BR /&gt;       Message:&lt;BR /&gt;              "ASR Detected by System ROM"&lt;BR /&gt;&lt;BR /&gt;       Description:&lt;BR /&gt;              This  message  indicates  that  the ProLiant&lt;BR /&gt;              Server ROM detected an  ASR  timeout.   This&lt;BR /&gt;              message is almost always present in the Pro-&lt;BR /&gt;              Liant Integrated Management Log when an  ASR&lt;BR /&gt;              timeout  occurs.   If this is the ONLY "ASR"&lt;BR /&gt;              message logged to  the  ProLiant  Integrated&lt;BR /&gt;              Management  Log, this may be indicative of a&lt;BR /&gt;              hardware failure (such as a  non-correctable&lt;BR /&gt;              ECC  error  on a memory DIMM).  The ASR fea-&lt;BR /&gt;              ture on a ProLiant server  will  hard  reset&lt;BR /&gt;              the  server when the timeout expires with no&lt;BR /&gt;              software intervention required.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Matthijs</description>
      <pubDate>Tue, 07 Feb 2006 15:42:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725788#M49843</guid>
      <dc:creator>Matthijs Wijers_1</dc:creator>
      <dc:date>2006-02-07T15:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725789#M49844</link>
      <description>We are seeing the exact same issue on two Proliant DL385's running RHEL 4 Update 2. Both servers experience unexpected reboots and the only error is the "ASR Detected by System ROM" in ILM. As soon as we disable ASR, the problem goes away and the servers run fine. I think this is a bug of some sort in ASR.&lt;BR /&gt;&lt;BR /&gt;-Dave</description>
      <pubDate>Wed, 08 Feb 2006 12:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725789#M49844</guid>
      <dc:creator>David Kennamer</dc:creator>
      <dc:date>2006-02-08T12:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725790#M49845</link>
      <description>Dear David Kennamer!!!&lt;BR /&gt;&lt;BR /&gt;the problem is when i tried to disable ASR. my server start hanging... i can understand.. y ??&lt;BR /&gt;&lt;BR /&gt;Asim Minhas</description>
      <pubDate>Thu, 09 Feb 2006 03:37:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725790#M49845</guid>
      <dc:creator>Minhas</dc:creator>
      <dc:date>2006-02-09T03:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725791#M49846</link>
      <description>No, when ASR is enabled on my servers, the server reboots at various times and with no errors. When ASR is disabled, the servers run fine and without any crashes or reboots.</description>
      <pubDate>Thu, 09 Feb 2006 10:28:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725791#M49846</guid>
      <dc:creator>David Kennamer</dc:creator>
      <dc:date>2006-02-09T10:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: Unexpected SHUTDOWN</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725792#M49847</link>
      <description>I also have same case too ! &lt;BR /&gt;&lt;BR /&gt;DL385 with AMD280 running RHEL4x86_AS with U3 that I also have such problem ASR ...&lt;BR /&gt;then server re-start.&lt;BR /&gt;&lt;BR /&gt;I will try to dis-able the ASR to see problem solve or not ! &lt;BR /&gt;&lt;BR /&gt;Thanks your experiences sharing ....&lt;BR /&gt;&lt;BR /&gt;Cody.&lt;BR /&gt;</description>
      <pubDate>Mon, 01 May 2006 22:24:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/unexpected-shutdown/m-p/3725792#M49847</guid>
      <dc:creator>Cody Chen</dc:creator>
      <dc:date>2006-05-01T22:24:00Z</dc:date>
    </item>
  </channel>
</rss>

