From: Sean Christopherson <seanjc@google.com>
To: Fabio Coatti <fabio.coatti@gmail.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: WARNING trace at kvm_nx_huge_page_recovery_worker on 6.3.4
Date: Fri, 26 May 2023 10:01:30 -0700 [thread overview]
Message-ID: <ZHDl6rXQ0UTWdk2O@google.com> (raw)
In-Reply-To: <CADpTngX9LESCdHVu_2mQkNGena_Ng2CphWNwsRGSMxzDsTjU2A@mail.gmail.com>
On Fri, May 26, 2023, Fabio Coatti wrote:
> Hi all,
> I'm using vanilla kernels on a gentoo-based laptop and since 6.3.2
What was the last kernel you used that didn't trigger this WARN?
> I'm getting the kernel log below when using kvm VM on my box.
Are you doing anything "interesting" when the WARN fires, or are you just running
the VM and it random fires? Either way, can you provide your QEMU command line?
> I know, kernel is tainted but avoiding to load nvidia driver could make
> things complicated on my side; if needed for debug I can try to avoid it.
Nah, don't worry about that at this point.
> Not sure which other infos can be relevant in this context; if you
> need more details just let me know, happy to provide them.
>
> [Fri May 26 09:16:35 2023] ------------[ cut here ]------------
> [Fri May 26 09:16:35 2023] WARNING: CPU: 5 PID: 4684 at
> kvm_nx_huge_page_recovery_worker+0x38c/0x3d0 [kvm]
Do you have the actual line number for the WARN? There are a handful of sanity
checks in kvm_recover_nx_huge_pages(), it would be helpful to pinpoint which one
is firing. My builds generate quite different code, and the code stream doesn't
appear to be useful for reverse engineering the location.
next prev parent reply other threads:[~2023-05-26 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 7:43 WARNING trace at kvm_nx_huge_page_recovery_worker on 6.3.4 Fabio Coatti
2023-05-26 8:34 ` Bagas Sanjaya
2023-05-26 17:01 ` Sean Christopherson [this message]
2023-05-28 9:22 ` Fabio Coatti
2023-05-28 10:54 ` Fabio Coatti
2023-05-28 12:44 ` Bagas Sanjaya
2023-05-30 10:42 ` Fabio Coatti
2023-05-30 17:37 ` Sean Christopherson
2023-05-31 1:27 ` Sean Christopherson
2023-05-31 2:04 ` Sean Christopherson
2023-06-01 8:38 ` Fabio Coatti
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=ZHDl6rXQ0UTWdk2O@google.com \
--to=seanjc@google.com \
--cc=fabio.coatti@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).