|
|
 |
|
|
Changelog for crash-4.0-8.9.1.SEL5_3.x86_64.rpm :
Wed Sep 9 00:00:00 2009 Anatoly Metetes
- Rebuild for StartCom Linux 5.0.x
Fri Jun 12 00:00:00 2009 Dave Anderson - 4.0-8.9.1.el5
- Fix for running \"foreach bt\" on a live system, where a backtrace that
is attempted on a task that no longer exists may cause a segmentation
violation due to the use of stale/invalid kernel stack pointer.
- Resolves: rhbz#504796
Sat Apr 18 00:00:00 2009 Dave Anderson - 4.0-8.9.el5
- Re-based package to upstream version 4.0-8.9.
- Resolves: rhbz#494028
- Fix for nonsensical usage of the \"set\" command when running
against the xen hypervisor binary. If entered alone on the
command line, the command would cause a segmentation violation,
because there is no concept of a \"context\" in the xen hypervisor.
In addition, more reasonable error messages are displayed if
\"set\", \"set -c \", \"set -p\", or \"set \" are
attempted when running against a xen hypervisor.
- Resolves: rhbz#462819
- Fix for \"irq -d\" option when run on x86_64 xen kernels. Without the
patch it would indicate: \"irq: invalid structure size: gate_struct\"
and dump a stack trace leading to x86_64_display_idt_table(). Now it
will indicate that the -d option is not applicable.
- Resolves: rhbz#464116
- Fixes for the \"bt\" command when running against the xen hypervisor
binary. The \"bt -o\" option, and setting it to run by default with
\"bt -O\", would fail with the vmlinux-specific error message \"bt:
invalid structure size: desc_struct\" with a stack trace leading
to read_idt_table(); with the patch it will display the generic
error message \"bt: -o option not supported or applicable on this
architecture or kernel\". The \"bt -e\" or \"bt -E\" will also display
the same error message, as opposed to the command usage message.
Lastly, the \"bt -R\" option would cause a segmentation violation;
it has been fixed to work as it was designed.
- Resolves: rhbz#464288
- Fix for the \"bt\" command when run on a xen hypervisor in which the
backtrace leads to either \"process_softirqs\" or \"page_fault\".
Without the patch, the backtrace indicates: \"bt: cannot resolve stack
trace\", and then the recovery code terminates the command with the
nonsensical error message: \"bt: invalid structure size: task_struct\".
- Resolves: rhbz#466724
- Fix for \"bt -a\" command when running against the xen hypervisor where
the number of physical cpus outnumber the MAX_VIRT_CPUS value for the
processor type. Without the patch on such a system, \"bt -a\" would
fail after displaying backtraces for the first 32 (MAX_VIRT_CPUS)
pcpus with the the error message: \"bt: invalid vcpu\". The patch also
corrects the \"vcpus\" command output to show the vcpus associated with
pcpus 32 through 63, and the \"doms\" command output to show the second
idle domain associated with pcpus 32 through 63.
- Resolves: rhbz#471790
- Fix for the \"bt\" command when run on a xen hypervisor in which the
backtrace leads to either \"process_softirqs\" or \"page_fault\".
Without the patch, the backtrace indicates: \"bt: cannot resolve stack
trace\", and then the recovery code terminates the command with the
nonsensical error message: \"bt: invalid structure size: task_struct\".
- Resolves: rhbz#474712
- Fix for \"mod -[sS]\" command if the target module object filename
contains both underscore and dash characters. Without the patch
the module load would fail with the error message: \"mod: cannot
find or load object file for module\". Examples are
the \"aes_x86_64\" module from the \"aes-x86_64.ko\" object file, and
the \"dm_region_hash\" module from the \"dm-region_hash.ko\" object file.
- Resolves: rhbz#480136
- 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)!\"
- Resolves: rhbz#487429
- The starting backtrace location of active, non-crashing, xen dom0
tasks are not available in kdump dumpfiles, nor is there anything
that can be searched for in their respective stacks. Therefore, for
those those tasks, the \"bt\" command will indicate: \"bt: starting
backtrace locations of the active (non-crashing) xen tasks cannot be
determined: try -t or -T options\". Without the patch, the backtrace
would either be empty, or it would show an invalid backtrace starting
at the last location where schedule() had been called.
- Fix for potentially empty \"bt -t\" output, and for \"bt -T\" potentially
dumping the text return addresses in the hard or soft IRQ stacks
instead of the process stack. This could occur if the targeted task
was the last task that used the hard or soft IRQ stack (x86 only).
- Resolves: rhbz#495586
Thu Jan 8 23:00:00 2009 Dave Anderson - 4.0-7.2.4
Fix for a \"bt\" command segmentation violation by correctly
handling the transition from the IRQ stack back to the process
stack running when running against a Xen kernel.
- Resolves: rhbz#478904
Fri Sep 26 00:00:00 2008 Dave Anderson - 4.0-7.2.3
Fix for the incomplete resolution for the \"search -k\" option when
run on RHEL5 ia64 CONFIG_SPARSEMEM kernels. The initial fix
addressed the segmentation violation, but on certain physical
memory configurations, it would prematurely bail out when making
the transition from the kernel mapped region to the vmalloc region.
- Resolves: rhbz#458417
Wed Sep 24 00:00:00 2008 Dave Anderson - 4.0-7.2.2
Fix for x86 \"bt\" command to correctly handle the transition from
the hard IRQ stack back to the process stack and then display
the interrupt exception frame.
- Resolves: rhbz#462624
Tue Sep 16 00:00:00 2008 Dave Anderson - 4.0-7.2.1
- Fix to prevent a potential divide-by-zero SIGFPE exception when
using a vmlinux that does not match the vmcore being analyzed.
This is a bad, but acceptable, practice, although when done, it
usually requires adding a System.map file to the command line
so that the correct symbol values are used; that was not done
in this case.
- Resolves: rhbz#457371
- Fix for the crash utility\'s \"search -u\" option, which searches
the current context\'s user virtual address space for a given value.
It would cause a SIGSEGV when run on a xen-syms hypervisor binary,
and gives a somewhat misleading error message when run on vmlinux
binary on a kernel thread. Both of these usages are nonsensical
because the xen-syms hypervisor and vmlinux kernel threads do not
have user address space regions. Fix for the \"search -k\" option,
which searches the kernel virtual address space for a given value.
When run on a xen-syms hypervisor binary, it would display a
nonsensical vmlinux-based error message. That option should not
be used with the xen-syms hypervisor, which requires that a starting
virtual address be supplied. The fix now displays error messages
that are applicable to the incorrect command usage.
- Resolves: rhbz#457373
Fix for the \"search -k\" option when run on RHEL5 ia64 CONFIG_SPARSEMEM
kernels. It would cause a segmentation violation, because it would
start the search at the base of the ia64 processor\'s identity-mapped
region, which is not necessarily backed by physical memory, and result
in a SIGSEGV. The fix sets the start of the ia64 kernel virtual address
space search to the appropriate virtual address.
- Resolves: rhbz#458417
Enhancement for invoking crash with an input-file of crash commands
using the -i command-line option, as in \"crash -i ...\",
and doing so from inside a script file instead of the command line.
It would indicates \"crash: /dev/tty: No such device or address\", run
the commands in the input-file, but then would hang. The fix terminates
the crash session after all of the commands in the input-file have
completed.
- Resolves: rhbz#458422
Sat Apr 26 00:00:00 2008 Dave Anderson - 4.0-5.0.3
- Fixes for xen 5.2 hypervisor support.
- Resolves: rhbz#442438
Thu Jan 17 23:00:00 2008 Dave Anderson - 4.0-5.0.2
- Fix for initialization-time segmentation violation when analyzing
a vmcore in which the kernel has over-run its kernel stack,
corrupting the process thread_info structure, which is used by
the crash utility for determining the process cpu.
- Resolves: rbhz#405101
Thu Jan 17 23:00:00 2008 Dave Anderson - 4.0-5.0.1
- Fix for initialization-time failure when analyzing a vmcore of
an i386-HVM guest that was taken when running on an x86_64 host
- Resolves: rbhz#288691
- Fix for initialization-time segmentation violation when analyzing
a vmcore in which the kernel has over-run its kernel stack,
corrupting the process thread_info structure, which is used by
the crash utility for determining the process cpu.
- Resolves: rbhz#405101
- Fix for \"mod\" command when analyzing ppc64 kernels with 64K pages.
- Resolves: rbhz#414881
Tue Aug 28 00:00:00 2007 Dave Anderson - 4.0-4.6.1
- Fix for \"bt\" command segmentation violation when run against
an x86 xen-syms hypervisor.
- Resolves: rhbz#252198
Sat Jun 23 00:00:00 2007 Dave Anderson - 4.0-4.3.1
- Fix for \"dev -p\" command for ppc64 machines with virtual devices
and for kernels that don\'t have the \"pci_device\" symbol.
- Resolves: rhbz#220929
- Fix for \"crash: cannot resolve \"init_task_union\" errors due to
to \"__per_cpu_start\" and \"__per_cpu_end\" symbols changing from
type \'A\' to type \'D\'.
- Resolves: rhbz#221901
- Fix for segmentation fault when attempting to read a xen core dump
from a 6 GB guest.
- Resolves: rhbz#224535
- Fix for crash session initialization failure indicating \"crash:
cannot read/find cr3 page\" in xendumps where the cr3 register
value in the dumpfile header is overloaded to be able to use
page directory pages that are greater than 4GB.
- Resolves: rhbz#223454
- Support for determining the physical base address in FV relocatable
x86_64 xendump dumpfiles run as xen guests.
- Resolves: rhbz#233151
Create a new crash-devel package for extension modules, which installs
defs.h in /usr/include/crash.
- Resolves: rhbz#241045
Reasonable backtraces for x86_64.
- Resolves: rhbz#221355
Fri Dec 1 23:00:00 2006 Dave Anderson - 4.0-3.14
- Fix for s390x live system analysis to recognize debuginfo vmlinux
file that contains an ASCII char adjacent to the Linux version
string.
- Resolves: rhbz#216973
Mon Nov 20 23:00:00 2006 Dave Anderson - 4.0-3.12
- Fix for ia64 kdump vmcore backtraces when crash was generated
via INIT switch or due to an MCA exception.
- Resolves: rhbz#216037
Wed Nov 8 23:00:00 2006 Dave Anderson - 4.0-3.11
- Revisited fix for BZ #213929; when crash is run in a small
terminal window, gdb does line-wrapping that breaks the fix
for x86_64 backtraces.
Fri Nov 3 23:00:00 2006 Dave Anderson - 4.0-3.10
- Updated crash.patch to match upstream version 4.0-3.9, bumped
by 1 to differentiate from RHEL4-5 errata version.
- Fixes for x86_64 \"bt\" command for tasks that have transitioned
to the IRQ stack from the process stack via hardware interrupt
or call_softirq entry point, and to the NMI stack from the
process stack.
- Resolves: rhbz#213929
Sat Oct 14 00:00:00 2006 Dave Anderson - 4.0-3.7
- Updated crash.patch to match upstream version 4.0-3.7.
- Resolves: rhbz#207296 rhbz#210471
Thu Sep 14 00:00:00 2006 Dave Anderson - 4.0-3.3
- Updated crash.patch to match upstream version 4.0-3.3.
- Support for x86_64 relocatable kernels. BZ #204557
Tue Aug 8 00:00:00 2006 Dave Anderson - 4.0-3.1
- Updated crash.patch to match upstream version 4.0-3.1.
- Added kdump reference to description.
- Added s390 and s390x to ExclusiveArch list. BZ #199125
- Removed LKCD v1 pt_regs references for s390/s390x build.
- Removed LKCD v2_v3 pt_regs references for for s390/s390x build.
Sat Jul 15 00:00:00 2006 Jesse Keating - 4.0-3
- rebuild
Tue May 16 00:00:00 2006 Dave Anderson - 4.0-2.26.4
- Updated crash.patch such that is not #include\'d
by s390_dump.c; IBM did not make the file s390[s] only; BZ #192719
Tue May 16 00:00:00 2006 Dave Anderson - 4.0-2.26.3
- Updated crash.patch such that is not #include\'d
by vas_crash.h; only ia64 build complained; BZ #191719
Tue May 16 00:00:00 2006 Dave Anderson - 4.0-2.26.2
- Updated crash.patch such that is not #include\'d
by lkcd_x86_trace.c; also for BZ #191719
Tue May 16 00:00:00 2006 Dave Anderson - 4.0-2.26.1
- Updated crash.patch to bring it up to 4.0-2.26, which should
address BZ #191719 - \"crash fails to build in mock\"
Tue Feb 7 23:00:00 2006 Jesse Keating - 4.0-2.18.1
- rebuilt for new gcc4.1 snapshot and glibc changes
Wed Jan 4 23:00:00 2006 Dave Anderson 4.0-2.18
- Updated source package to crash-4.0.tar.gz, and crash.patch
to bring it up to 4.0-2.18.
Fri Dec 9 23:00:00 2005 Jesse Keating
- rebuilt
Thu Mar 3 23:00:00 2005 Dave Anderson 3.10-13
- Compiler error- and warning-related fixes for gcc 4 build.
- Update to enhance x86 and x86_64 gdb disassembly output so as to
symbolically display call targets from kernel module text without
requiring module debuginfo data.
- Fix hole where an ia64 vmcore could be mistakenly accepted as a
usable dumpfile on an x86_64 machine, leading eventually to a
non-related error message.
Wed Mar 2 23:00:00 2005 Dave Anderson 3.10-12
- rebuild (gcc 4)
Thu Feb 10 23:00:00 2005 Dave Anderson 3.10-9
- Updated source package to crash-3.10.tar.gz, containing
IBM\'s final ppc64 processor support for RHEL4
- Fixes potential \"bt -a\" hang on dumpfile where netdump IPI interrupted
an x86 process while executing the instructions just after it had entered
the kernel for a syscall, but before calling the handler. BZ #139437
- Update to handle backtraces in dumpfiles generated on IA64 with the
INIT switch (functionality intro\'d in RHEL3-U5 kernel). BZ #139429
- Fix for handling ia64 and x86_64 machines booted with maxcpus=1 on
an SMP kernel. BZ #139435
- Update to handle backtraces in dumpfiles generated on x86_64 from the
NMI exception stack (functionality intro\'d in RHEL3-U5 kernel).
- \"kmem -[sS]\" beefed up to more accurately verify slab cache chains
and report errors found.
- Fix for ia64 INIT switch-generated backtrace handling when
init_handler_platform() is inlined into ia64_init_handler();
properly handles both RHEL3 and RHEL4 kernel patches.
BZ #138350
- Update to enhance ia64 gdb disassembly output so as to
symbolically display call targets from kernel module
text without requiring module debuginfo data.
Thu Jul 15 00:00:00 2004 Dave Anderson 3.8-5
- bump release for fc3
Wed Jul 14 00:00:00 2004 Dave Anderson 3.8-4
- Fix for gcc 3.4.x/gdb issue where vmlinux was mistakenly presumed non-debug
Sat Jun 26 00:00:00 2004 Dave Anderson 3.8-3
- remove (harmless) error message during ia64 diskdump invocation when
an SMP system gets booted with maxcpus=1
- several 2.6 kernel specific updates
Fri Jun 18 00:00:00 2004 Dave Anderson 3.8-2
- updated source package to crash-3.8.tar.gz
- diskdump support
- x86_64 processor support
Tue Sep 23 00:00:00 2003 Dave Anderson 3.7-5
- make bt recovery code start fix-up only upon reaching first faulting frame
Sat Sep 20 00:00:00 2003 Dave Anderson 3.7-4
- fix \"bt -e\" and bt recovery code to recognize new __KERNEL_CS and DS
Thu Sep 11 00:00:00 2003 Dave Anderson 3.7-3
- patch to recognize per-cpu GDT changes that redefine __KERNEL_CS and DS
Thu Sep 11 00:00:00 2003 Dave Anderson 3.7-2
- patches for netdump active_set determination and slab info gathering
Thu Aug 21 00:00:00 2003 Dave Anderson 3.7-1
- updated source package to crash-3.7.tar.gz
Thu Jul 24 00:00:00 2003 Dave Anderson 3.6-1
- removed Packager, Distribution, and Vendor tags
- updated source package to crash-3.6.tar.gz
Sat Jul 19 00:00:00 2003 Jay Fenlason 3.5-2
- remove ppc from arch list, since it doesn\'t work with ppc64 kernels
- remove alpha from the arch list since we don\'t build it any more
Sat Jul 19 00:00:00 2003 Matt Wilson 3.5-1
- use %defattr(-,root,root)
Wed Jul 16 00:00:00 2003 Jay Fenlason
- Updated spec file as first step in turning this into a real RPM for taroon.
- Wrote man page.
|
|
|
