Created attachment 1429820 [details]
dmesg from boot with kernel 4.16.3-200.fc27.x86_64 which works. Can't supply dmesg or anything from failed boots because of the problem manifests too early
Description of problem: After power up, goes through boot menu, but never comes to passphrase entry for encrypted volume.
Version-Release number of selected component (if applicable): 4.16.5-200.fc27.x86_64, 4.16.4-200.fc27.x86_64
How reproducible: Always on my system, it is enough just to power up and watch the screen.
Steps to Reproduce:
1. Power on the notebook
2. Watch the screen, after going through boot menu it never comes to passphrase entry for encrypted volume
Actual results: Black screen
Expected results: Should boot normally like with kernel 4.16.3-200.fc27.x86_64
Additional info: My T440s has ATI graphics. The disk layout is de facto standard, sda1 - /boot, sda2 - PV with encryption and / and everything in LVM
Errata: There is no ATI graphic on that T440s, it has Intel graphics.
4.16.3-200.fc27.x86_64 from updates-testing exhibits the same problem
Please fix this soon, I would like to update one of T400s notebooks which is designate to receive early releases and updates to F28 as soon as possible, but I am worrying to do so while experiencing the described problem.
Update: The hanged boot can be tricked to complete by pressing some strange key combinations or sequences, like <Alt><Alt><Enter> or <Ctrl>+<Alt>+<Enter>.
Not sure if there is any key sequence/combo always working on the first attempt. This works with 4.16.6-200.fc27.x86_64, 4.16.5-200.fc27.x86_64, not tested with uninstalled 4.16.4-200.fc27.x86_64.
I have also tried to enable the TPM module which i normally have in the visible, but not active state, e.g. may be said non-standard setting. Changing TPM to active in BIOS did not fix the problem.
When in hanged state, reaction to <Ctrl>+<Alt>+<Del> is "reboot: Restarting system" followed by immediate reboot.
This sounds like it may be https://bugzilla.redhat.com/show_bug.cgi?id=1572944. Can you try 4.16.6-202? It's on its way to updates-testing, but you can download it from koji as well. Thanks!
thanks for pointing me in the 4.16.6-202 direction, this version does not exhibit the problem.
Perfect, thanks for confirming!
*** This bug has been marked as a duplicate of bug 1572944 ***