/linux-6.12.1/tools/testing/selftests/wireguard/qemu/ |
D | init.c | 39 static void panic(const char *what) in panic() function 53 panic("uname"); in print_banner() 68 panic("open(random)"); in seed_rng() 70 panic("ioctl(RNDADDTOENTCNT)"); in seed_rng() 80 panic("settimeofday()"); in set_time() 93 panic("devtmpfs mount"); in mount_filesystems() 95 panic("procfs mount"); in mount_filesystems() 97 panic("sysfs mount"); in mount_filesystems() 99 panic("tmpfs mount"); in mount_filesystems() 101 panic("tmpfs mount"); in mount_filesystems() [all …]
|
/linux-6.12.1/include/drm/ |
D | drm_panic.h | 22 * panic screen, and display it. 37 * sent to the display hardware. Tearing is not an issue for the panic 68 * drm_panic_trylock - try to enter the panic printing critical section 72 * This function must be called by any panic printing code. The panic printing 75 * Panic printing code can make the following assumptions while holding the 76 * panic lock: 81 * - Furthermore the panic printing code only registers in drm_dev_unregister() 82 * and gets removed in drm_dev_unregister(). This allows the panic code to 102 * (which would be impossible in panic context anyway). 119 * drm_panic_lock - protect panic printing relevant state [all …]
|
/linux-6.12.1/kernel/trace/rv/ |
D | reactor_panic.c | 5 * Panic RV reactor: 6 * Prints the exception msg to the kernel message log and panic(). 18 panic(msg); in rv_panic_reaction() 22 .name = "panic", 23 .description = "panic the system if an exception is found.", 42 MODULE_DESCRIPTION("panic rv reactor: panic if an exception is found.");
|
D | Kconfig | 73 bool "Panic reactor" 77 Enables the panic reactor. The panic reactor emits a printk() 78 message if an exception is found and panic()s the system.
|
/linux-6.12.1/Documentation/admin-guide/ |
D | pstore-blk.rst | 3 pstore block oops/panic logger 9 pstore block (pstore/blk) is an oops/panic logger that writes its logs to a 78 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4. 79 It's optional if you do not care about the oops/panic log. 81 There are multiple chunks for oops/panic front-end depending on the remaining 84 pstore/blk will log to oops/panic chunks one by one, and always overwrite the 93 Unlike oops/panic front-end, there is only one chunk for pmsg front-end. 168 the first line of oops/panic data. For example:: 170 Panic: Total 16 times 172 It means that it's OOPS|Panic for the 16th time since the first booting. [all …]
|
D | lockup-watchdogs.rst | 13 panic; a sysctl, "kernel.softlockup_panic", a kernel parameter, 28 The panic option can be used in combination with panic_timeout (this 29 timeout is set through the confusingly named "kernel.panic" sysctl), 47 generate a kernel warning or call panic, depending on the 55 will call panic if it was instructed to do so or resume execution of
|
/linux-6.12.1/kernel/ |
D | panic.c | 3 * linux/kernel/panic.c 145 * Stop ourself in panic -- architecture code may override this 163 * Stop other CPUs in panic. Architecture dependent code may override this 173 * This function can be called twice in panic path, but obviously in crash_smp_send_stop() 181 * unfortunately means it may not be hardened to work in a panic in crash_smp_send_stop() 191 * A variant of panic() called from NMI context. We return if we've already 205 panic("%s", msg); in nmi_panic() 243 panic("%s: panic_on_warn set ...\n", origin); in check_panic_on_warn() 247 panic("%s: system warned too often (kernel.warn_limit is %d)", in check_panic_on_warn() 259 /* Temporary allow non-panic CPUs to write their backtraces. */ in panic_other_cpus_shutdown() [all …]
|
/linux-6.12.1/arch/arm64/hyperv/ |
D | hv_core.c | 78 * continue as a guest VM, so panic. in hv_set_vpreg() 112 * continue as a guest VM, so panic. in hv_get_vpreg_128() 132 * hyperv_report_panic - report a panic to Hyper-V. This function uses 135 * occurrence of a panic. The parallel hv_kmsg_dump() uses the 147 /* Don't report a panic to Hyper-V if we're not going to panic */ in hyperv_report_panic() 152 * We prefer to report panic on 'die' chain as we have proper in hyperv_report_panic() 154 * to report it on 'panic'. in hyperv_report_panic() 156 * Calling code in the 'die' and 'panic' paths ensures that only in hyperv_report_panic()
|
/linux-6.12.1/sound/soc/sof/ |
D | ops.c | 146 * snd_sof_dsp_panic - handle a received DSP panic message 148 * @offset: offset of panic information 149 * @non_recoverable: the panic is fatal, no recovery will be done by the caller 155 * offset from the panic message. in snd_sof_dsp_panic() 161 * Print warning if the offset from the panic message differs from in snd_sof_dsp_panic() 166 "%s: dsp_oops_offset %zu differs from panic offset %u\n", in snd_sof_dsp_panic() 170 * Set the fw_state to crashed only in case of non recoverable DSP panic in snd_sof_dsp_panic() 177 snd_sof_dsp_dbg_dump(sdev, "DSP panic!", in snd_sof_dsp_panic() 183 "DSP panic (recovery will be attempted)", in snd_sof_dsp_panic()
|
/linux-6.12.1/drivers/watchdog/ |
D | pretimeout_panic.c | 13 * pretimeout_panic - Panic on watchdog pretimeout event 16 * Panic, watchdog has not been fed till pretimeout event. 20 panic("watchdog pretimeout event\n"); in pretimeout_panic() 24 .name = "panic", 41 MODULE_DESCRIPTION("Panic watchdog pretimeout governor");
|
/linux-6.12.1/drivers/gpu/drm/ |
D | Kconfig | 109 bool "Display a user-friendly message when a kernel panic occurs" 113 Enable a drm panic handler, which will display a user-friendly message 114 when a kernel panic occurs. It's useful when using a user-space 121 hex "Drm panic screen foreground color, in RGB" 126 hex "Drm panic screen background color, in RGB" 135 panic handler to write the panic message to this plane scanout buffer. 140 string "Panic screen formatter" 145 panic occurs. You can choose between "user", a short message telling 153 bool "Add a panic screen with a QR code" 156 This option adds a QR code generator, and a panic screen with a QR [all …]
|
/linux-6.12.1/arch/xtensa/kernel/ |
D | s32c1i_selftest.c | 78 panic("S32C1I exception error"); in check_s32c1i() 80 panic("S32C1I compare error"); in check_s32c1i() 92 panic("S32C1I exception error (b)"); in check_s32c1i() 94 panic("S32C1I store error"); in check_s32c1i() 101 * we can get rid of this panic for single core (not SMP) in check_s32c1i() 103 panic("S32C1I exceptions not currently supported"); in check_s32c1i() 106 panic("inconsistent S32C1I exceptions"); in check_s32c1i()
|
/linux-6.12.1/arch/x86/kernel/cpu/mce/ |
D | severity.c | 31 * panic situations) 81 PANIC, "Processor context corrupt", 86 PANIC, "MCIP not set in MCA handler", 89 /* Neither return not error IP -- no chance to recover -> PANIC */ 91 PANIC, "Neither restart nor error IP", 95 PANIC, "In kernel and no restart IP", 99 PANIC, "In kernel and no restart IP", 140 PANIC, "Illegal combination (UCNA with AR=1)", 150 PANIC, "Action required with lost events", 189 PANIC, "Data load in unrecoverable area of kernel", [all …]
|
/linux-6.12.1/Documentation/driver-api/ |
D | ipmi.rst | 80 If you want the driver to put an event into the event log on a panic, 81 enable the 'Generate a panic event to all BMCs on a panic' option. If 82 you want the whole panic string put into the event log using OEM 83 events, enable the 'Generate OEM events containing the panic string' 586 this driver cannod to IPMI panic events, extend the watchdog at panic 587 time, or other panic-related IPMI functions without special kernel 678 is the amount of seconds before the reset that the pre-timeout panic will 683 is the value of timeout which is set on kernel panic, in order to let actions 684 such as kdump to occur during panic. 696 "preop_panic" to set the preoperation to panic, or "preop_give_data" [all …]
|
/linux-6.12.1/fs/pstore/ |
D | Kconfig | 35 problems while pstore is recording panic metadata. 42 messages, even if no oops or panic happened. 64 was last called before a reset or panic. 69 tristate "Log panic/oops to a RAM buffer" 76 This enables panic and oops messages to be logged to a circular 92 tristate "Log panic/oops to a block device" 98 This enables panic and oops message to be logged to a block dev 139 This just sets size of kmsg dump (oops, panic, etc) log for
|
/linux-6.12.1/drivers/char/ipmi/ |
D | Kconfig | 31 bool 'Generate a panic event to all BMCs on a panic' 33 When a panic occurs, this will cause the IPMI message handler to, 34 by default, generate an IPMI event describing the panic to each 41 bool 'Generate OEM events containing the panic string' 44 When a panic occurs, this will cause the IPMI message handler to, 46 address of the panic generator (byte 4 of the event), a sequence
|
/linux-6.12.1/crypto/asymmetric_keys/ |
D | selftest.c | 34 panic("Can't allocate certs %s selftest keyring: %ld\n", name, PTR_ERR(keyring)); in fips_signature_selftest() 38 panic("Can't allocate certs %s selftest keyring: %d\n", name, ret); in fips_signature_selftest() 44 panic("Certs %s selftest: pkcs7_parse_message() = %d\n", name, ret); in fips_signature_selftest() 50 panic("Certs %s selftest: pkcs7_verify() = %d\n", name, ret); in fips_signature_selftest() 54 panic("Certs %s selftest: pkcs7_validate_trust() = %d\n", name, ret); in fips_signature_selftest()
|
/linux-6.12.1/arch/mips/mti-malta/ |
D | malta-dtshim.c | 202 panic("Unsupported physical memory map v%u detected", in append_memory() 208 panic("Unable to add memory node to DT: %d", mem_off); in append_memory() 212 panic("Unable to set memory node device_type: %d", err); in append_memory() 218 panic("Unable to set memory regs property: %d", err); in append_memory() 224 panic("Unable to set linux,usable-memory property: %d", err); in append_memory() 307 panic("Corrupt DT"); in malta_dt_shim() 311 panic("Unable to open FDT: %d", err); in malta_dt_shim() 315 panic("No / node in DT"); in malta_dt_shim() 319 panic("No root compatible property in DT: %d", len); in malta_dt_shim() 330 panic("Unable to pack FDT: %d\n", err); in malta_dt_shim()
|
/linux-6.12.1/tools/testing/selftests/nolibc/ |
D | Makefile | 122 QEMU_ARGS_i386 = -M pc -append "console=ttyS0,9600 i8042.noaux panic=-1 $(TEST:%=NOLIBC_TEST=… 123 QEMU_ARGS_x86_64 = -M pc -append "console=ttyS0,9600 i8042.noaux panic=-1 $(TEST:%=NOLIBC_TEST=… 124 QEMU_ARGS_x86 = -M pc -append "console=ttyS0,9600 i8042.noaux panic=-1 $(TEST:%=NOLIBC_TEST=… 125 QEMU_ARGS_arm64 = -M virt -cpu cortex-a53 -append "panic=-1 $(TEST:%=NOLIBC_TEST=%)" 126 QEMU_ARGS_arm = -M virt -append "panic=-1 $(TEST:%=NOLIBC_TEST=%)" 127 QEMU_ARGS_mips32le = -M malta -append "panic=-1 $(TEST:%=NOLIBC_TEST=%)" 128 QEMU_ARGS_mips32be = -M malta -append "panic=-1 $(TEST:%=NOLIBC_TEST=%)" 129 QEMU_ARGS_ppc = -M g3beige -append "console=ttyS0 panic=-1 $(TEST:%=NOLIBC_TEST=%)" 130 QEMU_ARGS_ppc64 = -M powernv -append "console=hvc0 panic=-1 $(TEST:%=NOLIBC_TEST=%)" 131 QEMU_ARGS_ppc64le = -M powernv -append "console=hvc0 panic=-1 $(TEST:%=NOLIBC_TEST=%)" [all …]
|
/linux-6.12.1/arch/mips/pci/ |
D | msi-octeon.c | 144 panic("arch_setup_msi_irq: Unable to find a free MSI interrupt"); in arch_setup_msi_irq() 175 panic("arch_setup_msi_irq: Invalid octeon_dma_bar_type"); in arch_setup_msi_irq() 205 panic("arch_teardown_msi_irq: Attempted to teardown illegal " in arch_teardown_msi_irq() 228 panic("arch_teardown_msi_irq: Attempted to teardown MSI " in arch_teardown_msi_irq() 379 panic("request_irq(OCTEON_IRQ_PCI_MSI0) failed"); in octeon_msi_initialize() 383 panic("request_irq(OCTEON_IRQ_PCI_MSI1) failed"); in octeon_msi_initialize() 387 panic("request_irq(OCTEON_IRQ_PCI_MSI2) failed"); in octeon_msi_initialize() 391 panic("request_irq(OCTEON_IRQ_PCI_MSI3) failed"); in octeon_msi_initialize() 397 panic("request_irq(OCTEON_IRQ_PCI_MSI0) failed"); in octeon_msi_initialize() 401 panic("request_irq(OCTEON_IRQ_PCI_MSI1) failed"); in octeon_msi_initialize() [all …]
|
/linux-6.12.1/arch/powerpc/platforms/powernv/ |
D | opal-kmsg.c | 3 * kmsg dumper that ensures the OPAL console fully flushes panic messages 17 * OPAL_POLL_EVENTS, which flushes some console output. In a panic state, 18 * however, the kernel no longer calls OPAL_POLL_EVENTS and the panic message 26 * Outside of a panic context the pollers will continue to run, in kmsg_dump_opal_console_flush()
|
/linux-6.12.1/drivers/hv/ |
D | hv_common.c | 134 * Boolean to control whether to report panic messages over Hyper-V. 142 * reported to Hyper-V on panic. 168 * The following callback works both as die and panic notifier; its 169 * goal is to provide panic information to the hypervisor unless the 173 * Notice that both the panic/die report notifiers are registered only 182 /* Don't notify Hyper-V unless we have a die oops event or panic. */ in hv_die_panic_notify_crash() 195 * Hyper-V should be notified only once about a panic/die. If we will in hv_die_panic_notify_crash() 220 * Write dump contents to the page. No need to synchronize; panic should in hv_kmsg_dump() 229 * P3 to contain the physical address of the panic page & P4 to in hv_kmsg_dump() 230 * contain the size of the panic data in that page. Rest of the in hv_kmsg_dump() [all …]
|
/linux-6.12.1/arch/hexagon/lib/ |
D | io.c | 24 panic("unaligned pointer to readsw"); in __raw_readsw() 44 panic("unaligned pointer to writesw"); in __raw_writesw() 60 panic("unaligned pointer to readsl"); in __raw_readsl() 75 panic("unaligned pointer to writesl"); in __raw_writesl()
|
/linux-6.12.1/include/linux/ |
D | panic.h | 12 void panic(const char *fmt, ...) __noreturn __cold; 40 * panic_cpu is used for synchronizing panic() and crash_kexec() execution. It 41 * holds a CPU number which is executing panic() currently. A value of 42 * PANIC_CPU_INVALID means no CPU has entered panic() or crash_kexec().
|
/linux-6.12.1/drivers/mtd/ |
D | mtdoops.c | 3 * MTD Oops/Panic logger 173 static void mtdoops_inc_counter(struct mtdoops_context *cxt, int panic) in mtdoops_inc_counter() argument 185 panic ? "immediately" : "scheduled"); in mtdoops_inc_counter() 186 if (panic) { in mtdoops_inc_counter() 187 /* In case of panic, erase immediately */ in mtdoops_inc_counter() 199 static void mtdoops_write(struct mtdoops_context *cxt, int panic) in mtdoops_write() argument 215 if (panic) { in mtdoops_write() 219 pr_err("Cannot write from panic without panic_write\n"); in mtdoops_write() 232 mtdoops_inc_counter(cxt, panic); in mtdoops_write() 457 MODULE_DESCRIPTION("MTD Oops/Panic console logger/driver");
|