Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

[Kai-Chuan Hsieh]

Screen can't turn back on by clicking keyboard after screen off by meta + l key.
Try to do VT switch can make the screen back, some error poped when I try to wake up screen.

gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

==========================================================================

SRU Justification

[Impact]
The backlight power won't come back after the meta + l to turn off the display on ADL machines.

[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform

[Test]
Verified on at least 2 different machines, the backlight is on after the screen dimmed with touchpad movement or key stroke.

[Where problems could occcur]
The patches only affect ADL-P and up.

[Kai-Chuan Hsieh (kchsieh)]

apport information

[Kai-Chuan Hsieh (kchsieh)]

apport information

[Kai-Chuan Hsieh (kchsieh)]

apport information

[Kai-Chuan Hsieh (kchsieh)]

apport information

[Kai-Chuan Hsieh (kchsieh)]

Upload journalctl log.

[Kai-Chuan Hsieh (kchsieh)]

I can't reproduce the issue on 5.17.0-1003-oem kernel.

[Kai-Chuan Hsieh (kchsieh)]

I found this bug in upstream https://gitlab.gnome.org/GNOME/mutter/-/issues/2005, but I can still reproduce it after updating mutter to 42.0-1ubuntu1 with 5.15 kernel.

[Daniel van Vugt (vanvugt)]

Looks like the same error as https://gitlab.gnome.org/GNOME/mutter/-/issues/2197

[Daniel van Vugt (vanvugt)]

Please try these in /etc/environment:

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
  MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1

and then reboot.

If that works then please figure out which one is actually fixing the problem.

[Daniel van Vugt (vanvugt)]

Please also run:

  sudo drm_info > drminfo.txt

and attach the resulting text file here.

[Kai-Chuan Hsieh (kchsieh)]

MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 can still reproduce the issue.
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 gdm3 can't up successfully.

[Daniel van Vugt (vanvugt)]

Yes this is an Alder Lake issue which seems to have originated in the kernel. But at the same time we should make mutter more robust to handle missing driver features.

Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2197

[AceLan Kao (acelankao)]

Confirmed with fresh installed Jammy release(5.15.0-23). After the screen dim, the backlight power is off, "/sys/class/backlight/intel_backlight/bl_power", and can't echo 0 to it to light up.

Switch vt(ctrl+alt+F1) works, and then I can turn off and turn on the backlight by
   echo 4 | sudo tee /sys/class/backlight/intel_backlight/bl_power
   echo 0 | sudo tee /sys/class/backlight/intel_backlight/bl_power

Close the lid and then open it, got the same behavior as meta+l, can't turn on the backlight.

[AceLan Kao (acelankao)]

Can't reproduce this issue with KDE.
And can't boot up the machine with mainline kernel. So, it's hard to bisect if it's a kernel issue.

[Daniel van Vugt (vanvugt)]

Indeed it's mostly a mutter bug. And even then mutter won't try to use the missing GAMMA_LUT feature most of the time.

[Daniel van Vugt (vanvugt)]

New fix proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360

[Kai-Chuan Hsieh (kchsieh)]

I try the fix in #16 with the following command on XPS 9320, the result looks good to me.

$ sudo add-apt-repository ppa:kchsieh/verification
$ sudo apt install libmutter-10-0
$ sudo reboot

Thanks,

[Daniel van Vugt (vanvugt)]

Missing the GAMMA_LUT property on this OLED panel still feels like an i915 kernel bug to me. Not something Intel would intentionally omit. Please try the latest DRM kernel here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

The upstream mutter bug report also mentioned that a newer kernel solved it for them.

[Kai-Chuan Hsieh (kchsieh)]

@vanvugt

Hello,

Will you help to SRU it for jammy?

Thanks,

[Daniel van Vugt (vanvugt)]

There may be no need if 42.1 is tagged in the next week or so. It's scheduled for 23 April (roughly):

  https://wiki.gnome.org/FortyTwo

I imagine we will SRU 42.1 quickly. Also I don't have any sponsorship powers myself.

[AceLan Kao (acelankao)]

Thanks Timo, this series of patches seems fix this issue
https://www.spinics.net/lists/intel-gfx/msg284609.html

Here is the test kernel, I can't reproduce the issue with this kernel.
https://people.canonical.com/~acelan/bugs/lp1967274/

I'll submit SRU soon.

[Daniel van Vugt (vanvugt)]

Yeah a kernel fix is more useful because you won't get Night Light or colour profile support without a kernel fix.

[Kai-Chuan Hsieh (kchsieh)]

verify #21, the result is good. The kernel log for reference.

[AceLan Kao (acelankao)]

SRU sent
https://lists.ubuntu.com/archives/kernel-team/2022-April/129627.html

[Daniel van Vugt (vanvugt)]

> [Impact]
> The backlight power won't come back after the meta + l to turn off the
> display on ADL machines.

Judging by drminfo.txt, there is no backlight because it's OLED. Only the OLED variant of XPS 9320 is 3456x2160 pixels.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.15.0-28.29 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

[Kai-Chuan Hsieh (kchsieh)]

Verify kernel #26, the screen can work properly on XPS 9320 OLED sku after off, and gnome-shell has no "Failed to post KMS update: CRTC property (GAMMA_LUT) not found" error.

[Daniel van Vugt (vanvugt)]

Maybe also try enabling Night Light?

[Daniel van Vugt (vanvugt)]

The same kind of bug has now been seen in:

  * i915: Intel Alder Lake GPUs
  * vboxvideo: Legacy non-default graphics VirtualBox controllers
  * mgag200: Matrox server graphics

In all three cases we need the fix coming in mutter 42.1, but Intel Alder Lake would be better addressed with a kernel fix mentioned above.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-hwe-5.15/5.15.0-32.33~20.04.1 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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!

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 42.1-1ubuntu1

---------------
mutter (42.1-1ubuntu1) kinetic; urgency=medium

  [ Jeremy Bicha ]
  * Merge from Debian unstable. Remaining changes:
    - Add triple-buffering patch
    - Add x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr
    - Add ubuntu/wayland-data-device-Allow-any-drag-timestamp....patch
      + Allow any drag timestamp as drag start serial
    - Add backends-native-kms-crtc-Don-t-compare-gamma-values-on-un.patch
      + Avoid memory errors when comparing gamma values
    - Add monitor-manager-Ensure-monitors-settings-after-backend-ha.patch
      + Ensure privacy screen settings are applied on startup
    - Add patches from GNOME !2364
      + Fix X11 selection related crash when Xwayland died
    - debian/libmutter-10-0.symbols: Add symbols for triple buffering patch
  * Refresh triple buffering patch with latest version

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Adapt expected messages to new domains

mutter (42.1-1) unstable; urgency=medium

  * New upstream release
    (LP: #1972726, #1967274, #1965557, #1969574, #1948410, #1967219, #1971693)
  * Drop patches applied in new release
  * debian/libmutter-10-0.symbols: Add new symbol
  * debian/libmutter-10-0.symbols: Drop a symbol that was only in experimental
  * Add Breaks against old gtk3 & gtk4 versions.
    See Ubuntu bug 1972721
  * Release to unstable

mutter (42.0-5) experimental; urgency=medium

  * Team upload
  * d/patches: Update to upstream commit 42.0-74-g6c8e8fbba
    - Bug fixes targeted for 42.1
    - d/p/clutter-stage-Repick-when-pointer-actor-goes-unmapped.patch:
      Replace with the version that was applied upstream
    - d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
      Mark as applied upstream

mutter (42.0-4) unstable; urgency=medium

  * Team upload
  * d/patches: Update to upstream commit 42.0-55-gbe9deeba0
    - Update translations
    - Update upstream status of cherry-picked patches
    - Add various bug fixes including LP: #1959888, LP: #1964037
  * d/p/core-Account-ClutterStage-grabs-on-Wayland-key-focus-sync.patch:
    Add patch proposed upstream to fix grabs vs. system-modal prompts.
    This is particularly annoying when using pkexec, or when using gcr as
    a passphrase prompt for PGP, ssh and/or sudo.
    (Closes: #1008998, LP: #1964442)

 -- Jeremy Bicha <email address hidden> Fri, 13 May 2022 09:14:41 -0400

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.15.0-35.36

---------------
linux (5.15.0-35.36) jammy; urgency=medium

  * CVE-2022-21499
    - SAUCE: debug: Lock down kgdb

linux (5.15.0-34.35) jammy; urgency=medium

  * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)

  * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
    - drm/amdgpu: unify BO evicting method in amdgpu_ttm
    - drm/amdgpu: explicitly check for s0ix when evicting resources

  * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
    (LP: #1971597)
    - gpio: Request interrupts after IRQ is initialized

  * config CONFIG_HISI_PMU for kunpeng920 (LP: #1956086)
    - [Config] CONFIG_HISI_PMU=m

  * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
    - ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops

  * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
    (LP: #1971418)
    - Revert "rfkill: make new event layout opt-in"

  * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
    (LP: #1942160)
    - SAUCE: vmd: fixup bridge ASPM by driver name instead

  * Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
    - ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on EliteBook
      845/865 G9

  * Enable headset mic on Lenovo P360 (LP: #1967069)
    - ALSA: hda/realtek: Enable headset mic on Lenovo P360

  * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
    - Bluetooth: btusb: Improve stability for QCA devices

  * Screen sometimes can't update [Failed to post KMS update: CRTC property
    (GAMMA_LUT) not found] (LP: #1967274)
    - drm/i915/xelpd: Enable Pipe color support for D13 platform
    - drm/i915: Use unlocked register accesses for LUT loads
    - drm/i915/xelpd: Enable Pipe Degamma
    - drm/i915/xelpd: Add Pipe Color Lut caps to platform config

  * Jammy update: v5.15.35 upstream stable release (LP: #1969857)
    - drm/amd/display: Add pstate verification and recovery for DCN31
    - drm/amd/display: Fix p-state allow debug index on dcn31
    - hamradio: defer 6pack kfree after unregister_netdev
    - hamradio: remove needs_free_netdev to avoid UAF
    - cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
    - ACPI: processor idle: Check for architectural support for LPI
    - ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
    - btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
    - btrfs: remove no longer used counter when reading data page
    - btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
    - soc: qcom: aoss: Expose send for generic usecase
    - dt-bindings: net: qcom,ipa: add optional qcom,qmp property
    - net: ipa: request IPA register values be retained
    - btrfs: release correct delalloc amount in direct IO write path
    - ALSA: core: Add snd_card_free_on_error() helper
    - ALSA: sis7019: Fix the missing error handling
    - ALSA: ali5451: Fix the missing snd_card_free() call at probe error
    - ALSA: als300: Fix the missing snd_card_free() call at probe error
    - ALSA: als4000: Fix ...

[Ionut Negru (blackjohnny)]

I am using kernel v5.15.0-37 but I am still affected by this bug on my XPS 15 (9500). Installed mutter is 42.1.

Also, the Night Light is not working (I saw some references in this thread about this feature).

Is there anything else I must update on my system to have it working properly?

Thanks!

[Daniel van Vugt (vanvugt)]

This bug is fixed already in 42.1. If you still have problems then please open a new bug by running:

  ubuntu-bug gnome-shell

and we can work from there.

[Ionut Negru (blackjohnny)]

Thank you Daniel!

I have added the bug information here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534

[Germán Poo-Caamaño (gpoo)]

I would like to add one extra data point.

I was bitten by this issue using 22.10 (Kinetic), but with Linux 5.14-oem (the one shipped with Lenovo Thinkpad X1 Gen 10th, from 22.04).

From what I read, mutter 43.0 should have handled it nicely, but it did not. Otherwise I would not have arrived here :-)

Upgrading to Linux 5.17.0-1003-oem did work, though.

FWIW, I had some crashes with vmlinuz-5.19.0-23 at boot time and later on, so I tried the kernel that came with the laptop (5.14.0-1054-oem).

[Daniel van Vugt (vanvugt)]

Yes the mutter fix got lost/regressed and so we are dependent on having just the kernel fix now. This is being tracked in bug 1985869.