Kerneloops

Similar reports
Problem #575128
Component
kernel
Last affected version
0:3.10.0-957.21.3.el7
Executable
unknown
First occurrence
2024-03-08
Last occurrence
2024-03-08
Unique reports
1
Quality
-46

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-957.21.3.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
sched_show_task
vmlinux 0xffffffffb9cd6138
Build id: 3.10.0-957.21.3.el7.x86_64
0xa8
2
rcu_check_callbacks
vmlinux 0xffffffffb9d5653e
Build id: 3.10.0-957.21.3.el7.x86_64
0x72e
3
? tick_sched_do_timer
vmlinux 0xffffffffb9d0b080
Build id: 3.10.0-957.21.3.el7.x86_64
0x50
4
update_process_times
vmlinux 0xffffffffb9cab2a6
Build id: 3.10.0-957.21.3.el7.x86_64
0x46
5
tick_sched_handle
vmlinux 0xffffffffb9d0adf0
Build id: 3.10.0-957.21.3.el7.x86_64
0x30
6
tick_sched_timer
vmlinux 0xffffffffb9d0b0b9
Build id: 3.10.0-957.21.3.el7.x86_64
0x39
7
__hrtimer_run_queues
vmlinux 0xffffffffb9cc6103
Build id: 3.10.0-957.21.3.el7.x86_64
0xf3
8
hrtimer_interrupt
vmlinux 0xffffffffb9cc668f
Build id: 3.10.0-957.21.3.el7.x86_64
0xaf
9
local_apic_timer_interrupt
vmlinux 0xffffffffb9c5a58b
Build id: 3.10.0-957.21.3.el7.x86_64
0x3b
10
smp_apic_timer_interrupt
vmlinux 0xffffffffba37a6e3
Build id: 3.10.0-957.21.3.el7.x86_64
0x43
11
apic_timer_interrupt
vmlinux 0xffffffffba376df2
Build id: 3.10.0-957.21.3.el7.x86_64
0x162
12
? mpt_fault_reset_work
mptbase 0xffffffffc039ffa9
Build id: 3.10.0-957.21.3.el7.x86_64
0xc9
13
? try_to_wake_up
vmlinux 0xffffffffb9cd68a0
Build id: 3.10.0-957.21.3.el7.x86_64
0x190
14
process_one_work
vmlinux 0xffffffffb9cb9ebf
Build id: 3.10.0-957.21.3.el7.x86_64
0x17f
15
worker_thread
vmlinux 0xffffffffb9cbaf56
Build id: 3.10.0-957.21.3.el7.x86_64
0x126
16
? manage_workers.isra.25
vmlinux 0xffffffffb9cbae30
Build id: 3.10.0-957.21.3.el7.x86_64
0x2a0
17
kthread
vmlinux 0xffffffffb9cc1da1
Build id: 3.10.0-957.21.3.el7.x86_64
0xd1
18
? insert_kthread_work
vmlinux 0xffffffffb9cc1cd0
Build id: 3.10.0-957.21.3.el7.x86_64
0x40
19
ret_from_fork_nospec_begin
vmlinux 0xffffffffba375c37
Build id: 3.10.0-957.21.3.el7.x86_64
0x21
20
? insert_kthread_work
vmlinux 0xffffffffb9cc1cd0
Build id: 3.10.0-957.21.3.el7.x86_64
0x40
NMI watchdog: BUG: soft lockup - CPU#3 stuck for 113s! [kworker/u8:0:24583]
INFO: rcu_sched detected stalls on CPUs/tasks: {} (detected by 2, t=141647 jiffies, g=184006591, c=184006590, q=369)
All QSes seen, last rcu_sched kthread activity 141647 (7832928457-7832786810), jiffies_till_next_fqs=3
kworker/u8:2    R  running task        0 12770      2 0x00000080
Workqueue: mpt_poll_0 mpt_fault_reset_work [mptbase]
Call Trace:
<IRQ>  [<ffffffffb9cd6138>] sched_show_task+0xa8/0x110
[<ffffffffb9d5653e>] rcu_check_callbacks+0x72e/0x730
[<ffffffffb9d0b080>] ? tick_sched_do_timer+0x50/0x50
[<ffffffffb9cab2a6>] update_process_times+0x46/0x80
[<ffffffffb9d0adf0>] tick_sched_handle+0x30/0x70
[<ffffffffb9d0b0b9>] tick_sched_timer+0x39/0x80
[<ffffffffb9cc6103>] __hrtimer_run_queues+0xf3/0x270
[<ffffffffb9cc668f>] hrtimer_interrupt+0xaf/0x1d0
[<ffffffffb9c5a58b>] local_apic_timer_interrupt+0x3b/0x60
[<ffffffffba37a6e3>] smp_apic_timer_interrupt+0x43/0x60
[<ffffffffba376df2>] apic_timer_interrupt+0x162/0x170
<EOI>  [<ffffffffc039ffa9>] ? mpt_fault_reset_work+0xc9/0x47a [mptbase]
[<ffffffffb9cd68a0>] ? try_to_wake_up+0x190/0x390
[<ffffffffb9cb9ebf>] process_one_work+0x17f/0x440
[<ffffffffb9cbaf56>] worker_thread+0x126/0x3c0
[<ffffffffb9cbae30>] ? manage_workers.isra.25+0x2a0/0x2a0
[<ffffffffb9cc1da1>] kthread+0xd1/0xe0
[<ffffffffb9cc1cd0>] ? insert_kthread_work+0x40/0x40
[<ffffffffba375c37>] ret_from_fork_nospec_begin+0x21/0x21
[<ffffffffb9cc1cd0>] ? insert_kthread_work+0x40/0x40