From: "H. Peter Anvin" <hpa@zytor.com>
To: "John Z. Bohach" <jzb2@aexorsyst.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: large initramfs causes h/w reset after decompressing
Date: Thu, 14 Jul 2011 17:15:42 -0700 [thread overview]
Message-ID: <4E1F86AE.9090903@zytor.com> (raw)
In-Reply-To: <201107141635.07673.jzb2@aexorsyst.com>
On 07/14/2011 04:35 PM, John Z. Bohach wrote:
>>> But excuse my ignorance, I don't see the relevance of your
>>> question...the initramfs is part of the kernel itself...I simply
>>> load the kernel bzImage (all 890 MB) and that's where its all
>>> at...this is _not_ an initrd.
>>
>> Ah, interesting. You didn't say that. That does change some
>> things... I would not at all be surprised if the kernel decompressor
>> doesn't handle that very well...
>>
>
> 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.
-hpa
next prev parent reply other threads:[~2011-07-15 0:16 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 [this message]
2011-07-15 0:35 ` John Z. Bohach
-- 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=4E1F86AE.9090903@zytor.com \
--to=hpa@zytor.com \
--cc=jzb2@aexorsyst.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