From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752560Ab0CTWc2 (ORCPT ); Sat, 20 Mar 2010 18:32:28 -0400 Received: from authsmtp-0-4.virt.iitsp.net ([66.197.186.71]:52077 "EHLO authsmtp-0-4.virt.iitsp.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751397Ab0CTWc1 convert rfc822-to-8bit (ORCPT ); Sat, 20 Mar 2010 18:32:27 -0400 X-Greylist: delayed 397 seconds by postgrey-1.27 at vger.kernel.org; Sat, 20 Mar 2010 18:32:27 EDT Message-ID: <4BA54BA1.6020304@lbsd.net> Date: Sat, 20 Mar 2010 22:26:41 +0000 From: Nigel Kukard User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091201 IceDove/3.0 MIME-Version: 1.0 To: "H. Peter Anvin" CC: Linux Kernel Mailing List Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs References: <4B519F14.7020104@lbsd.net> <4B5CD711.7050204@zytor.com> <4BA51022.4010309@lbsd.net> <4BA51A48.6010509@zytor.com> <4BA52B6F.2060402@lbsd.net> <4BA52D01.1070506@zytor.com> <4BA52E9F.2080005@lbsd.net> <4BA54012.2080106@zytor.com> In-Reply-To: <4BA54012.2080106@zytor.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>>>> How much RAM are you giving your VM? The default for Qemu is 128 MB, >>>>> and if you have a 110 MB initramfs it's hardly surprising that you get >>>>> an out of memory error. >>>>> >>>>> >>>> The kernel now boots where it booted for my 64bit box. >>>> >>>> The main problem though is the instant reboots for bzip2 and lzma >>>> compressed initramfs images. The change for printf to /usr/bin/printf >>>> both render the sane end result when run with the same commandline being >>>> run in the makefile, so this isn't the issue. >>>> >>>> >>>> >>> Oh, you have *that* problem. >>> >>> What printf is being used? >>> >> coreutils 8.4 and 7.5 and bash all give me the same result for the >> commandline being run. This was just one of the things I tried and it >> didn't fix the problem. >> >> Here is what is run from the buildlog... >> (cat arch/x86/boot/compressed/vmlinux.bin | lzma -9 && printf >> \\150\\111\\241\\007) > arch/x86/boot/compressed/vmlinux.bin.lzma || (rm >> -f arch/x86/boot/compressed/vmlinux.bin.lzma ; false) >> >> I tested printf out... >> # printf \\150\\111\\241\\007 | xxd >> 0000000: 6849 a107 hI.. >> >> coreutils 7.5 >> # /usr/bin/printf \\150\\111\\241\\007 | xxd >> 0000000: 6849 a107 hI.. >> >> coreutils 8.4 >> # /usr/bin/printf \\150\\111\\241\\007 | xxd >> 0000000: 6849 a107 hI.. >> >> >> That confirms it? its not the b0rked printf issue afaics :) >> >> > Okay, so why the f*ck did you mention that instead of answering the > question I asked? *How much memory does your VM have?* Sorry, had 128M , now has 2G. The tests now render the same results between qemu and plain hardware. The reason I mentioned the printf issue is it causes this exact problem, I just wanted you to know that I've already touched that base to rule it out. Sorry.