Isolation for broken hardware during system suspend
summary
Drivers can abort system suspend by returning errors from their suspend callbacks, which leaves a laptop seemingly asleep while it actually is not; networking drivers failing resume and device resets that then fail are common examples. The talk frames the dilemma: either honor driver vetoes or provide a system-level override like the old S3 “big hammer.” No patch is presented; discussion points include detecting genuinely broken hardware and applying quirks to force suspend when safe.
AI-written summary · about
related talks
36mLinux Power Management Features, Their Relationships and Interactions
36mLinux Power Management Features, Their Relationships and Interactions
47mEvolution of Suspend-to-Idle Support in The Linux Kernel
30mHost and Guest Suspend Under Xen - S3 and S0ix
47mIs Linux Suspend ready for the next decade
25mMultiple system-wide low power-states
33mRemote Core Power Management in AMP Systems
41mLinux Power Management Features & Their Interactions, Part 2
