From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761663AbcIZGqk (ORCPT ); Mon, 26 Sep 2016 02:46:40 -0400 Received: from terminus.zytor.com ([198.137.202.10]:35342 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966318AbcIZGqi (ORCPT ); Mon, 26 Sep 2016 02:46:38 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: <20160924153222.GA7405@sucs.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: Warning from free_init_pages with large initrd From: "H. Peter Anvin" Date: Sun, 25 Sep 2016 23:45:57 -0700 To: Sitsofe Wheeler CC: Thomas Gleixner , Ingo Molnar , x86@kernel.org, "linux-kernel@vger.kernel.org" Message-ID: <7AF2AE75-2F14-4581-B83F-DBAD6F99B8A7@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On September 25, 2016 11:22:04 PM PDT, Sitsofe Wheeler wrote: >On 26 September 2016 at 03:14, H. Peter Anvin wrote: >> On 09/24/16 08:32, Sitsofe Wheeler wrote: >>> >>> While trying to PXE boot a Fedora LiveISO on VMware ESXi the kernel >>> throws the following warning: >>> >> [...] >>> >>> The initrd is big because it holds all the files in the ISO (see >>> https://fedorahosted.org/cobbler/wiki/HowToPxeAnyLiveCd for how it >was >>> made). The issue was originally filed on >>> https://bugzilla.redhat.com/show_bug.cgi?id=1274966 but was usually >>> against older kernels... >> >> How big is big? > >The one that matches that backtrace is 1385 Mbytes and was made from a >Fedora rawhide ISO. Here are some sizes in megabytes from different >versions of Fedora: >960 20/initrd0.img >1416 21/initrd0.img >1379 22/initrd0.img >1430 23/initrd0.img >1492 24/initrd.img And they all fail? Also, is this BIOS or EFI? When loading under BIOS there is currently a 2 GB limit with most loaders; it would have been 4 GB except that Grub had a bug (sigh.) -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.