Kerneloops

Similar reports
Problem #763308
Component
kernel
Last affected version
0:6.15.6-200.fc42
Executable
unknown
First occurrence
2025-06-24
Last occurrence
2025-07-17
Unique reports
16
Quality
-72

Statistics

Operating system Unique / Total count
Fedora 42 16 / 19
Operating system Count
Fedora 42 19
Architecture Count
x86_64 19
Related packages Count
kernel-core 19
 0:6.15.4-200.fc42 9
 0:6.15.3-200.fc42 7
 0:6.15.5-200.fc42 2
 0:6.15.6-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:

History

Daily:

Weekly:

Monthly:


Backtrace

Frame # Function Binary Source or offset Line
1
? security_file_permission
vmlinux 0x50
2
? security_file_permission
vmlinux 0x50
3
security_file_permission
vmlinux 0x50
4
? security_file_permission
vmlinux 0x50
5
? security_file_permission
vmlinux 0x50
6
? security_file_permission
vmlinux 0x50
7
security_file_permission
vmlinux 0x50
8
security_file_permission
vmlinux 0x50
9
? security_file_permission
vmlinux 0x50
10
? security_file_permission
vmlinux 0x50
11
security_file_permission
vmlinux 0x50
12
? security_file_permission
vmlinux 0x50
13
security_file_permission
vmlinux 0x50
14
? security_file_permission
vmlinux 0x50
15
? security_file_permission
vmlinux 0x50
16
security_file_permission
vmlinux 0x50
17
? security_file_permission
vmlinux 0x50
18
? security_file_permission
vmlinux 0x50
19
? security_file_permission
vmlinux 0x50
20
security_file_permission
vmlinux 0x50
21
? security_file_permission
vmlinux 0x50
22
security_file_permission
vmlinux 0x50
23
? security_file_permission
vmlinux 0x50
24
security_file_permission
vmlinux 0x50
25
security_file_permission
vmlinux 0x50
26
security_file_permission
vmlinux 0x50
27
? security_file_permission
vmlinux 0x50
28
security_file_permission
vmlinux 0x50 
WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:5143 init_hybrid_pmu+0x2c6/0x400
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.15.3-200.fc42.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+0x2c6/0x400
Code: 41 8b 7e 24 49 83 c6 20 85 ff 75 d0 48 8b 34 24 4c 89 fa 48 89 df e8 19 0d ff ff 84 c0 0f 85 5d f6 f0 ff 31 c0 e9 a7 fe ff ff <0f> 0b 48 c7 85 48 14 00 00 00 00 00 00 31 c0 e9 93 fe ff ff 48 89
RSP: 0000:ffffce4240017cd8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000006b RDI: 0000000000000000
RBP: ffff8a0673e18cc0 R08: 0000000000000000 R09: 000000000000006b
R10: 0000000000000001 R11: ffffffffb8fc8c80 R12: 0000000000000000
R13: ffff8a0673e18060 R14: ffffffffb8fa7cc0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8a06bae71000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8a0573e02000 CR3: 0000000132a2e001 CR4: 0000000000370ef0
Call Trace:
 <TASK>
 ? __kmalloc_cache_node_noprof+0x14b/0x400
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 intel_pmu_cpu_starting+0x253/0x420
 ? __pfx_x86_pmu_dead_cpu+0x10/0x10
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 x86_pmu_starting_cpu+0x1a/0x30
 cpuhp_invoke_callback+0x13c/0x440
 ? x86_pmu_prepare_cpu+0x30/0x90
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 cpuhp_issue_call+0x12f/0x210
 ? arch_static_call_transform+0x5b/0xb0
 __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+0x58/0x300
 ? __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>