[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Nov 2013 17:47:30 +0800
From: Madper Xie <cxie@...hat.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
Cc: Matt Fleming <matt@...sole-pimps.org>,
Richard Weinberger <richard@....at>, linux-efi@...r.kernel.org,
linux-kernel@...r.kernel.org, matt.fleming@...el.com,
matthew.garrett@...ula.com, jlee@...e.com
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia
Howdy Yasuaki,
I know some boxes with small NVRAM (less than 64kb?) will meet many
issues if we always keep ~5kb free space.
But if we really do not keep some free space as default, many box will
become a brick. (In fact, I just fixed a bricked dell xps 8500 last
week. 5kb is not enough for dell xps...)
So maybe the better way is: we check the size of nvram and decide how
many space we retain.
isimatu.yasuaki@...fujitsu.com writes:
> Hi Matt,
>
> I uses FUJITSU's x86 box.
> This does not become bricked even if I use all efi variable storage.
> Thus I want a way to not need to specify efi_no_storage_paranoia
> parameter.
>
> Thanks,
> Yasuaki Ishimatsu
>
>
> (2013/11/08 23:34), Matt Fleming wrote:
>> On Fri, 08 Nov, at 07:32:51PM, Yasuaki Ishimatsu wrote:
>>>> 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 for the information.
>>> I will read it.
>>
>> Out of curiosity, what hardware are you using?
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-efi" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best,
Madper Xie.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists