From: Matt Fleming <matt@console-pimps.org>
To: Madper Xie <cxie@redhat.com>
Cc: "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: Re: [BUG]: DELL XPS 8500 become a brick after fill too many entries to nvram.
Date: Wed, 13 Nov 2013 11:21:23 +0000 [thread overview]
Message-ID: <20131113112052.GJ22636@console-pimps.org> (raw)
In-Reply-To: <87eh6nt8oo.fsf@redhat.com>
On Mon, 11 Nov, at 08:38:31PM, Madper Xie wrote:
>
> matt@console-pimps.org writes:
>
> > 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?
> Yes, pretty sure. After I press power button, the screen shows "DELL"
> and hangs. I can't step into any configure interface and the keyboard is
> dead. (NumLock led on, and I can't turn it off.) Of course my kernel
> won't be loaded. The only way to fix it is change the jump line which is
> on the motherboard.
OK, that's pretty conclusive. Thanks.
> > - Have you got a dmesg from the machine before it broke?
> No. But with a diagnostic kernel(without change the behavior of
> efi. Simply print total size and remain size when I write something to
> nvram. Provided by Lenny), I got following output:
Have you been able to calculate the safe limit of NVRAM we need to
reserve to avoid bricking your machine?
I was interested in the DMI and other firmware strings from dmesg.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-11-13 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 6:15 Madper Xie
2013-11-11 11:07 ` Matt Fleming
2013-11-11 12:38 ` Madper Xie
2013-11-13 11:21 ` Matt Fleming [this message]
2013-11-13 12:57 ` Madper Xie
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=20131113112052.GJ22636@console-pimps.org \
--to=matt@console-pimps.org \
--cc=cxie@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/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
Powered by JetHome