From: Chris Chiu <chiu@endlessm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: GemniLake laptops goes power off directly after performing suspend
Date: Wed, 6 Dec 2017 00:19:03 +0800 [thread overview]
Message-ID: <CAB4CAwe-uahS0HECtqcQ4Mobwb6vD-pxb-v8vPY52t6z+sT5pg@mail.gmail.com> (raw)
In-Reply-To: <CAJZ5v0jS=E0mcm=R2xQSftSnzZXUbzL3RjjWafSYAB=Wd7=ECQ@mail.gmail.com>
On Tue, Dec 5, 2017 at 11:01 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:
> On Tue, Dec 5, 2017 at 11:32 AM, Chris Chiu <chiu@endlessm.com> wrote:
>> Hi,
>> I have 2 GemniLake laptops from ASUS, named X441MB and X507MA,
>> both go power off after I do "systemctl suspend" on top of kerne head
>> fd6d2e506ce6 (Merge tag 'docs-4.15-fixes' of git://git.lwn.net/linux).
>> I then wipe it out and install Windows RS3 instead, also goes to power
>> off after pressing media key for suspend(S3). Then I installed intel
>> graphic driver with the following version number, Windows has no
>> problem on suspend resume then.
>
> There is a suspend-related fix missing in 4.15-rc at this point, so
> please test 4.14.y or wait for the fix to be merged.
>
> Thanks,
> Rafael
You mean the suspend-related fix used to exist in 4.14? Could you point me
out which commit it is? Thanks
Chris
next prev parent reply other threads:[~2017-12-05 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:32 GemniLake laptops goes power off directly after performing suspend Chris Chiu
2017-12-05 15:01 ` Rafael J. Wysocki
2017-12-05 16:19 ` Chris Chiu [this message]
2017-12-05 21:56 ` Rafael J. Wysocki
2017-12-06 9:33 ` Chris Chiu
2017-12-06 13:34 ` Rafael J. Wysocki
2017-12-07 2:14 ` Chris Chiu
2017-12-08 10:31 ` Daniel Drake
2017-12-12 13:32 ` [Intel-gfx] " Imre Deak
2017-12-13 8:57 ` Chris Chiu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB4CAwe-uahS0HECtqcQ4Mobwb6vD-pxb-v8vPY52t6z+sT5pg@mail.gmail.com \
--to=chiu@endlessm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).