Verified linux-oem-6.11 version 6.11.0-1010.10 from ppa:canonical- kernel-team/proposed2.
** Description changed: + BugLink: https://bugs.launchpad.net/bugs/2090789 + + [Impact] + + During boot up and resume the DC layer will reset the panel brightness + to fix a flicker issue. It will cause the `dm->actual_brightness` is not + the current panel brightness level. So we set the backlight level with + `dm->brightness` value after set mode. + + [Fix] + + Proposed fix + https://github.com/torvalds/linux/commit/4f26c95ffc21a91281429ed60180619bae19ae92 + (in v6.12-rc7, and d83c747a1225d as in v6.11.8) + + [Test Case] + + 1. Set panel brightness value to, say 5%, by pressing keyboard function keys. + 2. Reboot and check if the actual panel brightness matches the setting. + + [Where problems could occur] + + This is to reset panel brightness value, not expecting anything could go + wrong. + + [Other Info] + + This has been in v6.12 and v6.11.8. SRU for oem-6.11 kernel for this + cycle only. + + ========== original bug report ========== + Upstream bug: https://gitlab.freedesktop.org/drm/amd/-/issues/3655: Actually the issue happen when 1. Login to a system to console mode, set brightness to 5% (light -S 5 or direct in sysfs), run compositor from command line. Screen brightness go up. 2. Turn brigtness down to 5% in wayfire screen, switch to text console and back to wayfire - again screen brightness goes up. 3. Turn brightness to 5% in wayfire and then screen blanks at idle. Touch key or mouse - screen again runs on the much higher brightness. In all cases in the /sys/class/backlight/amdgpu_bl0 directory brightness keep the value I set (5%) - but the actual brightness is different. So system somehpw ignores the value in brightness and not setting actual brightness the same but fill it with some default. == Proposed fix https://github.com/torvalds/linux/commit/4f26c95ffc21a91281429ed60180619bae19ae92 (in v6.12-rc7, and d83c747a1225d as in v6.11.8) ** Tags removed: verification-needed-noble-linux-oem-6.11 ** Tags added: verification-done-noble-linux-oem-6.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2090789 Title: display brightness level not retained over reboot with amdgpu Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2090789 [Impact] During boot up and resume the DC layer will reset the panel brightness to fix a flicker issue. It will cause the `dm->actual_brightness` is not the current panel brightness level. So we set the backlight level with `dm->brightness` value after set mode. [Fix] Proposed fix https://github.com/torvalds/linux/commit/4f26c95ffc21a91281429ed60180619bae19ae92 (in v6.12-rc7, and d83c747a1225d as in v6.11.8) [Test Case] 1. Set panel brightness value to, say 5%, by pressing keyboard function keys. 2. Reboot and check if the actual panel brightness matches the setting. [Where problems could occur] This is to reset panel brightness value, not expecting anything could go wrong. [Other Info] This has been in v6.12 and v6.11.8. SRU for oem-6.11 kernel for this cycle only. ========== original bug report ========== Upstream bug: https://gitlab.freedesktop.org/drm/amd/-/issues/3655: Actually the issue happen when 1. Login to a system to console mode, set brightness to 5% (light -S 5 or direct in sysfs), run compositor from command line. Screen brightness go up. 2. Turn brigtness down to 5% in wayfire screen, switch to text console and back to wayfire - again screen brightness goes up. 3. Turn brightness to 5% in wayfire and then screen blanks at idle. Touch key or mouse - screen again runs on the much higher brightness. In all cases in the /sys/class/backlight/amdgpu_bl0 directory brightness keep the value I set (5%) - but the actual brightness is different. So system somehpw ignores the value in brightness and not setting actual brightness the same but fill it with some default. == Proposed fix https://github.com/torvalds/linux/commit/4f26c95ffc21a91281429ed60180619bae19ae92 (in v6.12-rc7, and d83c747a1225d as in v6.11.8) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2090789/+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
