techsupport

2469 readers

15 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

24 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

[–] CameronDev@programming.dev 1 points 1 year ago (1 children)

If its been happening for multiple years and os's, maybe your network card is dead/dying? Buy a new network card and see if that helps?

[–] nicocool84@sh.itjust.works 2 points 1 year ago

Everything is 2 yo, so this would mean the mobo (well, the onboard ethernet thing) was malfunctioning from the start. Maybe!

I might try disabling and using the onboard wifi chip temporarily instead, just to see if I notice a new freeze. The issue is, I've never understood what triggers it, and it's quite rare (less than once a week), so it's really annoying to debug…