Release Notes
Table Of Contents
- Dell EMC PowerEdge Systems Running Red Hat Enterprise Linux 8 Release Notes
- Contents
- Release summary
- Compatibility
- New and enhanced in RHEL 8 release
- Important notes
- Fixes
- 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
- Operating system crashes on systems 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
for PCIe Gen 4 NVMe slots - NetworkManager may restart unexpectedly when creating greater than 256 VLAN devices configured with DHCP IP
- FCoE session is not reestablished after MX9116N switch is rebooted
- Dmesg shows drm related call trace in RHEL 8.3
- 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
- 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
- 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
- RHEL 8 does not discover FCoE LUNs connected over Broadcom BCM57XXX NICs
- 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
Workaround:
NOTE: The output of each command varies based on your system configuration.
Follow the steps:
1. Identify the parent device to which the NVMe device is connected using the following command:
lspci -t
-+-[0000:e0]-+-00.0
| +-00.2
| +-01.0
| +-02.0
| +-03.0
| +-03.1-[e2]----00.0
From the above snippet, the device e2:00.0 is the NVMe device and the device e0:03.1 is the
parent device. The parent device is used for the steps that are described subsequently.
2. Read the Slot Status Register in the PCI Express Capability structure by running the following
command:
setpci -s e0:03.1 CAP_EXP+0x1a.w
Output: 0148 (value returned)
3. Clear the event bits that are impacted by running the following command:
setpci -s e0:03.1 CAP_EXP+0x1a.w=0x0108
4. Re-read the Slot Status Register to confirm that event bits are cleared by running the following
command:
setpci -s e0:03.1 CAP_EXP+0x1a.w
Output: 0040 (value returned)
5. Unplug the drive and then plug-in the drive after clearing the event bits.
Solution
The issue is resolved in Red Hat Enterprise Linux 8.2 z-stream kernel version
kernel-4.18.0-193.13.2.el8_2.x86_64 and later
Systems
affected:
PowerEdge R6515, PowerEdge R7515, PowerEdge R6525, PowerEdge C6525, and PowerEdge R7525
Tracking number: 155501, 155503
Operating system enters the dracut shell during boot
Description:
When Red Hat Enterprise Linux 8.1 is installed on PowerEdge RAID Controller (PERC) virtual disk (VD)
and the system is rebooted, during this boot process the system enters the dracut shell with the following
error message:
scsi_alloc_sdev: Allocation failure during SCSI scanning
Applies to: Red Hat Enterprise Linux 8.1
Cause: The SCSI disk discovery failure is due to an issue in the block device allocation code.
Solution: Update the kernel to 4.18.0-147.5.1.el8_1.x86_64 version or later.
Systems
affected:
All Dell EMC PowerEdge servers
Tracking number: 160374
Fixes 13