Public bug reported:

[Impact]
Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display.

[Fix]
Disable IOMMU on Stoney Ridge.

[Test]
Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be
observed.
The flickering/tearing is gone once the patch is applied.

[Regression Potential]
Low. This fix limits to one specific SoC.
According to AMD, IOMMU isn't enabled for this SoC under Windows.
So it's expected behavior.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Eoan)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Focal)
     Importance: Undecided
         Status: New


** Tags: busan oem-priority originate-from-1852195

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Tags added: busan oem-priority originate-from-1852195

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

Title:
  Fix AMD Stoney Ridge screen flickering under 4K resolution

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  New

Bug description:
  [Impact]
  Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display.

  [Fix]
  Disable IOMMU on Stoney Ridge.

  [Test]
  Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be
  observed.
  The flickering/tearing is gone once the patch is applied.

  [Regression Potential]
  Low. This fix limits to one specific SoC.
  According to AMD, IOMMU isn't enabled for this SoC under Windows.
  So it's expected behavior.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to