- Processor: Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
- Memory: 32770MB (4395MB used)
- Motherboard: PRIME Z490-A
- Graphics Card: RTX 2060
- Operating System: Pop!_OS 22.04 LTS
The last two days, when I return to my workstation from the night before (I leave my system powered up) my system appears to have been restarted.
My previously open applications are all closed as if the system was restarted. But I know that it didn’t restart because the logs say so.
DMESG shows some interesting things, but no shutdown or start up messages except for when I manually restart the computer after arriving and finding my applications closed out and applications not functioning or acting erratically.
I’m not sure what this is but it seems like an issue with memory. I did a full hardware test on my system and found no trouble. I was wondering if someone could help me diagnose this. Here is my DMESG log on Pastebin.
Please note when I return to my workstation in the morning, at around 7:00-8:00am, the logs show my manual restart. I have to do this because of the erratic behavior.
Here are the last dozen or so lines of the DMESG log:
Mar 03 00:00:01.012586 pop-os kernel: audit: type=1400 audit(1677830401.008:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=1365188 comm="cupsd" capability=12 capname="net_admin" Mar 03 07:57:21.044559 pop-os kernel: rfkill: input handler enabled Mar 03 07:57:22.280555 pop-os kernel: hub 1-6:1.0: USB hub found Mar 03 07:57:22.280701 pop-os kernel: hub 1-6:1.0: 4 ports detected Mar 03 07:57:23.648558 pop-os kernel: ntfs3: Unknown parameter 'windows_names' Mar 03 07:57:23.852585 pop-os kernel: rfkill: input handler disabled Mar 03 08:04:21.444861 pop-os kernel: rfkill: input handler enabled Mar 03 08:04:24.060560 pop-os kernel: rfkill: input handler disabled Mar 03 08:04:51.664560 pop-os kernel: rfkill: input handler enabled Mar 03 08:04:51.692659 pop-os kernel: EXT4-fs (sdc4): unmounting filesystem. Mar 03 08:04:51.720558 pop-os kernel: EXT4-fs (sde1): unmounting filesystem. Mar 03 08:04:53.208616 pop-os systemd-shutdown: Syncing filesystems and block devices. Mar 03 08:04:53.228718 pop-os systemd-shutdown: Sending SIGTERM to remaining processes...
rebootcommand): - Find last boot time with:
who -b, or
tuptime -t) to see how long it has been up - Check
/var/log/messagesaround this time - Search for restart in cron scripts:
grep -re "sudo reboot" /etc/cron.d/- If desperate, search everywhere :
grep -re "sudo reboot" /etc/ /var/If you can't find any software that could be the cause, you should perhaps look for hardware causes (perhaps power).
@harrymcfor me to be notified.)
journalctlinvocation. Of course, the resulting log will be much too long, so you’ll have to look through it yourself first, then provide spots of (potential) interest. I also recommend narrowing down the log using time filters instead of the “boot ID” filter. You know the night it happened, you should make use of that information.