[Crash-utility] crash version 4.0-4.13 is available

[Dave Anderson]

Changelog:

- If the vmlinux file or dumpfile is a machine type mismatch with
   the crash utility binary, or far less likely, a ppc64 or ia64
   endian mismatch, the crash session will fail during initialization
   with the generic error message, "crash: <filename>: not a
   supported file format".  To aid the user in understanding what
   caused the failure, this patch prepends an additional error
   message that clarifies the reason behind the mismatch.
   (anderson at redhat.com, bwalle at suse.de)

- An update for "kmem -V" option, which currently displays the kernel's
   "vm_stat" counter values, will now also display the "vm_event_states"
   counter values, both of which were introduced in 2.6.18.  For 2.6
   kernels prior to 2.6.18, the precursor "page_states" counter values
   will be displayed.  (anderson at redhat.com)

- Implemented a new "kmem -z" option to display per-zone memory
   statistics.  The amount of data displayed is dependent upon the
   kernel version.  At a minimum, the size, min/low/high and free
   page counts are shown.  If the zone struct contains nr_active,
   nr_inactive, pages_scanned and all_unreclaimable members, those
   fields are shown.  If the zone struct contains a per-zone vm_stat[]
   array (identical to the system-wide vm_stat[] array), its contents
   are dumped.  For any other data in the zone, the address of the
   zone structure is displayed.
   (anderson at redhat.com)

- Fix for the RSS amounts displayed by the "ps" and "vm" commands
   on 2.6 kernels prior to 2.6.13.  (anderson at redhat.com)

- Fix for the x86 "bt" command when running a version of crash built
   on a pre-2.6.20 host against a 2.6.20 or later dumpfile, or when
   running a version of crash build on a 2.6.20 or later host against
   a pre-2.6.20 dumpfile.  Without the patch, kernel exception frames
   would be mistaken for, and displayed as, user exception frames, and
   parts of the backtrace above the kernel exception frame would be
   truncated.  (atyson at hp.com)

- Fix for FC8 xen x86 kernels (2.6.21-2952.fc8xen) that fail during
   initialization after reporting "WARNING: cannot read linux_banner
   string", followed by the fatal error message "crash: vmlinux and
   vmcore do not match!".  This required a change to the virtual
   address mask value used to determine the base value of the x86
   kernel's unity-mapped virtual address region.  (anderson at redhat.com)

- Set a default "phys_base" value for recent fully-virtualized
   relocatable x86_64 kernels whose text start address is not equal
   to the __START_KERNEL_map value.  Without the patch, the crash
   session fails during initialization with the warning message
   "WARNING: cannot read linux_banner string", followed by the fatal
   error message "crash: vmlinux and vmcore do not match!".  The
   error can alternatively be worked around if the "phys_base" value
   is first determined by running a crash session on the live system
   that generated the dumpfile, by entering: "help -m | grep phys_base".
   The value shown can then be used when running against the dumpfile
   like so: "crash --machdep phys_base=<value> vmlinux vmcore"
   (anderson at redhat.com)

- Debug: implemented a new "--active" crash command line option, which
   will gather only the active tasks from each runqueue, skipping the
   traversal of the kernel's pid_hash mechanism.
   (anderson at redhat.com)

- Debug: "help -n" formats and displays ASCII VMCOREINFO data.
   (anderson at redhat.com)

Download from: http://people.redhat.com/anderson