From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752102AbaHMSoy (ORCPT ); Wed, 13 Aug 2014 14:44:54 -0400 Received: from mail-we0-f170.google.com ([74.125.82.170]:61713 "EHLO mail-we0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751405AbaHMSow (ORCPT ); Wed, 13 Aug 2014 14:44:52 -0400 Date: Wed, 13 Aug 2014 19:44:49 +0100 From: Matt Fleming To: Mantas =?utf-8?Q?Mikul=C4=97nas?= Cc: Yinghai Lu , Matt Fleming , Linux Kernel Mailing List , linux-efi@vger.kernel.org Subject: Re: Loading initrd above 4G causes freeze on boot Message-ID: <20140813184449.GV15082@console-pimps.org> References: <53E62EEF.9040801@gmail.com> <20140809192302.GJ15082@console-pimps.org> <20140813140219.GP15082@console-pimps.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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