Re: CURRENT: EFI boot failure

Am Tue, 23 Sep 2014 16:51:08 +0200
Harald Schmalzbauer <h.schmalzbauer_at_omnilan.de> schrieb:

>  Bezüglich Harald Schmalzbauer's Nachricht vom 23.09.2014 16:28
> (localtime):
> >  Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
> >> …
> >> The problem I reported about in the first place is triggered by a faulty loader.efi
> >> that arises, when optimisation level is -O3. -O2 works fine.
> > I can confirm that this problem also shows up when using
> > 'CPUTYPE?=core-avx2'
> > Setting CPUTYPE to core-avx-i doesnt ehibit the problem.
> >
> > I could narrow down the cause to libefi.a (sys/boot/efi).
> > But I don't understand the things going on there, so no clue how to fix
> > besides maybe
> >
> > --- sys/boot/efi/Makefile.inc.orig 2014-09-23 16:22:46.000000000 +0200
> > +++ sys/boot/efi/Makefile.inc 2014-09-23 16:25:16.000000000 +0200
> > _at__at_ -2,6 +2,10 _at__at_
> >
> > BINDIR?= /boot
> >
> > +.ifdef CPUTYPE
> > +.undef CPUTYPE
> > +.endif
> 
> Sorry, forget the suggestion, it doesn't work since it leads to CFLAG
> -march="" and the same problem occurs.
> For my case this works:
> --- sys/boot/efi/Makefile.inc.orig      2014-09-23 16:22:46.000000000 +0200
> +++ sys/boot/efi/Makefile.inc   2014-09-23 16:46:30.000000000 +0200
> _at__at_ -2,6 +2,10 _at__at_
>  
>  BINDIR?=       /boot
>  
> +.if ${CPUTYPE} == "core-avx2"
> +CPUTYPE=       core-avx-i
> +.endif
> +
>  .if ${MACHINE_CPUARCH} == "i386"
>  CFLAGS+=        -march=i386
>  .endif
> 
> JFI
> 
> -Harry
> 

Has this problem anyhow seriously been addressed? I run into this very often on several
platforms with HAswell-based CPUs (other systems with IvyBridge or SandyBridge are still
to be migrated to UEFI boot, so I do not have any older architectures at hand to proof
whether this issue is still present or not on Non-AVX2 systems.

If there is no progress so far, would it be well-advised to open a PR?

Regards,
Oliver