Home
last modified time | relevance | path

Searched refs:KMSG_DUMP_PANIC (Results 1 – 14 of 14) sorted by relevance

/linux-6.1.9/arch/powerpc/platforms/powernv/
Dopal-kmsg.c29 if (reason != KMSG_DUMP_PANIC) in kmsg_dump_opal_console_flush()
/linux-6.1.9/include/linux/
Dkmsg_dump.h25 KMSG_DUMP_PANIC, enumerator
/linux-6.1.9/arch/um/kernel/
Dum_arch.c245 kmsg_dump(KMSG_DUMP_PANIC); in panic_exit()
/linux-6.1.9/Documentation/devicetree/bindings/reserved-memory/
Dramoops.yaml100 it is equivalent to max_reason = 1 (KMSG_DUMP_PANIC).
/linux-6.1.9/kernel/
Dpanic.c361 kmsg_dump(KMSG_DUMP_PANIC); in panic()
/linux-6.1.9/fs/pstore/
Dram.c661 pdata->max_reason = KMSG_DUMP_PANIC; in ramoops_parse_dt()
936 : KMSG_DUMP_PANIC; in ramoops_register_dummy()
Dzone.c438 else if (hdr->reason == KMSG_DUMP_PANIC) in psz_kmsg_recover_meta()
735 else if (hdr->reason == KMSG_DUMP_PANIC) in psz_write_kmsg_hdr()
877 record->reason == KMSG_DUMP_PANIC) in psz_pstore_write()
Dplatform.c157 case KMSG_DUMP_PANIC: in pstore_cannot_block_path()
/linux-6.1.9/Documentation/admin-guide/
Dramoops.rst44 ``max_reason`` should be set to 1 (KMSG_DUMP_PANIC). Setting this to 0
Dpstore-blk.rst149 ``max_reason`` should be set to 1 (KMSG_DUMP_PANIC). Setting this to 0
/linux-6.1.9/arch/powerpc/kernel/
Dnvram_64.c664 case KMSG_DUMP_PANIC: in oops_to_nvram()
Dtraps.c175 kmsg_dump(KMSG_DUMP_PANIC); in panic_flush_kmsg_end()
/linux-6.1.9/drivers/hv/
Dvmbus_drv.c1370 if ((reason != KMSG_DUMP_PANIC) || (!sysctl_record_panic_msg)) in hv_kmsg_dump()
/linux-6.1.9/kernel/printk/
Dprintk.c3627 case KMSG_DUMP_PANIC: in kmsg_dump_reason_str()