Date: Sat, 4 Oct 2014 08:47:37 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> Cc: Allan Jude <allanjude@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Ed Maste <emaste@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, Andriy Gapon <avg@freebsd.org> Subject: Re: CURRENT: EFI boot failure Message-ID: <20141004084737.64b35fd8.ohartman@zedat.fu-berlin.de> In-Reply-To: <542188DC.8000307@omnilan.de> References: <20140916020541.03c18d04.ohartman@zedat.fu-berlin.de> <54178607.1060305@freebsd.org> <541786BE.6010105@freebsd.org> <20140916075121.29989a53.ohartman@zedat.fu-berlin.de> <5417E20D.8070607@freebsd.org> <20140916230348.189e80cd.ohartman@zedat.fu-berlin.de> <CAPyFy2AicKf-PWGDnq80Zmm8ukwTkURZm8RRUFxdfHK=Xd7XAQ@mail.gmail.com> <5418B8C3.7040406@FreeBSD.org> <20140919152207.0473e213.ohartman@zedat.fu-berlin.de> <542183A6.7060802@omnilan.de> <542188DC.8000307@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Wu7x9jUNN+v16F1YD7Mii+Y
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Am Tue, 23 Sep 2014 16:51:08 +0200
Harald Schmalzbauer <h.schmalzbauer@omnilan.de> schrieb:
> Bez=FCglich Harald Schmalzbauer's Nachricht vom 23.09.2014 16:28
> (localtime):
> > Bez=FCglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
> >> =85
> >> The problem I reported about in the first place is triggered by a faul=
ty loader.efi
> >> that arises, when optimisation level is -O3. -O2 works fine.
> > I can confirm that this problem also shows up when using
> > 'CPUTYPE?=3Dcore-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
> > @@ -2,6 +2,10 @@
> >
> > BINDIR?=3D /boot
> >
> > +.ifdef CPUTYPE
> > +.undef CPUTYPE
> > +.endif
>=20
> Sorry, forget the suggestion, it doesn't work since it leads to CFLAG
> -march=3D"" and the same problem occurs.
> For my case this works:
> --- sys/boot/efi/Makefile.inc.orig 2014-09-23 16:22:46.000000000 +02=
00
> +++ sys/boot/efi/Makefile.inc 2014-09-23 16:46:30.000000000 +0200
> @@ -2,6 +2,10 @@
> =20
> BINDIR?=3D /boot
> =20
> +.if ${CPUTYPE} =3D=3D "core-avx2"
> +CPUTYPE=3D core-avx-i
> +.endif
> +
> .if ${MACHINE_CPUARCH} =3D=3D "i386"
> CFLAGS+=3D -march=3Di386
> .endif
>=20
> JFI
>=20
> -Harry
>=20
Has this problem anyhow seriously been addressed? I run into this very ofte=
n on several
platforms with HAswell-based CPUs (other systems with IvyBridge or SandyBri=
dge are still
to be migrated to UEFI boot, so I do not have any older architectures at ha=
nd 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=20
--Sig_/Wu7x9jUNN+v16F1YD7Mii+Y
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJUL5gKAAoJEOgBcD7A/5N8CuUH/0qJe5V9ogD2fLpkFaY85KAr
9nZbec4LMvnL5nmKLxaOL+PnGyp6YJ/E5eW4yUsfCD9720TDsxmEdRf4ylVSCcSy
2trr3zlSX8tRhXX1BGGpzecMauvVXKrmmZ+erdk+cRNnYsc5ntZesEBFLGBHBgR0
5dTIw72PaNuqwoG8z/C9Q/LA7OWt79K9USiDgV/qcuEXusKDJO4Ob8+G1jvzG5Ff
utcLgZ+x1T9XQefWw0fiobouQ00zjxwvHfLN2DB/RcTLA7GUUc2g4f1CdBzyn9K3
F/nTzWmk1DBxyUT+gpUh4+ThOtT0DRDbSaFWlgapVsz28TyvRjSkCZe9vOmfb5U=
=Qtrv
-----END PGP SIGNATURE-----
--Sig_/Wu7x9jUNN+v16F1YD7Mii+Y--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141004084737.64b35fd8.ohartman>