From: Benjamin Gilbert <bgilbert@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Gabriel C <nix.or.die@gmail.com>,
linux-x86_64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>,
bero@lindev.ch, Andi Kleen <ak@linux.intel.com>
Subject: Re: 4.17.x won't boot due to "x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G"
Date: Tue, 3 Jul 2018 23:10:27 -0400 [thread overview]
Message-ID: <20180704031027.GA24835@trogon.sfo.coreos.systems> (raw)
In-Reply-To: <20180703142150.tqckl7miou3wf33q@kshutemo-mobl1>
On Tue, Jul 03, 2018 at 05:21:50PM +0300, Kirill A. Shutemov wrote:
> I don't know how to solve it. As far as I know we don't support compiling
> kernel with LTO in mainline.
>
> Any suggestions?
>
> Benjamin, do you change LDFLAGS or CFLAGS when compiling the kernel?
We're using the standard build flags as far as I can tell. In particular,
we don't enable LTO, and I've verified that -flto isn't in the build logs.
Here's a sample image:
https://users.developer.core-os.net/bgilbert/4.17/vmlinuz-4.17.3-coreos
https://users.developer.core-os.net/bgilbert/4.17/vmlinux-4.17.3-coreos
https://users.developer.core-os.net/bgilbert/4.17/System.map
--Benjamin Gilbert
next prev parent reply other threads:[~2018-07-04 3:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF=P+=5c-baQp-CK1ViG8h=mMRv6d3EgEsN_U4rbBx-Pwv_Krw@mail.gmail.com>
2018-07-01 21:32 ` 4.17.x won't boot due to "x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G" Benjamin Gilbert
2018-07-02 9:34 ` Kirill A. Shutemov
2018-07-02 19:01 ` Benjamin Gilbert
2018-07-03 8:30 ` Kirill A. Shutemov
2018-07-03 8:59 ` Thomas Gleixner
2018-07-03 11:01 ` Kirill A. Shutemov
2018-07-03 11:24 ` Gabriel C
2018-07-03 12:44 ` Kirill A. Shutemov
2018-07-03 14:02 ` Thomas Gleixner
2018-07-03 14:07 ` Bernhard Rosenkraenzer
2018-07-03 14:19 ` Thomas Gleixner
2018-07-03 14:21 ` Kirill A. Shutemov
2018-07-03 14:27 ` Thomas Gleixner
2018-07-03 18:03 ` Andi Kleen
2018-07-03 20:26 ` Kirill A. Shutemov
2018-07-03 21:00 ` Andi Kleen
2018-07-04 3:10 ` Benjamin Gilbert [this message]
2018-07-04 13:21 ` Kirill A. Shutemov
2018-07-04 15:08 ` Kirill A. Shutemov
2018-07-04 20:42 ` Benjamin Gilbert
2018-07-06 6:37 ` Masahiro Yamada
2018-07-06 10:41 ` Kirill A. Shutemov
2018-07-06 14:13 ` Masahiro Yamada
2018-07-06 14:39 ` Gabriel C
2018-07-06 16:33 ` Kirill A. Shutemov
2018-07-06 17:31 ` Gabriel C
2018-07-07 0:55 ` Masahiro Yamada
2018-07-06 16:29 ` Kirill A. Shutemov
2018-07-06 18:11 ` Andi Kleen
2018-07-06 19:34 ` Benjamin Gilbert
2018-07-07 1:21 ` Masahiro Yamada
2018-07-09 10:10 ` Kirill A. Shutemov
2018-07-09 10:37 ` Masahiro Yamada
2018-07-25 17:26 Dmitry Malkin
2018-07-25 21:21 ` Kirill A. Shutemov
2018-07-26 8:10 ` Dmitry Malkin
2018-07-26 14:50 ` Kirill A. Shutemov
2018-07-26 16:21 ` Dmitry Malkin
2018-07-27 13:46 ` Kirill A. Shutemov
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=20180704031027.GA24835@trogon.sfo.coreos.systems \
--to=bgilbert@redhat.com \
--cc=ak@linux.intel.com \
--cc=bero@lindev.ch \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nix.or.die@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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