From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Madper Xie <cxie-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram.
Date: Mon, 11 Nov 2013 11:07:01 +0000 [thread overview]
Message-ID: <20131111110701.GE22636@console-pimps.org> (raw)
In-Reply-To: <87fvr3h3b9.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, 11 Nov, at 02:15:22PM, Madper Xie wrote:
> 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?
Urgh.............
Thanks for the report. Could you provide some more details?
- Is your machine definitely bricked?
- Exactly which Dell machine is this?
- What were you doing to cause your machine to not boot? Using
efibootmgr?
- Please send your .config
- Have you reported this to any BIOS engineers to confirm the cause of
the bricking?
- Have you got a dmesg from the machine before it broke?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-11-11 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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 12:57 ` Madper Xie
[not found] ` <878uws1msy.fsf-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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=20131111110701.GE22636@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=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 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).