[U-Boot] [BUG] Odroid-C2 does not boot with U-Boot master anymore

Alexander Graf agraf at suse.de
Sat Dec 8 21:59:44 UTC 2018



On 08.12.18 14:16, Heinrich Schuchardt wrote:
> Hello Alex,
> 
> the patch 7a82c3051c8f ("efi_loader: Align runtime section to 64kb")
> currently breaks booting Linux on the Odroid-C2.
> 
> Output stops for kernel 4.18 after earlycon is replaced:
> [    0.012518] console [tty0] enabled
> [    0.015923] bootconsole [meson0] disabled
> Without your patch it continues.
> 
> The calculation introduced by the patch does what is expected:
> ram_start = 0x0000000000000000
> ram_end = 0x0000000080000000
> __efi_runtime_start = 0x000000007ff67118
> ~runtime_mask = 0xffffffffffff0000
> runtime_start = 0x000000007ff60000
> runtime_end = 0x000000007ff70000
> 
> These two memory reservation do not conflict with addresses in question:
> arch/arm/mach-meson/board-common.c(60) meson_board_add_reserved_memory:
> 0x0000000000000000-0x0000000001000000
> arch/arm/mach-meson/board-common.c(60) meson_board_add_reserved_memory:
> 0x0000000010000000-0x0000000010200000

We had an unaligned runtime start before already, so I don't quite
understand yet why increasing that to 64kb would break things.

I do fully understand that this patch *is* the culprit. I just would
like to understand why, so we can fix it appropriately.

Loic, this is probably also the failing patch for you?


Alex


More information about the U-Boot mailing list