search

Frogging-Family / linux-tkg

linux-tkg custom kernels
GNU General Public License v2.0
1.35k stars 170 forks source link

[feature] Add amdgpu Navi 2X freeze patches for kernels 6.7+ #896

Closed xlacroixx closed 8 months ago

xlacroixx commented 8 months ago

Hello,

This is a feature request to add patches to the default list for kernels 6.7+.

These patches fix random freezes/panics on RX 6000 series GPUs and kernels 6.7.X. They are mostly reverts.

Patch 3

Updated for 6.7.6. Tested working on 6.7.8 and 6.7.6.

DDL to patch

Patch 2

Updated for 6.7.5. Untested.

DDL to patch

Patch 1

Original for 6.7.4. Untested.

DDL to patch

The whole thread where these patches can be found is here. Another thread referenced here.

Currently using patch 3 on locally compiled linux-tkg 6.7.8 with BORE-EEVDF. No freezes nor panics related to amdgpu thus far. Using an RX 6750 XT.

I have no idea why this still isn't pushed to the kernel mainline yet.

xlacroixx commented 8 months ago

Patches have been added. Thanks. I might try to directly do a PR next time; it would save time.

Probably unrelated but when I compiled 6.8.1-tkg with default patch selection and default EEVDF, neither my USB keyboard nor mouse would work in either TTY or Hyprland.

journalctl shows no relevant logs except some "kernel: too many entries; ignoring [mem ADDRESS-ADDRESS]" spam in some boots.

It's maybe an issue in the kernel or with my setup.

Issue should be probably closed now regardless.

Tk-Glitch commented 8 months ago

If you are using modprobed-db, you might want to rebuild a full kernel. Arch's 6.8 defconfig has moved quite a few builtins to modules so the db will need to be populated with the new entries. If you're not using modprobed-db however, that would be a valid upstream issue. Closing this one as resolved.

xlacroixx commented 8 months ago

If you are using modprobed-db, you might want to rebuild a full kernel. Arch's 6.8 defconfig has moved quite a few builtins to modules so the db will need to be populated with the new entries. If you're not using modprobed-db however, that would be a valid upstream issue. Closing this one as resolved.

Yes, I do use modprobed-db and this is what I suspected at first when there was no input coming through. Though when I checked the logs, I saw nothing mentionning a missing module, so I thought "whatever it'll get fixed" and just reverted to a previous TkG build.

I will wait for 6.8 to come into the Arch repos, run a modprobed-db store once there and rebuild. The new kernel shouldn't take long to arrive. Thanks a lot for the reply!