From: Jan Niehusmann <jan@gondor.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Daniel Blueman <daniel@quora.org>,
Len Brown <len.brown@intel.com>
Subject: Re: Dell XPS13 does not suspend with Linux 4.10-rc3
Date: Tue, 10 Jan 2017 21:43:31 +0100 [thread overview]
Message-ID: <20170110204331.GA3974@x61s.reliablesolutions.de> (raw)
In-Reply-To: <7b1ba8e4-03b2-8a73-603b-63cce6403c31@molgen.mpg.de>
Hi,
On Tue, Jan 10, 2017 at 03:08:32PM +0100, Paul Menzel wrote:
> Testing Linux 4.10-rc{1,2,3} the Dell XPS13 does not suspend with the
> attached configuration. The screen turns black, but the power button never
> goes dark. The white light stays always on.
Same here.
And I bisected the issue to commit 7279b238ba, "mei: send OS type to the
FW"
Suspending from the console with no_console_suspend shows that the last
message is "e1000e: EEE TX LPI TIMER: 00000000" (which is probably
unrelated).
More interesting is the first message missing, ie. the one after the one
mentioned when using a working kernel: "ACPI : EC: event blocked".
This seems to be related to the bisected commit. Maybe it's not even the
kernel's fault, but the EC just happens to change it's behavior when it
got told about the OS type, before?
Jan
next prev parent reply other threads:[~2017-01-10 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:08 Dell XPS13 does not suspend with Linux 4.10-rc3 Paul Menzel
2017-01-10 14:21 ` Thorsten Leemhuis
2017-01-10 20:43 ` Jan Niehusmann [this message]
2017-01-10 22:24 ` Jan Niehusmann
2017-01-11 8:53 ` Paul Menzel
2017-01-11 9:36 ` Greg Kroah-Hartman
2017-01-11 9:41 ` Paul Menzel
2017-01-11 9:49 ` Winkler, Tomas
2017-01-11 17:16 ` Paul Menzel
2017-01-11 22:14 ` Winkler, Tomas
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=20170110204331.GA3974@x61s.reliablesolutions.de \
--to=jan@gondor.com \
--cc=daniel@quora.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=pmenzel@molgen.mpg.de \
/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).