Description of problem: This error occours everytime at some point during startup. I am connecting 2 displays and multiple perifpherials such as mouse, keyboard, and webcam via belkin thunderbolt 3 hub. Possibly realted to the hub but not certain. Additional info: reporter: libreport-2.17.4 WARNING: CPU: 3 PID: 43 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x374/0x3b0 [i915] Modules linked in: uas usb_storage i915 nvme crct10dif_pclmul rtsx_pci_sdmmc crc32_pclmul crc32c_intel polyval_clmulni drm_buddy nvme_core polyval_generic mmc_core drm_display_helper cec r8152 hid_alps ghash_clmulni_intel mii sha512_ssse3 e1000e serio_raw rtsx_pci nvme_common ttm i2c_hid_acpi i2c_hid video wmi hid_multitouch ip6_tables ip_tables fuse CPU: 3 PID: 43 Comm: kworker/3:1 Not tainted 6.1.9-100.fc36.x86_64 #1 Hardware name: Dell Inc. Latitude 7280/0TVCVW, BIOS 1.29.0 11/17/2022 Workqueue: events output_poll_execute RIP: 0010:intel_modeset_verify_crtc+0x374/0x3b0 [i915] Code: 1c 00 00 0f b6 f0 48 c7 c7 28 10 9f c0 75 33 e8 d2 bb ff ea e9 71 fd ff ff e8 0e c0 46 eb 0f 0b e9 fb fd ff ff e8 02 c0 46 eb <0f> 0b e9 c7 fe ff ff e8 f6 bf 46 eb 0f 0b 0f b6 44 24 17 e9 b1 fd RSP: 0000:ffffc06d401d3ba8 EFLAGS: 00010286 RAX: 0000000000000019 RBX: ffff9e254c6b02a0 RCX: 0000000000000000 RDX: 0000000000000001 RSI: ffffffffac74c47b RDI: 00000000ffffffff RBP: ffff9e2549d72000 R08: 0000000000000000 R09: ffffc06d401d3a48 R10: 0000000000000003 R11: ffffffffad1465a8 R12: ffff9e2549f3e000 R13: ffff9e254a040000 R14: ffff9e254c6b02a8 R15: ffff9e254a040000 FS: 0000000000000000(0000) GS:ffff9e2c9e580000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000056390e828104 CR3: 00000001fd010006 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> intel_atomic_commit_tail+0x926/0xe20 [i915] intel_atomic_commit+0x358/0x3a0 [i915] drm_atomic_commit+0x64/0xd0 ? drm_plane_get_damage_clips.cold+0x1c/0x1c drm_client_modeset_commit_atomic+0x1e8/0x220 drm_client_modeset_commit_locked+0x56/0x160 drm_client_modeset_commit+0x21/0x40 drm_fb_helper_set_par+0x9e/0xe0 drm_fb_helper_hotplug_event+0x9f/0xe0 output_poll_execute+0x9c/0x200 process_one_work+0x1c4/0x380 worker_thread+0x4d/0x380 ? rescuer_thread+0x380/0x380 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>
Created attachment 1942208 [details] File: dmesg
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.