From: David Laight <David.Laight@ACULAB.COM>
To: 'Nazerke Turtayeva' <nturtayeva@ucsb.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Question about unpacking large initramfs (>2G)
Date: Sun, 10 Mar 2024 19:43:18 +0000 [thread overview]
Message-ID: <a6dddd70d2844e438c2e6c205fa41b7d@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHY78BqCpMQptPN0SMaXuRqHOhYi+wnMEUSTYt7OHDZih4e7yQ@mail.gmail.com>
From: Nazerke Turtayeva
> Sent: 09 March 2024 03:11
>
> Recently I was testing LLMs for RISC-V on Linux plus Buildroot plus
> OpenSBI and Spike ISA Simulator. Nevertheless, given my rootfs end up
> being pretty large, 3.6GB at the moment, my linux boot falls short
> with "Initramfs unpacking failed: write error". I was trying to debug
> this problem last week, but got confused with code complexity :(.
I'd look at removing unwanted stuff from initramfs.
For our buildroot images we delete a lot of stuff - since it
can be found in the disk image after mounting the disk /.
(Although I'm not at all sure how much of the initramfs memory
is recovered - especially without pivot_root.
One thing I have noticed on x86 is that the .ko files are
massive because they contain a lot of debug info.
(I was looking at why it took so long between the last grub
message and the first kernel one.)
Also the default build also puts all the modules into the
initramfs - even though most can be loaded from the root filesystem.
David.
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2024-03-10 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 3:11 Nazerke Turtayeva
2024-03-10 19:43 ` David Laight [this message]
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=a6dddd70d2844e438c2e6c205fa41b7d@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nturtayeva@ucsb.edu \
/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
all inboxes | Powered by JetHome®