<?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: Testing Memory in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470338#M775210</link>
    <description>Thank you all for the replys.  Is there anything that you could recommend for a test procedure that would allow me to test the servers for a memory failure, or is this something that doesn't even make sense to test?</description>
    <pubDate>Tue, 05 Dec 2000 18:22:57 GMT</pubDate>
    <dc:creator>brian bakke</dc:creator>
    <dc:date>2000-12-05T18:22:57Z</dc:date>
    <item>
      <title>Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470331#M775203</link>
      <description>good afternoon,&lt;BR /&gt;we are running HP-UX on our production servers and we are looking at testing the memory on the servers to see what type of alarms corrupt memory will generate - does anyone have any ideas on how to go about doing this?  TIA</description>
      <pubDate>Mon, 04 Dec 2000 22:39:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470331#M775203</guid>
      <dc:creator>brian bakke</dc:creator>
      <dc:date>2000-12-04T22:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470332#M775204</link>
      <description>No.  I know of no way to simulate a failure on a memory card.  But memory cards should be monitored with EMS (Event monitoring service).  the state of your event monitoring can be checked with:&lt;BR /&gt;&lt;BR /&gt;/etc/opt/resmon/lbin/moncheck</description>
      <pubDate>Mon, 04 Dec 2000 23:36:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470332#M775204</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2000-12-04T23:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470333#M775205</link>
      <description>Thanks - I haven't been able to find any info on testing the memory, so I figured it couldn't be done.  Would there be any benefit from changing the memory parameters in the kernal? TIA</description>
      <pubDate>Tue, 05 Dec 2000 00:25:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470333#M775205</guid>
      <dc:creator>brian bakke</dc:creator>
      <dc:date>2000-12-05T00:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470334#M775206</link>
      <description>The kernel modification for memory will be of help if you understand what result will be. Read the attached guide for kernel parameter settings and their meaning.&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html&lt;/A&gt;</description>
      <pubDate>Tue, 05 Dec 2000 08:49:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470334#M775206</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-12-05T08:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470335#M775207</link>
      <description>I supose that a unrecoverable memory error will force a reboot of the box.&lt;BR /&gt;&lt;BR /&gt;Memory errors are managed by hardware that can realocate blocks an deactivate bad areas.&lt;BR /&gt;&lt;BR /&gt;In order to test no more memory allocation erros you can write a simple C that allocate lots of memory.&lt;BR /&gt;&lt;BR /&gt;Hope This help.</description>
      <pubDate>Tue, 05 Dec 2000 08:54:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470335#M775207</guid>
      <dc:creator>Carlos Fernandez Riera</dc:creator>
      <dc:date>2000-12-05T08:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470336#M775208</link>
      <description>Apart from memory check occuring at boot, if you have fastboot disabled, you can use the "Support Tools Manager" (stm or xstm) to test or exercise the memory.</description>
      <pubDate>Tue, 05 Dec 2000 09:01:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470336#M775208</guid>
      <dc:creator>Tommy Palo</dc:creator>
      <dc:date>2000-12-05T09:01:53Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470337#M775209</link>
      <description>This is handled by the hardware. You have ECC SDRAM memory which will correct single bit errors. Once too many errors occur at the same location the memory location is marked as bad and is no longer used. I'm sorry that I don't know the exact verbiage used, but I suspect that either your CE can look it up or possibly you  may find it on HP's web site. It is extremely rare to see a problem on a system that has been is use for a while. If it happens at all it happens when it is first installed, usually within the first 30 days.&lt;BR /&gt;&lt;BR /&gt;Above all else, do not try and simulate a failure, you can fry a board that way. I'm sure that your friendly local memory salesman could supply you with a bad board if you are bound and determined to try this. &lt;BR /&gt;&lt;BR /&gt;FYI, ODE (Offline Diagnostic Environment) has memory tests available in it if you wish to take the system down and perform tests.</description>
      <pubDate>Tue, 05 Dec 2000 16:29:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470337#M775209</guid>
      <dc:creator>paul courry</dc:creator>
      <dc:date>2000-12-05T16:29:51Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470338#M775210</link>
      <description>Thank you all for the replys.  Is there anything that you could recommend for a test procedure that would allow me to test the servers for a memory failure, or is this something that doesn't even make sense to test?</description>
      <pubDate>Tue, 05 Dec 2000 18:22:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/testing-memory/m-p/2470338#M775210</guid>
      <dc:creator>brian bakke</dc:creator>
      <dc:date>2000-12-05T18:22:57Z</dc:date>
    </item>
  </channel>
</rss>

