From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, prabhakar.pkin@gmail.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
naresh.bhat@linaro.org, dann.frazier@canonical.com
Subject: Re: [edk2-devel] How /sys/firmware/fdt getting created
Date: Thu, 31 Oct 2019 12:16:42 +0000 [thread overview]
Message-ID: <20191031121642.GA16820@bivouac.eciton.net> (raw)
In-Reply-To: <2b268378-d9be-adb5-f139-a0ca8dab4329@redhat.com>
On Thu, Oct 31, 2019 at 11:07:52AM +0100, Laszlo Ersek wrote:
> +Leif, comment at bottom
Thanks Laszlo. +Dann, -kexec.
> On 10/30/19 09:16, Prabhakar Kushwaha wrote:
> >> So if you want to add these properties, you should add them there.
> >>
> >> Can you explain why doing this is necessary?
> >
> > I am trying to test kexec -p (kdump feature) on CentOS-release
> > 7.7.1908 and Ubuntu-18.04 distributions.
> >
> > "kexec -p" command show error on Ubuntu. While no error on CentOS
> >
> > CentOS:
> > $ kexec -p /boot/vmlinuz-`uname -r` --initrd=/boot/initramfs-`uname
> > -r`.img --reuse-cmdline
> > $ ==> No error
> >
> > Ubuntu
> > $ kexec -p /boot/vmlinuz-`uname -r` --initrd=/boot/initrd.img-`uname
> > -r` --reuse-cmdline
> > $ kexec: elfcorehdr doesn't fit cells-size.
> > $ kexec: setup_2nd_dtb failed.
> > $ kexec: load failed.
> > $ Cannot load /boot/vmlinuz-5.4.0-rc4+
> >
> > Note: Both CentOS and Ubuntu has Linux-5.4-rc4 tag.
> >
> > When i debugged further reason for Ubuntu error is due to
> > address-cells and size-cells as "1"
> > log from kexec tool :-
> > load_crashdump_segments: elfcorehdr 0x7f7cbfc000-0x7f7cbff7ff
> > read_1st_dtb: found name =dtb_sys /sys/firmware/fdt
> > get_cells_size: #address-cells:1 #size-cells:1
> >
> > On CentOS both values are "2".
> > log from kexec tool :-
> > load_crashdump_segments: elfcorehdr 0xbf98bf0000-0xbf98bf33ff
> > read_1st_dtb: found nmae=dtb_sys /sys/firmware/fdt
> > get_cells_size: #address-cells:2 #size-cells:2
> >
> > Note: Kexec tool read values from /sys/firmware/fdt.
> >
> > I am trying to figure out why 2 distributions showing different values.
>
> http://git.savannah.gnu.org/cgit/grub.git/commit/?id=347210a5d5ce655b95315f320faa515afb723c11
>
> Ubuntu probably ships a grub version that lacks this commit.
Yes, it came after the 18.04 release.
Dann: given that 18.04 is LTS, would it be reasonable to cherry-pick
this grub patch? I would consider the behaviour without it to be a
bug.
/
Leif
> (The commit was first released as part of upstream grub-2.04. I have no
> idea what version of grub is shipped in the CentOS distro you mention
> above -- it could be based upon upstream 2.04, or the upstream patch may
> have been backported to CentOS.)
>
> Thanks
> Laszlo
>
next prev parent reply other threads:[~2019-10-31 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 14:32 How /sys/firmware/fdt getting created prabhakar.pkin
2019-10-30 7:12 ` [edk2-devel] " Ard Biesheuvel
2019-10-30 7:36 ` Prabhakar Kushwaha
2019-10-30 7:44 ` Ard Biesheuvel
2019-10-30 8:16 ` Prabhakar Kushwaha
2019-10-31 10:07 ` Laszlo Ersek
2019-10-31 12:16 ` Leif Lindholm [this message]
2019-10-31 18:55 ` dann frazier
[not found] ` <15D2D0302F8A1888.21389@groups.io>
2019-10-31 20:34 ` dann frazier
2019-11-01 4:47 ` Prabhakar Kushwaha
2019-11-01 16:25 ` dann frazier
2019-11-04 4:11 ` Prabhakar Kushwaha
2019-10-31 20:29 ` Bhupesh Sharma
2019-11-01 4:51 ` Prabhakar Kushwaha
2019-11-01 5:46 ` Bhupesh Sharma
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-list 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=20191031121642.GA16820@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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