Bug 1390719 - Non PAE Kernel 4.7.9-200 will not start from Grub [NEEDINFO]
Summary: Non PAE Kernel 4.7.9-200 will not start from Grub
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: i686
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: 2016-11-01 18:04 UTC by Frank OLaughlin
Modified: 2017-04-28 17:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:27:25 UTC
Type: Bug
jforbes: needinfo?


Attachments (Terms of Use)

Description Frank OLaughlin 2016-11-01 18:04:13 UTC
Description of problem:
Kernel-4.7.9-200.fc24 and above will not start from Grub. The computer is a IBM T41 using a Pentium M processor which needs to run the non PAE version. Kernel-4.7.7-200.fc24 and all previous versions work ok.

Version-Release number of selected component (if applicable):
Kernel-4.7.9-200.fc24 i686

How reproducible:
Does not start from Grub each time. My second identical computer behaves exactly the same

Steps to Reproduce:
1.install Kernel-4.7.9-200.fc24 from repository
2.restart computer
3.Attempt to start the Kernel from Grub

Actual results:


Expected results:


Additional info:

Comment 1 Justin M. Forbes 2017-04-11 15:02:34 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  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 have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2017-04-28 17:27:25 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. 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.


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