<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3" href="https://bugs.freedesktop.org/show_bug.cgi?id=106597#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3" href="https://bugs.freedesktop.org/show_bug.cgi?id=106597">bug 106597</a> from <a class="email" href="mailto:lukas@wunner.de" title="Lukas Wunner <lukas@wunner.de>"> Lukas Wunner</a> <pre>Okay the real culprit seems to be commit 3b5b899ca67d ("ALSA: hda: Make use of core codec functions to sync power state"): <a href="https://git.kernel.org/linus/3b5b899ca67d">https://git.kernel.org/linus/3b5b899ca67d</a> If you revert that, does the issue go away? I can see on my MacBook Pro that the return value is consistently 0x233 without this commit when setting the power state to D3 (which is the correct return value), and 0x1 with the commit. The commit went into 4.17. Given how late we are in this cycle, I think a revert is in order. The commit breaks runtime suspend for any HDA controller. Why the hell wasn't this discovered before, this must have been in linux-next for > 4 months!?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>