Re: [Crash-utility] How to open 32 bit dom0 kdump....

----- "Feng LI" <funglee(a)gmail.com&gt; wrote: > Thanks Dave, > > > I tried the patch you attached in the previous email. > > I am using the 32 bit crash utilities, and it seems to be able to load > the vmcore (64bit). But I still have a problem, the physical address > 0x7fed9050 was padding as 0x7fed9050000, and crash32 exited with error > message > > <readmem: 7fed9050000, PHYSADDR, "xen kdump p2m mfn list page", 4096, (ROE), 894f538> > addr: 7fed9050000 paddr: 7fed9050000 cnt: 4096 > crash32: read error: physical address: 7fed9050000 type: "xen kdump p2m mfn list page" > ... > ps. > The output of patched crash32 > The next problem is the p2m_mfn value that it read from the vmcore, which is a pretty obviously incorrect value of 0, and which is ultimately causing it to read from physical address 0: > This GDB was configured as "i686-pc-linux-gnu"... > GETBUF(128 -> 0) > GETBUF(1500 -> 1) > > > FREEBUF(1) > FREEBUF(0) > <readmem: c034e720, KVADDR, "kernel_config_data", 32768, (ROE), 898e8e0> > addr: c034e720 paddr: 34e720 cnt: 2272 > x86_xen_kdump_p2m_create: p2m_mfn: 0 > <readmem: 0, PHYSADDR, "xen kdump p2m mfn page", 4096, (ROE), 894f538> > addr: 0 paddr: 0 cnt: 4096 > 00000000: 7fed9050 7fed904c 7fed9058 7fed9054 > 00000010: 7fed9060 7fed905c f000859c f000ff53 > 00000020: f000fea5 f000e987 f0000c75 f0000c75 > 00000030: 99800b7c f0000c75 f000ef57 f000f545 > > > <readmem: 7fed9050000, PHYSADDR, "xen kdump p2m mfn list page", 4096, (ROE), 894f538> > addr: 7fed9050000 paddr: 7fed9050000 cnt: 4096 > crash32: read error: physical address: 7fed9050000 type: "xen kdump p2m mfn list page" > > crash32: cannot read xen kdump p2m mfn list page When you run with "crash -d1 ..." you should have seen a display of the p2m_mfn value that was read from the vmcore header. Can you attach that output? Dave -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility