techsupport

2468 readers

6 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

GatoB@lemmy.world

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

submitted 1 year ago by nicocool84@sh.itjust.works to c/techsupport@lemmy.world

21 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

[–] nicocool84@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago) (1 children)

Updating. I'm willing to try your solution but I am a little bit worried about not being able to reinstall anything after I sudo apt remove network-manager. Why would a package reinstallation help? Wouldn't resetting the config files be more efficient btw?

EDIT: Ce n'est pas update sur update, y a juste eu bullseye (d'abord testing, puis stable), puis récemment je suis passé à bookworm. Mais le soucis est là depuis le début. Il est pas trop chiant parce que c'est rare, mais quand même ça m'enquiquine.

[–] Ashiette@lemmy.one 2 points 1 year ago* (last edited 1 year ago)

Thing is, I really haven't used debian based distros for the better part of the last two years so I'm not sure how to reinstall it if something goes south. With arch you just have to do a pacstrap with a liveUSB.

So... it seems kinda dangerous if you don't have a backup .deb. I'm not sure I would advise you to go this way.

I looked at your journalctl. The error might come from your wireless card. If that is the case, and since you don't use it at all there is a simple trick : sudo systemctl disable wpa_supplicant then reboot.

It won't have any incidence on the ethernet but will somewhat disable your wifi card. (Not exactly but you get the gist of it).

If I'm right it should make all of your problems go away. It might be worth a try. And if it doesn't work a simple sudo systemctl enable wpa_supplicant will reverse it back to the way it was.

Ça demeure chiant, même si c'est pas quotidien.