Dual monitors and single display startup

With the latest kernel updates 6.8.1 and 6.8.2 the problem arose of having to disconnect the HDMI cable and replace it to access the second monitor. The bug does not appear in previous kernel versions.

In kernel versions 6.7.11 and 6.6.23 everything works fine.

The bug appeared with the last 3 patches released by Intel for mitigations.

------------[ cut here ]------------
[    2.006477] i915 0000:00:02.0: drm_WARN_ON(!connector->dp.dsc_decompression_aux || !connector->dp.dsc_decompression_enabled)
[    2.006493] WARNING: CPU: 4 PID: 253 at drivers/gpu/drm/i915/display/intel_dp.c:3193 intel_dp_sink_disable_decompression+0x63/0xf0 [i915]
[    2.006674] Modules linked in: ext4 crc32c_generic crc16 uas mbcache usb_storage jbd2 i915(+) crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 sha256_ssse3 i2c_algo_bi
t sha1_ssse3 drm_buddy aesni_intel ttm nvme intel_gtt crypto_simd drm_display_helper nvme_core cryptd wdat_wdt xhci_pci cec nvme_auth xhci_pci_renesas video wmi pinctrl_tigerlake vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) pkcs8_key_parser 
i2c_dev sg crypto_user
[    2.006700] CPU: 4 PID: 253 Comm: (udev-worker) Tainted: G           OE      6.8.2-arch1-1 #1 819344009c6dd5b594ee32401344754f6c37aaf0
[    2.006704] Hardware name: Intel(R) Client Systems NUC11TNHv5/NUC11TNBv5, BIOS TNTGLV57.0075.2023.1003.1410 10/03/2023
[    2.006705] RIP: 0010:intel_dp_sink_disable_decompression+0x63/0xf0 [i915]
[    2.006879] Code: 8b 5f 50 48 85 db 0f 84 95 00 00 00 e8 b6 c6 03 f0 48 c7 c1 30 47 ab c0 48 89 da 48 c7 c7 89 04 ad c0 48 89 c6 e8 6d e3 7a ef <0f> 0b 5b 5d c3 cc cc cc cc 83 e0 fd 31 d2 88 86 a1 09 00 00 e8 d4
[    2.006880] RSP: 0018:ffffba0300c5b810 EFLAGS: 00010286
[    2.006882] RAX: 0000000000000000 RBX: ffff9c1ec2110ff0 RCX: 0000000000000027
[    2.006884] RDX: ffff9c26505219c8 RSI: 0000000000000001 RDI: ffff9c26505219c0
[    2.006885] RBP: ffff9c1ec3bd6000 R08: 0000000000000000 R09: ffffba0300c5b6a0
[    2.006886] R10: ffffba0300c5b698 R11: 0000000000000003 R12: ffff9c1eca362900
[    2.006887] R13: ffff9c1ed7600800 R14: ffff9c1ed764c000 R15: ffff9c1ec5177000
[    2.006888] FS:  00007594c98ef540(0000) GS:ffff9c2650500000(0000) knlGS:0000000000000000
[    2.006890] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.006891] CR2: 00007594c9837000 CR3: 000000010231a005 CR4: 0000000000f70ef0
[    2.006893] PKRU: 55555554
[    2.006893] Call Trace:
[    2.006896]  <TASK>
[    2.006898]  ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007055]  ? __warn+0x81/0x130
[    2.007061]  ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007189]  ? report_bug+0x171/0x1a0
[    2.007194]  ? console_unlock+0x78/0x120
[    2.007197]  ? handle_bug+0x3c/0x80
[    2.007201]  ? exc_invalid_op+0x17/0x70
[    2.007203]  ? asm_exc_invalid_op+0x1a/0x20
[    2.007206]  ? intel_dp_sink_disable_decompression+0x63/0xf0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007335]  intel_disable_ddi+0x133/0x1f0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007472]  intel_encoders_disable+0x8a/0xb0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007632]  hsw_crtc_disable+0x129/0x140 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007776]  intel_atomic_commit_tail+0x46d/0xf80 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.007920]  intel_atomic_commit+0x2c8/0x310 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008063]  drm_atomic_commit+0x97/0xd0
[    2.008067]  ? __pfx___drm_printfn_info+0x10/0x10
[    2.008070]  intel_initial_commit+0x16a/0x200 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008208]  intel_display_driver_probe+0x26/0x90 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008344]  i915_driver_probe+0x6a9/0xba0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008462]  local_pci_probe+0x42/0xa0
[    2.008467]  pci_device_probe+0xc1/0x260
[    2.008470]  ? sysfs_do_create_link_sd+0x6e/0xe0
[    2.008474]  really_probe+0x19b/0x3e0
[    2.008477]  ? __pfx___driver_attach+0x10/0x10
[    2.008480]  __driver_probe_device+0x78/0x160
[    2.008482]  driver_probe_device+0x1f/0x90
[    2.008483]  __driver_attach+0xd2/0x1c0
[    2.008485]  bus_for_each_dev+0x85/0xd0
[    2.008489]  bus_add_driver+0x116/0x220
[    2.008491]  driver_register+0x59/0x100
[    2.008494]  i915_init+0x22/0xc0 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008615]  ? __pfx_i915_init+0x10/0x10 [i915 a506bac01cd618ad024a7361f3bdf43f3f97d937]
[    2.008730]  do_one_initcall+0x58/0x320
[    2.008734]  do_init_module+0x60/0x240
[    2.008737]  init_module_from_file+0x89/0xe0
[    2.008740]  idempotent_init_module+0x120/0x2b0
[    2.008742]  __x64_sys_finit_module+0x5e/0xb0
[    2.008744]  do_syscall_64+0x86/0x170
[    2.008746]  ? do_syscall_64+0x96/0x170
[    2.008748]  ? do_syscall_64+0x96/0x170
[    2.008749]  ? exc_page_fault+0x7f/0x180
[    2.008752]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[    2.008754] RIP: 0033:0x7594ca3ce88d
[    2.008763] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 14 0d 00 f7 d8 64 89 01 48
[    2.008765] RSP: 002b:00007ffe87d65a48 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    2.008767] RAX: ffffffffffffffda RBX: 00005b52b387adc0 RCX: 00007594ca3ce88d
[    2.008768] RDX: 0000000000000004 RSI: 00007594ca4e3376 RDI: 0000000000000025
[    2.008769] RBP: 00007594ca4e3376 R08: 0000000000000001 R09: fffffffffffffe88
[    2.008770] R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
[    2.008771] R13: 00005b52b3844280 R14: 0000000000000000 R15: 00005b52b387c160
[    2.008772]  </TASK>
[    2.008773] ---[ end trace 0000000000000000 ]---

added Community label

Presumably fixed with commit 7a51a2aa2384 ("drm/i915/dp: Fix DSC state HW readout for SST connectors") @ideak ?

Yes, looks like the same issue, I missed CC:stable, will send it there.

changed the description

marked this issue as a duplicate of #10410 (closed)

closed

marked this issue as related to #10410 (closed)