From: Madper Xie <cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "linux-kernel@vger.kernel.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-efi@vger.kernel.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram.
Date: Mon, 11 Nov 2013 14:15:22 +0800 [thread overview]
Message-ID: <87fvr3h3b9.fsf@redhat.com> (raw)
Howdy all,
For now we ensure at least ~5kb free space. But my dell xps still
become a brick after I add too many entries to my nvram. So maybe 5kb
is not safe enough. and 5kb is just aginst Samsung's laptop.
So should we enlarge EFI_MIN_RESERVE?
--
Best,
Madper Xie.
WARNING: multiple messages have this Message-ID (diff)
From: Madper Xie <cxie@redhat.com>
To: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi\@vger.kernel.org" <linux-efi@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>
Subject: [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram.
Date: Mon, 11 Nov 2013 14:15:22 +0800 [thread overview]
Message-ID: <87fvr3h3b9.fsf@redhat.com> (raw)
Howdy all,
For now we ensure at least ~5kb free space. But my dell xps still
become a brick after I add too many entries to my nvram. So maybe 5kb
is not safe enough. and 5kb is just aginst Samsung's laptop.
So should we enlarge EFI_MIN_RESERVE?
--
Best,
Madper Xie.
next reply other threads:[~2013-11-11 6:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 6:15 Madper Xie [this message]
2013-11-11 6:15 ` [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram Madper Xie
[not found] ` <87fvr3h3b9.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-11 11:07 ` Matt Fleming
2013-11-11 11:07 ` Matt Fleming
2013-11-11 12:38 ` Madper Xie
2013-11-11 12:38 ` Madper Xie
[not found] ` <87eh6nt8oo.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-13 11:21 ` Matt Fleming
2013-11-13 11:21 ` Matt Fleming
2013-11-13 12:57 ` Madper Xie
2013-11-13 12:57 ` Madper Xie
[not found] ` <878uws1msy.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-13 14:08 ` Matt Fleming
2013-11-13 14:08 ` Matt Fleming
2013-11-18 19:07 ` 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=87fvr3h3b9.fsf@redhat.com \
--to=cxie-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.