On Wednesday 08 March 2017 10:59 PM, Philip Prindeville wrote: > 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) No sure whats going here..but above does not look good. It should have values from /proc/iomem. > 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 Above wrong ranges might be the reason of failure most likely in crash_create_elf**_headers(). ~Pratyush
