i915: 6.6.25: pipe state doesn't match for gamma_enable and post_csc_lut

[AndreasUfert]

In Yocto 5.0 scarthgap using kernel 6.6.25 from meta-intel we have the following i915 error:

[ 18.211203] i915 0000:00:02.0: [drm] ERROR [CRTC:51:pipe A] mismatch in gamma_enable (expected yes, found no)
[ 18.211251] i915 0000:00:02.0: [drm] ERROR [CRTC:51:pipe A] mismatch in post_csc_lut hw_state doesn't match sw_state
[ 18.211282] ------------[ cut here ]------------
[ 18.211296] i915 0000:00:02.0: pipe state doesn't match!
[ 18.211423] WARNING: CPU: 0 PID: 841 at /drivers/gpu/drm/i915/display/intel_modeset_verify.c:222 intel_modeset_verify_crtc+0x450/0x4e0 [i915]
[ 18.212618] Modules linked in: 8021q ti_adc081c industrialio_triggered_buffer kfifo_buf industrialio intel_rapl_msr intel_rapl_common intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp gpio_keys spi_pxa2xx_platform pwm_pca9685 dw_dmac at24 pwm_lpss_platform pwm_lpss sch_fq_codel uio i915 drm_buddy video wmi drm_display_helper configfs nfnetlink
[ 18.212856] CPU: 0 PID: 841 Comm: X Tainted: G U 6.6.25-intel-pk-standard #1
[ 18.212884] Hardware name: Intel E600/E600, BIOS 4.0 06/12/2017
[ 18.212898] RIP: 0010:intel_modeset_verify_crtc+0x450/0x4e0 [i915]
[ 18.214069] Code: 5d a8 e9 50 fd ff ff 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 b2 9c 88 f0 48 89 da 48 c7 c7 68 3b 79 c0 48 89 c6 e8 a0 67 0e f0 <0f> 0b e9 32 fe ff ff 48 8b 5f 50 48 85 db 75 03 48 8b 1f 89 4d a8
[ 18.214102] RSP: 0018:ffffbd3f4089fac0 EFLAGS: 00010282
[ 18.214128] RAX: 0000000000000000 RBX: ffffa1ed01a31610 RCX: 0000000000000027
[ 18.214146] RDX: ffffa1ed7921c448 RSI: 0000000000000001 RDI: ffffa1ed7921c440
[ 18.214163] RBP: ffffbd3f4089fb30 R08: 0000000000000000 R09: ffffffffb1e4f080
[ 18.214179] R10: ffffbd3f4089f928 R11: ffffffffb1ebf0c8 R12: ffffa1ed04a22000
[ 18.214196] R13: ffffa1ed079fa000 R14: ffffa1ed04a182b0 R15: ffffa1ed04a18000
[ 18.214213] FS: 00007f53b5b85440(0000) GS:ffffa1ed79200000(0000) knlGS:0000000000000000
[ 18.214234] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 18.214251] CR2: 00007f26aca49780 CR3: 000000000df96000 CR4: 00000000001006f0
[ 18.214269] Call Trace:
[ 18.214283]
[ 18.214300] ? show_regs+0x64/0x70
[ 18.214332] ? __warn+0x84/0x150
[ 18.214363] ? intel_modeset_verify_crtc+0x450/0x4e0 [i915]
[ 18.215514] ? report_bug+0x171/0x1a0
[ 18.215552] ? console_unlock+0x53/0xe0
[ 18.215580] ? handle_bug+0x42/0x80
[ 18.215609] ? exc_invalid_op+0x1c/0x70
[ 18.215637] ? asm_exc_invalid_op+0x1f/0x30
[ 18.215674] ? intel_modeset_verify_crtc+0x450/0x4e0 [i915]
[ 18.216834] ? frontbuffer_flush+0x80/0xe0 [i915]
[ 18.218020] intel_atomic_commit_tail+0x828/0xdb0 [i915]
[ 18.219270] intel_atomic_commit+0x32a/0x370 [i915]
[ 18.220518] drm_atomic_commit+0x98/0xd0
[ 18.220563] ? __pfx___drm_printfn_info+0x10/0x10
[ 18.220598] drm_atomic_helper_set_config+0x7d/0xc0
[ 18.220629] drm_mode_setcrtc+0x3ca/0x7f0
[ 18.220670] ? __pfx_drm_mode_setcrtc+0x10/0x10
[ 18.220730] drm_ioctl_kernel+0xd5/0x180
[ 18.220766] drm_ioctl+0x2b1/0x550
[ 18.220792] ? __pfx_drm_mode_setcrtc+0x10/0x10
[ 18.220830] __x64_sys_ioctl+0x9c/0xd0
[ 18.220860] do_syscall_64+0x47/0x90
[ 18.220889] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 18.220922] RIP: 0033:0x7f53b5e6b05c
[ 18.220946] Code: 1e fa 48 8d 44 24 08 48 89 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 b8 10 00 00 00 c7 44 24 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 0b 89 d0 c3 0f 1f 84 00 00 00 00 00 48 8b
[ 18.220969] RSP: 002b:00007ffcebbb6cf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 18.220997] RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007f53b5e6b05c
[ 18.221014] RDX: 00007ffcebbb6d60 RSI: 00000000c06864a2 RDI: 000000000000000c
[ 18.221030] RBP: 00007ffcebbb6d60 R08: 0000562fc984cda0 R09: 0000000000011a6c
[ 18.221047] R10: 0000000000000007 R11: 0000000000000246 R12: 00000000c06864a2
[ 18.221063] R13: 000000000000000c R14: 00007f53b4dfd000 R15: 0000562fc9849190
[ 18.221091]
[ 18.221103] ---[ end trace 0000000000000000 ]---

The display is connected to the GPU output DP-1 using a NXP PTN3460 eDP to LVDS bridge.

The display, however, works fine despite this error.

The problem does not occur in kernel 6.8 which we can't choose, though, because we need LTS.

[kraj]

@AndreasUfert maybe report it to upstream?

[AndreasUfert]

Just have done that: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11080