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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAPWNY8WdA+Q+WjXirGOsrYjMGp+69sCqYa8ST7_owQeVhQkT0w@mail.gmail.com>
Date:	Wed, 13 Aug 2014 19:38:14 +0300
From:	Mantas Mikulėnas <grawity@...il.com>
To:	Matt Fleming <matt@...sole-pimps.org>
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, Aug 13, 2014 at 5:02 PM, Matt Fleming <matt@...sole-pimps.org> wrote:
>
> On Sun, 10 Aug, at 09:43:32PM, Mantas Mikulėnas wrote:
> > On Sun, Aug 10, 2014 at 8:55 AM, Yinghai Lu <yinghai@...nel.org> wrote:
> > > On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas <grawity@...il.com> wrote:
> > >> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming <matt@...sole-pimps.org> wrote:
> > >> [However... Whether it's five chunks, four (after making the initrd
> > >> smaller), or just one (with your efi=nochunk), I noticed that it
> > >> *always* hangs during the *last* read, and the allocated memory always
> > >> ends at roughly the same address (0x137fffXXX). I wonder if it's
> > >> selecting a memory location already in use, or something like that...]
> > >>
> > >> (The laptop is Asus K52JT, AMI firmware v206, no updates available.)
> > >
> > > wonder if  efi_file_read return with wrong chunksize.
> > >
> > > Can you try attached patch ?
> >
> > Thanks, but it didn't change anything.
> >
> > (I tried adding some efi_printk's, and as far as I can see,
> > efi_file_read *doesn't* return at all.)
>
> Could you send you revert Yinghai's commit locally and send the dmesg
> from a successful boot? I'm wondering what other regions are around the
> 0x137fffxxx area.

Here you go.

-- 
Mantas Mikulėnas <grawity@...il.com>

View attachment "efi-bug-dmesg.txt" of type "text/plain" (100691 bytes)