Description of problem: Warning generated on boot, with no further graphical output on any connected monitor. Does not appear to matter which outputs on the card are connected during boot (usual set up is 1 DP and 1 DVI connection in use, but have tested both separately with no apparent difference in behaviour). Last working kernel version appears to be 6.3.8-200. Problem persists in 6.4.6-200. Additional info: reporter: libreport-2.17.11 WARNING: CPU: 2 PID: 153 at drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c:497 nvkm_dp_acquire+0x50d/0x750 [nouveau] Modules linked in: dm_crypt nouveau drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel video polyval_clmulni i2c_algo_bit polyval_generic mxm_wmi e1000e ghash_clmulni_intel drm_display_helper sha512_ssse3 ata_generic cec pata_acpi wmi scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip6_tables ip_tables dm_multipath i2c_dev fuse CPU: 2 PID: 153 Comm: kworker/u24:7 Not tainted 6.3.11-200.fc38.x86_64 #1 Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A14 07/01/2016 Workqueue: nvkm-disp gf119_disp_super [nouveau] RIP: 0010:nvkm_dp_acquire+0x50d/0x750 [nouveau] Code: 03 0f 85 0a 02 00 00 a8 04 0f 84 02 02 00 00 83 c2 01 39 fa 75 ca 41 8b 85 28 01 00 00 85 c0 0f 85 44 fc ff ff e9 df fb ff ff <0f> 0b c1 e8 03 45 88 66 62 44 89 fe 4c 89 ef 48 69 c0 cf 0d d6 26 RSP: 0018:ffffb6fd806c7d48 EFLAGS: 00010246 RAX: 0000000000041eb0 RBX: 0000000000087f4b RCX: 0000000000083d60 RDX: ffffffffc0771890 RSI: 0000000000000002 RDI: ffffb6fd806c7cd8 RBP: 00000000ffffffea R08: ffff8cb18fa21a00 R09: 0000000000005bee R10: 0000000000000008 R11: ffffb6fd806c7dc8 R12: 0000000000000002 R13: ffff8cb18fa35000 R14: ffff8cb18b0c1b80 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8cb91fa80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f4e367e8d70 CR3: 0000000271022006 CR4: 00000000001706e0 Call Trace: <TASK> ? nvkm_dp_acquire+0x50d/0x750 [nouveau] ? __warn+0x81/0x130 ? nvkm_dp_acquire+0x50d/0x750 [nouveau] ? report_bug+0x171/0x1a0 ? handle_bug+0x3c/0x80 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? __pfx_init_done+0x10/0x10 [nouveau] ? nvkm_dp_acquire+0x50d/0x750 [nouveau] ? nvkm_dp_acquire+0x2c5/0x750 [nouveau] nv50_disp_super_2_2+0x6d/0x430 [nouveau] gf119_disp_super+0x258/0x2e0 [nouveau] process_one_work+0x1c7/0x3d0 worker_thread+0x51/0x390 ? __pfx_worker_thread+0x10/0x10 kthread+0xde/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK> Potential duplicate: bug 1580139
Created attachment 1980837 [details] File: dmesg
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.