From: Jordan Hand <jorhand@linux.microsoft.com>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: Re: linux-tpmdd self signed kernel failing to boot with secreboot on
Date: Tue, 30 Apr 2019 16:00:40 -0700 [thread overview]
Message-ID: <0dc4e73c-00a8-5023-7065-3b21483a8a14@linux.microsoft.com> (raw)
In-Reply-To: <CACdnJuvpe6_O8jPb-2pBPqgAZ7J1NbuPvbOO4kDd4d80k8p8OA@mail.gmail.com>
On 4/30/19 3:43 PM, Matthew Garrett wrote:
> On Tue, Apr 30, 2019 at 9:28 AM Jordan Hand <jorhand@linux.microsoft.com> wrote:
>
>> 1st Gen (SKU Number from dmidecode is LENOVO_MT_3448)
>
> Ok, unfortunately not able to grab one of those. If you boot with
> earlyprintk=efi on the kernel command line, do you get any output
> around the hang?
>
No. The only print messages I get are from efi_printk. And they don't
show up like normal kernel logs do during boot. The purple grub screen
hangs and the efi_printk messages just print over the top of it.
Although now I'm wondering if the efi_printk messages I added after
efi_exit_boot_services just aren't showing up because I've exited boot
services and can no longer call that function (seems reasonable).
next prev parent reply other threads:[~2019-04-30 23:00 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
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 [this message]
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=0dc4e73c-00a8-5023-7065-3b21483a8a14@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).