Home
last modified time | relevance | path

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

1234

/openbmc/linux/Documentation/admin-guide/
H A 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 …]
/openbmc/phosphor-debug-collector/
H A Dramoops_manager.hpp13 namespace ramoops namespace
29 /** @brief Constructor to create ramoops
30 * @param[in] filePath - Path where the ramoops are stored.
37 * @param [in] files - ramoops files list
41 /** @brief Create an error indicating ramoops was found
47 } // namespace ramoops
H A Dramoops_manager.cpp21 namespace ramoops namespace
32 // Create error to notify user that a ramoops has been detected in Manager()
55 method.append("xyz.openbmc_project.Dump.Error.Ramoops", in createError()
65 "an error for ramoops detection", in createError()
117 DumpIntr::convertDumpTypeToString(DumpType::Ramoops); in createHelper()
127 lg2::error("Failed to create ramoops dump, errormsg: {ERROR}", "ERROR", in createHelper()
132 } // namespace ramoops
H A Dexample_dump_types.yaml7 - xyz.openbmc_project.Dump.Create.DumpType.Ramoops:
8 - ramoops
H A Dramoops_manager_main.cpp18 phosphor::dump::ramoops::Manager manager(SYSTEMD_PSTORE_PATH); in main()
/openbmc/linux/Documentation/devicetree/bindings/reserved-memory/
H A 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";
/openbmc/openbmc/meta-phosphor/recipes-phosphor/dump/phosphor-debug-collector/
H A Dramoops-monitor.service2 Description=Ramoops monitor.
3 ConditionPathExistsGlob=/var/lib/systemd/pstore/dmesg-ramoops-*
8 ExecStart=/usr/bin/phosphor-ramoops-monitor
9 SyslogIdentifier=ramoops-monitor
/openbmc/linux/include/linux/
H A Dpstore_ram.h22 * Ramoops platform data
23 * @mem_size memory size for ramoops
24 * @mem_address physical memory address to contain ramoops
/openbmc/phosphor-debug-collector/tools/dreport.d/plugins.d/
H A Dramoops4 # @brief: Move the ramoops data file to the dreport packaging.
10 desc="Ramoops file"
/openbmc/linux/fs/pstore/
H A DMakefile13 ramoops-objs += ram.o ram_core.o
14 obj-$(CONFIG_PSTORE_RAM) += ramoops.o
H A Dram.c187 * Ramoops headers provide time stamps for PSTORE_TYPE_DMESG, but in ramoops_pstore_read()
443 .name = "ramoops",
546 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_przs()
548 label = kasprintf(GFP_KERNEL, "ramoops:%s(%d/%d)", in ramoops_init_przs()
597 label = kasprintf(GFP_KERNEL, "ramoops:%s", name); in ramoops_init_prz()
700 * "ramoops" straight under the root node which isn't in ramoops_parse_dt()
730 * Only a single ramoops area allowed at a time, so fail extra in ramoops_probe()
854 * through /sys/module/ramoops/parameters/ in ramoops_probe()
893 { .compatible = "ramoops" },
901 .name = "ramoops",
[all …]
H A DKconfig51 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
80 "ramoops.ko".
82 For more information, see Documentation/admin-guide/ramoops.rst.
/openbmc/linux/drivers/platform/chrome/
H A 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()
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/
H A DCreate.interface.yaml102 - name: "Ramoops"
104 Dump triggered due to Ramoops type error commit.
/openbmc/openbmc/meta-phosphor/recipes-phosphor/dump/
H A Dphosphor-debug-collector_git.bb39 SYSTEMD_SERVICE:${PN}-monitor += "ramoops-monitor.service"
83 FILES:${PN}-monitor += "${bindir}/phosphor-ramoops-monitor"
/openbmc/openpower-debug-collector/dump/tools/bmcdump/
H A Ddreport_op.conf12 5: ramoops
/openbmc/phosphor-debug-collector/tools/dreport.d/
H A Dsample.conf12 5: ramoops
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md133 | Continued operation | ramoops, ftrace, `printk()` |
135 | Crash | kdump or ramoops |
139 (though may be handled by ramoops until kdump support is integrated). Kernel
141 either ramoops or kdump.
190 ramoops or kdump data to analyse. As data cannot be captured with an escalation
/openbmc/linux/arch/arm64/boot/dts/qcom/
H A Dsdm450-motorola-ali.dts36 ramoops@ef000000 {
37 compatible = "ramoops";
H A Dsm4250-oneplus-billie2.dts45 ramoops@cbe00000 {
46 compatible = "ramoops";
H A Dsdm632-motorola-ocean.dts82 ramoops@ef000000 {
83 compatible = "ramoops";
H A Dmsm8956-sony-xperia-loire.dtsi35 ramoops@57f00000 {
36 compatible = "ramoops";
H A Dmsm8953-xiaomi-tissot.dts61 ramoops@9ff00000 {
62 compatible = "ramoops";
/openbmc/linux/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-vegman.dtsi33 ramoops@9eff0000{
34 compatible = "ramoops";
/openbmc/linux/Documentation/translations/zh_TW/admin-guide/
H A Dindex.rst49 ramoops

1234