Desktop computer freeze which blocks all the local network‽ (sh.itjust.works)

submitted 1 year ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

I have assembled my desktop PC about 2 years ago. It's fairly beefy (AMD Ryzen 9 3950X 16-Core Processor, 128Go RAM, nVidia RTX 3080 Ti). It's running debian stable.

Once in a while (not that often, but like every 2 weeks or so), seemingly at random times, not especially under heavy loads, the system crash and freeze, irresponsive to even the linux sysrq magic keys. I never manage to find what was the cause. One interesting fact is that when it happens, for some reason it seems to "freeze my network" too, ie, other (ethernet) devices on my local network have no connectivity anymore. They're all connected to the same router, but not through this crashing PC. Connectivity comes back as soon as I force shutdown the crashing PC.

What can cause this and how could I fix these freezes?

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Check your system logs such as dmesg and journalctl immediately after the freeze (if it's still occurring). You could filter journalctl log to show, say the last 5 minutes since the last boot, like this:

journalctl --boot=-1 --since="5 min ago" --priority=0..3

[-] [email protected] 3 points 1 year ago* (last edited 1 year ago)

It happened yesterday, and here are the latest log lines before the freeze:

Sep 14 23:30:30 licorne NetworkManager[1291]:   [1694727030.1207] device (wlp4s0): set-hw-addr: set MAC address to CA:D0:86:5F:F9:85 (scanning)
Sep 14 23:30:30 licorne NetworkManager[1291]:   [1694727030.1478] device (wlp4s0): supplicant interface state: inactive -> disconnected
Sep 14 23:30:30 licorne NetworkManager[1291]:   [1694727030.1478] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> disconnected
Sep 14 23:30:30 licorne NetworkManager[1291]:   [1694727030.1530] device (wlp4s0): supplicant interface state: disconnected -> inactive
Sep 14 23:30:30 licorne NetworkManager[1291]:   [1694727030.1530] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> inactive
Sep 14 23:30:58 licorne syncthing[3169286]: [VY2L4] INFO: Established secure connection to REDACTED1 at [::]:22000-192.168.0.14:22000/quic-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P20
Sep 14 23:30:58 licorne syncthing[3169286]: [VY2L4] INFO: Device REDACTED1 client is "syncthing v1.23.4" named "REDACTED2.lan" at [::]:22000-192.168.0.14:22000/quic-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P20
Sep 14 23:31:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:31:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:31:11 licorne syncthing[3169286]: [VY2L4] INFO: Established secure connection to REDACTED1 at 192.168.0.98:22000-192.168.0.14:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10
Sep 14 23:31:11 licorne syncthing[3169286]: [VY2L4] INFO: Replacing old connection [::]:22000-192.168.0.14:22000/quic-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P20 with 192.168.0.98:22000-192.168.0.14:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10 for REDACTED1
Sep 14 23:31:11 licorne syncthing[3169286]: [VY2L4] INFO: Connection to REDACTED1 at [::]:22000-192.168.0.14:22000/quic-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P20 closed: replacing connection
Sep 14 23:31:11 licorne syncthing[3169286]: [VY2L4] INFO: Device REDACTED1 client is "syncthing v1.23.4" named "REDACTED2.lan" at 192.168.0.98:22000-192.168.0.14:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10
Sep 14 23:32:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:32:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:33:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:33:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:33:28 licorne systemd[1]: Started anacron.service - Run anacron jobs.
Sep 14 23:33:28 licorne anacron[4171587]: Anacron 2.3 started on 2023-09-14
Sep 14 23:33:28 licorne anacron[4171587]: Normal exit (0 jobs run)
Sep 14 23:33:28 licorne systemd[1]: anacron.service: Deactivated successfully.
Sep 14 23:34:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:34:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:35:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:35:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:36:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:36:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:37:04 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:37:04 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:37:25 licorne NetworkManager[1291]:   [1694727445.1045] device (wlp4s0): set-hw-addr: set MAC address to EE:65:E2:6E:73:D1 (scanning)
Sep 14 23:38:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.
Sep 14 23:38:03 licorne rtkit-daemon[1541]: Supervising 4 threads of 4 processes of 1 users.

this post was submitted on 15 Sep 2023

16 points (100.0% liked)

techsupport

2414 readers

85 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 1 year ago

MODERATORS

[email protected]