Lines Matching +full:system +full:- +full:firmware
2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
9 to minimize the total elapsed time until the system is back
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
31 - Unlike kdump, the system has been reset, and loaded
35 - Once the dump is copied out, the memory that held the dump
38 the system to the production configuration.
41 and assistance from the Power firmware. The procedure is
44 - The first kernel registers the sections of memory with the
45 Power firmware for dump preservation during OS initialization.
49 - When system crashes, the Power firmware will copy the registered
57 size will be the larger of 5% of system RAM or 256MB.
63 refer to Documentation/admin-guide/kdump/kdump.rst. If any
68 - After the low memory (boot memory) area has been saved, the
69 firmware will reset PCI and other hardware state. It will
73 - The freshly booted kernel will notice that there is a new node
74 (rtas/ibm,kernel-dump on pSeries or ibm,opal/dump/mpipl-boot
83 - User-space tools will read /proc/vmcore to obtain the contents
88 - Once the userspace tool is done saving dump, it will echo
91 next firmware-assisted dump registration.
97 Please note that the firmware-assisted dump feature
100 or later firmware versions on PowerNV (OPAL) platform.
101 Note that, OPAL firmware exports ibm,opal/dump node when
104 On OPAL based machines, system first boots into an intermittent
113 -- On OPAL based machines (PowerNV), if the kernel is build with
115 exported as /sys/firmware/opal/mpipl/core file. This procfs file is
118 '1' to /sys/firmware/opal/mpipl/release_core node.
121 # echo 1 > /sys/firmware/opal/mpipl/release_core
124 -----------------------
126 During boot, a check is made to see if firmware supports
144 Since this reserved memory area is used only after the system crash,
157 0 boot memory size |<------ Reserved dump area ----->| |
160 +-----------+-----/ /---+---+----+-----------+-------+----+-----+
162 +-----------+-----/ /---+---+----+-----------+-------+----+-----+
166 -------------------------------- | |
168 to reserved area by firmware at the | |
187 | |<------------ Crash preserved area ------------>|
188 V V |<--- Reserved dump area --->| |
189 +----+---+--+-----/ /---+---+----+-------+-----+-----+-------+
191 +----+---+--+-----/ /---+---+----+-------+-----+-----+-------+
193 ----- ------------------------------ ---------------
197 \ | ----------------------------
204 +---+
205 |///| -> Regions (CPU, HPTE & Metadata) marked like this in the above
206 +---+ figures are not always present. For example, OPAL platform
210 +---+
211 |ELF| -> elfcorehdr, it is created in second kernel after crash.
212 +---+
230 How to enable firmware-assisted dump (FADump):
231 ----------------------------------------------
246 2. If firmware-assisted dump fails to reserve memory then it
250 reserved memory not available to production system, then
255 --------------------
257 Firmware-assisted dump feature uses sysfs file system to hold
265 - 0 = FADump is disabled
266 - 1 = FADump is enabled
275 - 0 = FADump is not registered.
276 - 1 = FADump is registered and ready to handle system crash.
279 echo 0 > /sys/kernel/fadump_registered for un-register and stop the
280 FADump. Once the FADump is un-registered, the system crash will not
305 /sys/firmware/opal/mpipl/release_core
307 /sys/firmware/opal/mpipl/release_core
311 used by the kernel to export /sys/firmware/opal/mpipl/core file. To
314 echo 1 > /sys/firmware/opal/mpipl/release_core
318 +----------------------------------+--------------------------------+
320 +----------------------------------+--------------------------------+
322 +----------------------------------+--------------------------------+
324 +----------------------------------+--------------------------------+
326 +----------------------------------+--------------------------------+
336 <region>: [<start>-<end>] <reserved-size> bytes, Dumped: <dump-size>
340 DUMP: Src: <src-addr>, Dest: <dest-addr>, Size: <size>, Dumped: # bytes
346 CPU : [0x0000006ffb0000-0x0000006fff001f] 0x40020 bytes, Dumped: 0x0
347 HPTE: [0x0000006fff0020-0x0000006fff101f] 0x1000 bytes, Dumped: 0x0
348 DUMP: [0x0000006fff1020-0x0000007fff101f] 0x10000000 bytes, Dumped: 0x0
353 CPU : [0x0000006ffb0000-0x0000006fff001f] 0x40020 bytes, Dumped: 0x40020
354 HPTE: [0x0000006fff0020-0x0000006fff101f] 0x1000 bytes, Dumped: 0x1000
355 DUMP: [0x0000006fff1020-0x0000007fff101f] 0x10000000 bytes, Dumped: 0x10000000
356 : [0x00000010000000-0x0000006ffaffff] 0x5ffb0000 bytes, Dumped: 0x5ffb0000
365 -----
366 - Need to come up with the better approach to find out more