Soft Lockups in rpc.svcgssd

Jurjen Bokma

Last modified: "2018-05-18 10:05:03 jurjen"


Soft lockups in or 100% CPU use by rpc.svcgssd might occur when a Kerberized Linux NFS server takes part in an AD domain. The remedy is to set the NO_AUTH_DATA_REQUIRED bit on the userAccountControl attribute of the server in LDAP.

Table of Contents


We had soft lockups in rpc.scvgssd:

BUG: soft lockup - CPU#1 stuck for 22s!

Or if the watchdog timer was disabled, rpc.svcgssd would just take 100% CPU.

The effect for the user is that NFS access fails, even on $HOME, and already the login process gets stuck.