Kerneloops

Similar reports
Problem #801495
Component
xorg-x11-drv-nouveau
Last affected version
0:6.17.9-200.fc42
Executable
unknown
First occurrence
2025-10-25
Last occurrence
2025-12-22
Unique reports
2
Quality
-68

Statistics

Operating system Unique / Total count
Fedora 42 2 / 2
Operating system Count
Fedora 42 2
Architecture Count
x86_64 2
Related packages Count
kernel-core 2
 0:6.17.4-200.fc42 1
 0:6.17.9-200.fc42 1

Packages names with count less than the total count of reports are most probably not the cause of the problem.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.


Backtrace

Frame # Function Binary Source or offset Line
1
? nouveau_drm_ioctl
nouveau 0x58
2
nouveau_drm_ioctl
nouveau 0x58
3
? warn_thunk_thunk
vmlinux 0x16
4
? warn_thunk_thunk
vmlinux 0x16
5
nouveau_drm_ioctl
nouveau 0x58
6
nouveau_drm_ioctl
nouveau 0x58
7
nouveau_drm_ioctl
nouveau 0x58
8
nouveau_drm_ioctl
nouveau 0x58
9
nouveau_drm_ioctl
nouveau 0x58
10
nouveau_drm_ioctl
nouveau 0x58
11
nouveau_drm_ioctl
nouveau 0x58
12
warn_thunk_thunk
vmlinux 0x16
13
? warn_thunk_thunk
vmlinux 0x16
14
warn_thunk_thunk
vmlinux 0x16
15
warn_thunk_thunk
vmlinux 0x16
16
warn_thunk_thunk
vmlinux 0x16
17
warn_thunk_thunk
vmlinux 0x16
18
warn_thunk_thunk
vmlinux 0x16
19
warn_thunk_thunk
vmlinux 0x16
20
warn_thunk_thunk
vmlinux 0x16
21
warn_thunk_thunk
vmlinux 0x16
22
warn_thunk_thunk
vmlinux 0x16
23
warn_thunk_thunk
vmlinux 0x16
24
? warn_thunk_thunk
vmlinux 0x16
25
warn_thunk_thunk
vmlinux 0x16
26
? warn_thunk_thunk
vmlinux 0x16
27
? warn_thunk_thunk
vmlinux 0x16
28
warn_thunk_thunk
vmlinux 0x16
29
? warn_thunk_thunk
vmlinux 0x16
30
warn_thunk_thunk
vmlinux 0x16
WARNING: CPU: 2 PID: 752 at drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/disp.c:1131 r535_dp_release+0xa5/0xc0 [nouveau]
Modules linked in: nouveau raid0 drm_ttm_helper ttm gpu_sched i2c_algo_bit drm_gpuvm drm_exec drm_display_helper mxm_wmi polyval_clmulni ghash_clmulni_intel cec video wmi intel_oc_wdt pinctrl_cannonlake i2c_dev fuse
CPU: 2 UID: 0 PID: 752 Comm: kworker/2:2 Not tainted 6.17.4-200.fc42.x86_64 #1 PREEMPT(lazy) 
Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER/Z390 AORUS MASTER-CF, BIOS F10 10/15/2019
Workqueue: events output_poll_execute
RIP: 0010:r535_dp_release+0xa5/0xc0 [nouveau]
Code: ff ff ff 48 d3 c0 21 82 18 02 00 00 48 8b 43 68 48 c7 40 50 00 00 00 00 48 c7 43 68 00 00 00 00 48 83 c4 08 5b e9 cb a2 c8 c4 <0f> 0b 41 b8 06 00 00 00 c6 87 21 01 00 00 06 eb 93 66 2e 0f 1f 84
RSP: 0018:ffffd3ac407d79a0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8a8a94089800 RCX: ffffd3ac407d7a88
RDX: 0000000000000000 RSI: 0000000000000012 RDI: ffff8a8a94089800
RBP: ffff8a8a94089928 R08: 0000000000000000 R09: 0000000000000286
R10: 0000000000000000 R11: ffff8a8a94089928 R12: 0000000000000012
R13: ffff8a8a833bf310 R14: 0000000000000020 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8a9a76545000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7a15200010 CR3: 000000083662e001 CR4: 00000000003706f0
Call Trace:
 <TASK>
 ? nvkm_ioctl+0xd2/0x1e0 [nouveau]
 nvkm_uoutp_mthd_acquired+0x2d1/0x350 [nouveau]
 ? __sysvec_error_interrupt+0x184/0x190
 ? clockevents_program_event+0xa8/0x120
 nvkm_uoutp_mthd+0x300/0x520 [nouveau]
 nvkm_ioctl+0xd2/0x1e0 [nouveau]
 nvif_object_mthd+0xcd/0x1b0 [nouveau]
 nvif_outp_release+0x1b/0x80 [nouveau]
 nv50_disp_atomic_commit_core+0x55e/0x5c0 [nouveau]
 nv50_disp_atomic_commit_tail+0x6d5/0x780 [nouveau]
 nv50_disp_atomic_commit.part.0+0x174/0x1a0 [nouveau]
 drm_atomic_commit+0xae/0xe0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_client_modeset_commit_atomic+0x1ec/0x230
 drm_client_modeset_commit_locked+0x58/0x160
 drm_client_modeset_commit+0x25/0x40
 __drm_fb_helper_restore_fbdev_mode_unlocked+0x91/0xd0
 drm_fb_helper_hotplug_event+0xed/0x110
 drm_client_hotplug+0x3d/0x90
 drm_client_dev_hotplug+0x81/0xa0
 output_poll_execute+0x23c/0x290
 process_one_work+0x192/0x350
 worker_thread+0x25a/0x3a0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xf9/0x240
 ? __pfx_kthread+0x10/0x10
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0xf4/0x110
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>