kernel-packages team mailing list archive

[Launchpad Bug Tracker <1554608@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux - 4.4.0-12.28

---------------
linux (4.4.0-12.28) xenial; urgency=low

  * Miscellaneous Ubuntu changes
    - reconstruct: Work around orig tarball packaging limitiations
      Fixes FTBS

 -- Tim Gardner <tim.gardner@xxxxxxxxxxxxx>  Tue, 08 Mar 2016 13:26:08
-0700

** Changed in: linux (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1554608

Title:
  Radeon hybrid graphics problem on resume

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  From mainline commit 256faed: Revert "drm/radeon: call hpd_irq_event on resume"
  (Ubuntu kernels T, U, V, W, and X carry the patch to be reverted).

  -----

  commit 256faedcfd646161477d47a1a78c32a562d2e845
  Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
  Date:   Mon Mar 7 13:15:09 2016 -0800

      Revert "drm/radeon: call hpd_irq_event on resume"
      
      This reverts commit dbb17a21c131eca94eb31136eee9a7fe5aff00d9.
      
      It turns out that commit can cause problems for systems with multiple
      GPUs, and causes X to hang on at least a HP Pavilion dv7 with hybrid
      graphics.
      
      This got noticed originally in 4.4.4, where this patch had already
      gotten back-ported, but 4.5-rc7 was verified to have the same problem.
      
      Alexander Deucher says:
       "It looks like you have a muxed system so I suspect what's happening is
        that one of the display is being reported as connected for both the
        IGP and the dGPU and then the desktop environment gets confused or
        there some sort problem in the detect functions since the mux is not
        switched to the dGPU.  I don't see an easy fix unless Dave has any
        ideas.  I'd say just revert for now"
      
      Reported-by: Jörg-Volker Peetz <jvpeetz@xxxxxx>
      Acked-by: Alexander Deucher <Alexander.Deucher@xxxxxxx>
      Cc: Dave Airlie <airlied@xxxxxxxxx>
      Cc: stable@xxxxxxxxxx  # wherever dbb17a21c131 got back-ported
      Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554608/+subscriptions