- If a live kernel crash session fails during initialization due to read errors, and it appears to be because the running kernel was configured with CONFIG_STRICT_DEVMEM, display this warning message: "crash: This kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source." (anderson(a)redhat.com) - Fix for the "bt" command to prevent a segmentation violation seen with an x86_64 Egenera/LKCD dumpfile where the starting stack hooks for the active tasks in the dumpfile header were nonsensical. (anderson(a)redhat.com) - Fix for the chronological display of the kernel printk buffer data by the "log" output if the administrator has cleared the buffer with syslog() or klogctl(). (oomichi(a)mxs.nes.nec.co.jp) - Change the message displayed when supplying a non-process stack address as an argument to "bt -S". Because the supplied address is typically valid, such as a hard or soft IRQ stack address, the message will indicate "non-process address" instead of "invalid stack address". (anderson(a)redhat.com) - The crash-<release>.src.rpm will create an additional binary crash-extensions-<release>.rpm file containing the sial.so and dminfo.so extension modules. The modules will be installed in the /usr/lib[64]/crash/extensions directory. (holzheu(a)linux.vnet.ibm.com, anderson(a)redhat.com) - If a shared-object filename passed to the "extend" command is not expressed with a fully-qualified pathname, the following directories will be searched in the order shown, and the first instance of the file that is found will be selected: 1. the current working directory 2. the directory specified in the CRASH_EXTENSIONS shell environment variable 3. /usr/lib64/crash/extensions (64-bit architectures) 4. /usr/lib/crash/extensions The same rules will be applied when unloading shared object files with "extend -u <shared-object>". Without the patch, only files in the current directory or those specified with a fully-qualified pathname were accepted. (anderson(a)redhat.com) - Changed the manner in which the "bt" command determines which PID 0 swapper task was interrupted by an ia64 INIT or MCA exception. There is an existing ia64 INIT/MCA handler bug which incorrectly writes the pseudo task's command name in its comm[] name string such that the cpu number may not be part of the string. If that happens without this patch, the "bt" command fails to make the link back to the interrupted task, and displays the error message: "bt: unwind: failed to locate return link (ip=0x0)!" (anderson(a)redhat.com) - Removed an unused initialized variable in get_task_mem_usage(). (junkoi2004(a)gmail.com) - Added a debug-level 8 statement in readmem() that will display the current input address and its translated physical address under the existing debug-level 4 "<readmem: ...>" debug line, put in place to aid in debugging read and/or seek errors. (anderson(a)redhat.com) Download from: http://people.redhat.com/anderson