<?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: rx4640 component failures in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981236#M2398</link>
    <description>I've personally seen failures proximate to and triggered by a hardware upgrade or a hardware reconfiguration, and I've seen failures related to an upgrade or a change only by onset time.  This on VAX, on Alpha, on Integrity, and on IA-32 and Intel 64 iron.  Old VAX iron and PDP-11 iron was notorious for interconnected failures; anybody that's worked on that can remember swapping boards around to find a matched set of memory modules and slots, for instance.  (Shudder.)&lt;BR /&gt;&lt;BR /&gt;It's also possible to mechanically damage various gear during the repairs.  Things do sometimes get bumped.&lt;BR /&gt;&lt;BR /&gt;Follow the troubleshooting sequence for the particular failing component.  This may well involve re-seating various boards, and potentially the mechanical reseating of or the replacement of the processor or processor module.&lt;BR /&gt;&lt;BR /&gt;Conductive metal filaments can also migrate around from the casing or from a raised floor, and these cases can be difficult to find and to resolve.&lt;BR /&gt;&lt;BR /&gt;If anti-static procedures were not followed during the memory upgrade, do rethink that particular decision.&lt;BR /&gt;&lt;BR /&gt;Short of a root cause analysis for this particular failure, little can be ascertained from what we might know here.  What I have posted are simply guesses.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC&lt;BR /&gt;</description>
    <pubDate>Wed, 18 Apr 2007 09:18:12 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-04-18T09:18:12Z</dc:date>
    <item>
      <title>rx4640 component failures</title>
      <link>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981234#M2396</link>
      <description>Following incident happened with me on rx4640;&lt;BR /&gt;Out of 4 cpus 1 failed upon adding new memory to the system. I have worked with alpha servers for years. Never observe such cases. &lt;BR /&gt;&lt;BR /&gt;Do you have any comments regarding these new bread of servers in terms of component failure cases?&lt;BR /&gt;</description>
      <pubDate>Sat, 14 Apr 2007 01:24:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981234#M2396</guid>
      <dc:creator>DR M.JAVED K JADOON(PHD</dc:creator>
      <dc:date>2007-04-14T01:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: rx4640 component failures</title>
      <link>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981235#M2397</link>
      <description>How did you notice that one CPU failed.&lt;BR /&gt;&lt;BR /&gt;Have we tried running online diags on the system and check.....&lt;BR /&gt;&lt;BR /&gt;If the memory has been installed by HP CE or all precaution like anti static band etc have been taken care of then its very unlikely that installing/replacing a component will fail the other..</description>
      <pubDate>Sun, 15 Apr 2007 19:17:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981235#M2397</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2007-04-15T19:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: rx4640 component failures</title>
      <link>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981236#M2398</link>
      <description>I've personally seen failures proximate to and triggered by a hardware upgrade or a hardware reconfiguration, and I've seen failures related to an upgrade or a change only by onset time.  This on VAX, on Alpha, on Integrity, and on IA-32 and Intel 64 iron.  Old VAX iron and PDP-11 iron was notorious for interconnected failures; anybody that's worked on that can remember swapping boards around to find a matched set of memory modules and slots, for instance.  (Shudder.)&lt;BR /&gt;&lt;BR /&gt;It's also possible to mechanically damage various gear during the repairs.  Things do sometimes get bumped.&lt;BR /&gt;&lt;BR /&gt;Follow the troubleshooting sequence for the particular failing component.  This may well involve re-seating various boards, and potentially the mechanical reseating of or the replacement of the processor or processor module.&lt;BR /&gt;&lt;BR /&gt;Conductive metal filaments can also migrate around from the casing or from a raised floor, and these cases can be difficult to find and to resolve.&lt;BR /&gt;&lt;BR /&gt;If anti-static procedures were not followed during the memory upgrade, do rethink that particular decision.&lt;BR /&gt;&lt;BR /&gt;Short of a root cause analysis for this particular failure, little can be ascertained from what we might know here.  What I have posted are simply guesses.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Apr 2007 09:18:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/rx4640-component-failures/m-p/3981236#M2398</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-04-18T09:18:12Z</dc:date>
    </item>
  </channel>
</rss>

