Lines Matching +full:no +full:- +full:dump +full:- +full:oops
5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
77 This variable has no effect and may be removed in future kernel
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
170 %d dump mode, matches ``PR_SET_DUMPABLE`` and
173 %t UNIX time of dump
184 the rest of the pattern as a command to run. The core dump will be
209 captured in parallel, but that no waiting will take place (i.e. the
236 ctrl-alt-del
239 When the value in this file is 0, ctrl-alt-del is trapped and
247 mode, the ctrl-alt-del is intercepted by the program before it
258 When ``dmesg_restrict`` is set to 0 there are no restrictions.
292 See Documentation/driver-api/firmware/fallback-mechanisms.rst.
305 Determines whether ``ftrace_dump()`` should be called on an oops (or
312 1 Dump buffers of all CPUs.
313 2(orig_cpu) Dump the buffer of the CPU that triggered the
314 oops.
315 <instance> Dump the specific instance buffer on all CPUs.
316 <instance>=2(orig_cpu) Dump the specific instance buffer on the CPU
317 that triggered the oops.
320 Multiple instance dump is also supported, and instances are separated
322 the dump mode (1/2/orig_cpu) first for global buffer.
324 So for example to dump "foo" and "bar" instance buffer on all CPUs,
329 To dump global buffer and "foo" instance buffer on all
331 oops, user can::
346 debug information. If enabled, arch-specific all-CPU stack dumping
366 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
378 modern systems rely exclusively on the netlink-based uevent source and
385 If this option is set, the kernel will send an NMI to all CPUs to dump
392 1: Will non-maskably interrupt all CPUs and dump their backtraces when
431 0 means infinite timeout, no checking is done.
455 When this value reaches 0, no more warnings will be reported.
458 -1: report an infinite number of warnings.
464 Controls whether the panic kmsg data should be reported to Hyper-V.
472 ignore-unaligned-usertrap
486 See also `unaligned-trap`_.
498 -EPERM) for unprivileged processes not in the io_uring_group group.
502 always fails with -EPERM. Existing io_uring instances can still be
512 to create an io_uring instance. If io_uring_group is set to -1 (the
524 Once true, kexec can no longer be used, and the toggle cannot be set
540 -1 Unlimited calls to kexec. This is the default setting.
569 The correct long-term solution is to do the permission checks at
590 This sysctl only affects module autoloading. It has no effect on the
645 By default they are equal to -1, which means generic allocation logic.
651 2) Toggle with non-default value will be set back to -1 by kernel after
653 fails, it is undefined if the value remains unmodified or is reset to -1.
677 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
686 Documentation/admin-guide/kernel-parameters.rst).
697 A value of 0 means no change. The default value is 200 meaning the NMI
723 ideally is offset by improved memory locality but there is no universal
737 promotion throughput. The per-node max promotion throughput in MB/s
738 will be limited to be no more than the set value.
746 If this option is set, the kernel will send an NMI to all CPUs to dump
747 their backtraces when an oops event occurs. It should be used as a last
752 0: Won't show all CPUs backtraces when an oops is detected.
755 1: Will non-maskably interrupt all CPUs and dump their backtraces when
756 an oops event is detected.
785 The only way to tune these values is to rebuild the kernel :-)
791 if your architecture did not always support 32-bit UIDs (i.e. arm,
793 applications that use the old 16-bit UID/GID system calls, if the
825 servers issue this sort of NMI when the dump button is pushed,
826 and you can use this option to take a crash dump.
833 Controls the kernel's behaviour when an oops or BUG is encountered.
837 1 Panic immediately. If the `panic` sysctl is also non-zero then the
919 When ``panic_on_rcu_stall`` is set to 0, this value is has no effect.
937 sampling rate no matter how CPU time it takes.
939 1-100 Attempt to throttle perf's sample rate to this
962 -1 Allow use of (almost) all events by all users.
983 '``perf record -g``' or '``perf trace --call-graph fp``'.
985 This can only be done when no events are in use that have callchains
986 enabled, otherwise writing to this file will return ``-EBUSY``.
994 Control size of per-cpu ring buffer not counted against mlock limit.
1004 instance, when using '``perf record -g``' or '``perf trace --call-graph fp``'.
1006 This can only be done when no events are in use that have callchains
1007 enabled, otherwise writing to this file will return ``-EBUSY``.
1058 powersave-nap (PPC only)
1061 If set, Linux-PPC will use the 'nap' mode of powersaving,
1094 Value from 0 - 10000 is allowed.
1130 a one-time setting until next reboot: once set, it cannot be changed by
1159 writable for compatibility purposes, but writing to it has no effect
1165 writing to it has no effect on any RNG behavior.
1182 loaded to random addresses. Also for PIE-linked binaries, the
1192 start of the brk area is randomized. There are however no known
1193 non-legacy applications that would be broken this way, so for most
1202 real-root-dev
1205 See Documentation/admin-guide/initrd.rst.
1208 reboot-cmd (SPARC only)
1224 this value to 0. On Non-EAS platforms, write operation fails and
1231 Documentation/accounting/delay-accounting.rst. Enabling this feature incurs
1300 See Documentation/userspace-api/seccomp_filter.rst.
1303 sg-big-buff
1363 feature will do you no good unless you also configure your resource
1378 -1 Legacy per-write sysctl value handling, with no printk warnings.
1444 On x86, each "split lock" imposes a system-wide performance penalty. On larger
1446 denials of service to well-behaved and potentially more important users.
1457 0 Disable the mitigation mode - just warns the split lock on kernel log
1459 1 Enable the mitigation mode (this is the default) - penalizes the split
1482 stop-a (SPARC only)
1485 Controls Stop-A:
1488 0 Stop-A has no effect.
1489 1 Stop-A breaks to the PROM (default).
1492 Stop-A is always enabled on a panic, so that the user can return to
1499 See Documentation/admin-guide/sysrq.rst.
1505 Non-zero if the kernel has been tainted. Numeric values, which can be
1506 ORed together. The letters are seen in "Tainted" line of Oops reports.
1516 128 `(D)` kernel died recently, i.e. there was an OOPS or BUG
1521 4096 `(O)` externally-built ("out-of-tree") module was loaded
1529 See Documentation/admin-guide/tainted-kernels.rst for more information.
1536 See Documentation/admin-guide/kernel-parameters.rst for more details on
1540 threads-max
1550 The minimum value that can be written to ``threads-max`` is 1.
1552 The maximum value that can be written to ``threads-max`` is given by the
1555 If a value outside of this range is written to ``threads-max`` an
1561 When set to a non-zero value, attempt to migrate timers away from idle cpus to
1589 See Documentation/admin-guide/kernel-parameters.rst and
1590 Documentation/trace/boottime-trace.rst.
1593 unaligned-trap
1606 See also `ignore-unaligned-usertrap`_.
1613 value is non-zero, unknown NMI is trapped and then panic occurs. At
1625 will return ``-EPERM``. Once set to 1, this can't be cleared from the
1684 to re-enable cores that by default were not running the watchdog,
1691 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask