My Oracle Support Banner

Oracle Linux: Kworker Spinlock Contention Leading To High CPU Utilization (Doc ID 3012342.1)

Last updated on MARCH 25, 2024

Applies to:

Linux OS - Version Oracle Linux 7.0 with Unbreakable Enterprise Kernel [3.8.13] to Oracle Linux 8.9 with Unbreakable Enterprise Kernel [5.15.0] [Release OL7 to OL8U9]
Linux x86-64

Symptoms

sapcimb process exiting is using 8 kworker threads to unmap its memory and are running into contention on a swap_entry spinlock

A perf snippet showing sapcimb process exiting is using 8 kworker threads to unmap its memory using padata_mt_helper, and they're running into contention on a swap entry spinlock.

Changes

 No Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.