Let Sleeping CPUs Lie — S0ix

Lids down, batteries spared

It has been reported that the FreeBSD Foundation published a deep-dive by Aymeric Wibo about the surprisingly tricky business of making laptops actually sleep. Close the lid and you expect magic: hours, days, maybe weeks later, the machine wakes with the battery barely touched. Sounds trivial, right? In practice, the moment a screen goes dark is when an orchestra of silicon, firmware, and operating-system trickery has to play the quietest tune possible.

From SMM and SMI to ACPI — the long, bumpy road

Wibo walks readers through a history that matters because it explains why this is hard. Early systems used SMM/SMI — a firmware-controlled detour that could freeze the OS out of the loop. It has been reported that SMI handlers were a fertile ground for exploits, allegedly even surfacing in leaked toolsets like the NSA’s ANT catalogue. APM and later ACPI handed more responsibility to the OS, but only if the firmware behaved. In short: standards improved, but the ecosystem still depends on vendors writing decent, bug-free firmware. Easier said than done.

S0ix and the modern promise

Enter S0ix — a modern approach that keeps the system in S0 while pushing components into ultra-low-power states. The promise is elegant: let CPUs and peripherals do as little as possible while the OS retains control. For users it’s simple and emotional — that tiny moment of peace when you shut the lid and trust your laptop to sip battery, not guzzle it. For developers and firmware authors it’s a coordination problem: everyone must play by the new rules, or the machine will wake grumpy (or not at all).

Why it matters now

This isn’t just nerdy housekeeping. Mobile expectations have matured: instant resumes, long standby, and reliable battery life are baseline features. As Wibo’s piece argues, getting there requires continued work on firmware, standards, and OS power-management stacks — including on FreeBSD and other non-Linux systems trying to keep up. Want your laptop to behave like a well-trained dog and lie down until called? Then let sleeping CPUs lie — but only if everyone in the stack learns to whisper.

Sources: freebsdfoundation.org, Lobsters