From: kernel test robot <yi1.lai@intel.com>
To: Ian Rogers <irogers@google.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
yi1.lai@intel.com
Subject: [perf-tools-next:tmp.perf-tools-next] [perf vendor events intel] 3c989481ee: perf-sanity-tests.x86_topdown.topdown_events.fail
Date: Fri, 9 Oct 2026 14:09:24 +0800 [thread overview]
Message-ID: <202610091243.76a68f01-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "perf-sanity-tests.x86_topdown.topdown_events.fail" on:
commit: 3c989481ee3cc22ac5d34e73862a4016af770710 ("perf vendor events intel: Update emeraldrapids events from 1.24 to 1.25") https://git.kernel.org/cgit/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
[test failed on linux-next/master f0406245cb9855e6318335a8a223551354291a46]
in testcase: perf-sanity-tests
version:
with following parameters:
perf_compiler: gcc
group: group-02
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 256 threads 4 sockets INTEL(R) XEON(R) PLATINUM 8592+ (Emerald Rapids) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202610091243.76a68f01-lkp@intel.com
2026-10-04 03:23:58 sudo ASAN_OPTIONS=fast_unwind_on_malloc=0 /usr/src/linux-perf-x86_64-rhel-9.4-bpf-3c989481ee3cc22ac5d34e73862a4016af770710/tools/perf/perf test 77 -v
77: x86 topdown :
77.1: topdown events : Running (4 active)
---- start ----
...
event syntax error: 'cpu/mem_trans_retired.load_latency/'
\___ Bad event or PMU ...
event syntax error: '..atency/'
\___ expected numeric value ...
event syntax error: '..atency/'
\___ expected numeric value ...
WARNING: events were regrouped to match PMUs evlist after sorting/fixing: '{slots,cpu/topdown-bad-spec/}'
---- end(-1) ----
77.1: topdown events : FAILED!
77.2: topdown sorting : Ok
77.3: topdown slots injection : Ok
77.4: topdown metrics_clear no extra slots : Ok
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261009/202610091243.76a68f01-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-09 6:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202610091243.76a68f01-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.