<?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: CPU error for MICROVAX 3100 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011118#M37783</link>
    <description>&lt;BR /&gt;Thanks for the responses.&lt;BR /&gt;&lt;BR /&gt;Prasad</description>
    <pubDate>Fri, 01 Jun 2007 10:40:39 GMT</pubDate>
    <dc:creator>prasad_35</dc:creator>
    <dc:date>2007-06-01T10:40:39Z</dc:date>
    <item>
      <title>CPU error for MICROVAX 3100</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011115#M37780</link>
      <description>&lt;BR /&gt;Hi when I do a "show err " I did notice couple of errors as below :&lt;BR /&gt;&lt;BR /&gt;Device                           Error Coun&lt;BR /&gt;CPU                                      1&lt;BR /&gt;PAA0:                                    2&lt;BR /&gt;PAB0:                                    1&lt;BR /&gt;PTA0:                                    1&lt;BR /&gt;$5$MIA5: (TF867B)                       22&lt;BR /&gt;&lt;BR /&gt;Upon searching for the CPU error this what I could see.. Can some pleasae let me know how critical this error is and how to resolve this.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; ******************************* ENTRY      55. *******************************&lt;BR /&gt; ERROR SEQUENCE 16784.                           LOGGED ON:        SID 13000202&lt;BR /&gt; DATE/TIME 12-OCT-2006 05:06:33.79                            SYS_TYPE 05230E01&lt;BR /&gt; SYSTEM UPTIME: 43 DAYS 11:48:31&lt;BR /&gt; SCS NODE: ASCENT                                              VAX/VMS V6.2&lt;BR /&gt; &lt;BR /&gt; INT54 ERROR  KA681-AA  CPU Microcode Rev # 2.  CONSOLE FW REV# 2.3&lt;BR /&gt;                      Standard Microcode Patch    Patch Rev # 1.&lt;BR /&gt; &lt;BR /&gt;       REVISION        00000000&lt;BR /&gt;       SYSTAT          00000001&lt;BR /&gt;                                       ATTEMPTING RECOVERY&lt;BR /&gt;       FLAGS           00000002&lt;BR /&gt;                                       KA681-AA subpacket&lt;BR /&gt; &lt;BR /&gt; KA681 REGISTER SUBPACKET&lt;BR /&gt; &lt;BR /&gt;       BPCR            ECC80024&lt;BR /&gt;       PAMODE          00000000&lt;BR /&gt;                                       30 bit physical address mode &lt;BR /&gt;       MMEPTE          8995D314&lt;BR /&gt;       MMESTS          1C008000&lt;BR /&gt;       PCSCR           01000200&lt;BR /&gt;                                       Patchable control store enabled&lt;BR /&gt;                                       standard microcode patch&lt;BR /&gt;                                       CPU microcode Patch Rev # = 1.&lt;BR /&gt;       ICSR            00000001&lt;BR /&gt;                                       virtual instruction cache enabled&lt;BR /&gt;       ECR             000000CA&lt;BR /&gt;                                       full external interval timer enabled&lt;BR /&gt;       TBSTS           800001D0&lt;BR /&gt;       PCCTL           FFFFFE13&lt;BR /&gt;                                       pcache enabled for D-stream reference&lt;BR /&gt;                                       pcache enabled for I-stream reference&lt;BR /&gt;                                       pcache parity error detection enabled&lt;BR /&gt;                                       pcache redundancy elements enabled&lt;BR /&gt;       PCSTS           FFFFF800&lt;BR /&gt;       CCTL            00000007&lt;BR /&gt;                                       backup cache enabled&lt;BR /&gt;                                       bcache tag ram speed:&lt;BR /&gt;                                       read = 4 cycles, write = 4 cycles&lt;BR /&gt;                                       bcache data ram speed:&lt;BR /&gt;                                       read = 3 cycles, write = 4 cycles&lt;BR /&gt;                                       128 kilobyte backup cache&lt;BR /&gt;       BCEDSTS         00000000&lt;BR /&gt;       BCETSTS         000000E2&lt;BR /&gt;                                       BCACHE TAG CORRECTABLE ECC ERROR&lt;BR /&gt;                                       data stream tag lookup&lt;BR /&gt;       MESR            000CB000&lt;BR /&gt;       MMCDSR          0994DE00&lt;BR /&gt;                                       2600 cycles before disown write tmeout&lt;BR /&gt;                                       enable logging soft errors&lt;BR /&gt;                                       CQBIC on CP_I02&lt;BR /&gt;       CESR            00000000&lt;BR /&gt;       CMCDSR          0000C108&lt;BR /&gt;                                       DMA prefetching enabled&lt;BR /&gt;                                       3200 Cycles Before NDAL Timeout&lt;BR /&gt;                                       144 cycles before cp1 mt timeout&lt;BR /&gt;                                       144000 cycles before cp2 mt timeout&lt;BR /&gt;                                       cp1 interrupts pending:&lt;BR /&gt;                                       none&lt;BR /&gt;                                       cp2 interrupts pending:&lt;BR /&gt;                                       none&lt;BR /&gt;       CEFSTS          00019200&lt;BR /&gt;       NESTS           00000000&lt;BR /&gt;       NEOCMD          0000F004&lt;BR /&gt;       NEICMD          00000000&lt;BR /&gt;       DSER            00000000&lt;BR /&gt;       CBTCR           00004000&lt;BR /&gt;                                       CDAL Bus Timeout Interval = 16.384 MSEC&lt;BR /&gt;       MMEADR          00008AFC&lt;BR /&gt;       VMAR            000007E0&lt;BR /&gt;       TBADR           00000000&lt;BR /&gt;       PCADR           FFFFFFF8&lt;BR /&gt;       BCEDIDX         00000000&lt;BR /&gt;       BCEDECC         00000000&lt;BR /&gt;       BCETIDX         07A3CFA0&lt;BR /&gt;                                       bcache tag error address &lt;BR /&gt;                                       Index  = 0E7D&lt;BR /&gt;                                       Tag  = 3D1(X)&lt;BR /&gt;       BCETAG          07AB1200&lt;BR /&gt;                                       Tag block in error valid&lt;BR /&gt;                                       bcache tag: stored check bits = 22(X)&lt;BR /&gt;                                       bcache error tag  = 3D5(X)&lt;BR /&gt;       MEAR            08406010&lt;BR /&gt;       MOAMR           00000000&lt;BR /&gt;                                       &lt;BR /&gt;       CSEAR1          00000000&lt;BR /&gt;       CSEAR2          00000000&lt;BR /&gt;       CIOEAR1         0000465C&lt;BR /&gt;       CIOEAR2         00000300&lt;BR /&gt;       CNEAR           00000000&lt;BR /&gt;       CEFADR          E0000300&lt;BR /&gt;       NEOADR          07B69CE0&lt;BR /&gt;       NEDATHI         00000000&lt;BR /&gt;       NEDATLO         00000000&lt;BR /&gt;       QBEAR           0000000C&lt;BR /&gt;       DEAR            00000000&lt;BR /&gt;       IPCR0               0020&lt;BR /&gt;                                       Local Memory External Access Enabled&lt;BR /&gt;</description>
      <pubDate>Thu, 31 May 2007 16:47:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011115#M37780</guid>
      <dc:creator>prasad_35</dc:creator>
      <dc:date>2007-05-31T16:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: CPU error for MICROVAX 3100</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011116#M37781</link>
      <description>Prasad,&lt;BR /&gt;&lt;BR /&gt;  Here's the simple description:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;  BCACHE TAG CORRECTABLE ECC ERROR&lt;BR /&gt;&lt;BR /&gt;  So, some data path in a cache has dropped a bit, which has been detected and corrected by ECC.&lt;BR /&gt;&lt;BR /&gt;  Since it's a VAX, this is very old hardware. You have to expect the occasional error. The hardware itself has fixed the error, so, from an application perspective there is no problem.&lt;BR /&gt;&lt;BR /&gt;  The criticality depends on what the system does. If it's running a nuclear power plant, I'd be concerned, and would look at upgrading the hardware. On the other hand if the system has a less critical role, I'd make a note that it's happened and watch for repeats. It may be a proverbial cosmic ray, nothing to do with the age of the hardware, just a fluke event which will never be repeated. On the other hand, it might be the first indicator of the hardware failing through old age.&lt;BR /&gt;&lt;BR /&gt;  About the only way to "fix" this type of problem in a 3100 is to find another one and replace the hardware, but any 3100 you find will probably be in a similar condition and may well suffer the same fault (on the other hand, they're likely to be cheap, if not free!). Another option is to upgrade the hardware, either to Alpha or Integrity, or, if you're stuck on an OpenVMS version as ancient as your hardware, maybe consider one of the VAX emulators?</description>
      <pubDate>Thu, 31 May 2007 19:37:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011116#M37781</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2007-05-31T19:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: CPU error for MICROVAX 3100</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011117#M37782</link>
      <description>If this system has been up all the time since then, it's probably a transient (like John suggested.)&lt;BR /&gt;&lt;BR /&gt;I have a 3100 that just sits around serving up some stuff that I don't have anyplace else  (because of licensing) and it does things like that occasionally. (I do have a spare 3100 just in case.)&lt;BR /&gt;&lt;BR /&gt;Maybe a power or temperature glitch. If you haven't had the cover off for a while, you could have a dust-bunny infestation. One time I had a memory error and found some books stacked up against the one of the vents. That was years ago and the old beast is still humming away.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 May 2007 21:02:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011117#M37782</guid>
      <dc:creator>Doug Phillips</dc:creator>
      <dc:date>2007-05-31T21:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: CPU error for MICROVAX 3100</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011118#M37783</link>
      <description>&lt;BR /&gt;Thanks for the responses.&lt;BR /&gt;&lt;BR /&gt;Prasad</description>
      <pubDate>Fri, 01 Jun 2007 10:40:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011118#M37783</guid>
      <dc:creator>prasad_35</dc:creator>
      <dc:date>2007-06-01T10:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: CPU error for MICROVAX 3100</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011119#M37784</link>
      <description>Prasad,&lt;BR /&gt;&lt;BR /&gt;To say "thanks" the Forum way:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.&lt;BR /&gt;Consider, that every poster took at least the trouble of posting for you!&lt;BR /&gt;&lt;BR /&gt;To easily find your streams with unassigned points, click your own name somewhere.&lt;BR /&gt;This will bring up your profile.&lt;BR /&gt;Near the bottom of that page, under the caption "My Question(s)" you will find "questions or topics with unassigned points " Clicking that will give all, and only, your questions that still have unassigned postings.&lt;BR /&gt;If you have closed some of those streams, you must "Reopen" them to "Submit points". (After which you can "Close" again)&lt;BR /&gt;&lt;BR /&gt;Do not forget to explicitly activate "Submit points", or your effort gets lost again!!&lt;BR /&gt;&lt;BR /&gt;Thanks on behalf of your Forum colleagues.&lt;BR /&gt;&lt;BR /&gt;PS. - Zero points for this.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Fri, 01 Jun 2007 13:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-error-for-microvax-3100/m-p/4011119#M37784</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2007-06-01T13:15:37Z</dc:date>
    </item>
  </channel>
</rss>

