| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 026.out.nocache | 2 Errors while writing 128 kB
8 No errors were found on the image.
13 No errors were found on the image.
20 No errors were found on the image.
27 No errors were found on the image.
32 No errors were found on the image.
37 No errors were found on the image.
44 No errors were found on the image.
51 No errors were found on the image.
59 No errors were found on the image.
[all …]
|
| H A D | 026.out | 2 Errors while writing 128 kB
8 No errors were found on the image.
13 No errors were found on the image.
20 No errors were found on the image.
27 No errors were found on the image.
32 No errors were found on the image.
37 No errors were found on the image.
44 No errors were found on the image.
51 No errors were found on the image.
59 No errors were found on the image.
[all …]
|
| H A D | 159.out | 5 No errors were found on the image.
10 No errors were found on the image.
17 No errors were found on the image.
22 No errors were found on the image.
29 No errors were found on the image.
34 No errors were found on the image.
41 No errors were found on the image.
46 No errors were found on the image.
53 No errors were found on the image.
58 No errors were found on the image.
[all …]
|
| H A D | 284.out | 9 No errors were found on the image.
16 No errors were found on the image.
23 No errors were found on the image.
28 No errors were found on the image.
35 No errors were found on the image.
42 No errors were found on the image.
47 No errors were found on the image.
54 No errors were found on the image.
61 No errors were found on the image.
|
| H A D | 160.out | 5 No errors were found on the image.
10 No errors were found on the image.
17 No errors were found on the image.
22 No errors were found on the image.
29 No errors were found on the image.
34 No errors were found on the image.
41 No errors were found on the image.
46 No errors were found on the image.
|
| /openbmc/phosphor-logging/tools/ |
| H A D | elog-gen.py | 24 # the ordered list of errors
25 errors = list()
36 while len(errors) < len(i_errors):
38 if error in errors:
41 if (not i_parents[error]) or (i_parents[error] in errors):
44 errors.append(error)
46 # no inherited errors
47 errors = i_errors
49 return errors
67 # Ex: file xyz/openbmc_project/Error/Callout/Device.errors.yaml
[all …]
|
| /openbmc/ibm-logging/ |
| H A D | create_error_reports.py | 5 1) Dumps every error defined in the errors.yaml files passed in
11 "file":"xyz/openbmc_project/Common/Callout.errors.yaml",
20 showing if any errors are in one file but not the other.
32 """Finds all of the errors in all of the error YAML files in
50 # xyz/openbmc_project/x.errors.yaml -> xyz.openbmc_project.x.Error
52 error_base = error_base.replace(".errors.yaml", "")
56 metadata_file = yaml_file.replace("errors.yaml", "metadata.yaml")
115 """Finds all of the *.errors.yaml files in the directory passed in.
116 Returns a list of entries like xyz/openbmc_project/Common.Errors.yaml.
127 for f in [f for f in files if f.endswith(".errors.yaml")]
[all …]
|
| /openbmc/linux/Documentation/PCI/ |
| H A D | pcieaer-howto.rst | 41 - Gathers the comprehensive error information if errors occurred.
91 When PCIe AER errors are captured, the counters / statistics are also exposed
102 PCIe errors are classified into two types: correctable errors
103 and uncorrectable errors. This classification is based on the impact
104 of those errors, which may result in degraded performance or function
107 Correctable errors pose no impacts on the functionality of the
109 intervention or any loss of data. These errors are detected and
112 Unlike correctable errors, uncorrectable
113 errors impact functionality of the interface. Uncorrectable errors
116 errors are further classified into non-fatal errors and fatal errors.
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.mpc83xx.ddrecc | 6 * (injecting errors is initially disabled)
8 * define inject mask (which tells the DDR controller what type of errors
11 * enable injecting errors - from now on the controller injects errors as
14 IMPORTANT NOTICE: enabling injecting multiple-bit errors is potentially
15 dangerous as such errors are NOT corrected by the controller. Therefore caution
16 should be taken when enabling the injection of multiple-bit errors: it is only
19 Errors' below). In particular, when you simply set the multiple-bit errors in
21 errors will be injected when it accesses its code, data etc.
34 Injecting Single-Bit Errors
56 Multiple Memory Errors: 0
[all …]
|
| /openbmc/openpower-dbus-interfaces/ |
| H A D | generate_makefile.sh | 26 errors=`find $toplevel_dirs -name "*.errors.yaml"`
28 for e in ${errors};
30 iface_path=`dirname $e`/`basename $e .errors.yaml`
34 ${e%.errors.yaml}/error.cpp: ${e} ${e%.errors.yaml}/error.hpp
38 ${e%.errors.yaml}/error.hpp: ${e}
51 for e in ${errors};
53 echo " ${e%.errors.yaml}/error.cpp \\"
62 for e in ${errors};
64 echo " ${e%.errors.yaml}/error.hpp\\"
|
| /openbmc/ibm-dbus-interfaces/ |
| H A D | generate_makefile.sh | 26 errors=`find $toplevel_dirs -name "*.errors.yaml"`
28 for e in ${errors};
30 iface_path=`dirname $e`/`basename $e .errors.yaml`
34 ${e%.errors.yaml}/error.cpp: ${e} ${e%.errors.yaml}/error.hpp
38 ${e%.errors.yaml}/error.hpp: ${e}
51 for e in ${errors};
53 echo " ${e%.errors.yaml}/error.cpp \\"
62 for e in ${errors};
64 echo " ${e%.errors.yaml}/error.hpp\\"
|
| /openbmc/linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 5 The SoundWire PHY was designed with care and errors on the bus are going to
7 errors. Examples of this design can be found in the synchronization
8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
11 The errors can be detected with multiple mechanisms:
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
15 and audio data. The current implementation only logs such errors.
17 restarting from a known position. In the case of such errors outside of a
21 and after a number of such errors are detected the bus might be reset. Note
22 that bus clashes due to programming errors (two streams using the same bit
27 not be responsible for the errors so resetting them individually is not a
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/utils/ |
| H A D | dump.py | 79 Will give up permanently after 5 errors from running commands over
87 self.errors = 0
90 if self.errors >= 5:
91 …print("Too many errors when dumping data from target, assuming it is dead! Will not dump data anym…
100 self.errors = self.errors + 1
103 self.errors = self.errors + 1
110 Will stop completely if there are more than 5 errors when dumping monitor data.
117 self.errors = 0
124 if self.errors >= 5:
125 …print("Too many errors when dumping data from qemu monitor, assuming it is dead! Will not dump dat…
[all …]
|
| /openbmc/linux/drivers/md/bcache/ |
| H A D | io.c | 55 /* IO errors */
58 unsigned int errors; in bch_count_backing_io_errors() local
74 errors = atomic_add_return(1, &dc->io_errors); in bch_count_backing_io_errors()
75 if (errors < dc->error_limit) in bch_count_backing_io_errors()
96 unsigned int errors; in bch_count_io_errors() local
102 * successfully do so, we rescale the errors once: in bch_count_io_errors()
110 errors = atomic_read(&ca->io_errors); in bch_count_io_errors()
112 old = errors; in bch_count_io_errors()
113 new = ((uint64_t) errors * 127) / 128; in bch_count_io_errors()
114 errors = atomic_cmpxchg(&ca->io_errors, in bch_count_io_errors()
[all …]
|
| /openbmc/telemetry/tests/src/ |
| H A D | test_make_id_name.cpp | 33 errors::InvalidArgument); in TEST_F()
98 errors::InvalidArgument); in TYPED_TEST()
100 errors::InvalidArgument); in TYPED_TEST()
101 EXPECT_THROW(this->makeIdName("/123", "trigger"), errors::InvalidArgument); in TYPED_TEST()
102 EXPECT_THROW(this->makeIdName("/123/", "trigger"), errors::InvalidArgument); in TYPED_TEST()
110 errors::InvalidArgument); in TYPED_TEST()
112 errors::InvalidArgument); in TYPED_TEST()
114 errors::InvalidArgument); in TYPED_TEST()
116 errors::InvalidArgument); in TYPED_TEST()
117 EXPECT_THROW(this->makeIdName(longSuffix, "name"), errors::InvalidArgument); in TYPED_TEST()
[all …]
|
| /openbmc/linux/tools/testing/selftests/arm64/abi/ |
| H A D | syscall-abi.c | 76 int errors = 0; in check_gpr() local
87 errors++; in check_gpr()
91 return errors; in check_gpr()
109 int errors = 0; in check_fpr() local
119 errors++; in check_fpr()
132 errors++; in check_fpr()
136 return errors; in check_fpr()
156 int errors = 0; in check_z() local
175 errors++; in check_z()
185 errors++; in check_z()
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | error-reporting-tool.rst | 6 The error reporting tool allows you to submit errors encountered during
8 use a web interface to browse errors, view statistics, and query for
9 errors. The tool works using a client-server system where the client
16 https://errors.yoctoproject.org.
44 reporting causes the build process to collect the errors and store them
48 following command sends the errors to an upstream server::
52 In the previous example, the errors are sent to a public database
53 available at https://errors.yoctoproject.org, which is used by the
55 errors to a different database. Use the following command for more
64 typical link: https://errors.yoctoproject.org/Errors/Details/9522/
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/VirtualMedia/ |
| H A D | MountPoint.interface.yaml | 11 errors:
19 errors:
27 errors:
35 errors:
46 errors:
54 errors:
64 errors:
72 errors:
81 errors:
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/google/gbmc/ |
| H A D | Hoth.interface.yaml | 21 errors:
43 errors:
64 errors:
80 errors:
93 errors:
110 errors:
137 errors:
150 errors:
166 errors:
188 errors:
[all …]
|
| /openbmc/u-boot/scripts/dtc/pylibfdt/ |
| H A D | libfdt.i_shipped | 55 # Pass this as the 'quiet' parameter to return -ENOTFOUND on NOTFOUND errors,
83 This is used to check for errors returned by libfdt C functions.
87 quiet: Errors to ignore (empty to raise on all errors)
108 quiet: Errors to ignore (empty to raise on all errors)
159 quiet: Errors to ignore (empty to raise on all errors)
176 quiet: Errors to ignore (empty to raise on all errors)
191 quiet: Errors to ignore (empty to raise on all errors)
306 quiet: Errors to ignore (empty to raise on all errors)
322 quiet: Errors to ignore (empty to raise on all errors)
351 quiet: Errors to ignore (empty to raise on all errors)
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Ipmi/ |
| H A D | SessionInfo.interface.yaml | 11 errors:
17 errors:
23 errors:
29 errors:
35 errors:
41 errors:
47 errors:
54 errors:
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-pci-devices-aer_stats | 5 statistical counters indicate the errors "as seen/reported by the device".
8 errors may be "seen" / reported by the link partner and not the
16 Description: List of correctable errors seen and reported by this
17 PCI device using ERR_COR. Note that since multiple errors may
20 total of all the errors in the file. Sample output::
37 Description: List of uncorrectable fatal errors seen and reported by this
38 PCI device using ERR_FATAL. Note that since multiple errors may
41 total of all the errors in the file. Sample output::
67 Description: List of uncorrectable nonfatal errors seen and reported by this
68 PCI device using ERR_NONFATAL. Note that since multiple errors
[all …]
|
| /openbmc/sdeventplus/src/sdeventplus/ |
| H A D | event.hpp | 30 * @throws SdEventError for underlying sd_event errors
43 * @throws SdEventError for underlying sd_event errors
62 * @throws SdEventError for underlying sd_event errors
71 * @throws SdEventError for underlying sd_event errors
91 * @throws SdEventError for underlying sd_event errors
99 * @throws SdEventError for underlying sd_event errors
107 * @throws SdEventError for underlying sd_event errors
116 * @throws SdEventError for underlying sd_event errors
124 * @throws SdEventError for underlying sd_event errors
133 * @throws SdEventError for underlying sd_event errors
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/witherspoon/ |
| H A D | fan-errors.yaml | 9 # If a water cooled system, don't create errors for fan 1.
13 # their errors
203 'On fan present or functional state changes, check if errors need to be resolved.'
208 callback: resolve fan0 errors if present and functional
212 'On fan present or functional state changes, check if errors need to be resolved.'
217 callback: resolve fan1 errors if present and functional
221 'On fan present or functional state changes, check if errors need to be resolved.'
226 callback: resolve fan2 errors if present and functional
230 'On fan present or functional state changes, check if errors need to be resolved.'
235 callback: resolve fan3 errors if present and functional
[all …]
|
| /openbmc/phosphor-logging/ |
| H A D | README.md | 14 - [Boot Fail on Hardware Errors](#boot-fail-on-hardware-errors)
99 Any errors passed into these APIs must be known to phosphor-logging, usually by
100 being defined in `<phosphor-logging/elog-errors.hpp>`. The errors must also be
102 for details on how get errors into these headers.
107 #include <phosphor-logging/elog-errors.hpp>
145 #include <phosphor-logging/elog-errors.hpp>
174 `<error-category>.errors.yaml` file, and define any metadata in the
176 repository. During the build, phosphor-logging generates the elog-errors.hpp
184 `xyz/openbmc_project/Control/Device.errors.yaml`, the errors that come from that
187 In rare cases, one may want one to define their errors in the same repository
[all …]
|