[ANNOUNCE] crash version 5.0.7 is available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 - Introduction of ARM processor support for the crash utility.  This is
   the result of collaborative effort between Nokia and Sony Ericsson.
   The crash utility can be built as a native ARM binary to analyze ARM
   dumpfiles or run live on an ARM host, or alternatively it can be 
   built as an x86 binary to analyze ARM dumpfiles.  To build crash as 
   an ARM binary on an ARM host, enter "make" alone.  To build crash as 
   an x86 binary on an x86 host, enter "make target=ARM".  By extension, 
   the x86 binary can also be run on an x86_64 host.  It supports kdump,
   and diskdump formats, and live using /dev/mem on ARM hosts.  Stack
   unwinding support uses both frame pointers and ARM unwind tables.
   (ext-mika.1.westerberg@xxxxxxxxx, Jan.Karlsson@xxxxxxxxxxxxxxxx,
    Thomas.Fange@xxxxxxxxxxxxxxxx)

 - Fix to support KVM dumpfiles that have "ram" device header sections 
   with a version_id of 4.  Without the patch, the crash session fails
   with the error message "crash: qemu-load.c:267: ram_init_load: 
   Assertion `version_id == 3' failed".
   (pbonzini@xxxxxxxxxx, anderson@xxxxxxxxxx)

 - 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, all kinds of error messages would be
   displayed during invocation, and in all probability, the session 
   would fail.
   (anderson@xxxxxxxxxx)

 - Minor fix to memory.c to address a compiler warning when building 
   with "make warn", or a compiler failure when using "make Warn".
   (anderson@xxxxxxxxxx)

 - Fix for a segmentation violation caused by the "mount" command in the
   rare circumstance where the "init" task (pid 1) does not exist.
   (bob.montgomery@xxxxxx)

 - CONFIG_PREEMPT_RT x86_64 realtime kernels allocate only 3 exception 
   stacks to handle the 5 possible exception types, and therefore the 
   same per-cpu stack may be used for different exception types.  This 
   could cause "bt" output that contained exception stack name strings 
   to be incorrect.  The patch displays all exception stack name strings
   in RT kernels to all show "RT", as in "--- <RT exception stack> ---".
   (anderson@xxxxxxxxxx)

 - Fix for the potential to miss one or more tasks in 2.6.23 and earlier
   kernels, presumably due to catching an entry the kernel's pid_hash[] 
   chain in transition.  Without the patch, the task will simply not be
   seen in the gathered task list.
   (bob.montgomery@xxxxxx)

 - Fix to correct a presumption that the kernel's task_state_array[] 
   is NULL terminated.
   (holzheu@xxxxxxxxxxxxxxxxxx)

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

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility


[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux