Lately my system has been freezing and completely unresponsive. ctrl+alt+backspace, reisub, nothing works and I have to hard reset. I found some logs, syslog, and have posted a few leading up to the freeze. They’re all from ProtonVPN (I’m on beta). I’m hoping there’s something I can do without just not using ProtonVPN, assuming proton is the culprit. Can anyone make sense of this?

I don’t know how much of this info should be private so I redacted some, timezone, pc name, mac, ports.

2025-12-12T11:09:27.835680TIME MYPC protonvpn-app[4792]: 2025-12-12T15:09:27.835612+00:00 | proton.vpn.local_agent/port_forwarding.rs:225 | INFO | Receiving Response { version: 0, operation: 130, response_code: 0, gateway_epoch_seconds: 4116943, internal_port: REDACTED, external_port: REDACTED, lifetime_seconds: 60 }
2025-12-12T11:09:28.257753TIME MYPC protonvpn-app[4792]: 2025-12-12T15:09:28.257690+00:00 | proton.vpn.session.utils:112 | INFO | API:RESPONSE | '/feature/v2/frontend'
2025-12-12T11:09:28.258827TIME MYPC protonvpn-app[4792]: 2025-12-12T15:09:28.258799+00:00 | proton.vpn.core.refresher.feature_flags_refresher:94 | INFO | Next feature flag refresh scheduled in 1:39:23.178147
2025-12-12T11:09:32.026373-04:00 MYPC kernel: [UFW BLOCK] IN=proton0 OUT= MAC= SRC=REDACTED DST=REDACTED LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=30062 PROTO=TCP SPT=REDACTED DPT=REDACTED WINDOW=29200 RES=0x00 SYN URGP=0 
2025-12-12T11:32:17.244594TIME MYPC systemd-modules-load[957]: Inserted module 'lp'
  • data1701d (He/Him)@startrek.websiteEnglish
    0·
    11 days ago

    If you scroll down in journalctl, it can go later in time. Also, you can check different boots by changing the b parameter, with -b 0 being the current boot, -b -1 being the previous boot, b -2 being the boot before that, etcetera.

    For UFW, I’d just try unblocking the Proton ports if it says they’re blocked in Proton settings. Also, check to make sure you don’t have two firewalls installed; while this once again shouldn’t crash the system, my PC did some very weird things when both UFW and firewalld were installed.

    • Jack_Burton@lemmy.caOP
      0·
      11 days ago

      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 page

      Going 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/0x00000000

      Just 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.