| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-fetching.rst | 144 make any attempted network access a fatal error, which is useful for
|
| H A D | bitbake-user-manual-ref-variables.rst | 138 The default fatal behavior is safest because it is the sane reaction
|
| H A D | bitbake-user-manual-metadata.rst | 1147 exception. For example, an exception raised by ``bb.fatal()`` will be caught
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | sdm630.dtsi | 2196 interrupt-names = "wdog", "fatal", "ready",
|
| H A D | sc7280.dtsi | 2759 interrupt-names = "wdog", "fatal", "ready", "handover",
3487 interrupt-names = "wdog", "fatal", "ready", "handover",
|
| H A D | sc7180.dtsi | 2057 interrupt-names = "wdog", "fatal", "ready", "handover",
|
| /openbmc/linux/Documentation/ |
| H A D | memory-barriers.txt | 1550 be fatal in concurrent code. Here are some examples of these sorts
1599 single-threaded code, but can be fatal in concurrent code:
1665 it might well omit the second store. This would come as a fatal
|
| /openbmc/linux/net/ipv4/ |
| H A D | udp.c | 781 harderr = icmp_err_convert[code].fatal; in __udp4_lib_err()
|
| /openbmc/qemu/qapi/ |
| H A D | block-core.json | 5508 # @fatal: if set, the image is marked corrupt and therefore unusable
5510 # BLOCK_IMAGE_CORRUPTED event was fatal)
5530 'fatal' : 'bool' } }
|
| /openbmc/linux/Documentation/sound/kernel-api/ |
| H A D | writing-an-alsa-driver.rst | 2636 value is not changed, return 0 instead. If any fatal error happens,
3861 here, too, since it would be fatal if you cannot allocate a memory in
4061 fatal error happens there.
|
| /openbmc/qemu/ |
| H A D | hmp-commands.hx | 1288 " -a for advisory non fatal error\n\t\t\t"
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.debug | 501 bool "Make section mismatch errors non-fatal"
2826 module load requests, ultimately this could be fatal.
|
| /openbmc/linux/Documentation/translations/sp_SP/process/ |
| H A D | submitting-patches.rst | 71 dmesg, descripciones del error fatal, regresiones de rendimiento, picos de
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | quickly-build-trimmed-linux.rst | 538 'fatal: error in object: unshallow cafecaca0c0dacafecaca0c0dacafecaca0c0da'.
|
| H A D | kernel-parameters.txt | 4613 print-fatal-signals=
4614 [KNL] debug: print fatal signals
4618 too many POSIX.1 timers, fatal signals causing a
6105 fatal - the kernel will send SIGBUS to applications
6120 the kernel will oops in either "warn" or "fatal"
|
| H A D | reporting-issues.rst | 406 fatal error where the kernel stop itself) with a 'Oops' (a recoverable error),
|
| H A D | cgroup-v2.rst | 957 Processes in the frozen cgroup can be killed by a fatal signal.
|
| /openbmc/openbmc/poky/meta/classes-global/ |
| H A D | insane.bbclass | 986 bb.fatal("%s:%s: %s" % (var, pkg, e))
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | vivid.rst | 974 marked as having suffered a fatal error, the only way to recover
|
| /openbmc/linux/Documentation/translations/sp_SP/ |
| H A D | memory-barriers.txt | 1672 seguro en código de subproceso único, pero puede ser fatal en código
1742 lo que bien podría omitir el segundo store. Esto supondría una fatal
|
| /openbmc/openbmc/poky/meta/conf/distro/include/ |
| H A D | maintainers.inc | 398 RECIPE_MAINTAINER:pn-libtest-fatal-perl = "Tim Orling <tim.orling@konsulko.com>"
|
| /openbmc/linux/init/ |
| H A D | Kconfig | 1560 numerous fatal conditions. You should only consider disabling this
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-online-fsck-design.rst | 3426 Trylock loops enable scrub to check for pending fatal signals, which is how
5221 Userspace is allowed to send a fatal signal to the process which will cause
5224 Given that the scrub codebase has helpers to detect fatal signals, it shouldn't
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 190 In order to avoid fatal problems such as deadlocks, an RCU read-side
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | variables.rst | 373 The default fatal behavior is safest because it is the sane reaction
5944 system generates a fatal installation error. Because the build system
5945 halts the process with a fatal error, you can use the variable with
|