From: Oliver Sang <oliver.sang@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Sean Christopherson <seanjc@google.com>, <oe-lkp@lists.linux.dev>,
<lkp@intel.com>, <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
Srikanth Aithal <sraithal@amd.com>, <fengwei.yin@intel.com>,
<yujie.liu@intel.com>, <oliver.sang@intel.com>
Subject: Re: [tip:x86/alternatives] [x86/alternatives] ee8962082a: WARNING:at_arch/x86/kernel/cpu/cpuid-deps.c:#do_clear_cpu_cap
Date: Wed, 8 May 2024 16:37:42 +0800 [thread overview]
Message-ID: <Zjs51oZWhibDhWa3@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20240508082438.GBZjs2xsn4diYXU4ud@fat_crate.local>
hi, Boris,
On Wed, May 08, 2024 at 10:24:38AM +0200, Borislav Petkov wrote:
> On Wed, May 08, 2024 at 04:08:18PM +0800, Oliver Sang wrote:
> > we really don't do any manual change recently, however, per your reminding,
> > we rerun tests on both ee8962082a and its parent v6.9-rc3 again.
> >
> > while we made original report, we always saw below for both commits.
> > "x86/cpu: VMX (outside TXT) disabled by BIOS"
> >
> > by rerun today, we cannot see it again, on both commits.
>
> Yeah, from the last dump you shouldn't be seeing it.
>
> > then for ee8962082a, the reported
> > WARNING:at_arch/x86/kernel/cpu/cpuid-deps.c:#do_clear_cpu_cap
> > disappeared also while no "x86/cpu: VMX (outside TXT) disabled by BIOS"
>
> Yeah, it does feel like something underneath the OS has changed/is
> changing for this to happen.
>
> > we are using kexec to boot into kernel, and the kernel images keep same,
> > so we are sure this strage phenomenon is not caused by kernel build.
>
> Hmm, kexec won't go through BIOS so I can imagine if the kernel has left
> FEAT_CTL in some weird state... but then if it has been locked, nothing
> should change it anymore.
>
> > now we doubt it's really a bios issue, we found another similar machine,
> > which also show "x86/cpu: VMX (outside TXT) disabled by BIOS", but after
> > several rounds of cold reboot, the message disappeared, too.
>
> If you see that again, please run my branch with the debug patch - that
> should at least tell us what's weird in FEAT_CTL.
thanks a lot for education! sure, we will do that.
>
> > we will investigate this BIOS further and avoid this kind of misleading
> > report in the future.
> >
> > sorry again :(
>
> No worries, thanks for testing kernels and thanks Sean too. :-)
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
prev parent reply other threads:[~2024-05-08 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:00 [tip:x86/alternatives] [x86/alternatives] ee8962082a: WARNING:at_arch/x86/kernel/cpu/cpuid-deps.c:#do_clear_cpu_cap kernel test robot
2024-04-30 17:23 ` Borislav Petkov
2024-04-30 18:40 ` Sean Christopherson
2024-04-30 19:32 ` Borislav Petkov
2024-04-30 19:51 ` Sean Christopherson
2024-04-30 22:33 ` Borislav Petkov
2024-05-04 12:48 ` Borislav Petkov
2024-05-04 12:49 ` [PATCH 1/2] x86/alternatives: Check the correct cpu_data's caps Borislav Petkov
2024-05-04 12:50 ` [PATCH 2/2] x86/CPU/Intel: Do the MSR_IA32_FEAT_CTL setup before alternatives Borislav Petkov
2024-05-06 7:09 ` [tip:x86/alternatives] [x86/alternatives] ee8962082a: WARNING:at_arch/x86/kernel/cpu/cpuid-deps.c:#do_clear_cpu_cap Oliver Sang
2024-05-06 7:39 ` Borislav Petkov
2024-05-06 8:01 ` Borislav Petkov
2024-05-06 8:12 ` Borislav Petkov
2024-05-07 2:29 ` Oliver Sang
2024-05-06 15:28 ` Sean Christopherson
2024-05-06 15:57 ` Borislav Petkov
2024-05-07 7:08 ` Oliver Sang
2024-05-07 11:48 ` Borislav Petkov
2024-05-07 17:09 ` Sean Christopherson
2024-05-08 8:08 ` Oliver Sang
2024-05-08 8:24 ` Borislav Petkov
2024-05-08 8:37 ` Oliver Sang [this message]
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=Zjs51oZWhibDhWa3@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=bp@alien8.de \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=seanjc@google.com \
--cc=sraithal@amd.com \
--cc=x86@kernel.org \
--cc=yujie.liu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).