- Notes, cautions, and warnings
- Release summary
- Compatibility
- New and enhanced in RHEL 8 release
- Important notes
- Fixes
- The system hangs, and a kernel soft lockup error is observed when OMSA is installed
- I/O related errors are observed in dmesg
- RHEL 8.8 and RHEL 9.2 failed to boot
- Unattended operating system installation fails in RHEL using server configuration profile method
- RHEL 8.6 drops into maintenance mode while booting
- RHEL 8.6 fails to boot when UEFI secure boot is enabled BIOS
- Lspci utility lists HBA350i MM/ HBA350i MM LP as generic SAS devices
- RHEL 8.5 boot fails with Intel Corporation Ethernet Controller E810
- NetworkManager may restart unexpectedly when creating greater than 256 VLAN devices configured with DHCP IP
- RHEL 8.3 installer does not automatically locate the source installation repository when only inst.stage2=hd boot option is used
- The output of the systemctl status command displays the status as thawing
- RHEL 8 does not discover FCoE LUNs connected over Broadcom BCM57XXX NICs
- System may drop into emergency mode during boot process
- The version field in the output of the modinfo command for certain networking drivers is null
- System hangs when Intel tboot is used to boot the operating system
- BIOS update does not complete when an update is performed using the Linux .BIN files
- Dmesg shows drm related call trace in RHEL 8.3
- Operating system crashes on servers with NVIDIA GPGPUs
- Dmesg and /var/log/messages display AMD-Vi related messages
- The status of the NetworkManager service may be inactive when RHEL 8.3 is rebooted
- Operating system crashes on AMD Rome CPU-based systems and with Intel E810 NIC
- The lvcreate command requests a response from the user when -wipesignature -yes parameters are passed
- The mdmonitor service displays an error during operating system installation
- The dmidecode utility displays the slot type as <OUT OF SPEC> for PCIe Gen 4 NVMe slots
- The mcelog utility logs only decoding architectural errors message in var/log/messages
- Disk drives part of MD RAID are not listed as installation destination by the installer
- Dell EMC OpenManage Storage Services utility fails to reconfigure the virtual disk
- Guest VMs with SRIOV VFs assigned take a long time to power on, and libvirt related errors are observed
- Dmesg displays Integrity Measurement Architecture (IMA) driver related-messages during system boot
- After every reboot, the network interface name changes
- Red Hat Enterprise Linux Version 8 installation wizard creates a duplicate bonding interface
- Servers with the AMD Rome processor display a CCP initialization failure message in dmesg
- PowerEdge servers with the AMD Rome processor fail to detect an NVMe drive after multiple hot plugs
- Operating system enters the dracut shell during boot
- System crashes when rebooted with SR-IOV-enabled QLogic cards
- After system reboot, Disk data format (DDF) devices are not listed in /proc/mdstat
- Updating NVMe firmware using the nvme-cli utility displays an error in dmesg
- Fatal error BDF 02:00.0 is detected with BCM574xx NICs
- NVMe devices are not detected after hot-plugging
- Linux operating system fails to detect the Intel x710 card
- Dmidecode displays OUT OF SPEC in Slot Type and Slot Length of SMBIOS system slots
- Custom partitioning fails with FC LUN
- When booting the system from iSCSI with Mellanox CX-4 and CX-5 adapters, the system reports csum failure message
- Red Hat Enterprise Linux 8 kernel panic is observed due to fatal hardware error
- Known issues
- The dmesg displays qat related messages
- Booting into operating system fails on systems with TPM 1.2 chips
- The anaconda installer crashes while autoconfiguring disk partitions
- FCoE session is not reestablished after MX9116N switch is rebooted
- Dmesg displays error messages when NVMe device is surprise removed
- Status of the RAID 0 logical volume is displayed as Available when one of the members of the RAID array is surprise removed
- /proc/mdstat and mdadm -D commands display incorrect statuses when two NVMe devices are surprise removed from a RAID 5 MD array
- Dell Controlled Turbo feature is not functional
- Caps Lock key-press is not registered on the Dell PowerEdge iDRAC virtual console
- Advanced Configuration and Power Interface (ACPI) error messages displayed in dmesg
- Drivers available in OEMDRV drive are not installed during the operating system installation
- The Mellanox IB devices are listed under an incorrect device category on Red Hat Enterprise Linux 8
- The lspci utility is unable to read Vital Product Data (VPD) from QLogic QLE2692 adapter
- Driver dependency mismatch errors reported while installing out-of-box drivers on Red Hat Enterprise Linux 8.x
- Dmesg displays TPM and nvdimm related-messages in Red Hat Enterprise Linux 8.1
- Link Up message is observed when the NVMe device slot is powered off and the device is unplugged
- Mellanox InfiniBand adapters are listed in Bluetooth
- iscsiadm output displays STATIC in the iface.bootproto field when the network interface is configured to DHCP
- When system reboots, system stops responding at the end of the reboot process
- Unable to shut down RHEL 8 when you select Graceful shutdown option or when you press power button on the server
- iSCSI LUN not discovered during RHEL 8 installation
- RHEL 8 installation fails on systems with Emulex OneConnect card
- Switching between runlevels fails
- Limitations
- Resources and support
- Contacting Dell EMC
Dell PowerEdge Systems Red Hat Enterprise Linux 8 Release Notes
Dell Controlled Turbo feature is not functional
- Description
- Dell Controlled Turbo is not functional when the system profile setting in BIOS is set to performance or custom.
- Cause
- The intel_pstate driver may interfere with the processor settings which results in Dell Controlled Turbo feature being not functional.
- Solution
- Prevent the intel_pstate driver from loading. For more information on how to prevent the module from loading, see Red Hat Enterprise Linux Knowledge Base article 41278.
- Applies to
- Red Hat Enterprise Linux 8.0 and later
- Tracking number
- 167802
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\