From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36727) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c2hUt-0006QL-L6 for qemu-devel@nongnu.org; Fri, 04 Nov 2016 12:37:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c2hUq-0006X9-DQ for qemu-devel@nongnu.org; Fri, 04 Nov 2016 12:37:43 -0400 Received: from mail-oi0-x243.google.com ([2607:f8b0:4003:c06::243]:35714) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c2hUq-0006Vg-5T for qemu-devel@nongnu.org; Fri, 04 Nov 2016 12:37:40 -0400 Received: by mail-oi0-x243.google.com with SMTP id v84so13524093oie.2 for ; Fri, 04 Nov 2016 09:37:40 -0700 (PDT) Sender: Richard Henderson References: <0f042e9b-f6a3-27c1-4ca0-94e13f8102d8@gmx.net> <20161104110813.GF9817@stefanha-x1.localdomain> From: Richard Henderson Message-ID: Date: Fri, 4 Nov 2016 10:37:35 -0600 MIME-Version: 1.0 In-Reply-To: <20161104110813.GF9817@stefanha-x1.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] alpha platform is missing files after initrd load List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , Dennis Luehring Cc: qemu-devel On 11/04/2016 05:08 AM, Stefan Hajnoczi wrote: > On Thu, Oct 20, 2016 at 12:45:37PM +0200, Dennis Luehring wrote: >> qemu: 2.7.x (git head) >> platform: Alpha (Clipper) > > Two options: > > 1. Not many people use Alpha. You may need to debug this yourself by > learning about the Linux alpha boot protocol (where the initramfs is > loaded and how big that region of memory may be). Then you can > verify the memory contents after QEMU has loaded the > kernel/initramfs using monitor commands to read memory. You may need > to look at QEMU's kernel/initramfs loading code to see what it's > doing. > > 2. If it worked in a previous QEMU version, please use git-bisect(1) to > find out which commit broke it. > > Good luck! We debugged this via private mail. For the 4.7 kernel, we had enough ram to unpack the (large) initrd; with the 4.8 kernel, we ran out. The 4.8 kernel did in fact print an (obscure) error message to that effect, which had not been noticed. I consider it a bug that the kernel does not treat this like any other failure to mount /root, via panic. Increasing ram from 1GB to 2GB allowed the 4.8 kernel to succeed in unpacking and booting off of the initrd. r~