On 1/28/24 10:20, Heinrich Schuchardt wrote:
On 1/28/24 06:20, Bhumkar, Tejas Arvind wrote:
[AMD Official Use Only - General]
Hi Heinrich,
-----Original Message----- From: Heinrich Schuchardt xypron.glpk@gmx.de Sent: Wednesday, January 24, 2024 2:09 AM To: Bhumkar, Tejas Arvind tejas.arvind.bhumkar@amd.com Cc: u-boot@lists.denx.de; trini@konsulko.com; sjg@chromium.org; Simek, Michal michal.simek@amd.com; Abbarapu, Venkatesh venkatesh.abbarapu@amd.com; git@xilinx.com; Ilias Apalodimas ilias.apalodimas@linaro.org Subject: Re: [PATCH] efi_loader : Suppress error print message
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
On 1/23/24 19:53, Bhumkar, Tejas Arvind wrote:
[AMD Official Use Only - General]
Hi Ilias & Heinrich,
-----Original Message----- From: Heinrich Schuchardt xypron.glpk@gmx.de Sent: Tuesday, January 23, 2024 3:30 PM To: Ilias Apalodimas ilias.apalodimas@linaro.org; Bhumkar, Tejas Arvind tejas.arvind.bhumkar@amd.com Cc: u-boot@lists.denx.de; xypron.glpk@gmx.de; trini@konsulko.com; sjg@chromium.org; Simek, Michal michal.simek@amd.com; Abbarapu, Venkatesh venkatesh.abbarapu@amd.com; git@xilinx.com Subject: Re: [PATCH] efi_loader : Suppress error print message
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
On 1/23/24 09:33, Ilias Apalodimas wrote:
Hi Tejas,
On Mon, 22 Jan 2024 at 21:12, Tejas Bhumkar tejas.arvind.bhumkar@amd.com wrote: > > Currently, on certain Xilinx platforms, an issue has been > identified, manifesting as follows:
Hello Tejas,
thank you for bringing forward this issue.
Which defconfig are you relating to?
[Tejas]: Checking with xilinx_zynqmp_virt_defconfig
> > Starting kernel ... > > efi_free_pool: illegal free 0x0000000077830040 > efi_free_pool: illegal free 0x000000007782d040 > efi_free_pool: illegal free 0x000000007782c040 > > The issue arises when the ramdisk image is relocated, placing it > within the previously allocated EFI memory region( as EFI is > established quite early in U-Boot).
Which version of U-Boot are you on? Commit 06d514d77c37 ("lmb: consider EFI memory map") was meant to avoid such a situation.
[Tejas] : I'm verifying against the latest changes in the master branch. The introduction of commit 06d514d77c37 ("lmb: consider EFI memory map") has resolved the occurrence of the "efi_free_pool: illegal free" error. but, it leads to a new error, as detailed in the following patch: https://lore.kernel.org/all/20230212150706.2967007-1-sjoerd@collabora. com/
Could you, please, try to reproduce your issues with origin/master as of today and provide the full boot log. Please, also provide the output of the bdinfo and the printenv command as well as the sizes of the kernel and the RAM disk.
[Tejas]: I've provided two logs: one obtained from the latest u-boot origin/master, resulting in the "ERROR: reserving fdt memory region failed" error, and the other from reverting commit 06d514d77c37 ("lmb: consider EFI memory map"), which leads to the "efi_free_pool: illegal free" error.
Thank You, Tejas.
Where can I find these logs?
They were attached but you can see them for example here. https://lore.kernel.org/all/BL3PR12MB645027991850D2C0887FA80DD87F2@BL3PR12MB...
Thanks, Michal