From 7bdd8b2c56b883af3e65b261cd7c942104dc2ecc Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Sat, 5 Mar 2022 13:38:41 +0100 Subject: dashboard/config/linux: enable CONFIG_BACKTRACE_VERBOSE for arm W/o this config arm stack traces don't include PC which we expect when parsing stack traces. It was added in May 13 2021, and it seems since then we classified all arm reports as corrupted. --- dashboard/config/linux/bits/arm.yml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'dashboard/config/linux/bits/arm.yml') diff --git a/dashboard/config/linux/bits/arm.yml b/dashboard/config/linux/bits/arm.yml index a67e4f954..b9b6337a6 100644 --- a/dashboard/config/linux/bits/arm.yml +++ b/dashboard/config/linux/bits/arm.yml @@ -26,6 +26,8 @@ config: # The other one (UNWINDER_ARM) leads to unparsable oopses (no indication of stack start). - UNWINDER_FRAME_POINTER + # Print PCs in stack traces otherwise we fail to parse oopses. + - BACKTRACE_VERBOSE # Presumably this gives more interesting coverage. - HIGHMEM -- cgit mrf-deployment