* James Knott <james.knott@jknott.net> [09-23-19 19:00]:
On 2019-09-23 05:17 PM, Carlos E. R. wrote:
Which is precisely why I told you to leave that terminal running with that command in advance, and examine the resulting file after crash and reboot. Better with REISUB.
Even better if you do it via ssh from another computer - way before the crash.
Most of the time when it locks up, I can't even switch to open apps. This morning I was able to, as I could see it coming. As I mentioned in another note, a can't ssh in when it happens. Most of the time, my only option is to power down and up. Even repeatedly hitting Ctl-Alt-Backspace usually doesn't work. That makes it difficult to do anything other than hit the power button. If I'm at the computer when it starts, I may be able to do something. If I'm away and then come back, the computer is completely locked up.
as was suggested to you which you seem to be ignoring: open a terminal ssh into the subject machine fron another start top as suggested looking as swap leave the terminal open and the ssh connection when the machine locks up you will be able to see the error in the ssh connection. you might even direct the output from top to a remote machine for monitoring. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org