Release Notes

Table Of Contents
RHEL 8.3 installer does not automatically locate
the source installation repository when only
inst.stage2=hd boot option is used
Description: When both stage2 and the installation repository are on the same internal drive or external drive (USB
hard drive), RHEL 8.3 installer does not automatically locate the source installation repository when only
inst.stage2=hd boot option is used.
Applies to: Red Hat Enterprise Linux 8.3
Workaround: Modify the boot option inst.stage2=hd:LABEL=<NAME> to inst.repo=hd:LABEL=<NAME>
Systems
affected:
Dell EMC PowerEdge yx4x and yx5x servers
Tracking number: 182181
The output of the systemctl status command displays
the status as thawing
Description: The output of the systemctl status <service name> command displays the status Active:
active (running) (thawing) instead of Active: active (running) when a service is
reloaded. This issue is a cosmetic issue and can be ignored.
Applies to: Red Hat Enterprise Linux 8.3
Systems
affected:
Dell EMC PowerEdge yx4x and yx5x servers
Tracking number: 178127
Advanced Configuration and Power Interface (ACPI)
error messages displayed in dmesg
Description:
The following ACPI-related error messages are displayed in dmesg and /var/log/messages:
[ 10.265354] ACPI Error: No handler for Region [SYSI]
(ffff8f04edb31a20) [IPMI] (20130517/evregion-162)
[ 10.265359] ACPI Error: Region IPMI (ID=7) has no handler (20130517/
exfldio-305)
[ 10.265368] ACPI Error: Method parse/execution failed
[\_SB_.PMI0._GHL] (Node ffff8f106dea07e0), AE_NOT_EXIST (20130517/
psparse-536)
[ 10.265376] ACPI Error: Method parse/execution failed
[\_SB_.PMI0._PMC] (Node ffff8f106dea0720), AE_NOT_EXIST (20130517/
psparse-536)
[ 10.265381] ACPI Exception: AE_NOT_EXIST, Evaluating _PMC (20130517/
power_meter-753)
The error messages are related to the module dependency and module load order of the
acpi_power_meter and acpi_ipmi drivers.
Applies to: Red Hat Enterprise Linux 8 and later
Solution: The messages are informational and can be ignored. For more information, see Red Hat Enterprise Linux
Knowledge Base article 49225
Tracking number: 172165
24 Known issues