<?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: System crash --- &amp;quot;a_lock timeout&amp;quot; in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290634#M10065</link>
    <description>Never forget to give Operating System, level of Patch Kit, standalone or cluster...&lt;BR /&gt;&lt;BR /&gt;Agnes</description>
    <pubDate>Mon, 31 May 2004 01:48:51 GMT</pubDate>
    <dc:creator>Agnes Coat</dc:creator>
    <dc:date>2004-05-31T01:48:51Z</dc:date>
    <item>
      <title>System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290633#M10064</link>
      <description>Friends,&lt;BR /&gt;&lt;BR /&gt;I have 3 crash detals (attached here), all occured within amonth, have same "a_lock timeout" panic string and same stack trace  details!!!. &lt;BR /&gt;&lt;BR /&gt;4 panic&lt;BR /&gt;5 _a_lock_wait&lt;BR /&gt;6 u_anon_free&lt;BR /&gt;7 u_anon_unmap&lt;BR /&gt;8 u_map_delete&lt;BR /&gt;9 u_map_exec&lt;BR /&gt;10 vm_exec&lt;BR /&gt;11 exec_ungetxfile&lt;BR /&gt;12 common_exec&lt;BR /&gt;13 execve&lt;BR /&gt;14 syscall&lt;BR /&gt;&lt;BR /&gt;u_anon_free rtn has trhe current thread id. and all current PID points to oracel process.&lt;BR /&gt;&lt;BR /&gt;i see all your discussion in this forum, hope you can guide me to locate the cause of errors in this.&lt;BR /&gt;&lt;BR /&gt;good day&lt;BR /&gt;Sugu.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 29 May 2004 16:34:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290633#M10064</guid>
      <dc:creator>Sugumari</dc:creator>
      <dc:date>2004-05-29T16:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290634#M10065</link>
      <description>Never forget to give Operating System, level of Patch Kit, standalone or cluster...&lt;BR /&gt;&lt;BR /&gt;Agnes</description>
      <pubDate>Mon, 31 May 2004 01:48:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290634#M10065</guid>
      <dc:creator>Agnes Coat</dc:creator>
      <dc:date>2004-05-31T01:48:51Z</dc:date>
    </item>
    <item>
      <title>Re: System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290635#M10066</link>
      <description>Sugu,&lt;BR /&gt;&lt;BR /&gt;If you have a service contract, contact HP Services. &lt;BR /&gt;Make sure you installed all Early Release Patches.&lt;BR /&gt;&lt;BR /&gt;Joris&lt;BR /&gt;</description>
      <pubDate>Mon, 31 May 2004 10:16:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290635#M10066</guid>
      <dc:creator>Joris Denayer</dc:creator>
      <dc:date>2004-05-31T10:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290636#M10067</link>
      <description>first check if all patches are properly installed, be sure you understand the difference between "patch installed" and "patchkit installed", so checking the installation log of dupatch for each patch!&lt;BR /&gt;&lt;BR /&gt;If all patches are properly installed be sure you installed latest patchkit&lt;BR /&gt;&lt;BR /&gt;Next step is to open a call within the HP support center and provide crashdata and vmzcore and sys_check -escalate for analyse.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jun 2004 02:23:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290636#M10067</guid>
      <dc:creator>Ralf Puchner</dc:creator>
      <dc:date>2004-06-01T02:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290637#M10068</link>
      <description>Agens, Joris, Ralf&lt;BR /&gt;&lt;BR /&gt;All the latest patches and Patch kit 3 have been installed, and checked even few of the specific patches which points to similar kind of issues related with anon_rss_enforce set to hard limit; beeninstalled succesfully.&lt;BR /&gt;Env is Alpha server cluster 8 cpus, with Tru64 5.1B ver 2650.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sugu</description>
      <pubDate>Tue, 01 Jun 2004 15:21:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290637#M10068</guid>
      <dc:creator>Sugumari</dc:creator>
      <dc:date>2004-06-01T15:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: System crash --- "a_lock timeout"</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290638#M10069</link>
      <description>so next step is to open a call within the HP support center, this is not a call for a forum because it need deeper crash analysis...</description>
      <pubDate>Tue, 01 Jun 2004 15:22:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/system-crash-quot-a-lock-timeout-quot/m-p/3290638#M10069</guid>
      <dc:creator>Ralf Puchner</dc:creator>
      <dc:date>2004-06-01T15:22:50Z</dc:date>
    </item>
  </channel>
</rss>

