EDIT: The solution was that it was freesync. Turned it off on my monitor, and that fixed it.

I recently picked up a used RX 6600xt, and ever since the screen will occasionally freeze for 1-2 seconds before returning to normal. As far as I can tell, input and sound work as normal during these. There’s no real pattern either.

I’m on Mint 21.3 Cinnamon, on the 6.5 kernel (there was a sleep related issue for me in the default kernel version). Since getting the GPU, I’ve replaced the CPU and motherboard.

Any guesses as to what this might be, or where to look? I tried checking mint’s logs app and there didn’t seem to be anything associated with it.

    • Julian@lemm.eeOPEnglish
      5·
      8 months ago

      During the minute that one of these freezes happened, this is the log output:

      Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:39 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:39 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:06 HAL systemd[1880]: Started VTE child process 5674 launched by gnome-terminal-server process 5653.
Mar 30 12:14:06 HAL systemd[1880]: Started GNOME Terminal Server.
Mar 30 12:14:06 HAL dbus-daemon[1892]: [session uid=1000 pid=1892] Successfully activated service 'org.gnome.Terminal'
Mar 30 12:14:06 HAL systemd[1880]: Starting GNOME Terminal Server...
Mar 30 12:14:06 HAL systemd[1880]: Created slice Slice /app/org.gnome.Terminal.
Mar 30 12:14:06 HAL dbus-daemon[1892]: [session uid=1000 pid=1892] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.108' (uid=1000 pid=5650 comm="/usr/bin/gnome-terminal>
Mar 30 12:13:53 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:13:53 HAL rtkit-daemon[1238]: Successfully made thread 5636 of process 1889 owned by '1000' RT at priority 5.
      • Atemu@lemmy.ml
        4·
        8 months ago

        Just a hunch but I’d look into rtkit. A bad process with realtime priority could starve out others.

        Temporarily disable rtkit and log out.

        • Julian@lemm.eeOPEnglish
          4·
          8 months ago

          I vaguely know rtkit handles thread/process priority… could there be any possible issues if I disable it?

          Edit: actually have a more important question: how do I disable rtkit? It seems to just start up regardless of what I do.

          • Atemu@lemmy.ml
            2·
            8 months ago

            The only important instance I know of would be your audio server (pipewire, pulse) which could also explain why audio continues to work.

            how do I disable rtkit? It seems to just start up regardless of what I do.

            Masking the service should do it.

      • F04118F@feddit.nl
        3·
        8 months ago

        My guess would be 3rd line from the bottom: a systemd service named gnome-terminal-server is being started. Why is it being started? Maybe it crashed and is set to always restart? Not sure.

        • Julian@lemm.eeOPEnglish
          4·
          8 months ago

          I think that was me opening the terminal to run journalctl lol