Unnamed repository
3001788f4c
'maxcpus' setting normally don't work on several kdump enabled systems due to a known udev issue. Currently the fedora kdump configuration is set as the following on the aarch64 systems: # cat /etc/sysconfig/kdump <..snip..> # This variable lets us append arguments to the current kdump # commandline after processed by KDUMP_COMMANDLINE_REMOVE # KDUMP_COMMANDLINE_APPEND="irqpoll maxcpus=1 reset_devices" <..snip..> Since the 'maxcpus' setting doesn't limit the number of SMP CPUs, so the kdump kernel still boots with all CPUs available on the system. For e.g on the qualcomm amberwing its 46 CPUs: # lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 46 On-line CPU(s) list: 0-45 Thread(s) per core: 1 Core(s) per socket: 46 Socket(s): 1 NUMA node(s): 1 Vendor ID: Qualcomm Model: 1 Model name: Falkor Stepping: 0x0 CPU max MHz: 2600.0000 CPU min MHz: 600.0000 BogoMIPS: 40.00 L1d cache: 32K L1i cache: 64K L2 cache: 512K L3 cache: 58880K NUMA node0 CPU(s): 0-45 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid asimdrdm This causes the memory consumption in the kdump kernel to swell up and we can end up having OOM issues in the kdump kernel boot. Whereas if we use 'nr_cpus=1' in the bootargs, the number of SMP CPUs in the kdump kernel get limited to 1. The 'swiotlb=noforce' setting in bootargs provide us extra guarding, to ensure the crash kernel size requirements do not swell on systems which support swiotlb. With the above settings, crashkernel boots properly (without OOM) on all the aarch64 boards I could test on - qualcomm amberwings, hp-moonshots and hpe-apache (thunderx2) for crash dump saving on local disk. Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com> Acked-by: Pingfan Liu <piliu@redhat.com> |
||
---|---|---|
.gitignore | ||
98-kexec.rules | ||
98-kexec.rules.ppc64 | ||
dracut-early-kdump-module-setup.sh | ||
dracut-early-kdump.sh | ||
dracut-kdump-capture.service | ||
dracut-kdump-emergency.service | ||
dracut-kdump-emergency.target | ||
dracut-kdump-error-handler.service | ||
dracut-kdump-error-handler.sh | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress | ||
early-kdump-howto.txt | ||
fadump-howto.txt | ||
kdump-dep-generator.sh | ||
kdump-in-cluster-environment.txt | ||
kdump-lib-initramfs.sh | ||
kdump-lib.sh | ||
kdump-udev-throttler | ||
kdump.conf | ||
kdump.conf.5 | ||
kdump.service | ||
kdump.sysconfig | ||
kdump.sysconfig.aarch64 | ||
kdump.sysconfig.i386 | ||
kdump.sysconfig.ppc64 | ||
kdump.sysconfig.ppc64le | ||
kdump.sysconfig.s390x | ||
kdump.sysconfig.x86_64 | ||
kdumpctl | ||
kdumpctl.8 | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.18-makedumpfiles-honor-the-CFLAGS-from-environment.patch | ||
kexec-tools.spec | ||
live-image-kdump-howto.txt | ||
mkdumprd | ||
mkdumprd.8 | ||
README | ||
sources | ||
zanata-notes.txt |
Adding a patch to kexec-tools ============================= There is a mailing list kexec@lists.fedoraproject.org where all the dicussion related to fedora kexec-tools happen. All the patches are posted there for inclusion and committed to kexec-tools after review. So if you want your patches to be included in fedora kexec-tools package, post these to kexec@lists.fedoraproject.org. One can subscribe to list and browse through archives here. https://admin.fedoraproject.org/mailman/listinfo/kexec