I got a new work laptop (with alderlake i7-1250U), ran the gdb testsuite and
ran into issues with the "record btrace" command, on openSUSE Leap 15.4, but
not on openSUSE Tumbleweed.

The responsible gdb maintainer pointed me to a linux kernel commit that should
fix this:
...
$ git show ce0d998be9274dd3a3d971cbeaa6fe28fd2c3062
commit ce0d998be9274dd3a3d971cbeaa6fe28fd2c3062
Author: Adrian Hunter <adrian.hunter@intel.com>
Date:   Sat Nov 12 17:15:08 2022 +0200

    perf/x86/intel/pt: Fix sampling using single range output

    Deal with errata TGL052, ADL037 and RPL017 "Trace May Contain Incorrect
    Data When Configured With Single Range Output Larger Than 4KB" by
    disabling single range output whenever larger than 4KB.

    Fixes: 670638477aed ("perf/x86/intel/pt: Opportunistically use single range
output mode")
    Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: stable@vger.kernel.org
    Link:
https://lkml.kernel.org/r/20221112151508.13768-1-adrian.hunter@intel.com
... 

I went as far as applying the patch to tag v5.14.21, and it applied cleanly.

So, can we backport this to leap 15.4?

Related gdb PRs:
- https://sourceware.org/bugzilla/show_bug.cgi?id=30073
- https://sourceware.org/bugzilla/show_bug.cgi?id=30075