Jump to letter: [
9ABCDEFGHIJKLMNOPQRSTUVWXYZ
]
crash - Kernel crash and live system analysis utility
- Description:
The core analysis suite 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.
Packages
| crash-5.1.8-1.el5.i386
[2.2 MiB] |
Changelog
by Dave Anderson (2011-10-04):
- Rebase to upstream version 5.1.8.
Resolves: rhbz#715072
- Fix for the x86_64 "bt" command if the shutdown NMI is issued to a
32-bit task that has executed a "sysenter" instruction and the RSP
still contains the zero value loaded from the MSR_IA32_SYSENTER_ESP
register. The backtrace issued a warning message indicating
"WARNING: possibly bogus exception frame", and was unable to make a
transition from the NMI exception stack back to the process stack.
Resolves: rhbz#676408
- Fix for the x86 "bt" command for several backtraces of non-crashing
active tasks that fail with "bt: cannot resolve stack trace" errors
due to the failure to properly transition from the shutdown NMI stack
back to the process stack.
Resolves: rhbz#713050
- Fix to more correctly determine the KVM I/O hole size and location.
The I/O hole size to this point in time is either 1GB or 512MB, but
its setting is hardwired into the Qemu code that was used to create
the dumpfile. The dumpfile is a "savevm" file that is designed to be
used for guest migration, and since inter-version save/load is not
supported, the I/O hole information does not have to be encoded into the
dumpfile. Without the patch, the I/O hole for dumpfiles created by
older Qemu version was not being set to 1GB, so if the KVM guest was
configured with more than 3GB of memory, the crash session would
typically display numerous "read error" messages during session
initialization.
Resolves: rhbz#715070
- Fix for KVM dumpfiles from guests that were provisioned with more
than 3.5GB of RAM. KVM virtual systems contain an I/O hole in the
physical memory region from 0xe0000000 to 0x100000000 (3.5GB to 4GB).
If a guest is provisioned with more than 3.5GB of RAM, then the
memory above 3.5GB is "pushed up" to start at 0x100000000 (4GB).
But the "ram" device headers in the KVM dumpfiles do not reflect
that, and so without the patch, numerous error messages would be
displayed during invocation, and in all probability, the session
would fail.
Resolves: rhbz#716327
|
