| /kernel/linux/linux-5.10/tools/testing/selftests/wireguard/qemu/ |
| D | init.c | 37 static void panic(const char *what) in panic() function
51 panic("uname"); in print_banner()
71 panic("mknod(/dev/urandom)"); in seed_rng()
74 panic("open(urandom)"); in seed_rng()
77 panic("ioctl(urandom)"); in seed_rng()
92 panic("devtmpfs mount"); in mount_filesystems()
94 panic("procfs mount"); in mount_filesystems()
96 panic("sysfs mount"); in mount_filesystems()
98 panic("tmpfs mount"); in mount_filesystems()
100 panic("tmpfs mount"); in mount_filesystems()
[all …]
|
| /kernel/linux/linux-5.10/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
75 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
76 It's optional if you do not care oops/panic log.
78 There are multiple chunks for oops/panic front-end depending on the remaining
81 pstore/blk will log to oops/panic chunks one by one, and always overwrite the
90 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
|
| /kernel/linux/linux-5.10/kernel/ |
| D | panic.c | 3 * linux/kernel/panic.c
83 * Stop ourself in panic -- architecture code may override this
101 * Stop other CPUs in panic. Architecture dependent code may override this
111 * This function can be called twice in panic path, but obviously in crash_smp_send_stop()
119 * unfortunately means it may not be hardened to work in a panic in crash_smp_send_stop()
129 * A variant of panic() called from NMI context. We return if we've already
142 panic("%s", msg); in nmi_panic()
170 * panic - halt the system
177 void panic(const char *fmt, ...) in panic() function
188 * from deadlocking the first cpu that invokes the panic, since in panic()
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/blackbox/ |
| D | Kconfig | 31 panic occurs. It depends on supporting warm reset and disabling erase
49 panic occurs. It depends on supporting pstore blk. Especially, flash
50 driver's panic_write implementation is needed. Othersize, if a panic
61 panic occurs. It depends on supporting pstore ram.
69 panic occurs. It depends on reserving partition for blackbox.
78 prompt "Default storage material for fault log when a panic occurs."
82 panic occurs.
|
| /kernel/linux/linux-5.10/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");
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/arch/xtensa/kernel/ |
| D | s32c1i_selftest.c | 79 panic("S32C1I exception error"); in check_s32c1i()
81 panic("S32C1I compare error"); in check_s32c1i()
93 panic("S32C1I exception error (b)"); in check_s32c1i()
95 panic("S32C1I store error"); in check_s32c1i()
102 * we can get rid of this panic for single core (not SMP) in check_s32c1i()
104 panic("S32C1I exceptions not currently supported"); in check_s32c1i()
107 panic("inconsistent S32C1I exceptions"); in check_s32c1i()
|
| /kernel/linux/linux-5.10/drivers/clk/ |
| D | clk-tango4.c | 33 panic("%s: input not set to XTAL_IN\n", name); in make_pll()
47 panic("%s: unsupported divider %x\n", name, val); in make_cd()
57 panic("%pOFn: invalid address\n", np); in tango4_clkgen_setup()
60 panic("%pOFn: unsupported cpuclk setup\n", np); in tango4_clkgen_setup()
63 panic("%pOFn: unsupported sysclk setup\n", np); in tango4_clkgen_setup()
80 panic("%pOFn: clk registration failed\n", np); in tango4_clkgen_setup()
83 panic("%pOFn: clk provider registration failed\n", np); in tango4_clkgen_setup()
|
| /kernel/linux/linux-5.10/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'
565 this driver cannod to IPMI panic events, extend the watchdog at panic
566 time, or other panic-related IPMI functions without special kernel
618 is the amount of seconds before the reset that the pre-timeout panic will
623 is the value of timeout which is set on kernel panic, in order to let actions
624 such as kdump to occur during panic.
636 "preop_panic" to set the preoperation to panic, or "preop_give_data"
[all …]
|
| /kernel/linux/linux-5.10/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",
177 PANIC, "Data load in unrecoverable area of kernel",
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pstore_blk.h | 11 * typedef pstore_blk_panic_write_op - panic write operation to block device
20 * Panic write to block device must be aligned to SECTOR_SIZE.
30 * @panic_write:The write operation only used for the panic case.
33 * broken during a panic.
72 * @panic_write:The write operation only used for panic case. It's optional
73 * if you do not care panic log. The parameters are relative
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/drivers/clocksource/ |
| D | dw_apb_timer_of.c | 27 panic("Unable to map regs for %pOFn", np); in timer_get_base_and_rate()
40 * Not all implementations use a periphal clock, so don't panic in timer_get_base_and_rate()
61 panic("No clock nor clock-frequency property for %pOFn", np); in timer_get_base_and_rate()
72 panic("No IRQ for clock event timer"); in add_clockevent()
79 panic("Unable to initialise clockevent device"); in add_clockevent()
97 panic("Unable to initialise clocksource device"); in add_clocksource()
|
| /kernel/linux/linux-5.10/fs/pstore/ |
| D | Kconfig | 116 messages, even if no oops or panic happened.
137 was last called before a reset or panic.
149 fault log for BlackBox when oops or panic happened.
154 tristate "Log panic/oops to a RAM buffer"
161 This enables panic and oops messages to be logged to a circular
177 tristate "Log panic/oops to a block device"
184 This enables panic and oops message to be logged to a block dev
225 This just sets size of kmsg dump (oops, panic, etc) log for
|
| /kernel/linux/linux-5.10/arch/mips/pci/ |
| D | msi-octeon.c | 140 panic("arch_setup_msi_irq: Unable to find a free MSI interrupt"); in arch_setup_msi_irq()
171 panic("arch_setup_msi_irq: Invalid octeon_dma_bar_type"); in arch_setup_msi_irq()
229 panic("arch_teardown_msi_irq: Attempted to teardown illegal " in arch_teardown_msi_irq()
252 panic("arch_teardown_msi_irq: Attempted to teardown MSI " in arch_teardown_msi_irq()
403 panic("request_irq(OCTEON_IRQ_PCI_MSI0) failed"); in octeon_msi_initialize()
407 panic("request_irq(OCTEON_IRQ_PCI_MSI1) failed"); in octeon_msi_initialize()
411 panic("request_irq(OCTEON_IRQ_PCI_MSI2) failed"); in octeon_msi_initialize()
415 panic("request_irq(OCTEON_IRQ_PCI_MSI3) failed"); in octeon_msi_initialize()
421 panic("request_irq(OCTEON_IRQ_PCI_MSI0) failed"); in octeon_msi_initialize()
425 panic("request_irq(OCTEON_IRQ_PCI_MSI1) failed"); in octeon_msi_initialize()
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/trigger/ |
| D | ledtrig-panic.c | 3 * Kernel Panic LED Trigger
17 * This is called in a special context by the atomic panic
26 if (strcmp("panic", trig->name)) in led_trigger_set_panic()
69 led_trigger_register_simple("panic", &trigger); in ledtrig_panic_init()
|
| D | Kconfig | 118 bool "LED Panic Trigger"
120 This allows LEDs to be configured to blink on a kernel panic.
121 Enabling this option will allow to mark certain LEDs as panic indicators,
122 allowing to blink them on a kernel panic, even if they are set to
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/arch/arm/mach-s3c/ |
| D | init.c | 50 panic("Unknown S3C24XX CPU"); in s3c_init_cpu()
57 panic("Unsupported Samsung CPU"); in s3c_init_cpu()
79 panic("s3c24xx_init_clocks: no cpu setup?\n"); in s3c24xx_init_clocks()
82 panic("s3c24xx_init_clocks: cpu has no clock init\n"); in s3c24xx_init_clocks()
161 panic("s3c_arch_init: NULL cpu\n"); in s3c_arch_init()
|
| /kernel/linux/linux-5.10/arch/mips/generic/ |
| D | irq.c | 24 panic("Unimplemented!"); in get_c0_fdc_int()
40 panic("Unimplemented!"); in get_c0_perfcount_int()
56 panic("Unimplemented!"); in get_c0_compare_int()
|
| /kernel/linux/linux-5.10/arch/arm64/kvm/hyp/nvhe/ |
| D | host.S | 49 /* x0-7 are use for panic arguments */
83 /* Prepare and exit to the host's panic funciton. */
87 ldr lr, =panic
131 /* If a guest is loaded, panic out of it. */
138 * The panic may not be clean if the exception is taken before the host
|
| /kernel/linux/linux-5.10/sound/usb/hiface/ |
| D | pcm.c | 53 bool panic; /* if set driver won't do anymore pcm on device */ member
211 /* reset panic state when starting a new stream */ in hiface_pcm_stream_start()
212 rt->panic = false; in hiface_pcm_stream_start()
311 if (rt->panic || rt->stream_state == STREAM_STOPPING) in hiface_pcm_out_urb_handler()
346 rt->panic = true; in hiface_pcm_out_urb_handler()
356 if (rt->panic) in hiface_pcm_open()
398 if (rt->panic) in hiface_pcm_close()
423 if (rt->panic) in hiface_pcm_prepare()
457 if (rt->panic) in hiface_pcm_trigger()
489 if (rt->panic || !sub) in hiface_pcm_pointer()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 9 (often with panic), corrected ones cause a machine check log entry.
60 0: always panic on uncorrected errors, log corrected errors
61 1: panic or SIGBUS on uncorrected errors, log corrected errors
63 3: never panic or SIGBUS, log all errors (for testing only)
|