mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, Reinette Chatre <reinette.chatre@intel.com>
Cc: linux-sgx@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 1 PID: 83 at arch/x86/kernel/cpu/sgx/main.c:446 ksgxd+0x1b7/0x1d0
Date: Tue, 23 Aug 2022 09:32:45 -0700	[thread overview]
Message-ID: <beabe16c-b28b-cd65-f6b6-4242bc74926d@intel.com> (raw)
In-Reply-To: <63a60042-4a4a-3bc3-5fa1-4495d80cc06c@molgen.mpg.de>

On 8/23/22 06:48, Paul Menzel wrote:
>>> I'm suspecting either a BIOS problem.  Reinette (cc'd) also thought this
>>> might be a case of the SGX initialization getting a bit too far along
>>> when it should have been disabled.
>>>
>>> We had some bugs where we didn't stop fast enough after spitting out the
>>> "SGX Launch Control is locked..." errors.
> 
> Let’s hope it’s something known to you.

Thanks for the extra debug info.  Unfortunately, nothing is really
sticking out as an obvious problem.

The EREMOVE return codes would be interesting to know, as well as an
idea what the physical addresses are that fail and the _counts_ of how
many pages get sanitized versus fail.

But, I don't really have a theory about what could be going on yet.

  reply	other threads:[~2022-08-23 18:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 13:19 Paul Menzel
2022-08-19 16:02 ` Paul Menzel
2022-08-19 18:28   ` Dave Hansen
2022-08-20  6:13     ` Paul Menzel
2022-08-23 13:48       ` Paul Menzel
2022-08-23 16:32         ` Dave Hansen [this message]
2022-08-23 22:33           ` Paul Menzel
2022-08-24 18:39             ` Dave Hansen
2022-08-25  5:27             ` Jarkko Sakkinen
2022-08-25  2:12         ` Haitao Huang
2022-08-25  5:49           ` Jarkko Sakkinen
2022-08-25  8:34             ` Jarkko Sakkinen
2022-08-26  9:54           ` Paul Menzel
2022-08-25  4:57     ` Jarkko Sakkinen
2022-08-25  5:25       ` Jarkko Sakkinen
2022-08-25  6:46         ` Paul Menzel
2022-08-25  8:39           ` Jarkko Sakkinen

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=beabe16c-b28b-cd65-f6b6-4242bc74926d@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=reinette.chatre@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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
all inboxes | Powered by JetHome®