<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>If you are running a standard PANDA distribution, then DDT is in
the monitor and you may fail to it. Did it come up? Did you do
an examine from the KLH10 micro-engine to see what instruction it
was failing on? Did you see what module it is failing in?</p>
<p>My monitor is modified from the base PANDA distribution to
include several local enhancements, so when I looked at that
address, it showed up as in the entry of CHKOPC, which is what is
checking for differed closes on virtual circuits. This is in
PHYKLP which is the KLIPA driver (a.k.a. the CI). Since KLH10
(sadly) does not implement the CI, there is no way you should be
executing in that module as there nothing for it to talk to.</p>
<p>Moreover, there is no JRST 4 there. So probably you have
something else at that address.<br>
</p>
<p>I have been running KLH10 for a <i>very</i> long time; since
late December 2002 and have made modifications there, too to fix
an issue with locking memory and to better support Linux (recent
Ubuntu). It is remarkably robust; despite intensive development,
I have stayed up well over a year at a time (I.E., hit UP2LNG
BUGHLT's)<br>
</p>
<div class="moz-cite-prefix">I have found one problem; if you are
running it on an <u>extremely</u> fast machine with SSD storage
(in other words, you're basically never waiting for anything) and
you seriously beat on the file system, then the keep-alive counter
can get out of sync with the 20 thinking the front end has died
and the KLH10 DTE simulator apparently not understanding what to
do.</div>
<div class="moz-cite-prefix">
<p>The 20 typed an initial BUGCHK and then in the middle of the
second one, it hangs waiting for the front end.</p>
<p>It's on my list of things to investigate.<br>
</p>
</div>
<blockquote type="cite"
cite="mid:3f6d7313-d8cb-11d1-cd1c-ac04924d9893@riseup.net">
<hr width="100%" size="2">On 8/31/20 4:15 PM, Supratim Sanyal
wrote:<br>
<br>
hi all - my panda distribution instance is halting after a couple
of days with the following message. is this a known problem for
which there is some workaround?
<br>
<br>
Monitor RF434E DEC10 Development
<br>
System uptime 52:10:47
<br>
Current date/time Wednesday 29-Jul-120 6:01:04
<br>
<br>
[HALTED: Program Halt, PC = 22013]
<br>
<br>
thanks
<br>
<br>
Supratim
<br>
<br>
</blockquote>
</body>
</html>