Kerneloops

Similar reports
Problem #833123
Component
kernel
Last affected version
0:3.10.0-1160.36.2.el7
Executable
unknown
First occurrence
2023-08-18
Last occurrence
2023-08-18
Unique reports
1
Quality
-31

Statistics

Operating system Unique / Total count
CentOS 7 1 / 1
Operating system Count
CentOS 7 1
Architecture Count
x86_64 1
Related packages Count
kernel 1
 0:3.10.0-1160.36.2.el7 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
? __schedule
vmlinux 0xffffffffb8d88be8
Build id: 3.10.0-1160.36.2.el7.x86_64
0xf8
2
schedule
vmlinux 0xffffffffb8d89199
Build id: 3.10.0-1160.36.2.el7.x86_64
0x29
3
schedule_timeout
vmlinux 0xffffffffb8d86da8
Build id: 3.10.0-1160.36.2.el7.x86_64
0x168
4
? requeue_timers
vmlinux 0xffffffffb86ad890
Build id: 3.10.0-1160.36.2.el7.x86_64
0x170
5
? prepare_to_wait
vmlinux 0xffffffffb86c6a26
Build id: 3.10.0-1160.36.2.el7.x86_64
0x56
6
rcu_gp_kthread
vmlinux 0xffffffffb875b559
Build id: 3.10.0-1160.36.2.el7.x86_64
0x359
7
? wake_up_atomic_t
vmlinux 0xffffffffb86c6f30
Build id: 3.10.0-1160.36.2.el7.x86_64
0x30
8
? rcu_gp_fqs
vmlinux 0xffffffffb875b200
Build id: 3.10.0-1160.36.2.el7.x86_64
0x90
9
kthread
vmlinux 0xffffffffb86c5e41
Build id: 3.10.0-1160.36.2.el7.x86_64
0xd1
10
? insert_kthread_work
vmlinux 0xffffffffb86c5d70
Build id: 3.10.0-1160.36.2.el7.x86_64
0x40
11
ret_from_fork_nospec_begin
vmlinux 0xffffffffb8d95df7
Build id: 3.10.0-1160.36.2.el7.x86_64
0x21
12
? insert_kthread_work
vmlinux 0xffffffffb86c5d70
Build id: 3.10.0-1160.36.2.el7.x86_64
0x40
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gsd-color:6224]
INFO: rcu_sched detected stalls on CPUs/tasks: { 4} (detected by 0, t=67256 jiffies, g=1864982255, c=1864982254, q=775)
Task dump for CPU 4:
rcu_sched       S ffff93c999531080     0     9      2 0x00000000
Call Trace:
[<ffffffffb8d88be8>] ? __schedule+0xf8/0x680
[<ffffffffb8d89199>] schedule+0x29/0x70
[<ffffffffb8d86da8>] schedule_timeout+0x168/0x2d0
[<ffffffffb86ad890>] ? requeue_timers+0x170/0x170
[<ffffffffb86c6a26>] ? prepare_to_wait+0x56/0x90
[<ffffffffb875b559>] rcu_gp_kthread+0x359/0x720
[<ffffffffb86c6f30>] ? wake_up_atomic_t+0x30/0x30
[<ffffffffb875b200>] ? rcu_gp_fqs+0x90/0x90
[<ffffffffb86c5e41>] kthread+0xd1/0xe0
[<ffffffffb86c5d70>] ? insert_kthread_work+0x40/0x40
[<ffffffffb8d95df7>] ret_from_fork_nospec_begin+0x21/0x21
[<ffffffffb86c5d70>] ? insert_kthread_work+0x40/0x40