Ubuntu
linux package

cannot mount /sys/firmware/efi/efivars on boot

Bug #1146868 reported by G3R
74
This bug affects 19 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

If I choose "ignore" system seems to boot ok.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-10-generic 3.8.0-10.19
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: germanp 1696 F.... pulseaudio
 /dev/snd/controlC0: germanp 1696 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:
 [ 20.031972] r8169 0000:07:00.0 eth0: link up
 [ 20.031978] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Tue Mar 5 10:15:06 2013
HibernationDevice: #RESUME=UUID=f019730f-ee95-4a54-ad30-5d093fbf7e71
InstallationDate: Installed on 2012-12-08 (86 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-9-generic root=UUID=efc9d8fa-6823-4dee-b550-029067d9fb9a ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-9-generic N/A
 linux-backports-modules-3.8.0-9-generic N/A
 linux-firmware 1.103
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-02-17 (15 days ago)
dmi.bios.date: 06/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U1h
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z68X-UD3H-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU1h:bd06/13/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
G3R (germanp1982) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
syscon-hh (syscon-kono) wrote :

The same happens with the kernel image updated to

 * 3.8.0-11_3.8.0-11-20

@Joseph: Your link to the images shows no installable kernel image(s) - tested on march 6th 2013 - so requested test couldn't performed now.

Once more: Booting with the recovery, you will reach the "recovery" console.

After selecting "resume" you will be prompted to hit "S" to skip missing directory and you will reach the tty1 console for log in.

Revision history for this message
Jens Kreiensiek (jenx) wrote :

Same problem here.

The problem doesn't exist in 3.8.0-9.18.
I'll try the latest upstream kernel...

Revision history for this message
Jens Kreiensiek (jenx) wrote :

The problem persists in linux-image-3.9.0-030900rc1-generic_3.9.0-030900rc1.201303060659_amd64.deb

G3R (germanp1982)
tags: added: kernel-bug-exists-upstream
Revision history for this message
G3R (germanp1982) wrote :

Same problem in mainline kernel.

'kernel-bug-exists-upstream' tag added

Revision history for this message
Kithop (kithop) wrote :

I ran into this when compiling from the vanilla 3.9-rc1 (and 3.8.2; 3.8.1 is fine) sources on an Xubuntu 12.10 box with kernel-package. It manifested kind of strangely on my Lenovo machine with EFI support - all I'd see at boot is 'Scanning for btrfs filesystems' and it would appear to hang - recovery mode showed the mount issue with /sys/firmware/efi/efivars that I could successfully skip and at least get to a text console.

It looks like 'CONFIG_EFI_VARS' is the culprit - I unset it and recompiled, and I can now boot successfully. For those using menuconfig, it's under 'Firmware Drivers' as 'EFI Variable Support via sysfs'. I'm not sure if this patch notice is related or the culprit:

http://permalink.gmane.org/gmane.linux.kernel.efi/773

I'm not sure what the ramifications are of having this disabled on a machine that uses EFI to boot, but so far everything seems normal; let me know if you'd like more details from my particular system. Thanks!

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This could be a duplicate of bug 1146988

Revision history for this message
Richard Roberts (prowlcat2000) wrote :

Rather 1146988 might ba a duplicate of this one.

Revision history for this message
Jens Kreiensiek (jenx) wrote :

It seems like this problem is gone in linux-image-3.8.0-12-generic_3.8.0-12.21_amd64.deb

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@G3R

Can you confirm this bug is fixed in the 3.8.0-12 kernel? If so, please mark this bug as "Fix Released".

Thanks!

G3R (germanp1982)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Consumology (hans-georg-schmid) wrote :

Installed 3.8.0-12-generic, problem is gone!

Revision history for this message
Harald Hetzner (haraldhetzner) wrote :

With 3.8.0-12-generic, my computer with an ASRock FM2A75 Pro4-M mainboard, which booted fine with 3.8.0-11-generic in UEFI mode, hangs on boot.

Revision history for this message
Harald Hetzner (haraldhetzner) wrote :

In the meantime, I have erased the contents of my EFI parition and reinstalled grub to it. Now, my computer boots fine again, also with 3.8.0-12-generic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.