Red Hat ENTERPRISE LINUX 5.5 - S 2010, Manual

Page: 41 / 470

crash
31
An updated cpuspeed package that fixes some initscript exit statuses, avoids loading on problematic
CPUs, and starts only after syslogd is now available.
The cpuspeed package configures CPU frequency scaling.
This update fixes the following bugs:
* some exit status codes from the initscript were not in line with LSB standards. The codes were
updated, and are now compliant. (
BZ#495049
215
)
* where Intel Xeon Processor 7100 series processors were used with Hyper-Threading Technology
enabled, cpuspeed loading could create system deadlocks. The cpuspeed settings were changed and
system deadlocks no longer occur on this hardware. (
BZ#449004
216
)
* the cpuspeed initscript uses syslog to log important information about its status. However, cpuspeed
was being started before syslog on boot, and log messages generated by the cpuspeed init script
were not being captured. The cpuspeed init script now runs after the syslog init script, and all log
messages are now being recorded. (
BZ#516224
217
)
Users should upgrade to this updated package, which resolves these issues.
1.27. crash
1.27.1. RHBA-2010:0230: bug fix update
Updated crash packages that fix various bugs and add enhancements are now available.
The crash package is a core analysis suite. It is a self-contained tool that can be used to investigate
either live systems, kernel core dumps created from the netdump, diskdump, and kdump packages
from Red Hat Linux, the mcore kernel patch offered by Mission Critical Linux, or the LKCD kernel
patch.
* if a kdump NMI was issued and the task kernel stack was changed, the backtrace would in some
cases fail and produce an error: "bt: cannot transition from exception stack to current process
stack". The crash package was updated to report task inconsistencies and change the active task as
appropriate. Additionally, a new set -a option was added to manually set tasks to be the active task on
its CPU. (
BZ#504952
218
)
* if the kernel data structures in a non-matching vmlinux varied widely enough from the kernel
that generated the vmcore, erroneous data could be read and consumed. Several new defensive
mechanisms have been added and it now fails in a more reasonable manner. (
BZ#508156
219
)
* running the bt -a command against a Xen hypervisor resulted in a "cannot resolve stack trace"
warning message if the CPU received its shutdown NMI while running in an interrupt handler. The bt
command was changed and the error no longer occurs. (
BZ#510505
220
)
* added support for dumpfile format of virsh dump of KVM kernels. (
BZ#510519
221
)
215
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=495049
216
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=449004
217
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=516224
218
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=504952
219
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=508156
220
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=510505
221
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=510519