Your message dated Thu, 20 Feb 2025 15:17:36 +0100 (CET)
with message-id <20250220141736.14bbfbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1032262,
regarding Kernel builds past 5.3 seem to interfere with AMD dedicated GPU
performance on Acer Nitro 5 AN515-42 laptop (almost certainly kernel config
related)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1032262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: Any that include kernel versions post-5.3
Hello, I current run Debian 12 (Bookworm) on my Acer Nitro 5 AN515-42
laptop, but this issue has been present in Debian for quite a while.
I've noticed that the default kernel has some problems regarding the
hybrid Raven Ridge/RX560x setup in this machine.
No matter what 3D load is run, the performance of the GPU hardware
seems to be locked at its lowest state, resulting in extremely poor
performance. This happens regardless of DRI_PRIME setting.
Interestingly, this did NOT happen when I tested other distributions
on this hardware, such as Fedora and Ubuntu, regardless of kernel
version present.
The problem also disappears if I use the Xanmod kernel, which is a
third-party custom kernel not present in Debian's repositories.
Finally, out of curiosity, I compiled the mainline kernel for myself
the other day (version 6.1) using the kernel config present by default
in the third-party Xanmod kernel, and my compiled kernel resulted in
proper and expected performance across the board.
For these reasons, I believe the kernel config present in Debian is
somehow at fault. Unfortunately, despite looking at the diff between
the default kernel config and the custom one I used to build my
kernel, I don't really have a good idea of which settings were
responsible for the solution to this issue.
I would greatly appreciate it if anyone more knowledgeable than me
could help to investigate this and perhaps change the default Debian
kernel config upstream so that other users who might be affected by
this bug can benefit from the solution without having to compile their
own kernels.
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
