Skip to navigation

Bug Fix Advisory crash bug fix update

Advisory: RHBA-2010:0230-1
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2010-03-30
Last updated on: 2010-03-30
Affected Products: RHEL Desktop Workstation (v. 5 client)
Red Hat Enterprise Linux (v. 5 server)
Red Hat Enterprise Linux Desktop (v. 5 client)

Details

Updated crash packages that fix various bugs and add enhancements are now
available.

The crash package is a core analysis suite. It is a self-contained tool
that can be used to investigate either live systems, kernel core dumps
created from the netdump, diskdump, and kdump packages from Red Hat Linux,
the mcore kernel patch offered by Mission Critical Linux, or the LKCD
kernel patch.

* if a kdump NMI was issued and the task kernel stack was changed, the
backtrace would in some cases fail and produce an error: "bt: cannot
transition from exception stack to current process stack". The crash
package was updated to report task inconsistencies and change the active
task as appropriate. Additionally, a new set -a option was added to
manually set tasks to be the active task on its CPU. (BZ#504952)

* if the kernel data structures in a non-matching vmlinux varied widely
enough from the kernel that generated the vmcore, erroneous data could be
read and consumed. Several new defensive mechanisms have been added and it
now fails in a more reasonable manner. (BZ#508156)

* running the bt -a command against a Xen hypervisor resulted in a
"cannot resolve stack trace" warning message if the CPU received its
shutdown NMI while running in an interrupt handler. The bt command was
changed and the error no longer occurs. (BZ#510505)

* added support for dumpfile format of virsh dump of KVM kernels.
(BZ#510519)

* if a dump was collected when there were one or more cpus offline in the
system, an initialization-time failure would occur and the crash would
abort. A patch was backported from upstream and the failure no longer
occurs. (BZ#520506)

* running the 64-bit bt command could potentially start the backtrace of
an active non-crashing task on its per-cpu IRQ stack, cause a faulty
transition back to the process stack, the dumping of a bogus exception
frame and the message "bt: WARNING: possibly bogus exception frame". The
bt command was changed and it now starts from the NMI exception stack, the
error no longer occurs. (BZ#523512)

* when the cpu_possible_map contains more CPUs than the cpu_online_map, the
set, bt, runq and ps commands would reflect the existing but unused swapper
tasks on the non-existent CPUs. The 64-bit PowerPC CPU count determination
was fixed and the commands now run as expected. (BZ#550419)

* when INIT-generated pseudo-tasks were running in user-space and the
kernel was unable to modify the kernel stack, the backtrace would not
identify the interrupted task and would display a "bt: unwind: failed to
locate return link" error message. The Itanium backtraces were fixed, and
the backtrace now offers information regarding the task that was
interrupted. The error message is also suppressed. (BZ #553353)

* using dump to analyze very large xendump core files with ELF sections
located beyond a file offset of 4GB resulted in errors. Changes were made
to the xc_core_verify() initialization code and dump now works as expected.
(BZ #561767)

* The crash utility was rebased. See the changelog linked to in the
references section below for full details. (BZ#528184)

All users of crash are advised to upgrade to these updated packages,
which resolve these issues.


Solution

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259

Updated packages

RHEL Desktop Workstation (v. 5 client)

SRPMS:
crash-4.1.2-4.el5.src.rpm
File outdated by:  RHBA-2013:0140
    MD5: 6e417c39a1eb67f649229ba592122957
SHA-256: 69c7c47ee55a56de6246aa06ba500ade80f5ddf02c1194639ce6e32435c046d9
 
IA-32:
crash-devel-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8774ff0bf829525d89c1240328b57c09
SHA-256: 7bae4c7bcd79e40c9c854066870c4ff4db24d553ad6adf5ce64a817dba5f429c
 
x86_64:
crash-devel-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8774ff0bf829525d89c1240328b57c09
SHA-256: 7bae4c7bcd79e40c9c854066870c4ff4db24d553ad6adf5ce64a817dba5f429c
crash-devel-4.1.2-4.el5.x86_64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 11edbe9ca51bae2060e21616ee55b4eb
SHA-256: 5c5955c9db6b24fa02b182126afce7835bbf71c978e878477ec32f3026b294f2
 
Red Hat Enterprise Linux (v. 5 server)

SRPMS:
crash-4.1.2-4.el5.src.rpm
File outdated by:  RHBA-2013:0140
    MD5: 6e417c39a1eb67f649229ba592122957
SHA-256: 69c7c47ee55a56de6246aa06ba500ade80f5ddf02c1194639ce6e32435c046d9
 
IA-32:
crash-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: adb49e420a515d2c3649c14ceac678b5
SHA-256: 66f6b359aa0be1656fe8e578f9892490dac4d6f517eb3d4bb1d199f7b47147f8
crash-devel-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8774ff0bf829525d89c1240328b57c09
SHA-256: 7bae4c7bcd79e40c9c854066870c4ff4db24d553ad6adf5ce64a817dba5f429c
 
IA-64:
crash-4.1.2-4.el5.ia64.rpm
File outdated by:  RHBA-2013:0140
    MD5: a1641868f2730976bfdd4f23e59a3228
SHA-256: b99d4a52e52fa4268e3b34c5a9a2b1c7545d43cd2a8069c321edd87e0e79cb8e
crash-devel-4.1.2-4.el5.ia64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 595590337beb6924421374b395aa8ab6
SHA-256: 365be89d64491b8ac7ea19455af5d0f2539a683aed0b55e27dc64ff26d41b41e
 
PPC:
crash-4.1.2-4.el5.ppc64.rpm
File outdated by:  RHBA-2013:0140
    MD5: b39543f0d5957c0ca9addbe01eee09f7
SHA-256: 89fb7570c5b0014b2c9f5a9b300b13ca94bbbcc70d9acd526c3a8f65ab167fdb
crash-devel-4.1.2-4.el5.ppc64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 0cd3eb154767bdf4531899a8cb217df1
SHA-256: af2a21583b41a1e8de01709fca9f569a4bc28378d6b6a6a71c817d725c770129
 
s390x:
crash-4.1.2-4.el5.s390x.rpm
File outdated by:  RHBA-2013:0140
    MD5: 611d7f526196d8ceed87ada323de1fde
SHA-256: aea023bce812d5ddacfe330693602929db7950a56849a12459847c6a3cb97257
crash-devel-4.1.2-4.el5.s390.rpm
File outdated by:  RHBA-2013:0140
    MD5: ec302813e556c3bc1b3bf13baff9172b
SHA-256: 3c5254838e11e46d43541bc3f9c42fef3ea3af5ce3b4771989bd182b4e47dea9
crash-devel-4.1.2-4.el5.s390x.rpm
File outdated by:  RHBA-2013:0140
    MD5: 0938071ad826370194b8094dfa38fdbe
SHA-256: 75088db4a6fcf75af0f4370ee19a8f71a0b746c2ccaf1536da369cde1b328275
 
x86_64:
crash-4.1.2-4.el5.x86_64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8c6607298a5eff9d81a2f845c0984585
SHA-256: 14466b111a4eafe70dfbac4cede25358eaf2081ba8e1d6e1678b703159c6d4ee
crash-devel-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8774ff0bf829525d89c1240328b57c09
SHA-256: 7bae4c7bcd79e40c9c854066870c4ff4db24d553ad6adf5ce64a817dba5f429c
crash-devel-4.1.2-4.el5.x86_64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 11edbe9ca51bae2060e21616ee55b4eb
SHA-256: 5c5955c9db6b24fa02b182126afce7835bbf71c978e878477ec32f3026b294f2
 
Red Hat Enterprise Linux Desktop (v. 5 client)

SRPMS:
crash-4.1.2-4.el5.src.rpm
File outdated by:  RHBA-2013:0140
    MD5: 6e417c39a1eb67f649229ba592122957
SHA-256: 69c7c47ee55a56de6246aa06ba500ade80f5ddf02c1194639ce6e32435c046d9
 
IA-32:
crash-4.1.2-4.el5.i386.rpm
File outdated by:  RHBA-2013:0140
    MD5: adb49e420a515d2c3649c14ceac678b5
SHA-256: 66f6b359aa0be1656fe8e578f9892490dac4d6f517eb3d4bb1d199f7b47147f8
 
x86_64:
crash-4.1.2-4.el5.x86_64.rpm
File outdated by:  RHBA-2013:0140
    MD5: 8c6607298a5eff9d81a2f845c0984585
SHA-256: 14466b111a4eafe70dfbac4cede25358eaf2081ba8e1d6e1678b703159c6d4ee
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

504952 - bt: cannot transition from exception stack to current process stack
510519 - [RHEL5.4 KVM]: Unimplemented "virsh dump" capability - crash utility support
528184 - Rebase request for crash utility RHEL5.5 errata
550419 - bt:cannot determine NT_PRSTATUS ELF note for active task
553353 - [5.4] Crash fails to backtrace on IA64 machine
561767 - xm dump-core creates dump that crash cannot process


References



These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/