Bug 1530205 - 4.14 kernels fail to boot
Summary: 4.14 kernels fail to boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-02 09:13 UTC by Paweł Brodacki
Modified: 2019-05-07 11:11 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-23 16:45:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output for successful boot on 4.13.16-302.fc27.x86_64 (72.87 KB, text/plain)
2018-01-02 09:23 UTC, Paweł Brodacki
no flags Details

Description Paweł Brodacki 2018-01-02 09:13:39 UTC
Description of problem:
Physical system fails to boot with 4.14.x kernel version.

Version-Release number of selected component (if applicable):
kernel 4.14.6-300.fc27.x86_64
kernel 4.14.8-300.fc27.x86_64

How reproducible:
On every boot.

Steps to Reproduce:
1. Power off the system.
2. Power on the system, choose affected kernel version to boot.
3. 

Actual results:
System fails to boot. For a moment there's a looped series of messages displayed (copied from a screen photo for 4.14.8-300.fc27.x86_64 boot attempt):
ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKB (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKC (20170728/dspkginit-381)
ACPI Exception: Could not find/resolve named package element: LNKD (20170728/dspkginit-381)
(...)
then the screen gets blank.
Note: Error messages captured for a single boot failure, I did not verify if the same messages are displayed for every failure boot.

Expected results:
System boots correctly.

Additional info:
I observed similar symptoms (screen full of error messages, then a blank screen)  for 4.14.6-300.fc27.x86_64, but I didn't capture the errors. If that would be useful, I can do that.
Kernel 4.13.16-302.fc27.x86_64 boots without issues.

Comment 1 Paweł Brodacki 2018-01-02 09:23:33 UTC
Created attachment 1375555 [details]
dmesg output for successful boot on 4.13.16-302.fc27.x86_64

Comment 2 Laura Abbott 2018-02-20 19:59:29 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Laura Abbott 2018-03-23 16:45:33 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you did actually update, we apologize for the inconvenience (there are a lot of bugs). If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 4 Paweł Brodacki 2019-05-07 11:11:15 UTC
The bug persisted up to and including Fedora 30. I was able to boot live Fedora 30 KDE spin from a DVD drive.
After the installation completed I was not able to boot the system from the hard drive.
However, I could not reproduce the bug on any other hardware. 
Upgrade of the BIOS helped (my mainboard is Gigabyte GA-790XT-USB3) -- I am able to consistently boot the system.
If you are willing to allocate time and effort to investigate, I might be able to flash the old BIOS image and help with investigation.
If you have more urgent things to do than hunting errors in 9-years old BIOS then I'm happy to have the bug closed, as it's probably Gigabyte's fault anyhow.


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