> On Wed, Nov 20, 2019 at 10:03 PM John Donnelly <john.p.donnelly@xxxxxxxxxx> wrote: > > Hi, > > Recent test below > This is your makedumpfile pulled from sourceforge . Do you mean github? I don't remember pushing anything to sourceforge. Please share the exact branch name and the source URL for the makedumpfile you are using > It would be helpful if you bumped the VERSION and DATE to be certain we are using the correct pieces . You can print makedumpfile version in your scriptware. It lets you know the latest makedumpfile version. Note that this indicates the latest released version and not the development branch. The development branch is for things under test (like this change) and being stabilized whereas the released version contains a bump to a new VERSION number and DATE at which a release is made. # makedumpfile -v makedumpfile: version 1.6.6 (released on 27 Jun 2019) lzo enabled > kdump: saving vmcore > makedumpfile 1.6.6, 27 Jun 2019. > sadump: unsupported architecture > phys_start phys_end virt_start virt_end > LOAD[ 0] 92a80000 94fe0000 ffff800010080000 ffff8000125e0000 > LOAD[ 1] 90000000 92000000 ffffc00010000000 ffffc00012000000 > LOAD[ 2] 928c0000 dfe00000 ffffc000128c0000 ffffc0005fe00000 > LOAD[ 3] ffe00000 fffa0000 ffffc0007fe00000 ffffc0007ffa0000 > LOAD[ 4] 880000000 1000000000 ffffc00800000000 ffffc00f80000000 > LOAD[ 5] 8800000000 bff7030000 ffffc08780000000 ffffc0bf77030000 > LOAD[ 6] bff7060000 bff72b0000 ffffc0bf77060000 ffffc0bf772b0000 > LOAD[ 7] bff72f0000 bff8030000 ffffc0bf772f0000 ffffc0bf78030000 > LOAD[ 8] bff8050000 bff8070000 ffffc0bf78050000 ffffc0bf78070000 > LOAD[ 9] bff80d0000 bff8270000 ffffc0bf780d0000 ffffc0bf78270000 > LOAD[10] bff8280000 bff83d0000 ffffc0bf78280000 ffffc0bf783d0000> > LOAD[11] bff8870000 bffc1a0000 ffffc0bf78870000 ffffc0bf7c1a0000 > LOAD[12] bffc1c0000 bffc1d0000 ffffc0bf7c1c0000 ffffc0bf7c1d0000 > LOAD[13] bffe210000 bfffd10000 ffffc0bf7e210000 ffffc0bf7fd10000 > LOAD[14] bfffd40000 bfffd50000 ffffc0bf7fd40000 ffffc0bf7fd50000 > LOAD[15] bfffe00000 c000000000 ffffc0bf7fe00000 ffffc0bf80000000 > Linux kdump > VMCOREINFO : OSRELEASE=5.4.0-rc8 PAGESIZE=65536 > page_size : 65536 SYMBOL(init_uts_ns)=ffff800011a65ca8 SYMBOL(node_online_map)=ffff800011a5d490 SYMBOL(swapper_pg_dir)=ffff8000112f0000 SYMBOL(_stext)=ffff800010081000 SYMBOL(vmap_area_list)=ffff800011b29a98 SYMBOL(mem_section)=ffff00bf7be7e300 LENGTH(mem_section)=64 SIZE(mem_section)=16 OFFSET(mem_section.section_mem_map)=0 NUMBER(MAX_PHYSMEM_BITS)=48 OFFSET(vmap_area.va_start)=0 OFFSET(vmap_area.list)=40 LENGTH(zone.free_area)=14 SYMBOL(log_buf)=ffff800011ada808 SYMBOL(log_buf_len)=ffff800011ada810 SYMBOL(log_first_idx)=ffff800011e772d4 SYMBOL(clear_idx)=ffff800011e74d20 SYMBOL(log_next_idx)=ffff800011e772e0 SIZE(printk_log)=16 OFFSET(printk_log.ts_nsec)=0 OFFSET(printk_log.len)=8 OFFSET(printk_log.text_len)=10 OFFSET(printk_log.dict_len)=12 LENGTH(free_area.free_list)=6 NUMBER(NR_FREE_PAGES)=0 NUMBER(PG_lru)=4 NUMBER(PG_private)=13 NUMBER(PG_swapcache)=10 NUMBER(PG_swapbacked)=19 NUMBER(PG_slab)=9 NUMBER(PG_hwpoison)=22 NUMBER(PG_head_mask)=65536 NUMBER(PAGE_BUDDY_MAPCOUNT_VALUE)=-129 NUMBER(HUGETLB_PAGE_DTOR)=2 NUMBER(PAGE_OFFLINE_MAPCOUNT_VALUE)=-257 NUMBER(VA_BITS)=48 NUMBER(kimage_voffset)=0xffff7fff7d600000 NUMBER(PHYS_OFFSET)=0x80000000 NUMBER(tcr_el1_t1sz)=0x10 KERNELOFFSET=0 CRASHTIME=1574266958 > phys_base : 80000000 (vmcoreinfo) > max_mapnr : c00000 > There is enough free memory to be done in one cycle. > Buffer size for the cyclic mode: 3145728 > va_bits : 47 > page_offset : ffffc00000000000 > kdump: saving vmcore failed You again seem to be using an old/incorrect version of makedumpfile. As you can see here from [0] and [1] the newer makedumpfile patches I posted print where the va_bits are derived from - _stext symbol or vmcoreinfo. Since you are running a kdump test, it should print something like this for va_bits if you have the correct makedumpfile changes compiled in and installed (via make install) - notice the source from where va_bits is determined properly is printed in brackets: phys_base : 80000000 (vmcoreinfo) max_mapnr : 97fd00 There is enough free memory to be done in one cycle. Buffer size for the cyclic mode: 2490176 va_bits : 48 (vmcoreinfo) page_offset : ffff000000000000 (approximation) kimage_voffset : fffeffff8fc00000 max_physmem_bits : 52 section_size_bits: 30 Regards, Bhupesh [0]. <https://github.com/bhupesh-sharma/makedumpfile/blob/52-bit-va-support-via-vmcore-upstream-v4/arch/arm64.c#L468> [1]. <https://github.com/bhupesh-sharma/makedumpfile/blob/52-bit-va-support-via-vmcore-upstream-v4/arch/arm64.c#L511> _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
