/openbmc/openpower-hw-diags/analyzer/ |
H A D | analyzer_main.hpp | 13 * and the associated FFDC from analysis. 21 * and the associated FFDC from analysis. 27 * will be logged containing the FFDC from analysis (no service actions 36 * given analysis type. 38 * @param i_type The type of analysis to perform. See enum above. 43 * @return The platform log ID (PLID) of the PEL generated during analysis. Will
|
H A D | analyzer_main.cpp | 26 * @param i_type The type of analysis to perform. See enum for details. 39 * @param i_servData Data regarding service actions gathered during analysis. 90 trace::err("Unsupported analysis type: %u", i_type); in __analysisType() 104 trace::err("Hardware error analysis is not supported on this system"); in analyzeHardware() 155 // This is bad. Analysis should have found a root cause attention in analyzeHardware() 167 // resolutions for manual analysis. in analyzeHardware() 179 trace::err("Exception caught during root cause analysis"); in analyzeHardware() 183 // since the analysis failed, we need to callout Level 2 in analyzeHardware() 191 // Analysis failed so callout the Level 2 Support. in analyzeHardware() 210 // will be reserved for MP-IPLs during TI analysis. in analyzeHardware() [all …]
|
H A D | service_data.hpp | 16 * analysis. 24 * @param i_analysisType The type of analysis to perform. 47 /** The type of analysis to perform. */ 67 /** @return The type of analysis to perform. */ 79 /** @return Returns the guard type based on current analysis policies. */
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/power/power-sequencer/witherspoon/ |
H A D | ucd90160.yaml | 27 analysis: none 32 analysis: none 37 analysis: none 42 analysis: gpuPGOOD 47 analysis: gpuOverTemp 52 analysis: none 78 - type: gpuOverTemp # Extra analysis function to call for this type
|
/openbmc/phosphor-power/power-sequencer/example/ |
H A D | ucd90160.yaml | 27 analysis: none 32 analysis: none 37 analysis: none 42 analysis: gpuPGOOD 47 analysis: gpuOverTemp 52 analysis: none 78 - type: gpuOverTemp # Extra analysis function to call for this type
|
/openbmc/witherspoon-pfault-analysis/power-sequencer/example/ |
H A D | ucd90160.yaml | 27 analysis: none 32 analysis: none 37 analysis: none 42 analysis: gpuPGOOD 47 analysis: gpuOverTemp 52 analysis: none 78 - type: gpuOverTemp # Extra analysis function to call for this type
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/power/power-sequencer/swift/ |
H A D | ucd90160.yaml | 26 analysis: none 31 analysis: memGOOD0 36 analysis: memGOOD1 41 analysis: gpuPGOOD # Extra GPIOAnalysis to run if faulted 46 analysis: gpuOverTemp # Extra GPIOAnalysis to run if faulted 51 analysis: none 57 error_function: gpuPGOODError # Extra analysis function to call for this type 77 error_function: gpuOverTempError # Extra analysis function to call for this type 97 error_function: memGoodError # Extra analysis function to call for this type 141 error_function: memGoodError # Extra analysis function to call for this type
|
/openbmc/openbmc/poky/meta/recipes-devtools/clang/clang/ |
H A D | 0004-llvm-TargetLibraryInfo-Undefine-libc-functions-if-th.patch | 13 .../llvm/Analysis/TargetLibraryInfo.def | 22 ++++++++++++++++++- 16 diff --git a/llvm/include/llvm/Analysis/TargetLibraryInfo.def b/llvm/include/llvm/Analysis/TargetLi… 18 --- a/llvm/include/llvm/Analysis/TargetLibraryInfo.def 19 +++ b/llvm/include/llvm/Analysis/TargetLibraryInfo.def
|
/openbmc/openbmc/poky/scripts/ |
H A D | resulttool | 4 # (merge results, summarise results, regression analysis, generate manual test results file) 21 # To perform regression file analysis, execute the below 64 subparsers.add_subparser_group('analysis', 'analysis', 100)
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | kernel-yocto.bbclass | 518 CONFIG_ANALYSIS_FILE ?= "${WORKDIR}/config-analysis.txt" 543 for action in ["analysis","audit"]: 544 if action == "analysis": 546 …analysis = subprocess.check_output(['symbol_why.py', '--dotconfig', '{}'.format( d.getVar('B') + … 548 …bb.fatal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-… 554 …analysis = subprocess.check_output(['symbol_why.py', '--dotconfig', '{}'.format( d.getVar('B') + … 556 …bb.fatal( "config analysis failed when running '%s': %s" % (" ".join(e.cmd), e.output.decode('utf-… 569 f.write( analysis ) 573 bb.warn( analysis ) 622 …analysis = subprocess.check_output(['symbol_why.py', '--dotconfig', '{}'.format( d.getVar('B') + … [all …]
|
/openbmc/qemu/hw/net/ |
H A D | net_rx_pkt.h | 55 * parse and set packet analysis results 68 * fetches packet analysis results 97 * fetches IP6 header analysis results 99 * Return: pointer to analysis results structure which is stored in internal 106 * fetches IP4 header analysis results 108 * Return: pointer to analysis results structure which is stored in internal
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-pandas_2.2.3.bb | 1 SUMMARY = "pandas library for high-performance data analysis tools" 3 high-performance, easy-to-use data structures and data analysis tools for \
|
H A D | python3-bitstring_4.3.1.bb | 1 SUMMARY = "Simple construction, analysis and modification of binary data."
|
/openbmc/witherspoon-pfault-analysis/power-sequencer/ |
H A D | ucd90160.hpp | 26 * This class implements fault analysis for the UCD90160 146 * Does any additional fault analysis based on the 159 * Does additional fault analysis using GPIOs to 168 * @param[in] type - the type of analysis to do 289 * PGOOD fault analysis to avoid repeatedly logging errors
|
H A D | runtime_monitor.hpp | 23 * PGOOD was dropped due to a fatal fault. After the analysis, 72 * After doing an analysis, will issue a power off
|
/openbmc/phosphor-power/power-sequencer/ |
H A D | ucd90160.hpp | 26 * This class implements fault analysis for the UCD90160 146 * Does any additional fault analysis based on the 159 * Does additional fault analysis using GPIOs to 168 * @param[in] type - the type of analysis to do 289 * PGOOD fault analysis to avoid repeatedly logging errors
|
H A D | runtime_monitor.hpp | 23 * PGOOD was dropped due to a fatal fault. After the analysis, 72 * After doing an analysis, will issue a power off
|
/openbmc/docs/designs/ |
H A D | psu-monitoring.md | 22 The OpenBMC project currently has a [witherspoon-pfault-analysis][1] repository 113 [witherspoon-pfault-analysis][1] repository. This design was avoided due to: 149 [1]: https://github.com/openbmc/witherspoon-pfault-analysis 156 https://github.com/openbmc/witherspoon-pfault-analysis/tree/master/power-supply
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/mozjs/mozjs-128/ |
H A D | 0001-util.configure-fix-one-occasionally-reproduced-confi.patch | 8 | checking whether the C++ compiler supports -Wno-range-loop-analysis... 17 …sysroot=/mozjs/91.1.0-r0/recipe-sysroot /tmp/conftest.jr1qrcw3.cpp -Werror -Wrange-loop-analysis -c
|
/openbmc/openpower-hw-diags/ |
H A D | main_nl.cpp | 57 // TODO: At the moment, we'll only do MANUAL analysis (no service in main() 59 // line options to change the analysis type, if needed. in main()
|
/openbmc/witherspoon-pfault-analysis/ |
H A D | README.md | 1 # witherspoon-pfault-analysis
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/ntopng/files/ |
H A D | ntopng.service | 2 Description=ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool
|
/openbmc/openbmc/poky/scripts/lib/resulttool/ |
H A D | regression.py | 1 # resulttool - regression analysis 415 parser_build = subparsers.add_parser('regression', help='regression file/directory analysis', 416 … description='regression analysis comparing the base set of results to the target results', 417 group='analysis') 429 parser_build = subparsers.add_parser('regression-git', help='regression git analysis', 430 … description='regression analysis comparing base result set to target ' 432 group='analysis')
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/perfetto/ |
H A D | perfetto.inc | 1 SUMMARY = "Perfetto - System profiling, app tracing and trace analysis."
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
H A D | ManufacturerExt.interface.yaml | 13 such as part failure analysis. Any field needed for programmatic
|