From 0766ce61fd7dd3ac61b6daca0df194285c6ba891 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Wed, 24 Apr 2019 00:02:57 +0300 Subject: pkg/report: fix stalls in RIP frame Even though we extract an anchor frame which usually higher up the stack, the anchor frame can be on RIP: line too. Account for that. --- pkg/report/linux.go | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'pkg/report/linux.go') diff --git a/pkg/report/linux.go b/pkg/report/linux.go index c63b5bfd8..b498dd503 100644 --- a/pkg/report/linux.go +++ b/pkg/report/linux.go @@ -870,6 +870,7 @@ var linuxOopses = []*oops{ fmt: "BUG: soft lockup in %[1]v", stack: &stackFmt{ parts: []*regexp.Regexp{ + linuxRipFrame, compile("Call Trace:"), parseStackTrace, }, @@ -1134,6 +1135,11 @@ var linuxOopses = []*oops{ fmt: "INFO: rcu detected stall in %[1]v", stack: &stackFmt{ parts: []*regexp.Regexp{ + compile("apic_timer_interrupt"), + linuxRipFrame, + parseStackTrace, + }, + parts2: []*regexp.Regexp{ compile("apic_timer_interrupt"), parseStackTrace, }, -- cgit mrf-deployment