My workstation was faking sleep: how a $15 meter caught 163 watts of waste
A high-end Threadripper workstation was draining nearly 180 watts while suspended until a simple BIOS fix resolved it.
Stock photo for illustration only, not from the actual event
- A Threadripper workstation consumed 179.8 watts while seemingly suspended in s2idle mode.
- Linux default kernel settings often utilize software-only s2idle instead of deep hardware sleep.
- Enabling S3 sleep within the motherboard BIOS dropped suspended power draw down to 17 watts.
- A budget 15-dollar smart plug revealed the true electrical draw directly from the wall outlet.
A software developer running a high-end Threadripper workstation equipped with dual RTX A6000 GPUs in a home lab noticed warm air venting from the chassis while the machine was supposedly inactive. Prompted by curiosity, the owner purchased an energy-monitoring smart plug costing around 15 dollars to measure the actual power draw at the wall outlet, revealing an astonishing figure: the suspended machine was drawing 179.8 watts, which was significantly higher than its idle desktop power consumption of about 123 watts.
The root cause traces back to Linux power-management handling, which supports multiple suspension states. By default, systems often utilize s2idle, a software-only doze where the kernel pauses operations while platform components such as fans, voltage regulator modules, and peripheral devices remain fully powered. Compounding the issue, the power-management daemons responsible for minimizing idle draw cease execution while the operating system is parked, leaving the hardware burning energy continuously.
Stock photo for illustration only, not from the actual event
Inspecting the system configuration using the command cat /sys/power/mem_sleep displayed only [s2idle] with no option for deep sleep. The ASUS WRX90 workstation motherboard had S3 sleep disabled by default within its firmware under the Advanced menu and APM Configuration section. After adjusting the BIOS setting to enable S3 mode, rebooting the system, and running the same diagnostic command, the kernel automatically defaulted to real S3 sleep state.
The S3 (Suspend-to-RAM) state is a foundational power-saving standard where system memory enters a self-refresh mode while nearly all other components are powered down, allowing rapid resumption with minimal energy usage. Modern hardware platforms frequently ship with S3 disabled or superseded by vendor-driven modern standby architectures, which frequently introduces hidden power drainage issues for Linux deployments.
Following this single firmware adjustment, re-running the suspension command caused the energy monitor reading to plummet from 179.8 watts down to 17 watts. Wake-on-LAN functionality remained fully operational, and the dual GPUs resumed cleanly. The remaining 17-watt draw was attributed to the motherboard's Baseboard Management Controller, a dedicated management computer providing remote console access that remains continuously active by design.
Users encountering similar symptoms can follow these diagnostic steps to verify and fix their hardware:
- Check available sleep states via
cat /sys/power/mem_sleep. - If only s2idle is listed, inspect the BIOS settings for an S3 or ACPI sleep toggle.
- Force deep sleep mode manually using
echo deep | sudo tee /sys/power/mem_sleep. - Deploy a hardware smart plug to measure actual wall power rather than relying solely on system logs.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment