Kerneloops

Similar reports
Problem #795750
Component
kernel
Last affected version
0:3.10.0-693.el7
Executable
unknown
First occurrence
2021-11-21
Last occurrence
2022-01-08
Unique reports
2
Quality
-25

Statistics

Operating system Unique / Total count
CentOS 7 2 / 2
Operating system Count
CentOS 7 2
Architecture Count
x86_64 2
Related packages Count
kernel 2
 0:3.10.0-693.el7 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.

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
sched_show_task
vmlinux 0xffffffff810c3a98
Build id: 3.10.0-693.el7.x86_64
0xa8
2
dump_cpu_task
vmlinux 0xffffffff810c7429
Build id: 3.10.0-693.el7.x86_64
0x39
3
rcu_dump_cpu_stacks
vmlinux 0xffffffff81137b10
Build id: 3.10.0-693.el7.x86_64
0x90
4
rcu_check_callbacks
vmlinux 0xffffffff8113b132
Build id: 3.10.0-693.el7.x86_64
0x442
5
? tick_sched_do_timer
vmlinux 0xffffffff810f2ff0
Build id: 3.10.0-693.el7.x86_64
0x50
6
update_process_times
vmlinux 0xffffffff8109a2f6
Build id: 3.10.0-693.el7.x86_64
0x46
7
tick_sched_handle
vmlinux 0xffffffff810f2df0
Build id: 3.10.0-693.el7.x86_64
0x30
8
tick_sched_timer
vmlinux 0xffffffff810f3029
Build id: 3.10.0-693.el7.x86_64
0x39
9
__hrtimer_run_queues
vmlinux 0xffffffff810b4ae4
Build id: 3.10.0-693.el7.x86_64
0xd4
10
hrtimer_interrupt
vmlinux 0xffffffff810b507f
Build id: 3.10.0-693.el7.x86_64
0xaf
11
local_apic_timer_interrupt
vmlinux 0xffffffff81053895
Build id: 3.10.0-693.el7.x86_64
0x35
12
smp_apic_timer_interrupt
vmlinux 0xffffffff816b76bd
Build id: 3.10.0-693.el7.x86_64
0x3d
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 21s! [flux_app:17275]
INFO: rcu_sched self-detected stall on CPU { 5}  (t=122214 jiffies g=896438526 c=896438525 q=1952)
Task dump for CPU 5:
xfsaild/dm-0    R  running task        0   520      2 0x00000008
ffff880434bd6eb0 00000000a1738cbc ffff880237d438e0 ffffffff810c3a98
0000000000000005 ffffffff81a550c0 ffff880237d438f8 ffffffff810c7429
0000000000000006 ffff880237d43928 ffffffff81137b10 ffff880237d50260
Call Trace:
<IRQ>  [<ffffffff810c3a98>] sched_show_task+0xa8/0x110
[<ffffffff810c7429>] dump_cpu_task+0x39/0x70
[<ffffffff81137b10>] rcu_dump_cpu_stacks+0x90/0xd0
[<ffffffff8113b132>] rcu_check_callbacks+0x442/0x730
[<ffffffff810f2ff0>] ? tick_sched_do_timer+0x50/0x50
[<ffffffff8109a2f6>] update_process_times+0x46/0x80
[<ffffffff810f2df0>] tick_sched_handle+0x30/0x70
[<ffffffff810f3029>] tick_sched_timer+0x39/0x80
[<ffffffff810b4ae4>] __hrtimer_run_queues+0xd4/0x260
[<ffffffff810b507f>] hrtimer_interrupt+0xaf/0x1d0
[<ffffffff81053895>] local_apic_timer_interrupt+0x35/0x60
[<ffffffff816b76bd>] smp_apic_timer_interrupt+0x3d/0x50