Red Hat ENTERPRISE LINUX 5.3 - RELEASE MANIFEST, Руководство по выпуску

Страница: 44 / 240

Release Notes
44
This is caused by the cleanup code, which waits until the path checker request either completes or
fails. To display the current
multipath
state without hanging the command, use
multipath -l
instead.
• Upgrading
pm-utils
from a Red Hat Enterprise Linux 5.2 Beta version of
pm-utils
will fail,
resulting in the following error:
error: unpacking of archive failed on file /etc/pm/sleep.d: cpio: rename
To prevent this from occurring, delete the
/etc/pm/sleep.d/
directory prior to upgrading. If
/
etc/pm/sleep.d
contains any files, move those files to
/etc/pm/hooks/
.
• Hardware testing for the
Mellanox MT25204
has revealed that an internal error occurs under certain
high-load conditions. When the
ib_mthca
driver reports a catastrophic error on this hardware, it is
usually related to an insufficient completion queue depth relative to the number of outstanding work
requests generated by the user application.
Although the driver will reset the hardware and recover from such an event, all existing connections
at the time of the error will be lost. This generally results in a segmentation fault in the user
application. Further, if
opensm
is running at the time the error occurs, then you need to manually
restart it in order to resume proper operation.
• When installing Red Hat Enterprise Linux 5 on a guest, the guest is configured to explicitly use a
temporary installation kernel provided by
dom0
. Once installation finishes, it can then use its own
bootloader. However, this can only be achieved by forcing the guest's first reboot to be a shutdown.
As such, when the
Reboot
button appears at the end of the guest installation, clicking it shuts down
the guest, but does not reboot it. This is an expected behavior.
Note that when you boot the guest after this it will then use its own bootloader.
• Running
rpmbuild
on the
compiz
source RPM will fail if any KDE or
qt
development packages
(for example,
qt-devel
) are installed. This is caused by a bug in the
compiz
configuration script.
To work around this, remove any KDE or
qt
development packages before attempting to build the
compiz
package from its source RPM.
• If your system has either
ATI Radeon R500
or
R600
graphics card equipped,
firstboot
will not
run after installation. The system will go directly to the graphical login screen and skip
firstboot
altogether. If you attempt to run
firstboot
manually (i.e. from a failsafe terminal), the X session
will crash.
This issue is caused by the driver used by the
ATI Radeon R500/R600
hardware. The default driver
used by these graphics cards are still in technology preview. To work around this, backup your
/
etc/X11/xorg.conf
file; then, configure X to use the supported
vesa
driver instead using the
following command:
system-config-display --reconfig --set-driver=vesa
You can now run
firstboot
. To switch back to your old settings, restore your original
/etc/X11/
xorg.conf
.