Bug 1534711 - Fail to boot. Hangs. kernel 4.14.13-200
Summary: Fail to boot. Hangs. kernel 4.14.13-200
Keywords:
Status: CLOSED DUPLICATE of bug 1534031
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-15 19:06 UTC by Norman Goldstein
Modified: 2018-01-15 22:56 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1534031
Environment:
Last Closed: 2018-01-15 22:56:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Norman Goldstein 2018-01-15 19:06:52 UTC
+++ This bug was initially created as a clone of Bug #1534031 +++

Description of problem:
Unable to boot into kernel 4.14.13-200 .

Version-Release number of selected component (if applicable):
4.14.13-200

How reproducible:
Always

Steps to Reproduce:
1.Boot
2.Choose 4.14.13-200
3.

Actual results:
The final message is "Starting Window Manager"
This screen remains, and the boot does not progress.

Expected results:
Boot into graphical interface.

Additional info:
Work around by booting into 4.14.8-200

--- Additional comment from Laura Abbott on 2018-01-12 16:12:04 EST ---

Does it boot if you add nopti to the kernel command line?

--- Additional comment from Norman Goldstein on 2018-01-13 02:25:12 EST ---

(In reply to Laura Abbott from comment #1)
> Does it boot if you add nopti to the kernel command line?

I put   nopti   at the very end of the linux boot command, and hit Ctl-X  to complete the boot. The boot still hangs at the same place.

Comment 1 Dale Burr 2018-01-15 22:24:37 UTC
I am seeing similar issue on Fedora 27. The only difference is that the screen starts flashing (same messages, though). I am unable to do anything at this point except ctl-alt-del. It does recognize the key combo and reboots the machine. As in original info, booting to 4.14.8 works. (4.14.11 and 4.14.13 fail)

Comment 2 Laura Abbott 2018-01-15 22:56:49 UTC
Let's stick to a single bug for now.

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


Note You need to log in before you can comment on or make changes to this bug.