ABRT Analytics - Report #1305838 - kernel in warn_thunk

Kerneloops

Similar reports: Problem #783830
Component: kernel
Last affected version: 0:6.18.16-100.fc42
Executable: unknown
First occurrence: 2025-08-29
Last occurrence: 2026-10-28
Unique reports: 44
Quality: -63

Statistics

Operating system	Unique / Total count
Fedora 42	44 / 56

Operating system	Count
Fedora 42	56

Architecture	Count
x86_64	56


Related packages	Count
kernel-core	56
0:6.17.4-200.fc42	13
0:6.16.4-200.fc42	9
0:6.16.3-200.fc42	7
0:6.17.8-200.fc42	6
0:6.17.7-200.fc42	5
0:6.16.5-200.fc42	4
0:6.17.9-200.fc42	3
0:6.17.13-200.fc42	3
0:6.17.10-200.fc42	2
0:6.17.12-200.fc42	2
0:6.18.16-100.fc42	1
0:6.17.5-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	Line
1	? warn_thunk_thunk	vmlinux	0x16
2	warn_thunk_thunk	vmlinux	0x16
3	? warn_thunk_thunk	vmlinux	0x16
4	? warn_thunk_thunk	vmlinux	0x16
5	? warn_thunk_thunk	vmlinux	0x16
6	warn_thunk_thunk	vmlinux	0x16
7	warn_thunk_thunk	vmlinux	0x16
8	? warn_thunk_thunk	vmlinux	0x16
9	? warn_thunk_thunk	vmlinux	0x16
10	warn_thunk_thunk	vmlinux	0x16
11	? warn_thunk_thunk	vmlinux	0x16
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

WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:5384 init_hybrid_pmu+0x2b4/0x310
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.16.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+0x2b4/0x310
Code: 34 24 4c 89 fa 48 89 df e8 a9 0a ff ff 84 c0 0f 85 48 e4 f0 ff 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f e9 7c d8 24 01 <0f> 0b 48 c7 85 48 18 00 00 00 00 00 00 31 c0 eb dc 48 89 f7 e9 f4
RSP: 0000:ffffc9e800017cf8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000006a RDI: 0000000000000000
RBP: ffff89c433e18ca0 R08: 0000000000000000 R09: 000000000000006a
R10: 0000000000000001 R11: ffffffffb99dac80 R12: 0000000000000000
R13: ffff89c433e18060 R14: ffffffffb99b9ca0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff89c47a45f000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff89c43ffff000 CR3: 0000000058a2c001 CR4: 0000000000370ef0
Call Trace:
 <TASK>
 ? __pfx_x86_pmu_starting_cpu+0x10/0x10
 intel_pmu_cpu_starting+0x250/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+0x17/0x30
 cpuhp_invoke_callback+0x13c/0x440
 ? x86_pmu_prepare_cpu+0x10/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_init_hw_perf_events+0x10/0x10
 init_hw_perf_events+0x265/0x3e0
 do_one_initcall+0x58/0x300
 kernel_init_freeable+0xbd/0x130
 ? __pfx_kernel_init+0x10/0x10
 kernel_init+0x1a/0x140
 ret_from_fork+0x14f/0x180
 ? __pfx_kernel_init+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>