Revisions of crash
1
1
Upgrade to crash-7.1.1.
1
1
1
1
Upgrade to 7.0.7 (forwarded request 239876 from ptesarik)
Automatic submission by obs-autosubmit
Enable snappy compression (forwarded request 234362 from ptesarik)
Fix NMI backtraces (forwarded request 232167 from ptesarik)
- Implementation of 7.0.5 from upstream, including patch refresh Changelog: - Fix for the "runq -g" option for kernels that are configured with CONFIG_FAIR_GROUP_SCHED, but not CONFIG_CFS_BANDWIDTH. Without the patch, the command fails with the message "runq: invalid structure member offset: cfs_rq_throttled". (vinayakm.list@gmail.com) - Add support for Xen PVH guest types introduced in Xen 4.4. Without the patch, running against a Xen 4.4 hypervisor binary would fail during session initialization with the error message "crash: invalid structure member offset: domain_is_hvm". In addition, the PVH guest type is being registered internally as an HVM guest type, the debug "help -X ofs" command's display of the domain_domain_flags offset has been fixed to show it in decimal, and the setting of the internal dc->domain_flags has been fixed to contain all flags set, not just the first one found. (dslutz@verizon.com) - Fix for the "kmem -S" command on Linux 3.1 and later kernels that are configured with CONFIG_SLUB. Because the the page structure's inuse and objects fields used by SLUB were changed from discrete u16 types to bit-fields within an unsigned int, the display of per-node partial slab statistics are incorrect. Without the patch, the TOTAL and ALLOCATED values are incorrectly shown as equal values, and therefore the FREE value is always zero. (anderson@redhat.com) - Fix for the "kmem -S" command for kernels that are configured with CONFIG_SLUB. Eash per-cpu slab object dump may show incorrect ALLOCATED and FREE values; and as seen on Linux 3.5 and later kernels, the TOTAL value and the number of individual objects dumped may also be incorrect (too small). (anderson@redhat.com) ... (forwarded request 222786 from dmair)
- Enable ppc64le: o crash-patch-gdb.patch: allow applying custom gdb patches o crash-gdb-7.6.series: series file for gdb patches o gdb-7.6-ppc64_sysv_abi_push_float.patch: backported dependency o gdb-7.6-bound_minimal_symbol.patch: dtto o gdb-7.6-add-powerpc64le-linux.patch: dtto o gdb-7.6-update-autoconf-2013-04-24.patch: dtto o gdb-7.6-ppc_insns_match_pattern.patch: dtto o gdb-7.6-floatformat.patch: dtto o gdb-7.6-ppc64-ELFv2-trampoline-match.patch: dtto o gdb-7.6-update-autoconf-2013-06-10.patch: dtto o gdb-7.6-ppc64le.patch: patch used for the gdb package (forwarded request 215044 from ptesarik)
- enable ppc64le (forwarded request 213576 from msmeissn)
Fix removal of /boot/vmlinux-$version if it is not compressed.
- Implementation of 7.0.3 from upstream and patch refresh. - Fix for the ARM architecture if the backtrace unwind information cannot be gathered during session initialization. Without the patch, the two unwind-related warning messages indicating "WARNING: UNWIND: failed to gather unwind_table list" and "WARNING: UNWIND: failed to initialize module unwind tables" are followed by the fatal error message "crash: cannot hash task_struct entries". (anderson@redhat.com) - Fix for the "help -[Dn]" dumpfile information display of the GUID EFI table in the header of SADUMP dumpfiles. Without the patch, only 33 of the 36 bytes in the table are translated. (d.hatayama@jp.fujitsu.com) - Fix for the determination of the kernel NR_CPUS configurable for Linux 3.8 and later kernels that are configured with CONFIG_SLAB. Without the patch, the kernel's compiled-in NR_CPUS value was incorrectly calculated to be the sum of the kernel's NR_CPUS and MAX_NUMNODES configurables. (anderson@redhat.com) - In the next release of makedumpfile, the status field of the dumpfile header of compressed kdumps will show the compression type that was utilized. The "help -[Dn]" output has been updated to display that information. (anderson@redhat.com) - For kernels configured with CONFIG_SLAB in which an array_cache pointer referenced by a kmem_cache structure is invalid, the individual cache(s) will be marked as invalid. During session initialization, the message "crash: kmem_cache: <cache-address>: invalid array_cache pointer" will be displayed, and during runtime, attempts to access the cache(s) will result in a message indicating (forwarded request 207895 from dmair)
Upgrade to crash 7.0.2 (forwarded request 198814 from ptesarik)
Displaying revisions 61 - 80 of 194