Bug 1114775
| Summary: | efibootmgr and kernel fail to write NVRAM change during installation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||||
| Component: | efibootmgr | Assignee: | Peter Jones <pjones> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 22 | CC: | awilliam, collura, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pjones, surya_prabhakar | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-07-19 11:52:48 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: |
|
||||||||||
|
Description
Chris Murphy
2014-06-30 23:48:56 UTC
Created attachment 913594 [details]
dmesg
# efibootmgr -v BootCurrent: 0000 Timeout: 5 seconds show_boot_order(): No such file or directory # ls -l /sys/firmware/efi/efivars total 0 -rw-r--r--. 1 root root 12 Jun 30 18:59 AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e -rw-r--r--. 1 root root 6 Jun 30 18:59 BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 32 Jun 30 18:59 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 54 Jun 30 18:59 ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 8 Jun 30 18:59 epid_provisioned-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 32 Jun 30 18:59 ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 8 Jun 30 18:59 FirmwareFeatures-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 8 Jun 30 18:59 FirmwareFeaturesMask-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 7 Jun 30 18:59 Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 10 Jun 30 18:59 LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 1514 Jun 30 18:59 MemoryConfig-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 924 Jun 30 18:59 MokListRT-605dab50-e046-4300-abb6-3dd810dd8b23 -rw-r--r--. 1 root root 8 Jun 30 18:59 MTC-eb704011-1402-11d3-8e77-00a0c969723b -rw-r--r--. 1 root root 8 Jun 30 18:59 PchInit-e6c2f70a-b604-4877-85ba-deec89e117eb -rw-r--r--. 1 root root 20 Jun 30 18:59 PchS3Peim-e6c2f70a-b604-4877-85ba-deec89e117eb -rw-r--r--. 1 root root 692 Jun 30 18:59 Setup-4dfbbaab-1392-4fde-abb8-c41cc5ad7d5d -rw-r--r--. 1 root root 692 Jun 30 18:59 SetupDefaults-05299c28-3953-4a5f-b7d8-f6c6a7150b2a -rw-r--r--. 1 root root 6 Jun 30 18:59 Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c Do we have a bad build of efibootmgr? Created attachment 913595 [details]
strace efibootmgr
This is reproducing 100% on a MacBookPro8,2 with the latest firmware. I wasn't having NVRAM related problems with this model during previous Fedora testing so this is a regression as far as I can tell. Created attachment 913621 [details]
dmidecode mbp8,2
efibootmgr 0.7.0-3 landed on 2014-06-20 with this interesting changelog: * Thu Jun 19 2014 Peter Jones <pjones> - 0.7.0-3 - Reinstate an accidentally dropped hack to avoid apple brain damage. could you test, maybe, live images from 2014-06-18 and 2014-06-20 (or as close as you can get and still find images that don't have other showstopper bugs) and see if 06-18 works and 06-20 doesn't? (and verify the efibootmgr versions)? koji keeps old nightly live builds around for a while, you can find them by searching for 'closed' tasks of the createLiveCD' method. Problem "show_boot_order(): No such file or directory" only occurs when NVRAM has no boot order entry, which is the state after "zapping PRAM." If I regress to efibootmgr-0.5.4-16.fc20.x86_64 the problem doesn't happen. Problem is also 100% reproducible on a MacbookPro 9,2. All versions of efibootmgr-0.7.0 are affected. Problem doesn't occur with 0.5.4. This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |