Release Notes

ACPI displays warning message when system IO range
conflicts
Description: The Advanced Configuration and Power Interface (ACPI) displays a warning message, if there is a conflict
between the system input/output (IO) and operation address range (OpRange).
Applies to: Red Hat Enterprise Linux 7.2
Cause: The latest kernel in Red Hat Enterprise Linux 7.2 with ACPI_check_resource_conflict() checks
for the entire address range for a particular device. In the watchdog timer and General-purpose input/
output (GPIO), the memory address that is mapped by system IO and OpRange is accessed by both ACPI
and the operating system.
Workaround: This error message can be ignored because there is no functionality loss.
DWS login fails in Red Hat Enterprise Linux 7.2
Description: In OpenManage Server Administrator (OMSA), the distributed web server (DWS) login fails when it tries
to log in from another server.
Applies to: Red Hat Enterprise Linux 7.2
Cause: OMSA uses openwsman for web service and sfcb as cim broker, that are connected by using the local
socket. SELinux policy does not allow sfcb to write to this socket.
Workaround: Add SELinux policy for sfcb to access the local socket.
Red Hat Enterprise Linux 7.2 displays a warning
message in dmesg logs
Description:
In Red Hat Enterprise Linux 7.2, the system displays a warning message in dmesg logs: Your BIOS is
broken and requested that x2apic be disabled.
Applies to: Red Hat Enterprise Linux 7.2
Cause: By default x2apic is not enabled in BIOS.
Workaround: This issue can be ignored because there is no functionality loss. Enable x2apic in BIOS.
Invalid naming conventions for the Intel X710 card
when NPAR or NPAR-EP is enabled
Description:
Red Hat Enterprise Linux 7 with Intel X710 card naming conventions by biosdevname may not be
accurate for all the networking devices.
Applies to: Red Hat Enterprise Linux 7.2
Cause: Biosdevname reads the vital product data (VPD) information from the network adapter parallely, and
leads to incorrect interface naming because the VPD does not read the card names accurately.
Workaround: Add kernel boot parameter biosdevname=0, which makes the system to revert back to systemd naming
convention.
36 Known issues