Bug 1248859
Summary: | [aarch64] crash command "bt -f" Segmentation fault | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Qiao Zhao <qzhao> |
Component: | crash | Assignee: | Dave Anderson <anderson> |
Status: | CLOSED ERRATA | QA Contact: | Qiao Zhao <qzhao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | jbastian, lilu, qzhao, shdeng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | crash-7.1.2-2.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 12:00:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Qiao Zhao
2015-07-31 03:24:30 UTC
Qiao, Did you save the vmcore file? It's typically impossible to debug crash issue that occur with dumpfiles without having the vmcore. I have another vmcore and can reproduce the problem. This was introduced by this RHEL7.2 bugzilla: BZ #1227508 - Enhancement to the ARM64 backtrace capability https://bugzilla.redhat.com/show_bug.cgi?id=1227508 It requires a one-line fix. Fix applied in the upstream crash-utility git repository: https://github.com/crash-utility/crash/commit/9c102f994856d1de5a62644822d07a99318073cb Fix for a segmentation violation generated by the ARM64 "bt -[f|F]" options when analyzing the active tasks in vmcores generated by the kdump facility. This bug is a regression that was introduced in crash-7.1.2 by commit 15a58e4070486efa2aa965bdd636626e62b65cc7, which was an enhancement of the ARM64 backtrace capability for active tasks in kdump vmcores. (anderson) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2102.html |