All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <ray.kinsella-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org"
	<jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org>
Subject: Re: efi_printk
Date: Fri, 15 Apr 2016 10:08:44 +0000	[thread overview]
Message-ID: <1460714923.3575.2.camel@intel.com> (raw)
In-Reply-To: <005f85571fda40a483f7a5b7438a738d-KbE+qi2yd2TmmfPIhZPphU4JlKGuRTdvVpNB7YpNyf8@public.gmane.org>


Have you set CONFIG_EARLY_PRINTK_EFI ?

Ray K

On Thu, 2016-04-14 at 19:25 +0000, Jason Taylor wrote:
> I'm not having luck finding the efi_printk output for
> compressed/eboot.c. I have tried adding "earlyprintk=efi,keep" to the
> boot params. Is there something special that I need to do to enable
> it? I didn't see a config option that seemed to enable/disable it.
> From some bug reports, it looks like these messages should possibly
> just be showing up in dmesg? I'm running as a guest on Hyper-V in
> case that makes a difference.
> 
> Thanks,
> Jason
> ---------------------------------------------------------------------
> ------------------
> PRIVACY STATEMENT:
> This message is a PRIVATE communication.  This message and all
> attachments are a private communication sent by SimpliVity and are
> considered to be confidential or protected by privilege. If you are
> not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or use of the information contained
> in or attached to this message is strictly prohibited.  Please notify
> the sender of the delivery error by replying to this message, and
> then delete it from your system.
> ---------------------------------------------------------------------
> ------------------
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-efi"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-04-15 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 19:25 efi_printk Jason Taylor
     [not found] ` <005f85571fda40a483f7a5b7438a738d-KbE+qi2yd2TmmfPIhZPphU4JlKGuRTdvVpNB7YpNyf8@public.gmane.org>
2016-04-15 10:08   ` Kinsella, Ray [this message]
     [not found]     ` <1460714923.3575.2.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-15 14:24       ` efi_printk Jason Taylor
     [not found]         ` <666a26ae-8a78-a2d0-77c3-e2724be7d1d5-RrviKlmTjidOSnsfY10OVw@public.gmane.org>
2016-04-15 16:32           ` efi_printk Kinsella, Ray

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=1460714923.3575.2.camel@intel.com \
    --to=ray.kinsella-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=jason.taylor-RrviKlmTjidOSnsfY10OVw@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.