Over the weekend I was confronted by the above error being repeated on the console of a VM running Oracle RDBMS.
This error occurs when there is a shortage of CPU resources. For me the solution was a quick shut down of the VM and increasing the available CPU resources. However there are more ways to skin this cat…
There is also a kernel parameter which can be tweaked;
Were “x” is the threshold (in seconds) you want to allow the kernel to wait before decided there has been a soft lockup.
The Red Hat documentation showed a threshold of 30 seconds. So I would recommend a bit of experimentation if you feel that 30 seconds is not high enough. Or throw more resources at it.