03e916405f
Currently a lot of our configuration settings and panic sysctls are highly specific to SteamOS, so let's make them distro-agnostic, more focused on generic HW / usage of a regular Arch Linux user. The affected configs/sysctls are detailed below: (a) Pstore memory settings: since on Steam Deck we have somewhat pre-reserved RAM for pstore (~15M due to kernel memory alignment rounding), makes sense to have a bit more of such memory effectively available for pstore. In the general case though, likely users will require to manually reserve it, so 4M of total memory with 1M buffer seems more than enough to collect a dmesg, specially considering point (e) below. (b) The log storage folder was tuned for Deck, in which we have A/B partitioning scheme and a persistent /home, but in general (following standard kdump tools "on the market", like Debian's/Fedora's), /var is used for that, so we follow the trend here. (c) Grub file location was also special on SteamOS, so let's make it follow the default /boot/grub/grub.cfg here. (d) Kdump-specific tunings: the goal for people using kdump (not pstore!) is usually to collect the vmcore of the panicked kernel to explore it, using tools like crash/drgn. This is not the main goal on SteamOS, in which we want to collect as much info we can get *on dmesg* and that's it for most cases... With that in mind, we needed "crash_kexec_post_notifiers" parameter to dump more info on dmesg during a panic (a potentially problematic parameter in some HWs BTW, but tested in depth on Deck) and we disabled the vmcore saving by default as well. So, let's "revert" it here, having vmcore capturing enabled by default and dropping the post_notifiers parameter (see next point as well). (e) About the sysctls, we are more aggressive on panicking on Deck (like panic on soft lockups) and the goal is to collect the most info we can on dmesg, so needed to enable panic_print to dump tasks and whatnot on dmesg during a panic event. In the general case, people that wish to have the most information as possible would go with kdump, collecting vmcore, not with pstore collecting just the dmesg. With that said, "reduce" panic_print here to only show memory info and CPUs backtraces, and disable soft lockup panic. (Also we cleared the file to drop mentioning the choices of *not* panicking on hung tasks or RCU stalls). Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
65 lines
2.9 KiB
Bash
65 lines
2.9 KiB
Bash
#!/bin/sh
|
|
#
|
|
# SPDX-License-Identifier: LGPL-2.1+
|
|
#
|
|
# Copyright (c) 2021 Valve
|
|
# Maintainer: Guilherme G. Piccoli <gpiccoli@igalia.com>
|
|
#
|
|
# Configuration settings for kdump/pstore. After _any_ change in this
|
|
# file, it's required to re-create the kdump minimal initramfs by running:
|
|
# /usr/lib/kdump/kdump-load.sh create-initrd
|
|
#
|
|
#
|
|
# Pstore-RAM settings
|
|
# If USE_PSTORE_RAM is set to 1, Kdump won't be loaded. Instead, the Pstore
|
|
# RAM backend will be configured. In order to have success, this operation
|
|
# relies in having an available RAM buffer on /proc/iomem with at least
|
|
# PSTORE_MEM_AMOUNT (decimal, in MB) in size. Also, kernel must be able to
|
|
# allocate a contiguous memory amount of PSTORE_RECORD_SZ (decimal, MB).
|
|
USE_PSTORE_RAM=1
|
|
PSTORE_MEM_AMOUNT=4194304
|
|
PSTORE_RECORD_SZ=1048576
|
|
#
|
|
#
|
|
# Mount-related options
|
|
# since the link is not present so early in the system boot. MOUNT_FOLDER
|
|
# MOUNT_FOLDER is the the place in which both pstore and kdump logs will
|
|
# be stored, as well as the kdump initrd and some ancillary data. This
|
|
# directory should be in an accessible filesystem (read/write) and if such
|
|
# folder doesn't exist, it'll be created.
|
|
MOUNT_FOLDER="/var/crash/kdump"
|
|
#
|
|
#
|
|
# Kdump controlling settings
|
|
# Currently we only do local storage log collection (no network/iscsi dumps).
|
|
# If FULL_COREDUMP is !=0, we collect a full compressed vmcore, which might
|
|
# require a lot of disk space. The MAKEDUMPFILE_*_CMD settings refer to
|
|
# tunings on makedumpfile - we rely on zstd compression and maximum page
|
|
# exclusion for the full vmcore, mimic'ing Debian/Ubuntu kdump. We also
|
|
# base on Debian/Ubuntu for the KDUMP_CMDLINE_APPEND option - this contains
|
|
# the kernel parameters we append in the /proc/cmdline for the kdump kernel;
|
|
# the most important parameters are nr_cpus=1 (to save RAM memory usage and
|
|
# avoid some potential issues with SMP) and reset_devices (some drivers
|
|
# rely on that for proper kdump).
|
|
FULL_COREDUMP=1
|
|
MAKEDUMPFILE_COREDUMP_CMD="-z -d 31"
|
|
MAKEDUMPFILE_DMESG_CMD="--dump-dmesg"
|
|
KDUMP_APPEND_CMDLINE="panic=-1 oops=panic fsck.mode=force fsck.repair=yes nr_cpus=1 reset_devices"
|
|
#
|
|
#
|
|
# GRUB-related settings
|
|
# GRUB_AUTOSET determines if the pstore/kdump tooling should try to
|
|
# automatically set grub.cfg in order to reserve memory for kdump (if
|
|
# needed, i.e., when pstore is not in use) - keep it as '1' for enabling
|
|
# the mechanism (this is the default). GRUB_BOOT_FILE is the full path of
|
|
# grub.cfg file - this is used in the config update step plus for syncing
|
|
# purposes. GRUB_CFG_FILE is the config file we edit in order to add/remove
|
|
# the crashkernel parameter. Finally, GRUB_CMDLINE holds the change to be
|
|
# made in the grub config file, specially the crashkernel memory reservation
|
|
# (notice that a trailing space is required in this line, so we avoid
|
|
# messing with other kernel parameters).
|
|
GRUB_AUTOSET=1
|
|
GRUB_BOOT_FILE="/boot/grub/grub.cfg"
|
|
GRUB_CFG_FILE="/etc/default/grub"
|
|
GRUB_CMDLINE="crashkernel=256M "
|