/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/crash/ |
H A D | crash-cross-canadian_8.0.6.bb | 3 SUMMARY = "crash utility (cross-canadian crash for ${TARGET_ARCH} target)" 4 PN = "crash-cross-canadian-${TRANSLATED_TARGET_ARCH}" 5 BPN = "crash" 7 require crash.inc 32 # To ship crash into your sdk, you should create/update a packagegroup-cross-canadian.bbappend and 34 # CRASH = "crash-cross-canadian-${TRANSLATED_TARGET_ARCH}" 35 # RDEPENDS:${PN} += "${@all_multilib_tune_values(d, 'CRASH')}" 47 # crash $OECORE_TARGET_SYSROOT/boot/<vmlinux file> $OECORE_TARGET_SYSROOT/boot/<System.map file> <y… 50 install -m 0755 ${S}/crash ${D}/${bindir}
|
H A D | crash.inc | 18 SRC_URI = "git://github.com/crash-utility/${BPN}.git;branch=master;protocol=https \ 36 UPSTREAM_CHECK_URI = "https://github.com/crash-utility/crash/releases" 42 # crash 7.1.3 and before don't support mips64/riscv64 84 install -d ${D}${includedir}/crash 86 install -m 0644 ${S}/crash.8 ${D}/${mandir}/man8/ 87 install -m 0644 ${S}/defs.h ${D}${includedir}/crash
|
H A D | crash_8.0.6.bb | 1 require crash.inc 24 install -m 0755 ${S}/crash ${D}/${bindir}
|
/openbmc/openbmc-test-automation/openpower/ |
H A D | test_nmi_interface.robot | 36 Verify Crash Dump Directory After NMI Inject 41 Verify Crash Dump Directory After NMI Inject 42 [Documentation] Verification of crash dump directory after NMI inject. 46 Wait Until Keyword Succeeds 1 min 10 sec Verify Crash Dump Directory 62 OS Execute Command rm -rf /var/crash/* 64 # Start crash dump utility on OS. 84 Verify Crash Dump Directory 85 [Documentation] Verify that the crash dump directory is not empty. 87 # As per the requirement, there should be a crash dump file 91 ... OS Execute Command ls -ltr /var/crash/* print_out=1
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/crash/crash/ |
H A D | 7001force_define_architecture.patch | 3 diff -uprN crash-5.1.8.org/configure.c crash-5.1.8/configure.c 4 --- crash-5.1.8.org/configure.c 2011-09-17 04:01:12.000000000 +0900 5 +++ crash-5.1.8/configure.c 2012-09-13 13:28:45.393344108 +0900
|
H A D | 0001-symbol-fix-S-cannot-work-with-kaslr-detection.patch | 6 When kernel enabled the CONFIG_RANDOMIZE_BASE, crash needs to add "kaslr=auto" 7 in crash command line to tell crash to decode the random address. 8 But when with "-S" in command line, crash would bypass the kaslr option 11 The fix is provided by Tao Liu <ltao@redhat.com> from crash-utility upstream, 12 and not merged to crash master yet. 15 [https://lists.crash-utility.osci.io/archives/list/devel@lists.crash-utility.osci.io/thread/5OXNYPP…
|
H A D | gdb_build_jobs_and_not_write_crash_target.patch | 4 Subject: [PATCH] Makefile: Don't write ${TARGET} to crash.target 13 Don't write ${TARGET} to crash.target which causes rebuild fails. 29 - $(MAKE) CRASH_TARGET=${TARGET}; echo ${TARGET} > crash.target) \
|
H A D | 0001-Use-CC-env-var-to-get-compiler-version.patch | 19 Upstream-Status: Submitted [https://lists.crash-utility.osci.io/archives/list/devel@lists.crash-uti…
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/host/ |
H A D | op-proc-control-systemd-links.bb | 112 # on mpreboot systems, obmc-host-crash@.target is used for mpreboot 113 mkdir -p $D$systemd_system_unitdir/obmc-host-crash@0.target.requires 114 …LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.requires/obmc-host-force-warm-reboot@0.ta… 118 LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.requires/op-enter-mpreboot@0.service" 123 …LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.requires/obmc-host-diagnostic-mode@0.targ… 127 # If not a mpreboot system, default to quiesce target in crash target to support 129 mkdir -p $D$systemd_system_unitdir/obmc-host-crash@0.target.wants 130 LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.wants/obmc-host-quiesce@0.target" 181 …LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.requires/obmc-host-force-warm-reboot@0.ta… 184 LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.requires/op-enter-mpreboot@0.service" [all …]
|
/openbmc/qemu/include/hw/riscv/ |
H A D | boot_opensbi.h | 50 * stage leading to boot-time crash. To avoid this boot-time crash, 80 * stage leading to boot-time crash. To avoid this boot-time crash,
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/debug/ |
H A D | openpower-debug-collector-systemd-links.inc | 2 mkdir -p $D$systemd_system_unitdir/obmc-host-crash@0.target.wants 5 # The obmc-host-crash target is repurposed for the memory preserving reboot 9 …LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.wants/openpower-debug-collector-checkstop… 35 …LINK="$D$systemd_system_unitdir/obmc-host-crash@0.target.wants/openpower-debug-collector-checkstop…
|
/openbmc/openbmc/poky/meta/recipes-sato/webkit/webkitgtk/ |
H A D | no-musttail-arm.patch | 6 This causes clang-17 to crash see [1] 7 this code is new in webkit 2.42[2] thats why we do not see the crash in older webkit 12 Upstream-Status: Inappropriate [work around to avoid clang compiler crash]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/webkitgtk/webkitgtk3/ |
H A D | no-musttail-arm.patch | 6 This causes clang-17 to crash see [1] 7 this code is new in webkit 2.42[2] thats why we do not see the crash in older webkit 12 Upstream-Status: Inappropriate [work around to avoid clang compiler crash]
|
/openbmc/bmcweb/.github/ISSUE_TEMPLATE/ |
H A D | config.yml | 5 - name: "Crash bug" 8 "Please file any bug causing a crash to
|
/openbmc/debug-trigger/ |
H A D | README.md | 4 unresponsive. When the signal is received it triggers a crash to collect debug 15 which is to crash the kernel via `/proc/sysrq-trigger`. For systems with kdump
|
/openbmc/qemu/docs/devel/testing/ |
H A D | fuzzing.rst | 210 Building Crash Reproducers 212 When we find a crash, we should try to create an independent reproducer, that 215 Here are the steps for building a reproducer for a crash found by the 218 - Ensure the crash reproduces:: 220 qemu-fuzz-i386 --fuzz-target... ./crash-... 222 - Gather the QTest output for the crash:: 225 qemu-fuzz-i386 --fuzz-target... ./crash-... &> /tmp/trace 237 - Ensure the crash reproduces in qemu-system:: 241 - From the crash output, obtain some string that identifies the crash. This
|
/openbmc/qemu/scripts/oss-fuzz/ |
H A D | minimize_qtest_trace.py | 35 whether the crash occred. Optionally, manually set a string that idenitifes the 36 crash by setting CRASH_TOKEN= 48 type crash but indicates the same bug. Under this situation, our minimizer is 50 use a more sophisticated crash case deduplication method. 87 print(" Usually this indicates a different type of crash.\n") 132 # 1.) Try to remove lines completely and reproduce the crash. 282 sys.exit("The input qtest trace didn't cause a crash...")
|
/openbmc/qemu/qapi/ |
H A D | compat.json | 19 # @crash: abort() the process 24 'data': [ 'accept', 'reject', 'crash' ] }
|
/openbmc/openbmc/poky/meta/recipes-connectivity/connman/connman/ |
H A D | CVE-2025-32743.patch | 4 Subject: [PATCH] dnsproxy: Fix NULL/empty lookup causing potential crash 9 (application crash) or possibly execute arbitrary code, because those
|
/openbmc/openbmc-test-automation/ffdc/ |
H A D | ffdc_config.yaml | 244 - "tar -zcvf /tmp/crash.tar.gz /var/crash" 250 - "/tmp/crash.tar.gz" 289 - "tar -zcvf /tmp/crash.tar.gz /var/crash" 295 - "/tmp/crash.tar.gz" 330 - "tar -zcvf /tmp/crash.tar.gz /var/crash" 336 - "/tmp/crash.tar.gz"
|
/openbmc/phosphor-state-manager/scripts/ |
H A D | host-reboot | 49 # its reboot count and halt in Quiesce if so. But in the host-crash path this 63 "crash so reboot host"
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 283 | 70 crash, so current "something" is a lot better, and this test actual goal is 71 to check that crash is fixed :) 137 # with qemu-io (which will most likely crash qemu if it is still
|
/openbmc/docs/designs/ |
H A D | hw-fault-monitor.md | 75 based on fault incidents (e.g. crash dumps). 98 - On CATERR, the Host Error Monitor requests a crash dump (this is an existing 99 capability). The crash dump includes chipset registers but doesn’t include 103 the crash dump so that it could be post-processed by data center monitoring 109 crash. The fault monitor in the BMC could check link level retries and link
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/host/checkstop-monitor/ |
H A D | checkstop.conf | 2 Conflicts=obmc-host-crash@0.target
|
/openbmc/openbmc/meta-ibm/meta-palmetto/recipes-phosphor/host/checkstop-monitor/obmc/gpio/ |
H A D | checkstop | 4 TARGET=obmc-host-crash@0.target
|