From: Andrew Jeffery <andrew@aj.id.au>
To: Patrick Venture <venture@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Merging up to OpenBMC v2.2 from v2.1 - boot problem, invalid ramdisk format
Date: Wed, 27 Jun 2018 10:40:00 +0930 [thread overview]
Message-ID: <1530061800.2502410.1421595168.7609B886@webmail.messagingengine.com> (raw)
In-Reply-To: <CAO=notzW-7ffufai7uSQ8FtMvJrGT56F18TM5zm7L9+opFKb0Q@mail.gmail.com>
On Wed, 27 Jun 2018, at 01:49, Patrick Venture wrote:
> I assume this is just a recipe change such that I need to now specify
> something -- with OpenBMC v2.1 I see:
>
> """
> U-Boot 2016.07 (May 24 2018 - 12:55:55 -0700)
>
> DRAM: 120 MiB
> WARNING: Caches not enabled
> Flash: 64 MiB
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: aspeednic#0
> Error: aspeednic#0 address not set.
>
> Hit any key to stop autoboot: 0
> ## Loading kernel from FIT Image at 20080000 ...
> Using 'conf@1' configuration
> Trying 'kernel@1' kernel subimage
> Description: Linux kernel
> Type: Kernel Image
> Compression: uncompressed
> Data Start: 0x20080128
> Data Size: 1721352 Bytes = 1.6 MiB
> Architecture: ARM
> OS: Linux
> Load Address: 0x40008000
> Entry Point: 0x40008000
> Hash algo: sha1
> Hash value: de140d9d803c22f731c4d99a4250979489383a81
> Verifying Hash Integrity ... sha1+ OK
> ## Loading ramdisk from FIT Image at 20080000 ...
> Using 'conf@1' configuration
> Trying 'ramdisk@1' ramdisk subimage
> Description: obmc-phosphor-initramfs
> Type: RAMDisk Image
> Compression: lzma compressed
> Data Start: 0x2022ad00
> Data Size: 1592362 Bytes = 1.5 MiB
> Architecture: ARM
> OS: Linux
> Load Address: unavailable
> Entry Point: unavailable
> Hash algo: sha1
> Hash value: 9f6f2feb110e27e07f81bb60bb372b4083672f19
> Verifying Hash Integrity ... sha1+ OK
> ## Loading fdt from FIT Image at 20080000 ...
> Using 'conf@1' configuration
> Trying 'fdt@1' fdt subimage
> Description: Flattened Device Tree blob
> Type: Flat Device Tree
> Compression: uncompressed
> Data Start: 0x20224624
> Data Size: 26139 Bytes = 25.5 KiB
> Architecture: ARM
> Hash algo: sha1
> Hash value: 37864a4c4a608d5f4e370bbccf93ccbe3e77462d
> Verifying Hash Integrity ... sha1+ OK
> Booting using the fdt blob at 0x20224624
> Loading Kernel Image ... OK
> Loading Ramdisk to 47213000, end 47397c2a ... OK
> Loading Device Tree to 47209000, end 4721261a ... OK
>
> Starting kernel ...
> """
>
> With v2.2 I see:
> """
> U-Boot 2016.07 (Jun 25 2018 - 10:07:57 -0700)
>
> DRAM: 120 MiB
> WARNING: Caches not enabled
> Flash: 64 MiB
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: aspeednic#0
> Error: aspeednic#0 address not set.
>
> Hit any key to stop autoboot: 0
> libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
From below it looks like u-boot finds the kernel in the FIT, but your ramdisk is "corrupt". The error above suggests something is missing from the FIT. Can you check the initrd/ramdisk node in your FIT to make sure it is present and uses all the correct options and paths with respect to the initrd you intended to package?
Might also be helpful to provide the content of the .its file.
> ## Loading kernel from FIT Image at 20080000 ...
> Using 'conf@aspeed-bmc-quanta-q71l.dtb' configuration
> Trying 'kernel@1' kernel subimage
> Description: Linux kernel
> Type: Kernel Image
> Compression: uncompressed
> Data Start: 0x20080124
> Data Size: 1723192 Bytes = 1.6 MiB
> Architecture: ARM
> OS: Linux
> Load Address: 0x40008000
> Entry Point: 0x40008000
> Hash algo: sha1
> Hash value: 95ed76c9361d9f6f991a6a859a06eb7626af80df
> Verifying Hash Integrity ... sha1+ OK
> Wrong Ramdisk Image Format
> Ramdisk image is corrupt or invalid
> """
>
> I figured I'd reach out first as I'm sure this will be familiar to someone :D
>
> Patrick
next prev parent reply other threads:[~2018-06-27 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 16:19 Merging up to OpenBMC v2.2 from v2.1 - boot problem, invalid ramdisk format Patrick Venture
2018-06-27 1:10 ` Andrew Jeffery [this message]
2018-06-27 1:40 ` Kun Yi
2018-06-27 14:39 ` Patrick Venture
2018-06-27 14:38 ` Patrick Venture
2018-06-27 15:39 ` Patrick Venture
2018-06-27 21:17 ` Patrick Venture
2018-06-27 22:58 ` Patrick Venture
2018-06-28 1:30 ` Joel Stanley
2018-06-28 14:33 ` Patrick Venture
2018-07-02 17:13 ` Patrick Venture
2018-07-02 17:14 ` Patrick Venture
2018-07-02 17:39 ` Patrick Venture
2018-07-02 17:43 ` Patrick Venture
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=1530061800.2502410.1421595168.7609B886@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.com \
/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;
as well as URLs for NNTP newsgroup(s).