This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.4
---
makedumpfile (1:1.6.5-1ubuntu1~18.04.4) bionic; urgency=medium
[ Thadeu Lima de Souza Cascardo ]
* Fixes for DLPAR cpu add operation (LP: #1828596)
- d/kdump-config.in: Add a reload command.
-
This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu2
---
makedumpfile (1:1.6.6-2ubuntu2) eoan; urgency=medium
[ Thadeu Lima de Souza Cascardo ]
* Fixes for DLPAR cpu add operation (LP: #1828596)
- d/kdump-config.in: Add a reload command.
- d/kdump-config.in:
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616
I tested kdump functionality using makedumpfile and kdump version
'1:1.6.5-1ubuntu1~18.04.4' from -proposed on kernel 5.3.0-24 kernel and
it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
I was able to verify the Eoan -proposed version (1:1.6.6-2ubuntu2) - the test
was to try a kdump using the makedumpfile from eoan-release, running kernel
5.3.0-26-generic; as expected, it fails with the error message "__vtop4_x86_64:
Can't get a valid pmd_pte." and fallbacks to cp.
When using
Hello Guilherme, or anyone else affected,
Accepted makedumpfile into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Guilherme, or anyone else affected,
Accepted makedumpfile into eoan-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
For this LP SRU submission, the following candidate packages were tested in
amd64 arch running kernel 5.3:
* Bionic, candidate version 1.6.5-1ubuntu1~18.04.4;
* Eoan, candidate version 1.6.6-2ubuntu2;
The test consisted in performing a kdump collection with the package
currently in -updates, and
This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu2
---
makedumpfile (1:1.6.6-4ubuntu2) focal; urgency=medium
* x86_64: Fix an error due to makedumpfile being out-of-sync with recent
kernels. To achieve that, add the following patch: "Increase
We still need to discuss the feasibility/need of inclusion of each fix
in Xenial.
** Description changed:
- Due to an issue in the kaslr address resolution in makedumpfile, we may
- get the following error when collecting a dump:
+ [Impact]
+
+ * Currently makedumpfile has 2 flaws due to: (a)
** Changed in: makedumpfile (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Eoan)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Undecided => Low
** Changed in: makedumpfile (Ubuntu Xenial)
Importance: Undecided =>
This proved not to be the case; in fact, the issue was caused by a
change in kernel that changed a bit and hence, the vmcore collection
failed.
The culprit was kernel commit 326e1b8f83a4 ("mm/sparsemem: introduce a
SECTION_IS_EARLY flag"), introduced in kernel 5.3.
The makedumpfile fix for this
13 matches
Mail list logo
