linux-kernel - Re: Problem with efibootmgr on asus 1215b

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120312143806.GB12382@srcf.ucam.org>
Date:	Mon, 12 Mar 2012 14:38:06 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	Vasco Dias <rafa.vasco@...il.com>, linux-kernel@...r.kernel.org,
	mikew@...gle.com
Subject: Re: Problem with efibootmgr on asus 1215b

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@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/