From owner-freebsd-arch@freebsd.org Wed May 16 07:37:39 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EA99EAB7B9 for ; Wed, 16 May 2018 07:37:39 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 955D07C088 for ; Wed, 16 May 2018 07:37:38 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id F41C137601DE for ; Wed, 16 May 2018 09:37:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id E7CEC37601DC for ; Wed, 16 May 2018 09:37:20 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TeP0TcNQqcKs for ; Wed, 16 May 2018 09:37:20 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id D507237601D4 for ; Wed, 16 May 2018 09:37:20 +0200 (CEST) Date: Wed, 16 May 2018 09:37:20 +0200 (CEST) From: Emeric POUPON To: freebsd-arch Message-ID: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> Subject: Can't build kernel anymore: amd64 kernel requires linker ifunc support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thread-Topic: Can't build kernel anymore: amd64 kernel requires linker ifunc support Thread-Index: qiKSWHaxiQ7/TBc9Yl8V0EwqZGsfnA== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 07:37:39 -0000 Hello, Maybe I missed something, but I recently updated /usr/src (HEAD) and I can'= t build the kernel anymore, I get this: # make -j4 buildkernel --- buildkernel --- make[1]: "/usr/src/Makefile.inc1" line 166: SYSTEM_COMPILER: Determined tha= t CC=3Dcc matches the source tree. Not bootstrapping a cross-compiler. --- buildkernel --- -------------------------------------------------------------- >>> Kernel build for GENERIC started on Wed May 16 09:35:03 CEST 2018 -------------------------------------------------------------- =3D=3D=3D> GENERIC mkdir -p /usr/obj/usr/src/amd64.amd64/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /usr/src/sys/amd64/conf; PATH=3D/usr/obj/usr/src/amd64.amd64/tmp/legacy= /usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/= amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/o= bj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin config -= d /usr/obj/usr/src/amd64.amd64/sys/GENERIC -I '/usr/src/sys/amd64/conf' '/= usr/src/sys/amd64/conf/GENERIC' Kernel build directory is /usr/obj/usr/src/amd64.amd64/sys/GENERIC Don't forget to do ``make cleandepend && make depend'' -------------------------------------------------------------- >>> stage 2.1: cleaning up the object tree -------------------------------------------------------------- cd /usr/obj/usr/src/amd64.amd64/sys/GENERIC; COMPILER_VERSION=3D60000 COMPI= LER_FEATURES=3D" c++11 retpoline" COMPILER_TYPE=3Dclang COMPILER_FREEBSD_VE= RSION=3D1200014 MACHINE_ARCH=3Damd64 MACHINE=3Damd64 CPUTYPE=3D CC=3D"cc -t= arget x86_64-unknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/amd64.amd64/t= mp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX=3D"c++ -target x86_64-u= nknown-freebsd12.0 --sysroot=3D/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/= usr/src/amd64.amd64/tmp/usr/bin" CPP=3D"cpp -target x86_64-unknown-freebsd1= 2.0 --sysroot=3D/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.a= md64/tmp/usr/bin" AS=3D"as" AR=3D"ar" LD=3D"ld" LLVM_LINK=3D"" NM=3Dnm OBJC= OPY=3D"objcopy" RANLIB=3Dranlib STRINGS=3D SIZE=3D"size" INSTALL=3D"sh /usr= /src/tools/install.sh" PATH=3D/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/s= bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.= amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr= /src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin make -j 4 -J 15= ,16 -m /usr/src/share/mk KERNEL=3Dkernel cleandir make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel requires li= nker ifunc support *** [buildkernel] Error code 1 make[1]: stopped in /usr/src 1 error How can I proceed? Regards, From owner-freebsd-arch@freebsd.org Wed May 16 07:47:50 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92A70EAC1A6 for ; Wed, 16 May 2018 07:47:50 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 31EAA7C627 for ; Wed, 16 May 2018 07:47:50 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw0-x235.google.com with SMTP id l142-v6so893611ywc.11 for ; Wed, 16 May 2018 00:47:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PnonHOfUd7J5BegghP9WKivqK5C8xFSqYXKIXjWPbwc=; b=xrI5fP5QB6KR24cOc4v7DeOPwaurjELdrPrQ13z8jHZ/Gyyi9tdI6tkFCxqulnphvw 2lbTO7LAYeJd905wbXVMZufplcqt+NRWevO9KvZso12ZYegH2KxJq0t2EJP4TCNkM83b 5irNnHue4F2bLHlxImL7eWDGikvMAvmYAaWoH13P5PlNYIhMCQZgw/SXreApt5ywWkAw yJvwjrJVbJLUY9TtA3EFUDEkrIxE3qEAsOqxQfGhKwmJDBR6VgbsB+h3LGrXoLf3vvkq 1mI3hSlLd7quH1U+L5W8Vu069mDmchWUyM5xN58NJMXbBr0hpCbxCKmoBLyVgpW6vdhG NVzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PnonHOfUd7J5BegghP9WKivqK5C8xFSqYXKIXjWPbwc=; b=kqYcJK3J+rj8oLYf/cKLnHmaYV+5JoTSAXn7qvMjYjUD9QC9l27f1+qRig7GPxrT4/ VnYUc3wsGUWf+jaY4f28xuidqESpgvMU13YF5lsP5HtibCVOGsn7TyOK9XYjp18P18UH yZPvRw5YPcRRSCs8WKMD1MIZxYekpiEeMOOviz6lHd5ZxJ2CrHbpWEq68a10ZNkzrSg2 e+p+ckK06blvPFTu8I0mMV+0Z7mYgSEeYqZT277NKXt/BBPoSi0HW8XjpsPPs+SsYu63 3hjcIfF0nJ62t3COOD+SqE4fyUnVq6OFWAh5dq2891frhS2ImCf3Tc4vsBc/PpeRjH+x nfHw== X-Gm-Message-State: ALKqPwfjucYfy9NPb/0OQli2zlXKG7BhnYRRP6vySwvS7PQk3yzC79w6 KweB8dO4r2LFvfYOGnzi6euN90Sn7Zh9bpCzR43Qsg== X-Google-Smtp-Source: AB8JxZqSn1Sh4v4nfaNZyWgIQarrHAzbxZ2/3NRCnU4DstwnhjyayBJB6Yr3N/rIJ6CQyG1eWH2cq5x1QNjlOuRK8Vk= X-Received: by 2002:a81:9202:: with SMTP id j2-v6mr8003901ywg.214.1526456869401; Wed, 16 May 2018 00:47:49 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Wed, 16 May 2018 00:47:48 -0700 (PDT) In-Reply-To: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> From: Oliver Pinter Date: Wed, 16 May 2018 09:47:48 +0200 Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: Emeric POUPON Cc: freebsd-arch Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 07:47:50 -0000 On Wednesday, May 16, 2018, Emeric POUPON wrote: > Hello, > > Maybe I missed something, but I recently updated /usr/src (HEAD) and I > can't build the kernel anymore, I get this: > > # make -j4 buildkernel > --- buildkernel --- > make[1]: "/usr/src/Makefile.inc1" line 166: SYSTEM_COMPILER: Determined > that CC=cc matches the source tree. Not bootstrapping a cross-compiler. > --- buildkernel --- > > -------------------------------------------------------------- > >>> Kernel build for GENERIC started on Wed May 16 09:35:03 CEST 2018 > -------------------------------------------------------------- > ===> GENERIC > mkdir -p /usr/obj/usr/src/amd64.amd64/sys > -------------------------------------------------------------- > >>> stage 1: configuring the kernel > -------------------------------------------------------------- > cd /usr/src/sys/amd64/conf; PATH=/usr/obj/usr/src/amd64. > amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/ > tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/ > legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/ > obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin > config -d /usr/obj/usr/src/amd64.amd64/sys/GENERIC -I > '/usr/src/sys/amd64/conf' '/usr/src/sys/amd64/conf/GENERIC' > Kernel build directory is /usr/obj/usr/src/amd64.amd64/sys/GENERIC > Don't forget to do ``make cleandepend && make depend'' > -------------------------------------------------------------- > >>> stage 2.1: cleaning up the object tree > -------------------------------------------------------------- > cd /usr/obj/usr/src/amd64.amd64/sys/GENERIC; COMPILER_VERSION=60000 > COMPILER_FEATURES=" c++11 retpoline" COMPILER_TYPE=clang > COMPILER_FREEBSD_VERSION=1200014 MACHINE_ARCH=amd64 MACHINE=amd64 > CPUTYPE= CC="cc -target x86_64-unknown-freebsd12.0 > --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" > CXX="c++ -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CPP="cpp -target > x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" AS="as" AR="ar" LD="ld" > LLVM_LINK="" NM=nm OBJCOPY="objcopy" RANLIB=ranlib STRINGS= SIZE="size" > INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/amd64. > amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/ > tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/ > legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/ > obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin make > -j 4 - > J 15,16 -m /usr/src/share/mk KERNEL=kernel cleandir > make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel requires > linker ifunc support > *** [buildkernel] Error code 1 > > make[1]: stopped in /usr/src > 1 error > > > > How can I proceed? Please consult the ${srctop}/UPDATING file or search back on freebsd current mail list. Hint: buildworld before kernel > > Regards, > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-arch@freebsd.org Wed May 16 09:07:47 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EB94EB0973 for ; Wed, 16 May 2018 09:07:47 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 223937F368 for ; Wed, 16 May 2018 09:07:46 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id 608A23761972; Wed, 16 May 2018 11:07:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 5376B37617E4; Wed, 16 May 2018 11:07:35 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id oblofA5-q-Fn; Wed, 16 May 2018 11:07:35 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 416C137616A6; Wed, 16 May 2018 11:07:35 +0200 (CEST) Date: Wed, 16 May 2018 11:07:35 +0200 (CEST) From: Emeric POUPON To: Oliver Pinter Cc: freebsd-arch Message-ID: <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> In-Reply-To: References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Thread-Topic: Can't build kernel anymore: amd64 kernel requires linker ifunc support Thread-Index: NqTCxmbXDPOxDRoLzmlFCNy2O/hGNA== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 09:07:47 -0000 >> make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel requires >> linker ifunc support >> *** [buildkernel] Error code 1 >> >> make[1]: stopped in /usr/src >> 1 error >> >> >> >> How can I proceed? > > > Please consult the ${srctop}/UPDATING file or search back on freebsd > current mail list. > > Hint: buildworld before kernel > Thanks for your help. Actually, I already did all the steps described here: https://www.freebsd.org/doc/handbook/makeworld.html with success. After step 10, I now get this error. I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild everything with no luck. Regards, From owner-freebsd-arch@freebsd.org Wed May 16 09:20:51 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4E4BEB1368 for ; Wed, 16 May 2018 09:20:51 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 435227FC09 for ; Wed, 16 May 2018 09:20:51 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw0-x22f.google.com with SMTP id p144-v6so14752ywg.7 for ; Wed, 16 May 2018 02:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xwtvFmh+lJL9zifoD2uIHIH0LKdiW+RxLPq35wyBuXc=; b=1GS9m/WynKNm02gKRhsDG01FNqzPdCVHHzdtNsDg124NrX9oZYMvnBoTMk+LTxy8Vk QQgJZDIYhnu6cdfZQh6LKip/l3EYYlXyYn1FmoJaljrdVKQeneCdKRnDxCt8lCct2sc0 iPq36VmSl0Ub3mg6DpXjlOINjJIitCIHAgUtVvCQFIJuy383nq1Tulmb7myuIdZMGUhA OvcWaQ0iO8ilieG67HHVB5FvXAdZBShq6tnL4nzF6ealflOBknM4PekerKjIt4rBPlW6 1d33ZPEcwVkZrB4ES8k6WNLpFKfbm6ngppumVYSnyia9BVQ/RyMMgQ4zMDXnj9Z0wAAp +exA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xwtvFmh+lJL9zifoD2uIHIH0LKdiW+RxLPq35wyBuXc=; b=gbD2YuYz+TMgmM8HW882jVM6WyfZcu5xcMmVilSgMHMx3bJE2/e5d/JE5ZJFUkGfcm elQU+f4LCJ46Jszy4MZ8fpi/2Yif6sXfDE8gCKvTlQQ2C8YgRuBzdMcrR25JwOb7jo8p 03ZO3sdSzT9btG57sjp9QIrXCihMOn1UeIs1rYr0dyx8cvi4vlCAYo7WciPKR32V3Gxg dHphYeKP8k3HonIqOOXXffr4k9uH/PH4FtBE6misSodu0aRrDy8fcNHGm7Y3uHS77SnA bDT8pjvhEPlO+uIuov3QOSbJMnuAXFCw1Yx6go1WS9CfZAJe3zyUpP6Ay8a/waP8436q Im4Q== X-Gm-Message-State: ALKqPweK2sDmxjWdQF+Ftj4LqazFS9X9Wi1ipuF/hPCnR+/yT7PE5DsV m/3EWhbSlL97NxK4lFWXL8bw5pVxQJHswPOFDbHj6w== X-Google-Smtp-Source: AB8JxZrxzGlbU5jbVTNvOG7rrQtHMgIZrSGJTa7SZKl+kyqkia/IYfLHNc38vAVZA2p0t3Pkr2zzD/BXSyha3tZgDM0= X-Received: by 2002:a81:6905:: with SMTP id e5-v6mr20333ywc.265.1526462450704; Wed, 16 May 2018 02:20:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Wed, 16 May 2018 02:20:50 -0700 (PDT) In-Reply-To: <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> From: Oliver Pinter Date: Wed, 16 May 2018 11:20:50 +0200 Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: Emeric POUPON Cc: freebsd-arch Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 09:20:51 -0000 On Wednesday, May 16, 2018, Emeric POUPON wrote: > > >> make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > requires > >> linker ifunc support > >> *** [buildkernel] Error code 1 > >> > >> make[1]: stopped in /usr/src > >> 1 error > >> > >> > >> > >> How can I proceed? > > > > > > Please consult the ${srctop}/UPDATING file or search back on freebsd > > current mail list. > > > > Hint: buildworld before kernel > > > > Thanks for your help. > > Actually, I already did all the steps described here: > https://www.freebsd.org/doc/handbook/makeworld.html with success. > After step 10, I now get this error. > I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild > everything with no luck. > > Please remove this line from your src.conf, lld is required for building kernel since the ifunc support. > Regards, > > > From owner-freebsd-arch@freebsd.org Wed May 16 09:42:45 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0AEAEC8633 for ; Wed, 16 May 2018 09:42:45 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C8E780A85 for ; Wed, 16 May 2018 09:42:45 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id D2B8437617D2; Wed, 16 May 2018 11:42:33 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id C47453761A60; Wed, 16 May 2018 11:42:33 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id v7EwV5Wmn_qs; Wed, 16 May 2018 11:42:33 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id B2DF337617D2; Wed, 16 May 2018 11:42:33 +0200 (CEST) Date: Wed, 16 May 2018 11:42:33 +0200 (CEST) From: Emeric POUPON To: Oliver Pinter Cc: freebsd-arch Message-ID: <470629758.12930429.1526463753682.JavaMail.zimbra@stormshield.eu> In-Reply-To: References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Thread-Topic: Can't build kernel anymore: amd64 kernel requires linker ifunc support Thread-Index: IyRCX0WRWJnqum4mSdEFh56iQEBkXw== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 09:42:45 -0000 >> Thanks for your help. >> >> Actually, I already did all the steps described here: >> https://www.freebsd.org/doc/handbook/makeworld.html with success. >> After step 10, I now get this error. >> I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild >> everything with no luck. >> >> > Please remove this line from your src.conf, lld is required for building > kernel since the ifunc support. > I already did all the steps of the handbook without this line, and I finally had the issue I described. What I told is that adding this line + make buildworld does not solve the kernel building issue. From owner-freebsd-arch@freebsd.org Wed May 16 09:49:26 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1B26EC8AFE for ; Wed, 16 May 2018 09:49:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 405DA80D02 for ; Wed, 16 May 2018 09:49:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3C89C26011B; Wed, 16 May 2018 11:49:24 +0200 (CEST) Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: Emeric POUPON , Oliver Pinter Cc: freebsd-arch References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> <470629758.12930429.1526463753682.JavaMail.zimbra@stormshield.eu> From: Hans Petter Selasky Message-ID: <115a98db-8cb0-93e9-8f4f-1080ea79ae73@selasky.org> Date: Wed, 16 May 2018 11:49:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <470629758.12930429.1526463753682.JavaMail.zimbra@stormshield.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 09:49:26 -0000 On 05/16/18 11:42, Emeric POUPON wrote: > >>> Thanks for your help. >>> >>> Actually, I already did all the steps described here: >>> https://www.freebsd.org/doc/handbook/makeworld.html with success. >>> After step 10, I now get this error. >>> I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild >>> everything with no luck. >>> >>> >> Please remove this line from your src.conf, lld is required for building >> kernel since the ifunc support. >> > > I already did all the steps of the handbook without this line, and I finally had the issue I described. > What I told is that adding this line + make buildworld does not solve the kernel building issue. Try adding: -m $PWD/share/mk After make. Not sure if it helps. --HPS From owner-freebsd-arch@freebsd.org Wed May 16 13:22:44 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0CFAEE203E for ; Wed, 16 May 2018 13:22:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AD50685B4 for ; Wed, 16 May 2018 13:22:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x244.google.com with SMTP id e20-v6so1822285itc.1 for ; Wed, 16 May 2018 06:22:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mKtu5V9L+q7BYS918pxZK49MvEJQi52WUb8H3a8lKN4=; b=J8IG52s9j7RludQicDf6tvBIP3FRrIVKbBjQBZ1vg7pe3SjMrRFvzKGvkuLV/10/fd yxPjDXoQyQHmvCvK3aC5Mckdx1cY/vYqvRWIQE03eGxrbAAzoaUKBS1a3CNgXI0xJ1Kn APYwlPebvdKIbagJ0dmk7wZanBAHZqlQucJ/ZQVD0e03X+x0MTzYd/cd6jns37BW/IKz 3WB4uZ2vwyqJVaxnVKDy9bPLtsMgmok2nKxRSjKYstvkLB+qXsY63Vu7obNGMtvo0oeF Ybf4RhDufK8Y9+Bs3rxmjswJxfcPZTHnvcTGhWL5Pl64M7fN+wggaw5L3tcV15io//7q 98RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=mKtu5V9L+q7BYS918pxZK49MvEJQi52WUb8H3a8lKN4=; b=cNXwSmYVU7nKbkecVNJeIxk5Rtooex8RvEi23cHtoT06h5noMPOl8fc4bmGtkrOkZl rvbHc8haZTdeO7QBwPA+pZuUGChxAeaJQuDa1/TtzF0gatVwXal9sy0wD3iNDx6GEHMm Ju8tC3O/AEXsHgBq8H/ScoSWag2p+soPZVXBhhlM7c5qX8DR34sgqJmAVDQb+VC6MMGX yHEFdcJF0MPcVEByjQmdnI1MlzqSYQbLeZunpv0PWEBfXqX0mosWJRg2P6HN+UE0X+Od r1ovhgnZUFBI7z9Pfaa6dQ2S7QteDHhPCmygMiXggk0iRBa/8w1XprK3NTOcIXg5pmNm L1ng== X-Gm-Message-State: ALKqPwfespK+aT0KQ/+H6Q4RIIDN2C0K5H+nsHODCMioqQiokwxFuuII Q2uThqLf2Y+kPh6kl2gpNk/JtHkrSuUi4X8GjqKbWw== X-Google-Smtp-Source: AB8JxZr+70CgPj/5H+LQc0fS1MwjL5UI4h1dwsaBBsuKaD7sfmFcIGkpND4LcLlRFmFH2FNcUOA9LHpYxhI9KCgT4Yo= X-Received: by 2002:a6b:3846:: with SMTP id f67-v6mr955091ioa.117.1526476963350; Wed, 16 May 2018 06:22:43 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Wed, 16 May 2018 06:22:42 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <115a98db-8cb0-93e9-8f4f-1080ea79ae73@selasky.org> References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> <470629758.12930429.1526463753682.JavaMail.zimbra@stormshield.eu> <115a98db-8cb0-93e9-8f4f-1080ea79ae73@selasky.org> From: Warner Losh Date: Wed, 16 May 2018 07:22:42 -0600 X-Google-Sender-Auth: f6xbgUiPJFs3jYYLIbr86xcwXXY Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: Hans Petter Selasky Cc: Emeric POUPON , Oliver Pinter , freebsd-arch Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 13:22:44 -0000 On Wed, May 16, 2018 at 3:49 AM, Hans Petter Selasky wrote: > On 05/16/18 11:42, Emeric POUPON wrote: > >> >> Thanks for your help. >>>> >>>> Actually, I already did all the steps described here: >>>> https://www.freebsd.org/doc/handbook/makeworld.html with success. >>>> After step 10, I now get this error. >>>> I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild >>>> everything with no luck. >>>> >>>> >>>> Please remove this line from your src.conf, lld is required for building >>> kernel since the ifunc support. >>> >>> >> I already did all the steps of the handbook without this line, and I >> finally had the issue I described. >> What I told is that adding this line + make buildworld does not solve the >> kernel building issue. >> > > Try adding: > > -m $PWD/share/mk > > After make. > > Not sure if it helps. LD=ld.lld make is the magic here. The kernel needs a new linker to properly link in the ifunc, and that's not our ancient ld. lld does it, as does the latter-day binutils. Warner From owner-freebsd-arch@freebsd.org Wed May 16 13:43:22 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DB6CEE33AB for ; Wed, 16 May 2018 13:43:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C1E6E69509 for ; Wed, 16 May 2018 13:43:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x243.google.com with SMTP id p3-v6so1971859itc.0 for ; Wed, 16 May 2018 06:43:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lOkfg4sTz/GWj/GhcIOzyqmVV3jdU85rN2I34dL2Pgg=; b=URFxnAbxS3ShaICEvw8oNosHoxxv7UjMXhAHrpzXd32rwaae6Wp721zs5JsLHYOrgj h92AJMhfoG5TwoFNQ0K0Ylcvh3gEOL3rlSyvJOPr0CSrwAEq4qgaOnZvUEZiXDZLNGbB 3nP59g7avX+Vl2rZ8T9JutCbLRBtX4fsQnS1wA27KKPTpwVM0dLb9gG+u7mVjeAOFihs dhU5k+BTstGYs+F86s9jD3lho6EhKvyyqRCVTPgTMjizckOXLwq2COjF2ES3PeBK5Qyr 0FVM7ri70uE9jRa+J2deDzNUIHqyaZnH4DdA0088SwAp+MOqNXZSQLvqN/sRhUuFoJsF F7Sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lOkfg4sTz/GWj/GhcIOzyqmVV3jdU85rN2I34dL2Pgg=; b=a+fLefkoGOgwkypKrTuhg8X0j7epTXe5Uyd7TVTWJTmBV05R7eGWKLVvMT7gzP0dQI qDPaSfVZfDBUgorvxbfvuS/mEEZPkAvklYjhMMi6ht3MGd6aneEG4CN+jjbe2Z7c6gWn QJH4xj31rSUwGFWSyLhU+vuEyTlAIM3uVM4pmAOMeRRX7S+W9KCopuMuXCOgyR3OSNEO i3t3Cncwp3mI0JAkiM93GZXVyW+JrOOlit2nqgEdb69xziCX2r5uhCfYTcg+j0onPI2s R8hJNaYhgcCLfJYbT2sFuB+QCm0T1AILso78L9VzO7DHstaXaEQ929ijJkkUI0PjSIaR 9rTg== X-Gm-Message-State: ALKqPwfuoUCzTBAXHKukMuov33hMvr4Li8vKcjAzov82j7kuVOQo0scj EC4hRo2uzyCjj32ms+62ugoqobON/1yHIDgKx6vMjQ== X-Google-Smtp-Source: AB8JxZqd7dQiZiNAPviP0numtOGUsj+L6GeEWI5qbr5UmshCiEfZSp8O9BT6R+Qf7OUxqViKrRmN2aCXcb2H73fSnGY= X-Received: by 2002:a6b:be01:: with SMTP id o1-v6mr989880iof.299.1526478200853; Wed, 16 May 2018 06:43:20 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Wed, 16 May 2018 06:43:18 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <201805161335.w4GDZvSM000645@pdx.rh.CN85.dnsmgr.net> References: <201805161335.w4GDZvSM000645@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 16 May 2018 07:43:18 -0600 X-Google-Sender-Auth: JtiirrviErtNqkGMIx0bHqxZtFE Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: "Rodney W. Grimes" Cc: Hans Petter Selasky , Emeric POUPON , Oliver Pinter , freebsd-arch Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 13:43:22 -0000 On Wed, May 16, 2018 at 7:35 AM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > On Wed, May 16, 2018 at 3:49 AM, Hans Petter Selasky > > wrote: > > > > > On 05/16/18 11:42, Emeric POUPON wrote: > > > > > >> > > >> Thanks for your help. > > >>>> > > >>>> Actually, I already did all the steps described here: > > >>>> https://www.freebsd.org/doc/handbook/makeworld.html with success. > > >>>> After step 10, I now get this error. > > >>>> I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild > > >>>> everything with no luck. > > >>>> > > >>>> > > >>>> Please remove this line from your src.conf, lld is required for > building > > >>> kernel since the ifunc support. > > >>> > > >>> > > >> I already did all the steps of the handbook without this line, and I > > >> finally had the issue I described. > > >> What I told is that adding this line + make buildworld does not solve > the > > >> kernel building issue. > > >> > > > > > > Try adding: > > > > > > -m $PWD/share/mk > > > > > > After make. > > > > > > Not sure if it helps. > > > > > > LD=ld.lld make > > > > is the magic here. The kernel needs a new linker to properly link in the > > ifunc, and that's not our ancient ld. lld does it, as does the latter-day > > binutils. > > Since this now seems to be a mandatory thing to get a kernel built > can it please be set in the Makefile that is needing it? > No. It's a transient requirement that will be gone shortly when Ed does the next step of lld integration. Wanrer From owner-freebsd-arch@freebsd.org Wed May 16 14:04:35 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9D88EE476E for ; Wed, 16 May 2018 14:04:35 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 1F3476A4E6 for ; Wed, 16 May 2018 14:04:34 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w4GDZvSq000646; Wed, 16 May 2018 06:35:57 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w4GDZvSM000645; Wed, 16 May 2018 06:35:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805161335.w4GDZvSM000645@pdx.rh.CN85.dnsmgr.net> Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support In-Reply-To: To: Warner Losh Date: Wed, 16 May 2018 06:35:57 -0700 (PDT) CC: Hans Petter Selasky , Emeric POUPON , Oliver Pinter , freebsd-arch X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 14:04:35 -0000 > On Wed, May 16, 2018 at 3:49 AM, Hans Petter Selasky > wrote: > > > On 05/16/18 11:42, Emeric POUPON wrote: > > > >> > >> Thanks for your help. > >>>> > >>>> Actually, I already did all the steps described here: > >>>> https://www.freebsd.org/doc/handbook/makeworld.html with success. > >>>> After step 10, I now get this error. > >>>> I tried to put WITHOUT_LLD_BOOTSTRAP=yes in /etc/src.conf + rebuild > >>>> everything with no luck. > >>>> > >>>> > >>>> Please remove this line from your src.conf, lld is required for building > >>> kernel since the ifunc support. > >>> > >>> > >> I already did all the steps of the handbook without this line, and I > >> finally had the issue I described. > >> What I told is that adding this line + make buildworld does not solve the > >> kernel building issue. > >> > > > > Try adding: > > > > -m $PWD/share/mk > > > > After make. > > > > Not sure if it helps. > > > LD=ld.lld make > > is the magic here. The kernel needs a new linker to properly link in the > ifunc, and that's not our ancient ld. lld does it, as does the latter-day > binutils. Since this now seems to be a mandatory thing to get a kernel built can it please be set in the Makefile that is needing it? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arch@freebsd.org Wed May 16 14:43:30 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77A8DEE6925 for ; Wed, 16 May 2018 14:43:30 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF8DC6BF20 for ; Wed, 16 May 2018 14:43:29 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x244.google.com with SMTP id p3-v6so2519971itc.0 for ; Wed, 16 May 2018 07:43:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=PqCi5wUTVLr1V4Jq5MrGxK+891zSeqOJjxHuOLV2y4U=; b=SDvx6lA1Xry1i+irhc6hastjn2glME50Y+ANOOyGR7Nuw58lEj37GKIdKIJU3Uhoo2 eI1FF6IWhlrFw8yf8/OVYY/wybIRF6c4qH1flyvrq395vgNrx5oxg0wZA2H7w4fbKB/x 7NoSsqEeW8Pfg6kN3X+qTUEjtVJ04HKoLN74hkehGxddq450WwdSx3zQwVnyx8VGj0Z6 fv3cLqEfZG5U7vwWxj4M/Z2Umq1vHF9dcW7eKo9hj8qkHEE0KdhwTWRG83f3Oc4hxY3c dmwOvlzLdYf890G9NL/3Yy2SeKvQLKFlQeWLyUdO6d9Z21KhmfgrctcR+OZ+EFQrtvKU d6GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=PqCi5wUTVLr1V4Jq5MrGxK+891zSeqOJjxHuOLV2y4U=; b=GteM0z9zyG7AhcG7dLj0yyVxHXcLLmbSGtsa4SyhKf5P0Eo09+p/nngpOh2pOBoQuV U2Fxu+T2sjQlI68tbUak/V0EaNQuReWiJKgBs0typQjOu0P2ti4xBYDUaMRnqBqo6PZy bFVWx0dA/Yha8L/9/H/x/fNqBYhuUNvMAYqrhqJwav76chkjaGlnMer312viaDRjhd6V jcqMpaKxO6u7YcuW37G5plqTLP0mmnesUwQiFpEHYHi6MILETbTMTwpxUdWuS3WbQhto +lQQBdUyUTT++s7ZqFIrwve3F5hVN5MoyyqPGO8RxL2CewL2m84TF4FO3UFHFT5FrBfO y5gQ== X-Gm-Message-State: ALKqPwf1IpsbmLjKh4UhkeSysbjSZFXI4E9eaacRMAc/Jx5gKNiZlvcM lv1/op/ZB63dV6MItYfkB77cDIRNqRIAcflibDQ= X-Google-Smtp-Source: AB8JxZqMLxStxHeyl8U21ovk0BCPoOBX2qmnXu766P1o3NUzu4fVRhJdZ/nbo+8hws0zGpk9fdvrMtjs4Puf6B1OxtQ= X-Received: by 2002:a24:2fce:: with SMTP id j197-v6mr1210108itj.52.1526481809296; Wed, 16 May 2018 07:43:29 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.167 with HTTP; Wed, 16 May 2018 07:43:08 -0700 (PDT) In-Reply-To: <201805161335.w4GDZvSM000645@pdx.rh.CN85.dnsmgr.net> References: <201805161335.w4GDZvSM000645@pdx.rh.CN85.dnsmgr.net> From: Ed Maste Date: Wed, 16 May 2018 10:43:08 -0400 X-Google-Sender-Auth: CYjEZzu1E9zDtAh9OTwxzQKSyCM Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: "Rodney W. Grimes" Cc: Warner Losh , Hans Petter Selasky , Emeric POUPON , Oliver Pinter , freebsd-arch Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 14:43:30 -0000 On 16 May 2018 at 09:35, Rodney W. Grimes wrote: >> >> LD=ld.lld make >> >> is the magic here. The kernel needs a new linker to properly link in the >> ifunc, and that's not our ancient ld. lld does it, as does the latter-day >> binutils. > > Since this now seems to be a mandatory thing to get a kernel built > can it please be set in the Makefile that is needing it? It's already handled by the Makefile that needs it when using the normal build process - i.e., "make buildworld buildkernel" (or toolchain or kernel-toolchain followed by buildkernel). The failure arises when building a kernel the "old" way, using config and then and make in the kernel directory. This inherently uses the host's linker (/usr/bin/ld), which is too old to link the kernel. We can't just add LD=ld.lld to the kernel's Makefile(s), because it would break external toolchain and other cases where users use a specific linker. I hope to introduce a KERNEL_LD Make variable that controls the linker used for the kernel link, but it's more involved than a one or two line change for the same reason that we can't just set LD=ld.lld. ld.lld will start being installed as /usr/bin/ld once these two issues are resolved: pr227968 [exp-run] Update lang/ghc to 8.4.2, devel/stack to 1.7.1, and all the */hs-* ports pr214864 [exp-run] test build with lld as /usr/bin/ld The exp-run for the first is complete and I believe we are now just waiting on the change to be committed. As soon as that happens I will ask for another exp-run for the second PR, and will commit the change to install lld by default as soon as it completes (assuming successfully). From owner-freebsd-arch@freebsd.org Wed May 16 15:11:15 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA8F1EE7B35 for ; Wed, 16 May 2018 15:11:15 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 F34DC6CCA1; Wed, 16 May 2018 15:11:14 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w4GFBCEo001109; Wed, 16 May 2018 08:11:12 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w4GFBCTQ001108; Wed, 16 May 2018 08:11:12 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805161511.w4GFBCTQ001108@pdx.rh.CN85.dnsmgr.net> Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support In-Reply-To: To: Ed Maste Date: Wed, 16 May 2018 08:11:12 -0700 (PDT) CC: Hans Petter Selasky , Emeric POUPON , Oliver Pinter , freebsd-arch X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 15:11:16 -0000 > On 16 May 2018 at 09:35, Rodney W. Grimes > wrote: > >> > >> LD=ld.lld make > >> > >> is the magic here. The kernel needs a new linker to properly link in the > >> ifunc, and that's not our ancient ld. lld does it, as does the latter-day > >> binutils. > > > > Since this now seems to be a mandatory thing to get a kernel built > > can it please be set in the Makefile that is needing it? > > It's already handled by the Makefile that needs it when using the > normal build process - i.e., "make buildworld buildkernel" (or > toolchain or kernel-toolchain followed by buildkernel). > > The failure arises when building a kernel the "old" way, using config > and then and make in the kernel directory. This inherently uses the > host's linker (/usr/bin/ld), which is too old to link the kernel. We > can't just add LD=ld.lld to the kernel's Makefile(s), because it would > break external toolchain and other cases where users use a specific > linker. I hope to introduce a KERNEL_LD Make variable that controls > the linker used for the kernel link, but it's more involved than a one > or two line change for the same reason that we can't just set > LD=ld.lld. > > ld.lld will start being installed as /usr/bin/ld once these two issues > are resolved: ... In the meantime what about reverting the ifunc usage until this can be done? > > pr227968 [exp-run] Update lang/ghc to 8.4.2, devel/stack to 1.7.1, and > all the */hs-* ports > pr214864 [exp-run] test build with lld as /usr/bin/ld > > The exp-run for the first is complete and I believe we are now just > waiting on the change to be committed. As soon as that happens I will > ask for another exp-run for the second PR, and will commit the change > to install lld by default as soon as it completes (assuming > successfully). > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arch@freebsd.org Wed May 16 19:34:36 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAC47EACD01 for ; Wed, 16 May 2018 19:34:35 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw0-x242.google.com (mail-yw0-x242.google.com [IPv6:2607:f8b0:4002:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F87877DC9 for ; Wed, 16 May 2018 19:34:35 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw0-x242.google.com with SMTP id v132-v6so600678ywc.6 for ; Wed, 16 May 2018 12:34:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DRDCBX/Tn112poE3dhv/4Ec7pDA+st7JEnuWpGF2lD4=; b=O0eFwd+olMM99uWaJVlbLk+SDOrSntKjBLKeGV1WNVOi+2xOvvkrcV94GviR9kEAii MlW0A5o6fGv2g+HzucqkuIA8uE1PvO7WEPjILyWgPfvmqUbDs78rcYn8yINHiHKXMdeg 5dFAuUqWaqbg4Qn8x7EDZD+1cTvGmX4VSSSSYMWDL7PWvkHKPLKUrUxSwVYC6yeadqaQ CVekVXoHh8GfMGrieYGq98MAelMXt+ZVkbqYCiXwTB7Bl/bj8NWSLfYv1G7SqSlgGQzv 5IoB2JSet8ND84JBRgbN8xHY34/5L+8oXPRvQ5U7MjBR/mMRucn2drdZbUDYTCohCpZW V1Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DRDCBX/Tn112poE3dhv/4Ec7pDA+st7JEnuWpGF2lD4=; b=mjtjcja7kyhigj/njJoEU7qBbigYDGGZ4TN4BOhpOC7RXyOSxuU5Smfy9pK1ztBHZD 45Tty36eoOFcRGkiTu2jPBlqDV5zmWQXJS57Rpmt4xbWgYMDFv8SPnn6qSdDp+VJuomx 9HYTEjp3075+jtHwb0mTxZPLpQh9KgqeHU8eyf0CKO12XFcMZaQijBlxIJSPkpV2DlkQ gnKxMK8hclfT+RMKvGY516x45S7Qgfb7nX7L2/I6yIZ6Ha6mc2f4hAGrXso1kj17d7C3 EltKTfLJCvzcJD3roYrcZPF/9EzK0zoWzBYFV94B2x6CJwcbwHnA8/QuxkRnYePb3NcF GvOA== X-Gm-Message-State: ALKqPwctSaTC5IvERWj7fETnpbIhEugK2EFrNwYjcxMxgYMqJhtPhZ1i uedNWdsSLOlWebbYGTEgw74YDTRsEvQ6I2lWcZkV6A== X-Google-Smtp-Source: AB8JxZqV1D+gIBTUMVxK2DtbTYoiHJiJxajfDFgOq21K+/lpRwVg9PUbJpcmphpbk+MoJ00cLtq1Ih5til3IWWeFjc0= X-Received: by 2002:a81:ad05:: with SMTP id l5-v6mr1180177ywh.382.1526499274626; Wed, 16 May 2018 12:34:34 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Wed, 16 May 2018 12:34:33 -0700 (PDT) In-Reply-To: <201805161511.w4GFBCTQ001108@pdx.rh.CN85.dnsmgr.net> References: <201805161511.w4GFBCTQ001108@pdx.rh.CN85.dnsmgr.net> From: Oliver Pinter Date: Wed, 16 May 2018 21:34:33 +0200 Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: "Rodney W. Grimes" Cc: Ed Maste , Hans Petter Selasky , Emeric POUPON , freebsd-arch Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 19:34:36 -0000 On 5/16/18, Rodney W. Grimes wrote: >> On 16 May 2018 at 09:35, Rodney W. Grimes >> wrote: >> >> >> >> LD=ld.lld make >> >> >> >> is the magic here. The kernel needs a new linker to properly link in >> >> the >> >> ifunc, and that's not our ancient ld. lld does it, as does the >> >> latter-day >> >> binutils. >> > >> > Since this now seems to be a mandatory thing to get a kernel built >> > can it please be set in the Makefile that is needing it? >> >> It's already handled by the Makefile that needs it when using the >> normal build process - i.e., "make buildworld buildkernel" (or >> toolchain or kernel-toolchain followed by buildkernel). >> >> The failure arises when building a kernel the "old" way, using config >> and then and make in the kernel directory. This inherently uses the >> host's linker (/usr/bin/ld), which is too old to link the kernel. We >> can't just add LD=ld.lld to the kernel's Makefile(s), because it would >> break external toolchain and other cases where users use a specific >> linker. I hope to introduce a KERNEL_LD Make variable that controls >> the linker used for the kernel link, but it's more involved than a one >> or two line change for the same reason that we can't just set >> LD=ld.lld. >> >> ld.lld will start being installed as /usr/bin/ld once these two issues >> are resolved: > ... > > In the meantime what about reverting the ifunc usage until this > can be done? Nope. If somebody take trouble over compiling their kernel manually, then at least read the documentation, how to compile their system in the new way. We talking about 12-CURRENT and not about 1X-STABLE branches.... > >> >> pr227968 [exp-run] Update lang/ghc to 8.4.2, devel/stack to 1.7.1, and >> all the */hs-* ports >> pr214864 [exp-run] test build with lld as /usr/bin/ld >> >> The exp-run for the first is complete and I believe we are now just >> waiting on the change to be committed. As soon as that happens I will >> ask for another exp-run for the second PR, and will commit the change >> to install lld by default as soon as it completes (assuming >> successfully). >> _______________________________________________ >> freebsd-arch@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arch >> To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >> > > -- > Rod Grimes > rgrimes@freebsd.org > From owner-freebsd-arch@freebsd.org Wed May 16 19:46:45 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE3D1EAD802 for ; Wed, 16 May 2018 19:46:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B9F9786EA for ; Wed, 16 May 2018 19:46:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x243.google.com with SMTP id q72-v6so5132811itc.0 for ; Wed, 16 May 2018 12:46:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vDwiEa3erh+qYx4dI7AnGCg4pY68zoZOolZDp7KTApQ=; b=C9UT5b2n4GknHrU7HBNS3BhWHizAwfC4m1jijFnH8H6GvoKhsX4j66oclox4n0ZFci UsDA7rFToXq6dKbAMGB+w9gHEBSNqELgWfZIrqu81oq48frFV/L3zJ8aDM6T6zzpiVgY X4DhGjhA/N2eoTLnUodCCi3i5a05k2EmSUGNFAGrRyYFAYON6/LPDN7PRitcj3rDhpxX taDa7vh8LKqvCcIJ52+ZMJ/zDefT4BEgkcyhh0JTI0u21dzjt4CG79hn+RQv59ybSEy4 Tl9gD6/pkn/Se4VeEG6nlGMZCZgwWm6F+ejb9oJbQ+CkYHXDaMCDKAad7YcsGtOfwYOS cjhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vDwiEa3erh+qYx4dI7AnGCg4pY68zoZOolZDp7KTApQ=; b=JwnTM8prKJbwLw4JLpYfMakNhf5wU4/QlkMcokb9lo2gxPR65VQCisdB8buHH385EK xS0Nwo5n6XSf1XSCu6l9rNY9q4bFwTe7qL+iaf1UYzc1OGgVfyhH4dyEMASM4fRWGHEL eCKmQe88qYn1OGdQy0RXvWGnib3O/1xwflDkFQPv43a0xMKzjIrmJH4UyBf7CbmrEN8R OmQVXeSOuXQzthxdGrlX+p7bZas61PVPgzs6/EsMKohXEXQK8qVxNO7D/YEORLlUvoGx 437FFb8ck+PWdeDQN7O5AeWSwzESPsZ1g+Vpxs+QwbVg390d3YN9kZN8g0H3kSP7P+q5 jUfQ== X-Gm-Message-State: ALKqPwdf6ubjYItTJRgVmKmTcrSpfRkC+0mJwJZYNmp+bfTiXP9ZPpQg 0AsrJlhotDHgj3DCMHA1vjvbX2FRoCdzpv87AHDk2w== X-Google-Smtp-Source: AB8JxZq69fKcOBpVo3xYbcQWZJFbVnMve7K8VoYJF6VO8TifC2VxIjm5KjVia/T7tnHbCh1RtGBbJR39s23lQBo9Tew= X-Received: by 2002:a24:6ec1:: with SMTP id w184-v6mr2432428itc.57.1526500003673; Wed, 16 May 2018 12:46:43 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Wed, 16 May 2018 12:46:43 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <201805161511.w4GFBCTQ001108@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 16 May 2018 13:46:43 -0600 X-Google-Sender-Auth: E2AW-j2llxpOhUo5aHD043lhIuk Message-ID: Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support To: Oliver Pinter Cc: "Rodney W. Grimes" , Hans Petter Selasky , Emeric POUPON , Ed Maste , freebsd-arch Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 19:46:45 -0000 On Wed, May 16, 2018 at 1:34 PM, Oliver Pinter < oliver.pinter@hardenedbsd.org> wrote: > On 5/16/18, Rodney W. Grimes wrote: > >> On 16 May 2018 at 09:35, Rodney W. Grimes > >> wrote: > >> >> > >> >> LD=ld.lld make > >> >> > >> >> is the magic here. The kernel needs a new linker to properly link in > >> >> the > >> >> ifunc, and that's not our ancient ld. lld does it, as does the > >> >> latter-day > >> >> binutils. > >> > > >> > Since this now seems to be a mandatory thing to get a kernel built > >> > can it please be set in the Makefile that is needing it? > >> > >> It's already handled by the Makefile that needs it when using the > >> normal build process - i.e., "make buildworld buildkernel" (or > >> toolchain or kernel-toolchain followed by buildkernel). > >> > >> The failure arises when building a kernel the "old" way, using config > >> and then and make in the kernel directory. This inherently uses the > >> host's linker (/usr/bin/ld), which is too old to link the kernel. We > >> can't just add LD=ld.lld to the kernel's Makefile(s), because it would > >> break external toolchain and other cases where users use a specific > >> linker. I hope to introduce a KERNEL_LD Make variable that controls > >> the linker used for the kernel link, but it's more involved than a one > >> or two line change for the same reason that we can't just set > >> LD=ld.lld. > >> > >> ld.lld will start being installed as /usr/bin/ld once these two issues > >> are resolved: > > ... > > > > In the meantime what about reverting the ifunc usage until this > > can be done? > > Nope. If somebody take trouble over compiling their kernel manually, > then at least > read the documentation, how to compile their system in the new way. > We talking about 12-CURRENT and not about 1X-STABLE branches.... IMHO, this is an acceptable breakage for -current. This is on the 'experts only' path and there's a note in UPDATING to cope. We don't intend to keep it that way forever, and the benefit of getting useful testing from a wider audience in this case, imho, out weights the minor inconvenience for the small minority of users that go old-school. Warner From owner-freebsd-arch@freebsd.org Thu May 17 00:26:18 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E087EE079A for ; Thu, 17 May 2018 00:26:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3C15385F68 for ; Thu, 17 May 2018 00:26:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id F3E03EE0793; Thu, 17 May 2018 00:26:17 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E11C1EE0792 for ; Thu, 17 May 2018 00:26:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 952D785F66; Thu, 17 May 2018 00:26:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 58AC9D10F; Thu, 17 May 2018 00:26:17 +0000 (UTC) (envelope-from jhb@freebsd.org) From: John Baldwin To: Brooks Davis Cc: Bruce Evans , arch@freebsd.org Subject: Re: LIBC_SCCS Date: Wed, 16 May 2018 14:00:54 -0700 Message-ID: <6859500.cJmFvTkEvq@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180501215303.GA4870@spindle.one-eyed-alien.net> References: <1711113.VelFtdTVS7@ralph.baldwin.cx> <20180428110152.Q4737@besplex.bde.org> <20180501215303.GA4870@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 00:26:18 -0000 On Tuesday, May 01, 2018 09:53:03 PM Brooks Davis wrote: > On Sat, Apr 28, 2018 at 11:39:02AM +1000, Bruce Evans wrote: > > On Fri, 27 Apr 2018, John Baldwin wrote: > > > > > I suspect no one cares, but for whatever reason our current handling of the > > > LIBC_SCCS macro in some of our libraries annoys me. In theory it seems like > > > LIBC_SCCS's purpose is to control whether or not old SCCS IDs from Berkeley > > > are included in libc's sources when libc is built. (Similar to how macros > > > control the behavior of __FBSDID().) However, we use an odd construct in > > > the tree. First, we define LIBC_SCCS by default in the CFLAGS of various > > > libraries (libkvm, libutil, libthr, libc, etc.) which in theory would enable > > > the IDs, but then we explicitly wrap them in #if 0, e.g.: > > > > > > #if defined(LIBC_SCCS) && !defined(lint) > > > #if 0 > > > static char sccsid[] = "@(#)kvm_hp300.c 8.1 (Berkeley) 6/4/93"; > > > #endif > > > #endif /* LIBC_SCCS and not lint */ > > > > Most aren't actually wrapped with '#if 0'. E.g., in libc/*/*.c there are > > 839 files but only 47 of these have any '#if 0' at all. SO this can be > > fixed without much churn. > > > > I thought there is a problem with the above not actually compiling if > > LIBC_SCCS is defined, but WARNS is only 2 for libc and it takes WARNS >= 4 > > to give -Wwrite-strings. > > At higher WARNS levels the ones without #if 0 also warn about unused > static variable. If we're going to keep them, using an __FBSDID()-like > macro seems like the best option so that's easy to make correct and > doesn't require churn if compilers change. I have a review for libkvm (which has many smaller examples than libc) at https://reviews.freebsd.org/D15459 for any folks who are interested. It uses __SCCSID() but then disables them by default via -DNO__SCCSID. -- John Baldwin From owner-freebsd-arch@freebsd.org Thu May 17 12:11:29 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC7CFEED76D for ; Thu, 17 May 2018 12:11:29 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B4AE7CB8C for ; Thu, 17 May 2018 12:11:28 +0000 (UTC) (envelope-from emeric.poupon@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id 3B14B3761BF7; Thu, 17 May 2018 14:11:11 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 2BF983760ED6; Thu, 17 May 2018 14:11:11 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id iZBFhZuSltLx; Thu, 17 May 2018 14:11:11 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 1639B3761BF5; Thu, 17 May 2018 14:11:11 +0200 (CEST) Date: Thu, 17 May 2018 14:11:11 +0200 (CEST) From: Emeric POUPON To: Warner Losh Cc: Hans Petter Selasky , Oliver Pinter , freebsd-arch Message-ID: <10524809.13188920.1526559071011.JavaMail.zimbra@stormshield.eu> In-Reply-To: References: <1427128516.12874490.1526456240718.JavaMail.zimbra@stormshield.eu> <793855837.12916849.1526461655128.JavaMail.zimbra@stormshield.eu> <470629758.12930429.1526463753682.JavaMail.zimbra@stormshield.eu> <115a98db-8cb0-93e9-8f4f-1080ea79ae73@selasky.org> Subject: Re: Can't build kernel anymore: amd64 kernel requires linker ifunc support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Thread-Topic: Can't build kernel anymore: amd64 kernel requires linker ifunc support Thread-Index: EctCxxdm+R151BiKgORSNNRTpt3+Pw== X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 12:11:29 -0000 > LD=ld.lld make > > is the magic here. The kernel needs a new linker to properly link in the > ifunc, and that's not our ancient ld. lld does it, as does the latter-day > binutils. > > Warner Thanks a lot, that works fine! Emeric From owner-freebsd-arch@freebsd.org Thu May 17 17:24:19 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD307EDA0F8 for ; Thu, 17 May 2018 17:24:19 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 403076B842 for ; Thu, 17 May 2018 17:24:19 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pg0-x241.google.com with SMTP id c22-v6so1444253pgn.11 for ; Thu, 17 May 2018 10:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=fHvt62qYmeCedNbXSiHUBRPPpLXGyznUpBsDUEqZye8=; b=nLYO+TPN6oS1JC2eCdFSuKDYBtcXULYf3RTZhnNejPczGAEmIs0b3z50iF4XxI0uYH 5FJ4shhS36sbKQyP1YtCi1TaPPDxJ9dzRVKDWK0ikTgJuEJLcqYSyzMxKrYjUVf0YVm3 Ln/rPOifdSjhBsFfJtyPENRIiPJ98ZWp7c8fb54e3087K9F9m38KRnaWc3sMUwxT7YEB pKf1o7rASQbO/+CdAslgA2AoCNJp7NiW3RBC4yB4Kg6vxu3J22mq63mEt3+Ep3x+5gvo UnUh1BpF84iL1ooLHbLR4XvZsuLhJKIFCu3bBheZJmJnrVHRDPx/ti9Z7cqjBRhyYIZd EEKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mime-version:content-disposition:user-agent; bh=fHvt62qYmeCedNbXSiHUBRPPpLXGyznUpBsDUEqZye8=; b=d85ZpEA9iRvIMigSDYibMm9fGoufLS9WEWm9xoXWIkQL1uziAQPnopPBTz05AJ7qaN y6VD4FtbjEyCwj5GJ04HvR+jjgAI0+PRq9lnT1VWmk5wrY7F8Pmaqxy0hCdEEsJPcLru mGI9MPyKSI/UIqglnGIgvTZoNDGWK9XT2NTLoVTuY0fyUQh7MYISLJfK5L+z1NqjMdIg FPsc4HIX9gwmqxFZQiAnZWqk22dqa9QtWWZ+Bkg7Fq31rnG1S+yALY+9EDonzAPw3bP2 TsJz6MZd7lJiC9IfkjA7je8YqOaImgPxp9B62oMZusCXSJVl/GvLoEz4gM2oMXIUthSh wcXA== X-Gm-Message-State: ALKqPwcGDQOcZWBrqfs+g6O1icN3wDFAY6ZxM2SiUU2UyR+nUqe3hOaA k2U1ZxD1eLkKwWpXZxaaoPS9/Q== X-Google-Smtp-Source: AB8JxZpQ4Ski2uAkRcn7FPc1nX3Ii2X8vG/EtpOO3ysBvLmH7OAlyhjs1RBCg7C6DkI8UKYYJ8mkZA== X-Received: by 2002:a62:c987:: with SMTP id l7-v6mr5856867pfk.221.1526577857826; Thu, 17 May 2018 10:24:17 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id y29-v6sm13517096pff.42.2018.05.17.10.24.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 10:24:17 -0700 (PDT) Sender: Mark Johnston Date: Thu, 17 May 2018 13:24:12 -0400 From: Mark Johnston To: freebsd-arch@FreeBSD.org Subject: enabling kernel dump options in GENERIC Message-ID: <20180517172412.GA92051@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 17:24:19 -0000 Hi, Over the past couple of years, a number of kernel dump features have been added: encryption, compression and dumping to a remote host (netdump). These features are currently all omitted from GENERIC. Adding the EKCD, GZIO, ZSTDIO and NETDUMP kernel options gives only a small increase in the size of amd64 GENERIC kernels: stock GENERIC: 31026016 bytes modified GENERIC: 31033000 bytes stock GENERIC-NODEBUG: 30995592 bytes modified GENERIC-NODEBUG: 31002680 bytes (The GZIO and ZSTDIO options also enable support for compressed user core dumps.) Therefore, I'd like to propose enabling these features by default on i386, amd64, arm64, powerpc(64) and sparc64 so that they're available out of the box in 12.0. Does anyone have concerns or objections around this? I've posted the corresponding change here: https://reviews.freebsd.org/D15465 From owner-freebsd-arch@freebsd.org Thu May 17 17:57:37 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ACA5EDB7B9 for ; Thu, 17 May 2018 17:57:37 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36CE16D1B0; Thu, 17 May 2018 17:57:37 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f179.google.com with SMTP id t23-v6so3062772ioc.10; Thu, 17 May 2018 10:57:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=Dfj/hnGCJSdBu0NJO23KLWdV6V1ISi1qN+7pld/67m8=; b=JjGOyyoPWVeYqvGi5rqY56lnXt2+G9ypjXz1nZOSD+lMivYFPrxzYrKSOHOvf5wmiy UGU0T0tEMGEuGSqL/3cigp36f/QDuTmBiDQr0aEFx6E59pMDLhyibBO7RZ4olX3yv0GK Ju4j2qWmMzkNOPVEONzWPw8u2wXLoHS+TX5SK/sH9/HeunfjHF0Eoox2UkMU4P3LH2gG RtoK6vJ7wiLM+gV3/IJ9NRIldYec8wEyPdT3Y7Rd16Vnhf7kT/Qx6Hv4U7lIR59SjajO j8XZj8Eic5hS2scQYrWph9eCcEtoROyqJU7pTMq9oSf2BJt1EikIqMVJKQyiDR5ihONA e1Qg== X-Gm-Message-State: ALKqPwewgWnnuYTVx0M/heVtXFXbaFfYsAjc1ma26ydaIUqL+as7XspX mDftkq7qNq7DzI5lKw9p9S5Djm6u X-Google-Smtp-Source: AB8JxZqPzKc4U9W7QDSt2rZ6zBzKYgrYjSj/hj6ORyNuyY36ZmFrPAS25PFRpBsPxvrMEFkjRvhQPA== X-Received: by 2002:a6b:8bc8:: with SMTP id n191-v6mr7292361iod.145.1526579856321; Thu, 17 May 2018 10:57:36 -0700 (PDT) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com. [209.85.223.174]) by smtp.gmail.com with ESMTPSA id a43-v6sm3207947itj.11.2018.05.17.10.57.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 10:57:36 -0700 (PDT) Received: by mail-io0-f174.google.com with SMTP id e12-v6so3058427iob.8; Thu, 17 May 2018 10:57:36 -0700 (PDT) X-Received: by 2002:a6b:3a87:: with SMTP id h129-v6mr6759759ioa.220.1526579856091; Thu, 17 May 2018 10:57:36 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:d81:0:0:0:0:0 with HTTP; Thu, 17 May 2018 10:57:35 -0700 (PDT) In-Reply-To: <20180517172412.GA92051@raichu> References: <20180517172412.GA92051@raichu> From: Conrad Meyer Date: Thu, 17 May 2018 10:57:35 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: enabling kernel dump options in GENERIC To: Mark Johnston Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 17:57:37 -0000 On Thu, May 17, 2018 at 10:24 AM, Mark Johnston wrote: > Hi, > > Over the past couple of years, a number of kernel dump features have > been added: encryption, compression and dumping to a remote host > (netdump). These features are currently all omitted from GENERIC. I don't have anything substantive to add, but as someone who has code-reviewed, written, and/or used a bunch of these features at $DAYJOB, I'd love to see them built by default in GENERIC =E2=80=94 even if disabled by default (compression =E2=80=94 the others don't have a sane default configuration). I don't think GZIO is especially useful if we enable ZSTDIO, but at the same time I think it's harmless to enable as an option. Thanks, Conrad From owner-freebsd-arch@freebsd.org Thu May 17 18:09:32 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9DF5EDBC9B for ; Thu, 17 May 2018 18:09:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C1D16DC26; Thu, 17 May 2018 18:09:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x242.google.com with SMTP id a20-v6so2478844pfo.0; Thu, 17 May 2018 11:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=e5nPAWi1kPA0TaF0B66le1WzSofzQXdd8WDWx/9W/H0=; b=MmMfLBIYhlkx4EIxdsmUvVMyeK2dHTe8KE1+FCdSOhOYQI2mq0IsTkdZuXdU3vVNMV tam0NRq8QcsuwTr9H1t97zEuV3eiSJnjQzLrRTztx2GsO8o0ome39pNcPVd11NVlA2JG 8f3AYKtRWpx1lNSOitvrmm/iP6Be5qjMeKCMtcv2fZhNkli2mYohfG/ODuJzJFktsAco WLI4Vq71m7mVCLvWLjzEGn+EWpbiKpCWhLRK8rz261m0t7NBRYkJ801Q54YOUu44GJyh Qm0IhmZJJipJI5CmdXFoDbd+LUPJdmnwX8+0pZvNma1Uve5k7BtWygdsuIWmQ+ExKcJz yUqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=e5nPAWi1kPA0TaF0B66le1WzSofzQXdd8WDWx/9W/H0=; b=Jrhzaq9x+KqIizyuSIIBAdBa+2WtuqM7Pvs/Ve5L96zMejxLDSImSuUbfpA3TmiEGD w4dU+N3val0DB9SrkmMYXF06xfJzL/dQvSU7wsDceSV3aiG8RylG3pgfASZD+c3oJbeg ySGYCs5Sriirc5cG+5RSLhvEwN6qkxnfxhBgoQ/c/SEsTSei00S3gZNq07bF34M7Sinz sQlC7yRoe3Db+BqjP7Kb8PExLOO+pDSL7+PIHTHkkd2oK2PSWH+5WEh+A1zywJRyEg4e 7ZDfDpZiemp9bvGJ69hf8sXaNjJl4tuIyrHff7kE53XcubOo3QsHfUE6fPQeNR9ZoBMA L4Lw== X-Gm-Message-State: ALKqPwedetVPl2nEBdkrufkmJs8on9Xy1ynAXpk8qsmKbnlOMPPdsd6A jSl99a74lUJi3A/Jto1ljMEPB7dJ X-Google-Smtp-Source: AB8JxZrDVmKHmZJp9abJtU6VAVCO43MBQpHeWizN+Blmm+BmzsMB8b6j31KnEWpuQUVboaH5OykzuQ== X-Received: by 2002:a63:5f10:: with SMTP id t16-v6mr81789pgb.52.1526580570987; Thu, 17 May 2018 11:09:30 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id o84-v6sm12377941pfi.27.2018.05.17.11.09.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 11:09:30 -0700 (PDT) Sender: Mark Johnston Date: Thu, 17 May 2018 14:09:27 -0400 From: Mark Johnston To: Conrad Meyer Cc: "freebsd-arch@freebsd.org" Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180517180927.GB5515@raichu> References: <20180517172412.GA92051@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 18:09:33 -0000 On Thu, May 17, 2018 at 10:57:35AM -0700, Conrad Meyer wrote: > On Thu, May 17, 2018 at 10:24 AM, Mark Johnston wrote: > > Hi, > > > > Over the past couple of years, a number of kernel dump features have > > been added: encryption, compression and dumping to a remote host > > (netdump). These features are currently all omitted from GENERIC. > > I don't have anything substantive to add, but as someone who has > code-reviewed, written, and/or used a bunch of these features at > $DAYJOB, I'd love to see them built by default in GENERIC — even if > disabled by default (compression — the others don't have a sane > default configuration). I don't think GZIO is especially useful if we > enable ZSTDIO, but at the same time I think it's harmless to enable as > an option. Yeah, given that the size increase is very small, I didn't see a reason to specifically exclude GZIO. I can also imagine a scenario where one uses GZIO+netdump to send dumps to a host lacking zstd(1). From owner-freebsd-arch@freebsd.org Fri May 18 03:58:27 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6450EEE87CF for ; Fri, 18 May 2018 03:58:27 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic305-22.consmr.mail.ne1.yahoo.com (sonic305-22.consmr.mail.ne1.yahoo.com [66.163.185.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0253783FC0 for ; Fri, 18 May 2018 03:58:26 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: _LZG4qcVM1nviEqB.XDTu5sJdFKfFPxAcGLr3CrdB3IWRikW9jhCjUk_rf8LnAk LnqpS5GnTp0Cd4_9L97Ur6dw7duKzD5We.oHxtYwaTMeoUY7xWFqBdmuv94ggK_p9DKrIxOjmaoD fAh64iEaAMuZyvZW.bwHFLRWDcrGXSawp2nsR9Q.bKSwGCaAnQ1WpBHir_9dSP8ISZvmHvLDSZiQ sm4WAosRBl4Lnw2bCQkCedbprLt7PU5fBIQjRpoj9pIL1wKiuJgdiViMKif5rp_9d5tjP0TRyiYx yYdjd6HPp06SaZqBlsgQnaSxkO9IFl4EPI6t27CYR_oW1Z9SIfXgaC6h6rQdcQB_Nf_xADx8hYKj .o9Ul94bc5T5q_LJx4L3swCnm44svCdNRWltRF_nzi9jY4RtE4CPIUQH.nQOhf2nVnV3ns._zpk6 soA_eukawwGoCNYnNSrbj9gvMF0_ZZMYqd3aqJz47OSzzAKK415YLYRenoBxkucHz6OUtrXNg4Wa ymsuVvFbUaevC8g.86LLB6hXEe.3i4tT3qwHYUPrPZ6dRUp9uhJVVlVh7gwkbi0fzX7r7WPgBabE hZMF0WJSyeZTwCWSseldNG_vK_GiJCwF3tWGY78ntZEBOEebYAuIultmCPMCSOGzFlpjA5LHlgqq 3r2piH05L Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ne1.yahoo.com with HTTP; Fri, 18 May 2018 03:58:20 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp403.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4f9c57344d3faaa3226565dc801e2d2c; Fri, 18 May 2018 03:58:18 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC Message-Id: Date: Thu, 17 May 2018 20:58:16 -0700 To: Mark Johnston , freebsd-arch@freebsd.org, FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 03:58:27 -0000 Mark Johnston markj at FreeBSD.org wrote on Thu May 17 17:24:19 UTC 2018 : > Over the past couple of years, a number of kernel dump features have > been added: encryption, compression and dumping to a remote host > (netdump). These features are currently all omitted from GENERIC. >=20 > . . . > Therefore, I'd like to propose enabling these features by default > on i386, amd64, arm64, powerpc(64) and sparc64 so that they're = available > out of the box in 12.0. > . . . Bugzilla 214598 (from late 2016) was about dump for TARGET_ARCH=3Dpowerpc64 builds getting failures like: KDB: enter: manual escape to debugger [ thread pid 12 tid 10018 ] Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 db> dump Dumping 9 MB (3 chunks) chunk 0: 10MB (2510 pages) ... ok chunk 1: 1MB (24 pages) ... ok chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: = c000000000022000 (A 32-bit powerpc build on the same machine worked fine for dumping.) I just tried it with head -r333594 and I got something similar. (Old and new mention routines with _bus_dma_map_ in the names near the trap in the call stack. I've not done a detailed comparison.) So, at least for the old PowerMac G5 so-called "Quad Core" powerpc64 context that was in use, there may be problems putting the changes to use --or in any use of dump. As for config for the kernel configuration involved: # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG # # GENERIC -- Custom configuration for the powerpc/powerpc64 # include "GENERIC64" ident GENERIC64vtsc-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols nooptions PS3 # Sony Playstation 3 = HACK!!! to allow sc options KDB # Enable kernel debugger support options ALT_BREAK_TO_DEBUGGER options BREAK_TO_DEBUGGER # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger options GDB # HACK!!! ... # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable any extra checking for. . . nooptions DEADLKRES # Enable the deadlock resolver nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones device filemon device geom_label =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arch@freebsd.org Fri May 18 06:17:44 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F6FAEEBA29; Fri, 18 May 2018 06:17:44 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9D0068B12; Fri, 18 May 2018 06:17:43 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x244.google.com with SMTP id x9-v6so3252306pfm.2; Thu, 17 May 2018 23:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cZFzvAHCZ9ZyqGrlvJc7qbfcstDWs/5KBZPvVr4aeJ4=; b=iDIWSJEq69TJocFJbkxpPr7ihhHFyv0iwecZr0HUCASHSoRDFr8nCxNsj6+EdYEEqn o4D42ZBzIb7y9ryEFhKBYg7LMe8OxsUpDtL/2nsQfFvChxsLcK5RyZxqPJrGVe78IEp1 /uBvb1q2ktVkSyDvehxh2ZbfqD2Pgh19Y0fs+PoO/LLMHY9FP0rmbDBOGEfW0c/8XBw8 xp3k9lZJ2L+3a42S0xoBo/hgo9eY1HcOpqi3oOuM2py0m6+H5kRkzKw4T3vqO8pfyVLu 0/v7wCUnlkvN9OS5zq+k0kvqBWfpVFfWjfiu0qeesBP0ZxSVEwCNGQyWSHRf56MC8yyp NAbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=cZFzvAHCZ9ZyqGrlvJc7qbfcstDWs/5KBZPvVr4aeJ4=; b=YzzlI6hPCJeFN6o0a0T0R5B3UwEX7zUC1R3ov+ABfvxwYbkSBPTG7s103hO5E6Lwjc ri10HWMxonguTRkH/A7LOog2np6qu4jMZaBNeXOXdM2IDUg9R2M2BE2Iag6jSY0Tnvnc NxiarOCiJ6YJ687DOODBXqy5YbAYKdEAOz37GqbiqQ4tNMl/3fu948wYT+MPJnNQ/ZrT oSsUWe7gj6Ta2U/zXVl0y95r7DmuX0UieYlgnwUEXXFtRklinWNTp4RimYEpXozE2nFs +ApmOaQbEC8of7df4I0MxX2hgYXcS8jsSMTUsiBLgIOycdtpbF3FHdVSW7a6gcoHInUb Mc5Q== X-Gm-Message-State: ALKqPwe0cRaMHdpNRV/9hP7/cIETlYFZMRao4SihpW4+fILPgX/KNSkS OE1xi3uIvSX+m/pppYtIwfc= X-Google-Smtp-Source: AB8JxZo1xk4EFCa/yNo+mhjaqiAoNWrci9l+Wh5GwHvcjveTv2UPVyiSjFzE2s9NzibUZSsrHqGxeA== X-Received: by 2002:a62:a391:: with SMTP id q17-v6mr8124835pfl.87.1526624262727; Thu, 17 May 2018 23:17:42 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id g207-v6sm12556422pfb.18.2018.05.17.23.17.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 23:17:41 -0700 (PDT) Sender: Mark Johnston Date: Fri, 18 May 2018 02:17:39 -0400 From: Mark Johnston To: Mark Millard Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180518061739.GC5515@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 06:17:44 -0000 On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: > Mark Johnston markj at FreeBSD.org wrote on > Thu May 17 17:24:19 UTC 2018 : > > > Over the past couple of years, a number of kernel dump features have > > been added: encryption, compression and dumping to a remote host > > (netdump). These features are currently all omitted from GENERIC. > > > > . . . > > Therefore, I'd like to propose enabling these features by default > > on i386, amd64, arm64, powerpc(64) and sparc64 so that they're available > > out of the box in 12.0. > > . . . > > Bugzilla 214598 (from late 2016) was about > dump for TARGET_ARCH=powerpc64 builds getting > failures like: > > KDB: enter: manual escape to debugger > [ thread pid 12 tid 10018 ] > Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 > db> dump > Dumping 9 MB (3 chunks) > chunk 0: 10MB (2510 pages) ... ok > chunk 1: 1MB (24 pages) ... ok > chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: c000000000022000 > > (A 32-bit powerpc build on the same machine worked > fine for dumping.) > > I just tried it with head -r333594 and I got something > similar. (Old and new mention routines with _bus_dma_map_ > in the names near the trap in the call stack. I've not > done a detailed comparison.) What is the call stack? From owner-freebsd-arch@freebsd.org Fri May 18 13:14:58 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D155EF4C3B for ; Fri, 18 May 2018 13:14:58 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-21.consmr.mail.gq1.yahoo.com (sonic311-21.consmr.mail.gq1.yahoo.com [98.137.65.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A9C775372 for ; Fri, 18 May 2018 13:14:56 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: IZDxD5MVM1kEqN7oRScH8dHlbWym4Or4dg6eRlIMX98ui6r35nefzBlwv4b4XoV OdDij4y7ZQBV5emzFLimWb1aqRl9h4LM.5GfEqUbqGwIOFIkEG8M5wW3l0CKRqGf3KLwFqUbZGRE jJpA68IJl1gkceWp.MjhN5fMNCFYNI1mZFebaO.lxDgY7W9O0GbXmAETHVBCO5y.hlaUOKQsKbSt 9BGthI_vg5TBpaQE.G2MfBAOuaPlVYqyUHEG5rKN12wyhkjwTU74XOm6FYNDC_hk5Nfu2nAqvfY2 9NOs8QSLE1v6_LDKKzocVXCEj9jtwizCBL5zhpjfG77cx1iWuHX.xZ6AhQgcvt8RyYoHjFT_aN6K vXzU301rwNjRz0BZM5Oh0n8bXJl_svaQvG9rLcinCqplJUfx2xCZdwA6a8w0ag2UXPhd7cKoV1Hz 19H0XK1_Bo5zbbPz_FfrL3hqnCvqNPZNhHBX2w8PYpsuataBHGb70IKNtJTWqZhoLPv4jSWWMq5J cSOx8lcoE9hZxzXz7iANxyOGlXgqpXkQflJ5ixheV7Va2UR4ZQOv_Pht.n6I1nBYSioAkwamifpi XK1o4XUHo1SKIwZ24HC5R.X.r_.TESWOXGvZnZtVCWBeLwn2kcvdls5CC9cxMHp4DYM7SJevy4vX 0kWtlrC89 Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Fri, 18 May 2018 13:14:55 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp422.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 3842a887bad1402a8d7eac6d60f0749f; Fri, 18 May 2018 13:14:51 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC From: Mark Millard In-Reply-To: <20180518061739.GC5515@raichu> Date: Fri, 18 May 2018 06:14:50 -0700 Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180518061739.GC5515@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 13:14:58 -0000 On 2018-May-17, at 11:17 PM, Mark Johnston wrote: > On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: >> Mark Johnston markj at FreeBSD.org wrote on >> Thu May 17 17:24:19 UTC 2018 : >>=20 >>> Over the past couple of years, a number of kernel dump features have >>> been added: encryption, compression and dumping to a remote host >>> (netdump). These features are currently all omitted from GENERIC. >>>=20 >>> . . . >>> Therefore, I'd like to propose enabling these features by default >>> on i386, amd64, arm64, powerpc(64) and sparc64 so that they're = available >>> out of the box in 12.0. >>> . . . >>=20 >> Bugzilla 214598 (from late 2016) was about >> dump for TARGET_ARCH=3Dpowerpc64 builds getting >> failures like: >>=20 >> KDB: enter: manual escape to debugger >> [ thread pid 12 tid 10018 ] >> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 >> db> dump >> Dumping 9 MB (3 chunks) >> chunk 0: 10MB (2510 pages) ... ok >> chunk 1: 1MB (24 pages) ... ok >> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: = c000000000022000 >>=20 >> (A 32-bit powerpc build on the same machine worked >> fine for dumping.) >>=20 >> I just tried it with head -r333594 and I got something >> similar. (Old and new mention routines with _bus_dma_map_ >> in the names near the trap in the call stack. I've not >> done a detailed comparison.) >=20 > What is the call stack? I'll have to induce the failure, take a picture of the screen that results, and hand type in the material for the fairly modern backtrace (-r333594). I will not be able to do this until later today. The bugzilla report has the old backtrace. I did not quote all the material from that report in the above. So there is something to compare against once I supply a modern one. Also: in about a week I'll lose access to the PowerMacs for an unknown period of time (weeks? months?). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arch@freebsd.org Fri May 18 15:11:26 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD363EAB174; Fri, 18 May 2018 15:11:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 614E97A13A; Fri, 18 May 2018 15:11:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl0-x242.google.com with SMTP id w19-v6so4756521plq.4; Fri, 18 May 2018 08:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=8wCpiNzu9sm6HYU41FTNvfeU6u5ocXmr9sw74+ewt4M=; b=kc6ln7mKra6aQUCd4QfOSUEhPYYj2dqVIdr8XnbTi+KOgAeVzBrV03hAX6j7SvOUr5 pgeBrVb/DXp0SEGTah1rdiM9wj81TaGJ4xbCzKYQVI5q1kSFJy4pNj6O8KDeptCJp05H 5KeBZ7whTTtZCGKwnFEYjpNU3R5xoGxqC5BtG79HUsG9qBbXfmJiX6trZk+Ka3MLHIeb eSd5yFf4Zbp8EaxPWkGs7s/Lg7ePgu70MnE3ZMSkbcUDwIy98McNBDlAY+ns0KN3Dy+J 7KzS6UIfYopkPvNgv4F6uRklrzl/Ht6ir6B/BGbUx0FRc4vWHABcI8Zs89dUrnJyM6Ji dWTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=8wCpiNzu9sm6HYU41FTNvfeU6u5ocXmr9sw74+ewt4M=; b=lcN7Bd5pnhqvGKj8exrprGpFkDNIqeCYYRCzBCyf2331MZqRnzrt1ZU/Pt/CsVOooM QXWLQuXnNv5rkp2bhbKzM2E25i7FZ5vqnBf0eQ1e1eKOh6P9hojUOTC8sctlmKf6fZEu avBuyXfKFkA6lCrrzFxfNfzO+sGce1gHT5LQ4LIZXhqPGD1DRcrdN4OKP8d8zhsjUrcZ rfkZE9s0dg9k1U8Xt6/IyKmYm7/BbccsytPMD6MtQ0SuAnqCBaRn+PBWznwfO+1XGKDN wKFoSBzbjOD+KH3rV1qAqwqwUOu2zev1xsUuKEFjeTQIzCVIwEdQyjvlHD8ERYIwDmG4 Tx1w== X-Gm-Message-State: ALKqPwerrm5GYPEXvDnOqnZZCqdHMEjbtW1AJZlaDTwKcE8booVY+OcX Im7dbronp+G0LN5cVE6t7fM= X-Google-Smtp-Source: AB8JxZo4B90wHlVx2cF569A3dyOti72O5dKLTNt5MPWL1BJ2tXWwdZCVybT3w2v5LQ8X9LFDFCOL+Q== X-Received: by 2002:a17:902:7e05:: with SMTP id b5-v6mr9717775plm.230.1526656284478; Fri, 18 May 2018 08:11:24 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id u6-v6sm10181530pgo.46.2018.05.18.08.11.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 08:11:23 -0700 (PDT) Sender: Mark Johnston Date: Fri, 18 May 2018 11:11:20 -0400 From: Mark Johnston To: Mark Millard Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180518151120.GE5515@raichu> References: <20180518061739.GC5515@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 15:11:26 -0000 On Fri, May 18, 2018 at 06:14:50AM -0700, Mark Millard wrote: > On 2018-May-17, at 11:17 PM, Mark Johnston wrote: > > > On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: > >> Mark Johnston markj at FreeBSD.org wrote on > >> Thu May 17 17:24:19 UTC 2018 : > >> > >>> Over the past couple of years, a number of kernel dump features have > >>> been added: encryption, compression and dumping to a remote host > >>> (netdump). These features are currently all omitted from GENERIC. > >>> > >>> . . . > >>> Therefore, I'd like to propose enabling these features by default > >>> on i386, amd64, arm64, powerpc(64) and sparc64 so that they're available > >>> out of the box in 12.0. > >>> . . . > >> > >> Bugzilla 214598 (from late 2016) was about > >> dump for TARGET_ARCH=powerpc64 builds getting > >> failures like: > >> > >> KDB: enter: manual escape to debugger > >> [ thread pid 12 tid 10018 ] > >> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 > >> db> dump > >> Dumping 9 MB (3 chunks) > >> chunk 0: 10MB (2510 pages) ... ok > >> chunk 1: 1MB (24 pages) ... ok > >> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: c000000000022000 > >> > >> (A 32-bit powerpc build on the same machine worked > >> fine for dumping.) > >> > >> I just tried it with head -r333594 and I got something > >> similar. (Old and new mention routines with _bus_dma_map_ > >> in the names near the trap in the call stack. I've not > >> done a detailed comparison.) > > > > What is the call stack? > > I'll have to induce the failure, take a picture of > the screen that results, and hand type in the > material for the fairly modern backtrace (-r333594). > I will not be able to do this until later today. > > The bugzilla report has the old backtrace. I did not > quote all the material from that report in the above. > So there is something to compare against once I > supply a modern one. My apologies, I missed the fact that the backtrace was included in that PR. Since the problem still occurs and apparently manifests with a similar backtrace, it wouldn't be useful to retest. I'm afraid I don't have any suggestions on how to make progress here. Given that the new options give only a small increase in the kernel size, I'm still inclined to enable them on powerpc64 for consistency with other architectures. > Also: in about a week I'll lose access to the PowerMacs > for an unknown period of time (weeks? months?). > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > From owner-freebsd-arch@freebsd.org Sat May 19 01:14:25 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 552F3EE3508 for ; Sat, 19 May 2018 01:14:25 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-23.consmr.mail.ne1.yahoo.com (sonic311-23.consmr.mail.ne1.yahoo.com [66.163.188.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB929730E1 for ; Sat, 19 May 2018 01:14:24 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: EwX6AUIVM1lUPOUXdR2CMcSo3rD78JVZu8CXtjGghZMOU5L4PB8VWRYEfIjtFiC SUK2qYU4m8MEAsoTOpna1L8CimXeb7p67RG_ZliOUy1ITLvI7edhRv_Vba7KeXhgf5R1JbnrUy2m pe4JoNAjyG.i6m.YV71dTVBtc0KZbx60Bjn2BrQdz2aG5ci5ZLVlC6s051N1fRW6cV57Zw3hwFU. LxqepViORRhYZ8rUZDd54XINyQkpMtYkIW_YZyZMlMgMmM33ZehvNO0gFvPU3pk5OiIcW9PLfl2v x5UDcN3EB1jzjZ2VhXWgHsTNIJhYVs56CdVXhUaqqpV00OLU_tHgyu5jszOFo_dY6HsH8digCbSD gyZejFG8OQ14QHKUhRSzCFnLbQ7pHQZUH3ablCZhwGzVxonBN2agmHfQEv3UkNVw.93JHt9NcE8Q 6wS6oyHu_HUbq.WJMRrk1xMLmgUDY1AK38skLyVKK_fK2FVzjFpFY679Idvs6mj7XBJdR3FvQ7bm RM1Ea5fOqOeB.g3vf4KDgwciq630KBnBXNprpgS1Ihjgw3PlBSYijUmI1sNbtVw1vN9Yzi0qdGpo 57H0S6u1zd_rKGQrGlasFbtH6rxGJwcpz1ppOZVi7RzLwtqJTqU1frZI0VgJlaBNFMXftx5sFE.. dk3KBnb2z Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ne1.yahoo.com with HTTP; Sat, 19 May 2018 01:14:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp409.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4b44c99488cf204d5d8b53f8e16ac17c; Sat, 19 May 2018 01:14:13 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC From: Mark Millard In-Reply-To: <20180518151120.GE5515@raichu> Date: Fri, 18 May 2018 18:14:12 -0700 Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <7F24144E-62CC-480F-A605-D06D2A4C7142@yahoo.com> References: <20180518061739.GC5515@raichu> <20180518151120.GE5515@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 01:14:25 -0000 On 2018-May-18, at 8:11 AM, Mark Johnston wrote: > On Fri, May 18, 2018 at 06:14:50AM -0700, Mark Millard wrote: >> On 2018-May-17, at 11:17 PM, Mark Johnston = wrote: >>=20 >>> On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: >>>> . . . >>>> Bugzilla 214598 (from late 2016) was about >>>> dump for TARGET_ARCH=3Dpowerpc64 builds getting >>>> failures like: >>>>=20 >>>> KDB: enter: manual escape to debugger >>>> [ thread pid 12 tid 10018 ] >>>> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 >>>> db> dump >>>> Dumping 9 MB (3 chunks) >>>> chunk 0: 10MB (2510 pages) ... ok >>>> chunk 1: 1MB (24 pages) ... ok >>>> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, = addr: c000000000022000 >>>>=20 >>>> (A 32-bit powerpc build on the same machine worked >>>> fine for dumping.) >>>>=20 >>>> I just tried it with head -r333594 and I got something >>>> similar. (Old and new mention routines with _bus_dma_map_ >>>> in the names near the trap in the call stack. I've not >>>> done a detailed comparison.) >>>=20 >>> What is the call stack? >>=20 >> I'll have to induce the failure, take a picture of >> the screen that results, and hand type in the >> material for the fairly modern backtrace (-r333594). >> I will not be able to do this until later today. >>=20 >> The bugzilla report has the old backtrace. I did not >> quote all the material from that report in the above. >> So there is something to compare against once I >> supply a modern one. >=20 > My apologies, I missed the fact that the backtrace was included in = that > PR. Since the problem still occurs and apparently manifests with a > similar backtrace, it wouldn't be useful to retest. I'm afraid I don't > have any suggestions on how to make progress here. Given that the new > options give only a small increase in the kernel size, I'm still > inclined to enable them on powerpc64 for consistency with other > architectures. Seems reasonable. May be there are other powerpc64 contexts that can test the updates. Useful or not, I've updated bugzilla 214598 with a backtrace from head -r333594 and have updated its one-line summary to reference -r333594 . Looks like I missed a 0 in: 0xe7ced0: at 0xc00000006ab17fc it should be: 0xe7ced0: at 0xc000000006ab17fc I've no clue why this address has no symbol. I showed more of the stack this time. At least now the old and new can be compared. That is better than forcing folks to rely on my earlier quick look. >> Also: in about a week I'll lose access to the PowerMacs >> for an unknown period of time (weeks? months?). >>=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)