| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | error-reporting-tool.rst | 3 Using the Error Reporting Tool
6 The error reporting tool allows you to submit errors encountered during
15 There is a live instance of the error reporting server at
29 By default, the error reporting tool is disabled. You can enable it by
36 By default, the error reporting feature stores information in
44 reporting causes the build process to collect the errors and store them
72 To disable the error reporting feature, simply remove or comment out the
78 Setting Up Your Own Error Reporting Server
81 If you want to set up your own error reporting server, you can obtain
|
| H A D | index.rst | 49 error-reporting-tool
|
| /openbmc/openpower-hw-diags/analyzer/plugins/ |
| H A D | p10-tod-plugins.cpp | 57 * @param i_chipAtFault The chip reporting step check fault.
77 * @param i_chipAtFault The chip reporting a step check fault.
100 * @param i_chipAtFault The chip reporting the fault.
158 // Given the chip reporting the error and the IOHS position within that in getChipSourcingClock()
325 // - First, check if the MDMT chip is reporting a fault. If so, it is in tod_step_check_fault()
328 // - If MDMT is not reporting a fault, look for any network path errors in tod_step_check_fault()
330 // of the chips sourcing those step check errors (not the chips reporting in tod_step_check_fault()
332 // - If no other errors found, callout any chips reporting internal step in tod_step_check_fault()
|
| H A D | p10-plugins.cpp | 14 * @brief Adds all clocks/chips reporting PLL unlock attentions to the callout
18 * more than one processor is reporting a PLL unlock attention on the same
53 // Callout the processors connected to this clock that are reporting PLL in pll_unlock()
|
| /openbmc/openbmc/meta-security/recipes-mac/AppArmor/files/ |
| H A D | 0001-fail.py-handle-missing-cgitb.patch | 49 - file.write('Please consider reporting a bug at https://gitlab.com/apparmor/apparmor/-/…
55 + file.write('Please consider reporting a bug at https://gitlab.com/apparmor/apparmo…
65 …print('Please consider reporting a bug at https://gitlab.com/apparmor/apparmor/-/issues', file=sys…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/libreport/ |
| H A D | libreport_2.17.15.bb | 1 DESCRIPTION = "Libraries providing API for reporting different problems in applications \
3 SUMMARY = "Generic library for reporting various problems"
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team.md | 1 # The OpenBMC security vulnerability reporting process
3 This describes the OpenBMC security vulnerability reporting process which is
|
| H A D | obmc-security-response-team-guidelines.md | 5 problems reported by the [security vulnerability reporting process][].
93 [security vulnerability reporting process]: ./obmc-security-response-team.md
113 - Thank you for reporting this.
204 `for privately reporting OpenBMC security vulnerabilities` with description:
205 This email list is for privately reporting OpenBMC security vulnerabilities.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Attestation/ |
| H A D | ComponentIntegrity.interface.yaml | 50 - name: reporting
53 "reporting" association to provide a link to the target trusted
|
| /openbmc/google-ipmi-sys/ |
| H A D | file_system_wrapper.hpp | 36 * @param[in] ec - out-parameter for error reporting in the non-throwing
47 * @param[in] ec - out-parameter for error reporting in the non-throwing
|
| /openbmc/libcper/specification/json/sections/ |
| H A D | cper-vtd-dmar.json | 32 … "description": "Value of revision field in VT-d specific DMA remapping reporting structure"
36 … "description": "Value of OEM ID field in VT-d specific DMA remapping reporting structure"
|
| /openbmc/openbmc/poky/scripts/lib/build_perf/ |
| H A D | html.py | 6 """Helper module for HTML reporting"""
|
| /openbmc/docs/designs/ |
| H A D | event-logging.md | 13 There is currently not a consistent end-to-end error and event reporting design
139 Application code reporting an error:
172 likely to become outdated over time as internal OpenBMC error reporting
185 Message Registry and the reporting application. It also requires every
187 and external management interfaces. This also leaves gaps for reporting errors
197 - The `sdbusplus` bindings for error reporting do not currently handle lossless
203 `phosphor-health-monitor`. One cause of this is two different error reporting
222 mechanics for push-reporting.
252 - APIs to implement error and event reporting should have good ergonomics. These
268 reporting; expand it to cover tracing events; improve the ergonomics of the
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/smartmontools/files/ |
| H A D | smartd.service | 2 Description=Self Monitoring and Reporting Technology (SMART) Daemon
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-progress_1.6.bb | 1 SUMMARY = "Easy progress reporting for Python"
|
| /openbmc/qemu/include/qemu/ |
| H A D | help-texts.h | 8 /* Bug reporting information for --help arguments, About dialogs, etc */
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-meh/ |
| H A D | python3-meh_0.52.bb | 2 DESCRIPTION = "The python-meh package is a python library for handling, saving, and reporting \
|
| /openbmc/qemu/include/gdbstub/ |
| H A D | syscalls.h | 104 * gdb_exit: exit gdb session, reporting inferior status
107 * This closes the session and sends a final packet to GDB reporting
|
| /openbmc/openbmc/meta-raspberrypi/.github/ |
| H A D | ISSUE_TEMPLATE.md | 2 If you are reporting a new issue, make sure that we do not have any duplicates
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
| H A D | libice_1.1.2.bb | 7 negotiating versions, and for reporting errors. "
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/devtool/devtool-upgrade-test1-1.5.3/ |
| H A D | 0001-Add-a-note-line-to-the-quick-reference.patch | 23 .SH REPORTING BUGS
|
| /openbmc/qemu/util/ |
| H A D | qemu-progress.c | 110 * Initialize progress reporting.
111 * If @enabled is false, actual reporting is suppressed. The user can
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | TrustedComponent.interface.yaml | 20 reverse_name: reporting
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/satyr/ |
| H A D | satyr_0.43.bb | 2 failure processing, analysis, and reporting supporting kernel space, user \
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/freedesktop/UPower/ |
| H A D | Device.interface.yaml | 205 power sources are capable of only reporting percentages and in this
251 100. However, some primitive power sources are not capable reporting
286 reporting)
|