linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Matt Fleming <matt@console-pimps.org>
Cc: Vasco Dias <rafa.vasco@gmail.com>,
	linux-kernel@vger.kernel.org, mikew@google.com
Subject: Re: Problem with efibootmgr on asus 1215b
Date: Mon, 12 Mar 2012 14:38:06 +0000	[thread overview]
Message-ID: <20120312143806.GB12382@srcf.ucam.org> (raw)
In-Reply-To: <1327060106.3618.53.camel@mfleming-mobl1.ger.corp.intel.com>

Somewhat late to this I know, but:

On Fri, Jan 20, 2012 at 11:48:26AM +0000, Matt Fleming wrote:

> [  441.370854] BUG: unable to handle kernel paging request at 00000000ffe1fbc8

So it's attempting a direct access to 00000000ffe1fbc8, which, if I had 
to guess, is probably where the flash is located. That makes sense from 
the perspective of it being used in efivars. The obvious sadness here is 
that it's doing this with a physical address rather than a virtual one.

It's possible that the machine is too broken to live - does Windows 
succeed in performing a UEFI install? If it does then I think we need to 
just accept that life is ugly and map the UEFI runtime areas with a 1:1 
mapping as well as into virtual address space. That would also fix the 
problem we see right now where the reboot call often uses a physical 
address rather than a virtual one.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2012-03-12 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-01  6:20 Problem with efibootmgr on asus 1215b Vasco Dias
2012-01-01  6:27 ` Vasco Dias
2012-01-20 11:48 ` Matt Fleming
2012-01-20 20:19   ` Mike Waychison
2012-01-21  3:26   ` Vasco Dias
2012-03-12 14:38   ` Matthew Garrett [this message]
2012-03-15  1:29     ` Motiejus Jakštys
2012-03-15  2:27       ` Vasco Dias
2012-03-15  3:06         ` Motiejus Jakštys
2012-03-15  4:23           ` Vasco Dias

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=20120312143806.GB12382@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=mikew@google.com \
    --cc=rafa.vasco@gmail.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).