Kerneloops

Similar reports
Problem #673759
Component
kernel
Last affected version
0:6.15.9-101.fc41
Executable
unknown
First occurrence
2025-07-02
Last occurrence
2025-08-22
Unique reports
7
Quality
-54

Statistics

Operating system Unique / Total count
Fedora 41 7 / 8
Operating system Count
Fedora 41 8
Architecture Count
x86_64 8
Related packages Count
kernel-core 8
 0:6.15.4-100.fc41 3
 0:6.15.9-101.fc41 2
 0:6.15.5-100.fc41 1
 0:6.15.10-100.fc41 1
 0:6.15.7-100.fc41 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.

No reports in the last 20 weeks.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.

No reports in the last 20 weeks.


Backtrace

Frame # Function Binary Source or offset Line
1
? drm_gem_object_release_handle
vmlinux 0x54
2
drm_gem_object_release_handle
vmlinux 0x54
3
? drm_gem_object_release_handle
vmlinux 0x54
4
drm_gem_object_release_handle
vmlinux 0x54
5
drm_gem_object_release_handle
vmlinux 0x54
6
drm_gem_object_release_handle
vmlinux 0x54
7
? drm_gem_object_release_handle
vmlinux 0x54
8
? drm_gem_object_release_handle
vmlinux 0x54
9
drm_gem_object_release_handle
vmlinux 0x54
10
? drm_gem_object_release_handle
vmlinux 0x54
11
? drm_gem_object_release_handle
vmlinux 0x54
12
? drm_gem_object_release_handle
vmlinux 0x54
13
drm_gem_object_release_handle
vmlinux 0x54
14
drm_gem_object_release_handle
vmlinux 0x54
15
? drm_gem_object_release_handle
vmlinux 0x54
16
drm_gem_object_release_handle
vmlinux 0x54
17
? drm_gem_object_release_handle
vmlinux 0x54
18
drm_gem_object_release_handle
vmlinux 0x54
19
drm_gem_object_release_handle
vmlinux 0x54
20
drm_gem_object_release_handle
vmlinux 0x54
21
? drm_gem_object_release_handle
vmlinux 0x54
22
drm_gem_object_release_handle
vmlinux 0x54 
WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:5143 init_hybrid_pmu+0x2cd/0x400
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.15.4-100.fc41.x86_64 #1 PREEMPT(lazy) 
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
RIP: 0010:init_hybrid_pmu+0x2cd/0x400
Code: 41 8b 7e 24 49 83 c6 20 85 ff 75 d0 48 8b 14 24 4c 89 fe 48 89 df e8 92 12 ff ff 84 c0 0f 85 f7 db f1 ff 31 c0 e9 a0 fe ff ff <0f> 0b 48 c7 85 48 14 00 00 00 00 00 00 31 c0 e9 8c fe ff ff 48 89
RSP: 0000:ffffd21780017cd0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 000000000000006b RDI: 0000000000000000
RBP: ffff8b35b3e18cc0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffd21780017d58 R11: ffff8b35bffd4000 R12: 0000000000000000
R13: ffff8b35b3e18060 R14: 0000000000000000 R15: ffff8b3611403000
FS:  0000000000000000(0000) GS:ffff8b3611403000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8b35bffff000 CR3: 0000000083a2e001 CR4: 0000000000f70ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? __kmalloc_cache_node_noprof+0x14b/0x400
 intel_pmu_cpu_starting+0x254/0x3f0
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 x86_pmu_starting_cpu+0x17/0x30
 cpuhp_invoke_callback+0x12e/0x440
 cpuhp_issue_call+0x137/0x1e0
 ? __SCT__x86_pmu_pebs_aliases+0x8/0x8
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 __cpuhp_setup_state_cpuslocked+0xfe/0x2c0
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 __cpuhp_setup_state+0x63/0xf0
 init_hw_perf_events+0x265/0x3e0
 ? __pfx_init_hw_perf_events+0x10/0x10
 do_one_initcall+0x57/0x310
 ? __pfx_kernel_init+0x10/0x10
 kernel_init_freeable+0xbd/0x130
 kernel_init+0x1a/0x140
 ret_from_fork+0x31/0x50
 ? __pfx_kernel_init+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>