System cannot recover from S4, but can still be accessed remotely by ssh. tested on: Arch: x86_64 OSD: Fedora release 8 (Werewolf) Kernel: (for-linus)07f4f3e8a24138ca2f3650723d670df25687cd05 Libdrm: (master)2cb4c64d7310904b354365c2cbc263211e9eb4a1 Mesa: (mesa_7_5_branch)fc7f92478286041a018ac4e72d2ccedeea7c0eca Xserver: (server-1.6-branch)5cd5a01259ba349f1868ca4af04207cf120d69e4 Xf86_video_intel: (master)66ceedc0cc123e5c9f85f708b2e56d943f00e4b9
Created attachment 26520 [details] dmesg
S4 works fine with UMS, and will fail with KMS kernel no matter X is started or not.
Hi, Yifen Will you please try the latest linus git tree and see whether it can be resumed from hibernation? BTW: had better add the boot option of "resume= xxx", xxx means the swap partition. Thanks.
I do the test on this box by using the latest linux kernel(2.6.31-rc2) and S4 can work well. So this bug can be marked as resolved. BTW: the boot option of "resume=xxx" had better be added for the S4 test. XXX means the swap partition. Thanks.
S4 works find now, though there's still one small problem: compiz will lost all the windows' decoration after resume, all other stuff looks good now.
let's track the rest compiz issue at bug#22433.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.