-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.1
-
None
-
No
-
None
-
rhel-display-window-mgmt
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
The plymouth-quit-wait.service boot time more then 5min on RHEL 10
root@bootp-73-114-201:~# systemd-analyze blame
5min 1.167s plymouth-quit-wait.service
2.773s sys-module-fuse.device
2.737s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
2.737s dev-ttyS0.device
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
6.12.0-105.el10.x86_64
plymouth-24.004.60-17.el10.x86_64
How reproducible is this bug?:
100%
Steps to reproduce
- Install RHEL with GUI as VM on VMware's ESXi
- Boot up the RHEL guest
- Check the boot time #systemd-analyze blame
Expected results
The service plymouth-quit-wait.service should not need so long time 5min 1.167s
Actual results
The service plymouth-quit-wait.service use 5min 1.167s
root@bootp-73-114-201:~# systemd-analyze
Startup finished in 730ms (kernel) + 1.807s (initrd) + 5min 4.393s (userspace) = 5min 6.932s
graphical.target reached after 5min 4.376s in userspace.
root@bootp-73-114-201:~# systemd-analyze blame
5min 1.167s plymouth-quit-wait.service
2.773s sys-module-fuse.device
2.737s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
2.737s dev-ttyS0.device
Additional info:
This issue not occur on RHEL 10.0 and 9.7.