You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm making this bug report because I've noticed this some times already, but I've noticed that sometimes intel_lpmd is started but doesn't do anything, just reports that it sets wlt_idle and there's a lot of "received uevent" lines, but it never changes state. I just work around this by restarting it and then it works as normal
I've been having similar issues with the current lpmd. There are some errors in the logs about being unable to write to a cgroup, it looks like if the device doesn't shut down cleanly these are left and prevent lpmd from functioning correctly. A restart resolves the issue by cleaning the old cgroup and creating a new one, this should be probably be handled automatically though. I can see there's been some work done on this already in an older release, does this need checking?
At first I thought I misunderstood the PerformanceDef/BalancedDef/PowersaverDef options. But no matter what value I put, I always end up with OFF/DEFAULT_OFF state.
@octomike do you have WLT Proxy setting enabled in your config file?
I noticed it was a little broken when working on issue #106 that's also related to F6 M170. I put the solutions I found in a comment there.
No, I have <WLTProxyEnable>0</WLTProxyEnable> and still - unless I run intel_lpmd_control AUTO (currently as ExecStartPost in systemd) the daemon doesn't do anything.
Because if they're all '-1' or '1' then it will either start of in force disabled or force enabled (so always in low power mode)
If you want them to start in auto it needs to be '0'. I guess we should change the default to auto since it doesn't make sense to have the default be disabled.
Activity
Toxblh commentedon Jul 4, 2025
Hi @stereomato, looks like that is never works for me. Could you pls show how looks like log, when it works fine.
spandruvada commentedon Sep 19, 2025
It is possible that from configuration, this is not enabled by default.
But, you can do
intel_lpmd_control AUTO
jamlam commentedon Nov 6, 2025
I've been having similar issues with the current lpmd. There are some errors in the logs about being unable to write to a cgroup, it looks like if the device doesn't shut down cleanly these are left and prevent lpmd from functioning correctly. A restart resolves the issue by cleaning the old cgroup and creating a new one, this should be probably be handled automatically though. I can see there's been some work done on this already in an older release, does this need checking?
spandruvada commentedon Nov 17, 2025
Can you try the latest version and see if you see issue.
octomike commentedon Dec 11, 2025
I'm on
mainand see a similar behaviour - namely: nothing, unless I runintel_lpmd_control AUTOBefore, I see debug logs like this:
(using WLT hints only on M6 F170)
after setting to
AUTOI get all the migration/enter/exit logsAt first I thought I misunderstood the
PerformanceDef/BalancedDef/PowersaverDefoptions. But no matter what value I put, I always end up with OFF/DEFAULT_OFF state.octomike commentedon Dec 11, 2025
For what it's worth, it also breaks the moment i switch from
AUTOtoONand back toAUTO.Debug output stays at:
and I don't see any WLT events / changes anymore. So I'm stuck on the efficiency cores. Going back to
OFFand thenAUTOmakes it work again.maciejwieczorretman commentedon Feb 13, 2026
@octomike do you have WLT Proxy setting enabled in your config file?
I noticed it was a little broken when working on issue #106 that's also related to F6 M170. I put the solutions I found in a comment there.
retblast commentedon Feb 24, 2026
@maciejwieczorretman I will be testing that fork you have.
retblast commentedon Feb 24, 2026
Seems like it does work!
octomike commentedon Feb 24, 2026
No, I have
<WLTProxyEnable>0</WLTProxyEnable>and still - unless I runintel_lpmd_control AUTO(currently asExecStartPostin systemd) the daemon doesn't do anything.maciejwieczorretman commentedon Feb 24, 2026
@retblast that's great! Thanks for confirming :)
maciejwieczorretman commentedon Feb 24, 2026
@octomike okay, and what values does your config file have in these fields:
Because if they're all '-1' or '1' then it will either start of in force disabled or force enabled (so always in low power mode)
If you want them to start in auto it needs to be '0'. I guess we should change the default to auto since it doesn't make sense to have the default be disabled.