Show Table of Contents
8. Resolved Issues
8.1. All Architectures
- Netapp devices can now complete failback (after a previously-failed path is restored) within a reasonable time with the default
dm-multipathconfiguration. system-config-kickstartnow supports package selection through the Red Hat Network plugin.kudzucan now properly parseifcfg-*files that contain quotes around theHWADDRorSUBCHANNELSparameters. In addition, if a device'sHWADDRis not specified,kudzuno longer modifies network configurations when the device is changed.- Running
netstatwith the-A inetor-A inet6option (on a system wheresctpwas not added to the kernel) no longer terminates abnormally. Note, however, thatnetstatwill display the following warning message when invoked with the-soption:netstat: no support for `AF INET (sctp)' on this system.
- The
nohideexport option is no longer required on referral exports (i.e. exports that specify a referral server). For more information on bound mounts, refer toman 5 exports. - The priority callouts of
dm-multipathare now statically compiled and copied onto the memory ofmultipathd. As such,multipathdno longer requires access to the root file system in order to execute priority callouts.This fixes a problem that occurred when runningdm-multipathon devices containing the root file system, which caused such devices to freeze during fibre-channel path faults. partedcan now understand and correctly print out Xen Virtual Device (XVD) partition labels. This allows paravirtualized guests to use thepartedutility. It is no longer necessary to runpartedwithindom0to configure disk partitions on paravirtualized guests.- When upgrading to Red Hat Enterprise Linux 5.2 via Red Hat Network, you no longer need to manually import the redhat-beta key prior to upgrading.
- Systems using the AMD 8132 or HT 1000 chipsets no longer need the
pci=nommconfkernel parameter.Note that the system will still restrict such bridges to using the PortIO CF8/CFC mechanism. However, bridges (including those on the same platform) that respond correctly toMMCONFIGcycles will useMMCONFIG, provided that the platform's BIOS correctly supportsMMCONFIG.However, if you are installing Red Hat Enterprise Linux 5.2 on an HP DC7800, the kernel parameter,pci=nommconf, is still needed. This is because the HP DC7800 is not yet included in theMMCONFblacklist. - Previous versions of Red Hat Enterprise Linux 5 on HP BL860c blade systems could hang during the IP information request stage of installation. When this occurred, you were required to reboot and perform the installation with Ethernet autonegotiation disabled.Red Hat Enterprise Linux 5.2 includes a fix for this issue.
- Gemalto 64K smart cards now use Chip/Smart Card Interface Devices-compliant (CCID-compliant) readers. Previously, this smart card used the built-in e-gate reader, which essentially meant that the card and reader were being inserted at the same time. As a result,
coolkeydid not consistently recognize Gemalto 64K smart cards.With this update,coolkeynow works correctly with Gemalto 64k smart cards.
8.2. x86-64 Architectures
- Systems equipped with Intel graphics cards that have the
XD(execute disable) option disabled no longer crash upon exiting an X session. - Using the
divider=command-line argument now works properly on this architecture. - The Calgary IOMMU chip is now supported by default. As such, the kernel command line option
iommu=calgaryto enable support for this chip is no longer necessary.
8.3. ia64 Architecture
- Kernel modules such as
e1000andqla2xxxcan now be unloaded while running the virtualized kernel. As such, you no longer need to reboot the system after installing third-party drivers. - The X server no longer attempts to utilize memory regions incompatible to its needs. This fixes a bug that previously caused a Machine Check Abort (MCA) on some Itanium systems.
- A machine check error (which previously resulted in a
dom0reboot) no longer occurs when you attempt to run the virtualized kernel on systems that use the P600 SmartArray controller.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.