linux-kernel - Re: BUG: unable to handle kernel paging request at 000000effd870020

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: <50E476C2.7060300@zytor.com>
Date:	Wed, 02 Jan 2013 10:04:50 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Nathan Zimmer <nzimmer@....com>
CC:	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
	matt.fleming@...el.com, tglx@...utronix.de, mingo@...hat.com
Subject: Re: BUG: unable to handle kernel paging request at 000000effd870020

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?

	-hpa

--
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/