* crash and makedumpfile with 5.3 missing memory in dump
@ 2019-11-01 1:48 Andi Kleen
2019-11-01 12:48 ` [Crash-utility] " Dave Anderson
0 siblings, 1 reply; 4+ messages in thread
From: Andi Kleen @ 2019-11-01 1:48 UTC (permalink / raw)
To: crash-utility; +Cc: k-hagio, kexec
Hi,
[I'm not sure if that is a crash or mkdumpfile problem]
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.
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Crash-utility] crash and makedumpfile with 5.3 missing memory in dump
2019-11-01 1:48 crash and makedumpfile with 5.3 missing memory in dump Andi Kleen
@ 2019-11-01 12:48 ` Dave Anderson
2019-11-01 13:05 ` John Donnelly
0 siblings, 1 reply; 4+ messages in thread
From: Dave Anderson @ 2019-11-01 12:48 UTC (permalink / raw)
To: Discussion list for crash utility usage, maintenance and development
Cc: kexec
----- Original Message -----
> Hi,
>
> [I'm not sure if that is a crash or mkdumpfile problem]
>
> 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.
>
> 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
>
Yeah, I'm not sure either. I've tested the github crash on kernels up to 5.4-rc5,
but only running on a live system. Given that the errors indicate "page excluded",
it looks like makedumpfile 1.6.6 may not cover 5.4 kernels. The makedumpfile git
log's master branch shows these as the last two commits:
commit 0a8b504102dbdb952b2e2e3ce15ae706165eba4e
Author: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Date: Thu Jun 27 08:42:40 2019 -0400
[v1.6.6] Update version
Update makedumpfile to version 1.6.6.
Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
commit 8c21fc7e7c52a2c3e0299e50a8b37becadfa77b4
Author: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Date: Thu Jun 13 15:32:55 2019 -0400
[PATCH] Support newer kernels up to v5.1
A new makedumpfile supports newer kernels:
- 4.20, 5.0, 5.1 (x86 FLATMEM)
- 4.20, 5.0, 5.1 (x86 SPARSEMEM)
- 4.20, 5.0, 5.1 (x86_64 SPARSEMEM)
Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Dave
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Crash-utility] crash and makedumpfile with 5.3 missing memory in dump
2019-11-01 12:48 ` [Crash-utility] " Dave Anderson
@ 2019-11-01 13:05 ` John Donnelly
2019-11-01 13:54 ` Kazuhito Hagio
0 siblings, 1 reply; 4+ messages in thread
From: John Donnelly @ 2019-11-01 13:05 UTC (permalink / raw)
To: Dave Anderson, Discussion list for crash utility usage,
maintenance and development
Cc: kexec
On 11/1/19 7:48 AM, Dave Anderson wrote:
SEE BELOW
>
>
> ----- Original Message -----
>> Hi,
>>
>> [I'm not sure if that is a crash or mkdumpfile problem]
>>
>> 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.
>>
>> 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
>>
>
> Yeah, I'm not sure either. I've tested the github crash on kernels up to 5.4-rc5,
> but only running on a live system. Given that the errors indicate "page excluded",
> it looks like makedumpfile 1.6.6 may not cover 5.4 kernels. The makedumpfile git
> log's master branch shows these as the last two commits:
>
> commit 0a8b504102dbdb952b2e2e3ce15ae706165eba4e
> Author: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
> Date: Thu Jun 27 08:42:40 2019 -0400
>
> [v1.6.6] Update version
>
> Update makedumpfile to version 1.6.6.
>
> Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
>
> commit 8c21fc7e7c52a2c3e0299e50a8b37becadfa77b4
> Author: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
> Date: Thu Jun 13 15:32:55 2019 -0400
>
> [PATCH] Support newer kernels up to v5.1
>
> A new makedumpfile supports newer kernels:
>
> - 4.20, 5.0, 5.1 (x86 FLATMEM)
> - 4.20, 5.0, 5.1 (x86 SPARSEMEM)
> - 4.20, 5.0, 5.1 (x86_64 SPARSEMEM)
>
> Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
>
> Dave
>
>
>
>
Hello,
Kazuhito Hagio asked me to share my test results on this patch for
makedumpfile :
https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_makedumpfile_code_ci_7bdb468c2c99dd780c9a5321f93c79cbfdce2527_&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=RRTWEGpecudcCrNL7TSmV5r2eIO7t_VrYruNXGGFhUE&s=BlcGeqwro6opkCKG9utpl8jfwoHMehRzt_V0nGz1fk4&e=
And I was successfully able to get vmcore dumps on vmlinuz-5.3.6 and
5.4.0-rc3 Intel ( x86-64) kernels.
Also I was able to use crash
7.2.6-2.el8
to review the dump. I didn't do a lot of crash comamnds but it did
process the vmcore
>
>
>
>> --
>> Crash-utility mailing list
>> Crash-utility@redhat.com
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_mailman_listinfo_crash-2Dutility&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=9yL0dKr8YPcdyw8vhjxi5rc_RZGNuf0lc0WRWsTNSlo&s=pVuyiNdvWTttmzeUYAUiduUcsdeYChqP6s1XzM3OxX4&e=
>>
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_mailman_listinfo_kexec&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=9yL0dKr8YPcdyw8vhjxi5rc_RZGNuf0lc0WRWsTNSlo&s=csTpNCSCrSAX9v0u0oSf00VFC7TzIABjI6cYaDBk6v0&e=
>
--
Thank You,
John
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: [Crash-utility] crash and makedumpfile with 5.3 missing memory in dump
2019-11-01 13:05 ` John Donnelly
@ 2019-11-01 13:54 ` Kazuhito Hagio
0 siblings, 0 replies; 4+ messages in thread
From: Kazuhito Hagio @ 2019-11-01 13:54 UTC (permalink / raw)
To: andi
Cc: kexec, Discussion list for crash utility usage,
maintenance and development
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
> >>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-11-01 13:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-01 1:48 crash and makedumpfile with 5.3 missing memory in dump Andi Kleen
2019-11-01 12:48 ` [Crash-utility] " Dave Anderson
2019-11-01 13:05 ` John Donnelly
2019-11-01 13:54 ` Kazuhito Hagio
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.