linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: P J P <ppandit@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 3.12 to 3.13 boot regression bisected - still applies to 3.16
Date: Tue, 5 Aug 2014 16:07:37 +0100	[thread overview]
Message-ID: <20140805150737.GR15082@console-pimps.org> (raw)
In-Reply-To: <20140805162107.4698f717@pluto>

On Tue, 05 Aug, at 04:21:07PM, Bruno Prémont wrote:
> 
> Thanks, enabling CONFIG_RELOCATABLE allows kernel to successfully boot!
> 
> So you can add my tested-by to the patch.
 
Great, thanks for testing! I've tagged the patch for stable and I'll get
it sent to tip quickly.

> If of interest, memory layout information as reported by 3.16 with
> CONFIG_RELOCATABLE enabled:

[...]

> [    0.000000] efi: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x0000000001100000) (1MB)

Bingo, this is likely to be the reason for the resets.

Overwriting EFI_LOADER_DATA regions (well, any region other than
EFI_CONVENTIONAL_MEMORY) is gonna cause some issues.

-- 
Matt Fleming, Intel Open Source Technology Center

      reply	other threads:[~2014-08-05 15:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  9:34 3.12 to 3.13 boot regression bisected - still applies to 3.16 Bruno Prémont
2014-08-04 12:27 ` Matt Fleming
2014-08-04 13:06   ` Bruno Prémont
2014-08-04 13:54     ` Matt Fleming
2014-08-05  8:02       ` Bruno Prémont
2014-08-05  8:45         ` Matt Fleming
2014-08-05  9:13           ` Bruno Prémont
2014-08-05  9:18             ` Matt Fleming
2014-08-05 11:51               ` Bruno Prémont
2014-08-05 12:11                 ` Bruno Prémont
2014-08-05 12:55                   ` Matt Fleming
2014-08-05 14:21                     ` Bruno Prémont
2014-08-05 15:07                       ` Matt Fleming [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=20140805150737.GR15082@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=akpm@linux-foundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ppandit@redhat.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;
as well as URLs for NNTP newsgroup(s).