From 54fa54c7169bfe5fc83dc52ba6f9abd69dfb2ce4 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Wed, 20 Apr 2022 14:13:11 +0200 Subject: dashboard/config/linux: enable CSD_LOCK_WAIT_DEBUG As asked by Hillf here: https://lore.kernel.org/all/20220419134616.GE4285@paulmck-ThinkPad-P17-Gen-1/ This config can provide more precise diagnostic for some bugs. --- dashboard/config/linux/bits/debug.yml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'dashboard/config/linux/bits/debug.yml') diff --git a/dashboard/config/linux/bits/debug.yml b/dashboard/config/linux/bits/debug.yml index 099c02be2..aee3e760c 100644 --- a/dashboard/config/linux/bits/debug.yml +++ b/dashboard/config/linux/bits/debug.yml @@ -16,6 +16,10 @@ config: - DEBUG_VIRTUAL: [-s390] - LOCKUP_DETECTOR: [-s390] - SOFTLOCKUP_DETECTOR: [-s390] + # This config itself was added in v5.10, but the smp.csd_lock_timeout command line argument + # that is required to make it reliably usable is currently only in linux-next. + # TODO: change this to v5.18 when smp.csd_lock_timeout reaches mainline. + - CSD_LOCK_WAIT_DEBUG: [linux-next] - DETECT_HUNG_TASK - WQ_WATCHDOG - BOOTPARAM_HUNG_TASK_PANIC -- cgit mrf-deployment