[Bug 1741860] Re: Use the kernel default for crashkernel offset
Launchpad Bug Tracker
1741860 at bugs.launchpad.net
Mon Nov 11 15:56:26 UTC 2019
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1.3
makedumpfile (1:1.6.5-1ubuntu1.3) disco; urgency=medium
[ Guilherme G. Piccoli ]
* Add kdump retry/delay mechanism when dumping over network (LP: #1681909)
[ Thadeu Lima de Souza Cascardo ]
* Use maxcpus instead of nr_cpus on ppc64el. (LP: #1828597)
* ppc64: increase MAX_PHYSMEM_BITS to 2PB (LP: #1841288)
[ Connor Kuehl ]
* Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)
-- Thadeu Lima de Souza Cascardo <cascardo at canonical.com> Wed, 09 Oct
2019 15:33:57 -0300
** Changed in: makedumpfile (Ubuntu Disco)
Status: Fix Committed => Fix Released
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
Use the kernel default for crashkernel offset
Status in The Ubuntu-power-systems project:
Status in makedumpfile package in Ubuntu:
Status in makedumpfile source package in Xenial:
Status in makedumpfile source package in Bionic:
Status in makedumpfile source package in Disco:
Status in makedumpfile source package in Eoan:
* The value chosen for ppc64el of 128MB aligns with that of the
kernel default. That may change some day, so it would be best to let
the kernel decide what value it should use. If the value does change
and the kernel is not allowed to choose a value, this may stop the
kernel from booting on a production system.
Run `cat /etc/default/grub.d/kdump-tools.cfg`
* Expected result: there is no offset specified at the end of the
line (.e.g, @128M).
* Actual result: For Xenial, Bionic, Disco, and Eoan there are
* Right now, the offset described in the kdump-tools.cfg aligns with
that of what the kernel would select, so since they are the same we
would expect no change in operation.
Original bug description follows:
== Comment: #0 - Hari Krishna Bathini <hbathini at in.ibm.com> - 2018-01-08 01:06:41 ==
A default offset of 128MB is enforced for crashkernel by kdump-tools utility
overriding the kernel default.
While the kernel default offset for crashkernel is also 128MB, that may change
and the right thing to do would be to let the kernel decide on the offset of
crashkernel in the default scenario..
Get rid of "@128M" in kdump-tools.cfg file
Contact Information = hbathini at in.ibm.com
Machine Type = na
A debugger is not configured
---Steps to Reproduce---
# cat /etc/default/grub.d/kdump-tools.cfg
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M at 128M"
The offset is specified via kdump-tools where as the kernel may be the right place to
set an offset by default..
Userspace tool common name: kdump-tools
The userspace tool has the following bit modes: 64-bit
Userspace rpm: kdump-tools
Userspace tool obtained from project website: na
*Additional Instructions for hbathini at in.ibm.com:
-Attach ltrace and strace of userspace application.
== Comment: #3 - MAMATHA INAMDAR <mainamdar at in.ibm.com> - 2018-01-08 03:05:05 ==
This bug is opened to follow-up other bug based on the comment 19
https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad 1676884 )
To manage notifications about this bug go to:
More information about the Ubuntu-sponsors