On (09/27/18 12:46), Daniel Wang wrote: > Prior to this change, the combination of `softlockup_panic=1` and > `softlockup_all_cpu_stacktrace=1` may result in a deadlock when the reboot path > is trying to grab the console lock that is held by the stack trace printing > path. What seems to be happening is that while there are multiple CPUs, only one > of them is tasked to print the back trace of all CPUs. On a machine with many > CPUs and a slow serial console (on Google Compute Engine for example), the stack > trace printing routine hits a timeout and the reboot path kicks in. The latter > then tries to print something else, but can't get the lock because it's still > held by earlier printing path. Sorry, I'm missing something here. Steven's patch deals with lockups and I understand why you want to backport the patch set; but console output deadlock on panic() is another thing. You said "then tries to print something else, but can't get the lock because it's still held by earlier printing path" Can't get which of the locks? -ss
