Comment 16 for bug 1841288

Revision history for this message
Guilherme G. Piccoli (gpiccoli) wrote :

I was able to verify both releases.

*** Disco test, with kernel 5.0.0-32-generic ***
Running kdump-tools/makedumpfile from -updates pocket :

$ file vmcore.201911051825
vmcore.201911051825: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style

Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1.3 :

$ file dump.201911051840
dump.201911051840: Kdump compressed dump v6, system Linux, node gpiccoli-ppc64, release 5.0.0-32-generic,
version #34-Ubuntu SMP Wed Oct 2 02:06:32 UTC 2019, machine ppc64le, domain (none)

*** Bionic test, with kernel 5.0.0-32-generic ***
Running kdump-tools/makedumpfile from -updates pocket :

$ file vmcore.201911051957
vmcore.201911051957: ELF 64-bit LSB core file 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style

Also, saw the following message in console while makedumpfile was trying to
collect the compressed dump: "get_machdep_info_ppc64: Can't detect max_physmem_bits."

Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1~18.04.3 :

$ file dump.201911052003
dump.201911052003: Kdump compressed dump v6, system Linux, node bionic-ppc, release 5.0.0-32-generic,
version #34~18.04.2-Ubuntu SMP Thu Oct 10 10:35:58 UTC 2019, machine ppc64le, domain (none)