Hello Niklas, > It should be ready for testing: > https://github.com/floatious/linux/tree/external-port-v2[https://github.com/floatious/linux/tree/external-port-v2] > With this, you should no longer need: > for foo in /sys/class/scsi_host/host*/link_power_management_policy; > do echo med_power_with_dipm > $foo; > done > (Assuming you have compiled your kernel with CONFIG_SATA_MOBILE_LPM_POLICY=3). Oh sweet! Will give it a spin over the weekend if I find the time. > You shouldn't need to do: > $ hdparm -Y > As that bypasses some of the internal logic in libata. > I assume that you didn't need this on v6.6 and older? > (Instead libata should put the device to standby or sleep itself, > it shouldn't need to be done explicitly by the user.) I'm at a loss either. No idea why this is actually working. When I encountered the low-power issue I searched the web and stumbled upon hdparm -Y and gave it a shot. > How certain are you that v6.6 works? Let's put it this way: I've installed most 6.6-rc's so I had it running for several weeks and I always have an eye on conky showing me the c-states in 5 second interval. And during all that time and several suspends it never occured. It definately started with the first 6.7 -rc I've installed (don't recall wich one first). There were no hardware changes and no BIOS updates during that time. If I find some spare time, I'm gonna give the latest 6.6 from kernel.org a spin to verify. > Could it be the same problem there, that it works sometimes and doesn't > work sometimes? Again I've never encountered this issue with 6.6 or any other kernel before. I would have remembered that. > The reason why I'm asking is that Damien's major changes got included > in v6.6-rc4: > https://lore.kernel.org/linux-ide/20230929133324.164211-1-dlemoal@xxxxxxxxxx/[https://lore.kernel.org/linux-> ide/20230929133324.164211-1-dlemoal@xxxxxxxxxx/] > So I would be less surprised if you said that you can enter pc8 on every > boot on v6.5, but on v6.6 it only works occasionally. To be sure I would have to switch back to 6.6. If I find the time I'll give it a shot. > But if you can enter pc8 on every boot on v6.6, but not on v6.7, > then it is probably easier to figure out which commit that broke > things, as there were not that many suspend/resume related changes > added in v6.7. Maybe you could point them out so I can try to bisect? Kind regards, Dieter
