group.of.nepali.translators team mailing list archive

[Timo Aaltonen <tjaalton@xxxxxxxxxx>]

** Changed in: linux-oem (Ubuntu Bionic)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759188

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] [CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759188/+subscriptions