Kerneloops

Similar reports
Problem #796171
Component
kernel
Last affected version
0:6.10.9-200.fc40
Executable
unknown
First occurrence
2024-08-27
Last occurrence
2025-12-27
Unique reports
27
Quality
-76

Statistics

Operating system Unique / Total count
Fedora 40 27 / 29
Operating system Count
Fedora 40 29
Architecture Count
x86_64 29
Related packages Count
kernel-core 29
 0:6.10.11-200.fc40 9
 0:6.10.6-200.fc40 5
 0:6.10.7-200.fc40 5
 0:6.10.9-200.fc40 4
 0:6.10.10-200.fc40 2
 0:6.10.8-200.fc40 2
 0:6.10.12-200.fc40 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:

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
? follow_pte
vmlinux 0x1f0
2
? follow_pte
vmlinux 0x1f0
3
? follow_pte
vmlinux 0x1f0
4
? follow_pte
vmlinux 0x1f0
5
? follow_pte
vmlinux 0x1f0
6
? follow_pte
vmlinux 0x1f0
7
? follow_pte
vmlinux 0x1f0
8
? follow_pte
vmlinux 0x1f0
9
? follow_pte
vmlinux 0x1f0
10
? follow_pte
vmlinux 0x1f0
11
follow_pte
vmlinux 0x1f0
12
follow_pte
vmlinux 0x1f0
13
follow_pte
vmlinux 0x1f0
14
? follow_pte
vmlinux 0x1f0
15
? follow_pte
vmlinux 0x1f0
16
follow_pte
vmlinux 0x1f0
17
? follow_pte
vmlinux 0x1f0
18
? follow_pte
vmlinux 0x1f0
19
follow_pte
vmlinux 0x1f0
20
follow_pte
vmlinux 0x1f0
21
? follow_pte
vmlinux 0x1f0
22
follow_pte
vmlinux 0x1f0
23
? follow_pte
vmlinux 0x1f0
24
follow_pte
vmlinux 0x1f0
25
? follow_pte
vmlinux 0x1f0
26
follow_pte
vmlinux 0x1f0
27
follow_pte
vmlinux 0x1f0
28
? follow_pte
vmlinux 0x1f0
29
follow_pte
vmlinux 0x1f0 
WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:4813 intel_pmu_cpu_starting+0x4ac/0x740
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.6-200.fc40.x86_64 #1
Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
RIP: 0010:intel_pmu_cpu_starting+0x4ac/0x740
Code: 00 00 00 bf d9 01 00 00 74 36 e8 6f 21 95 00 e9 2f fc ff ff 48 8b 05 03 a5 80 02 48 85 c0 74 0a ff d0 0f 1f 00 e9 03 fe ff ff <0f> 0b 48 8b 04 24 48 c7 80 48 14 00 00 00 00 00 00 e9 9c fd ff ff
RSP: 0000:ffffb70200017c68 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 000000000001a220 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000006a RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffb70200017cb0 R11: 0000000000000246 R12: ffff8d76abe1a220
R13: ffff8d76abe00000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8d76abe00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8d766f803000 CR3: 00000003ee428001 CR4: 0000000000f70ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? intel_pmu_cpu_starting+0x4ac/0x740
 ? __warn.cold+0x8e/0xe8
 ? intel_pmu_cpu_starting+0x4ac/0x740
 ? report_bug+0xff/0x140
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? intel_pmu_cpu_starting+0x4ac/0x740
 ? intel_pmu_cpu_starting+0x2a7/0x740
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 x86_pmu_starting_cpu+0x17/0x30
 cpuhp_invoke_callback+0x12e/0x430
 cpuhp_issue_call+0x137/0x1e0
 ? x86_pmu_filter+0x27/0x50
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 __cpuhp_setup_state_cpuslocked+0xf1/0x2e0
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 ? __pfx_x86_pmu_dying_cpu+0x10/0x10
 __cpuhp_setup_state+0x63/0xf0
 init_hw_perf_events+0x4ba/0x640
 ? __pfx_init_hw_perf_events+0x10/0x10
 do_one_initcall+0x58/0x310
 ? __pfx_kernel_init+0x10/0x10
 kernel_init_freeable+0x128/0x310
 ? __pfx_kernel_init+0x10/0x10
 kernel_init+0x1a/0x140
 ret_from_fork+0x31/0x50
 ? __pfx_kernel_init+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>