aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits/debug.yml
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2021-04-14 10:09:00 +0200
committerDmitry Vyukov <dvyukov@google.com>2021-04-14 10:55:17 +0200
commit3134b37f0ab0b36b36f6b94e842ca007d35108b6 (patch)
treeac633377816cd083bc5f32a0e970c011dc04e994 /dashboard/config/linux/bits/debug.yml
parentf87ec44e18d4518253f8758eb8c58a9adfbd6642 (diff)
dashboard/config/linux: tune LOCKDEP capacity
We are seeing the following warnings from LOCKDEP: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! BUG: MAX_LOCKDEP_CHAINS too low! BUG: MAX_LOCKDEP_ENTRIES too low! Increase the corresponding capacity constants.
Diffstat (limited to 'dashboard/config/linux/bits/debug.yml')
-rw-r--r--dashboard/config/linux/bits/debug.yml6
1 files changed, 5 insertions, 1 deletions
diff --git a/dashboard/config/linux/bits/debug.yml b/dashboard/config/linux/bits/debug.yml
index b50a1c8f0..b83eec837 100644
--- a/dashboard/config/linux/bits/debug.yml
+++ b/dashboard/config/linux/bits/debug.yml
@@ -6,8 +6,12 @@
config:
# Instances that use nonoise also ignore WARNINGs, so they don't want panic_on_warn.
- CMDLINE: [append, "panic_on_warn=1"]
-
- LOCKDEP
+ - LOCKDEP_BITS: [16, linux-next]
+ - LOCKDEP_CHAINS_BITS: [17, linux-next]
+ - LOCKDEP_STACK_TRACE_BITS: [19, linux-next]
+ - LOCKDEP_STACK_TRACE_HASH_BITS: [14, linux-next]
+ - LOCKDEP_CIRCULAR_QUEUE_BITS: [12, linux-next]
- PROVE_LOCKING
- DEBUG_ATOMIC_SLEEP
- PROVE_RCU