linux-kernel - Re: Loading initrd above 4G causes freeze on boot

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Aug 2014 19:44:49 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Mantas Mikulėnas <grawity@...il.com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-efi@...r.kernel.org
Subject: Re: Loading initrd above 4G causes freeze on boot

On Wed, 13 Aug, at 07:38:14PM, Mantas Mikulėnas wrote:
> 
> Here you go.
> 
> [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000137ffffff] usable

[...]

> [    0.000000] reserve setup_data: [mem 0x0000000100000000-0x0000000137ffffff] usable

[...]

> [    0.000000] efi: mem201: type=7, attr=0xf, range=[0x0000000100000000-0x0000000138000000) (896MB)

Nothing crazy here, unless we're getting the calculation wrong and
reading past the buffer, the code looks OK though. Or something like the
last page or so of that memory isn't actually free even though the
firmware tells us it is.

At this point, I think modifying the max address is the best way to
debug this further, and figure out what address causes the hang.

-- 
Matt Fleming, Intel Open Source Technology Center
--
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/