linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: lv.zheng@intel.com, matt.fleming@intel.com,
	linux-efi@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@acpica.org, lenb@kernel.org,
	rafael.j.wysocki@intel.com, robert.moore@intel.com
Subject: Re: kernel boot fail with efi earlyprintk (bisected)
Date: Fri, 22 Aug 2014 18:02:58 +0800	[thread overview]
Message-ID: <20140822100258.GA1877@darkstar.nay.redhat.com> (raw)
In-Reply-To: <20140821205224.GJ29733@console-pimps.org>

On 08/21/14 at 09:52pm, Matt Fleming wrote:
> On Tue, 19 Aug, at 04:16:58PM, Dave Young wrote:
> > Hi,
> > 
> > 3.16 kernel boot fail with earlyprintk=efi on my laptop.
> > It keeps scrolling at the bottom line of screen.
> > 
> > Bisected, the first bad commit is below:
> > commit 86dfc6f339886559d80ee0d4bd20fe5ee90450f0
> > Author: Lv Zheng <lv.zheng@intel.com>
> > Date:   Fri Apr 4 12:38:57 2014 +0800
> > 
> >     ACPICA: Tables: Fix table checksums verification before installation.
> > 
> > 
> > I did some debugging by enabling both serial and efi earlyprintk, below is
> > some debug dmesg, seems early_ioremap fails in scroll up function due to
> > no free slot, but I'm still not sure if the debug info is right or not.
> 
> Thanks Dave, your callstack seems to make sense.
> 
> Can you also enable early_ioremap_debug so that we can figure out where
> all the FIXMAP slots are going?

With early_ioremap_debug enabled, there will be a lot of "dropped printk", so
I can not get any useful information.

Will try to do more debug.

Thanks
Dave

  parent reply	other threads:[~2014-08-22 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19  8:16 kernel boot fail with efi earlyprintk (bisected) Dave Young
2014-08-21 20:52 ` Matt Fleming
2014-08-22  1:43   ` Zheng, Lv
2014-08-22  5:55   ` Zheng, Lv
2014-08-22 10:04     ` Dave Young
2014-08-22 10:02   ` Dave Young [this message]
     [not found]     ` <20140822100258.GA1877-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-08-25  6:07       ` Dave Young
     [not found]         ` <20140825060713.GA4011-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2014-08-25  6:34           ` Zheng, Lv
2014-08-25  9:06             ` Dave Young
2014-08-25 11:16               ` Matt Fleming

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=20140822100258.GA1877@darkstar.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=devel@acpica.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.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).