[Crash-utility] arm64: doesn't work for kernel v5.4?

[Bhupesh Sharma]

Hi Akashi,

On Thu, Oct 3, 2019 at 10:49 AM AKASHI Takahiro
<takahiro.akashi at linaro.org> wrote:
>
> Hi Dave,
>
> I tried to use crash v7.2.7 with kernel v5.4-rc1 on arm64.
>
> 1. VA_BITS_ACTUAL is missing in vmcoreinfo.
>    Does anyone work on fixing it on kernel side?
>    (just adding one or two lines though)

I am working on the changes in the vmcoreinfo after the 52-bit VA
changes from Steve were accepted in Linux 5.4-rc1 ("Support for 52-bit
virtual addressing in kernel space").

The suggestions during the last set of reviews (my v3 patchset) was to
introduce arch specific details like TCR_EL1.TxSZ in the vmcoreinfo
and also to wait for the 52-bit changes to make way upstream (as I
raised a couple of issues/kernel panic issues) earlier with the 52-bit
VA changes from Steve.

I plan to send out the v4 patchset later this week (and will Cc you).

Thanks,
Bhupesh


> 2. With a tweak above, I still fail to run crash with vmcore
>    seeing the following errors;
>    (I didn't dig into details)
>
>    crash-arm64: invalid kernel virtual address: ffff800010c689a8  type: "kernel_config_data"
>    WARNING: cannot read kernel_config_data
>    crash-arm64: invalid kernel virtual address: ffff80001177a160  type: "possible"
>    WARNING: cannot read cpu_possible_map
>    crash-arm64: invalid kernel virtual address: ffff80001177a140  type: "present"
>    WARNING: cannot read cpu_present_map
>    crash-arm64: invalid kernel virtual address: ffff80001177a120  type: "online"
>    WARNING: cannot read cpu_online_map
>    crash-arm64: invalid kernel virtual address: ffff80001177a188  type: "active"
>    WARNING: cannot read cpu_active_map
>    crash-arm64: invalid kernel virtual address: ffff80001196afe0  type: "shadow_timekeeper xtime_sec"
>    crash-arm64: invalid kernel virtual address: ffff800011782b3c  type: "init_uts_ns"
>    WARNING: invalid linux_banner pointer: ffff800010c500e8
>    crash: vmlinux.1003 and vmcore.1003 do not match!
>
> Have you noticed this issue?
>
> Thanks,
> -Takahiro Akashi
>
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility