Bug 113191 - Lenovo ideapad 100s doesnt wake from suspend
Summary: Lenovo ideapad 100s doesnt wake from suspend
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_power-sleep-wake
Depends on:
Blocks: 113151
  Show dependency tree
Reported: 2016-02-25 19:44 UTC by dan.g.tob
Modified: 2016-03-15 08:29 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.4.2
Tree: Mainline
Regression: No

systemd journal (114.17 KB, text/x-log)
2016-02-25 19:44 UTC, dan.g.tob

Description dan.g.tob 2016-02-25 19:44:57 UTC
Created attachment 206121 [details]
systemd journal

don't have any useful logs yet
Comment 1 Zhang Rui 2016-02-29 02:28:52 UTC
Please be specific about the symptom of the problem. And then follow the corresponding section of Chapter 4, in this doc https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
Comment 2 dan.g.tob 2016-02-29 04:31:55 UTC
booted into rescue/single user mode (systemd.unit=rescue)

freeze disk

echo freeze > /sys/power/state ; machine appears to suspend. all leds go out, screen goes blank. machine cant be woken by keyboard, touchpad or power button, screen open/close etc. caps lock led doesnt respond.

dmesg reports only s0 and s5 are supported

Device	S-state	  Status   Sysfs node
WLAN	  S0	 disabled  sdio:mmc1:0001:1
RTLW	  S0	 disabled

(^ should I be seeing touchpad/keyboard here?)

tried to setup netconsole but;
netconsole: wlan0 doesn't support polling, aborting
Comment 3 Zhang Rui 2016-03-15 08:29:58 UTC
AFAICS, this is still a BIOS related issue as there is no ACPI S3, which surprises me.
If you're using freeze state, you should enable the driver wakeup capability as well. And it seems that there are either driver gaps or BIOS gaps to support freeze state from my point of view. Please tell me that you bought this laptop from the market...

Anyway, I'm closing this bug as the problem you mentioned are rather BIOS/vender_driver gaps that should not be tracked & fixed here.

Note You need to log in before you can comment on or make changes to this bug.