Bug#815125: Boot failure with Debian linux 4.4.2 package
On Mon, 29 Feb, at 09:34:55PM, Roger Shimizu wrote:
> On Mon, Feb 29, 2016 at 9:25 PM, Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > On Mon, 29 Feb, at 10:49:54AM, Raphael Hertzog wrote:
> >> Hello Matt and Borislav,
> >>
> >> in Debian we got a report (see below and https://bugs.debian.org/815125) that
> >> https://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit?id=67a9108ed4313b85a9c53406d80dc1ae3f8c3e36
> >> was breaking early boot on some machines.
> >>
> >> Can you have a look at those failures?
> >>
> >
> > Can someone provide me with the list of EFI patches that were applied
> > for linux-image-4.4.0-1-amd64 that are not part of the stable kernel
> > tree for linux-4.4.y?
>
> Debian's kernel patch is located in:
> https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/?h=sid
>
> and EFI related, I guess, is in:
> https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/bugfix/x86?h=sid
>
> the final "?h=sid" implies it's for sid which is currently 4.4
> the master branch is for preparing 4.5-rc now.
Thanks Roger.
OK, that rules out an error porting the feature because all the
required patches are present.
Looking at traceback_linux-4.4.2_with_patch_x86-efi-build-our-own-page-table-structures.jpg
from comment #164, it appears as though the firmware is trying to
access an address that isn't mapped in our new dedicated EFI page
tables while inside of SetVirtualAddressMap().
Curiously the E280 memory map describes the range covering the
faulting IP (0x00000000aa9462ee) as "type 20" which is a bogus E820
type and a bogus EFI memory map type.
Alexis, could you boot a kernel with CONFIG_EFI_PGT_DUMP enabled,
efi=debug on the command line and upload the dmesg output? Booting
with efi=old_map,debug should be fine (so your machine won't crash).
Reply to: