From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "Bruno Prémont"
<bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
Cc: P J P <ppandit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 3.12 to 3.13 boot regression bisected - still applies to 3.16
Date: Mon, 4 Aug 2014 13:27:28 +0100 [thread overview]
Message-ID: <20140804122728.GH15082@console-pimps.org> (raw)
In-Reply-To: <20140804113435.34ed8c76@pluto>
On Mon, 04 Aug, at 11:34:35AM, Bruno Prémont wrote:
> Hi,
>
> Since 3.13 kernels with built-in initrd fail to boot on Fujitsu hardware
> in EFI mode (efi stub) though the exact same kernel binary does boot in
> BIOS mode (grub).
> Interestingly EFI kernels with different config do boot under VMWare.
>
> Your patch "initramfs: read CONFIG_RD_ variables for initramfs
> compression" is the trigger.
>
>
> Is something missing in EFI stub or why do things behave differently?
Nuts. I suspect it's an EFI boot stub bug. Have you definitely tried out
3.16? In particular the following commit might make a difference,
commit c7fb93ec51d4
Author: Michael Brown <mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
Date: Thu Jul 10 12:26:20 2014 +0100
x86/efi: Include a .bss section within the PE/COFF headers
The PE/COFF headers currently describe only the initialised-data
portions of the image, and result in no space being allocated for the
uninitialised-data portions. Consequently, the EFI boot stub will end
up overwriting unexpected areas of memory, with unpredictable results.
Fix by including a .bss section in the PE/COFF headers (functionally
equivalent to the init_size field in the bzImage header).
Signed-off-by: Michael Brown <mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
Cc: Thomas Bächler <thomas-fd97jBR+K/6hPH1hqNUYSQ@public.gmane.org>
Cc: Josh Boyer <jwboyer-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy@public.gmane.org>
Cc: <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Signed-off-by: Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Looking at compiled kernel with and without this patch the resulting
> bzImage is similar in size but in build directory I get:
Could you send me the initrd image? I'd like to try and reproduce this
on my end, even though I regularly boot with a built-in initrd.
--
Matt Fleming, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
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
Subject: Re: 3.12 to 3.13 boot regression bisected - still applies to 3.16
Date: Mon, 4 Aug 2014 13:27:28 +0100 [thread overview]
Message-ID: <20140804122728.GH15082@console-pimps.org> (raw)
In-Reply-To: <20140804113435.34ed8c76@pluto>
On Mon, 04 Aug, at 11:34:35AM, Bruno Prémont wrote:
> Hi,
>
> Since 3.13 kernels with built-in initrd fail to boot on Fujitsu hardware
> in EFI mode (efi stub) though the exact same kernel binary does boot in
> BIOS mode (grub).
> Interestingly EFI kernels with different config do boot under VMWare.
>
> Your patch "initramfs: read CONFIG_RD_ variables for initramfs
> compression" is the trigger.
>
>
> Is something missing in EFI stub or why do things behave differently?
Nuts. I suspect it's an EFI boot stub bug. Have you definitely tried out
3.16? In particular the following commit might make a difference,
commit c7fb93ec51d4
Author: Michael Brown <mbrown@fensystems.co.uk>
Date: Thu Jul 10 12:26:20 2014 +0100
x86/efi: Include a .bss section within the PE/COFF headers
The PE/COFF headers currently describe only the initialised-data
portions of the image, and result in no space being allocated for the
uninitialised-data portions. Consequently, the EFI boot stub will end
up overwriting unexpected areas of memory, with unpredictable results.
Fix by including a .bss section in the PE/COFF headers (functionally
equivalent to the init_size field in the bzImage header).
Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>
Cc: Thomas Bächler <thomas@archlinux.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
> Looking at compiled kernel with and without this patch the resulting
> bzImage is similar in size but in build directory I get:
Could you send me the initrd image? I'd like to try and reproduce this
on my end, even though I regularly boot with a built-in initrd.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-08-04 12:27 UTC|newest]
Thread overview: 21+ 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 9:34 ` Bruno Prémont
2014-08-04 12:27 ` Matt Fleming [this message]
2014-08-04 12:27 ` Matt Fleming
[not found] ` <20140804122728.GH15082-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-08-04 13:06 ` Bruno Prémont
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
[not found] ` <20140805084542.GM15082-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-08-05 9:13 ` Bruno Prémont
2014-08-05 9:13 ` Bruno Prémont
2014-08-05 9:18 ` Matt Fleming
[not found] ` <20140805091848.GN15082-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-08-05 11:51 ` Bruno Prémont
2014-08-05 11:51 ` Bruno Prémont
2014-08-05 12:11 ` Bruno Prémont
2014-08-05 12:11 ` Bruno Prémont
2014-08-05 12:55 ` Matt Fleming
2014-08-05 12:55 ` Matt Fleming
[not found] ` <20140805125548.GP15082-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-08-05 14:21 ` Bruno Prémont
2014-08-05 14:21 ` Bruno Prémont
2014-08-05 15:07 ` Matt Fleming
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=20140804122728.GH15082@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ppandit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 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.