<?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: Bugcheck and Accelerator board errors on DL585 box in ProLiant Servers - Netservers</title>
    <link>https://community.hpe.com/t5/proliant-servers-netservers/bugcheck-and-accelerator-board-errors-on-dl585-box/m-p/1073493#M16838</link>
    <description>The Stop 0x9C is a machine check exception.  Replace the cache module (DIMM).</description>
    <pubDate>Thu, 09 Apr 2009 11:26:38 GMT</pubDate>
    <dc:creator>Kedd Guyton</dc:creator>
    <dc:date>2009-04-09T11:26:38Z</dc:date>
    <item>
      <title>Bugcheck and Accelerator board errors on DL585 box</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/bugcheck-and-accelerator-board-errors-on-dl585-box/m-p/1073492#M16837</link>
      <description>&lt;!--!*#--&gt;Need assistance on a couple of isses with our DL585G1 box.&lt;BR /&gt;
1. The server rebooted unexpectedly yesterday and generated the bug check below,&lt;BR /&gt;
Blue Screen Trap (BugCheck, STOP: 0x0000009C (0x00000000, 0xF774D2B0, 0xF60A0000, 0x00000135))&lt;BR /&gt;
&lt;BR /&gt;
2. Also we get the following error message whenever the server is rebooted,&lt;BR /&gt;
Event description: Accelerator Board Status Change.  This trap signifies that the agent has detected a change in the status of an array accelerator cache board.  The current status is represented by the variable cpqDaAccelStatus.  User Action: If the accelerator board status is permDisabled(5), you may need to replace the accelerator board.&lt;BR /&gt;
Location: Slot 0&lt;BR /&gt;
Model: sa-5i&lt;BR /&gt;
Serial Number: P52AC0AUCRN0L2&lt;BR /&gt;
Total Memory: 49152&lt;BR /&gt;
Status: permDisabled&lt;BR /&gt;
Error Code: writeErr&lt;BR /&gt;
&lt;BR /&gt;
Below are a couple of sections int the ADU logs,&lt;BR /&gt;
ACU has encountered the following critical error while attempting to configure your controller:&lt;BR /&gt;
The array accelerator on the current array controller is not functioning properly.&lt;BR /&gt;
Parity errors occurred when trying to write data to the array accelerator's memory possibly due to a loose connection between the array accelerator and the current array controller. Array accelerator operations are permanently disabled.&lt;BR /&gt;
For more information, run the Array Diagnostics Utility. &lt;BR /&gt;
---------------------&lt;BR /&gt;
SLOT 0 Smart Array 5i Controller ERROR REPORT:&lt;BR /&gt;
&lt;BR /&gt;
   Array accelerator status:&lt;BR /&gt;
      Permanently disabled&lt;BR /&gt;
      Warranty alert&lt;BR /&gt;
   Array accelerator parity write errors: 1&lt;BR /&gt;
---------------------&lt;BR /&gt;
ACCELERATOR STATUS:&lt;BR /&gt;
   Logical Drive Disable Map: 0x00000000&lt;BR /&gt;
   Read Cache Size:           24 MBytes&lt;BR /&gt;
   Posted Write Size:         24 MBytes&lt;BR /&gt;
   Disable Flag:              0x00&lt;BR /&gt;
   Status:                    0x40000004&lt;BR /&gt;
   Disable Code:              0x0012&lt;BR /&gt;
   Total Memory Size:         48 MBytes&lt;BR /&gt;
   Battery Count:             1&lt;BR /&gt;
   Battery Status:            0x0001&lt;BR /&gt;
   Parity Read Errors:        0000&lt;BR /&gt;
   Parity Write Errors:       0001&lt;BR /&gt;
   Error Log:&lt;BR /&gt;
            00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
            00 00 01 00 00 00 00 10 00 0a 00 00 00 01 00 00 &lt;BR /&gt;
            00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &lt;BR /&gt;
   Failed Batteries:          0x0000&lt;BR /&gt;
   Board Present:             Yes&lt;BR /&gt;
   Accelerator Failure Map:   0x00000000&lt;BR /&gt;
   Max Error Log Entries:     16&lt;BR /&gt;
   NVRAM Load Status:         0x00&lt;BR /&gt;
   Memory Size Shift Factor:  0x0a&lt;BR /&gt;
   Non Battery Backed Memory: 0 MBytes&lt;BR /&gt;
   Memory State:              0x00&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Apr 2009 07:30:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/bugcheck-and-accelerator-board-errors-on-dl585-box/m-p/1073492#M16837</guid>
      <dc:creator>Fini Oladimeji</dc:creator>
      <dc:date>2009-04-08T07:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Bugcheck and Accelerator board errors on DL585 box</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/bugcheck-and-accelerator-board-errors-on-dl585-box/m-p/1073493#M16838</link>
      <description>The Stop 0x9C is a machine check exception.  Replace the cache module (DIMM).</description>
      <pubDate>Thu, 09 Apr 2009 11:26:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/bugcheck-and-accelerator-board-errors-on-dl585-box/m-p/1073493#M16838</guid>
      <dc:creator>Kedd Guyton</dc:creator>
      <dc:date>2009-04-09T11:26:38Z</dc:date>
    </item>
  </channel>
</rss>

