From a56e954886fc9dadfa50247f25679ebfdd60d52b Mon Sep 17 00:00:00 2001 From: Petr Vorel Date: Tue, 20 Aug 2024 12:56:23 +0200 Subject: [PATCH] LTP: Add 'Call Trace:' as failure in dmesg At least syslog11 on unfixed SLERT-15SP6 produced this output in dmesg. Link: https://bugzilla.suse.com/show_bug.cgi?id=1229025#c1 Signed-off-by: Petr Vorel --- lib/known_bugs.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/known_bugs.pm b/lib/known_bugs.pm index 0063168a7f11..98b2bde4bd7c 100644 --- a/lib/known_bugs.pm +++ b/lib/known_bugs.pm @@ -65,6 +65,8 @@ sub create_list_of_serial_failures { push @$serial_failures, {type => $type, message => 'Kernel stack is corrupted', pattern => quotemeta 'stack-protector: Kernel stack is corrupted'}; push @$serial_failures, {type => $type, message => 'Kernel BUG found', pattern => quotemeta 'BUG: failure at'}; push @$serial_failures, {type => $type, message => 'Kernel Ooops found', pattern => quotemeta '-[ cut here ]-'}; + # bsc#1229025, but must be soft because any LTP test which intentionally triggers OOM killer will produce this call trace as well + push @$serial_failures, {type => 'soft', message => 'Kernel Call Trace found', pattern => quotemeta 'Call Trace:'}; } push @$serial_failures, {type => 'soft', message => 'Low memory problem detected bsc#1166955', pattern => quotemeta 'kswapd0 Kdump'};