Include errors outside sof-audio before scanning dmesg for errors, ignore only specific known issues

[fredoh9]

When scan errors in kernel log in sof-kernel-log-check.sh, current code filter "sof-audio" first then check for error. This will limit scanning logs and not scalable. Below $project_key is nothing but "sof-audio".

err_str="error|failed|timed out|panic|oops"
project_key="sof-audio"

if [ "$ignore_str" ]; then
    err=$(eval $cmd|grep 'Call Trace' -A5 -B3)$(eval $cmd | grep $project_key | grep -E "$err_str"|grep -vE "$ignore_str")
else
    err=$(eval $cmd|grep 'Call Trace' -A5 -B3)$(eval $cmd | grep $project_key | grep -E "$err_str")
fi

We should remove this limitation. If we see unrelated error, we can add it to ignoring error list. This is first step toward this approach. I ran first test on APL, CML Helios, ICL RVP. If no objection is raised, I will scan logs for all supported platforms and update ignore_str.

[marc-hb]

Thanks for doing this.

[marc-hb]

The shellcheck warnings seem to all make sense.

[marc-hb]

err_str="error|failed|timed out|panic|oops"

Later we should drop such "screen scraping" and use something more robust like journalctl --dmesg --priority err with no false positive (for instance a debug message with one of these keywords) and no false negative (e.g. ERR:). I'm not suggesting to do that right now but probably good to keep in mind while you're doing this PR.

[fredoh9]

err_str="error|failed|timed out|panic|oops"

Later we should drop such "screen scraping" and use something more robust like journalctl --dmesg --priority err with no false positive (for instance a debug message with one of these keywords) and no false negative (e.g. ERR:). I'm not suggesting to do that right now but probably good to keep in mind while you're doing this PR.

This is good idea, I will create an issue to follow up.

[marc-hb]

cc: @xiulipan - this would be a perfect use case for sof-test CI.

[aiChaoSONG]

Thanks for the fix. LGTM