> The only issue is that s2idle drains the battery like crazy compared to S3.
Properly working s2idle should use as little power as S3, but it seems to be much more common with s2idle that some piece of hardware is left enabled while it should have been disabled to save power.
Well it seems that in theory it should exist, amd_s2idle script that tests various things. I can get the machine into what seems to be sleep, but if you listen careful on the fan you will hear that it's constantly restarting. The script then reports that most of the time is actually spent in user space, when what it should really do is spend over 90% in actual idle. Unfortunately no one seems to have a good answer on how I can find out what causes the user space sleep inhibitions. It's not a wakeup.
This is interesting. On my HPs, both Intel and AMD, the fan-on-while-it-should-be-sleeping thing only happens with Windows. Under Linux, the fan will turn off even if it was spinning, say if I put it to sleep during a compile and the laptop is hot.
On Linux, the fan never turns on and the pc never gets warm while asleep. Windows sometimes does something that requires the fan to spin like crazy, and the PC is usually somewhat warm to the touch.
Properly working s2idle should use as little power as S3, but it seems to be much more common with s2idle that some piece of hardware is left enabled while it should have been disabled to save power.