As of kernel 4.3-rc1 system will not stay in S3 suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Critical
|
|||
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Note: this bug report is just for local tracking of an upstream issue:
Reference: http://
also copied below:
This started somewhere between Kernel 4.2 and 4.3-rc1,
but I only noticed it a day ago.
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_
[ 152.697262] dpm_run_callback(): pci_pm_
[ 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.
The kernel was bisected, and the result was double checked by clean compiles
of the first bad commit and the immediately preceding commit. Bisect results
copied below:
$ git bisect good
dc4be6071a24f0d
commit dc4be6071a24f0d
Author: John Harrison <email address hidden>
Date: Fri May 29 17:43:39 2015 +0100
drm/i915: Add explicit request management to i915_gem_init_hw()
Now that a single per ring loop is being done for all the different
intialisation steps in i915_gem_init_hw(), it is possible to add proper request
management as well. The last remaining issue is that the context enable call
eventually ends up within *_render_
_i915_
This patch adds explicit request creation and submission to the top level loop
and removes the add_request() from deep within the sub-functions.
v2: Updated for removal of batch_obj from add_request call in previous patch.
For: VIZ-5115
Signed-off-by: John Harrison <email address hidden>
Reviewed-by: Tomas Elf <email address hidden>
Signed-off-by: Daniel Vetter <email address hidden>
Changed in linux: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → Incomplete |
tags: | added: bisect-done kernel-bug-exists-upstream |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux: | |
status: | Incomplete → Confirmed |
Changed in linux: | |
status: | Confirmed → Incomplete |
Changed in linux: | |
importance: | High → Critical |
Changed in linux: | |
status: | Incomplete → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1504584
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.