summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Release 1.6.7-2 to unstabledebian/1%1.6.7-2archive/debian/1%1.6.7-2Thadeu Lima de Souza Cascardo2020-04-17
| | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@cascardo.eti.br>
* Switch to debhelper-compat 12.Thadeu Lima de Souza Cascardo2020-04-17
| | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@cascardo.eti.br>
* Remove upstart support.Thadeu Lima de Souza Cascardo2020-04-17
| | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@cascardo.eti.br>
* Commit patch queue (exported by git-debrebase)debian/1%1.6.7-1archive/debian/1%1.6.7-1Thadeu Lima de Souza Cascardo2020-03-03
| | | | [git-debrebase make-patches: export and commit patches]
* Release 1.6.7-1 to unstableThadeu Lima de Souza Cascardo2020-03-03
|
* Skip initrd generation during postinst.Thadeu Lima de Souza Cascardo2020-03-03
| | | | | | | | | When installing kdump-tools on a chroot, the kernel might not be available until boot. initrd generation is already taken care of when kdump-tools is first loaded, so doing it during postinst is no longer necessary. Closes: #856594
* Declare fast forward / record previous workThadeu Lima de Souza Cascardo2020-03-03
|\ | | | | | | [git-debrebase pseudomerge: quick]
| * Release 1.6.6-4 to unstabledebian/1%1.6.6-4archive/debian/1%1.6.6-4Thadeu Lima de Souza Cascardo2019-12-18
| | | | | | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Set Rules-Requires-Root to noThadeu Lima de Souza Cascardo2019-12-18
| | | | | | | | | | | | | | | | | | | | | | There is no need for root to build the package, and all files belong to root anyway. dh_builddeb will end up calling dpkg-deb with --root-owner-group, which will do the right thing. A test build resulted in the same package contents, the binary packages were reproducible bit-by-bit by changing only that. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * udev: hotplug: use try-reloadThadeu Lima de Souza Cascardo2019-12-17
| | | | | | | | | | | | | | We should not reload kdump unconditionally after a hotplug event, but only reload it when it was loaded already, which is what try-reload does. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * kdump-config: implement try-reloadThadeu Lima de Souza Cascardo2019-12-17
| | | | | | | | | | | | | | Use a lock file to allow try-reload to be run concurrently, and verify that kdump is loaded before trying to unload and load again. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)Thadeu Lima de Souza Cascardo2019-12-17
| |
| * Release 1.6.6-3 to unstabledebian/1%1.6.6-3archive/debian/1%1.6.6-3Thadeu Lima de Souza Cascardo2019-09-18
| | | | | | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Use reset_devices as a cmdline parameter.Thadeu Lima de Souza Cascardo2019-09-18
| | | | | | | | | | | | | | | | reset_devices will be used by some drivers to do a special reset during kdump. This will allow some systems with some devices that use such drivers to kdump instead of fail to probe them. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Use kdump-config reload after cpu or memory hotplug.Thadeu Lima de Souza Cascardo2019-09-18
| | | | | | | | | | | | | | | | | | | | | | | | The solution used to allow multiple reloads during a hotplug event ended up not working because udev won't execute two commands under a shell. So, using a single command that reloads and do not interact with systemd should work here. As an extra, this adds support for other init systems. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Add a reload command.Thadeu Lima de Souza Cascardo2019-09-18
| | | | | | | | | | | | | | kdump-config reload will unload the current kdump kernel, and load a new one. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Release 1.6.6-2 to unstabledebian/1%1.6.6-2archive/debian/1%1.6.6-2Thadeu Lima de Souza Cascardo2019-07-20
| | | | | | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Allow proper reload of kdump after multiple hotplug events.Thadeu Lima de Souza Cascardo2019-07-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a CPU is hotplugged, multiple events will be issued for each CPU thread getting online. On a POWER system, that usually means 8 threads. Those 8 events will cause systemd to consider the multiple restarts as failed. One alternative fix would be setting StartLimitIntervalSec to 0, but that would apply to all cases where those failures might happen, not only on the hotplug case. Instead, we use reset-failed before try-restart, which will allow those multiple restarts to happen on a short interval. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Reload kdump when CPU is brought online.Thadeu Lima de Souza Cascardo2019-07-20
| | | | | | | | | | | | | | This is needed on ppc64el, as CPUs are not added or removed, but simply brought online. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
| * Use maxcpus instead of nr_cpus on ppc64el.Thadeu Lima de Souza Cascardo2019-07-20
| | | | | | | | | | | | | | | | | | On a kdump kernel, nr_cpus is broken, and it will take some time to be properly fixed. In the meantime, we can just use maxcpus. In the worst case, we will get an OOM and reboot instead of panicing too early during boot. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
| * Use a different service for vmcore dump.Thadeu Lima de Souza Cascardo2019-07-20
| | | | | | | | | | | | | | | | | | | | | | | | During the dump itself, spurious CPU or memory hotplug events will cause the dump to fail, because the service would be restarted, and an old incomplete dump would prevent the dump from being collected. This work also allows us to stop requiring network during kdump loading, and sets the way to stop requiring network when the dump is not over the network. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Add kdump retry/delay mechanism when dumping over networkGuilherme G. Piccoli2019-07-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kdump currently try mounting NFS (or doing the SSH dump) only once, and if it fails, it just gives-up. Since kdump may be essential to debug hard to reproduce bugs, we should improve the resilience and retry a bit, delaying at each attempt. This patch introduces a retry/delay mechanism for both NFS and SSH dumps; the delay time is the same but number of retries is different (since NFS mounts takes a long time between failures and is inherently more resilient), both being configurable parameters from /etc. The original trigger of this issue is a long-term (bad) behavior of some NICs, which present a "Link Up" status _before_ being ready to transmit packets; hence network kdump will try and fail without this patch. Signed-off-by: Guilherme G. Piccoli <gpiccoli@canonical.com> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| * Merge tag 'debian/1%1.6.5-1'debian/1%1.6.6-1archive/debian/1%1.6.6-1Thadeu Lima de Souza Cascardo2019-07-12
| |\ | | | | | | | | | | | | makedumpfile release 1:1.6.5-1 for unstable (sid) [dgit] [dgit distro=debian]
| | * Declare fast forward from 1:1.6.4-3debian/1%1.6.5-1archive/debian/1%1.6.5-1Thadeu Lima de Souza Cascardo2019-01-05
| | |\ | | | | | | | | | | | | [dgit --overwrite]
| | | * adapt-makefile-to-debianLouis Bouchard2018-10-16
| | | | | | | | | | | | | | | | | | | | =================================================================== Gbp-Pq: Name 0002-adapt-makefile-to-debian.patch
| | | * Remove libebl from link optionsLouis Bouchard2018-10-16
| | | | | | | | | | | | | | | | Description: Remove libebl from link options Gbp-Pq: Name 0001-Remove-libebl-linkage.patch
| | | * makedumpfile (1:1.6.4-3) unstable; urgency=mediumThadeu Lima de Souza Cascardo2018-10-16
| | | |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Reload kdump after memory/CPU hotplug. (LP: #1655280) * Fix adding crashkernel to zipl.conf when no quotation mark is used. (LP: #1790788) [dgit import unpatched makedumpfile 1:1.6.4-3]
| | | | * Import makedumpfile_1.6.4-3.debian.tar.xzThadeu Lima de Souza Cascardo2018-10-16
| | | | | | | | | | | | | | | | [dgit import tarball makedumpfile 1:1.6.4-3 makedumpfile_1.6.4-3.debian.tar.xz]
| | | * Import makedumpfile_1.6.4.orig.tar.gzThadeu Lima de Souza Cascardo2018-07-19
| | | | | | | | | | | | [dgit import orig makedumpfile_1.6.4.orig.tar.gz]
| | * Commit patch queue (exported by git-debrebase)Thadeu Lima de Souza Cascardo2019-01-05
| | | | | | | | | | | | [git-debrebase make-patches: export and commit patches]
| | * Release 1.6.5-1 to unstableThadeu Lima de Souza Cascardo2019-01-05
| | | | | | | | | | | | Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@debian.org>
| | * adapt-makefile-to-debianLouis Bouchard2019-01-05
| | | | | | | | | | | | | | | =================================================================== Gbp-Pq: Name 0002-adapt-makefile-to-debian.patch
| | * Remove libebl from link optionsLouis Bouchard2019-01-05
| | | | | | | | | | | | Description: Remove libebl from link options Gbp-Pq: Name 0001-Remove-libebl-linkage.patch
| * | Commit patch queue (exported by git-debrebase)Thadeu Lima de Souza Cascardo2019-07-12
| | | | | | | | | | | | [git-debrebase make-patches: export and commit patches]
| * | Declare fast forward / record previous workThadeu Lima de Souza Cascardo2019-07-12
| |\ \ | | | | | | | | | | | | [git-debrebase pseudomerge: quick]
| | * | adapt-makefile-to-debianLouis Bouchard2018-12-17
| | | | | | | | | | | | | | | | | | | | =================================================================== Gbp-Pq: Name 0002-adapt-makefile-to-debian.patch
| | * | Remove libebl from link optionsLouis Bouchard2018-12-17
| | | | | | | | | | | | | | | | Description: Remove libebl from link options Gbp-Pq: Name 0001-Remove-libebl-linkage.patch
| * | | adapt-makefile-to-debianLouis Bouchard2019-07-12
| | | | | | | | | | | | | | | | | | | | =================================================================== Gbp-Pq: Name 0002-adapt-makefile-to-debian.patch
| * | | Remove libebl from link optionsLouis Bouchard2019-07-12
| | | | | | | | | | | | | | | | Description: Remove libebl from link options Gbp-Pq: Name 0001-Remove-libebl-linkage.patch
* | | | adapt-makefile-to-debianLouis Bouchard2020-03-02
| | | | | | | | | | | | | | | | | | | | =================================================================== Gbp-Pq: Name 0002-adapt-makefile-to-debian.patch
* | | | Update changelog for new upstream 1.6.7Thadeu Lima de Souza Cascardo2020-03-02
| | | | | | | | | | | | | | | | [git-debrebase changelog: new upstream 1.6.7]
* | | | Update to upstream 1.6.7Thadeu Lima de Souza Cascardo2020-03-02
|\ \ \ \ | | | | | | | | | | | | | | | [git-debrebase anchor: new upstream 1.6.7, merge]
| * | | | [v1.6.7] Update versionKazuhito Hagio2020-01-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update makedumpfile to version 1.6.7. Signed-off-by: Kazuhito Hagio <k-hagio-ab@nec.com>
| * | | | [PATCH] Support newer kernels up to v5.4Kazuhito Hagio2020-01-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Support newer kernels as follows: - 5.2, 5.3, 5.4 (x86_64 SPARSEMEM) - 5.4 (x86 FLATMEM, SPARSEMEM) Signed-off-by: Kazuhito Hagio <k-hagio-ab@nec.com>
| * | | | [PATCH] Update README fileKazuhito Hagio2020-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update README file as follows: - Change the required version of elfutils to 0.144 because of the PN_XNUM support recently added. - Update the email address to which bug report should be sent. Signed-off-by: Kazuhito Hagio <k-hagio-ab@nec.com>
| * | | | [PATCH] s390: Use get_kaslr_offset_general() for s390xMikhail Zaslonko2020-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since kernel v5.2 KASLR is supported on s390. Use recently introduced get_kaslr_offset_general() for s390x in order to derive kaslr offset from vmcoreinfo when -x makedumpfile option specified. Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>
| * | | | [PATCH] Pass 0 to get_kaslr_offset() in find_kaslr_offsets()Kazuhito Hagio2020-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently SYMBOL(_stext) is passed to get_kaslr_offset() in find_kaslr_offsets(), but it is always zero, because it has not been set yet at the time. On the other hand, the vaddr argument of get_kaslr_offset() is only used to decide whether to return a KASLR offset or not, but the return value is not used in find_kaslr_offsets(). Therefore, passing SYMBOL(_stext) is meaningless and confusing, so let's pass it 0 explicitly to avoid confusion. Reported-by: Lianbo Jiang <lijiang@redhat.com> Signed-off-by: Kazuhito Hagio <k-hagio-ab@nec.com>
| * | | | [PATCH] Generalize get_kaslr_offset_arm64() for other architecturesKazuhito Hagio2020-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generalize the get_kaslr_offset_arm64() and rename it to get_kaslr_offset_general() for use by other architectures supporting KASLR. Also, modify the confusing comment in the function and its x86_64 version. Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
| * | | | [PATCH] Fix compilation warnings on 32-bit systemKazuhito Hagio2019-12-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Suppress the following warnings in get_elf64_phnum() on 32-bit system. elf_info.c: In function 'get_elf64_phnum': elf_info.c:1052: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'Elf64_Off' elf_info.c:1057: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'Elf64_Off' Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
| * | | | [PATCH] assign bitmap1/2 fd for subprocess in non-cyclic modePingfan Liu2019-12-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In non-cyclic mode with the --split option, each subprocess inherits bitmap1/2->fd from parent. Then they lseek()/read() on the same fd, which means that they interfere with each other. This breaks the purpose of SPLITTING_FD_BITMAP(i) for each subprocess. Without this patch, makedumpfile can fail with error like the following in refiltering, or can break the dumpfile silently by excluding pages wrongly. readpage_kdump_compressed: pfn(2fc1000) is excluded from vmcore. readmem: type_addr: 1, addr:2fc1000000, size:4096 read_pfn: Can't get the page data. Fix it by assigning a subprocess dedicated fd to bitmap1/2->fd. Signed-off-by: Pingfan Liu <piliu@redhat.com> Signed-off-by: Kazuhito Hagio <k-hagio@ab.jp.nec.com>