From: Matt Fleming <matt@console-pimps.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: joeyli <jlee@suse.com>,
matthew.garrett@nebula.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: Re: Cannot add new efi boot entry
Date: Mon, 22 Apr 2013 12:07:15 +0100 [thread overview]
Message-ID: <517519E3.2030409@console-pimps.org> (raw)
In-Reply-To: <5172466B.9080105@suse.cz>
On 20/04/13 08:40, Jiri Slaby wrote:
> On 04/18/2013 08:07 PM, Jiri Slaby wrote:
>> On 04/17/2013 04:51 PM, Matt Fleming wrote:
>>> On 17/04/13 15:29, Jiri Slaby wrote:
>>>> On 04/16/2013 12:11 PM, Matt Fleming wrote:
>>>>> On 16/04/13 10:56, joeyli wrote:
>>>>>> I think I just got the same situation on my side with Acer machine. I am
>>>>>> trying Matthew's new patchset hope can avoid this situation:
>>>>>>
>>>>>> https://lkml.org/lkml/2013/4/15/473
>>>>>
>>>>> Please do let us know whether the patches work for you.
>>>>
>>>> Hmm, where did efi_query_variable_store in 3/3 come from?
>>>
>>> It's in a patch on the 'urgent' branch at,
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
>>
>> The 3 patches plus that one work for me.
>
> Actually they don't :(:
> open("/sys/firmware/efi/vars/new_var", O_WRONLY) = 3
> write(3,
> "B\0o\0o\0t\0000\0000\0001\0003\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 2084) = -1 ENOSPC (No space left on device)
> close(3) = 0
Thanks for testing Jiri.
You can disable the EFI storage checks in -rc8 by using the
efi_no_storage_paranoia kernel parameter, but it's only recommended to
do that if you machine ends up in these kinds of situations where
garbage collection isn't be initiated, or your machine ships with > 50%
of the variable store in use from the factory.
Matthew, what kind of info do you need from Jiri to improve the storage
limit algorithm?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-04-22 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 21:25 Cannot add new efi boot entry Jiri Slaby
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 [this message]
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=517519E3.2030409@console-pimps.org \
--to=matt@console-pimps.org \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=jlee@suse.com \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).