<?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: memtest in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763634#M16613</link>
    <description>Hass,&lt;BR /&gt;&lt;BR /&gt;Unless otherwise you do research on this error for others, google won't get any good answer for this type of question, see this thread on the same error...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://lists.debian.org/debian-alpha/2004/11/msg00041.html" target="_blank"&gt;http://lists.debian.org/debian-alpha/2004/11/msg00041.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://groups.google.com/group/comp.os.vms/browse_thread/thread/15cdeac3ce96834a/b10be84e29dcf564?lnk=st&amp;amp;q=alpha+memtest+not+valid+zone+address+dynamic&amp;amp;rnum=1&amp;amp;hl=en#b10be84e29dcf564" target="_blank"&gt;http://groups.google.com/group/comp.os.vms/browse_thread/thread/15cdeac3ce96834a/b10be84e29dcf564?lnk=st&amp;amp;q=alpha+memtest+not+valid+zone+address+dynamic&amp;amp;rnum=1&amp;amp;hl=en#b10be84e29dcf564&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
    <pubDate>Sun, 02 Apr 2006 05:38:58 GMT</pubDate>
    <dc:creator>Arch_Muthiah</dc:creator>
    <dc:date>2006-04-02T05:38:58Z</dc:date>
    <item>
      <title>memtest</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763630#M16609</link>
      <description>guys im sorry if i make any distrupe but i need solution for this &lt;BR /&gt;when i run the cmd memtest in SRM ruslte for that is 00000000 is not valid zone address Use dynamic to list  valid Zone this the erro im getting but when i do reboot it change can any one tell me the defnition for this plz &lt;BR /&gt;        thanking you hass</description>
      <pubDate>Fri, 31 Mar 2006 17:46:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763630#M16609</guid>
      <dc:creator>hass_2k</dc:creator>
      <dc:date>2006-03-31T17:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: memtest</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763631#M16610</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;why do you want to do an explicit memory test? The normal test will do that too. Have a look at&lt;BR /&gt;&lt;A href="http://ftp.digital.com/pub/digital/info/semiconductor/literature/srmcons.pdf" target="_blank"&gt;http://ftp.digital.com/pub/digital/info/semiconductor/literature/srmcons.pdf&lt;/A&gt;&lt;BR /&gt;and look for the desciption of memtest. There are some examples of how to use it.&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Sat, 01 Apr 2006 07:39:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763631#M16610</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2006-04-01T07:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: memtest</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763632#M16611</link>
      <description>Just one information. Once we had a system with problems, memexer (command that test the memory) did not detected any problems, but as you start the system and run some memory intensive application, or a simple backup with the vdump command, the system crashed. So, I won't trust too much in memexer.</description>
      <pubDate>Sat, 01 Apr 2006 11:38:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763632#M16611</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-04-01T11:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: memtest</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763633#M16612</link>
      <description>Hass,&lt;BR /&gt;&lt;BR /&gt;Memtest is very critical cmnd, does four difft types (t1 thru t4) of intensive mem tests. To make it work, better we have to supply correct parameters, especially we should specify the section of memory we want to test. The important thing I hope you know is that the memtest command will destroy the data in the specified section of&lt;BR /&gt;memory we passed!!!.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
      <pubDate>Sun, 02 Apr 2006 05:33:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763633#M16612</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2006-04-02T05:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: memtest</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763634#M16613</link>
      <description>Hass,&lt;BR /&gt;&lt;BR /&gt;Unless otherwise you do research on this error for others, google won't get any good answer for this type of question, see this thread on the same error...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://lists.debian.org/debian-alpha/2004/11/msg00041.html" target="_blank"&gt;http://lists.debian.org/debian-alpha/2004/11/msg00041.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://groups.google.com/group/comp.os.vms/browse_thread/thread/15cdeac3ce96834a/b10be84e29dcf564?lnk=st&amp;amp;q=alpha+memtest+not+valid+zone+address+dynamic&amp;amp;rnum=1&amp;amp;hl=en#b10be84e29dcf564" target="_blank"&gt;http://groups.google.com/group/comp.os.vms/browse_thread/thread/15cdeac3ce96834a/b10be84e29dcf564?lnk=st&amp;amp;q=alpha+memtest+not+valid+zone+address+dynamic&amp;amp;rnum=1&amp;amp;hl=en#b10be84e29dcf564&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
      <pubDate>Sun, 02 Apr 2006 05:38:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/memtest/m-p/3763634#M16613</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2006-04-02T05:38:58Z</dc:date>
    </item>
  </channel>
</rss>

