From: Jiri Slaby <jslaby@suse.cz>
To: matthew.garrett@nebula.com
Cc: matt.fleming@intel.com, cbouatmailru@gmail.com,
ccross@android.com, keescook@chromium.org,
Tony Luck <tony.luck@intel.com>,
linux-efi@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Cannot add new efi boot entry
Date: Sun, 14 Apr 2013 23:25:39 +0200 [thread overview]
Message-ID: <516B1ED3.9040900@suse.cz> (raw)
Hi,
after update to 3.8, every update of the kernel ends up in an unbootable
machine. It is due to the following commit:
commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
Author: Matthew Garrett <matthew.garrett@nebula.com>
Date: Sat Mar 2 19:40:17 2013 -0500
efi: be more paranoid about available space when creating variables
efibootmgr which tries to add an entry and silently fails when writing
to /sys/firmware/efi/vars/new_var with -ENOSPC.
There are many entries in there:
# efibootmgr
BootCurrent: 000D
Timeout: 0 seconds
BootOrder:
0018,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Lenovo Diagnostics
Boot0004 Startup Interrupt Menu
Boot0005 ME Configuration Menu
Boot0006 Rescue and Recovery
Boot0007* USB CD
Boot0008* USB FDD
Boot0009* ATAPI CD0
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* ATA HDD2
Boot000D* USB HDD
Boot000E* PCI LAN
Boot000F* ATAPI CD1
Boot0010 Other CD
Boot0011* ATA HDD3
Boot0012 Other HDD
Boot0013* IDER BOOT CDROM
Boot0014* IDER BOOT Floppy
Boot0015* ATA HDD
Boot0016* ATAPI CD:
Boot0017* PCI LAN
Boot0018* Linux
Remaining size is about 20k, added entry size is hundreds bytes, store
size is 64k.
Obviously lowering the limitation from 1/2 to 1/4 fixes the problem for
me because it always worked on my setup to store a new entry...
Any ideas how to overcome that? It would be better to blacklist bad
machines rather than whitelist good ones, right?
thanks,
--
js
suse labs
next reply other threads:[~2013-04-14 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 21:25 Jiri Slaby [this message]
2013-04-16 9:56 ` joeyli
2013-04-16 10:11 ` Matt Fleming
2013-04-17 11:33 ` joeyli
2013-04-17 14:29 ` Jiri Slaby
2013-04-17 14:49 ` joeyli
2013-04-17 14:51 ` joeyli
2013-04-17 14:51 ` Matt Fleming
2013-04-18 18:07 ` Jiri Slaby
2013-04-20 7:40 ` Jiri Slaby
2013-04-22 11:07 ` Matt Fleming
2013-04-22 11:31 ` joeyli
2013-04-22 12:20 ` Matt Fleming
2013-04-22 12:25 ` Jiri Slaby
2013-04-22 16:43 ` Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516B1ED3.9040900@suse.cz \
--to=jslaby@suse.cz \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthew.garrett@nebula.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome