[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BA52E9F.2080005@lbsd.net>
Date: Sat, 20 Mar 2010 20:22:55 +0000
From: Nigel Kukard <nkukard@...d.net>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs
>>> 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 :)
-N
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists