All of lore.kernel.org
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
	matthew.garrett@nebula.com, cbouatmailru@gmail.com,
	ccross@android.com, keescook@chromium.org,
	Tony Luck <tony.luck@intel.com>,
	linux-efi@vger.kernel.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Cannot add new efi boot entry
Date: Wed, 17 Apr 2013 19:33:17 +0800	[thread overview]
Message-ID: <1366198397.23707.68.camel@linux-s257.site> (raw)
In-Reply-To: <516D23B5.4070209@intel.com>

於 二，2013-04-16 於 11:11 +0100，Matt Fleming 提到：
> On 16/04/13 10:56, joeyli wrote:
> > I think I just got the same situation on my side with Acer machine. I am
> > trying Matthew's new patchset hope can avoid this situation:
> > 
> > https://lkml.org/lkml/2013/4/15/473
> 
> Please do let us know whether the patches work for you.
> 
> 

I applied Matthew's patches to v3.9-rc7 then tested...

The active_size checking works to me on my Acer machine for avoid the
storage_size/2 issue, I can use efibootmgr to create new boot entry,
now.

But, I found there have the following warning:

[    1.347581] [Firmware Bug]: efi: Inconsistent initial size

Then, I add printk to print the values of var_size and active_size,
found the values always 0 after system reboot. I am doing to add more
log for locate if this is a BIOS issue.


Thanks a lot!
Joey Lee

  reply	other threads:[~2013-04-17 11:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 21:25 Cannot add new efi boot entry Jiri Slaby
2013-04-14 21:25 ` Jiri Slaby
     [not found] ` <516B1ED3.9040900-AlSwsSmVLrQ@public.gmane.org>
2013-04-16  9:56   ` joeyli
2013-04-16  9:56     ` joeyli
2013-04-16 10:11     ` Matt Fleming
2013-04-17 11:33       ` joeyli [this message]
     [not found]       ` <516D23B5.4070209-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-04-17 14:29         ` Jiri Slaby
2013-04-17 14:29           ` Jiri Slaby
     [not found]           ` <516EB1B6.7050506-AlSwsSmVLrQ@public.gmane.org>
2013-04-17 14:49             ` joeyli
2013-04-17 14:49               ` joeyli
     [not found]               ` <1366210184.23707.69.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-04-17 14:51                 ` joeyli
2013-04-17 14:51                   ` joeyli
2013-04-17 14:51             ` Matt Fleming
2013-04-17 14:51               ` Matt Fleming
     [not found]               ` <516EB6F2.6070806-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-18 18:07                 ` Jiri Slaby
2013-04-18 18:07                   ` Jiri Slaby
2013-04-20  7:40                   ` Jiri Slaby
     [not found]                     ` <5172466B.9080105-AlSwsSmVLrQ@public.gmane.org>
2013-04-22 11:07                       ` Matt Fleming
2013-04-22 11:07                         ` Matt Fleming
     [not found]                         ` <517519E3.2030409-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-22 11:31                           ` joeyli
2013-04-22 11:31                             ` joeyli
     [not found]                             ` <1366630277.23707.132.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-04-22 12:20                               ` Matt Fleming
2013-04-22 12:20                                 ` Matt Fleming
2013-04-22 12:25                                 ` Jiri Slaby
     [not found]                                   ` <51752C2C.4090707-AlSwsSmVLrQ@public.gmane.org>
2013-04-22 16:43                                     ` Matthew Garrett
2013-04-22 16:43                                       ` 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=1366198397.23707.68.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=cbouatmailru@gmail.com \
    --cc=ccross@android.com \
    --cc=jslaby@suse.cz \
    --cc=keescook@chromium.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matthew.garrett@nebula.com \
    --cc=tony.luck@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 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.