Kerneloops

Similar reports
Problem #722738
Component
kernel
Last affected version
0:6.6.9-200.fc39
Executable
unknown
First occurrence
2023-12-17
Last occurrence
2024-02-08
Unique reports
9
Quality
-53

Graphs

Statistics

Operating system Unique / Total count
Fedora 38 1 / 1
Fedora 39 9 / 9
Operating system Count
Fedora 39 9
Fedora 38 1
Architecture Count
x86_64 10
Related packages Count
kernel-core 10
 0:6.6.8-200.fc39 2
 0:6.6.6-200.fc39 2
 0:6.6.13-200.fc39 2
 0:6.6.7-200.fc39 1
 0:6.6.9-100.fc38 1
 0:6.6.12-200.fc39 1
 0:6.6.9-200.fc39 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.

No reports in the last 20 months.

History

Daily:

Weekly:

Monthly:

No reports in the last 20 days.

No reports in the last 20 weeks.

No reports in the last 20 months.


Backtrace

Frame # Function Binary Source or offset Line
1
? refcount_warn_saturate
vmlinux 0xe5
2
? refcount_warn_saturate
vmlinux 0xe5
3
? refcount_warn_saturate
vmlinux 0xe5
4
? refcount_warn_saturate
vmlinux 0xe5
5
? refcount_warn_saturate
vmlinux 0xe5
6
? refcount_warn_saturate
vmlinux 0xe5
7
? refcount_warn_saturate
vmlinux 0xe5
8
? refcount_warn_saturate
vmlinux 0xe5
9
? refcount_warn_saturate
vmlinux 0xe5
10
? refcount_warn_saturate
vmlinux 0xe5
11
? refcount_warn_saturate
vmlinux 0xe5
12
? refcount_warn_saturate
vmlinux 0xe5
13
? refcount_warn_saturate
vmlinux 0xe5
14
refcount_warn_saturate
vmlinux 0xe5
15
refcount_warn_saturate
vmlinux 0xe5
16
? refcount_warn_saturate
vmlinux 0xe5
17
refcount_warn_saturate
vmlinux 0xe5
18
? refcount_warn_saturate
vmlinux 0xe5
19
refcount_warn_saturate
vmlinux 0xe5 
WARNING: CPU: 2 PID: 116 at crypto/testmgr.c:5936 alg_test+0x516/0x630
Modules linked in:
CPU: 2 PID: 116 Comm: cryptomgr_test Not tainted 6.6.6-200.fc39.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H310CM-HDV/M.2, BIOS P4.30 07/28/2021
RIP: 0010:alg_test+0x516/0x630
Code: ff ff 4c 89 e6 4c 89 e7 41 89 c7 e8 14 dc fe ff e9 37 ff ff ff 44 89 f9 48 89 ea 4c 89 ee 48 c7 c7 f0 c4 94 8b e8 6a 08 9c ff <0f> 0b e9 7d fe ff ff 48 89 c2 48 89 ee 48 c7 c7 28 c4 94 8b 45 89
RSP: 0018:ffffc900004b3e10 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 00000000000000bf RCX: c0000000ffffdfff
RDX: 0000000000000000 RSI: 00000000ffffdfff RDI: 0000000000000001
RBP: ffff88810026f800 R08: 0000000000000000 R09: ffffc900004b3c98
R10: 0000000000000003 R11: ffffffff8c3464e8 R12: 00000000000000c0
R13: ffff88810026f880 R14: 00000000ffffffff R15: 00000000ffffffea
FS:  0000000000000000(0000) GS:ffff88845f080000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd042c17f18 CR3: 0000000258222001 CR4: 00000000003706e0
Call Trace:
 <TASK>
 ? alg_test+0x516/0x630
 ? __warn+0x81/0x130
 ? alg_test+0x516/0x630
 ? report_bug+0x171/0x1a0
 ? console_unlock+0x78/0x120
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? alg_test+0x516/0x630
 ? sched_clock_cpu+0xf/0x190
 ? __smp_call_single_queue+0xad/0x120
 ? ttwu_queue_wakelist+0xef/0x110
 ? __pfx_cryptomgr_test+0x10/0x10
 cryptomgr_test+0x24/0x40
 kthread+0xe5/0x120
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x31/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 </TASK>