Bug 1472473 - kernel: no 4.11 kernel boots
kernel: no 4.11 kernel boots
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-18 16:29 EDT by David Anderson
Modified: 2017-08-05 13:59 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Anderson 2017-07-18 16:29:40 EDT
Description of problem:

After choosing the kernel to boot in GRUB, if it is later than 4.10, then after showing the message "EFI stub: UEFI secure boot is enabled", the computer freezes. No further activity takes place, and it is unresponsive to key-presses.

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

Any later than 4.10. For example, the current latest 4.11.10-200.fc25

How reproducible:

Every time

Steps to Reproduce:
1. Boot into 4.11.x kernel

Actual results: Freezes
Expected results: Boots

Additional info:

The CPU model name in /proc/cpuinfo is "Intel (R) Pentium(R) CPU N3540 @ 1.26GHz", with cpu family 6, model 55. The machine is an Asus Laptop, model number E402M.

I waited for a while before reporting it (there have been a few 4.11 kernels) in case it got fixed in the mean-time. But it's been some weeks now, so I am reporting it.
Comment 1 David Anderson 2017-08-05 13:59:56 EDT
I upgraded the machine to Fedora 26. Attempting to boot with the Fedora 26 kernel, it gets further into the boot process (if I remove 'rhgb' and 'quiet' from the kernel command line, then lots of things scroll past), but it still locks up during the boot process. The Fedora 25 kernel allows it to boot into userspace.

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