From: "John Z. Bohach" <jzb2@aexorsyst.com>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: large initramfs causes h/w reset after decompressing
Date: Thu, 14 Jul 2011 17:35:36 -0700 [thread overview]
Message-ID: <201107141735.36175.jzb2@aexorsyst.com> (raw)
In-Reply-To: <4E1F86AE.9090903@zytor.com>
> > Sorry, I thought initramfs would be clear on its own that its not
> > initrd, but I guess some people do use it interchangeably. Anyway,
> > I have some experience in programming, so is there anything you
> > could suggest that I might tweak to test your theory on the
> > decompressor? Or would this be more of a kernel VM allocator
> > issue? Also, would ramdisk_size have any bearing on this?
>
> initramfs can be built in or loaded via the initrd protocol.
>
> Anyway, it's hard to say for sure what to look for, but the first
> thing is to try to "fence" the problem... that is, establish the
> latest point which is successfully crossed and the earliest point
> which is not.
Fair enough...I'll start with a 2 GB boundary and see where it takes
me...thanks for you feedback.
--john
next prev parent reply other threads:[~2011-07-15 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 16:06 large initramfs causes h/w reset after decompressing John Z. Bohach
2011-07-14 21:14 ` H. Peter Anvin
2011-07-14 22:32 ` John Z. Bohach
2011-07-14 23:26 ` H. Peter Anvin
2011-07-14 23:35 ` John Z. Bohach
2011-07-15 0:15 ` H. Peter Anvin
2011-07-15 0:35 ` John Z. Bohach [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-14 16:37 John Z. Bohach
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=201107141735.36175.jzb2@aexorsyst.com \
--to=jzb2@aexorsyst.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox