-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LACT sometimes completely disables power limit (6900XT) #207
Comments
As you've noted, this is the behaviour of the driver, which LACT has no direct control of. Could you test if doing this manually avoids the problem on your system? Set the performance level to lowest together with the new power limit, apply, and then change it back to automatic. If it does help, then I'll implement it to be done automatically when setting the limit. |
Switching to lowest clocks doesn't seem to apply until the card exits the highest power state either. Weird... Maybe there's some way to "suspend" work on the GPU for a fraction of a second when clicking apply, that would cause it to switch power states. Also, this might be an issue worth reporting to whoever develops the kernel part of the AMD driver, regardless of overclocking settings, the card should never disable its power limit. |
I don't think there's a good way to "suspend" the GPU. Kernel issues are generally reported here: https://gitlab.freedesktop.org/drm/amd |
Reported it: https://gitlab.freedesktop.org/drm/amd/-/issues/2992 |
@adolfintel if this is still relevant: could you try building the |
@ilya-zlobintsev that works! Good job :) |
If the power limit is set to a value that's too low for the power state that the card is currently in, it seems that the driver completely disables the power limit, causing the card to have a spike in power consumption (I've seen it go as high as 420w up from a 293w TDP) until the card leaves that state and then it is applied correctly.
This can be easily replicated by setting the power limit while running any GPU intensive application that will keep the card at its highest power state (demonstrated in the video using stable diffusion) and can potentially lead to damage if running something like furmark which is not memory-bound.
OS: Arch Linux, Kernel 6.6.1, GPU: 6900XT
Here's a video of the problem:
plbug.webm
The text was updated successfully, but these errors were encountered: