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?

  • 🧟‍♂️ Cadaver
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Uninstall (I don’t know how, on debian) NetworkManager and reinstall it (better get a .deb)

    Then sudo systemctl enable NetworkManager.service

    Reboot and hope for the best.

    • nicocool84@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      This has been happening for 2 years, with the previous debian version too, so I doubt this would do anything?

      • 🧟‍♂️ Cadaver
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Have you been updating or reinstalling ?

        Parce que si c’est update sur update ça pourrait venir de là. Dans ce cas réinstalle peut etre ?

        • nicocool84@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          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.

          • 🧟‍♂️ Cadaver
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            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.

      • CameronDev@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        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.worksOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          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…