[8086:3e92] display becomes blank after S3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem (Ubuntu) |
Fix Released
|
Undecided
|
AceLan Kao | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The display becomes black after S3 with the following error messages.
dmesg:
[ 60.546305] [drm:intel_
Xorg.0.log:
[ 60.748] (EE) modeset(0): failed to set mode: Invalid argument
[ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, tried resetting the current mode. You may be left with a black screen if this fails...
[Fix]
Looks like link training fallback fails sometimes with eDP, we need this commit to fix the issue.
commit a306343bcd7df89
Author: Manasi Navare <email address hidden>
Date: Thu Oct 12 12:13:38 2017 -0700
drm/i915/edp: Do not do link training fallback or prune modes on EDP
[Regression Potential]
Should be low.
To avoid conflicts, we introduce 4 commits, I'll try explaining them below
a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP
This is the fix commit and the behavior only changes when DP is eDP, it does nothing if DP is eDP. Should be fine to not do link training fallback and not emit Hotplug Uevent to userspace to start modeset, since its eDP, the display is fixed.
1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_
Above 2 commits do function name renaming only.
dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available.
Change the prototype of function "intel_
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: originate-from-1758823 somerville |
Changed in linux-oem (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in linux-oem (Ubuntu): | |
status: | In Progress → Invalid |
status: | Invalid → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Artful): | |
status: | New → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Invalid |
Changed in linux-oem (Ubuntu Artful): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in linux (Ubuntu Artful): | |
status: | In Progress → Fix Committed |
Changed in linux-oem (Ubuntu): | |
status: | In Progress → Fix Released |
tags: |
added: verification-done-artful removed: verification-needed-artful |
Changed in linux (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in linux-oem (Ubuntu Bionic): | |
status: | New → Invalid |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in hwe-next: | |
status: | New → Fix Released |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1763271
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.