From: Madper Xie <cxie@redhat.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Matt Fleming <matt@console-pimps.org>,
Richard Weinberger <richard@nod.at>,
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
Date: Mon, 11 Nov 2013 17:47:30 +0800 [thread overview]
Message-ID: <87eh6ngthv.fsf@redhat.com> (raw)
In-Reply-To: <52809AEB.9080100@jp.fujitsu.com>
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@jp.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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best,
Madper Xie.
next prev parent reply other threads:[~2013-11-11 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 7:33 [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage_paranoia Yasuaki Ishimatsu
2013-11-08 8:05 ` Richard Weinberger
2013-11-08 8:46 ` Madper Xie
2013-11-08 9:34 ` Yasuaki Ishimatsu
2013-11-08 9:37 ` Richard Weinberger
2013-11-08 10:25 ` Yasuaki Ishimatsu
2013-11-08 10:29 ` Richard Weinberger
2013-11-08 10:32 ` Yasuaki Ishimatsu
2013-11-08 14:34 ` Matt Fleming
2013-11-11 8:52 ` Yasuaki Ishimatsu
2013-11-11 9:47 ` Madper Xie [this message]
2013-11-11 10:54 ` Matt Fleming
2013-11-19 3:03 ` Yasuaki Ishimatsu
2013-11-19 3:16 ` Madper Xie
2013-11-20 6:26 ` Yasuaki Ishimatsu
2013-11-20 8:08 ` joeyli
2013-11-21 9:13 ` Yasuaki Ishimatsu
2013-11-21 9:53 ` joeyli
2013-11-21 10:27 ` joeyli
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=87eh6ngthv.fsf@redhat.com \
--to=cxie@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=matthew.garrett@nebula.com \
--cc=richard@nod.at \
/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