public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216598] New: Assertion Failure in kvm selftest mmio_warning_test
Date: Mon, 17 Oct 2022 07:42:19 +0000	[thread overview]
Message-ID: <bug-216598-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216598

            Bug ID: 216598
           Summary: Assertion Failure in kvm selftest mmio_warning_test
           Product: Virtualization
           Version: unspecified
    Kernel Version: 6.0.0-rc7
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: lixiao.yang@intel.com
        Regression: No

Created attachment 303018
  --> https://bugzilla.kernel.org/attachment.cgi?id=303018&action=edit
Host dmesg log

Environment:
CPU Architecture: x86_64
Host OS: Red Hat Enterprise Linux 8.4 (Ootpa)
Host kernel: 6.0.0-rc7
gcc: gcc (GCC) 8.4.1 
Host kernel source:  https://git.kernel.org/pub/scm/virt/kvm/kvm.git
Branch: next
Commit: e18d6152ff0f41b7f01f9817372022df04e0d354


Bug Detailed Description:
Assertion failure and host call trace happened after executing kvm selftest
mmio_warning_test.


Reproducing Steps:
git clone https://git.kernel.org/pub/scm/virt/kvm/kvm.git
cd kvm && make headers_install
cd kvm/tools/testing/selftests/kvm && make
cd x86_64 && ./mmio_warning_test

Actual Result:
[root@icx-2s2 ~]# kvm/tools/testing/selftests/kvm/x86_64/mmio_warning_test
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
ret1=0 exit_reason=17 suberror=1
ret1=0 exit_reason=8 suberror=65530
==== Test Assertion Failure ====
  x86_64/mmio_warning_test.c:118: warnings_before == warnings_after
  pid=4383 tid=4383 errno=0 - Success
     1  0x0000000000402463: main at mmio_warning_test.c:117
     2  0x00007f5bc5c23492: ?? ??:0
     3  0x00000000004024dd: _start at ??:?
  Warnings found in kernel.  Run 'dmesg' to inspect them.

[root@icx-2s2 ~]#dmesg |grep -i "call trace"
[  208.938961] Call Trace:
[  209.289307] Call Trace:
[  209.683239] Call Trace:
[  210.016660] Call Trace:
[  210.389796] Call Trace:
[  210.727731] Call Trace:
[  211.090710] Call Trace:
[  211.422556] Call Trace:
[  211.785661] Call Trace:
[  212.117551] Call Trace:

Expected Result:
[root@icx-2s2 ~]#kvm/tools/testing/selftests/kvm/x86_64/mmio_warning_test
[root@icx-2s2 ~]
[root@icx-2s2 ~]#dmesg |grep -i "call trace"
[root@icx-2s2 ~]

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-10-17  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  7:42 bugzilla-daemon [this message]
2022-10-17  7:44 ` [Bug 216598] Assertion Failure in kvm selftest mmio_warning_test bugzilla-daemon
2022-10-17 15:22 ` [Bug 216598] New: " Sean Christopherson
2022-10-17 15:23 ` [Bug 216598] " bugzilla-daemon

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=bug-216598-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox