- Not specifying the
-Noption when setting retransmission intervals of IPMI messages over the LAN or LANplus interface may cause various error messages to be returned. For example:
ipmitool -I lanplus -H $HOST -U root -P $PASS sensor listUnable to renew SDR reservation Close Session command failed: Reservation cancelled or invalid ~]#
ipmitool -I lanplus -H $HOST -U root -P $PASS delloem powermonitorError getting power management information, return code c1 Close Session command failed: Invalid command
- The ipmitool may crash in certain cases. For example, when an incorrect password is used, a segmentation fault occurs:
ipmitool -I lanplus -H $HOST -U root -P wrongpass delloem powermonitorError: Unable to establish IPMI v2 / RMCP+ session Segmentation fault (core dumped)
- Unloading the
be2netdriver with a Virtual Function (VF) attached to a virtual guest results in kernel panic.
- The Brocade BFA Fibre Channel and FCoE driver does not currently support dynamic recognition of Logical Unit addition or removal using the sg3_utils utilities (for example, the
sg_scancommand) or similar functionality. Please consult Brocade directly for a Brocade equivalent of this functionality.
- iSCSI and FCoE boot support on Broadcom devices is not included in Red Hat Enterprise Linux 6.3. These two features, which are provided by the
bnx2fcBroadcom drivers, remain a Technology Preview until further notice.
- Starting with Red Hat Enterprise Linux 6.0 and later, kexec kdump supports dumping core to the Brtfs file system. However, note that because the findfs utility in busybox does not support Btrfs yet,
UUID/LABELresolving is not functional. Avoid using the
UUID/LABELsyntax when dumping core to Btrfs file systems.
- When running kdump in a busybox environment and dumping to a Btrfs file system, you may receive the following error message:
/etc/kdump.conf: Unsupported type btrfsHowever, Btrfs is supported as a kdump target. To work around this issue, install the btrfs-progs package, verify that the
/sbin/btrfsckfile exists, and retry.
trace-cmdservice does start on 64-bit PowerPC and IBM System z systems because the
sys_exitevents do not get enabled on the aforementioned systems.
- trace-cmd's subcommand,
report, does not work on IBM System z systems. This is due to the fact that the
CONFIG_FTRACE_SYSCALLSparameter is not set on IBM System z systems.
- Red Hat Enterprise Linux 6.1 and later enter processor power-saving states more aggressively. This may result in a small performance penalty on certain workloads. This functionality may be disabled at boot time by passing the
intel_idle.max_cstate=0parameter, or at run time by using the cpu_dma_latency pm_qos interface.
- Red Hat Enterprise Linux 6 only has support for the first revision of the UPEK Touchstrip fingerprint reader (USB ID 147e:2016). Attempting to use a second revision device may cause the fingerprint reader daemon to crash. The following command returns the version of the device being used in an individual machine:
lsusb -v -d 147e:2016 | grep bcdDevice
- The Emulex Fibre Channel/Fibre Channel-over-Ethernet (FCoE) driver in Red Hat Enterprise Linux 6 does not support DH-CHAP authentication. DH-CHAP authentication provides secure access between hosts and mass storage in Fibre-Channel and FCoE SANs in compliance with the FC-SP specification. Note, however that the Emulex driver (
lpfc) does support DH-CHAP authentication on Red Hat Enterprise Linux 5, from version 5.4. Future Red Hat Enterprise Linux 6 releases may include DH-CHAP authentication.
- The recommended minimum HBA firmware revision for use with the
mpt2sasdriver is "Phase 5 firmware" (that is, with version number in the form
05.xx.xx.xx). Note that following this recommendation is especially important on complex SAS configurations involving multiple SAS expanders.