Re:63 Cores Blocked by Seven Instructions
by brucedawson on Monday October 21, 2019 @11:32PM
(#21320162)
Correct. Nobody was spinning on a lock. Everybody was waiting politely.
The problem was that the system process held the lock for too long, due to some inefficiency in system restore (root cause not yet understood by me).
So it looks more like "process is holding lock A while doing a very long scan through memory". That would fit with the name of the function, too.