Kernel panic - not syncing: softlockup: hung tasks

Latest response

OS is CentOS 7.2 minimal, and the kernel version is 4.9.90.

The following kernel panic has occurred multiple times, and the content of all these vmcores are the same. The attached is the corresponding vmcore-dmesg.txt.

[260152.258219] Kernel panic - not syncing: softlockup: hung tasks
[260152.258266] CPU: 29 PID: 25772 Comm: kworker/29:33 Tainted: G           OEL  4.9.90-29.el7.x86_64 #1
[260152.258329] Hardware name: Dell Inc. PowerEdge C6320/082F9M, BIOS 2.4.2 01/09/2017
[260152.258416] Workqueue: xfs-buf/sdb1 xfs_buf_ioend_work [xfs]
[260152.258460]  ffff8be19f383e70 ffffffff8f3fdb39 0000000000000000 ffffffff8fcd5c9e
[260152.258520]  ffff8be19f383ee8 ffffffff8f1c26a5 0000000000000008 ffff8be19f383ef8
[260152.258581]  ffff8be19f383e98 0000000000000762 0000000000000000 0000000000000000
[260152.258641] Call Trace:
[260152.258663]  <IRQ>
[260152.258686]  [<ffffffff8f3fdb39>] dump_stack+0x63/0x8a
[260152.258724]  [<ffffffff8f1c26a5>] panic+0xdb/0x229
[260152.258766]  [<ffffffff8f167cd0>] watchdog_timer_fn+0x210/0x220
[260152.258811]  [<ffffffff8f167ac0>] ? watchdog_park_threads+0x70/0x70
[260152.258858]  [<ffffffff8f11b6f4>] __hrtimer_run_queues+0xe4/0x250
[260152.258918]  [<ffffffff8f11bb98>] hrtimer_interrupt+0xa8/0x1a0
[260152.258967]  [<ffffffff8f051085>] local_apic_timer_interrupt+0x35/0x60
[260152.259015]  [<ffffffff8f88e3dd>] smp_apic_timer_interrupt+0x3d/0x50
[260152.259062]  [<ffffffff8f88cb80>] apic_timer_interrupt+0xa0/0xb0
[260152.259105]  <EOI>
[260152.259128]  [<ffffffff8f0f688b>] ? native_queued_spin_lock_slowpath+0x11b/0x1a0
[260152.259180]  [<ffffffff8f1c2e1a>] queued_spin_lock_slowpath+0xb/0xf
[260152.259227]  [<ffffffff8f88a8b0>] _raw_spin_lock+0x20/0x30
[260152.259301]  [<ffffffffc0502a42>] xfs_buf_rele+0x52/0x280 [xfs]
[260152.259387]  [<ffffffffc052af15>] ? xfs_buf_iodone_callbacks+0xd5/0x2a0 [xfs]
[260152.259473]  [<ffffffffc050360b>] xfs_buf_ioend+0x12b/0x1e0 [xfs]
[260152.259555]  [<ffffffffc052af15>] xfs_buf_iodone_callbacks+0xd5/0x2a0 [xfs]
[260152.259639]  [<ffffffffc050357d>] xfs_buf_ioend+0x9d/0x1e0 [xfs]
[260152.259714]  [<ffffffffc05036d5>] xfs_buf_ioend_work+0x15/0x20 [xfs]
[260152.259762]  [<ffffffff8f0c2153>] process_one_work+0x153/0x3f0
[260152.259812]  [<ffffffff8f0c2e8b>] worker_thread+0x12b/0x4c0
[260152.259868]  [<ffffffff8f0c2d60>] ? max_active_store+0x60/0x60
[260152.259911]  [<ffffffff8f0c2d60>] ? max_active_store+0x60/0x60
[260152.259967]  [<ffffffff8f0c8307>] kthread+0xd7/0xf0
[260152.260005]  [<ffffffff8f0c8230>] ? kthread_park+0x60/0x60
[260152.260048]  [<ffffffff8f0039a3>] ? do_syscall_64+0x73/0x180
[260152.260091]  [<ffffffff8f88adb7>] ret_from_fork+0x57/0x70

Attachments

Responses

Err, you are posting this in "Red Hat Enterprise Linux for ARM 64 ".

Your OS is CentOS 7.2. Your kernel is 4.9.90. Your hardware is PowerEdge C6320 (Xeon, not ARM)

Nevertheless, I hope you can get useful hints to resolve your issue.

Thanks very much for your remind, but I cannot find the product name matching my environment. I will change the name into other.

Another thing to note is that the kernel is "Tainted (G OEL)" with out-of-tree/unsigned module(s).

This is caused by the DPDK module igb_uio.ko. Is it necessary to reproduce the panic without DPDK?

Hi Kai,

RHEL users might not be able to reproduce your issue. Red Hat does not support the 4.x.y kernels. Might be introduced in RHEL 8.0, as RHEL 8.0 is still alpha only a few major vendors have access to it.

As the kernel you use is not the standard for RHEL 7.2, I doubt it is the original kernel for CentOS 7.2. Did you compile it yourself, or did someone provided it?

If it is provided by a third party, I advise you to ask them for support.

Regards,

Jan Gerrit Kootstra

Hi Jan,

Thanks very much for your reply. Yes, the kernel 4.9 is complied by myself, using the archive from https://www.kernel.org/. The original kernel of CentOS 7.2 is 3.10, I replaced it with the compiled version. Maybe I need to ask the kernel community according to your advice.

Best regards,

Kai Wang

Hi Kai,

First try to unload the DPDK module igb_uio.ko, see if you can boot without this module.

Regards,

Jan Gerrit

Hi Jan,

OK, I'll try to test without DPDK. The past panics occurred when the system CPU load became very high.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.