mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt.fleming@intel.com>
To: Robin Holt <holt@sgi.com>
Cc: Nathan Zimmer <nzimmer@sgi.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.com
Subject: Re: BUG: unable to handle kernel paging request at 000000effd870020
Date: Thu, 03 Jan 2013 15:50:55 +0000	[thread overview]
Message-ID: <1357228255.8203.10.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20130102210958.GD3470@sgi.com>

On Wed, 2013-01-02 at 15:09 -0600, Robin Holt wrote:
> On Wed, Jan 02, 2013 at 01:13:43PM -0600, Nathan Zimmer wrote:
> > On 01/02/2013 12:04 PM, H. Peter Anvin wrote:
> > >On 01/02/2013 09:21 AM, Nathan Zimmer wrote:
> > >>I am getting an early boot problem. It only happens on the larger of the
> > >>machines I haven't seen it crop up on machines with more then 512 GB of ram.
> > >>It shows in the latest linus kernel too.
> > >>
> > >>I am (wildly) guessing that what is happening is that the new_memmap that is
> > >>being passed to bios is somehow placed incorrectly.
> > >>I have come up with a workaround.  By placing it the DMA area the issue goes
> > >>away but that doesn't seem like a real fix.
> > >>
> > >What does your memory map look like?
> 
> We reported this a few times (Russ Anderson and I both).  The problem is
> at the point in boot where the efi_enter_virtual_mode callback is, there
> is no identity mapping for most of memory.  If the allocation happens
> to be above the 512GB (or maybe something lower than that) point, the
> BIOS is not able to address this via the physical address passed to it.

Right, looks like efi_call_phys_prelog() needs rewriting to install a
proper identity mapping that actually addresses *all* of available
memory, instead of just the first PGDIR_SIZE bytes.



  reply	other threads:[~2013-01-03 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 17:21 Nathan Zimmer
2013-01-02 18:04 ` H. Peter Anvin
2013-01-02 19:13   ` Nathan Zimmer
2013-01-02 21:09     ` Robin Holt
2013-01-03 15:50       ` Matt Fleming [this message]
2013-01-03 22:07         ` Nathan Zimmer

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=1357228255.8203.10.camel@mfleming-mobl1.ger.corp.intel.com \
    --to=matt.fleming@intel.com \
    --cc=holt@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nzimmer@sgi.com \
    --cc=tglx@linutronix.de \
    /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®