<?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: &amp;quot;Dmesg&amp;quot; reply errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442658#M207552</link>
    <description>It;s likely your encountering a processor problem. Another place to look is in the GSP logs. Here is a similar discussion to yours.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=692543" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=692543&lt;/A&gt;</description>
    <pubDate>Mon, 13 Dec 2004 20:21:15 GMT</pubDate>
    <dc:creator>Michael Tully</dc:creator>
    <dc:date>2004-12-13T20:21:15Z</dc:date>
    <item>
      <title>"Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442657#M207551</link>
      <description>Hello all.&lt;BR /&gt;&lt;BR /&gt;When I use "Dmesg" command,it replies with errors such like "LPMC type : I-Cache Parity Error." &lt;BR /&gt;&lt;BR /&gt;In syslog.log I see two lines about "Cache":&lt;BR /&gt;Dec  5 22:19:19 xgjf1 vmunix: LPMC type : I-Cache Parity Error.&lt;BR /&gt;Dec  5 22:19:19 xgjf1 vmunix: LPMC type : I-Cache Parity Error.&lt;BR /&gt;But no more information is finded.&lt;BR /&gt;&lt;BR /&gt;MODEL--9000/800/L2000-5X&lt;BR /&gt;&lt;BR /&gt;So what can i do now?Thanks to anyone who gives a advisement</description>
      <pubDate>Mon, 13 Dec 2004 20:14:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442657#M207551</guid>
      <dc:creator>RuyiLuo</dc:creator>
      <dc:date>2004-12-13T20:14:28Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442658#M207552</link>
      <description>It;s likely your encountering a processor problem. Another place to look is in the GSP logs. Here is a similar discussion to yours.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=692543" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=692543&lt;/A&gt;</description>
      <pubDate>Mon, 13 Dec 2004 20:21:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442658#M207552</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2004-12-13T20:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442659#M207553</link>
      <description>This is a Low Priority Machine Check&lt;BR /&gt;&lt;BR /&gt;It needs to be dealt with before it becomes a High Priority Machine Check(HPMC)&lt;BR /&gt;&lt;BR /&gt;If that happens its instant crash. In this situation you may come back up with no system due to a system board issue, or short a processor.&lt;BR /&gt;&lt;BR /&gt;This should be dealth with via a hardware call as soon as practical.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 13 Dec 2004 20:32:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442659#M207553</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-12-13T20:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442660#M207554</link>
      <description>Because these two events happened at the same time, for our purposes let's call them the same event. Yours is a Low Priority Machine Check in the Instruction Cache. This is really only of concern if you see it freequently. I'll loosely define frequently as more than about 1 per week. This type of event can literally be the result of comsic or other background radiation although, in general, unless you are in an unusual environment only cosmic radiation is energetic enough to cause this. If you begin to see these events often then it is time to call your HP Mr. Goodwrench and have a processor board replaced.&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Dec 2004 20:50:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442660#M207554</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-12-13T20:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442661#M207555</link>
      <description>I am sorry that i have ignored the information follows:&lt;BR /&gt;&lt;BR /&gt;Dec  5 22:19:19 xgjf1 vmunix: Parity Error.^M&lt;BR /&gt;Dec  5 22:19:19 xgjf1 vmunix: LPMC type : I-Cache Parity Error.^M&lt;BR /&gt;Dec  5 22:10:25 xgjf1 cmcld: Warning: cmcld process was unable to run for the last 3 seconds&lt;BR /&gt;Dec  5 22:19:19 xgjf1 vmunix: LPMC type : I-Cache Parity Error.^M&lt;BR /&gt;Dec  5 22:39:19 xgjf1  above message repeats 80 times&lt;BR /&gt;Dec  5 22:10:30 xgjf1 cmcld: Warning: cmcld process was unable to run for the last 3 seconds&lt;BR /&gt;&lt;BR /&gt;It seems terrible.I have made a hardware call,and the result they give me is a problem of Memory.They promise me replacement of Memory.&lt;BR /&gt;&lt;BR /&gt;But i still want to know how to deal with this situation.</description>
      <pubDate>Tue, 14 Dec 2004 03:21:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442661#M207555</guid>
      <dc:creator>RuyiLuo</dc:creator>
      <dc:date>2004-12-14T03:21:02Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442662#M207556</link>
      <description>Hi guru&lt;BR /&gt;Here is good link:&lt;BR /&gt;&lt;A href="http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000065556468" target="_blank"&gt;http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000065556468&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;(You have to type username/password to login)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;And here is good thread, it may help you:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=105608" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=105608&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;BR /&gt;&lt;BR /&gt;Regard,&lt;BR /&gt;&lt;BR /&gt;Jimkery&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Dec 2004 04:44:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442662#M207556</guid>
      <dc:creator>Hoang Chi Cong_1</dc:creator>
      <dc:date>2004-12-14T04:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442663#M207557</link>
      <description>Oops, click 'submit' a bit prematurely...&lt;BR /&gt;&lt;BR /&gt;You can check in the syslog.log file for the even ID. Then check in this site:&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/en/diag/ems/lpmc_em.htm" target="_blank"&gt;http://www.docs.hp.com/en/diag/ems/lpmc_em.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;regard,&lt;BR /&gt;Jimkery</description>
      <pubDate>Tue, 14 Dec 2004 04:54:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442663#M207557</guid>
      <dc:creator>Hoang Chi Cong_1</dc:creator>
      <dc:date>2004-12-14T04:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: "Dmesg" reply errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442664#M207558</link>
      <description>Confirm that Diagnostics and Patches are updated in your system to latest.&lt;BR /&gt;&lt;BR /&gt;MDT. Memory Deallocation table. and Page deallocation table. Keeps the track of faulty pages in memory. Those pages once locked will not be used again by system.&lt;BR /&gt;&lt;BR /&gt;memlogd is the daemon for this.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Saurav</description>
      <pubDate>Tue, 14 Dec 2004 05:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-dmesg-quot-reply-errors/m-p/3442664#M207558</guid>
      <dc:creator>Saurav_1</dc:creator>
      <dc:date>2004-12-14T05:34:29Z</dc:date>
    </item>
  </channel>
</rss>

