Questions about kexec-tools (resend to list)

[philipp@xxxxxxxxxxxxxxxxx (Philip Prindeville)]

> On Mar 8, 2017, at 10:29 AM, Philip Prindeville <philipp at fedoraproject.org> wrote:
> 
>> 
>> Humm..can you pl run with -d and share debug output.
> 
> Sure thing:
> 
> root at PowercodeBMU:/# file /tmp/boot/boot/vmlinuz 
> /tmp/boot/boot/vmlinuz: Linux kernel x86 boot executable bzImage, version 4.4.14 (philipp at ubuntu16) #10 Wed Mar 8 17:19:10 UTC 2017, RO-rootFS, swap_dev 0x2, Normal VGA
> root at PowercodeBMU:/# 
> root at PowercodeBMU:/# kexec -d -p /tmp/boot/boot/vmlinuz --reuse-cmdline --append="irqpoll maxcpus=1 reset_devices 1"
> Try gzip decompression.
> Try LZMA decompression.
> lzma_decompress_file: read on /tmp/boot/boot/vmlinuz of 65536 bytes failed
> kernel: 0x7f18b2596020 kernel_size: 0x27af20
> MEMORY RANGES
> 0000000000000100-0000000000099bff (0)
> 0000000000099c00-000000000009ffff (1)
> 00000000000e0000-00000000000fffff (1)
> 0000000000100000-00000000cc309fff (0)
> 00000000cc30a000-00000000cc310fff (3)
> 00000000cc311000-00000000cc946fff (0)
> 00000000cc947000-00000000ccb5bfff (1)
> 00000000ccb5c000-00000000db8b4fff (0)
> 00000000db8b5000-00000000db957fff (1)
> 00000000db958000-00000000db96dfff (2)
> 00000000db96e000-00000000dbac3fff (3)
> 00000000dbac4000-00000000dbffefff (1)
> 00000000dbfff000-00000000dbffffff (0)
> 00000000dd000000-00000000df1fffff (1)
> 00000000f8000000-00000000fbffffff (1)
> 00000000fec00000-00000000fec00fff (1)
> 00000000fed00000-00000000fed03fff (1)
> 00000000fed1c000-00000000fed1ffff (1)
> 00000000fee00000-00000000fee00fff (1)
> 00000000ff000000-00000000ffffffff (1)
> 0000000100000000-000000041fdfffff (0)
> CRASH MEMORY RANGES
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000005-ffffffffffffffff (3)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (2)
> 0000000000000005-ffffffffffffffff (3)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (1)
> 0000000000000005-ffffffffffffffff (0)
> 0000000000000130-00007f18b2a21938 (0)
> Cannot get kernel page_offset_base symbol address
> kernel symbol _stext vaddr =      a0000000005
> kernel vaddr = 0xffffffff81000000 size = 0x818000
> Memmap after adding segment
> 0000000000000000-000000000009ffff (0)
> Cannot load /tmp/boot/boot/vmlinuz
> root at PowercodeBMU:/# 
> 
> -Philip


The above memory ranges look highly suspect.

Anyone have any ideas where I should start digging to figure out where things are going sideways?

I?m using 2.0.14 on a Linux 4.4.19 kernel, with gcc 5.3.0 and MUSL 1.1.16.

Thanks,

-Philip