[Crash-utility] crash and makedumpfile with 5.3 missing memory in dump

[Kazuhito Hagio]

Hi,

> -----Original Message-----
> >> I'm trying to use crash to read a makedumpfile vmcore from 5.3, but I always
> >> end up with an error when opening the dump.

As John mentioned, makedumpfile needs the following patch to work with
5.3 or later correctly.  This patch is in the devel branch now.
Please try the latest one.
https://sourceforge.net/p/makedumpfile/code/ci/7bdb468c2c99dd780c9a5321f93c79cbfdce2527/

Although the commit message says that it causes makedumpfile an error,
I saw some patterns later that makedumpfile created a broken dumpfile
without error.

(Usually I had to wrote "Required for kernel 5.3" in the commit message,
but forgot it at that time..)

Thanks,
Kazu

> >>
> >> I'm using the latest github crash
> >>
> >> crash 7.2.7++
> >> ...
> >>   crash: page excluded: kernel virtual address: ffffffff82110370  type:
> >>   "possible"
> >>   WARNING: cannot read cpu_possible_map
> >>   crash: page excluded: kernel virtual address: ffffffff82110360  type:
> >>   "present"
> >>   WARNING: cannot read cpu_present_map
> >>   crash: page excluded: kernel virtual address: ffffffff82110368  type:
> >>   "online"
> >>   WARNING: cannot read cpu_online_map
> >>   crash: page excluded: kernel virtual address: ffffffff82110358  type:
> >>   "active"
> >>   WARNING: cannot read cpu_active_map
> >>   crash: page excluded: kernel virtual address: ffffffff82011544  type:
> >>   "init_uts_ns"
> >>   crash: page excluded: kernel virtual address: ffffffff82110360  type:
> >>   "cpu_present_map"
> >>   crash: page excluded: kernel virtual address: ffffffff82110360  type:
> >>   "cpu_present_map"
> >>   WARNING: ORC unwinder: cannot read lookup_num_blocks
> >>   crash: seek error: kernel virtual address: ffff88822dffb000  type:
> >>   "memory section root table"
> >>
> >> The dump is created with the latest makedumpfile release
> >>
> >> makedumpfile: version 1.6.6 (released on 27 Jun 2019)
> >>
> >> It complains that it doesn't support the kernel
> >>
> >> Any ideas?
> >>
> >> -Andi
> >>