From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Matt Fleming <matt@console-pimps.org>
Cc: Madper Xie <cxie@redhat.com>,
"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: Mon, 18 Nov 2013 19:07:20 +0000 [thread overview]
Message-ID: <20131118190720.GA20875@srcf.ucam.org> (raw)
In-Reply-To: <20131113140647.GK22636@console-pimps.org>
On Wed, Nov 13, 2013 at 02:08:14PM +0000, Matt Fleming wrote:
> OK, it looks like the firmware Boot Manager gets very confused when it
> tries to parse the Boot Load Option you created with efibootmgr. This
> looks like a general firmware bug and not something we need to worry
> about in the kernel.
Well, we do do some parsing of the boot parameters in the kernel in
order to avoid hitting a Tianocore bug. But if the problem is just that
the Dell firmware falls over if it sees something that isn't Unicode, I
don't think we can really work around that.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-11-18 19: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
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 [this message]
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=20131118190720.GA20875@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=cxie@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.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).