On Wed, Nov 22, 2017 at 10:23:25PM +0900, Tetsuo Handa wrote: > When you hit that problem next time, please capture SysRq-t and SysRq-m output > after logging in remotely. > > # dmesg -c > dmesg.txt > # echo t > /proc/sysrq-trigger > # echo m > /proc/sysrq-trigger > # dmesg -c >> dmesg.txt > # sleep 60 > # echo t > /proc/sysrq-trigger > # echo m > /proc/sysrq-trigger > # dmesg -c >> dmesg.txt
Thanks. I figured there had to be a way to get a bit more insight into what was happening. System has been up for 12 hours without incident as I type this: Xorg has been started and exited multiple times with no issue. Still going to keep an eye on it for a while. --Bob
