On Wed, Apr 07, 2021 at 04:54:33PM +0200, Petr Mladek wrote:

On Tue 2021-03-30 20:05:12, Stephen Boyd wrote:

quoted

Let's make kernel stacktraces easier to identify by including the build
ID[1] of a module if the stacktrace is printing a symbol from a module.
This makes it simpler for developers to locate a kernel module's full
debuginfo for a particular stacktrace. Combined with
scripts/decode_stracktrace.sh, a developer can download the matching
debuginfo from a debuginfod[2] server and find the exact file and line
number for the functions plus offsets in a stacktrace that match the
module. This is especially useful for pstore crash debugging where the
kernel crashes are recorded in something like console-ramoops and the
recovery kernel/modules are different or the debuginfo doesn't exist on
the device due to space concerns (the debuginfo can be too large for
space limited devices).

...

It shows wrong build id for vmlinux.
And it does not show the build if for the module at all.

From your previous messages and this seems like virtualization breaks the
access / use of build ID :-(

-- 
With Best Regards,
Andy Shevchenko