On Wed, Apr 17, 2019 at 07:32:34AM +0100, Colin Watson wrote:
> On Wed, Apr 17, 2019 at 08:04:57AM +0200, Heinrich Schuchardt wrote:
> > Since this commit a51f953f4ee8 ("mkimage: Align efi sections on 4k
> > boundary") grubarm.efi crashes.
> >
> > Hence I suggest to revert this patch for when building packages
> > grub-efi-arm*.
> >
> > According to the author of the problematic patch without the patch Qcom
> > ARM notebooks did not work. So we better do not revert it for aarch64
> > until a final solution is found.
>
> I'm not going to revert a patch when building for one architecture but
> not for another. I'm happy to apply follow-up patches if people with
> access to the right hardware point me to suitable ones (and preferably
> get them upstream first).
>
> > The upstream report is here:
> > http://lists.gnu.org/archive/html/grub-devel/2019-04/msg00075.html
>
> Alexander, Leif, any comment here?
This 2-patch series posted to grub-devel by Alex Tuesday evening
resolves this issue:
https://lists.gnu.org/archive/html/grub-devel/2019-04/msg00130.html
1/2 also satisfactorily explains why there was a difference in
behaviour between images generated by grub-mkimage and
grub-mkstandalone (trampolines spilling over into different sections).
>From code review as well as some (but not exhaustive) testing, this
seems like a no-op for all !armhf platforms.
Could these two patches be cherry-picked into Buster please?
/
Leif
