** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995573
Title:
Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Screen cannot turn on after screen is off
[Fix]
Below commit from v6.0-rc1 fixes the issue
c577b2f43e80 drm/mgag200: Enable atomic gamma lut update
And applied some other commits to fix the conflicts
c48a36301634 drm/mgag200: Optimize damage clips
3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support
5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID
931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock
e13f13e039dc drm: Add DRM-managed mutex_init()
[Tests]
Verified on the machine with Matrox G200eW3 [102b:0536] graphics card.
[Where problems could occur]
The commits to solve the conflicts are trivial, and not likely to introduce
regressions. The fix patch change a lot of code and hard to evaluate the risk,
but check the latest linus/master tree and linux-next/master tree, there is no
fixed commit for all these cherry-picked commits, so should be safe to include
them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995573/+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
