https://bugzilla.suse.com/show_bug.cgi?id=1213830 https://bugzilla.suse.com/show_bug.cgi?id=1213830#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- No, no, everything should work as expected like before. The only difference of s2idle is that the explicit deep sleep is replaced with the runtime suspend of each driver. The wake up should work as the runtime resume of each driver, as well. If anything doesn't work, *that* should be reported, instead. It's more likely a bug of each individual driver / component. You're scratching a wrong surface. Note that s2idle was known to be problematic in the past because many drivers didn't follow the runtime PM properly. But, basically it's a bug of those drivers, and the situation became better nowadays, as it's fixed for most drivers. -- You are receiving this mail because: You are the assignee for the bug.