From: Jordan Hand <jorhand@linux.microsoft.com>
To: Matthew Garrett <mjg59@google.com>,
linux-integrity <linux-integrity@vger.kernel.org>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: Re: linux-tpmdd self signed kernel failing to boot with secreboot on
Date: Mon, 29 Apr 2019 08:30:55 -0700 [thread overview]
Message-ID: <6373c67f-ea2f-ae1d-0343-4bb774f1d52f@linux.microsoft.com> (raw)
In-Reply-To: <CACdnJuuhiQQ8Uq1A_qfidCLVPVQ_3Ty_Kqg+tQPDx2z3P0Yp9w@mail.gmail.com>
On 4/25/19 2:47 PM, Matthew Garrett wrote:
> On Wed, Apr 24, 2019 at 11:30 AM 'Jordan' via mjg59 <mjg59@google.com> wrote:
>> Under the following circumstances my kernel will not boot:
>
> Will it boot under other circumstances (ie, if you disable Secure
> Boot, does it work fine with the patches?)
Yes it works fine if secure boot is disabled.
>
>> I have traced kernel boot to the call to efi_exit_boot_services in
>> arch/x86/boot/compressed/eboot at which point execution terminates. I
>> see Matthew has made a couple changes in efi_main which calls exit_boot
>> (and in turn calls efi_exit_boot_services).
>
> Does the boot hang or does the machine reboot?
>
The boot hangs.
I haven't had a chance yet but I'll try it out with upstream grub this
week (instead of the Ubuntu package) and see if maybe its grub doing
something weird.
next prev parent reply other threads:[~2019-04-29 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:30 linux-tpmdd self signed kernel failing to boot with secreboot on Jordan
2019-04-25 21:47 ` Matthew Garrett
2019-04-29 15:30 ` Jordan Hand [this message]
2019-04-29 19:17 ` Matthew Garrett
2019-04-29 20:35 ` Jordan Hand
2019-04-29 22:50 ` Matthew Garrett
2019-04-30 16:28 ` Jordan Hand
2019-04-30 22:43 ` Matthew Garrett
2019-04-30 23:00 ` Jordan Hand
2019-04-30 23:24 ` Matthew Garrett
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=6373c67f-ea2f-ae1d-0343-4bb774f1d52f@linux.microsoft.com \
--to=jorhand@linux.microsoft.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.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 NNTP newsgroup(s).