From: Sean Christopherson <seanjc@google.com>
To: lkp@lists.01.org
Subject: Re: [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail
Date: Mon, 15 Aug 2022 21:42:27 +0000 [thread overview]
Message-ID: <Yvq9wzXNF4ZnlCdk@google.com> (raw)
In-Reply-To: <Yvn60W/JpPO8URLY@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On Mon, Aug 15, 2022, kernel test robot wrote:
> commit: e923b0537d28e15c9d31ce8b38f810b325816903 ("KVM: selftests: Fix target thread to be migrated in rseq_test")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
...
> # selftests: kvm: rseq_test
> # ==== Test Assertion Failure ====
> # rseq_test.c:278: i > (NR_TASK_MIGRATIONS / 2)
> # pid=49599 tid=49599 errno=4 - Interrupted system call
> # 1 0x000000000040265d: main at rseq_test.c:278
> # 2 0x00007fe44eed07fc: ?? ??:0
> # 3 0x00000000004026d9: _start at ??:?
> # Only performed 23174 KVM_RUNs, task stalled too much?
> #
> not ok 56 selftests: kvm: rseq_test # exit=254
...
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86_64 5.19.0-rc6 Kernel Configuration
> #
> CONFIG_CC_VERSION_TEXT="gcc-11 (Debian 11.3.0-3) 11.3.0"
> CONFIG_CC_IS_GCC=y
> CONFIG_GCC_VERSION=110300
> CONFIG_CLANG_VERSION=0
> CONFIG_AS_IS_GNU=y
> CONFIG_AS_VERSION=23800
> CONFIG_LD_IS_BFD=y
> CONFIG_LD_VERSION=23800
> CONFIG_LLD_VERSION=0
Assuming 23800 == 2.38, this is a known issue.
https://lore.kernel.org/all/20220810104114.6838-1-gshan(a)redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Gavin Shan <gshan@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
Andrew Jones <andrew.jones@linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
xudong.hao@intel.com, regressions@lists.linux.dev
Subject: Re: [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail
Date: Mon, 15 Aug 2022 21:42:27 +0000 [thread overview]
Message-ID: <Yvq9wzXNF4ZnlCdk@google.com> (raw)
In-Reply-To: <Yvn60W/JpPO8URLY@xsang-OptiPlex-9020>
On Mon, Aug 15, 2022, kernel test robot wrote:
> commit: e923b0537d28e15c9d31ce8b38f810b325816903 ("KVM: selftests: Fix target thread to be migrated in rseq_test")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
...
> # selftests: kvm: rseq_test
> # ==== Test Assertion Failure ====
> # rseq_test.c:278: i > (NR_TASK_MIGRATIONS / 2)
> # pid=49599 tid=49599 errno=4 - Interrupted system call
> # 1 0x000000000040265d: main at rseq_test.c:278
> # 2 0x00007fe44eed07fc: ?? ??:0
> # 3 0x00000000004026d9: _start at ??:?
> # Only performed 23174 KVM_RUNs, task stalled too much?
> #
> not ok 56 selftests: kvm: rseq_test # exit=254
...
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86_64 5.19.0-rc6 Kernel Configuration
> #
> CONFIG_CC_VERSION_TEXT="gcc-11 (Debian 11.3.0-3) 11.3.0"
> CONFIG_CC_IS_GCC=y
> CONFIG_GCC_VERSION=110300
> CONFIG_CLANG_VERSION=0
> CONFIG_AS_IS_GNU=y
> CONFIG_AS_VERSION=23800
> CONFIG_LD_IS_BFD=y
> CONFIG_LD_VERSION=23800
> CONFIG_LLD_VERSION=0
Assuming 23800 == 2.38, this is a known issue.
https://lore.kernel.org/all/20220810104114.6838-1-gshan@redhat.com
next prev parent reply other threads:[~2022-08-15 21:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 7:50 [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail kernel test robot
2022-08-15 7:50 ` kernel test robot
2022-08-15 21:42 ` Sean Christopherson [this message]
2022-08-15 21:42 ` Sean Christopherson
2022-08-16 5:02 ` Gavin Shan
2022-08-16 5:02 ` Gavin Shan
2022-08-16 10:02 ` Gavin Shan
2022-08-16 10:02 ` Gavin Shan
2022-08-16 22:23 ` Sean Christopherson
2022-08-16 22:23 ` Sean Christopherson
2022-08-17 0:06 ` Gavin Shan
2022-08-17 0:06 ` Gavin Shan
2022-09-05 10:47 ` [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail #forregzbot Thorsten Leemhuis
2022-09-05 10:47 ` Thorsten Leemhuis
2022-11-01 8:32 ` [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail Robert Hoo
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=Yvq9wzXNF4ZnlCdk@google.com \
--to=seanjc@google.com \
--cc=lkp@lists.01.org \
/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.