<?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 Error at syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188555#M164249</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am facing the following error from one of our HP-9000 server:&lt;BR /&gt;&lt;BR /&gt;mis vmunix: LPMC type : D-Cache Parity Error&lt;BR /&gt;&lt;BR /&gt;Here MIS is the hostname of our server.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me the probable reason for this.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;&lt;BR /&gt;Utpal</description>
    <pubDate>Wed, 11 Feb 2004 00:16:28 GMT</pubDate>
    <dc:creator>Utpal Krishna</dc:creator>
    <dc:date>2004-02-11T00:16:28Z</dc:date>
    <item>
      <title>Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188555#M164249</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am facing the following error from one of our HP-9000 server:&lt;BR /&gt;&lt;BR /&gt;mis vmunix: LPMC type : D-Cache Parity Error&lt;BR /&gt;&lt;BR /&gt;Here MIS is the hostname of our server.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me the probable reason for this.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;&lt;BR /&gt;Utpal</description>
      <pubDate>Wed, 11 Feb 2004 00:16:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188555#M164249</guid>
      <dc:creator>Utpal Krishna</dc:creator>
      <dc:date>2004-02-11T00:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188556#M164250</link>
      <description>LPMC&lt;BR /&gt;Low priority machine checks&lt;BR /&gt;These messages come from the processor on the server.&lt;BR /&gt;As stated above these messages are low priority.&lt;BR /&gt;&lt;BR /&gt;Make sure these messages do not come frequently,as then you should plan to replace the processor throwing these messages.</description>
      <pubDate>Wed, 11 Feb 2004 00:24:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188556#M164250</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2004-02-11T00:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188557#M164251</link>
      <description>This is the Data Cache parity error in one of the processor. If you have contract with HP, pls talk to them with details.&lt;BR /&gt;&lt;BR /&gt;For getting further details you may send the /var/tombstones/ts99 files to them.&lt;BR /&gt;&lt;BR /&gt;You can also see the file&lt;BR /&gt;#strings /var/tombstones/ts99&lt;BR /&gt;&lt;BR /&gt;these are processor logs</description>
      <pubDate>Wed, 11 Feb 2004 00:26:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188557#M164251</guid>
      <dc:creator>PVR</dc:creator>
      <dc:date>2004-02-11T00:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188558#M164252</link>
      <description>HPMC&lt;BR /&gt;But do check whether there are HPMC errors for the processor/cache.&lt;BR /&gt;&lt;BR /&gt;If then,replace the processor.</description>
      <pubDate>Wed, 11 Feb 2004 00:30:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188558#M164252</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2004-02-11T00:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188559#M164253</link>
      <description>If this system does any kind of work you depend on, get the CPU replaced now.  &lt;BR /&gt;&lt;BR /&gt;You can test it by running xstm in X and excersizing the CPU.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 11 Feb 2004 00:31:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188559#M164253</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-11T00:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188560#M164254</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Thanks everyone for the information.&lt;BR /&gt;But I am adding that after this(after 16 Hours) I cannot ping to my server and also cannot login to server also the attension light is blinking. Can anyone tell me the probable solution for this.&lt;BR /&gt; &lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Utpal</description>
      <pubDate>Wed, 11 Feb 2004 01:10:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188560#M164254</guid>
      <dc:creator>Utpal Krishna</dc:creator>
      <dc:date>2004-02-11T01:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188561#M164255</link>
      <description>I couldn't get you!</description>
      <pubDate>Wed, 11 Feb 2004 01:19:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188561#M164255</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2004-02-11T01:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188562#M164256</link>
      <description>Utpal,&lt;BR /&gt;&lt;BR /&gt;apparently your server crashed.&lt;BR /&gt;Did you try to login at the console?&lt;BR /&gt;If the server is 'dead', try connecting to the GSP by entering '^B' at the console.&lt;BR /&gt;The attention light indicates there are messages in the logfile of the GSP.&lt;BR /&gt;You may view the logfile, and you may reset the hardware (= hard reboot of your server).&lt;BR /&gt;&lt;BR /&gt;JP.&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2004 02:04:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188562#M164256</guid>
      <dc:creator>Jeroen Peereboom</dc:creator>
      <dc:date>2004-02-11T02:04:37Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188563#M164257</link>
      <description>goto GSP .&lt;BR /&gt;&lt;BR /&gt;^b at console. u shall get GSP prompt.&lt;BR /&gt;type "sl"&lt;BR /&gt;then "e". This will give the LPMC / HPMC error details. In the last of each event there will be a number of hex codes. U can communicate the same to HP solution center people. They shall tell you which part is defective. Can u forward me the hex codes&lt;BR /&gt;&lt;BR /&gt;Once you see these messages at GSP prompt, attention light will go to off state&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2004 02:24:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188563#M164257</guid>
      <dc:creator>PVR</dc:creator>
      <dc:date>2004-02-11T02:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Error at syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188564#M164258</link>
      <description>a LPMC is usually a memory related error. Usually one of the following has failed or failed out at the time of the crash:&lt;BR /&gt;&lt;BR /&gt;Memory Card/Carrarier or Memory Port on the system board. If there was a system board related you would have received a LPMC with a HPMC then you would cored and panic'd. All of this would also be present in your Guardian Processor.&lt;BR /&gt;&lt;BR /&gt;I would run a Q4 and place a call to the down server team at HP and get a tech onsite with some memory and board. I have seen these alot.&lt;BR /&gt;&lt;BR /&gt;Not for Nothin a LPMC is usually recoverable, normally it's caused by a rouge C program trying to lock a memory region that is unlockable or unavailable and that cause's a memory fault and some times throws an LPMC.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2004 22:30:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-at-syslog/m-p/3188564#M164258</guid>
      <dc:creator>Albert Smith_1</dc:creator>
      <dc:date>2004-02-11T22:30:09Z</dc:date>
    </item>
  </channel>
</rss>

