All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Viresh Kumar' <viresh.kumar@linaro.org>,
	"'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: linux-pm@vger.kernel.org, Doug Smythies <dsmythies@telus.net>
Subject: As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION]
Date: Wed, 7 Oct 2015 15:51:13 -0700	[thread overview]
Message-ID: <001f01d10152$ab653de0$022fb9a0$@net> (raw)

Hi,

This started somewhere between Kernel 4.2 and 4.3-rc1,
but I only noticed it now.

The first S3 suspend after a fresh boot works fine.
Thereafter, suspends simply resume again immediately.

I get the following errors on my console:

[  152.697247] i915 0000:00:02.0: GEM idle failed, resume might fail
[  152.697258] pci_pm_suspend(): i915_pm_suspend+0x0/0x50 [i915] returns -11
[  152.697262] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -11
[  152.697264] PM: Device 0000:00:02.0 failed to suspend async: error -11
[  152.697306] PM: Some devices failed to suspend, or early wake event detected

The issue is not limited to my normal way of doing suspend, using "pm-suspend".
It also happens using the "echo mem > /sys/power/state" method that Rafael mentioned
during the 4.2 cycle.

I have searched the bug reports and such and didn't find a related bug, (which
doesn't mean it doesn't exist, just that if it does I didn't find it).

I am about to start bisecting the kernel, but thought to ask here first, just in case
someone already knows the root issue.

Note: There was the e-mail earlier 
"Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting"
But he has had the issue since kernel 3.19.0, and I tried his workaround, without
success, anyhow.



             reply	other threads:[~2015-10-07 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 22:51 Doug Smythies [this message]
2015-10-07 23:40 ` As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION] Rafael J. Wysocki

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='001f01d10152$ab653de0$022fb9a0$@net' \
    --to=dsmythies@telus.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.