diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2020-03-06 13:37:58 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-03-06 13:38:53 +0100 |
| commit | fd2a5f28eb5e2b7c83b5e814f53e44e2a5dde24c (patch) | |
| tree | 3db98c79b3220c44faa6ec98fda13eb594c4ed1e /pkg | |
| parent | 7fb694ef82d4dace30cf68efba5a6af705c94fa4 (diff) | |
executor: prevent "NMI handler took too long" messages
nmi_check_duration() prints "INFO: NMI handler took too long" on slow debug kernels.
It happens a lot in qemu, and the messages are frequently corrupted
(intermixed with other kernel output as they are printed from NMI)
and are not matched against the suppression in pkg/report.
This write prevents these messages from being printed.
Diffstat (limited to 'pkg')
| -rw-r--r-- | pkg/report/linux.go | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/pkg/report/linux.go b/pkg/report/linux.go index da56e1219..b81ffd814 100644 --- a/pkg/report/linux.go +++ b/pkg/report/linux.go @@ -1341,13 +1341,6 @@ var linuxOopses = append([]*oops{ []*regexp.Regexp{ compile("INFO: lockdep is turned off"), compile("INFO: Stall ended before state dump start"), - // This is printed by nmi_check_duration(), the message simply states - // that an interrupt took too long. It happens a lot in qemu, - // and the messages are frequently corrupted (intermixed with other - // kernel output as they are printed from NMI) and are not matched - // against this suppression. There is a debug var that holds the current - // max duration, so potentially this can be fixed with: - // echo 10000000000 > /sys/kernel/debug/x86/nmi_longest_ns compile("INFO: NMI handler"), compile("INFO: recovery required on readonly filesystem"), compile("(handler|interrupt).*took too long"), |