Bug 1119938 - Exit from Grub2 back to Firmware causes system to hang on Fedora 20
Summary: Exit from Grub2 back to Firmware causes system to hang on Fedora 20
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-15 22:06 UTC by aaron.pop
Modified: 2014-12-29 15:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-29 15:46:08 UTC


Attachments (Terms of Use)

Description aaron.pop 2014-07-15 22:06:07 UTC
Description of problem:

Patch 0447-Add-support-for-crappy-cd-craparino.patch is overwriting the UEFI systems device path instead of creating its own duplicate of the device path and modifying the duplicate.

Version-Release number of selected component (if applicable):
grub2-2.00-26.fc20.src.rpm
grub2-2.00-25.fc20.src.rpm

How reproducible:
Depending on the UEFI firmware, the modification of the device path can prevent the system from booting to the next UEFI boot device by causing a system hang.

Steps to Reproduce:
1. Using the Fedora 20 DVD, UEFI boot to the installation media (secure boot disabled)
2. Press the 'c' key when the grub menu is shown
3. type 'exit' into the command prompt 
4. The system can hang after control is returned back to the firmware

Actual results:
The modification of the device path causes the system to have duplicate device paths for two separate device handles (UEFI specification says that device paths should be unique)

Expected results:
Booting to the installation media and then exiting should not cause any modifications to the firmware provided device paths.

Additional info:
This does not exist in the grub2-2.02-0.6.fc21.src.rpm that is part of rawhide and fedora 21

Comment 1 aaron.pop 2014-12-29 15:46:08 UTC
Because the latest versions of grub operate on a duplicated device path, and do not have the same problem, I am closing this.


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