Home
last modified time | relevance | path

Searched full:ramoops (Results 1 – 25 of 90) sorted by relevance

1234

/kernel/linux/linux-6.6/Documentation/admin-guide/
Dramoops.rst1 Ramoops oops/panic logger
11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
12 crashes. It works by logging oopses and panics in a circular buffer. Ramoops
16 Ramoops concepts
19 Ramoops uses a predefined memory area to store the dump. The start and size
52 Ramoops also supports software ECC protection of persistent memory regions.
60 Setting the ramoops parameters can be done in several different manners:
64 boot and then use the reserved memory for ramoops. For example, assuming a
67 ramoops region at 128 MB boundary::
69 mem=128M ramoops.mem_address=0x8000000 ramoops.ecc=1
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dramoops.rst1 Ramoops oops/panic logger
11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
12 crashes. It works by logging oopses and panics in a circular buffer. Ramoops
16 Ramoops concepts
19 Ramoops uses a predefined memory area to store the dump. The start and size
50 Ramoops also supports software ECC protection of persistent memory regions.
58 Setting the ramoops parameters can be done in several different manners:
62 boot and then use the reserved memory for ramoops. For example, assuming a
65 ramoops region at 128 MB boundary::
67 mem=128M ramoops.mem_address=0x8000000 ramoops.ecc=1
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/reserved-memory/
Dramoops.yaml4 $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
7 title: Ramoops oops/panic logger
10 ramoops provides persistent RAM storage for oops and panics, so they can be
12 is named "ramoops" after the backend, rather than "pstore" which is the
34 const: ramoops
92 If present, pass ramoops behavioral flags
136 ramoops@bfdf0000 {
137 compatible = "ramoops";
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/reserved-memory/
Dramoops.txt1 Ramoops oops/panic logger
4 ramoops provides persistent RAM storage for oops and panics, so they can be
6 is named "ramoops" after the backend, rather than "pstore" which is the
23 - compatible: must be "ramoops"
59 - flags: if present, pass ramoops behavioral flags (defaults to 0,
/kernel/linux/linux-6.6/include/linux/
Dpstore_ram.h22 * Ramoops platform data
23 * @mem_size memory size for ramoops
24 * @mem_address physical memory address to contain ramoops
/kernel/linux/linux-6.6/fs/pstore/
DMakefile13 ramoops-objs += ram.o ram_core.o
14 obj-$(CONFIG_PSTORE_RAM) += ramoops.o
Dram.c199 * Ramoops headers provide time stamps for PSTORE_TYPE_DMESG, but in ramoops_pstore_read()
466 .name = "ramoops",
569 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_przs()
571 label = kasprintf(GFP_KERNEL, "ramoops:%s(%d/%d)", in ramoops_init_przs()
620 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_prz()
724 * "ramoops" straight under the root node which isn't in ramoops_parse_dt()
756 * Only a single ramoops area allowed at a time, so fail extra in ramoops_probe()
893 * through /sys/module/ramoops/parameters/ in ramoops_probe()
933 { .compatible = "ramoops" },
941 .name = "ramoops",
[all …]
DKconfig81 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
122 "ramoops.ko".
124 For more information, see Documentation/admin-guide/ramoops.rst.
/kernel/linux/linux-5.10/fs/pstore/
DMakefile13 ramoops-objs += ram.o ram_core.o
14 obj-$(CONFIG_PSTORE_RAM) += ramoops.o
Dram.c197 * Ramoops headers provide time stamps for PSTORE_TYPE_DMESG, but in ramoops_pstore_read()
464 .name = "ramoops",
559 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_przs()
561 label = kasprintf(GFP_KERNEL, "ramoops:%s(%d/%d)", in ramoops_init_przs()
609 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_prz()
708 * "ramoops" straight under the root node which isn't in ramoops_parse_dt()
740 * Only a single ramoops area allowed at a time, so fail extra in ramoops_probe()
879 * through /sys/module/ramoops/parameters/ in ramoops_probe()
930 { .compatible = "ramoops" },
938 .name = "ramoops",
[all …]
DKconfig125 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
166 "ramoops.ko".
168 For more information, see Documentation/admin-guide/ramoops.rst.
/kernel/linux/linux-6.6/drivers/platform/chrome/
Dchromeos_pstore.c2 // Driver to instantiate Chromebook ramoops device.
65 .name = "ramoops",
98 pr_info("chromeos ramoops using acpi device.\n"); in chromeos_probe_acpi()
/kernel/linux/linux-5.10/drivers/platform/chrome/
Dchromeos_pstore.c2 // Driver to instantiate Chromebook ramoops device.
65 .name = "ramoops",
98 pr_info("chromeos ramoops using acpi device.\n"); in chromeos_probe_acpi()
/kernel/linux/linux-5.10/include/linux/
Dpstore_ram.h121 * Ramoops platform data
122 * @mem_size memory size for ramoops
123 * @mem_address physical memory address to contain ramoops
/kernel/linux/linux-5.10/arch/arm64/boot/dts/qcom/
Dsdm660-xiaomi-lavender.dts27 ramoops@a0000000 {
28 compatible = "ramoops";
Dsdm630-sony-xperia-nile.dtsi81 ramoops@ffc00000 {
82 compatible = "ramoops";
Dmsm8994-sony-xperia-kitakami.dtsi71 ramoops@1fe00000 {
72 compatible = "ramoops";
Dmsm8992-bullhead-rev-101.dts35 ramoops@1ff00000 {
36 compatible = "ramoops";
/kernel/linux/linux-6.6/arch/arm/boot/dts/aspeed/
Daspeed-bmc-vegman.dtsi33 ramoops@9eff0000{
34 compatible = "ramoops";
/kernel/linux/linux-6.6/arch/arm64/boot/dts/qcom/
Dsdm450-motorola-ali.dts36 ramoops@ef000000 {
37 compatible = "ramoops";
Dsm4250-oneplus-billie2.dts45 ramoops@cbe00000 {
46 compatible = "ramoops";
Dsdm632-motorola-ocean.dts82 ramoops@ef000000 {
83 compatible = "ramoops";
Dmsm8953-xiaomi-tissot.dts61 ramoops@9ff00000 {
62 compatible = "ramoops";
/kernel/linux/linux-5.10/Documentation/translations/zh_CN/admin-guide/
Dindex.rst38 ramoops
/kernel/linux/linux-6.6/Documentation/translations/zh_TW/admin-guide/
Dindex.rst49 ramoops

1234