All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs
Date: Sat, 20 Mar 2010 13:16:01 -0700	[thread overview]
Message-ID: <4BA52D01.1070506@zytor.com> (raw)
In-Reply-To: <4BA52B6F.2060402@lbsd.net>

On 03/20/2010 01:09 PM, Nigel Kukard wrote:
>>>     
>> 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?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-03-20 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 11:12 [BUG] kernel 2.6.33-rc4 OOPS's with large initramfs Nigel Kukard
2010-01-24 23:26 ` H. Peter Anvin
2010-03-20 18:12   ` Nigel Kukard
2010-03-20 18:56     ` H. Peter Anvin
2010-03-20 20:09       ` Nigel Kukard
2010-03-20 20:16         ` H. Peter Anvin [this message]
2010-03-20 20:22           ` Nigel Kukard
2010-03-20 21:37             ` H. Peter Anvin
2010-03-20 22:26               ` Nigel Kukard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA52D01.1070506@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkukard@lbsd.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.