Kerneloops

Similar reports
Problem #817033
Component
kernel
Last affected version
0:6.14.9-300.fc42
Executable
unknown
First occurrence
2025-05-27
Last occurrence
2026-02-12
Unique reports
53
Quality
-66

Statistics

Operating system Unique / Total count
Fedora 42 53 / 58
Operating system Count
Fedora 42 58
Architecture Count
x86_64 58
Related packages Count
kernel-core 58
 0:6.14.9-300.fc42 28
 0:6.14.11-300.fc42 17
 0:6.14.8-300.fc42 7
 0:6.14.6-300.fc42 4
 0:6.14.5-300.fc42 2

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

History

Daily:

Weekly:

Monthly:

History

Daily:

Weekly:

Monthly:


Backtrace

Frame # Function Binary Source or offset Line
1
? drm_helper_probe_detect_ctx
vmlinux 0x97
2
drm_helper_probe_detect_ctx
vmlinux 0x97
3
? drm_helper_probe_detect_ctx
vmlinux 0x97
4
? drm_helper_probe_detect_ctx
vmlinux 0x97
5
drm_helper_probe_detect_ctx
vmlinux 0x97
6
drm_helper_probe_detect_ctx
vmlinux 0x97
7
? drm_helper_probe_detect_ctx
vmlinux 0x97
8
? drm_helper_probe_detect_ctx
vmlinux 0x97
9
drm_helper_probe_detect_ctx
vmlinux 0x97
10
? drm_helper_probe_detect_ctx
vmlinux 0x97
11
drm_helper_probe_detect_ctx
vmlinux 0x97
12
? drm_helper_probe_detect_ctx
vmlinux 0x97
13
? drm_helper_probe_detect_ctx
vmlinux 0x97
14
drm_helper_probe_detect_ctx
vmlinux 0x97
15
? drm_helper_probe_detect_ctx
vmlinux 0x97
16
? drm_helper_probe_detect_ctx
vmlinux 0x97
17
? drm_helper_probe_detect_ctx
vmlinux 0x97
18
drm_helper_probe_detect_ctx
vmlinux 0x97
19
? drm_helper_probe_detect_ctx
vmlinux 0x97
20
drm_helper_probe_detect_ctx
vmlinux 0x97
21
? drm_helper_probe_detect_ctx
vmlinux 0x97
22
drm_helper_probe_detect_ctx
vmlinux 0x97
23
drm_helper_probe_detect_ctx
vmlinux 0x97
24
drm_helper_probe_detect_ctx
vmlinux 0x97
25
? drm_helper_probe_detect_ctx
vmlinux 0x97
26
drm_helper_probe_detect_ctx
vmlinux 0x97 
WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:5088 init_hybrid_pmu+0xe4/0x3e0
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.6-300.fc42.x86_64 #1
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
RIP: 0010:init_hybrid_pmu+0xe4/0x3e0
Code: 41 83 fe 01 74 53 e8 3b ee 04 00 83 f8 02 75 06 41 83 fe 04 74 39 8b 05 72 18 96 02 83 c5 01 48 81 c3 60 10 00 00 39 e8 7f ae <0f> 0b 48 8b 04 24 48 c7 80 48 14 00 00 00 00 00 00 31 c0 eb 5f e8
RSP: 0000:ffffaf7980017cd0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8b5177e00000
RDX: 0000000000000000 RSI: 000000000000006c RDI: 0000000000000000
RBP: 0000000000019020 R08: 0000000000000000 R09: 000000000000006c
R10: 0000000000000001 R11: 000000000003f300 R12: 000000000001a240
R13: 0000000000000000 R14: ffff8b5177e1a240 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8b5177e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8b517ffff000 CR3: 000000007382c001 CR4: 0000000000370ef0
Call Trace:
 <TASK>
 ? __kmalloc_cache_node_noprof+0x14c/0x400
 intel_pmu_cpu_starting+0x265/0x450
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 x86_pmu_starting_cpu+0x17/0x30
 cpuhp_invoke_callback+0x139/0x440
 ? x86_pmu_prepare_cpu+0x90/0x90
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 cpuhp_issue_call+0x12f/0x210
 ? arch_static_call_transform+0x86/0xa0
 __cpuhp_setup_state_cpuslocked+0x101/0x2f0
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 __cpuhp_setup_state+0x67/0x100
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 ? __pfx_kernel_init+0x10/0x10
 ? __pfx_init_hw_perf_events+0x10/0x10
 init_hw_perf_events+0x265/0x3e0
 ? __pfx_kernel_init+0x10/0x10
 do_one_initcall+0x59/0x310
 ? __pfx_kernel_init+0x10/0x10
 kernel_init_freeable+0xc2/0x130
 kernel_init+0x1a/0x140
 ret_from_fork+0x31/0x50
 ? __pfx_kernel_init+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>