From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 20:53:32 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 7362E820; Mon, 3 Nov 2014 20:53:32 +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 F0BD896E; Mon, 3 Nov 2014 20:53:31 +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 <1XlOcz-001ccU-Vv>; Mon, 03 Nov 2014 21:53:29 +0100 Received: from g226063058.adsl.alicedsl.de ([92.226.63.58] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1XlOcz-002PsC-S5>; Mon, 03 Nov 2014 21:53:29 +0100 Date: Mon, 3 Nov 2014 21:53:26 +0100 From: "O. Hartmann" To: Dimitry Andric Subject: Re: CURRENT: EFI boot failure Message-ID: <20141103215326.4a2a0e91.ohartman@zedat.fu-berlin.de> In-Reply-To: <9F1F287F-751C-4456-BB5E-540824E1B4E8@FreeBSD.org> 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> <54218B0F.20707@freebsd.org> <9F1F287F-751C-4456-BB5E-540824E1B4E8@FreeBSD.org> Organization: FU Berlin X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/IL3yE1G9y_cZe8hsVz_9mrW"; protocol="application/pgp-signature" X-Originating-IP: 92.226.63.58 X-ZEDAT-Hint: A Cc: Ed Maste , Andriy Gapon , Harald Schmalzbauer , FreeBSD Current , Nathan Whitehorn , Allan Jude 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: Mon, 03 Nov 2014 20:53:32 -0000 --Sig_/IL3yE1G9y_cZe8hsVz_9mrW Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Am Tue, 23 Sep 2014 17:14:46 +0200 Dimitry Andric schrieb: > On 23 Sep 2014, at 17:00, Nathan Whitehorn wrote: > > On 09/23/14 07:28, Harald Schmalzbauer wrote: > >> 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 fau= lty 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. > >>=20 > >> 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 > >>=20 > >> --- 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 @@ > >>=20 > >> BINDIR?=3D /boot > >>=20 > >> +.ifdef CPUTYPE > >> +.undef CPUTYPE > >> +.endif > >> + > >> .if ${MACHINE_CPUARCH} =3D=3D "i386" > >> CFLAGS+=3D -march=3Di386 > >> .endif > > Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9? > > -Nathan >=20 > IMHO CPUTYPE should be ignored for any boot loader program, and the > lowest common denominator should be used instead (i486 for 32-bit, plain > x86_64 for 64-bit). It makes no sense to optimize boot loaders for e.g. > core-avx2. :-) >=20 > But indeed, it appears that we need to add more -mno-foo magic flags... >=20 > -Dimitry >=20 I repoted a bug at Bug 194641 - [EFI] boot/loader.efi: miscompilation on Intel Haswell with AV= X2=20 Please feel free to comment and replenish my superficial observation. Hopefullz, this doesn't get lost. This nasty bug on Haswell CPU bothers me = all the days I update world. --Sig_/IL3yE1G9y_cZe8hsVz_9mrW Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUV+tJAAoJEOgBcD7A/5N8/qYH/3BrCIInWFJb56OWcItBnEtx 1J44YlezR+3b8XP0Fve0MwcVNPHcloA8t7l1/19dI+jlmTZDX668RLdmOI4fKhyL 5OT5hDhcq4Bq+PW0CBN7yxU9/dID1O8jR5JI3M88TD+ixqUSfuHx1CFy1brncJmj gbtqmffHaAxw7Vs/h2Hbo8qKmOPHDFdNXZm0gyq1VNeI/W2/CbZiym/iz9CRSbRT MtZf+63kxO55oDl++Lk6kOqHaTBXS3ZEdbVHVA6/ksL3/zLOTZNh+7An05jbx81l jUP2Ic5XCSKwKbeskz5HysBnOyUCo2OlPvxTKB2u8f0G0378UjqmtjP9Ke9fmv8= =UWZg -----END PGP SIGNATURE----- --Sig_/IL3yE1G9y_cZe8hsVz_9mrW--