Bug 1534031
| Summary: | Fail to boot. Hangs. kernel 4.14.11-200 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Norman Goldstein <normvcr> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | airlied, ajax, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, normvcr, porcupie, steved | ||||
| Target Milestone: | --- | ||||||
| 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: | |||||||
| : | 1534711 (view as bug list) | Environment: | |||||
| Last Closed: | 2018-02-28 03:33:26 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Does it boot if you add nopti to the kernel command line? (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. *** Bug 1534711 has been marked as a duplicate of this bug. *** Yay a boot problem that isn't caused by the PTI patches. Do you see anything on the screen if you remove quiet from the kernel command line? Can you also share lspci, specifically I want to know the graphics card information. You clearly sees the glass as half full. Removed quiet from the boot line. Still hangs at the flashing screen, whose last message is for having successfully started the window manager. ============== lspci ============================================= 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) Problem persists with 4.14.16-200 . The last two messages on the blinking screen are: OK Started Gnome Display Manager OK Created slice User Slice of root Did clean install of F27 + update, and things are good. 4.14.16-300.fc27.x86_64 Using nouveau driver. Thanks for letting us know. |
Created attachment 1380527 [details] The last boot is into 4.14.8-200 (successful). The previous boot is a failed boot. Description of problem: Unable to boot into kernel 4.14.11-200 . Version-Release number of selected component (if applicable): 4.14.11-200 How reproducible: Always Steps to Reproduce: 1.Boot 2.Choose 4.14.11-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