mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aditya Garg <gargaditya08@live.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Jeremy Kerr <jk@ozlabs.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Orlando Chamberlain <redecorating@protonmail.com>,
	Aun-Ali Zaidi <admin@kodeit.net>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG SEVERE] Failure to enable EFI Runtime services on T2 Macs
Date: Tue, 8 Feb 2022 14:55:12 +0000	[thread overview]
Message-ID: <2A5B5047-23DE-4660-9ABD-446EE264CC54@live.com> (raw)
In-Reply-To: <CAMj1kXEUudnnX8FaAhtUmcKB+jt237BUTsMrNC8ZoOepf4P3pQ@mail.gmail.com>



> On 08-Feb-2022, at 7:33 PM, Ard Biesheuvel <ardb@kernel.org> wrote:
> 
> On Tue, 8 Feb 2022 at 14:55, Aditya Garg <gargaditya08@live.com> wrote:
>> 
>> On using some specific kernel configuration, on Macs with the T2 Security chip, EFI Runtime services fail to start. Some logs which may be useful are as follows :-
>> 
>> Feb 08 17:11:11 MacBook kernel: [Firmware Bug]: Page fault caused by firmware at PA: 0xffffa79840068000
>> Feb 08 17:11:11 MacBook kernel: WARNING: CPU: 11 PID: 150 at arch/x86/platform/efi/quirks.c:735 efi_crash_gracefully_on_page_fault+0x50/0xd0
> 
> This means the firmware is broken. There is very little we can do
> about this beyond disabling EFI runtime services entirely on such
> systems.
> 
> ...
> 
>> The kernel configuration where this bug is seen is on https://github.com/t2linux/T2-Ubuntu-Kernel/blob/Mainline/templates/default-config
>> 
>> I had an old kernel configuration, where I did not face this issue and was easily able to write to the NVRAM. That kernel configuration is on https://github.com/t2linux/T2-Ubuntu-Kernel/blob/b5c20b8c7689251dd943e22dbe02cef9020db8d1/templates/default-config
>> 
>> I believe these lines in the kernel config, which are present in the former but absent in the latter are causing the issue :-
>> 
> ...
> 
>> Especially CONFIG_LOAD_UEFI_KEYS=y is which I guess may be the culprit.
>> 
> 
> Yes, that seems likely.
> 
>> I request you to reply to my issue as soon as possible
>> 
> 
> Please stop demanding attention like this, even though it is thinly
> veiled as courteous.
> 
> If you want to run bleeding edge kernels on non-standard EFI hardware,
> you have to be able to sort yourself out to some extent. I am the
> EFI-on-Linux maintainer, but that doesn't mean I work for you and have
> to be on call to fix your problems.

Looks like I offended you. Heartiest apologies for that. I guess being from a non English background my works had a negative effect on you. My intention was just to get help, not complain.

Regards
Aditya


      reply	other threads:[~2022-02-08 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 13:55 Aditya Garg
2022-02-08 14:03 ` Ard Biesheuvel
2022-02-08 14:55   ` Aditya Garg [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=2A5B5047-23DE-4660-9ABD-446EE264CC54@live.com \
    --to=gargaditya08@live.com \
    --cc=admin@kodeit.net \
    --cc=ardb@kernel.org \
    --cc=jk@ozlabs.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=redecorating@protonmail.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

all inboxes | Powered by JetHome®