| /openbmc/qemu/hw/misc/ |
| H A D | pvpanic.c | 28 static bool logged; in handle_event() local
30 if (event & ~(PVPANIC_PANICKED | PVPANIC_CRASH_LOADED) && !logged) { in handle_event()
32 logged = true; in handle_event()
|
| /openbmc/qemu/qga/ |
| H A D | commands-linux.c | 241 int fd, i = 0, logged; in qmp_guest_fsfreeze_do_thaw() local
251 logged = false; in qmp_guest_fsfreeze_do_thaw()
274 if (ret == 0 && !logged) { in qmp_guest_fsfreeze_do_thaw()
276 logged = true; in qmp_guest_fsfreeze_do_thaw()
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | runqemu.py | 58 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
82 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
108 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
142 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
153 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
|
| H A D | efibootpartition.py | 33 self.assertTrue(qemu.runner.logged, "Failed: %s" % cmd)
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/ |
| H A D | imap-2007f-format-security.patch | 16 - if (!logged++) syslog (LOG_ERR,tmp);
17 + if (!logged++) syslog (LOG_ERR, "%s", tmp);
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 17 cache. This means that normal WRITE requests are not actually logged until the
39 Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
48 If we logged DISCARD when it completed, the replay would look like this:
68 <#logged entries> <highest allocated sector>
71 #logged entries Number of logged entries
|
| /openbmc/u-boot/test/py/ |
| H A D | u_boot_utils.py | 289 logged = False
294 if not logged:
297 logged = True
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | design.md | 68 - The error will be logged.
130 - The error will be logged. If the same error occurs repeatedly on a Rail, it
131 will only be logged once per system boot.
158 an error is logged. This provides "de-glitching" to ignore transient hardware
161 A phase fault error will only be logged for a regulator once per system boot.
165 - The error will be logged. If the same error occurs repeatedly on regulator, it
166 will only be logged once per system boot.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-acpi | 11 firmware_start_ns: Timer value logged at the beginning
13 bootloader_load_ns: Timer value logged just prior to
16 bootloader_launch_ns: Timer value logged just prior to
19 exitbootservice_start_ns: Timer value logged at the
23 exitbootservice_end_ns: Timer value logged at the point
38 logged since the last full boot sequence,
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | phase_fault_detection.md | 12 error should be logged warning the user that the regulator has lost redundancy.
19 detected two consecutive times (15 seconds apart) before an error is logged.
22 Phase faults are detected and logged by executing actions:
|
| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 46 - Event logs should be logged to redfish for Platform Firmware Resilience.
96 Below type of events should be logged as part of PFR or provisioning. These
111 Below are some cases, where firmware resiliency error events logged for
127 Below are some cases, where these events can be logged.
142 Below are few cases, where these events can be logged.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/gammu/gammu/ |
| H A D | gammu-smsdrc | 36 # File (or stderr, syslog, eventlog) where information will be logged
38 # Amount of information being logged, each bit mean one level
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 201 during any method execution will be logged.
207 during method execution of "trace_method_name" will be logged.
213 during method execution of "trace_method_name" will be logged only once.
219 during method/opcode execution of "trace_method_name" will be logged.
225 during method/opcode execution of "trace_method_name" will be logged only
|
| /openbmc/openbmc/meta-security/recipes-scanners/clamav/files/ |
| H A D | clamav-milter.conf.sample | 259 # This option allows to tune what is logged when a message is infected.
260 # Possible values are Off (the default - nothing is logged),
261 # Basic (minimal info logged), Full (verbose info logged)
273 # This option allows to tune what is logged when no threat is found in a scanned message.
286 # then one line is logged for each recipient and the command indicated
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | FaultLogType.interface.yaml | 7 Type of fault data logged.
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | esel_utils.robot | 36 [Documentation] Count eSEL entries logged.
44 [Documentation] Verify eSEL entries logged.
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | fan_missing_error_delay.md | 7 logged when the fan is not present when the attribute is not given.
|
| H A D | nonfunc_rotor_error_delay.md | 7 defaults to **no error** being logged when the attribute is not given and a
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/ |
| H A D | pap | 11 # It will be logged to stderr or to the file specified with the -r chat option.
|
| /openbmc/linux/Documentation/ABI/removed/ |
| H A D | sysfs-kernel-uids | 9 are two users logged in, each with an equal number of
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | Trigger.interface.yaml | 69 Defines a context of a message that is logged when numeric threshold
95 Defines a context of a message that is logged when discrete threshold
|
| /openbmc/linux/arch/x86/ras/ |
| H A D | Kconfig | 23 file that dumps out the current state of all pages logged so far.
|
| /openbmc/openbmc-test-automation/redfish/systems/LogServices/ |
| H A D | test_post_codes.robot | 23 [Documentation] Boot the system and verify PostCodes from host are logged.
37 [Documentation] Initiate Host reboot the system and verify PostCodes from host are logged.
55 [Documentation] Power off the system and verify PostCodes from host are logged.
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | machinecheck.rst | 17 When you see the "Machine check errors logged" message in the system
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/mediatek/ |
| H A D | devapc.yaml | 13 The security violation is logged and sent to the processor for further
|