On Thu, Feb 01, 2024 at 08:10:11AM +0100, Dieter Mummenschanz wrote: > > It should be needed until we add (or modify the existing entry, if any) > > your PCI vendor and device id to use "board_ahci_low_power" instead of > > "board_ahci", see e.g. > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/ahci.c?> id=b8b8b4e0c052b2c06e1c4820a8001f4e0f77900f > > Not sure I understand. So this CAN be fined inside the Kernel? Yes, this part of the problem can be avoided by adding an explicit entry that uses "board_ahci_low_power", as I explained in: https://lore.kernel.org/linux-ide/ZaATdGDOo5jiBqCR@x1-carbon/T/#u We seem to have a problem with Tiger Lake, but that problem seems to be related to Intel VMD. >From looking at your logs, you don't seem to have Intel VMD, however I'm guessing that some other motherboards that uses Cannon Lake might have Intel VMD, so I guess the safest thing is to wait until that issue has been resolved before adding a "board_ahci_low_power" entry for Cannon Lake. However, we are still confused why the revert in this series did not enable your system to enter deeper power states, as you have previously confirmed that reverting this change: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/ata/libata-core.c?id=d035e4eb38b3ea5ae9ead342f888fd3c394b0fe0 allowed you to enter deeper power states once again. I see now that Damien's revert (patch 2/2 in this series) is not a simple $ git revert fd3a6837d8e18cb7be80dcca1283276290336a7a it seems to have some other small changes in the same patch as well. Sorry for asking you to test something once more... But could you please test with: v6.6-rc2 + git revert fd3a6837d8e18cb7be80dcca1283276290336a7a Kind regards, Niklas
