search for: 5924bbecd0267d87c24110cbe2041b

...ng loaded. Is there a PT_LOAD that covers that address? Is the bootloader loading it? That issue is gone. Not sure what changed, but looks something was fixed in LLD during last week. Latest status of booting linux kernel is next currently: At this location, https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/boot/compressed/head_64.S#L424 kernel calls extract_kernel(). And 2 lines below it tries to jmp to the address of decompressed kernel and fails to do that for me. extract_kernel() method is: https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x8...

...investigation from my side. I traced kernel linked with LLD to find where it fails. LLD linked kernel starts execution and then I came up to protected_mode_jump? function, which intention to jump to startup_64: jmpl *%eax # Jump to the 32-bit entrypoint (https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/boot/pmjump.S#L76) (https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/kernel/head_64.S#L48) It does not happen. Code executes right before jmpl and then fail on this call for me, so startup_64 never called. startup_64 is a part of vmlinux...

>That address seems to come from >here: https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/boot/pm.c#L124 > >``` >protected_mode_jump(boot_params.hdr.code32_start, > (u32)&boot_params + (ds() << 4)); >``` > >That boot_params.hdr.code32_start field is probably either invalid (bad reloc or something else causing the bootloader to >calc...