RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
"bt -f" command will trigger Segmentation fault.
detail info: http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2015/07/10323/1032336/2115170/32833830/crash.vmcore.log

https://beaker.engineering.redhat.com/jobs/1032336

Version-Release number of selected component (if applicable):
4.2.0-0.rc3.15.el7.aarch64
crash-7.1.2-1.el7.aarch64
kexec-tools-2.0.7-28.el7.aarch64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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