mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Daniel Bristot de Oliveira <bristot@kernel.org>,
	"Vineeth Pillai (Google)" <vineeth@bitbyteword.org>,
	Juri Lelli <juri.lelli@redhat.com>, <aubrey.li@linux.intel.com>,
	<yu.c.chen@intel.com>, <oliver.sang@intel.com>
Subject: [linus:master] [sched/rt]  5f6bd380c7: kernel-selftests.kvm.rseq_test.fail
Date: Mon, 21 Oct 2024 13:44:24 +0800	[thread overview]
Message-ID: <202410211347.6d1c29b9-oliver.sang@intel.com> (raw)



Hello,

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

commit: 5f6bd380c7bdbe10f7b4e8ddcceed60ce0714c6d ("sched/rt: Remove default bandwidth control")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master      684a64bf32b6e488004e0ad7f0d7e922798f65b6]
[test failed on linux-next/master 2b7275670032a98cba266bd1b8905f755b3e650f]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:

	group: kvm



config: x86_64-rhel-8.3-kselftests
compiler: gcc-12
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


we noticed the issue happens randomly, 57 times out of 200 runs as below.
but parent keeps clean.

c8a85394cfdb4696 5f6bd380c7bdbe10f7b4e8ddcce
---------------- ---------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :200         28%          57:200   kernel-selftests.kvm.rseq_test.fail



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/202410211347.6d1c29b9-oliver.sang@intel.com


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241021/202410211347.6d1c29b9-oliver.sang@intel.com


# timeout set to 120
# selftests: kvm: rseq_test
# Random seed: 0x6b8b4567
# ==== Test Assertion Failure ====
#   rseq_test.c:293: skip_sanity_check || i > (NR_TASK_MIGRATIONS / 2)
#   pid=46138 tid=46138 errno=4 - Interrupted system call
#      1	0x000000000040299a: main at rseq_test.c:293
#      2	0x00007fc679e6e249: ?? ??:0
#      3	0x00007fc679e6e304: ?? ??:0
#      4	0x0000000000402a80: _start at ??:?
#   Only performed 47875 KVM_RUNs, task stalled too much?
# 
#   Try disabling deep sleep states to reduce CPU wakeup latency,
#   e.g. via cpuidle.off=1 or setting /dev/cpu_dma_latency to '0',
#   or run with -u to disable this sanity check.
not ok 78 selftests: kvm: rseq_test # exit=254

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


                 reply	other threads:[~2024-10-21  5:44 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=202410211347.6d1c29b9-oliver.sang@intel.com \
    --to=oliver.sang@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=bristot@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=vineeth@bitbyteword.org \
    --cc=yu.c.chen@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

all inboxes | Powered by JetHome®