it looks like the SP3 legitimately does not expose the S3 state, and instead only allows MS's Connected Standby / InstantGo spec. As such there are two issues here that I can see: 1) pm-utils does not fall back on freeze 2) freeze state is using much more power than connected standby does on windows.
Let's restrict this bug to the first one as it's a couple of lines of bash to fix. Should I reassign this myself? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380076 Title: Can't suspend on Surface Pro 3 Status in “linux” package in Ubuntu: Incomplete Bug description: Suspend on surface pro 3 from GUI does not work. (Nothing happens) Doing it manually also fails, and nothing appears in dmesg: #echo "mem" > /sys/power/state Error while writing to stdout write_loop: Invalid argument And, more interestingly, #cat /sys/power/state freeze disk Using the not-so-good-and-apparently-unsupported #echo "freeze" > /sys/power/state does seem to successfully suspend, however I cannot resume from this (assumed to be a separate issue). Likewise, pm-hibernate seems somewhat functional. I am using a the utopic unicorn kernel compiled from git at kernel.ubuntu.com, with a tiny patch that is required for my keyboard to work (hard to file bug reports without a keyboard). The official kernel behaves identically, as does vanilla 3.17 from the mainline folder of kernel-ppa. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
