Hi, I bought a new computer recently and i chose to install fedora on it. After a couple of days I got a random freeze. After restarting the computer everything works fine again. After one more week, or something similar, I get another freeze. After running ‘journalctl -b -1 -r’ i get this as the top output:
May 16 20:28:19 fedora kernel: kernel BUG at lib/list_debug.c:59!
May 16 20:28:19 fedora kernel: ------------[ cut here ]------------
May 16 20:28:19 fedora kernel: list_del corruption. prev->next should be ffffe4a4891845c8, but was ffffe4a4899845c8. (prev=ffffe4a48ed0fd08)
May 16 20:28:19 fedora systemd[1935]: Started dbus-:1.2-org.gnome.ScreenSaver@1874.service.
May 16 20:28:18 fedora systemd[1935]: Started dbus-:1.2-org.gnome.ScreenSaver@1873.service.
May 16 20:28:17 fedora systemd[1935]: Started dbus-:1.2-org.gnome.ScreenSaver@1872.service.
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: libva info: va_openDriver() returns 0
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: ATTENTION: default value of option mesa_glthread overridden by environment.
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: libva info: Found init function __vaDriverInit_1_18
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: libva info: VA-API version 1.18.0
May 16 20:28:16 fedora /usr/libexec/gdm-x-session[8246]: libva info: va_openDriver() returns 0
The ‘ATTENTION: default value of option mesa_glthread overridden by environment.’ gets repeated a lot but reading a thread it does not look like it should be the issue.
I know that this is not a lot to go on but as it a new computer I would like to know what is the problem. Can I turn on some debugging in the kernel or what would be the best way of gathering more information about the freeze?
Are you using mesa-freeworld? I ask because I was seeing system freezes before removing the freeworld package too. It could be entirely coincidental, and it was some update or another that actually fixed the issue, I don’t really know. But if you’re using the freeworld package, it could be worth a shot swapping it out with the non-freeworld package and see if that changes anything.
Another thing that comes to mind is this bug. I can’t tell from the journal output you posted whether there could be something about ring timeouts elsewhere in the journal, but I thought I’d mention the possibility anyway.
Thanks for responding.
I have not done any configuration or installation to my knowledge of mesa-freeworld, I am not familiar with that software and a bit unsure how i should check if I am using it.
The other bug thread looks interesting and I agree It looks to be a similar experience to mine. Looking through the logs however I can’t see any direct similarities. But looking through my logs i have some prints from the amdgpu but non of them are errors or warnings.
I did find this in my log about “ring sdma0” but dose not look like anything is wrong:
fedora kernel: PM: suspend exit
fedora kernel: random: crng reseeded on system resumption
fedora kernel: Restarting tasks … done.
fedora kernel: OOM killer enabled.
fedora kernel: PM: resume devices took 2.112 seconds
fedora kernel: usb 1-6: reset full-speed USB device number 3 using xhci_hcd
fedora kernel: usb 1-11: reset full-speed USB device number 5 using xhci_hcd
fedora kernel: usb 1-7: reset low-speed USB device number 4 using xhci_hcd
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
fedora kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0