public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Maxim Levitsky <mlevitsk@redhat.com>, <kvm@vger.kernel.org>,
	<xudong.hao@intel.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [KVM]  7803339fa9: kernel-selftests.kvm.pmu_counters_test.fail
Date: Tue, 14 Jan 2025 10:40:22 +0800	[thread overview]
Message-ID: <202501141009.30c629b4-lkp@intel.com> (raw)



Hello,


we fould the test failed on a Cooper Lake, not sure if this is expected.
below full report FYI.


kernel test robot noticed "kernel-selftests.kvm.pmu_counters_test.fail" on:

commit: 7803339fa929387bbc66479532afbaf8cbebb41b ("KVM: selftests: Use data load to trigger LLC references/misses in Intel PMU")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master 37136bf5c3a6f6b686d74f41837a6406bec6b7bc]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-7503345ac5f5-1_20241208
with following parameters:

	group: kvm



config: x86_64-rhel-9.4-kselftests
compiler: gcc-12
test machine: 224 threads 4 sockets Intel(R) Xeon(R) Platinum 8380H CPU @ 2.90GHz (Cooper Lake) with 192G 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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202501141009.30c629b4-lkp@intel.com



# timeout set to 120
# selftests: kvm: pmu_counters_test
# Random seed: 0x6b8b4567
# Testing arch events, PMU version 0, perf_caps = 0
# Testing GP counters, PMU version 0, perf_caps = 0
# Testing fixed counters, PMU version 0, perf_caps = 0
# Testing arch events, PMU version 0, perf_caps = 2000
# Testing GP counters, PMU version 0, perf_caps = 2000
# Testing fixed counters, PMU version 0, perf_caps = 2000
# Testing arch events, PMU version 1, perf_caps = 0
# ==== Test Assertion Failure ====
#   x86/pmu_counters_test.c:129: count >= (10 * 4 + 5)
#   pid=6278 tid=6278 errno=4 - Interrupted system call
#      1	0x0000000000411281: assert_on_unhandled_exception at processor.c:625
#      2	0x00000000004075d4: _vcpu_run at kvm_util.c:1652
#      3	 (inlined by) vcpu_run at kvm_util.c:1663
#      4	0x0000000000402c5e: run_vcpu at pmu_counters_test.c:62
#      5	0x0000000000402e4d: test_arch_events at pmu_counters_test.c:315
#      6	0x0000000000402663: test_arch_events at pmu_counters_test.c:304
#      7	 (inlined by) test_intel_counters at pmu_counters_test.c:609
#      8	 (inlined by) main at pmu_counters_test.c:642
#      9	0x00007f3b134f9249: ?? ??:0
#     10	0x00007f3b134f9304: ?? ??:0
#     11	0x0000000000402900: _start at ??:?
#   count >= NUM_INSNS_RETIRED
not ok 21 selftests: kvm: pmu_counters_test # exit=254



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250114/202501141009.30c629b4-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2025-01-14  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  2:40 kernel test robot [this message]
2025-01-14 19:47 ` [linux-next:master] [KVM] 7803339fa9: kernel-selftests.kvm.pmu_counters_test.fail Sean Christopherson
2025-01-15  2:44   ` Mi, Dapeng
2025-01-17  3:04     ` Mi, Dapeng
2025-01-17 17:11       ` Sean Christopherson
2025-01-20  2:02         ` Mi, Dapeng
2025-01-21 16:13           ` Sean Christopherson
2025-01-22  1:26             ` Mi, Dapeng

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=202501141009.30c629b4-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mlevitsk@redhat.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=seanjc@google.com \
    --cc=xudong.hao@intel.com \
    /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