aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/image/rt288x.mk
diff options
context:
space:
mode:
authorHannu Nyman <hannu.nyman@iki.fi>2022-02-09 23:54:47 +0200
committerChristian Lamparter <chunkeey@gmail.com>2022-02-24 20:45:12 +0100
commit97158fe10e6090a8b21629df130734bac53f87ee (patch)
tree5eb053bb9d381a65141acf24232a920235db1755 /target/linux/ramips/image/rt288x.mk
parent1050e66c8f7c67ab8b3d1895e2559f03baeb2345 (diff)
downloadupstream-97158fe10e6090a8b21629df130734bac53f87ee.tar.gz
upstream-97158fe10e6090a8b21629df130734bac53f87ee.tar.bz2
upstream-97158fe10e6090a8b21629df130734bac53f87ee.zip
kernel: package ramoops pstore-ram crash log storage
Package the ability to log kernel crashes to 'ramoops' pstore files into RAM in /sys/fs/pstore Reference to the ramoops admin guide in upstream Linux: https://www.kernel.org/doc/html/v5.10/admin-guide/ramoops.html The files in RAM survive a warm reboot, but not a cold reboot. Note: kmod-ramoops selects kmod-pstore and kmod-reed-solomon. The feature can be used by selecting the kmod-ramoops and adding a ramoops reserved-memory definition to the device DTS. Example from R7800: reserved-memory { rsvd@5fe00000 { reg = <0x5fe00000 0x200000>; reusable; }; ramoops@42100000 { compatible = "ramoops"; reg = <0x42100000 0x40000>; record-size = <0x4000>; console-size = <0x4000>; ftrace-size = <0x4000>; pmsg-size = <0x4000>; }; }; If no definition has been made in DTS, no crash log is stored for the device. Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (added CONFIG_EFI_VARS_PSTORE disable)
Diffstat (limited to 'target/linux/ramips/image/rt288x.mk')
0 files changed, 0 insertions, 0 deletions