Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
AceLan Kao | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
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.
CVE References
Changed in linux (Ubuntu Kinetic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
status: | New → Won't Fix |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu Kinetic): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
assignee: | nobody → AceLan Kao (acelankao) |
description: | updated |
tags: | added: oem-priority originate-from-1990928 somerville |
description: | updated |
Changed in linux (Ubuntu Kinetic): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
This bug is awaiting verification that the linux/5.19.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- kinetic' to 'verification- done-kinetic' . If the problem still exists, change the tag 'verification- needed- kinetic' to 'verification- failed- kinetic' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!