-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pdp10-ka ITS gets catatonic after a while #323
Comments
Sometimes I can get LOCK to schedule the system to go down, but it doesn't:
|
Is this on a VPS or some kind of virtual machine? Twice I have problems running on a VPS. First it broke klh10 (another failure mode though). Now since a few months back, I can no longer run pdp10-ka despite not having changed anything on my end. I also get those "ITS REVIVED" messages after, say, roughly 10 or 24 hours or so. I have no problem running on my own physical machines, PC type or Raspberry Pi. |
This is on my M1 Mac. No VPS. |
It MAY have something to do with the Mac going to sleep and then waking up from sleep. |
If I let my KA ITS (running under pdp10-ka) run overnight, or sometimes a little more than overnight, I find that there are hundreds of "EXA ITS revived! messages in my DDT session, and hundreds of "EXA ITS 1652 REVIVED. hh:mm:ss" messages on the system console. Neither session responds to ^Z, or if they do, it is many 10s of seconds later. Then after an initial response, everything hangs for a while, until the next "revived" message. The system is completely unusable at this point, and I have to crash it. I cannot, even if on the console at a DDT prompt, run LOCK successfully. Sometimes I can get it started, but the system hangs and then revives, but never long enough for a shutdown to occur.
Also, typing the simulator escape sequence (^) doesn't respond for quite some time when the simulator is in this state. It may eventually respond with the prompt, and typing the "cont" command goes back to the wedged state. Sometimes, I can force a return to DSKDMP, but most time, I can never get things back working. I have to simply quit the simulator (if I can get to the prompt) or kill the process (if I can't).
The text was updated successfully, but these errors were encountered: