t14 gen2 amd

[OhYou_]

When you close the lid while it's plugged in, the laptop goes to sleep as expected, but the fan comes on and spins for a bit and goes off, about every 10-30 seconds.
When you unplug the laptop in this lid closed state, the fan maintains this cycle and basically begins draining your battery.
to fix it you have to disable modern standby or whatever by enabling s3 sleep which makes you reinstall the os.
latest firmware, latest windows 10 update, whatever.
what a piece of rubbish

[mikemex]

I don't even understand the necessity for the new state, as the old one was working perfectly fine. The only explanation I have is that they are trying to emulate phones by placing the whole system into a very low power state, but still active, so it can do things on the background and not suspend completely.

Could be useful if the asymmetric core design had a truly low power mode. But it seems to me like the new "efficient" cores are anything but efficient. So a good idea on paper, but bad on practice.

Or maybe this was intended with different architectures like ARM in mind?

[dr_st]

to fix it you have to disable modern standby or whatever by enabling s3 sleep which makes you reinstall the os.

You shouldn't have to reinstall the OS to switch between Modern Standby and Legacy S3, but I guess there can be various components that won't behave properly if you don't, as they were not implemented with the idea in mind that sleep modes can be changed on the fly.

I don't even understand the necessity for the new state, as the old one was working perfectly fine. The only explanation I have is that they are trying to emulate phones by placing the whole system into a low power draw state, but still active, so it can do things on the background and not suspend completely.

This is exactly what it is. To combine low-power with fast responsiveness (faster than from S3) and seamless connectivity. Contrary to intuition, if implemented properly, Modern Standby can even bring lower power consumption than S3, but... it's very hard to implement properly (as evident from OP's issue). There are just so many components and dependencies (hardware, system firmware, drivers, OS).

I think S0ix is the term Intel coined for it. "Modern Standby" is Microsoft's name, in Linux it is often referred to as "suspend to idle", versus S3 (suspend-to-RAM), S4 (suspend-to-disk), and S5 (power-off).

https://01.org/blogs/qwang59/2018/how-a ... ates-linux

[mikemex]

This is exactly what it is. To combine low-power with fast responsiveness (faster than from S3) and seamless connectivity. Contrary to intuition, if implemented properly, Modern Standby can even bring lower power consumption than S3, but... it's very hard to implement properly (as evident from OP's issue). There are just so many components and dependencies (hardware, system firmware, drivers, OS).

Everything on modern computing is super complex. Have you ever seen the UEFI specification? No wonder why Lenovo screwed it up on ts first implementations (say, the T420 et al)...

They'll get there, eventually. What I don't see a way around is the basic power demands of x86-64 cores. x86 is a stack based architecture (it stores procedure parameters in memory), so it depends on RAM for its basic operation. It is, in essence, a legacy architecture that began with 8 basic registers and it has only extended the amount to 16 when x64 came. It's still way limited compared to modern modern architectures (RISC-V, for example, provides 32).