Kerneloops

Similar reports
Problem #747321
Component
kernel
Last affected version
0:3.10.0-1160.el7
Executable
unknown
First occurrence
2023-06-18
Last occurrence
2023-06-18
Unique reports
1
Quality
-25

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.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
finish_task_switch
vmlinux 0xffffffffab4d49d7
Build id: 3.10.0-1160.el7.x86_64 		0x57
2
__schedule
vmlinux 0xffffffffabb86c8f
Build id: 3.10.0-1160.el7.x86_64 		0x3af
3
schedule
vmlinux 0xffffffffabb87169
Build id: 3.10.0-1160.el7.x86_64 		0x29
4
futex_wait_queue_me
vmlinux 0xffffffffab5121f6
Build id: 3.10.0-1160.el7.x86_64 		0xc6
5
futex_wait
vmlinux 0xffffffffab512f9b
Build id: 3.10.0-1160.el7.x86_64 		0x17b
6
? hrtimer_get_res
vmlinux 0xffffffffab4c9860
Build id: 3.10.0-1160.el7.x86_64 		0x50
7
? futex_wait_queue_me
vmlinux 0xffffffffab5121d4
Build id: 3.10.0-1160.el7.x86_64 		0xa4
8
do_futex
vmlinux 0xffffffffab514d06
Build id: 3.10.0-1160.el7.x86_64 		0x106
9
? sched_clock_cpu
vmlinux 0xffffffffab4de185
Build id: 3.10.0-1160.el7.x86_64 		0x85
10
SyS_futex
vmlinux 0xffffffffab515220
Build id: 3.10.0-1160.el7.x86_64 		0x80
11
system_call_fastpath
vmlinux 0xffffffffabb93f92
Build id: 3.10.0-1160.el7.x86_64 		0x25 
NMI watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [Wt-640:2267]
scsi_transport_spi mptscsih serio_raw mptbase vmxnet3 drm_panel_orientation_quirks floppy dm_mirror dm_region_hash dm_log dm_mod fuse
CPU: 2 PID: 2267 Comm: Wt-640 Kdump: loaded Not tainted 3.10.0-1160.el7.x86_64 #1
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016
task: ffff8ac1b339b180 ti: ffff8ac408054000 task.ti: ffff8ac408054000
RIP: 0010:[<ffffffffab4d49d7>]  [<ffffffffab4d49d7>] finish_task_switch+0x57/0x1c0
RSP: 0018:ffff8ac408057c08  EFLAGS: 00000286
RAX: ffff8ac44c0e1080 RBX: ffff8ac408057bb8 RCX: 00000000c0000102
RDX: ffff8ac408055fd8 RSI: ffff8ac1b339b180 RDI: ffff8ac46f29acc0
RBP: ffff8ac408057c28 R08: ffff8ac408054000 R09: 0000000000000001
R10: 0000000000000002 R11: 0000000000000000 R12: ffff8ac408057bb8
R13: 0000000300000020 R14: 0000000400000008 R15: ffff8ac1bfd18c00
FS:  00007f020541c700(0000) GS:ffff8ac46f280000(0000) knlGS:0000000b69820000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c5ead29e5 CR3: 000000042dd56000 CR4: 00000000003607e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
[<ffffffffabb86c8f>] __schedule+0x3af/0x860
[<ffffffffabb87169>] schedule+0x29/0x70
[<ffffffffab5121f6>] futex_wait_queue_me+0xc6/0x130
[<ffffffffab512f9b>] futex_wait+0x17b/0x280
[<ffffffffab4c9860>] ? hrtimer_get_res+0x50/0x50
[<ffffffffab5121d4>] ? futex_wait_queue_me+0xa4/0x130
[<ffffffffab514d06>] do_futex+0x106/0x5a0
[<ffffffffab4de185>] ? sched_clock_cpu+0x85/0xc0
[<ffffffffab515220>] SyS_futex+0x80/0x190
[<ffffffffabb93f92>] system_call_fastpath+0x25/0x2a
Code: 1f 44 00 00 65 48 8b 34 25 c0 0e 01 00 0f 1f 44 00 00 41 c7 45 28 00 00 00 00 48 89 df c6 07 00 0f 1f 40 00 fb 66 0f 1f 44 00 00 <65> 48 8b 04 25 c0 0e 01 00 48 8b 98 78 01 00 00 48 85 db 74 22