Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStephen Steward
2020-05-02 20:07:51 UTC
Description of problem:
After upgrade to RHEL 8.2 (from 8.1), the system hangs at "Starting Switch Root". Previously, whenever a new kernel update was available, I would need to follow the official instructions located at https://access.redhat.com/solutions/4134381 to install the proprietary NVIDIA graphics driver for my system; I am using a NVIDIA GeForce 2070 Super graphics card. This only needed to be done once per kernel update; after following the instructions, the kernel would boot into graphical.target with no further issues.
After updating to 8.2, these instructions have to be completed every time the computer loses power: either after shutdown and boot, reboot, or wake from sleep mode. I believe that somehow the NVIDIA driver is corrupting the initramfs somehow, but it was never a problem before 8.2. On reboot or boot from shutdown, I'll get the "Starting Switch Root" error, and the computer will not boot until forcefully shut down, booting into multi-user.target by appending "systemd.unit=multi-user.target" to the kernel parameters and following the instructions above; on wake from sleep, I'll get a blank screen and must shutdown forcefully and follow the steps above from multi-user.target.
Version-Release number of selected component (if applicable):
RHEL 8.2 on newest kernel 4.18.0-193.el8
NVIDIA graphics driver 440.82
Latest RHEL version of dracut
How reproducible:
After upgrade to 8.2, always.
Before 8.2, only on initial upgrade to new Red Hat issued kernel
Steps to Reproduce:
1. Remove power from computer (reboot, shutdown/boot, or wake from sleep)
2. Attempt to boot into RHEL 8.2 with graphical.target set as systemd default
3. Watch systemd output hang at "starting switch root" with no further progress; computer must be forcefully shutdown, booted into multi-user.target, and following official Red Hat NVIDIA driver installation instructions
Actual results:
Boot progress halts at "starting switch root", possibly due to a corrupted initramfs due to NVIDIA driver issues. While not a persistent problem before, it is now a persistent problem that must be addressed every boot.
Expected results:
System should boot into GNOME Shell using graphical.target without issues
Additional info:
Before 8.2, NVIDIA driver would install correctly without having KVM enabled in UEFI/BIOS. Upon upgrade to 8.2, the only way to correctly get NVIDIA driver installed was to enable KVM and allow NVIDIA driver to install a DKMS module.
Comment 3RHEL Program Management
2021-11-02 07:27:01 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.