From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757257Ab3KHK3d (ORCPT ); Fri, 8 Nov 2013 05:29:33 -0500 Received: from b.ns.miles-group.at ([95.130.255.144]:1661 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757091Ab3KHK32 (ORCPT ); Fri, 8 Nov 2013 05:29:28 -0500 Message-ID: <527CBD01.1000908@nod.at> Date: Fri, 08 Nov 2013 11:29:21 +0100 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Yasuaki Ishimatsu CC: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, matt.fleming@intel.com, matthew.garrett@nebula.com, jlee@suse.com Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia References: <527C93B5.7010407@jp.fujitsu.com> <527C9B5C.6040509@nod.at> <527CB013.30200@jp.fujitsu.com> <527CB0F4.8080606@nod.at> <527CBC05.6080505@jp.fujitsu.com> In-Reply-To: <527CBC05.6080505@jp.fujitsu.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 08.11.2013 11:25, schrieb Yasuaki Ishimatsu: > (2013/11/08 18:37), Richard Weinberger wrote: >> Am 08.11.2013 10:34, schrieb Yasuaki Ishimatsu: >>> (2013/11/08 17:05), Richard Weinberger wrote: >>>> Am 08.11.2013 08:33, schrieb Yasuaki Ishimatsu: >>>>> By following works, my system very often fails set_variable() to set new >>>>> variable to efi variable storage and shows "efivars: set_variable() failed: >>>>> status=-28" message. >>>>> >>>>> - commit 31ff2f20d9003e74991d135f56e503fe776c127c >>>>> efi: Distinguish between "remaining space" and actually used space >>>>> - commit 8c58bf3eec3b8fc8162fe557e9361891c20758f2 >>>>> x86,efi: Implement efi_no_storage_paranoia parameter >>>>> - commit f8b8404337de4e2466e2e1139ea68b1f8295974f >>>>> Modify UEFI anti-bricking code >>>>> >>>>> When booting my system, remaining space of efi variable storage is about >>>>> 5KB. So there is no room that sets a new variable to the storage. >>>>> >>>>> According to above works, efi_no_storage_paranoia parameter was prepared >>>>> for sane UEFI which can do gc and fulfills spec. But why need a system >>>>> with a sane UEFI set the parameter? It is wrong. A system with a broken >>>>> UEFI should set the parameter. >>>> >>>> And how does one know that his UEFI is broken? >>> >>> I have no idea. But at least, bricked board is broken UEFI. >>> Do you know the issue occurs on several boards or specific board? >> >> On *many* boards including laptops.... >> Please read the history of the whole issue. > > Thank you for your comment. > I has read git log. But there is no information like this. > So I will read them of related threads again. Do you know good threads > to know the history of the issue? Everything started with an issue that killed Samsung laptops: http://mjg59.dreamwidth.org/22855.html Later it was found that if you write too much into UEFI variables many UEFI implementations will do bad things. Thanks, //richard