Bug 2296143

Summary: Fedora 40: systemd-vconsole-setup.service fails to lock /dev/console at boot
Product: [Fedora] Fedora Reporter: Don <darling.don>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 40CC: daan.j.demeyer, dtardon, fedoraproject, lnykryn, msekleta, ryncsn, suraj.ghimire7, systemd-maint, yuwatana, zbyszek
Target Milestone: ---Keywords: Desktop, Regression, Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-08 12:29:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Don 2024-07-06 23:39:27 UTC 
After upgrading to Fedora 40, I consistently encounter the following error message during boot:

systemd-vconsole-setup[####]: Failed to lock /dev/console: Input/output error

This results in the service failing to start.  The system eventually boots into the graphical environment.


Reproducible: Always

Steps to Reproduce:
Boot Fedora 40.
Observe the new error message on the text console, or in the boot logs or system journal (journalctl -xe).
Actual Results:  
The systemd-vconsole-setup.service fails to start.

Expected Results:  
The systemd-vconsole-setup.service should start successfully, configuring the virtual consoles (TTYs) and allowing access to the console from the start of the boot process.

Hardware: ASUS PRIME X570-PRO motherboard, AMD Ryzen 9 5950X CPU, NVIDIA GeForce RTX 3080 GPU (proprietary drivers).

Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.9.7-200.fc40.x86_64 root=UUID=[xxx] ro rootflags=subvol=root rd.luks.uuid=luks-[xxx] console=tty1 console=ttyS0,115200
Comment 1 David Tardon 2024-07-08 12:29:02 UTC 

*** This bug has been marked as a duplicate of bug 2273069 ***