From owner-freebsd-current@FreeBSD.ORG Sat Oct 4 06:47:41 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95C45C0A; Sat, 4 Oct 2014 06:47:41 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DF51992; Sat, 4 Oct 2014 06:47:40 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1XaJ7y-0001qs-Ng>; Sat, 04 Oct 2014 08:47:38 +0200 Received: from e179164176.adsl.alicedsl.de ([85.179.164.176] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1XaJ7y-000rZV-IN>; Sat, 04 Oct 2014 08:47:38 +0200 Date: Sat, 4 Oct 2014 08:47:37 +0200 From: "O. Hartmann" To: Harald Schmalzbauer 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> <5418B8C3.7040406@FreeBSD.org> <20140919152207.0473e213.ohartman@zedat.fu-berlin.de> <542183A6.7060802@omnilan.de> <542188DC.8000307@omnilan.de> Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/Wu7x9jUNN+v16F1YD7Mii+Y"; protocol="application/pgp-signature" X-Originating-IP: 85.179.164.176 X-ZEDAT-Hint: A Cc: Allan Jude , FreeBSD Current , Ed Maste , Nathan Whitehorn , Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2014 06:47:41 -0000 --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 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--