

For the log? I just opened syslog in /var/log. Running journalctl -b -1 -p 3 only goes back to around 14:10, right after booting from the last freeze. dmesg just spits out a ton of the same UFW BLOCK entries, usb connections and such, and only one error that says usb 1-2.4.1.1.3: clock source 41 is not valid, cannot use (I have no idea if this is new or just always was). The first freeze happened yesterday morning, frozen sometime overnight when I wasn’t even using the PC, but I didn’t know about logs or anything so had no idea what to check.
The ports are whichever port is currently active in ProtonVPN’s port forwarding.
I saw another Lemmy post earlier about task managers and installed glances earlier this morning. Unfortunately it wasn’t running at the first freeze but was at the second, and didn’t look like anything was amiss to me. I have had issues in the past though with running too many things at once, like a browser with open tabs, music player, and video editor at the same time eating RAM like crazy. I’ve since created a swap file and I can’t remember the other thing, but it’s meant to shut down the most memory hungry app before things get sluggish.
This type of freezing up is new though, nothing works, and I’ve left it for hours with no change. Previous freezes from eating RAM resulted in a slow moving cursor and resolved in about 20 mins. I also made a lot of adjustments for audio recording months ago that I’d really rather not reinstall the OS and lose, mostly since I’m new to Linux and don’t remember how I got it working haha.
CPU temp seems to stay pretty constant around 45-48 degrees.



OK! So I must have rebooted more than I remembered. Going back to -4 gave me the errors from the first freeze today:
Dec 12 11:09:36 MYPCNAME kernel: BUG: unable to handle page fault for address: ffffaa5cf71f6380 Dec 12 11:09:36 MYPCNAME kernel: #PF: supervisor read access in kernel mode Dec 12 11:09:36 MYPCNAME kernel: #PF: error_code(0x0000) - not-present pageGoing back to -2 I got the errors prior to the second freeze:
Dec 12 14:09:12 MYPCNAME kernel: BUG: unable to handle page fault for address: 000066fd90033180 Dec 12 14:09:12 MYPCNAME kernel: #PF: supervisor read access in kernel mode Dec 12 14:09:12 MYPCNAME kernel: #PF: error_code(0x0000) - not-present page Dec 12 14:09:12 MYPCNAME kernel: Fixing recursive fault but reboot is needed! Dec 12 14:09:12 MYPCNAME kernel: BUG: scheduling while atomic: plasma-browser-/162281/0x00000000Just want to say how much I appreciate you taking the time, I’m learning a lot with this, thank you.
Edit: Looks like it may be related to memory issues OOM? I did install something regarding oom awhile back but I don’t remember what it was. I’m seeing nohang recommended tho
Edit 2: I check my running services, the other one was earlyoom. I’ve removed earlyoom and installed nohang. Hope I’m on the right track.