Support Notes for Red Hat Enterprise Linux 5.2 for HP Integrity Servers

29. If you have an AD385A 10GbE card in your configuration, ethtool may not always provide
the correct link status. In some situations, ethtool may indicate that the link for this card
is up after it has been taken down. This problem will be fixed in a future release.
30. The lspci -v command may on occasion generate a large amount of output. This may be
worked around by piping the output of the lspci command to the head command with
the desired number of lines of output. Example for 100 lines of output:
# lspci -v | head -n 100
31. The HP Integrity Essentials Foundation Pack for Linux (HPIEFPL) Support Pack does not
currently support servers running Xen kernels for RHEL 5.2. Installation and configuration
of any software packages delivered by the HPIEFPL Support Pack could result in system
downtime due to potential kernel panics. To determine whether a server is running within
a Xen kernel, execute the command uname -r and verify that the kernel string contains
the substring "xen" (such as 2.6.18-8.el5xen).
32. The RHEL 5.2 update includes the support of virtualization on Intel Itanium processor-based
platforms. HP endorses the use of this virtualization technology for those customers interested
in early deployments. HP’s recommended reading for customers seeking to use the
virtualization technology includes Red Hat’s RHEL 5.2 documentation (release notes,
installation and virtualization guides). These documents will cover feature updates, known
issues, minimum and maximum configuration limits for RHEL 5.2 virtualization on HP
Integrity servers.
Red Hat’s RHEL 5.2 documentation can be found at:
http://www.redhat.com/docs/manuals/enterprise/
33. If you have an AD385A 10GbE card in your configuration, ethtool may not always provide
the correct link status. In some situations, ethtool may indicate that the link for this card
is up after it has been taken down. This problem will be fixed in a future release.
34. When Linux boots on an mid-range/high-end (cellular) IA-64 machine with discontiguous
memory, a cell may end up in a state where it has too little contiguous memory available,
and could cause an MCA.
If you experience this issue, try one of the following methods to resolve the problem:
a. Try changing the memory configuration so that the memory in each cell is equal.
b. Try changing the CLM (Cell Local Memory) setting to increase the size of contiguous
memory.
If the system was working previously, try the pdt command at the EFI prompt. If there are
PDT entries, consider replacing the bad memory.
Known Issues 11