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] 31efbec216: perf-stat-tests.UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU.fail
Date: Fri, 9 Oct 2026 14:30:17 +0800 [thread overview]
Message-ID: <202610091437.bf2c2d3c-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "perf-stat-tests.UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU.fail" on:
commit: 31efbec2161d2d31b020b086958e41f35f070a38 ("perf vendor events intel: Update sapphirerapids events from 1.39 to 1.40") https://git.kernel.org/cgit/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
[test failed on linux-next/master eea3fef32a9cf36abcb5975a5a594e4135a6b026]
in testcase: perf-stat-tests
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire 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/202610091437.bf2c2d3c-lkp@intel.com
EventName: UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU
2026-10-05 17:15:24 perf stat -e UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU -a sleep 0.1
event syntax error: 'UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ Bad event name
Unable to find event on a PMU of 'UNC_IIO_NUM_TGT_MATCHED_REQ_OF_CPU'
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
event syntax error: '..O_NUM_TGT_MATCHED_REQ_OF_CPU'
\___ value too big for format (umask), maximum is 255
Run 'perf list' for a list of valid events
Usage: perf stat [<options>] [<command>]
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261009/202610091437.bf2c2d3c-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-09 6:30 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=202610091437.bf2c2d3c-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®