Bug 1158235

Summary: [abrt] efibootmgr: vars_get_variable(): efibootmgr killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Juan Orti Alcaine <jorti>
Component: efibootmgrAssignee: Peter Jones <pjones>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: apieum, fedoraproject, Lindhe94, pjones, surya_prabhakar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/61c10b7d76766d712443fe3d267874c0ea7b1268
Whiteboard: abrt_hash:c604792c51597f60e449f5afb7913580635dded6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 04:34:02 UTC Type: ---
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 Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: os_info_in_rootdir
none
File: proc_pid_status
none
File: var_log_messages none

Description Juan Orti Alcaine 2014-10-28 22:12:38 UTC
Description of problem:
Installing Fedora21-Workstation-Beta-RC1-x86_64 in my PC with EFI. I added gpt to the boot options to make the partitions with GPT.
I choosed Btrfs partitions, everything else on defaults.
When the installation process was configuring the boot loader, this error prompted.

Version-Release number of selected component:
efibootmgr-0.7.0-5.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        efibootmgr
crash_function: vars_get_variable
executable:     /mnt/sysimage/usr/sbin/efibootmgr
kernel:         3.17.1-302.fc21.x86_64
os_release_in_rootdir: Fedora release 21 (Twenty One)
rootdir:        /mnt/sysimage
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 vars_get_variable at vars.c:165
 #1 efi_get_variable at lib.c:94
 #2 read_vars at src/efibootmgr/efibootmgr.c:108

Comment 1 Juan Orti Alcaine 2014-10-28 22:12:41 UTC
Created attachment 951566 [details]
File: backtrace

Comment 2 Juan Orti Alcaine 2014-10-28 22:12:42 UTC
Created attachment 951567 [details]
File: cgroup

Comment 3 Juan Orti Alcaine 2014-10-28 22:12:43 UTC
Created attachment 951568 [details]
File: core_backtrace

Comment 4 Juan Orti Alcaine 2014-10-28 22:12:44 UTC
Created attachment 951569 [details]
File: environ

Comment 5 Juan Orti Alcaine 2014-10-28 22:12:46 UTC
Created attachment 951570 [details]
File: exploitable

Comment 6 Juan Orti Alcaine 2014-10-28 22:12:47 UTC
Created attachment 951571 [details]
File: limits

Comment 7 Juan Orti Alcaine 2014-10-28 22:12:48 UTC
Created attachment 951572 [details]
File: maps

Comment 8 Juan Orti Alcaine 2014-10-28 22:12:49 UTC
Created attachment 951573 [details]
File: open_fds

Comment 9 Juan Orti Alcaine 2014-10-28 22:12:51 UTC
Created attachment 951574 [details]
File: os_info_in_rootdir

Comment 10 Juan Orti Alcaine 2014-10-28 22:12:52 UTC
Created attachment 951575 [details]
File: proc_pid_status

Comment 11 Juan Orti Alcaine 2014-10-28 22:12:53 UTC
Created attachment 951576 [details]
File: var_log_messages

Comment 12 Florian Kisser 2014-11-10 21:02:35 UTC
Another user experienced a similar problem:

While installing Fedora 21 Beta 4 on an UEFI system the installation process paused after software installation and then prompted if to ignore this error.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        efibootmgr
crash_function: vars_get_variable
executable:     /mnt/sysimage/usr/sbin/efibootmgr
kernel:         3.17.1-302.fc21.x86_64
os_release_in_rootdir: Fedora release 21 (Twenty One)
package:        efibootmgr-0.7.0-5.fc21
reason:         efibootmgr killed by SIGSEGV
rootdir:        /mnt/sysimage
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Grégory Salvan 2015-04-24 17:58:04 UTC
Hi, in case it helps, I had the same issue (efi, btrfs), I think I found why: efivars are not mounted on sysimage.

After install process, I mounted efivarfs on sysimage like that:
$ sudo mount -t efivarfs none /mnt/sysimage/sys/firmware/efi/efivars

Then I chroot with install mounted file system on /mnt/sysimage and installed grub-efi, grub-efi-modules, efivars:
$ sudo chroot /mnt/sysimage /bin/bash
$ yum install grub2-efi grub2-efi-modules efivars

Finaly "yum update" installed the newest kernel which had automatically updated the boot and fix the matter.

Comment 14 Fedora End Of Life 2015-11-04 12:31:27 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-12-02 04:34:05 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.