From owner-freebsd-current@freebsd.org Sun Nov 24 05:27:01 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 19BB21CC203 for ; Sun, 24 Nov 2019 05:27:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic305-19.consmr.mail.gq1.yahoo.com (sonic305-19.consmr.mail.gq1.yahoo.com [98.137.64.82]) (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 47LJZD1QX6z4s9S for ; Sun, 24 Nov 2019 05:26:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: CZmBAZUVM1kQNkfuPyjtih36HoobPYvdLupRVitvNiD4NAS95Rtl6NH1GU0NYBc IcCFw9MJZHNfyEjlud0u0gdoqztAjMTHaaJIjiLHhWV64ItlijnXg1inFJinOgnXM9BJHztuP9cM FSJTAQgONAmJD_EvNtPgPc7W16FWehAnlcqgC8Q48H0OJhpNmlOLojEwPf0i.k4RAyG2LNDNdfIi P85vw2mhaBDYOTzwWT0dLcxr92EGoIajMr_FOvEwPRatGydQ._T7GyKTQ2xdm4a7KrGBoLPBf3Je H5kCuMs_2Z5w4DUuocW_4yOr1R3KkCNQd4ihyLLz1XqYlLwGQALZHBbbGZn2GpUYTX1.dps67NfP 3Y78Q8JJMDGCri2A1Tds_qhPgQliwDYdQXALPGlo.PTLiUXn0H_Ub2Z9P2585wuXb9sPC6JlvkPc mI5KhQJybHYv8ddxRTm5MilbG5b8ZUoCd0UGejXjV3KbX.DU5i3rmFBvu8nVM1RB_oGnLg6MEQEF wIY.qOrL39VuGUE01ra60o1hu8hiQLKTJE.mqqpWROmf1I8UaNnlToBxZ1ZBlaEKWXk91YY.8i1p yh9XyGuTBioUxg1r7YBHVNWVmbqFqzzWAG2xDHo1Qn5pZL2Kt2qa6SVj_EjzbChzvA02JiOLsHl. a5j4t3r1biJvVBEzUI786FwSU7T3ZTMBRB7ZZ.EX2vlOy1OqKyt9.Bz0xMuS_UhVcHtvimum4nyY kaPMmLqvA8uJCW5FyprkkyURKjtL4H4iWfwraQC2Rt2okrZ.KIR2kRrNtmU41r4dkbFC_PU8_kka e51NWB_budhIC.3TDNkAZb44oCP05ndSnSZRNsFjP2thhPGuujY.Wqwxvw_NWHe2TC6vd9aX6yYD S_QOBnEFoEBZ0Ih5gRgGSpyUcaPrOqRqjlW6n_ZfKBVsJZLJZcW88Azj2OCMqdtQxFGdwv5RWqgS 8U_LhZe5wRqxW1fN83URGZFzWv.0_BGVM.hWZclx6ppabDBJuOSw023wzXw9bueXju8kSAMWVVz4 nn8tc6ZzbGnocv2gw2UBs7mtwrc3fB8h7vCGDa28wktn7_Kwz9e_KMoks8QAyhQOS_jSxPG2hJEN qvEJ5BpUbzRJMR63bRvqCtny06KMpMeHKENFc_ZeHHFV6nhQO5Ek.IO6jMbAe52kmK8MtwrkmAze N2AGoh53JuAdxHdOKy9BkRKlyQMpmro3PrwveVIepy2vqk1yQIDitZzUyx6zcZTvhhGNocpXUNAP TQ19jZq2F6xqSsOnHKR3zR20ot6kZT7SEkIYKj.HCaZn0ur2oexQZyGMCeFo9xrXtYAXcattYOY6 8XVFOAxUVpxUWUuAQMEV_qKQgQhFLsbyWUlwqD3g9EmEwZijM_F6.yeMuYyNwGimBUsYjSvpUVJN 7_Ieeh5t4XBjAFHbmxoz9jV0gLz6F13WSnDf9 Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.gq1.yahoo.com with HTTP; Sun, 24 Nov 2019 05:26:56 +0000 Received: by smtp429.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 3478ead8698d0abce18233374cb45105; Sun, 24 Nov 2019 05:26:54 +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 13.0 \(3601.0.10\)) Subject: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h Message-Id: <364D98C1-727B-4956-A73B-10CFEB8E1A12@yahoo.com> Date: Sat, 23 Nov 2019 21:26:52 -0800 To: FreeBSD Current , FreeBSD Toolchain X-Mailer: Apple Mail (2.3601.0.10) References: <364D98C1-727B-4956-A73B-10CFEB8E1A12.ref@yahoo.com> X-Rspamd-Queue-Id: 47LJZD1QX6z4s9S X-Spamd-Bar: + X-Spamd-Result: default: False [1.44 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_SPAM_MEDIUM(0.96)[0.963,0]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[82.64.137.98.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_LONG(0.98)[0.979,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.00)[ip: (6.06), ipnet: 98.137.64.0/21(0.88), asn: 36647(0.70), country: US(-0.05)]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 05:27:01 -0000 My poudiere jail constructions with the likes of -a arm64.aarch64 -x are all getting: awk: can't open file /sys/param.h source line number 1 If /sys is supposed to be something like: # ls -ld /sys lrwxr-xr-x 1 root wheel 11 May 21 2018 /sys -> usr/src/sys then the path would appear to need to be something like /sys/sys/param.h = . But I notice that the likes of my: /usr/obj/DESTDIRs/clang-cortexA53-installworld-poud/ does not have a sys/ . Possibly (likely?) not relevant: I'll note that doing a source upgrade to go from head -r352341 to -r355027 did not establish a /etc/os-release on the amd64 host. But /var/run/os-release does exist. By contrast: # ls -ld = /usr/obj/DESTDIRs/clang-cortexA53-installworld-poud/etc/os-release lrwxr-xr-x 1 root wheel 21 Nov 23 19:56 = /usr/obj/DESTDIRs/clang-cortexA53-installworld-poud/etc/os-release -> = ../var/run/os-release was established, possibly via the distrib-dirs distribution = DB_FROM_SRC=3D1 use involved in (re-)constructing = /usr/obj/DESTDIRs/clang-cortexA53-installworld-poud/ . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Nov 24 20:51:17 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C07221BA9B5 for ; Sun, 24 Nov 2019 20:51:17 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Lj4h74XTz4SZ8 for ; Sun, 24 Nov 2019 20:51:16 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi1-f169.google.com with SMTP id o12so11242916oic.9 for ; Sun, 24 Nov 2019 12:51:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=1M3LqaZ+cj+Sr4kIX53LgzW9BG8r40Ub2IR2Yp9cgHQ=; b=reGOv03Z5SRbPaeS1FCBaOk0Fkd6uLw/9j7HRAxeL6I85m+fgcFBYnsL5wAlr3O9MH KN1uIf3PufCL872rJ00F39ciXGUesY3dEz0xYKBazdM3xmf1qNE4IE5J2EdkKejLj5Q/ 9wcI4bmP00IiQy4ZvfZBd7776inG+qnWce3uB3a4KwtjI5F9oNCdKFikwFnCM5IVZY9T O85B7hJJNjeQPezhVpnQS3fTetup68cErjZVVOn1TLLEB4OILisAQqqwCi2M6eWbdeN8 Pq9M/i9oTjLWxph+twfcV30COeZTQDrIrOevYAL6Dzbyqbj+UfesXn1TJBEqp3rSYZNJ Iy4Q== X-Gm-Message-State: APjAAAVD+TYkTpbGoya6us8Fcc0ldCF3PDVTUObscfDfdxokePwXt5bT l8q3hw1rqFxECyb9thY6AU0xwuqF X-Google-Smtp-Source: APXvYqw7Yn7RnHxhtKBCzPVpBxGTrnIYCjl3FMDHOvFQqgSuHaXAnB8YnRxgdTJmvd4ctwf55avmhw== X-Received: by 2002:aca:60c1:: with SMTP id u184mr6486903oib.75.1574628675099; Sun, 24 Nov 2019 12:51:15 -0800 (PST) Received: from mail-oi1-f171.google.com (mail-oi1-f171.google.com. [209.85.167.171]) by smtp.gmail.com with ESMTPSA id e186sm1801446oia.47.2019.11.24.12.51.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 24 Nov 2019 12:51:14 -0800 (PST) Received: by mail-oi1-f171.google.com with SMTP id e9so11257578oif.8 for ; Sun, 24 Nov 2019 12:51:14 -0800 (PST) X-Received: by 2002:aca:320a:: with SMTP id y10mr19942057oiy.152.1574628674589; Sun, 24 Nov 2019 12:51:14 -0800 (PST) MIME-Version: 1.0 References: <20191124.061357.2264854536159910571.yasu@utahime.org> In-Reply-To: <20191124.061357.2264854536159910571.yasu@utahime.org> Reply-To: cem@freebsd.org From: Conrad Meyer Date: Sun, 24 Nov 2019 12:51:03 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: /etc/os-release isn't created To: Yasuhiro KIMURA Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Lj4h74XTz4SZ8 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.167.169 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-3.12 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[169.167.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.12)[ip: (-0.40), ipnet: 209.85.128.0/17(-3.17), asn: 15169(-1.96), country: US(-0.05)]; RWL_MAILSPIKE_POSSIBLE(0.00)[169.167.85.209.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 20:51:17 -0000 Hi, Did you run etcupdate or mergemaster as part of updating your host? Best, Conrad On Sat, Nov 23, 2019 at 1:15 PM Yasuhiro KIMURA wrote: > > Hello, > > Yesterday I updated my 13-CURRENT host from r354592 to r355028 and > /etc/os-release symbolic link wasn't created. > > yasu@rolling-vm-freebsd1[2061]% uname -a > FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355028: Sat Nov 23 22:35:58 JST 2019 rootz@rolling-vm-freebsd1.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/head/amd64.amd64/sys/GENERIC amd64 > yasu@rolling-vm-freebsd1[2062]% ls -l /etc/os-release > ls: /etc/os-release: No such file or directory > yasu@rolling-vm-freebsd1[2063]% > > But after that I made same update of 13-CURRENT poudriere jail and > then /etc/os-release was created in it. > > yasu@rolling-vm-freebsd1[2063]% ls -l /usr/local/poudriere/jails/curamd64/etc/os-release > lrwxr-xr-x 1 root wheel 21 Nov 24 05:04 /usr/local/poudriere/jails/curamd64/etc/os-release@ -> ../var/run/os-releaseyasu@rolling-vm-freebsd1[2064]% > > Why such difference happens? > > --- > Yasuhiro KIMURA > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sun Nov 24 23:11:34 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ED1AF1BF329; Sun, 24 Nov 2019 23:11:34 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47LmBZ04y3z4cKd; Sun, 24 Nov 2019 23:11:33 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-vs1-xe2f.google.com with SMTP id u6so8785008vsp.4; Sun, 24 Nov 2019 15:11:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5G8Xxq+P/j3tLqkVs8MFQy9ajAjDf5wMTw3BsSrws1Q=; b=ssp+73jG1zLhHk8596k8Xxm0YWD2re7v3Hxot9AAYWSsqGmwF/q5g+iD3eYW5sMqZa mV0OCNxBpSPsrydsPgHZPAKk1T6qGK1aBOtcfOs3dQXm8MBwoKNZ6uCOhIBNCcweQi+1 C3B7ZpNHS4Pf5qJhSaN+eZu6/dVl/Ugajb5PYstO87WUc80XKHAcKiYOKpyrCoCtSBqb mr0xLaA8R9wlRTRjWvEM4UgCX4m8UCAuOrR6+gByDJiYO5+79kIrDbmDBqpOZ6L3Gk6V ivJXjR7ZYvNwxFW4KBWL/QSQ9x2VtV/0B6Uh3E+me44DfJ+AAMgulUVe8LmxDvFdxfnr q5rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5G8Xxq+P/j3tLqkVs8MFQy9ajAjDf5wMTw3BsSrws1Q=; b=eN04jNn/nR7b0kdZFm3bvhhbHJGj4n9Xa4UGWm0eLwcEUcq8CYxd9vEqe2CBCVheyY 8gpaEaSKGKk9qlhBZbHQO8Era5Bik0o53mSIjGKltcFXOezj68eB4VL5oid6RSpYUykf q5GuuBYODlX4XU9OEdnV4ntRXtvG0t4ugdf7IQbad0PrZfFHXBA0c0edOK3SiCXsbo3d S2hQuDlTnyDRWJs3ThdNjtt6tem938Np0OQlwgSGYa9cIUtOVgaHP37Esfa3iiQlbYd8 agDmhziLa/uw2pI7mpPiNdt0h5DnHL0tXUOYGJfSMNtyfyhceVhPd/ahkrtk7ViXEEAU sgrQ== X-Gm-Message-State: APjAAAXe8wraJ3qivudvZpOO5fq9vkOa4GdpzOyXnm9IZ2YewsbT/6S+ SnhQ4kukJhR/qSSofT6Jct4yCMl8uEMRL0uUpZQ= X-Google-Smtp-Source: APXvYqyqw994XftCwfY6qC7XU4Uz4klud4fcuZegaFEXi8qpGB5f/Iol6c9dr1HtaAOzHkiHg9+SNONeYPEeNNChFFI= X-Received: by 2002:a67:8d09:: with SMTP id p9mr17459843vsd.53.1574637092509; Sun, 24 Nov 2019 15:11:32 -0800 (PST) MIME-Version: 1.0 References: <364D98C1-727B-4956-A73B-10CFEB8E1A12.ref@yahoo.com> <364D98C1-727B-4956-A73B-10CFEB8E1A12@yahoo.com> In-Reply-To: <364D98C1-727B-4956-A73B-10CFEB8E1A12@yahoo.com> From: Ben Woods Date: Mon, 25 Nov 2019 07:11:21 +0800 Message-ID: Subject: Re: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h To: Mark Millard Cc: FreeBSD Current , FreeBSD Toolchain , FreeBSD ports X-Rspamd-Queue-Id: 47LmBZ04y3z4cKd X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ssp+73jG; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of woodsb02@gmail.com designates 2607:f8b0:4864:20::e2f as permitted sender) smtp.mailfrom=woodsb02@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(0.00)[ip: (-9.66), ipnet: 2607:f8b0::/32(-2.28), asn: 15169(-1.96), country: US(-0.05)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[f.2.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 23:11:35 -0000 On Sun, 24 Nov 2019 at 1:27 pm, Mark Millard wrote: > My poudiere jail constructions with the likes of -a arm64.aarch64 -x are > all getting: > > awk: can't open file /sys/param.h > source line number 1 Hi Mark, I have been getting this same error on amd64 for some time when I use the command below. # poudriere jail -j 13amd64 -u -m src=/usr/src Any ideas what it could be? Regards, Ben > -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-current@freebsd.org Sun Nov 24 23:14:12 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BDB741BF67A for ; Sun, 24 Nov 2019 23:14:12 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (gate.utahime.jp [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47LmFb3Pf0z4cqH for ; Sun, 24 Nov 2019 23:14:11 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gate.utahime.jp (Postfix) with ESMTPS id 7D9BD1D4C9 for ; Mon, 25 Nov 2019 08:14:01 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 09DE840C81; Mon, 25 Nov 2019 08:14:01 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.1 at eastasia.home.utahime.org Date: Mon, 25 Nov 2019 08:13:19 +0900 (JST) Message-Id: <20191125.081319.1547651065831056208.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: /etc/os-release isn't created From: Yasuhiro KIMURA In-Reply-To: References: <20191124.061357.2264854536159910571.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47LmFb3Pf0z4cqH X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of yasu@utahime.org designates 183.180.29.210 as permitted sender) smtp.mailfrom=yasu@utahime.org X-Spamd-Result: default: False [0.82 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.25)[-0.253,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.51)[-0.506,0]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[utahime.org]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.38)[ip: (0.28), ipnet: 183.180.0.0/16(0.14), asn: 2519(1.45), country: JP(0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 23:14:12 -0000 From: Conrad Meyer Subject: Re: /etc/os-release isn't created Date: Sun, 24 Nov 2019 12:51:03 -0800 > Did you run etcupdate or mergemaster as part of updating your host? Yes. I run 'mergemaster -Fi' after 'make installworld' I recieved report by private mail that /etc/os-release is created only when 'make distribution' is executed. And I found that's exactly what is written in /usr/src/etc/Makefile. yasu@rolling-vm-freebsd1[2103]% grep '\$FreeBSD' /usr/src/etc/Makefile # $FreeBSD: head/etc/Makefile 354922 2019-11-20 23:45:31Z imp $ yasu@rolling-vm-freebsd1[2104]% tail +50 /usr/src/etc/Makefile | head -n 12 distribution: .if !defined(DESTDIR) @echo "set DESTDIR before running \"make ${.TARGET}\"" @false .endif ${_+_}cd ${.CURDIR}/gss; ${MAKE} install ${_+_}cd ${.CURDIR}/mtree; ${MAKE} install ${_+_}cd ${SRCTOP}/share/termcap; ${MAKE} etc-termcap ${_+_}cd ${SRCTOP}/usr.sbin/rmt; ${MAKE} etc-rmt ${INSTALL_SYMLINK} ../var/run/os-release \ ${DESTDIR}/etc/os-release yasu@rolling-vm-freebsd1[2105]% But 'make distribution' isn't executed by normal upgrade steps. So it's a bug and should be fixed. --- Yasuhiro KIMURA From owner-freebsd-current@freebsd.org Sun Nov 24 23:22:58 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2531A1BFC4A for ; Sun, 24 Nov 2019 23:22:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic311-25.consmr.mail.gq1.yahoo.com (sonic311-25.consmr.mail.gq1.yahoo.com [98.137.65.206]) (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 47LmRh56MFz4dVp for ; Sun, 24 Nov 2019 23:22:56 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 8tDVOY0VM1mtcj2RYgPmdCq6jtdan6mhgaHzgBA9KH4ziSDD92gqYfuHkm9jhKk bBvuPDvm9ClekxdhaUEJjyYoI9MAR6S8mtFKklVnI.RHR_VHq3JZgMg_FiUF4q1tXrCYhbRKeef6 oOK7Mm0K6zNlvTzmm76gOSFxXjfmVD3gamun0GEqop7Zzde_bamSc20V7DqbOPPo0VfVnV08b5M_ pjMKFj0pvV1IyMEIWoCSjF0A1tp73gH49Eribl30sHtKVGdGcw3maqHPpNWAUQhMkxtwCqsjcf2G 42L07weepFaXY9EgkxGu89u32E6_igSnhm09Cg43c8ViGKDkhyHNVVq5T7etLPwJ9cF1raBsApfP zNBhDZoXP_zYhuo7FUcNP2Exw.Iub2NhM0XGSjVopVyzGlcWsad_woJsPbzApb.ZeKvccgGSGd1f mPk70mYzplTiEf0Wyh.qAjtMrwoWGuBPqxCLlSfepzmJsMnPz0Gw4NXa8SZlO.cju7ipQl5n7DSU FDRxdOHAFVKk5hlthqbbOrFr_P.PHIVP1byoQKOYG988liD7jYxTFro5R8weLu9747SY1Hx9dC.W PML89eFJPupeTpx_E7k1IolJhnycoimj0mf_HYHWJHHs2EinEmnMNJuTFFnEQQop8mbdoasuZbxX rdloYRLeI5KkJXEvfcXJZiApfqZTGipPwt.CyKS1RImeL9dcJgVBDcXZ93cwTUWp5I_MKYBtPBUX e29NDAcjsxc9AB7mQYMmuL6kgDVQzBU2QnyPVPnxdFTBc31f8Y16eLk9b8TtS9RSFk1iR0WgF.9L zjDSLoTkYZazz8ABAq1SpxQm9OHf0EVOdLDIuPuyB6MHJiRKjF8BH20ufG3.oeRRdPNSF7ZxqSaA 9Kc_ey_iW7FzRFeNM7hqT1aDb4R87aNBTu0pyvvaHRX4wqzbbGjO9TQyaEqdgVt3nwqPIrQ7398w WtZZtqNr1WPZQYzRuKD0m_alPcPJRbAOraUwsHMEtLxA4QsVWVvu2_CqAVRaIl4l0aexYx_fgH0J Ac__IMZqNzq4O3GyxNz3peVz7mntA.ejBX3fEq6dyA6JYsvQwFDboJw3ElqbQ21Fvw9ncYUr1vzH 4.nWXbfWuWC5OnO4EvYRRzzDmRFZ_FWKrSr3_w8oD32BnaPDhOBG_oReGkeaLXGcq3N_lBtK_F6. CEHNWifDKoeJP4Lg3D4h8Pu37Qu2KoRbUJ3APhbTmfRvgpbxMSjWP67AfkmjufMejn8gfjpdpA4v LxIFxi06Uddlsq0WU7tK2UqDrC2kpMkB1PsWcvoflAEEoteP2MNyHrnrCkbWcsuv8NlHsU4mGUgK MAOaNYRh2ee9LhnlyXOrJW0VX6EsJu8jwH4yL7UdlNn.L5PVRD2htJ_peFnneJqaIk9eQCxpS2cp zns2n7lMiSNzjv1SRkrPcKc6HVXtZdez1g5_GEQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Sun, 24 Nov 2019 23:22:54 +0000 Received: by smtp401.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 73a63cf729dde055d3f9043ff1ebb512; Sun, 24 Nov 2019 23:22:51 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h From: Mark Millard In-Reply-To: Date: Sun, 24 Nov 2019 15:22:50 -0800 Cc: FreeBSD Current , FreeBSD Toolchain , FreeBSD ports Content-Transfer-Encoding: quoted-printable Message-Id: <82CE331F-D359-415A-A702-49BF7285D88E@yahoo.com> References: <364D98C1-727B-4956-A73B-10CFEB8E1A12.ref@yahoo.com> <364D98C1-727B-4956-A73B-10CFEB8E1A12@yahoo.com> To: Ben Woods X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47LmRh56MFz4dVp X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.45 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.979,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-0.97)[-0.968,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-1.42), ipnet: 98.137.64.0/21(0.87), asn: 36647(0.70), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[206.65.137.98.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 23:22:58 -0000 On 2019-Nov-24, at 15:11, Ben Woods wrote: > On Sun, 24 Nov 2019 at 1:27 pm, Mark Millard = wrote: > My poudiere jail constructions with the likes of -a arm64.aarch64 -x = are > all getting: >=20 > awk: can't open file /sys/param.h > source line number 1 >=20 > Hi Mark, >=20 > I have been getting this same error on amd64 for some time when I use = the command below. > # poudriere jail -j 13amd64 -u -m src=3D/usr/src >=20 > Any ideas what it could be? Not so far. Good to know that cross-building is not part of the required = context. I've yet to find a place that might be involved that mixes awk use with = an expression generating a file path that could generate /sys/param.h as the path. If this was happening in my prior -r352341 context, I did not notice it. = I jumped from there to -r355027 . So I can not effectively narrow the range for = when it started based on my activity. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Nov 24 23:40:11 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 594B21C051B for ; Sun, 24 Nov 2019 23:40:11 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (gate.utahime.jp [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47LmqZ3Wcpz4fFQ for ; Sun, 24 Nov 2019 23:40:10 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gate.utahime.jp (Postfix) with ESMTPS id B9EC51D4D4 for ; Mon, 25 Nov 2019 08:40:06 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 780CE40CB0; Mon, 25 Nov 2019 08:40:05 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.1 at eastasia.home.utahime.org Date: Mon, 25 Nov 2019 08:39:48 +0900 (JST) Message-Id: <20191125.083948.65297440774951244.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: /etc/os-release isn't created From: Yasuhiro KIMURA In-Reply-To: <20191125.081319.1547651065831056208.yasu@utahime.org> References: <20191124.061357.2264854536159910571.yasu@utahime.org> <20191125.081319.1547651065831056208.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47LmqZ3Wcpz4fFQ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of yasu@utahime.org designates 183.180.29.210 as permitted sender) smtp.mailfrom=yasu@utahime.org X-Spamd-Result: default: False [0.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.08)[-0.075,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.90)[-0.899,0]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[utahime.org]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.38)[ip: (0.28), ipnet: 183.180.0.0/16(0.14), asn: 2519(1.44), country: JP(0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2019 23:40:11 -0000 From: Yasuhiro KIMURA Subject: Re: /etc/os-release isn't created Date: Mon, 25 Nov 2019 08:13:19 +0900 (JST) > I recieved report by private mail that /etc/os-release is created only > when 'make distribution' is executed. And I found that's exactly what > is written in /usr/src/etc/Makefile. > > yasu@rolling-vm-freebsd1[2103]% grep '\$FreeBSD' /usr/src/etc/Makefile > # $FreeBSD: head/etc/Makefile 354922 2019-11-20 23:45:31Z imp $ > yasu@rolling-vm-freebsd1[2104]% tail +50 /usr/src/etc/Makefile | head -n 12 > > distribution: > .if !defined(DESTDIR) > @echo "set DESTDIR before running \"make ${.TARGET}\"" > @false > .endif > ${_+_}cd ${.CURDIR}/gss; ${MAKE} install > ${_+_}cd ${.CURDIR}/mtree; ${MAKE} install > ${_+_}cd ${SRCTOP}/share/termcap; ${MAKE} etc-termcap > ${_+_}cd ${SRCTOP}/usr.sbin/rmt; ${MAKE} etc-rmt > ${INSTALL_SYMLINK} ../var/run/os-release \ > ${DESTDIR}/etc/os-release > yasu@rolling-vm-freebsd1[2105]% > > But 'make distribution' isn't executed by normal upgrade steps. So > it's a bug and should be fixed. I submitted bug report about this problem to Bugzilla. Bug 242212 /etc/os-release isn't created when you upgrade an existing 13-CURRENT host https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 --- Yasuhiro KIMURA From owner-freebsd-current@freebsd.org Mon Nov 25 01:11:45 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 67D1D1C2B7B for ; Mon, 25 Nov 2019 01:11:45 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47LpsD3M8fz3Ftd for ; Mon, 25 Nov 2019 01:11:43 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Mon, 25 Nov 2019 02:11:35 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail201809; t=1574644295; bh=QrM1mstdWdrxUHlGUAzEv2AEjujCR1FUvWb2qON7f/E=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=Pw1LJpIIj8gFIoJmLu43ufM5VjmHAAWfRisC8c3OE0sCRv3BLsLg0ROayb0ydchUr hsw1qUJxNPWvA9dW7jWu3iPUL/5OLVElPPBE5yiKRPu6c0CHaUDFZStLsB3hvj+M8h JDS8rHuhSAnBiX0dFFKCJDBv4KaBPXN3Q7HVkOhN6Ae064KECPJyaLxpd9U9wCjf7g r9ckJvlwqiSslZiHlzAdb0uOqOk+KsTLVbW7vCL2OPlEO7jQkNe85e8LQcYXBB3xdl nZpHaC1uvLsa9EvAbnvlI0gzLNTZsGGowowPZKZ82YnnY6+bZVs+EWwglngw+ww3rh Ea0ESMWvMgacg== From: "Herbert J. Skuhra" To: freebsd-current@freebsd.org Subject: Re: /etc/os-release isn't created Message-ID: <20191125011135.GA69956@mail.bsd4all.net> References: <20191124.061357.2264854536159910571.yasu@utahime.org> <20191125.081319.1547651065831056208.yasu@utahime.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191125.081319.1547651065831056208.yasu@utahime.org> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 47LpsD3M8fz3Ftd X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail201809 header.b=Pw1LJpII; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 94.130.200.20 as permitted sender) smtp.mailfrom=herbert@gojira.at X-Spamd-Result: default: False [-2.91 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail201809]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:94.130.200.20]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[gojira.at]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DKIM_TRACE(0.00)[gojira.at:+]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.41)[ipnet: 94.130.0.0/16(-0.45), asn: 24940(-1.58), country: DE(-0.01)]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 01:11:45 -0000 On Mon, Nov 25, 2019 at 08:13:19AM +0900, Yasuhiro KIMURA wrote: > distribution: > .if !defined(DESTDIR) > @echo "set DESTDIR before running \"make ${.TARGET}\"" > @false > .endif > ${_+_}cd ${.CURDIR}/gss; ${MAKE} install > ${_+_}cd ${.CURDIR}/mtree; ${MAKE} install > ${_+_}cd ${SRCTOP}/share/termcap; ${MAKE} etc-termcap > ${_+_}cd ${SRCTOP}/usr.sbin/rmt; ${MAKE} etc-rmt > ${INSTALL_SYMLINK} ../var/run/os-release \ > ${DESTDIR}/etc/os-release > yasu@rolling-vm-freebsd1[2105]% > > But 'make distribution' isn't executed by normal upgrade steps. So > it's a bug and should be fixed. - mergemaster runs 'make distribution': ${MM_MAKE} DESTDIR=${TEMPROOT} distribution >/dev/null;} || - the link etc/os-release is created in /var/tmp/temproot when running mergemaster but not moved to / -- Herbert From owner-freebsd-current@freebsd.org Mon Nov 25 01:28:34 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 79B7D1C35AD for ; Mon, 25 Nov 2019 01:28:34 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (gate.utahime.jp [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47LqDd02qSz3Gwv for ; Mon, 25 Nov 2019 01:28:32 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gate.utahime.jp (Postfix) with ESMTPS id 557831D4FF for ; Mon, 25 Nov 2019 10:28:27 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 2CA7940D82; Mon, 25 Nov 2019 10:28:26 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.1 at eastasia.home.utahime.org Date: Mon, 25 Nov 2019 10:27:36 +0900 (JST) Message-Id: <20191125.102736.1372422754370589145.yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: /etc/os-release isn't created From: Yasuhiro KIMURA In-Reply-To: <20191125011135.GA69956@mail.bsd4all.net> References: <20191125.081319.1547651065831056208.yasu@utahime.org> <20191125011135.GA69956@mail.bsd4all.net> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47LqDd02qSz3Gwv X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of yasu@utahime.org designates 183.180.29.210 as permitted sender) smtp.mailfrom=yasu@utahime.org X-Spamd-Result: default: False [0.24 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.42)[-0.423,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.91)[-0.907,0]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[utahime.org]; MV_CASE(0.50)[]; MID_CONTAINS_FROM(1.00)[]; IP_SCORE(0.37)[ip: (0.28), ipnet: 183.180.0.0/16(0.14), asn: 2519(1.44), country: JP(0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 01:28:34 -0000 From: "Herbert J. Skuhra" Subject: Re: /etc/os-release isn't created Date: Mon, 25 Nov 2019 02:11:35 +0100 > - mergemaster runs 'make distribution': > ${MM_MAKE} DESTDIR=${TEMPROOT} distribution >/dev/null;} || > - the link etc/os-release is created in /var/tmp/temproot when running > mergemaster but not moved to / Thank you for investigation. Then is is bug of mergemaster? --- Yasuhiro KIMURA From owner-freebsd-current@freebsd.org Mon Nov 25 09:05:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AA0211CD8B1 for ; Mon, 25 Nov 2019 09:05:48 +0000 (UTC) (envelope-from egypcio@gmail.com) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47M1NC6Qhfz49xQ for ; Mon, 25 Nov 2019 09:05:47 +0000 (UTC) (envelope-from egypcio@gmail.com) Received: by mail-yb1-xb33.google.com with SMTP id n3so2006084ybm.7 for ; Mon, 25 Nov 2019 01:05:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zYKYJ2OmyzxR9mWiywmpa2HxS8ZfCbytDf8cdXDpSU8=; b=e+LlhDGC8AY2bMtKpdpOhyRwBUx1sHgJRkCLVcqqHDn7TpAi+X3KiURixRQC8q7415 2TzcQ/eIqtjXFdVbjCR8qU5YQd72vvaIEW7q+V+GoMbghkSX6ejQwvgCW1VrZvy0bUgv b7UI4+DryiEVJNErvHRizo/E/SHhnDqWelWTPjA+eNQQJC8C5niskrOanLJVJihQQuSG phXDdDlQvwD+Rxbr6tmWCfd6iSWMGu2mG1cdLqS0mbiL3BEvOEwfZ72xA7WZngFTRGHW b3PKCEtzLGQlSea1TG35KQKM7otauUZJADOHt4heHQVfQtILk20FP2lv3yya4cbxjuvM Ym/Q== X-Gm-Message-State: APjAAAW3WXHydyv5cFhoCmdiFkySgLZyKpd2kywVH8b3/uxI9LXOOdWo lklsAWapKkl2/N9cRNtH/JzDSL5LvWF1yd+aLIh4HQ== X-Google-Smtp-Source: APXvYqwr10YIQwgMgPD+gWlSUNAtyl3N4ca4R9qVIVd/YoIHvvcFuBCDOV9upF4SqyYUb23EkumvnImX+nKpUI18pVs= X-Received: by 2002:a25:7452:: with SMTP id p79mr22708175ybc.462.1574672745844; Mon, 25 Nov 2019 01:05:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Vin=C3=ADcius_Zavam?= Date: Mon, 25 Nov 2019 09:05:34 +0000 Message-ID: Subject: Fwd: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized) To: freebsd-current@freebsd.org X-Rspamd-Queue-Id: 47M1NC6Qhfz49xQ X-Spamd-Bar: - X-Spamd-Result: default: False [-1.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; URI_COUNT_ODD(1.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; FORGED_SENDER(0.30)[egypcio@googlemail.com,egypcio@gmail.com]; IP_SCORE(0.00)[ip: (-9.42), ipnet: 2607:f8b0::/32(-2.27), asn: 15169(-1.96), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[egypcio@googlemail.com,egypcio@gmail.com]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[3.3.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 09:05:48 -0000 as this one also hits HEAD, I am forwarding this email to current@. ---------- Forwarded message --------- Von: Vin=C3=ADcius Zavam Date: Do., 21. Nov. 2019 um 12:22 Uhr Subject: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized) To: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242137 From owner-freebsd-current@freebsd.org Mon Nov 25 14:06:22 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CFBED1AD84A for ; Mon, 25 Nov 2019 14:06:22 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47M8314kjtz4SGN for ; Mon, 25 Nov 2019 14:06:21 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: by mail-lj1-x243.google.com with SMTP id k15so16024037lja.3 for ; Mon, 25 Nov 2019 06:06:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=xET3eZVyqXcbuGcTFi9PibYck/vB3i51OWlYxv0mMQM=; b=Hg8hblOoRlwaj5YisQYYVWTr4WQ6BW2aJJcdT76YkEffycMsGZ+SSwxtw1fM4mQBPI bpFX8UTUMz6B+0NTJmgrmQUMyivVIXMgcrm6xaxlVNCqYm9D8uhrbhBPTJWtdZ1RVCas e+NvwinKWihWMQK33uoFd3Lox7ZtOvvfeS7WAxyeOdCslXmUVQ9MuKFT/oJsnAyiekmW GVMJw7J7M+svTrDS+HdtbHLiNRP3vtYh8znnXN4i3RLNBS1obaUrCO56lNKHUZKkagE/ Hwsw9u+il3irDgh9K/b1M6x99RHkHgAiuYvBObBbAoG2fs7b2rnqjJMWCYaWnMsOVG8s rTjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=xET3eZVyqXcbuGcTFi9PibYck/vB3i51OWlYxv0mMQM=; b=YkMBuCQG3144AA8kvUW5MCG1p7vg5eXBFaugD3iL6AxEjI6Osf7SRFRSnppNRcMBpk doWxuKfJQRfKHDc1qNX7wuBuBrA+c8d8nvuNDxsfXl4bxl4mRLkVzmCNtUvIpSpAFS9z FZuEzDwlcqzXun38/YNx5JA+BcgR0nYAt9DxHd2xs5apsL7tgy+QRDCI1bv6v13dt+2J 0pOXeFI81wKp3mnn0XX0ui3o3jYoUSU5vwl7EaBC/NUv3c2aIgdeGJaTuLCnouCafALH 3sr8bK4ecvMQeaIMzjaaXQXRyzpgPprdlCdz4+8eaHMX2gXGvog66Mfzabdk+lmZ11uM bc/A== X-Gm-Message-State: APjAAAVUkZCxzSjueOtA6vyOuIWY9I206oAQ6oNgvwz8KURgyR+a0/aH W7WO1gEpSEli4mLldEdchBBjow8gq1M= X-Google-Smtp-Source: APXvYqx5XFCYfNN9xpAvz0/DiPvUIBFbe5Tyd2esuYhpqPSd9d8MNrCjRSmS9TbGo0Tszi/tDvRnzw== X-Received: by 2002:a2e:99c2:: with SMTP id l2mr22497563ljj.145.1574690777559; Mon, 25 Nov 2019 06:06:17 -0800 (PST) Received: from [192.168.1.2] ([46.48.69.183]) by smtp.gmail.com with ESMTPSA id 144sm3726947lfi.67.2019.11.25.06.06.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Nov 2019 06:06:15 -0800 (PST) To: freebsd-current@freebsd.org From: Ruslan Garipov Subject: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL Message-ID: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> Date: Mon, 25 Nov 2019 19:06:11 +0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47M8314kjtz4SGN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Hg8hblOo; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ruslanngaripov@gmail.com designates 2a00:1450:4864:20::243 as permitted sender) smtp.mailfrom=ruslanngaripov@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.75), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.96), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[3.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 14:06:22 -0000 Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished successfully on the build machine, I get there, for example, /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/install program having the shlxq instruction (one from the BMI2 instruction set extensions). This eventually causes make installkernel and make installworld to fail with SIGILL on a virtual machine which must consume built world and kernel, and which is hosted on another ESXi instance, with older physical CPU (read: with CPU not implementing shlxq). The build machine (FreeBSD 13.0-CURRENT r354802) builds (x)install using the following commands (a part of buildworld): $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD -MF.depend.xinstall.o -MTxinstall.o -std=gnu99 -Wno-format-zero-length -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/usr.bin/xinstall/xinstall.c -o xinstall.o $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD -MF.depend.getid.o -MTgetid.o -std=gnu99 -Wno-format-zero-length -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -c /usr/src/contrib/mtree/getid.c -o getid.o $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -std=gnu99 -Wno-format-zero-length -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -static -L/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib -o xinstall xinstall.o getid.o -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/libmd -lmd -legacy This produces xintstall with `shlxq`s: $ llvm-objdump --disassemble xinstall | grep -c shlxq 135 I believe statically linked /usr/lib/libmd.a is a stuff which brings `shlxq`s into the xinstall. I didn't examine it further, sorry... My question is: is it possible to buildworld without issuing instructions which are native for the host CPU? I have neither /etc/make.conf, nor /etc/src.conf on the build machine. Is it possible at all for FreeBSD CURRENT to be built outside a host and installed on the host later? Just as a reference: My build machine has Intel(R) Xeon(R) Gold 6150 CPU that supports BMI2: # cpucontrol -i 7 /dev/cpuctl0 cpuid level 0x7: 0x00000000 0xd19f6ffb 0x00000018 0xbc000000 (Bit 08 in EBX is set) , and a consuming machine has Intel(R) Xeon(R) CPU E5-4617 CPU that doesn't support BMI2: # cpucontrol -i 7 /dev/cpuctl0 cpuid level 0x7: 0x00000000 0x00000002 0x00000000 0xbc000000 (Bit 08 in EBX is unset). Both machines install kernel and world without any problem, if they were built locally. Thanks! -- Yours truly, Ruslan Garipov . ---------------------------------------------- MinGW-w64 developer, with write after approval GEDKeeper collaborator From owner-freebsd-current@freebsd.org Mon Nov 25 15:15:35 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 079961AFCDD for ; Mon, 25 Nov 2019 15:15:35 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660069.outbound.protection.outlook.com [40.107.66.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47M9Zs1LXTz4XJP for ; Mon, 25 Nov 2019 15:15:32 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Tl7aiM1DNBOxf5j8x/am0ilghibUfcAQt23gJVzvdvdhpW5hRsFcVw5JZFkrNuh2w5nGGKPtmgVVr6BPu/JljElr5Q3hET47YveMWB8mc2r3FZC6KW3S2S9vcxIcYqbub/gp0ZeED8oIqw0JNGAEGTyH5D+14UkY3exIdkTVDWIITI7KQaq4iKcbgm5WOYhmE841BircFsmIFa+e2Mpexbs05o1EZXapIQvP2D/QIe0EA1gUso/NzNerQ80rF7Ei6UrEmEsLnLfOp3YA+a4ovM97dHfg0znI+4Kh9zfoqyZoe9SJKTkV2kZQtGLUzLOBy5NzqJss/s8nSbxwHN4n2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=b2Xqayar/ILZrdEmfTk8YQYpSELgqTP5ekCGKdvWqlM=; b=T8FCED5lnORvCgJdCpU6MvcyyqA6nAwKaMCIEe3uMkRs0oZVpACiF0vI0RYlwnDnOEXeH81I5dV24T3CkZLMXK+lqLtAU7kyzgfigp4aI2gL6fAOryYkESSV6Fqulj88NyY+UUllpXTcUovcwpBsIGjTKIzPa+h/W4zBD8Db0dlcjYR7WQn5hTnZZSCsyGWvoAwMOl0Ewhyj82v/Uk7Dx1+KJ9mdkfbBaUSQGSddr5/M95k7CzJqrOMNKnGax6U6XI51boRrUrXHdS631basFzInTI+zIhspZHC9qj3kWp3x5oVDEawzAN7M6rIGO+HXgL74iFpkbtzmTnNi7KKbzQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uoguelph.ca; dmarc=pass action=none header.from=uoguelph.ca; dkim=pass header.d=uoguelph.ca; arc=none Received: from YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM (52.132.69.153) by YQBPR0101MB1284.CANPRD01.PROD.OUTLOOK.COM (52.132.71.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.22; Mon, 25 Nov 2019 15:15:29 +0000 Received: from YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM ([fe80::9504:a50d:ee12:b75]) by YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM ([fe80::9504:a50d:ee12:b75%5]) with mapi id 15.20.2474.023; Mon, 25 Nov 2019 15:15:29 +0000 From: Rick Macklem To: "freebsd-current@FreeBSD.org" Subject: merge of NFSv4.2 support into head/current Thread-Topic: merge of NFSv4.2 support into head/current Thread-Index: AQHVo6GRwVWVdgDktki1lUrbSQEWpg== Date: Mon, 25 Nov 2019 15:15:29 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:569:fac0:e900:b4af:a03b:7354:e4d6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f7232f0a-a3c4-451b-60eb-08d771ba4ee9 x-ms-traffictypediagnostic: YQBPR0101MB1284: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 0232B30BBC x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(346002)(136003)(396003)(366004)(199004)(189003)(5660300002)(2501003)(46003)(186003)(99286004)(7736002)(6116002)(8676002)(55016002)(33656002)(305945005)(81166006)(316002)(8936002)(786003)(25786009)(5640700003)(256004)(7696005)(478600001)(6436002)(14454004)(2351001)(71200400001)(71190400001)(74316002)(81156014)(6916009)(9686003)(6506007)(86362001)(64756008)(102836004)(66446008)(66556008)(52536014)(66946007)(66476007)(2906002)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:YQBPR0101MB1284; H:YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: fGcFPVBJ0/h3tLjSCbqEFNOiypHroZqJLWNN4fBc0J985Ux9JE57iSVesm1iYpNv/og3l1zLxhp4GBN0CznO9eTpCPhDAcRhCXyt2mhS2+q0p2+n15+A6n5IWo4W0371sHTOc3daw9WJCEtgM7vB0anA+m26C53m4A9TqyOqvcEzMBBYh3gA3Sq+sJt4FFfEnyRdxoIhvhUXZHX6czUqqdR3dmJxrZ0OkQmQTjSLApM5I6sT72ct0ioDwNxHIf7rwyrgorni1eU3dK3ffExIA5WPydUIZhGmSlO2vOZEtQLNVFpzQ41ZzqBRDimRWBY76JptuERgy3Q4sYHXJv1LR0dQav0sDviV5jgfOU8dYxSNBREhCJVd27tNoaDmia5aa1AhRl8JJQFii9AcC0H8PJF7LoCsGRU8MoFTroV/i4p2GHoKYGEfxJ17l5JG0VoA x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: f7232f0a-a3c4-451b-60eb-08d771ba4ee9 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Nov 2019 15:15:29.7368 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: goA+vTkpAumGQRRD1RYevkZpFxGbz4xCulJO+UjyvWyWYBQJjraqI4rSqD0Ov+z2uekZPIKCzbdJGHx3ouRncA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: YQBPR0101MB1284 X-Rspamd-Queue-Id: 47M9Zs1LXTz4XJP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.66.69 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-4.65 / 15.00]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[uoguelph.ca]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-1.35)[ipnet: 40.64.0.0/10(-3.85), asn: 8075(-2.83), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[69.66.107.40.list.dnswl.org : 127.0.3.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; ARC_ALLOW(-1.00)[i=1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 15:15:35 -0000 Hi,=0A= =0A= I have completed development and a testing cycle for the NFSv4.2 (RFC-7862)= =0A= code in base/projects/nfsv42 on subversion.=0A= =0A= NFSv4.2 is a minor revision to NFSv4.1 and adds support for the following o= ptional=0A= features:=0A= - lseek(SEEK_DATA/SEEK_HOLE)=0A= - posix_fallocate()=0A= - posix_fadvise(POSIX_FADV_WILLNEED/POSIX_FADV_DONTNEED)=0A= - Server side copy of byte ranges between two files on the same NFS mount= =0A= point when the copy_file_range(2) syscall is used.=0A= - Extended attribute support as specified by RFC-8276.=0A= (There are some other optional features, but I do not intend to implement t= hose=0A= at this time.)=0A= =0A= Although this patch is fairly large, it should not affect the other version= s of=0A= NFS.=0A= =0A= If anyone would like to do testing of it now, all you need is a fairly curr= ent=0A= FreeBSD-current system, with the kernel replaced by one built from the=0A= sources found in the above projects area. (And then you specify "minorversi= on=3D2"=0A= as a mount option.=0A= =0A= If anyone sees a problem with merging this code into head/current over=0A= the next few weeks, please let me know.=0A= =0A= Thanks, rick=0A= =0A= From owner-freebsd-current@freebsd.org Mon Nov 25 17:30:10 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 74B171B3403 for ; Mon, 25 Nov 2019 17:30:10 +0000 (UTC) (envelope-from SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 47MDZ90mg5z4fpQ for ; Mon, 25 Nov 2019 17:30:08 +0000 (UTC) (envelope-from SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2437F28459; Mon, 25 Nov 2019 18:30:06 +0100 (CET) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id B5A3A28461; Mon, 25 Nov 2019 18:30:04 +0100 (CET) Subject: Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL To: Ruslan Garipov , freebsd-current@freebsd.org References: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Mon, 25 Nov 2019 18:30:04 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47MDZ90mg5z4fpQ X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.89)[ip: (0.40), ipnet: 94.124.104.0/21(0.20), asn: 42000(3.75), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.995,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(1.00)[0.996,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 17:30:10 -0000 Ruslan Garipov wrote on 2019/11/25 15:06: > Hello. > > I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast > virtual machine for other ones (all the virtual machines are hosted on > VMware EXSi hypervisors, which have different physical CPUs). > > After `make -j16 buildworld` has finished successfully on the build > machine, I get there, for example, > /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/install program having the > shlxq instruction (one from the BMI2 instruction set extensions). This > eventually causes make installkernel and make installworld to fail with > SIGILL on a virtual machine which must consume built world and kernel, > and which is hosted on another ESXi instance, with older physical CPU > (read: with CPU not implementing shlxq). > > The build machine (FreeBSD 13.0-CURRENT r354802) builds (x)install using > the following commands (a part of buildworld): > > $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree > -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD > -MF.depend.xinstall.o -MTxinstall.o -std=gnu99 -Wno-format-zero-length > -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include > -c /usr/src/usr.bin/xinstall/xinstall.c -o xinstall.o > $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree > -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD > -MF.depend.getid.o -MTgetid.o -std=gnu99 -Wno-format-zero-length > -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include > -c /usr/src/contrib/mtree/getid.c -o getid.o > $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree > -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -std=gnu99 > -Wno-format-zero-length -Qunused-arguments > -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -static > -L/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib -o xinstall xinstall.o > getid.o -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/libmd -lmd -legacy > > This produces xintstall with `shlxq`s: > > $ llvm-objdump --disassemble xinstall | grep -c shlxq > 135 > > I believe statically linked /usr/lib/libmd.a is a stuff which brings > `shlxq`s into the xinstall. I didn't examine it further, sorry... > > My question is: is it possible to buildworld without issuing > instructions which are native for the host CPU? I have neither > /etc/make.conf, nor /etc/src.conf on the build machine. Is it possible > at all for FreeBSD CURRENT to be built outside a host and installed on > the host later? > > Just as a reference: > > My build machine has Intel(R) Xeon(R) Gold 6150 CPU that supports BMI2: > > # cpucontrol -i 7 /dev/cpuctl0 > cpuid level 0x7: 0x00000000 0xd19f6ffb 0x00000018 0xbc000000 > > (Bit 08 in EBX is set) > > , and a consuming machine has Intel(R) Xeon(R) CPU E5-4617 CPU that > doesn't support BMI2: > > # cpucontrol -i 7 /dev/cpuctl0 > cpuid level 0x7: 0x00000000 0x00000002 0x00000000 0xbc000000 > > (Bit 08 in EBX is unset). > > Both machines install kernel and world without any problem, if they were > built locally. I didn't tried this with current but I am using it with stable (11.3 at this time). Building on Xeon E3-1240v3 and installing on many different machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, some 10 years old Intel Pentium. So at least it worked in the past (11.3 amd64). Did you use this workflow in the past / did it work? I remember some issue in the past which was (accidentaly?) fixed by running "make buildworld && make builkernel && make installkernel && make installworld" on the build host (to some different DESTDIR) and then "make installkernel && make installworld" on the target host (build machine is shared via NFS) Miroslav Lachman From owner-freebsd-current@freebsd.org Mon Nov 25 18:26:53 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B1DB81B5572 for ; Mon, 25 Nov 2019 18:26:53 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: from mail-lj1-x241.google.com (mail-lj1-x241.google.com [IPv6:2a00:1450:4864:20::241]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MFqc4xDLz3GY1 for ; Mon, 25 Nov 2019 18:26:52 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: by mail-lj1-x241.google.com with SMTP id m4so17047992ljj.8 for ; Mon, 25 Nov 2019 10:26:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=e7WAluMMQSduInbIZQ00awvJQkNGWx2mOA9g/CNjQUw=; b=jecoH1nDMki8X/q0aDY8qHrDRq+1D+pT5sqth7QeDAGfNSR910bcHri6ejqwU4Ik9v 9+vqPDRbjakHC4DKbfX+SC46Dpfr+pE7LrCGFr5yimszd6xSFQLr4uoKQpMx33q1GJZa hGFcmaeBKMULwwOemndOnX5UZsLcB2ht7zZIE1rt8S+nI7KJ8j3gOIDJFGKOoLNnjCQR A+bQNbQr2WAGsyeXub4+2s4ngdwxKlmbq4EHSUTTqOGdSRHSBk4ygd5Ll2+OM/AT3Gy+ KZxTk1SJlwcIJ8sJeYqq1mV7TQzz5TCaqB1kOoxoNKKbD8aavEUItwXBfF/9YkUryPIE MNng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=e7WAluMMQSduInbIZQ00awvJQkNGWx2mOA9g/CNjQUw=; b=LPGOewfhQsvjTzewGt3dD9WDyVclMebH6LwL/IacxpC/1HFHWivaPV2KBn1pb1DqJj n32RnzCetv9YfjLUTR59P0Mf1nhbjKv9Hd2RKAafZea/Tlsfp/GcDbpqyweL8bYYKQSJ xZTQEHI1kowMmieSJo46lbjjX7t9nxW7n0n0xSGBIYKDOqrdGWyZBl9Ch/4fosnBNnC0 1wDho8ICm1NDZ2wQPeMt0bL+ED9NXVNe//dj5sOKDAkrA3aVJvZr4vABjmmag7HQFffP twos/B9UnnjCRm2uwRWxzjuT0ctuxUUfZMUD5W5jQLULizjJbmJk/33CC8FzHJCd96G6 Rw/Q== X-Gm-Message-State: APjAAAU4roTN8OgmcusV6radShi4Almx5Vc2EzokNRui4BwANVvzTg6D jScSqpMDdEo7Uj50+AjxN9iQ9GTrMFk= X-Google-Smtp-Source: APXvYqyG0RzzkuMiWyuewqnQMi1103U1DlgVigb+SbxwFD3FEnRBlJqlut3zY+uP5FDuzG1xcC/M9Q== X-Received: by 2002:a05:651c:1117:: with SMTP id d23mr23871052ljo.90.1574706410524; Mon, 25 Nov 2019 10:26:50 -0800 (PST) Received: from [192.168.1.2] ([46.48.69.183]) by smtp.gmail.com with ESMTPSA id b28sm4983303ljp.9.2019.11.25.10.26.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Nov 2019 10:26:49 -0800 (PST) Subject: Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org References: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> From: Ruslan Garipov Message-ID: Date: Mon, 25 Nov 2019 23:26:46 +0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47MFqc4xDLz3GY1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=jecoH1nD; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ruslanngaripov@gmail.com designates 2a00:1450:4864:20::241 as permitted sender) smtp.mailfrom=ruslanngaripov@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.89), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.96), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 18:26:53 -0000 On 11/25/2019 10:30 PM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 15:06: >> Hello. >> >> I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast >> virtual machine for other ones (all the virtual machines are hosted on >> VMware EXSi hypervisors, which have different physical CPUs). >> >> After `make -j16 buildworld` has finished successfully on the build >> machine, I get there, for example, >> /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/install program having the >> shlxq instruction (one from the BMI2 instruction set extensions). This >> eventually causes make installkernel and make installworld to fail with >> SIGILL on a virtual machine which must consume built world and kernel, >> and which is hosted on another ESXi instance, with older physical CPU >> (read: with CPU not implementing shlxq). >> >> The build machine (FreeBSD 13.0-CURRENT r354802) builds (x)install using >> the following commands (a part of buildworld): >> >> $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree >> -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD >> -MF.depend.xinstall.o -MTxinstall.o -std=gnu99 -Wno-format-zero-length >> -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include >> -c /usr/src/usr.bin/xinstall/xinstall.c -o xinstall.o >> $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree >> -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -MD >> -MF.depend.getid.o -MTgetid.o -std=gnu99 -Wno-format-zero-length >> -Qunused-arguments -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include >> -c /usr/src/contrib/mtree/getid.c -o getid.o >> $ cc -O2 -pipe -O2 -march=x86-64 -pipe -I/usr/src/contrib/mtree >> -I/usr/src/lib/libnetbsd -DHAVE_STRUCT_STAT_ST_FLAGS=1 -std=gnu99 >> -Wno-format-zero-length -Qunused-arguments >> -I/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include -static >> -L/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib -o xinstall xinstall.o >> getid.o -L/usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/libmd -lmd -legacy >> >> This produces xintstall with `shlxq`s: >> >> $ llvm-objdump --disassemble xinstall | grep -c shlxq >> 135 >> >> I believe statically linked /usr/lib/libmd.a is a stuff which brings >> `shlxq`s into the xinstall. I didn't examine it further, sorry... >> >> My question is: is it possible to buildworld without issuing >> instructions which are native for the host CPU? I have neither >> /etc/make.conf, nor /etc/src.conf on the build machine. Is it possible >> at all for FreeBSD CURRENT to be built outside a host and installed on >> the host later? >> >> Just as a reference: >> >> My build machine has Intel(R) Xeon(R) Gold 6150 CPU that supports BMI2: >> >> # cpucontrol -i 7 /dev/cpuctl0 >> cpuid level 0x7: 0x00000000 0xd19f6ffb 0x00000018 0xbc000000 >> >> (Bit 08 in EBX is set) >> >> , and a consuming machine has Intel(R) Xeon(R) CPU E5-4617 CPU that >> doesn't support BMI2: >> >> # cpucontrol -i 7 /dev/cpuctl0 >> cpuid level 0x7: 0x00000000 0x00000002 0x00000000 0xbc000000 >> >> (Bit 08 in EBX is unset). >> >> Both machines install kernel and world without any problem, if they were >> built locally. > > I didn't tried this with current but I am using it with stable (11.3 at > this time). Building on Xeon E3-1240v3 and installing on many different > machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, > some 10 years old Intel Pentium. > So at least it worked in the past (11.3 amd64). Did you use this > workflow in the past / did it work? No, unfortunately I didn't. Always built world/kernel on target host. > I remember some issue in the past which was (accidentaly?) fixed by > running "make buildworld && make builkernel && make installkernel && > make installworld" on the build host (to some different DESTDIR) and > then "make installkernel && make installworld" on the target host (build > machine is shared via NFS) Therefore, this trick somehow "fixes" /usr/obj shared on the build machine? I'll try this later. Thanks! > > Miroslav Lachman > From owner-freebsd-current@freebsd.org Mon Nov 25 18:27:03 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B95891B55A4 for ; Mon, 25 Nov 2019 18:27:03 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MFqp67fvz3Gd0 for ; Mon, 25 Nov 2019 18:27:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id ZJ4bihqBZRnrKZJ4didWgk; Mon, 25 Nov 2019 11:27:00 -0700 X-Authority-Analysis: v=2.3 cv=L7FjvNb8 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=PDcaXgylx7MA:10 a=MeAgGD-zjQ4A:10 a=mK_AVkanAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=fafuQvmIW6Ifzg_L1JIA:9 a=QEXdDO2ut3YA:10 a=7-lTe5PpE-NjhZ64FWgA:9 a=s9xOrodDKr_4wJWa:21 a=_W_S_7VecoQA:10 a=3gWm3jAn84ENXaBijsEo:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from android-5582cadb5e5ad825.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 43A2A8D2; Mon, 25 Nov 2019 10:26:57 -0800 (PST) Date: Mon, 25 Nov 2019 10:01:58 -0800 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Subject: Re: Fwd: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized) To: freebsd-current@freebsd.org, =?ISO-8859-1?Q?Vin=EDcius_Zavam?= From: Cy Schubert Message-ID: <934EBF76-8CEF-423D-A0A9-B66407FB66F6@cschubert.com> X-CMAE-Envelope: MS4wfPdtCVQUyO6sH0b09WNhQ070N4jQ//UJtz7NVPAtIJoPp/HZewKhoTEsheqzswr54zTWiqIAn1XRNpNr6cJLrqcWDtKbTnuxp4gHvuYnnPasBmn0e7I7 DjCJe8M1vQtFjwauBkt+N6XTAhgJNTOZMtSoJsXXhFPulvpVkzI7IoY3XglE7xyfNVNdZCjrgpE/B9A10kZ3+KGx8pLuMxL9qD6j4w0lM/wK2uTwL81Cy8n5 X-Rspamd-Queue-Id: 47MFqp67fvz3Gd0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.137) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-3.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[233.154.66.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11,17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; URI_COUNT_ODD(1.00)[9]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[137.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.28)[ip: (-5.87), ipnet: 64.59.128.0/20(-3.06), asn: 6327(-2.37), country: CA(-0.09)]; FROM_EQ_ENVFROM(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 18:27:03 -0000 On November 25, 2019 1:05:34 AM PST, "Vin=C3=ADcius Zavam" wrote: >as this one also hits HEAD, I am forwarding this email to current@=2E > >---------- Forwarded message --------- >Von: Vin=C3=ADcius Zavam >Date: Do=2E, 21=2E Nov=2E 2019 um 12:22 Uhr >Subject: [NTP] "Unexpected origin timestamp 0xe180e455=2Ed15bf3fb does >not >match aorg 0000000000=2E00000000 from server" (kernel reports TIME_ERROR: >0x41: Clock Unsynchronized) >To: > > >https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D242137 >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" I don't have access to bugzilla through this phone (I haven't memorized my= gibberish password) so I'll answer here for now and update the PR when I g= et to a real keyboard with internet access in a few hours=2E I suspect your clock is drifting enough over that it's stepping the clock = and starting over=2E What are the contents of /var/db/ntpd=2Edrift on your affected and unaffe= cted machines in the PR? I'd also be interested in seeing ntpq -p outputs side-by-side=2E --=20 Pardon the typos and autocorrect, small keyboard in use=2E=20 Cy Schubert FreeBSD UNIX: Web: https://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-current@freebsd.org Mon Nov 25 19:09:57 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C77281B6B50 for ; Mon, 25 Nov 2019 19:09:57 +0000 (UTC) (envelope-from SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 47MGnJ74sCz3KPn for ; Mon, 25 Nov 2019 19:09:56 +0000 (UTC) (envelope-from SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6300028416; Mon, 25 Nov 2019 20:09:54 +0100 (CET) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9032428411; Mon, 25 Nov 2019 20:09:53 +0100 (CET) Subject: Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL To: Ruslan Garipov , freebsd-current@freebsd.org References: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <41b921c4-568f-5bd1-ae0f-1d85d750a8c7@quip.cz> Date: Mon, 25 Nov 2019 20:09:53 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47MGnJ74sCz3KPn X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.89)[ip: (0.39), ipnet: 94.124.104.0/21(0.20), asn: 42000(3.74), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.988,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.99)[0.994,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=C6/G=ZR=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 19:09:57 -0000 Ruslan Garipov wrote on 2019/11/25 19:26: [...] >> I didn't tried this with current but I am using it with stable (11.3 at >> this time). Building on Xeon E3-1240v3 and installing on many different >> machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, >> some 10 years old Intel Pentium. >> So at least it worked in the past (11.3 amd64). Did you use this >> workflow in the past / did it work? > No, unfortunately I didn't. Always built world/kernel on target host. > >> I remember some issue in the past which was (accidentally?) fixed by >> running "make buildworld && make builkernel && make installkernel && >> make installworld" on the build host (to some different DESTDIR) and >> then "make installkernel && make installworld" on the target host (build >> machine is shared via NFS) > Therefore, this trick somehow "fixes" /usr/obj shared on the build > machine? I'll try this later. Thanks! Yes, I think so. But I am not a developer nor I know much about how build process works. Miroslav Lachman From owner-freebsd-current@freebsd.org Mon Nov 25 19:57:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 677431B82AF for ; Mon, 25 Nov 2019 19:57:48 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MHrX0DYlz3N61 for ; Mon, 25 Nov 2019 19:57:47 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Message-ID:Subject:To:From:Date:Content-Type:MIME-Version: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=hI6i7cHIRLNeQzwqMzAUqHE+aSYjvIF2aUAcNjLAOWw=; b=OH5Nw8hAOp/ZSNS7ms6v8QBJ5V IoRZ4+TlhOMrvW9xUBN1uQ5A8vl0ekClg43ZsuvB6XMFYMlVWm/T4B2r5DPbi1VkRPDbAzqeGWkIt X9V888BBbYYJxOslxvBBpHPL+TNNRUewM3UPzynDxujIOCBDcez4kgdaE26Wg2fy+KfCO+23Wiurl P/J6fZwaRCSjj9JLcpIFCIxf2cRx4QsyWC1m2/KbN2AHlRtvAKzm1VVErQ0WfEvSsFIVPGLfPFFG9 8+KpdTIA+tVKtm3I4Swpfsn03+qPVyz63wFDJH2XLe6tdypMai0vxR0iVLYbeFYB/nrGC8E2ZBt6F jI00habw==; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:bb:dcff:fe50:d900]:16080 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3 (FreeBSD)) (envelope-from ) id 1iZKTH-000Jnh-2H for freebsd-current@freebsd.org; Mon, 25 Nov 2019 13:56:31 -0600 Received: from 2600:1700:210:b180:1c79:519a:510:f3cb by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 25 Nov 2019 13:56:28 -0600 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_a19731d0d19c657b062517bcba25301f"; micalg=pgp-sha256 Date: Mon, 25 Nov 2019 13:56:28 -0600 From: Larry Rosenman To: Freebsd current Subject: ng_snd_item: I thought(?) we fixed this :( r354843 Message-ID: <87a22130604a655dabcd8e7e812e83bb@FreeBSD.org> X-Sender: ler@FreeBSD.org User-Agent: Roundcube Webmail/1.3.10 X-Rspamd-Queue-Id: 47MHrX0DYlz3N61 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.64 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.81)[-0.814,0]; NEURAL_HAM_LONG(-0.82)[-0.823,0]; ASN(0.00)[asn:8166, ipnet:192.147.25.0/24, country:US] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 19:57:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_a19731d0d19c657b062517bcba25301f Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed I thought someone, somewhere fixed this, but it's hit again. core *IS* available, and I can give access as well. Unread portion of the kernel message buffer: panic: ng_snd_item: 42 != 1414 cpuid = 0 time = 1574707403 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0215a304d0 vpanic() at vpanic+0x17e/frame 0xfffffe0215a30530 panic() at panic+0x43/frame 0xfffffe0215a30590 ng_snd_item() at ng_snd_item+0x482/frame 0xfffffe0215a305d0 ng_ether_output() at ng_ether_output+0x5e/frame 0xfffffe0215a30600 ether_output() at ether_output+0x661/frame 0xfffffe0215a306a0 arpintr() at arpintr+0xf0c/frame 0xfffffe0215a30840 netisr_dispatch_src() at netisr_dispatch_src+0x94/frame 0xfffffe0215a308c0 ether_demux() at ether_demux+0x15e/frame 0xfffffe0215a308f0 ng_ether_rcv_upper() at ng_ether_rcv_upper+0xb2/frame 0xfffffe0215a30940 ng_apply_item() at ng_apply_item+0xa4/frame 0xfffffe0215a309c0 ng_snd_item() at ng_snd_item+0x2b0/frame 0xfffffe0215a30a00 ng_apply_item() at ng_apply_item+0xa4/frame 0xfffffe0215a30a80 ng_snd_item() at ng_snd_item+0x2b0/frame 0xfffffe0215a30ac0 ng_ether_input() at ng_ether_input+0x4c/frame 0xfffffe0215a30af0 ether_nh_input() at ether_nh_input+0x2c9/frame 0xfffffe0215a30b40 netisr_dispatch_src() at netisr_dispatch_src+0x94/frame 0xfffffe0215a30bc0 ether_input() at ether_input+0x58/frame 0xfffffe0215a30c10 bce_intr() at bce_intr+0x6b7/frame 0xfffffe0215a30c90 ithread_loop() at ithread_loop+0x1c6/frame 0xfffffe0215a30cf0 fork_exit() at fork_exit+0x80/frame 0xfffffe0215a30d30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0215a30d30 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 6d7h53m25s Dumping 27613 out of 131029 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 55 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct pcpu, (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 #1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:392 #2 0xffffffff804bbc20 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:479 #3 0xffffffff804bc076 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:908 #4 0xffffffff804bbdd3 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:835 #5 0xffffffff8262f442 in ng_snd_item (item=0xfffff813c2e41280, flags=0) at /usr/src/sys/netgraph/ng_base.c:2252 #6 0xffffffff82643c0e in ng_ether_output (ifp=, mp=0xfffffe0215a30658) at /usr/src/sys/netgraph/ng_ether.c:294 #7 0xffffffff805c44e1 in ether_output (ifp=, m=0xfffff80be7cfe500, dst=0xfffffe0215a30800, ro=) at /usr/src/sys/net/if_ethersubr.c:430 #8 0xffffffff805ded6c in in_arpinput (m=) at /usr/src/sys/netinet/if_ether.c:1144 #9 arpintr (m=0xfffff80be7cfe500) at /usr/src/sys/netinet/if_ether.c:747 #10 0xffffffff805cff94 in netisr_dispatch_src (proto=4, source=0, m=0xfffff80be7cfe500) at /usr/src/sys/net/netisr.c:1127 #11 0xffffffff805c47ce in ether_demux (ifp=0xfffff8107db75800, m=) at /usr/src/sys/net/if_ethersubr.c:916 #12 0xffffffff82644042 in ng_ether_rcv_upper (hook=, item=) at /usr/src/sys/netgraph/ng_ether.c:744 #13 0xffffffff8262f514 in ng_apply_item (node=0xfffff8106c02c200, item=0xfffff813c2e41280, rw=0) at /usr/src/sys/netgraph/ng_base.c:2403 #14 0xffffffff8262f270 in ng_snd_item (item=0xfffff813c2e41280, flags=0) at /usr/src/sys/netgraph/ng_base.c:2320 #15 0xffffffff8262f514 in ng_apply_item (node=0xfffff8012c69de00, item=0xfffff813c2e41280, rw=0) at /usr/src/sys/netgraph/ng_base.c:2403 #16 0xffffffff8262f270 in ng_snd_item (item=0xfffff813c2e41280, flags=0) at /usr/src/sys/netgraph/ng_base.c:2320 #17 0xffffffff82643c9c in ng_ether_input (ifp=, mp=0xfffffe0215a30b18) at /usr/src/sys/netgraph/ng_ether.c:255 #18 0xffffffff805c5a59 in ether_input_internal (ifp=0xfffff8107db75800, m=0xfffff80be7cfe500) at /usr/src/sys/net/if_ethersubr.c:654 #19 ether_nh_input (m=) at /usr/src/sys/net/if_ethersubr.c:735 #20 0xffffffff805cff94 in netisr_dispatch_src (proto=5, source=0, m=0xfffff80be7cfe500) at /usr/src/sys/net/netisr.c:1127 #21 0xffffffff805c4c48 in ether_input (ifp=0xfffff8107db75800, m=0x0) at /usr/src/sys/net/if_ethersubr.c:824 #22 0xffffffff82455767 in bce_rx_intr (sc=0xfffffe0234fc8000) at /usr/src/sys/dev/bce/if_bce.c:6848 #23 bce_intr (xsc=0xfffffe0234fc8000) at /usr/src/sys/dev/bce/if_bce.c:8017 #24 0xffffffff80485166 in intr_event_execute_handlers (p=, ie=) at /usr/src/sys/kern/kern_intr.c:1148 #25 ithread_execute_handlers (p=, ie=) at /usr/src/sys/kern/kern_intr.c:1161 #26 ithread_loop (arg=) at /usr/src/sys/kern/kern_intr.c:1241 #27 0xffffffff80481ca0 in fork_exit ( callout=0xffffffff80484fa0 , arg=0xfffff8107d1ffcc0, frame=0xfffffe0215a30d40) at /usr/src/sys/kern/kern_fork.c:1059 #28 (kgdb) -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 --=_a19731d0d19c657b062517bcba25301f Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAl3cMe4ACgkQaXyZsatI p33qVgf/QWVLkMBxYwb7luujr3UoTA2mbBA8+U5blD+pPVbdralt0W4NAYtJnzdf HXjO8o4f0AqDBpwiILd1+SorDkpSyCN+smoi1CP9XpiZMbuI/FwBWh0+J+Z08jZp cO16kP+WiiER4XJ/vsznLoW53b8EDLCXyVjnqX5lYGg6hhf32Usur6ZhwNJumBse ltam3ZPoRDT0ShK5z34gbSDsw7auK8/nBdS3WsMczvfJOT5Y3ds1xTgchtCGAxju S99fnmKhXRIFzknJ010ZkIVx2zQ/D5q+3PZ2wx33Al1YEkaJxfVU9NoDEQLGPfLy DXrDECA6BU5a32lEFmgvaGvlFLhFDg== =ulMZ -----END PGP SIGNATURE----- --=_a19731d0d19c657b062517bcba25301f-- From owner-freebsd-current@freebsd.org Mon Nov 25 22:06:06 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BDF721BB6CA for ; Mon, 25 Nov 2019 22:06:06 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021201.me.com (pv50p00im-ztdg10021201.me.com [17.58.6.45]) (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 47MLhY5qxCz40GR for ; Mon, 25 Nov 2019 22:06:05 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021201.me.com (Postfix) with ESMTPSA id 69AA6A40571; Mon, 25 Nov 2019 22:06:03 +0000 (UTC) From: Toomas Soome Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Testing needed:) Message-Id: Date: Tue, 26 Nov 2019 00:06:00 +0200 To: FreeBSD Developers , Current X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-25_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=670 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911250176 X-Rspamd-Queue-Id: 47MLhY5qxCz40GR X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[45.6.58.17.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-4.27), ipnet: 17.58.0.0/20(-2.20), asn: 714(-2.35), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 22:06:06 -0000 Hi! Can someone with arm media file path type of storage device and someone = with apple UEFI 1.10 test https://reviews.freebsd.org/D22553 please:) Other tests are also very welcome:) thanks, toomas= From owner-freebsd-current@freebsd.org Tue Nov 26 04:40:36 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 411431C78A3 for ; Tue, 26 Nov 2019 04:40:36 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MWRl3Kzhz4Lsr for ; Tue, 26 Nov 2019 04:40:35 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id j18so1426255wmk.1 for ; Mon, 25 Nov 2019 20:40:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=K/m8rFFQYtrayzOL4Gb4Izx+TfovLZBnZb1eSuAu94c=; b=PJJfLUFA58s6iyYuSIvkRGs99v0PzvjFuNrjT0WxBkXgxOi+6daClqpSqZyNdhA3fj tPBESw7EiF20PzJGKC1VUrPugyJR+wbPylU+okG738HXCSDsgtK+TZMHKfdABrtml/GU QKmCFK5FLcv0sje62qtdvNmcYgpZ9ijFh9iKvRGXjutebNgRi6U6hqv1jXJQ5g60DynD FvYyKywkMRKhqGwss/SoGBtK+4IJIuzCiKq+d3EXtwO8PQTNRuE7QcmxYfhIun/tHsJI 8NkYZMEYIc38cE9CmuGkrMaLoai2r0pLfk0n4jXcKeaq4nIEzXB9RkIfYtauzb1kRuGE V6mA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=K/m8rFFQYtrayzOL4Gb4Izx+TfovLZBnZb1eSuAu94c=; b=d1pSbA2TRaDmH15l6i9C3+7Z01jDbJ27OXeQ/cjyOCRF8zOEttiG3yf4/XK7t2Fz7d TBD1QoIbLxfXnPeluMxMZYCO00dbS4S1ZxZ1H77uDfBIHzOkjt90wrnD871vfIbl8wzR ndJJeetQ6slOEgpwEpt2ycU1qUXyAlyEklzmnrRHDKvicBarqEBXMijzTdFfkyJc0th9 68xwQI7WGHwz4r7lGcIOKo+rVVmLeSod+J7EDHb72GQrsp1kykXWxzvYGVoKH1wtMU55 RdwtzwBRY2oZTRn8uQZUFUwQF/nD+EaF/aGqS37pmjSv6SO7fQ4WJc4O5bq7n0WOks4v VJ+g== X-Gm-Message-State: APjAAAUC3nvf32/Q03Ex73LftwpfhfmvAxUgJOc3JPLDzTsjDuY983IM CiMSEDdZ5Sqb54woUJFADtKXLJD3bSM= X-Google-Smtp-Source: APXvYqzRPbz3lltXbc714+DhTbx92VoUc+xnEk6yehe7PHWZBp2IGX6JyRjWSwtKL0XRhrNT3k66aw== X-Received: by 2002:a7b:c001:: with SMTP id c1mr2148519wmb.96.1574743232805; Mon, 25 Nov 2019 20:40:32 -0800 (PST) Received: from [192.168.1.7] (host-2-100-169-93.as13285.net. [2.100.169.93]) by smtp.gmail.com with ESMTPSA id 60sm12464603wrn.86.2019.11.25.20.40.31 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Nov 2019 20:40:31 -0800 (PST) To: FreeBSD CURRENT From: Graham Perrin Subject: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk Message-ID: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> Date: Tue, 26 Nov 2019 04:40:30 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 47MWRl3Kzhz4Lsr X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=PJJfLUFA; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::32a as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[93.169.100.2.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-9.46), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.96), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[a.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 04:40:36 -0000 The tail of my most recent run of make -j2 buildkernel KERNCONF=GENERIC-NODEBUG ===> Ports module graphics/gpu-firmware-kmod (all) cd ${PORTSDIR:-/usr/ports}/graphics/gpu-firmware-kmod; env  -u CC -u CXX  -u CPP  -u MAKESYSPATH  -u MK_AUTO_OBJ  -u MAKEOBJDIR MAKEFLAGS="-j 2 -J 15,16 -j 2 -J 15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNCONF=GENERIC-NODEBUG KERNEL=kernel TARGET=amd64 TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/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::/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src  OSVERSION=1300060 WRKDIRPREFIX=/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B clean build ===>  Cleaning for gpu-firmware-kmod-g20191015 ===>  License AMD INTEL accepted by the user ===>   gpu-firmware-kmod-g20191015 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by gpu-firmware-kmod-g20191015 for building ===>  Extracting for gpu-firmware-kmod-g20191015 => SHA256 Checksum OK for FreeBSDDesktop-kms-firmware-g20191015-81315fa_GH0.tar.gz. ===>  Patching for gpu-firmware-kmod-g20191015 ===>  Configuring for gpu-firmware-kmod-g20191015 ===>  Building for gpu-firmware-kmod-g20191015 ===> i915kmsfw (all) ===> i915kmsfw/bxtdmc (all) make[6]: "/usr/src/sys/conf/kmod.mk" line 77: Could not find bsd.sysdir.mk make[6]: Fatal errors encountered -- cannot continue make[6]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa/i915kmsfw/bxtdmc *** Error code 1 Stop. make[5]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa/i915kmsfw *** Error code 1 Stop. make[4]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[3]: stopped in /usr/ports/graphics/gpu-firmware-kmod *** [all] Error code 1 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 1 error make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG *** [buildkernel] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildkernel] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src root@momh167-gjp4-8570p:/usr/src # ---- Environment: # date ; uname -v Tue Nov 26 04:38:41 GMT 2019 FreeBSD 13.0-CURRENT #37 r354945: Thu Nov 21 19:11:47 GMT 2019 root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG # bectl list BE       Active Mountpoint Space Created r350684  -      -          1.66M 2019-08-07 19:01 r354082b -      -          108G  2019-10-27 14:08 r354616b -      -          1.37M 2019-11-16 17:35 r354945  -      -          1.29M 2019-11-21 13:06 r354945a -      -          1.39M 2019-11-22 02:26 r354945b -      -          1.61M 2019-11-25 06:04 r355097  NR     /          25.7G 2019-11-25 19:16 # From owner-freebsd-current@freebsd.org Tue Nov 26 04:55:05 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4D7E51A82EC for ; Tue, 26 Nov 2019 04:55:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MWmS14LZz4MrJ for ; Tue, 26 Nov 2019 04:55:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x835.google.com with SMTP id g24so13201978qtq.11 for ; Mon, 25 Nov 2019 20:55:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GAQ7JU8Q2c8jqQ+OF3LyFGHihRAPRb9OQ5MX/7I/e7A=; b=sxajA6OJZGuLq5Xowz1cRpfQIyR3JglG7gx8j9zn23SnQn4WYB2Ud1dCCAbI/UcxuO 0I4Ergd5LZ0C+uC31OJd8/JFAOMDiTybbbLe63wbnNFk7IouHJIMTXoi3LE5oBq88OsF vkLGKVAwcnHKGKuyzq4rr2cygvygfvczNflaf6LLEFeufZk8KGeBmzCxwXyaIgAcmfPu C/FstsfJtCBCIaRQEqrqBY24Hd33jD+9OPaQswfnk0F0SnV43KOA/Fr1tAJAhbU2lj4h Vmtx30WLT0aSaeGwdJooy8AAaoFRiabjnX1MhqJD6X5boHrb6eA/bUmnpzFQ/haKik2P /UPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GAQ7JU8Q2c8jqQ+OF3LyFGHihRAPRb9OQ5MX/7I/e7A=; b=fVObR6J8DEzu69GWLhi7r42OaI9umy4oqM7xqv6NpJI1LEAKaWxjMHLFfdyGffS2SF +9NzaN5LsdLSZAchl+Yp0nyok5oYzr4CG60X74wsrgMOtEaiWxwwyBvhOxmYJ67YzLB/ FGBLIHv9FRBGATv7jg5gl1YMFnhQWZNfNae8swq69gyYrueL0LHwG3XWgsUVFd4ulcZl F0V5Pmymch+o4SzvchuKzxapdvTA/iS/cR7rzKUN5OPAaOllQBC3AfPJ9F3/Dy271hn+ 7H1cKil/nlBO3wkUfIFHWGGZ1ZWpR6NDf0tnIMIuEwhDEDDt1SZno3f3sHFn4DAIq7di ECtw== X-Gm-Message-State: APjAAAWwFx8vennxSesKpeJWSZsT81xNbezgxbJphZzalFKlKcmQlW9P Nmgpm5SUJ+VLSg+f/6hVCW0vtxP9sForPj20LYuRQG5X X-Google-Smtp-Source: APXvYqzE/8sgOFoPE/CTb8LhlK3/LNsmR5Wo2d4ySeIBJNON/rgriuUXTcIdC3NEQxmz8MEHff0YV7Vc7vidx7yPbUI= X-Received: by 2002:ac8:6697:: with SMTP id d23mr12456418qtp.32.1574744102161; Mon, 25 Nov 2019 20:55:02 -0800 (PST) MIME-Version: 1.0 References: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> In-Reply-To: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> From: Warner Losh Date: Mon, 25 Nov 2019 21:54:49 -0700 Message-ID: Subject: Re: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk To: Graham Perrin Cc: FreeBSD Current X-Rspamd-Queue-Id: 47MWmS14LZz4MrJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=sxajA6OJ; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::835) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.72 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[9]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[5.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.72)[ip: (-9.34), ipnet: 2607:f8b0::/32(-2.27), asn: 15169(-1.96), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 04:55:05 -0000 So when I committed the sysdir stuff I forgot to add it to the install list. I've fixed it now. Either upgrade, or just copy src/share/mk/ bsd.sysdir.mk to /usr/share/mk Warner On Mon, Nov 25, 2019, 9:40 PM Graham Perrin wrote: > The tail of my most recent run of > > make -j2 buildkernel KERNCONF=3DGENERIC-NODEBUG > > =3D=3D=3D> Ports module graphics/gpu-firmware-kmod (all) > cd ${PORTSDIR:-/usr/ports}/graphics/gpu-firmware-kmod; env -u CC -u > CXX -u CPP -u MAKESYSPATH -u MK_AUTO_OBJ -u MAKEOBJDIR MAKEFLAGS=3D"-= j > 2 -J 15,16 -j 2 -J 15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=3DMAKELEVEL > KERNCONF=3DGENERIC-NODEBUG KERNEL=3Dkernel TARGET=3Damd64 TARGET_ARCH=3Da= md64" > SYSDIR=3D/usr/src/sys > PATH=3D/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.a= md64/tmp/usr/bin:/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/leg= acy/bin::/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin > > SRC_BASE=3D/usr/src OSVERSION=3D1300060 > WRKDIRPREFIX=3D/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B > clean build > =3D=3D=3D> Cleaning for gpu-firmware-kmod-g20191015 > =3D=3D=3D> License AMD INTEL accepted by the user > =3D=3D=3D> gpu-firmware-kmod-g20191015 depends on file: /usr/local/sbin= /pkg > - found > =3D=3D=3D> Fetching all distfiles required by gpu-firmware-kmod-g20191015= for > building > =3D=3D=3D> Extracting for gpu-firmware-kmod-g20191015 > =3D> SHA256 Checksum OK for > FreeBSDDesktop-kms-firmware-g20191015-81315fa_GH0.tar.gz. > =3D=3D=3D> Patching for gpu-firmware-kmod-g20191015 > =3D=3D=3D> Configuring for gpu-firmware-kmod-g20191015 > =3D=3D=3D> Building for gpu-firmware-kmod-g20191015 > =3D=3D=3D> i915kmsfw (all) > =3D=3D=3D> i915kmsfw/bxtdmc (all) > make[6]: "/usr/src/sys/conf/kmod.mk" line 77: Could not find bsd.sysdir.m= k > make[6]: Fatal errors encountered -- cannot continue > make[6]: stopped in > > /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-f= irmware-kmod/work/kms-firmware-81315fa/i915kmsfw/bxtdmc > *** Error code 1 > > Stop. > make[5]: stopped in > > /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-f= irmware-kmod/work/kms-firmware-81315fa/i915kmsfw > *** Error code 1 > > Stop. > make[4]: stopped in > > /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-f= irmware-kmod/work/kms-firmware-81315fa > =3D=3D=3D> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failur= e to > the maintainer. > *** Error code 1 > > Stop. > make[3]: stopped in /usr/ports/graphics/gpu-firmware-kmod > *** [all] Error code 1 > > make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > 1 error > > make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > *** [buildkernel] Error code 2 > > make[1]: stopped in /usr/src > 1 error > > make[1]: stopped in /usr/src > *** [buildkernel] Error code 2 > > make: stopped in /usr/src > 1 error > > make: stopped in /usr/src > root@momh167-gjp4-8570p:/usr/src # > > ---- > > Environment: > > # date ; uname -v > Tue Nov 26 04:38:41 GMT 2019 > FreeBSD 13.0-CURRENT #37 r354945: Thu Nov 21 19:11:47 GMT 2019 > root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > # bectl list > BE Active Mountpoint Space Created > r350684 - - 1.66M 2019-08-07 19:01 > r354082b - - 108G 2019-10-27 14:08 > r354616b - - 1.37M 2019-11-16 17:35 > r354945 - - 1.29M 2019-11-21 13:06 > r354945a - - 1.39M 2019-11-22 02:26 > r354945b - - 1.61M 2019-11-25 06:04 > r355097 NR / 25.7G 2019-11-25 19:16 > # > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Tue Nov 26 08:16:09 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DE3401ADE93 for ; Tue, 26 Nov 2019 08:16:09 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47McDS3W9nz4XNB for ; Tue, 26 Nov 2019 08:16:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 960672601B1; Tue, 26 Nov 2019 09:16:05 +0100 (CET) Subject: Re: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk To: Warner Losh , Graham Perrin Cc: FreeBSD Current References: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> From: Hans Petter Selasky Message-ID: <363d65d5-1b49-ca53-5531-185bf5374fb5@selasky.org> Date: Tue, 26 Nov 2019 09:15:10 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47McDS3W9nz4XNB X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-5.43 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(-3.13)[ip: (-9.33), ipnet: 88.99.0.0/16(-4.73), asn: 24940(-1.57), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 08:16:09 -0000 On 2019-11-26 05:54, Warner Losh wrote: > So when I committed the sysdir stuff I forgot to add it to the install > list. I've fixed it now. Either upgrade, or just copy src/share/mk/ > bsd.sysdir.mk to /usr/share/mk > > Warner Or: make -m /usr/src/share/mk --HPS From owner-freebsd-current@freebsd.org Tue Nov 26 08:46:49 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A49831AEA4D for ; Tue, 26 Nov 2019 08:46:49 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Mcvr14plz4YZt for ; Tue, 26 Nov 2019 08:46:47 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x42d.google.com with SMTP id i12so21439946wro.5 for ; Tue, 26 Nov 2019 00:46:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=DJxiZ/2ojNTfTaoN02k3K0WTbRHIkgB5ZsePHdGA+9Q=; b=GfJgIn4rP1vp0b5KUmKWjnspqiDBXaPsBU0rfmtLibqstXfWeUZc+PHB6fvu7H2nUI Wtz6oLq7Fpsdpew92ahtVZU6Cnl6ZsqNGAR/wFp7Issm897viqOewDFRD+xVtTWXbRoY ztV5cWe+LIAqVtmG9gmbBty7a8ZBs4pu/oigvjHpv/ghq7kS+IqYACOcHAZvrzaWNeHO dWvhm5wcVOC80WxF0Gawl2U3cDScnw0lekDvv7XeUaMfHklojbGNp5wh99NYhkihwvCC TrqHDdFF4co0T56VlEYD1MZKVyfpIUxL1Db5ktqTyuIQZGUWEQFmUNRrqW1hGM2UImjo 13lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=DJxiZ/2ojNTfTaoN02k3K0WTbRHIkgB5ZsePHdGA+9Q=; b=apMD5z5Ti7rOM/UVD74+3hqDF1GIhgQZrPuAiMRfOrr60ooEHBTtSU4C8R9gNFjLhl JuheU76h2E7RxpJm3rRgKe9yxc7YxAQUMAAb6LTiuitTOMhkmrM4xUnk389GL/Z4JN89 mnF9hqYWQXIxgQE619RpNQ0PqJA7G+CmG9jNmR5RNPnd/NkHMlOdoqiC8aUMGhMR/Gyq N+lp4qxFJgv39Od5/gg7q62iFrFyw541Kij2Y0mwhVroEeCOXfdpWJT2Vm20YlHd9G5o crU3lxd96QKMExeNmnOe69BhI6+fNrXFovLqSrJRxUUdgMnoMJHhdghiwrMXmCJyogXI SXBg== X-Gm-Message-State: APjAAAUiCCqOigZn/SCr9MZ5/urdQGkubuAOdDtmqMN0UIubKzz2gPNA lyzKoa24q1Js3ujW/s01ctgefHK6AMs= X-Google-Smtp-Source: APXvYqyQpvMRwCiD85z5TuCjM43Ov4GLlN9n6Owk7UQpnSTg0MU489bjTQEDPE0o8ttZzGtvZEvYAg== X-Received: by 2002:adf:ea8a:: with SMTP id s10mr26364587wrm.278.1574758006179; Tue, 26 Nov 2019 00:46:46 -0800 (PST) Received: from [192.168.1.7] (host-2-100-169-93.as13285.net. [2.100.169.93]) by smtp.gmail.com with ESMTPSA id o10sm2230614wmc.42.2019.11.26.00.46.45 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Nov 2019 00:46:45 -0800 (PST) Subject: Re: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk To: FreeBSD Current References: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> From: Graham Perrin Message-ID: <1d229b4d-ee42-57fc-2a04-d4744e2790b7@gmail.com> Date: Tue, 26 Nov 2019 08:46:44 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 47Mcvr14plz4YZt X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GfJgIn4r; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::42d as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[93.169.100.2.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-8.77), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.96), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[d.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 08:46:49 -0000 On 26/11/2019 04:54, Warner Losh wrote: > So when I committed the sysdir stuff I forgot to add it to the install list. I've fixed it now. Either upgrade, or just copy src/share/mk/bsd.sysdir.mk to /usr/share/mk Thanks! Now building r355107. From owner-freebsd-current@freebsd.org Tue Nov 26 08:57:24 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6CEF81AF08A for ; Tue, 26 Nov 2019 08:57:24 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from jax4mhob03.myregisteredsite.com (jax4mhob03.myregisteredsite.com [64.69.218.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.registeredsite.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Md833CFzz4Z5g for ; Tue, 26 Nov 2019 08:57:23 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mailpod.hostingplatform.com (atl4qobmail01pod2.registeredsite.com [10.30.77.35]) by jax4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id xAQ8vKcT017473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 26 Nov 2019 03:57:21 -0500 Received: (qmail 16027 invoked by uid 0); 26 Nov 2019 08:57:20 -0000 X-TCPREMOTEIP: 99.253.169.68 X-Authenticated-UID: dclarke@blastwave.org Received: from unknown (HELO ?172.16.35.2?) (dclarke@blastwave.org@99.253.169.68) by 0 with ESMTPA; 26 Nov 2019 08:57:20 -0000 To: FreeBSD Current From: Dennis Clarke Subject: GCC 8.x or 9.x for FreeBSD rv64imafdc ?? Message-ID: <4e366b17-25ae-5b89-79ad-e1e113149494@blastwave.org> Date: Tue, 26 Nov 2019 08:57:20 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Thunderbird/71.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47Md833CFzz4Z5g X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dclarke@blastwave.org has no SPF policy when checking 64.69.218.83) smtp.mailfrom=dclarke@blastwave.org X-Spamd-Result: default: False [4.38 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.51)[ipnet: 64.69.218.0/23(0.92), asn: 19871(1.67), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[blastwave.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.985,0]; NEURAL_SPAM_LONG(0.99)[0.985,0]; RCVD_IN_DNSWL_NONE(0.00)[83.218.69.64.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:19871, ipnet:64.69.218.0/23, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 08:57:24 -0000 ---------------------------------------------------------------- I will cross post this as there are very few options left. ---------------------------------------------------------------- rv64imafdc folks : I will send this out to the only people and places that are likely to not simply be a black hole from which nothing ever returns. However most of my messages do just die on the mail lists with no reply from anyone ever and that is very true for the gcc maillists for anything RISC-V related. I wish I knew why. I am able to checkout and cross compile FreeBSD 13.0-CURRENT r354873 however there is no compiler. I looked. The output destination rootfs shows no signs of LLVM/Clang and certainly not gcc of any flavor. I do see wonderful things like : https://github.com/freebsd-riscv/riscv-gcc/commit/be9abee2aaa919ad8530336569d17b5a60049717 However nothing actually usable by any user out here in the more or less real world that is not inside SiFive or similar. So is there any place at all that one may attain a compiler or am I left to decipher the horrific mess that is known as the Canadian cross compiler bootstrap which has never worked for me. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional From owner-freebsd-current@freebsd.org Tue Nov 26 13:43:08 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7268C1B664E for ; Tue, 26 Nov 2019 13:43:08 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MlTk5wTjz3L4W for ; Tue, 26 Nov 2019 13:43:06 +0000 (UTC) (envelope-from ruslanngaripov@gmail.com) Received: by mail-lf1-x143.google.com with SMTP id l28so14167949lfj.1 for ; Tue, 26 Nov 2019 05:43:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=iPofq1qdygw6k88WF3VfRgAkTR366vPtC/ZHoCxwQsM=; b=GWs+vb5bY2WaclGbdO3sWKMWk1rHeKvWW+zTXEgWrpSD2VBC0dNAnS0lUSo3lGs38p c56D/kG67hVAQk4QO2qqYnljLJGjD8nzeRfwNiKAnJ6JQA8njO8mAYTxShkMAGu34iBd D7Pps/W3RrXE1ecVPweAGRXqY5WrqD7p0qy29T06uMWzIVGzew7L5gU0F0hvWNO7IFMq hnMNmr8jq76Y+Ljb5ICsxfs85cFols6DhXA20B9mZniZjAHix7rP3A7lX5NRQvJsVSgZ HlhnEuxRDDLaUSTcbCKoypAtUUoW8KtJxCL+hz4v1+huoBJLciVR9ndGOzSPs74MY/xT /LwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iPofq1qdygw6k88WF3VfRgAkTR366vPtC/ZHoCxwQsM=; b=tNDzhitrQiclh4yWQvIFSPPIbTMmxode7eDAryLD8Y3kVuNWLa+MjsjSPvwo0A0kL5 KUsIZLF/0PehyFrE84wyjzvJg4vQdckhHnrNjJhlnJFLQ3tJXFXmNvxiD84wdn3B6Qv+ yMtJucD/PDar9RrZEymxTM8oC/HKXkeOF0dbnz+mLww0nRgDUB5KwxRJOl78wmvBNB9+ GuIV1YAVvSuVul8EdWGb/taagmSDE/LiwmgGQhR4Vq+K6li3kRH2DbDN5Kakm/17FaYk rYY4mpZE93EorTflItg8uro3zG/iBrIukbpDCC7IFzUYele4Vu/WwuidZDqsf1ZKY0Mj CwrQ== X-Gm-Message-State: APjAAAXIXBm4CT0FvT4f7l620zjXG09EXRNYGqBKfLNxAfZi85NudvnN Fst+zkKnGK+pZxwUe83/A1tKNyCdFUA= X-Google-Smtp-Source: APXvYqwnveMIjNsc6Egn4XEqHfIxW4Ttnu5gRr5uV5JGqH0PjPm7P5VqIFkSSukFvAuEfov3fvUxng== X-Received: by 2002:ac2:4882:: with SMTP id x2mr5881577lfc.103.1574775784472; Tue, 26 Nov 2019 05:43:04 -0800 (PST) Received: from [192.168.1.2] ([46.48.69.183]) by smtp.gmail.com with ESMTPSA id i6sm5298576lfo.12.2019.11.26.05.43.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Nov 2019 05:43:03 -0800 (PST) Subject: Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org References: <5596338e-134c-9849-de9e-710d3106687f@gmail.com> <41b921c4-568f-5bd1-ae0f-1d85d750a8c7@quip.cz> From: Ruslan Garipov Message-ID: <4d7c7c51-33b9-2345-93fa-0736e2e640c9@gmail.com> Date: Tue, 26 Nov 2019 18:42:59 +0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <41b921c4-568f-5bd1-ae0f-1d85d750a8c7@quip.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47MlTk5wTjz3L4W X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GWs+vb5b; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ruslanngaripov@gmail.com designates 2a00:1450:4864:20::143 as permitted sender) smtp.mailfrom=ruslanngaripov@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.72), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.95), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 13:43:08 -0000 On 11/26/2019 12:09 AM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 19:26: > > [...] > >>> I didn't tried this with current but I am using it with stable (11.3 at >>> this time). Building on Xeon E3-1240v3 and installing on many different >>> machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, >>> some 10 years old Intel Pentium. >>> So at least it worked in the past (11.3 amd64). Did you use this >>> workflow in the past / did it work? >> No, unfortunately I didn't. Always built world/kernel on target host. >> >>> I remember some issue in the past which was (accidentally?) fixed by >>> running "make buildworld && make builkernel && make installkernel && >>> make installworld" on the build host (to some different DESTDIR) and >>> then "make installkernel && make installworld" on the target host (build >>> machine is shared via NFS) >> Therefore, this trick somehow "fixes" /usr/obj shared on the build >> machine? I'll try this later. Thanks! > > Yes, I think so. But I am not a developer nor I know much about how > build process works. I've tried to installkernel/installworld with non-default DESTDIR, it doesn't help for GENERIC kernel. But... After I had failed with that DESTDIR, I decided to update kernel/world on the build machine to the revision I tried to deploy (r355085). I cleaned result of the previous build, restored make.conf and src.conf specifying sandybridge† there as value of CPUTYPE and explicit -march, build and install kernel and world. Then I cleaned result of the build again, run buildworld and buildkernel preparing to investigate the build logs. But before doing that, I decided to run `make installkernel` once again on a target machine, and ... bang! It completed successfully! mergemaster, installworld -- the same! Everything completed smoothly. I updated the source to r355105 on the build machine, buildworld and buildkernel there -- installkernel, mergemaster, installworld on a target machine completed with no errors. To be honest, I don't know what exactly was a reason for my previous failure. Because I've tried to build with sandybridge in the configs. May be r355085 helped me, I don't know. In any case, I should inspect the build log, I believe. Miroslav, thanks for support! † This is the oldest chip we have on our ESXi hosts. From owner-freebsd-current@freebsd.org Tue Nov 26 13:44:12 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 060791B6791 for ; Tue, 26 Nov 2019 13:44:12 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from MailHost (unknown [80.211.33.142]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47MlVz136zz3LDJ for ; Tue, 26 Nov 2019 13:44:11 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from root (uid 0) (envelope-from salvadore@FreeBSD.org) id 2276 by MailHost (DragonFly Mail Agent v0.11+); Tue, 26 Nov 2019 14:43:32 +0100 To: freebsd-hackers@FreeBSD.org Subject: FreeBSD Quarterly Status Report - Third Quarter 2019 Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Date: Tue, 26 Nov 2019 14:43:32 +0100 Message-Id: <5ddd2c04.2276.7c14d497@MailHost> From: X-Rspamd-Queue-Id: 47MlVz136zz3LDJ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.80 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.91)[-0.912,0]; NEURAL_HAM_LONG(-0.89)[-0.890,0]; ASN(0.00)[asn:31034, ipnet:80.211.0.0/17, country:IT] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 13:44:12 -0000 FreeBSD Project Quarterly Status Report - Third Quarter 2019 Here is the third quarterly status report for 2019. This quarter the reports team has been more active than usual thanks to a better organization: calls for reports and reminders have been sent regularly, reports have been reviewed and merged quickly (I would like to thank debdrup@ in particular for his reviewing work). Efficiency could still be improved with the help of our community. In particular, the quarterly team has found that many reports have arrived in the last days before the deadline or even after. I would like to invite the community to follow the guidelines below that can help us sending out the reports sooner. Starting from next quarter, all quarterly status reports will be prepared the last month of the quarter itself, instead of the first month after the quarter's end. This means that deadlines for submitting reports will be the 1st of January, April, July and October. Next quarter will then be a short one, covering the months of November and December only and the report will probably be out in mid January. -- Lorenzo Salvadore __________________________________________________________________ FreeBSD Team Reports * Cluster Administration Team * Continuous Integration * FreeBSD Core Team * FreeBSD Foundation * FreeBSD Graphics Team status report * FreeBSD Release Engineering Team * FreeBSD Security Team Projects * FAT / msdosfs support for makefs(8) * FUSE * Google Summer of Code 2019 * GSoC'19 Project - MAC policy on IP addresses in Jail: mac_ipacl * Improving laptop support * NFS Version 4.2 implementation * Rockchip RK3399 SoC's eMMC support * syzkaller on FreeBSD * TPM2 Software Stack (TSS2) Kernel * Casueword(9) livelock * Kernel Mapping Protections * Kernel ZLIB Update * PROT_MAX mmap/mprotect maximum protections API * Randomized Top of Stack pointer * Signals delivered on unhandled Page Faults Architectures * Broadcom ARM64 SoC support * FreeBSD support for the forthcoming Arm Morello CPU, SoC, and board * FreeBSD/powerpc Project * NXP ARM64 SoC support Userland Programs * gets(3) retirement Ports * FreshPorts * Java on FreeBSD * KDE on FreeBSD * Ports Collection * XFCE 4.14 update Third-Party Projects * ClonOS: virtualization platform on top of FreeBSD Operating System * ENA FreeBSD Driver Update * Nomad pot driver - Orchestrating jails via nomad * sysctlinfo __________________________________________________________________ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. Cluster Administration Team Contact: Cluster Administration Team The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following: * Change IPv6 address in TWN site. * Solved hardware issues in KWC site (with hrs@). * Moved remaining infrastructure from the YSV (Yahoo!) site to NYI (New York Internet) (peter@). * YSV hosted most of FreeBSD.org between 2000 and 2019. Installed new machines for portmgr@ courtesy of the FreeBSD Foundation. Resolved outtages (thanks uqs@) with GitHub exporter, Bugzilla and hg-beta (thanks bapt@). PowerPC64 servers are online (power8) building pkgs and reference hosts. Ongoing systems administration work: * Creating accounts for new committers. * Backups of critical infrastructure. * Keeping up with security updates in 3rd party software. Work in progress: * Review the service jails and service administrators operation. * South Africa Mirror (JINX) in progress. * NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder. * Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation. * Boot issues with Aarch64 reference machines. * New NYI.net sponsored colocation space in Chicago-land area. * Setup new host for CI staging environment. __________________________________________________________________ Continuous Integration Links FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org/ FreeBSD Jenkins wiki URL: https://wiki.freebsd.org/Jenkins freebsd-testing Mailing List URL: https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci Tickets related to freebsd-testing@ URL: https://preview.tinyurl.com/y9maauwg Hosted CI wiki URL: https://wiki.freebsd.org/HostedCI FreeBSD CI weekly report URL: https://hackmd.io/@FreeBSD-CI Contact: Jenkins Admin Contact: Li-Wen Hsu The FreeBSD CI team maintains continuous integration system and related tasks for the FreeBSD project. The CI system regularly checks the committed changes can be successfully built, then performs various tests and analysis of the results. The results from build jobs are archived in an artifact server, for the further testing and debugging needs. The CI team members examine the failing builds and unstable tests, and work with the experts in that area to fix the code or adjust test infrastructure. The details are of these efforts are available in the weekly CI reports. We had a testing working group at the 201909 DevSummit lwhsu@ has presented the Testing/CI project status and "how to work with the FreeBSD CI system", slides are available at the DevSummit page. Some contents have been migrated to https://wiki.freebsd.org/Jenkins/Debug , extending is welcomed. We continue publishing CI Weekly Report and moved the archive to https://hackmd.io/@FreeBSD-CI Work in progress: * Collecting and sorting CI tasks and ideas at https://hackmd.io/bWCGgdDFTTK_FG0X7J1Vmg * Setup the CI stage environment and put the experimental jobs on it * Extending and publishing the embedded boards testbed * Implementing automatic tests on bare metal hardware * Adding drm ports building test against -CURRENT * Testing and merging pull requests at https://github.com/freebsd/freebsd-ci/pulls * Planning for running ztest and network stack tests * Help more 3rd software get CI on FreeBSD through a hosted CI solution Please see freebsd-testing@ related tickets for more WIP information. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. * Core has provisionally accepted the BSD+patent license for use in some cases. The Core Team must approve the import of new BSD+Patent licensed components or the change of license of existing components to the BSD+Patent License. https://opensource.org/licenses/BSDplusPatent * Kernel Pseudo Random Number Generator (PRNG) maintainership was updated to reduce the contribution barrier for committers who have demonstrated competence in this part of the tree. * Core approved a source commit bit for Pawel/ Biernacki. Konstantin Belousov will mentor Pawel/ and Mateusz Guzik will be co-mentor. * The Core-initiated Git Transition Working Group met over the last quarter, however a report is still forthcoming. Discussions will continue in the fourth quarter of 2019. There are many issues to resolve including how to deal with contrib/, whether to re-generate hashes in the current Git repository, and how to best implement commit testing. __________________________________________________________________ FreeBSD Foundation Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Funding comes from individual and corporate donations and is used to fund and manage software development projects, conferences and developer summits, and provide travel grants to FreeBSD contributors. The Foundation purchases and supports hardware to improve and maintain FreeBSD infrastructure and provides resources to improve security and quality assurance efforts; publishes marketing material to promote, educate, and advocate for the FreeBSD Project; facilitates collaboration between commercial vendors and FreeBSD developers; and finally, represents the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. Here are some highlights of what we did to help FreeBSD last quarter: Partnerships and Commercial User Support We help facilitate collaboration between commercial users and FreeBSD developers. We also meet with companies to discuss their needs and bring that information back to the Project. In Q3, Ed Maste and Deb Goodkin met with a few commercial users in the US. It is not only beneficial for the above, but it also helps us understand some of the applications where FreeBSD is used. We were also able to meet with a good number of commercial users at vBSDCon and EuroBSDCon. These venues provide an excellent opportunity to meet with commercial and individual users and contributors to FreeBSD. Fundraising Efforts Our work is 100% funded by your donations. We are continuing to work hard to get more commercial users to give back to help us continue our work supporting FreeBSD. More importantly, we'd like to thank our individual donors for making $10-$1,000 donations last quarter, for more than $16,000! Please consider making a donation to help us continue and increase our support for FreeBSD! We also have the Partnership Program, to provide more benefits for our larger commercial donors. Find out more information at www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ and share with your companies. OS Improvements The Foundation supports software development projects to improve the FreeBSD operating system through our full time technical staff, contractors, and project grant recipients. They maintain and improve critical kernel subsystems, add new features and functionality, and fix problems. Over the last quarter there were 345 commits to the FreeBSD base system repository sponsored by the FreeBSD Foundation - this represents about one fifth of all commits during this period. Many of these projects have their own entries in this quarterly report (and are not repeated here). Foundation staff member Konstantin Belousov committed many improvements to multiple kernel subsystems, as well as low-level 32-bit and 64-bit x86 infrastructure. These included fixes for robust mutexes, unionfs, the out of memory (OOM) handler, and per-cpu allocators. Additional work included fixes for security issues and introduction and maintenance of vulnerability mitigations, and improving POSIX conformance. Ed Maste committed a number of minor security bug fixes and improvements, as well as the first iteration of a tool for editing the mitigation control ELF note. Additional work included effort on build infrastructure and the tool chain. Clang's integrated assembler (IAS) is now used more widely, as part of the path to retiring the assembler from GNU binutils 2.17.50. The readelf tool now decodes some additional ELF note information. Ed also enabled the Linuxulator (Linux binary support layer) on arm64, and added a trivial implementation of the renameat2 system call (handling common options). Mark Johnston added Capsicum support to a number of ELF Tool Chain utilities, and committed a number of other Capsicum kernel and userland fixes. Mark worked on a number of changes related to security improvements, including integration and support of the Syzkaller automated system call fuzzer, and fixing issues identified by Syzkaller. Other changes included addressing failures caused by refcount wraparound, improvements to the prot_max memory protection. Other work included NUMA, locking, kernel debugging, RISC-V and arm64 kernel improvements. Edward Napierala continued working on Linuxulator improvements over the quarter. The primary focus continued to be tool improvements - strace is now more usable for diagnosing issues with Linux binaries running under the Linuxulator. That said, as with previous work a number of issues have been fixed along the way. These are generally minor issues with a large impact - for example, every binary linked against up-to-date glibc previously segfaulted on startup. This is now fixed. Continuous Integration and Quality Assurance The Foundation provides a full-time staff member who is working on improving our automated testing, continuous integration, and overall quality assurance efforts. During the third quarter of 2019, Foundation staff continued to improve the project's CI infrastructure, worked with contributors to fix the failing build and test cases, and worked with other teams in the Project for their testing needs. We added several new CI jobs and worked on getting the hardware regression testing lab ready. Li-Wen Hsu gave presentations "Testing/CI status update" and "How to work with the FreeBSD CI system" at the 201909 DevSummit. Slides are available at the DevSummit page. We continue publishing the CI weekly report on the freebsd-testing@. mailing list, and an archive is available. See the FreeBSD CI section of this report for completed work items and detailed information. Supporting FreeBSD Infrastructure The Foundation provides hardware and support to improve the FreeBSD infrastructure. Last quarter, we continued supporting FreeBSD hardware located around the world. FreeBSD Advocacy and Education A large part of our efforts are dedicated to advocating for the Project. This includes promoting work being done by others with FreeBSD; producing advocacy literature to teach people about FreeBSD and help make the path to starting using FreeBSD or contributing to the Project easier; and attending and getting other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD tables, and give FreeBSD presentations. The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, to work together on projects, and to facilitate collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. Check out some of the advocacy and education work we did last quarter: * Sponsored USENIX 2019 Annual Technical Conference as an Industry Partner * Represented FreeBSD at OSCON 2019 in Portland, OR * Represented FreeBSD at COSCUP 2019 in Taiwan * Presented at the Open Source Summit, North American in San Diego, CA * Executive Director Deb Goodkin was interviewed by TFiR https://www.freebsdfoundation.org/news-and-events/latest-news/tfir-interview-freebsd-meets-linux-at-the-open-source-summit/ * Sponsored FreeBSD Hackathon at vBSDcon 2019 in Reston, VA * Sponsored the attendee bags and attended vBSDcon 2019 in Reston VA * Represented FreeBSD at APNIC-48 in Chiang Mai, Thailand * Represented FreeBSD at MNNOG-1 in Ulaanbaatar, Mongolia * Served as an administrator for the Project's Google Summer of Code Session. See the Google Summer of Code section of this report for more information. * Sponsored FreeBSD Developers Summit at EuroBSDCon in Lillehammer, Norway * Sponsored and attended EuroBSDcon 2019 in Lillehammer, Norway * Applied and was accepted for a FreeBSD Miniconf at linux.conf.au, in Gold Coast, Australia, Jan 14, 2020 * Our FreeBSD talk was accepted at seaGL, Seattle, WA, November 15 and 16. We continued producing FreeBSD advocacy material to help people promote FreeBSD. Learn more about our recent efforts to advocate for FreeBSD around the world: https://www.freebsdfoundation.org/blog/freebsd-around-the-world/ Our Faces of FreeBSD series is back. Check out the latest post: Roller Angel. Read more about our conference adventures in the conference recaps and trip reports in our monthly newsletters: https://www.freebsdfoundation.org/news-and-events/newsletter/ We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/. You can find out more about events we attended and upcoming events. We opened our official FreeBSD Swag Store. Get stickers, shirts, mugs and more at ShopFreeBSD. We have continued our work with a new website developer to help us improve our website. Work has begun to make it easier for community members to find information and to make the site more efficient. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to http://www.FreeBSDfoundation.org to find out how we support FreeBSD and how we can help you! __________________________________________________________________ FreeBSD Graphics Team status report Links Project GitHub page URL: https://github.com/FreeBSDDesktop Contact: FreeBSD Graphics Team Contact: Niclas Zeising The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics stack. This includes graphics drivers, graphics libraries such as the MESA OpenGL implementation, the X.org xserver with related libraries and applications, and Wayland with related libraries and applications. During the last period, several changes have been made, but most of them has been behind the scene. We have also worked on general clean up of old xorg ports that have been deprecated upstream. The ports infrastructure for xorg ports and ports that depend on xorg ports have been updated. We have switched USE_XORG and XORG_CAT to use the USES framework, instead of the old way of including bsd.xorg.mk from bsd.port.mk. This infrastructure work has been fairly substantial, and new ports depending on xorg ports should add USES=xorg to their makefiles. As part of this bsd.xorg.mk was split up, and the XORG_CAT part was split out to USES=xorg-cat. This is used for the xorg ports themselves, and sets up a common environment for building all xorg ports. In addition, framework for pulling xorg ports directly from freedesktop.org gitlab was added, which will make improve development and testing, since it makes it possible to create ports of unreleased versions. Further improvements in this area includes framework for using meson instead of autotools for building xorg ports. This is still a work in progress. We have also worked to clean up and deprecate several old xorg ports and libraries. Some of these ports have already been removed, and some are still waiting on removal after a sufficient deprecation period. Most notably amongst the deprecations are x11/libXp, which required to fix several dependencies. Several other old libraries have also been deprecated, such as x11/Xxf86misc, x11-fonts/libXfontcache and graphics/libGLw. Some applications and drivers have also been deprecated during the period. With the remaining removals in this area, we should be up to speed with deprecations upstream. We are currently investigating if there are new software added upstream that we need to port to FreeBSD. We have also continued our regularly scheduled bi-weekly meetings. People who are interested in helping out can find us on the x11@FreeBSD.org mailing list, or on our gitter chat: https://gitter.im/FreeBSDDesktop/Lobby. We are also available in #freebsd-xorg on EFNet. We also have a team area on GitHub where our work repositories can be found: https://github.com/FreeBSDDesktop __________________________________________________________________ FreeBSD Release Engineering Team Links FreeBSD 11.3-RELEASE announcement URL: https://www.freebsd.org/releases/11.3R/announce.html FreeBSD 12.1-RELEASE schedule URL: https://www.freebsd.org/releases/12.1R/schedule.html FreeBSD 12.1-RELEASE BETA/RC builds URL: https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/ FreeBSD development snapshots URL: https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. During the third quarter of 2019, the FreeBSD Release Engineering team finished the 11.3-RELEASE cycle, with the final release build started on July 5th and the official announcement sent on July 9th. FreeBSD 11.3-RELEASE is the fourth release from the stable/11 branch, building on the stability and reliability of 11.2-RELEASE. The FreeBSD Release Engineering Team also started work on the upcoming 12.1-RELEASE, which started September 6th. This release cycle is the first "freeze-less" release from the Subversion repository, and the test bed for eliminating the requirement of a hard code freeze on development branches. Commits to the releng/12.1 branch still require explicit approval from the Release Engineering Team, however. At present, there have been three BETA builds, and so far, two RC builds, with the final 12.1-RELEASE build scheduled for November 4th. Additionally throughout the quarter, several development snapshots builds were released for the head and stable/11 branches; snapshots for stable/12 were released as well although not during the 12.1-RELEASE cycle. Much of this work was sponsored by Rubicon Communications, LLC (Netgate) and the FreeBSD Foundation. __________________________________________________________________ FreeBSD Security Team Links FreeBSD security information URL: https://www.freebsd.org/security/ Contact: Security Team Several members of the security team met at the Vendor Summit in October to formalize team structure dedicated for architecture and crypto engineering in addition to the existing product security incident response function. Since June we have started having fortnightly conference calls to discuss important issues and to collaborate closely on advisories and errata notices in the pipeline. * Security advisories sent out in 2019-Q3: 7 * Errata Notices sent out in 2019-Q3: 5 __________________________________________________________________ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. FAT / msdosfs support for makefs(8) Contact: Ed Maste In order to streamline the process of creating install or virtual machine system images we needed FAT filesystem support in makefs(8). Makefs was originally developed in NetBSD, and FAT support was added there not much later, but after the tool was ported to FreeBSD. Siva Mahadevan, one of the FreeBSD Foundation's interns from the University of Waterloo, worked on porting FAT support from NetBSD. I rebased and updated Siva's work, and committed it during this quarter. After a few follow-up fixes we are able to build FAT filesystem images without using md(4) and without requiring root. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ FUSE Contact: Alan Somers FUSE (File system in USErspace) allows a userspace program to implement a file system. It is widely used to support out-of-tree file systems like NTFS, as well as for exotic pseudo file systems like sshfs. FreeBSD's fuse driver was added as a GSoC project in 2012. Since that time, it has been largely neglected. The FUSE software is buggy and out-of-date. Our implementation is about 11 years behind. I completed this work during Q3. I fixed a few newly-introduced bugs, fixed a long-standing sendfile bug that affects FUSE ([236466](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236466)) and merged everything to head and stable/12. Then I fixed the resulting Coverity CIDs. There have been no new FUSE-related bug reports, so I can only assume that everything is working great. Report any problems to asomers@FreeBSD.org. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ Google Summer of Code 2019 Links 2019 Summer of Code Project Wikis URL: https://wiki.freebsd.org/SummerOfCode2019Projects 2019 Summer of Code Projects URL: https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/ Contact: Summer of Code Admins The FreeBSD Project is pleased to have participated in Google Summer of Code 2019 marking our 14th year of participation. This year we had six successful projects: * Dual-stack ping command by Ján Sucan * Firewall test suite by Ahsan Barkati * Kernel sanitizers by Costin Carabas * MAC policy on IP addresses for FreeBSD Jail by Shivank Garg * Separation of ports build process from local installation by Theron Tarigo * Virtual memory compression by Paavo-Einari Kaipila We thank Google for the opportunity to work with these students and hope they continue to work with FreeBSD in the future. This project was sponsored by Google Summer of Code. __________________________________________________________________ GSoC'19 Project - MAC policy on IP addresses in Jail: mac_ipacl Links FreeBSD's Phabricator Differential Link URL: https://reviews.freebsd.org/D20967 Github Diff Link URL: https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail Project Wiki Page URL: https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail Contact: Shivank Garg About - With the introduction of VNET(9) in FreeBSD, Jails are free to set their IP addresses. However, this privilege may need to be limited by the host as per its need for multiple security reasons. This project uses mac(9) for an access control framework to impose restrictions on FreeBSD jails according to rules defined by the root of the host using sysctl(8). It involves the development of a dynamically loadable kernel module (mac_ipacl) based on The TrustedBSD MAC Framework to implement a security policy for configuring the network stack. This project allows the root of the host to define the policy rules to limit the root of a jail to a set of IP (v4 or v6) addresses and/or subnets for a set of interfaces. Features this new MAC policy module are: * The host can define one or more lists of IP addresses/subnets for the jail to choose from. * The host can restrict the jail from setting certain IP addresses or prefixes (subnets). * The host can restrict this privilege to a few network interfaces. Implementation - The mac_ipacl module is a loadable kernel module. It implements mac checks in netinet/in.c and netinet6/in6.c to check the IP addresses requested by jail. The idea to implement these checks at these places comes from the fact that SIOCAIFADDR (for IPv4) and SIOCAIFADDR_IN6 (for IPv6) ioctl handlers are defined for adding the IP addresses to an interface. This is used by ifconfig (in userspace) for setting the IP address. The MAC Framework acts as multiplexer between the netinet and the module. The requested IP and the credentials are checked with the rules in mac_ipacl and output is returned accordingly to netinet. The module can be tuned with various sysctl and similarly, policy rules are also be defined with sysctl. TestSuite - Test scripts integrated with kyua and ATF are included with the module. Using the module - I have written a man page for the module. Please refer to the mac_ipacl(4) for using the new MAC module and various examples. Final Deliverables - * A loadable kernel module - mac_ipacl in sys/security/mac_ipacl * ATF tests for the module in tests/sys/mac/ipacl * A man page for this new mac module - mac_ipacl.4 in share/man/man4/mac_ipacl.4 This is a new project, developed as part of Google Summer of Code'19 under the guidance of Bjoern A. Zeeb . The module is reviewed and Revision for this project is accepted and ready to land. It is yet to be merged with FreeBSD HEAD, and waiting to be tested by few more hands in the industry. I'll be very thankful if you can give this module a try and share your valuable experience about it. Please be free to share your ideas and feedback on this module and please do not hesitate to send me an email. __________________________________________________________________ Improving laptop support Contact: Ed Maste The FreeBSD Foundation would like to ensure that running FreeBSD on contemporary hardware, including laptops, remains viable. To that end we plan to purchase the latest generation of one or more of a family of laptops preferred by members of the FreeBSD community, evaluate the existing state of hardware support, and implement missing hardware support where possible. As the first laptop for this project we have selected a 7th Generation Lenovo X1 Carbon. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ NFS Version 4.2 implementation Contact: Rick Macklem RFC-7862 describes a new minor revision to the NFS Version 4 protocol. This project implements this new minor revision. The NFS Version 4 Minor Version 2 protocol adds several optional features to NFS, such as support for SEEK_DATA/SEEK_HOLE, file copying done on the server that avoids data transfer over the wire and support for posix_fallocate(), posix_fadvise(). Hopefully these features can improve performance for certain applications. The implementation is now nearing completion and recent work has been mostly testing. A cycle of interoperability testing with Linux has just been completed. The main area that still needs testing is use of the pNFS server with NFSv4.2 and that should start soon. Once testing of pNFS is completed, I believe the code is ready to be incorporated into FreeBSD head/current. Testing by others would be appreciated. The modified kernel can be found at https://svn.freebsd.org/base/projects/nfsv42/sys and should run with a recent FreeBSD head/current system. Client mounts need the "minorversion=2" mount option to enable this protocol. __________________________________________________________________ Rockchip RK3399 SoC's eMMC support Contact: Ganbold Tsagaankhuu The followings features have been added to support RK3399 SoC eMMC on FreeBSD: * Extended simple_mfd driver to expose a syscon interface if that node is also compatible with syscon. For instance, Rockchip RK3399's GRF (General Register Files) is compatible with simple-mfd as well as syscon and has devices like usb2-phy, emmc-phy and pcie-phy etc. under it. * Made Rockchip's General Register Files driver the subclass of Simple MFD driver * Added driver for Rockchip RK3399 eMMC PHY. * Added eMMC support codes for Rockchip RK3399 SoC. * All above was tested on NanoPC-T4 board. __________________________________________________________________ syzkaller on FreeBSD Contact: Andrew Turner Contact: Mark Johnston Contact: Michael Tuexen Contact: Samy Al Bahra See the syzkaller entry in the 2019q1 quarterly report for an introduction to syzkaller. Work has continued on fixing bugs uncovered by syzkaller. Over a dozen kernel bugs fixed in the past three months have been directly attributed to syzkaller, and a number of syzkaller reproducers have been incorporated into our test suite. backtrace.io, via Samy, has graciously provided a large server for running a dedicated syzkaller instance to fuzz FreeBSD under bhyve. Though syzbot, the public syzkaller instance run by Google, already fuzzes FreeBSD, it has proven fruitful to run multiple syzkaller instances: different instances find different bugs, and syzkaller.backtrace.io allows us to experiment with FreeBSD-specific extensions. In particular, this instance currently uploads data about each crash to backtrace.io, making it much easier to triage and analyze crashes. We plan to make this service generally available to FreeBSD developers in the near future. Going forward we will continue to extend syzkaller coverage and make it simpler for users and developers to run private instances, and optionally collect kernel crash information for debugging or for submission. This project was sponsored by backtrace.io, and The FreeBSD Foundation. __________________________________________________________________ TPM2 Software Stack (TSS2) Links tpm2-tss Documentation URL: https://tpm2-tss.readthedocs.io/en/latest/index.html tpm2 Source Repository URL: https://github.com/tpm2-software/ tpm2 mailing list URL: https://lists.01.org/postorius/lists/tpm2.lists.01.org/ tpm2 irc channel URL: ircs://chat.freenode.net:6697/tpm2.0-tss Contact: D Scott Phillips Intel has contributed ports of the TPM2 Software Stack to the ports tree, with the new ports securtity/tpm2-tss, security/tpm2-tools, security/tpm2-abrmd. tpm2-tss contains a set of libraries which expose various TPM2 APIs for using a TPM conforming to the TCG TPM 2.0 specification. tpm2-tools provides a set of command line tools which use the tpm2-tss libraries to perform tpm operations. Finally, tpm2-abrmd is a userspace daemon which acts as a TPM Access Broker and Resource Manager, multiplexing many TPM users onto a single TPM device. Sponsored by: Intel Corporation __________________________________________________________________ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. Casueword(9) livelock Contact: Konstantin Belousov The Compare-And-Swap (CAS) is one of the fundamental building blocks for hardware-assisted atomic read/modify/write operations. Some architectures support it directly, for instance x86 and sparc. Others provide different building blocks, usually the pair of Load Linked/Store Conditional instructions (ll/sc) which can be used to construct CAS or other atomic operations like Fetch-And-Add or any atomic arithmetic ops using plain arithmetic instructions. An example is the LDXR/STXR pair on AArch64. The ll/sc operation is performed by first using the load linked instruction to load a value from memory and simultaneously mark the cache line for exclusive access. The value is then updated by the store conditional instruction, but only if there were not any writes to the marked cache line. Any write by another CPU makes the store instruction fail. So typically atomic primitives on ll/sc architectures retry the whole operation if only store failed, because it just means that this CPU either lost a race, or even the failure was spurious. This is so called strong version of CAS and atomics. If primitive returns failure instead, the CAS variant is called weak by C standard. For the FreeBSD threading library lock implementation, when the fast path mode in userspace was not possible, the kernel often needs to do a CAS operation on user memory location. In addition to all guarantees of normal CAS, it also must ensure the safety and tolerance to paging. In FreeBSD, the casueword32(9) primitive provides CAS on usermode 32bit words for kernel. Casueword32(9) was implemented as strong CAS, similarly to the mode of operation of hardware CAS instructions on x86. Using the strong implementation for casueword may be dangerous, since the same address is potentially accessible to other, potentially malicious, threads in the same or other processes. If such a thread constantly dirties the cache line used by a ll/sc loop, it could practically force the kernel-mode thread to remain stuck in the loop forever. Since the loop is tight, and it does not check for signals, the thread cannot be stopped or killed. The solution is to make the casueword implementation weak, which means that the interface of the primitive must be changed to allow notifying the caller about spurious failures. Also, it is now the caller's responsibility to retry as appropriate. The change to casueword was made for all architectures. Even on x86, the PSL.ZF value after the CMPXCHG instruction was returned directly for the new casueword. All two dozens uses of the primitive, all located in kern_umtx.c, were inspected and retry added as needed. As a somewhat related note, in-kernel atomic_cmpset(9) operations are strong, while atomic_fcmpset(9) should be weak, unless broken by a specific architecture. The general attitude seems to be that retry is the duty of the primitive's caller. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ Kernel Mapping Protections Contact: Mark Johnston Modern CPU architectures have the ability to flag memory mappings as "no-execute" (NX), which prevents that memory from being executed by a processor. NX mappings are an important security mitigation since they help segregate code and data, blocking unintentional execution of memory whose contents is controlled by an attacker. W^X (write XOR execute) is a security policy which disallows the creation of mappings that are simultaneously writeable and executable. Under this policy, memory whose contents can be modified must be mapped with the NX flag. This policy makes it harder to exploit bugs that permit an attacker to arbitrarily overwrite data. FreeBSD has long made use of the NX flag for userspace mappings whenever possible, but only in the past several years has it been applied to kernel mappings. A recent project has sought to implement a W^X-by-default policy for the amd64 kernel by completing an audit of the remaining executable mappings in the kernel, and making modifications to either apply the NX bit to those mappings or to make them read-only. This work has landed in HEAD and will be available in FreeBSD 13.0 and 12.2. Similar work for other CPU architectures is also planned. To help audit kernel mapping protections, the vm.pmap.kernel_maps sysctl was added; it dumps a snapshot of the kernel's page table entries and their attributes. This way, mappings violating the W^X policy can easily be discovered and investigated, and the sysctl provides information useful to anyone interested in kernel memory layout. With a few rare exceptions, the only kernel mappings which require execute permission are those of the kernel executable itself, and loadable kernel modules. A number of other regions of memory were unnecessarily being mapped without NX, and these were identified and corrected first. To address the kernel code mappings, the amd64 kernel linker script was modified to pad the .text segment to a 2MB boundary. To improve performance, the kernel creates superpage mappings of its .text segment, but this means that any data cohabiting the final 2MB .text mapping is mapped with execute permissions. The padding allows executable code to be segregated from data which follows in the kernel image, avoiding this problem and maintaining the superpage optimization at the expense of some wasted RAM. Enforcing W^X turned out to be somewhat trickier. Unlike other CPU architectures supported by FreeBSD, amd64 kernel modules are linked as relocatable object files, i.e., .o files. (On other architectures, they are dynamically shared objects (DSOs, or .so files), as one might naively expect.) The use of .o files means that amd64 kernel modules contain more efficient code than they would if linked as DSOs, since DSOs inherently make use of certain types of indirection which allow shared libraries to be loaded at arbitrary addresses, and this indirection is useless in the kernel. As part of this project an attempt was made to switch amd64 to using DSOs as well, since the cost of this indirection can largely be mitigated with modern toolchains, but it was found that the use of DSOs would also force a change to the code model used when compiling amd64 kernel code, resulting in a further performance penalty. The main obstacle with the use of .o files is that sections are not page-aligned by default; the segregation of sections with differing mapping protection requirements is done by the static linker when linking a DSO or executable file. Since mapping protections are applied at the granularity of the page size (4KB on amd64), the overlap of sections within a page causes problems since, for example, the end of the read-only .text section may overlap with the beginning of the read-write .data section. One possible solution is to perform any required section reordering and padding at kernel module load time, but this approach breaks debugging tools such as dtrace(1) and kgdb which assume that the kernel linker does not modify the layout of loadable modules. As a result, an amd64 kernel module linker script is now used to insert padding for specific sections. Finally, the kernel linker was modified to restrict mapping protections based on section flags. As a result of all of this, amd64 kernels now boot without any writeable, executable mappings. Though some of the work was architecture-specific, much of it can and will be leveraged to provide the same policy for our other supported architectures. This project was sponsored by Netflix. __________________________________________________________________ Kernel ZLIB Update Contact: Xin Li Contact: Yoshihiro Ota The ZLIB is a compression library is widely used in various software. The FreeBSD system had used an ancient (over 20 year-old) version of zlib (version 1.0.4) and total of 3 versions, one in user-land, one in ZFS, and one in kernel. Xin and Yoshihiro upgraded zlib to the latest and eliminated 2 extra copies. Along the efforts, zlib version was upgraded to 1.2.11, netgraph's ppp is re-implemented to use the standard zlib, and removed unmaintained code. We now only have one and the latest version of zlib in FreeBSD code base, new compress, compress2, and uncompress APIs exposed in the kernel, and importing changes from zlib will be simple. Kernel zlib changes * sys/crc32.h is split to avoid object file name conflict with ZLIB's * contrib/zlib is moved to sys/contrib/zlib * Kernel started switching to sys/contrib/zlib and ZFS copy dropped * Kernel zcalloc is introduced and compress, compress2, and uncompress APIs are exposed to kernel * Removed zlib 1.0.4 from kernel Kernel zlib user updates * kern_ctf.c updated * opencryptodeflate updated * geom_uzip updated * subr_compressor updated * if_mxge updated * bxe updated * ng_deflate updated Legacy code removals * Removed MIPS zlib elf trampoline * Removed kgzip and kgzldr * Removed gzip'ed a.out support * Removed ArmvX elf_trampoline.c __________________________________________________________________ PROT_MAX mmap/mprotect maximum protections API Links PROT_MAX commit URL: https://reviews.freebsd.org/rS349240 Contact: Brooks Davis Unix-like systems provide the mmap(2) system call to allocate memory or map files or devices into memory with specified access protection, and the mprotect(2) system call to change protections on mapped memory. Protection flags specify whether the memory may be read, written, and/or executed (PROT_READ, PROT_WRITE, PROT_EXEC respectively). Traditionally, mprotect(2) can be used to set any desired protections (except that a shared mapping of a file opened read-only cannot have PROT_WRITE set). A new macro PROT_MAX() adds a facility for specifying the maximum possible protection flags for mmap(2) and mprotect(2) calls. The program can then specify whether a mapping may be changed in the future to allow a given access protection. For example, a memory mapping can be set such that it can have read and write protections set, but may never be made executable. Maximum protection values are provided to the PROT_MAX() macro, and are OR'd with regular protection values. This change allows (e.g.) a region that must be writable during run-time linking or JIT code generation to be made permanently read+execute after writes are complete. This complements Write-XOR-Execute (W^X) protections available on other operating systems, allowing more precise control by the programmer. For example, to request memory that cannot be made executable: mmap(NULL, size, PROT_READ | PROT_WRITE | PROT_MAX(PROT_READ | PROT_WRITE), MAP_ANON, -1, 0); and to request memory that may have execute permission enabled later on, but is not currently executable: mmap(NULL, size, PROT_READ | PROT_WRITE | PROT_MAX(PROT_READ | PROT_WRITE | PROT_EXECUTE), MAP_ANON, -1, 0); This change alters mprotect argument checking and returns an error when unhandled protection flags are set. This differs from POSIX (in that POSIX only specifies an error if a valid permission can not be set), but is the documented behavior on Linux and more closely matches historical mmap behavior. In addition to explicit setting of the maximum permissions, an experimental sysctl vm.imply_prot_max causes mmap to assume that the initial permissions requested should be the maximum when the sysctl is set to 1. This behavior is known to break code that uses PROT_NONE reservations before mapping contents into part of the reservation. A later version of this work is expected to provide per-binary and per-process opt-in/out options and this sysctl may be removed in its current form. As such it is undocumented. While these flags are non-portable, they can be used in portable code with simple ifdefs to expand PROT_MAX() to 0. Sponsors: DARPA, AFRL __________________________________________________________________ Randomized Top of Stack pointer Contact: Konstantin Belousov After the ASLR so useful addition, next in the series of the buzzword-compliant checkboxes is the stack addresses randomization. The main userspace thread stack on FreeBSD is traditionally allocated from the top of the user address space and grows down. Besides the initial pointer for the stack on userspace entry, this area also contains structures for program arguments and environment (so called strings), and aux vector data for ELF images. Considering the goal of randomizing the addresses of strings and main thread initial frame, moving the main stack area in the address space is not feasible. It would cause significant ABI breakage, invalidates the knowledge already coded into many introspection tools, and causes unneeded additional fragmentation of the user address space. Instead a typical approach of adding a gap of randomized size between top of stack and a place for strings was used. It is done in a way which preserves the stack alignment requirement. Stack gap is only enabled if ASLR is enabled (not default) and stack gap itself is enabled (default if ASLR is enabled). Stack gap is specified in percentage of the total stack size that can be used for maximum gap. The main drawback of the gap approach was shortly identified. Since gap is cut from the normal stack area, attempts of the programs to reduce stack size using rlimit(RLIMIT_STACK) could cut the active stack region if new limit happens to be smaller than the gap. E.g. on amd64 with its default 512M main thread stack, even one percent of the max gap gives approximately 5M of unused stack, that can blow up the limit of several KBs. Typical reason for using rlimit(2) this way is for programs that wire all of its address space with mlockall(2), trying to reduce potential wired stack size to avoid exceeding RLIMIT_MEMLOCK. First victim of that issue was ntpd, which resets the stack limit after start for a really small value. Currently the wiring was removed from ntpd, because apparently it does not make the timekeeping better by any means, contrary to popular belief. My opinion is that the problem is more in the user interface area than in the gap approach itself. We should make it easy to specify small gap sizes, which cannot be done with integral percentage interface. So far I did not formulated a way to do this which I would like, and since nobody looked for a good solution because after ntpd was fixed, the severity of the issue seems very low. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ Signals delivered on unhandled Page Faults Contact: Konstantin Belousov By necessity, handling of page faults is separated into two pieces. The first is the architecture-dependent low-level machine exception handler, and the second is the architecture-independent vm_fault() function in sys/vm/vm_fault.c. Machine-dependent code for page faults typically consists of three components: a trampoline written in assembly which creates the C execution environment and gathers hardware-supplied data about page fault reason, a trap() function which is common C-level entry point to dispatch all exceptions processing, and the trap_pfault() C function to specifically handle page faults. trap_pfault() calls vm_fault() when help from VM is needed to resolve the situation. If the fault was handled either by trap()/trap_pfault() or vm_fault(), the faulting instruction is restarted. If fault cannot be handled for any reason, the next action depends on the mode in which the fault occured. If it was in kernel, and the kernel installed a helper, then the helper is called instead of returning to the faulting instruction. Otherwise, a kernel-mode page fault causes a panic. If the unhandled fault occured in usermode, then all Unixes send a signal to the thread whose execution caused the exception. POSIX (or Single Unix Specification) lists several cases where a signal should be sent, and specifies the signal number and si_code from siginfo that must be supplied with the signal. Unfortunately, FreeBSD was rather non-compliant in this regard. A long time ago, to improve compliance, we changed the signal sent on access to a page with permissions incompatible with the access mode. That caused multiple problems with garbage collection (GC)-based runtimes which incorporated knowledge of the FreeBSD quirks, so the machdep.prot_fault_translation sysctl knob was added. More cases of incompatibility were identified recently. Part of the problem is that code to calculate the signal and si_code from the Mach error returned by vm_fault() was located in trap_pfault(). In other words, each architecture did that on its own, with a specific set of bugs and non-compliance. Sometimes code even mis-interpreted returned Mach errors as errno. A new helper function vm_fault_trap() was added, that does several things for trap handlers: it creates ktrace points for faults, calls vm_fault(), and then interprets the result in terms of the user-visible error condition, returning precalculated signal number and si_code to the caller. Now trap_pfault() only needs to provide signal numbers for truly machine-dependent errors. For amd64, an example of such a case is a protection key violation. Besides compliance and bug fixes, we also provided some refinements to userspace about the reason of the delivered signal. For instance, on SIGBUS caused by copy-on-write failure due to exceeding swap reservation limit, we provide specific si_code BUS_OOMERR. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ Architectures Updating platform-specific features and bringing in support for new hardware platforms. Broadcom ARM64 SoC support Contact: Michal Stanek Contact: Kornel Duleba Contact: Marcin Wojtas The Semihalf team continued working on FreeBSD support for the Broadcom BCM5871X SoC series BCM5871X are quad-core 64-bit ARMv8 Cortex-A57 communication processors targeted for networking applications such as 10G routers, gateways, control plane processing and NAS. Completed since the last update: * iProc PCIe root complex (internal and external buses): fixes and improvements, * Crypto engine acceleration for IPsec offloading. Todo: * Upstreaming of work. This work is expected to be submitted/merged to HEAD in the Q4 of 2019. This project was sponsored by Juniper Networks, Inc. __________________________________________________________________ FreeBSD support for the forthcoming Arm Morello CPU, SoC, and board Contact: Robert Watson Contact: Andrew Turner Contact: Brooks Davis In September 2019, Arm announced Morello, an experimental multicore superscalar ARMv8-A CPU, SoC, and prototype board extended to implement the CHERI protection model. Morello will become available in 2021. More details can be found in Arm's blog, a Light Blue Touchpaper blog, and the main CHERI website. We have updated CheriBSD, a CHERI-adapted version of FreeBSD originally targeted at the MIPS-based SRI/Cambridge CHERI processor prototype, to support the current draft architecture. This includes full userspace spatial and referential memory safety CheriABI, as well as backwards compatibility to support running existing ARMv8-A userspace binaries. We will continue to update CheriBSD/Morello as the ISA is finalised. Will also closely track the public CheriBSD/MIPS trunk, picking up new software features utilizing CHERI as they mature, as well as to pick up changes from the baseline FreeBSD development trunk. We currently anticipate releasing CheriBSD/Morello as open source once the ISA and toolchain are published in 2020. Sponsors: DARPA, AFRL __________________________________________________________________ FreeBSD/powerpc Project Links Status of FreeBSD ports on PowerPC URL: https://wiki.freebsd.org/powerpc/ports Status of FreeBSD ports on PowerPC built using gcc URL: https://wiki.freebsd.org/powerpc/ports/PortsOnGcc Status of FreeBSD ports on PowerPC built using clang URL: https://wiki.freebsd.org/powerpc/ports/PortsOnClang Bringing LLVM to PowerPC64 target, using OpenPower ELF v2 ABI URL: https://wiki.freebsd.org/powerpc/llvm-elfv2 Contact: Mark Linimon (ports) Contact: Justin Hibbits (src) Contact: Piotr Kubaj (ports) The FreeBSD/powerpc project continues to make great strides. However, as we discovered at BSDCan 2019, we have not done a great job of letting people know. Key points: * powerpc64 src on recent hardware has been production-quality for over a year now. * powerpc64 ports has been developer-quality for over 18 months now. The main targeted platforms: * powerpc64 on IBM POWER8 and POWER9 chips (the most recent available). This is the primary focus going forward. FreeBSD 12 is required; FreeBSD 13 is recommended. * powerpc64 on older Apple Power Macs, on a continuing but secondary basis. Any FreeBSD version should work. * powerpc64 on x5000. However, this is still developer-only quality. FreeBSD 13 is recommended. * powerpcspe on Amiga A1222. However, this is still developer-only quality. FreeBSD 13 is recommended. The software status: * powerpc*/12 and earlier still remain on the antiquated gcc4.2.1 in base. * powerpc*/13 will soon be switched to llvm90 in base. A great deal of work has been undertaken to ensure as few regressions as possible. Once that switch has occurred (see llvm-elfv2 link above), powerpc*/13 support on gcc4.2.1 will no longer be a priority. * FreeBSD.org package sets are available for powerpc64/12 (quarterly) and powerpc64/13 (default) through the usual method. * Firefox works on powerpc64 using experimental (not-yet committed) patches, * As of the most recent package build on powerpc64/13 (still gcc4.2.1), the following statistics apply: Queued Built Failed Skipped Ignored 33306 30514 245 1686 861 * More ports fixes are being committed every day. Also, Piotr would like to thank the FreeBSD Foundation for funding his personal Talos, and Raptor (via its IntegriCloud subsidiary) for loaning a server on which talos.anongoth.pl runs. The team would like to thank IBM for the loan of two POWER8 machines, and Oregon State University (OSU) for providing the hosting. As well, we would like to thank the clusteradm team for keeping the Tyan POWER8 machines online that are hosted at NYI. __________________________________________________________________ NXP ARM64 SoC support Contact: Marcin Wojtas Contact: Artur Rojek The Semihalf team initiated working on FreeBSD support for the NXP LS1046A SoC LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with integrated packet processing acceleration and high speed peripherals including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide range of networking, storage, security and industrial applications. Completed since the last update: * DPAA Network interface support * SD/MMC * USB3.0 * I2C * GPIO In progress: * QSPI * Network performance improvements Todo: * Upstreaming of developed features. This work is expected to be submitted/merged to HEAD in the Q4 of 2019. This project was sponsored by Alstom Group. __________________________________________________________________ Userland Programs Changes affecting the base system and programs in it. gets(3) retirement Contact: Ed Maste gets is an obsolete C library routine for reading a string from standard input. It was removed from the C standard as of C11 because there was no way to use it safely. Prompted by a comment during Paul Vixie's talk at vBSDCon 2017 I started investigating what it would take to remove gets from libc. The patch was posted to Phabricator and refined several times, and the portmgr team performed several exp-runs to identify ports broken by the removal. Symbol versioning is used to preserve binary compatibility for existing software that uses gets. The change was committed in September, and will be in FreeBSD 13.0. This project was sponsored by The FreeBSD Foundation. __________________________________________________________________ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. FreshPorts Links FreshPorts URL: https://www.FreshPorts.org/ git_proc_commit code URL: https://github.com/FreshPorts/git_proc_commit Things you didn't know FreshPorts can do URL: https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/ Contact: Dan Langille FreshPorts consolidates commits into an easy-to-follow format so you can track changes to your favorite ports. It also processes src, doc, and www commit. FreshPorts parses incoming emails and refreshes the database with what it finds. In early September I started looking at how FreshPorts could use a git repository for processing commits. The result was an approach for identifying new commits and for iterating through them. The next idea was commit hooks but the most interesting bit of that exercise was commit iteration. At the EuroBSDCon 2019 FreeBSD Developer summit, I wrote up a small requirements section and then received great help from two sources: * Jan-Piet MENS recommended a Python library and it turned out to be great * Sergey Kozlov wrote Python code to create xml using that Python library On the trip home, I was able to get the code to parse a git commit into XML and loaded into a FreshPorts database. Returning home from the conference, I created a new FreshPorts instance for processing git based on the above. The website has needed no changes related to git. The remaining tasks: * automate the script (git pull, etc) * detect new commits (for later iteration) * design a light-weight git hook Event: EuroBSDCon 2019 Hackathon Sponsored by: Intel Corporation (work done by Sergey Kozlov) __________________________________________________________________ Java on FreeBSD Links OpenJDK 11 repository at FreeBSD GitHub URL: https://github.com/freebsd/openjdk-jdk11u Contact: Greg Lewis Over the last few quarters there has been considerable work in improving support for Java 11 and higher, with some work being backported to Java 8. Starting with the initial release in March on amd64, over the intervening months FreeBSD support was added for features such as: * Java Flight Recorder * HotSpot Serviceability Agent * HotSpot Debugger * DTrace * Javac Server * Java Sound * SCTP In addition, support for the aarch64, i386 and powerpc64 architectures was also added. With most features supported, attention turned to compliance, using the internal JDK test suite as a method of measuring this. Most work during the third quarter has focused on this, with test failures dropping from 50+ failures to only 2 tier1 test failures (which don't appear to impact functionality at all). Some significant fixes include: * A stack overflow crash * Errors in external process handling * The unpack200 utility (on little endian systems) * HotSpot Debugger functionality such as thread enumeration * Networking functionality Finally, this work has been forward ported to Java 12 and 13, with FreeBSD gaining support for these versions on or just after the day of release. Note that this work has been a collaboration with many others. While there are too many contributors to list here (please take a look at the commit history of the GitHub repository), I'd like to recognise Kurt Miller of OpenBSD for his tireless work as a co-collaborator on Java for BSD through many years. I'm also grateful to the sponsorship of the FreeBSD Foundation, which has allowed me to focus on this work for Q3. This project was sponsored by FreeBSD Foundation. __________________________________________________________________ KDE on FreeBSD Links KDE FreeBSD URL: https://freebsd.kde.org/ KDE Community FreeBSD URL: https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages the software produced by the KDE Community for FreeBSD. The software includes a full desktop environment, the art application https://kdenlive.org and hundreds of other applications that can be used on any FreeBSD desktop machine. Along with KDE itself, the team maintains the Qt libraries, the CMake build system, and a handful of other C++ libraries used in the KDE stack. The upstream releases KDE Frameworks (libraries) on a monthly cycle, KDE Plasma (the desktop environment) quarterly and a collection of KDE Applications (usable everywhere) twice a year. The KDE on FreeBSD team chased a dozen updates to these components so that FreeBSD remains one of the most up-to-date systems with KDE software (and Qt). A large (and possibly breaking, still needs more investigation) change came with the release to KDE's Digikam 6.3.0, which stopped using its previous plugins system (the "old" plugins are still used by other KDE software). A new entry in the net-im category was added for Ruqola, a Rocket.chat client for rich instant-messaging. CMake was updated twice. This forces the rebuild of several thousand C++-based ports. The KDE on FreeBSD team then fixes those ports, regardless of whether the error is in the CMake update, or in the upstream code. These updates tend to take a large amount of effort, since they touch unfamiliar (and often very-very-legacy) code. The open bugs list grew to 24 this quarter. It tends to hover around 20 items as new things come in and old ones are resolved. We welcome detailed bug reports and patches. KDE packaging updates are prepared in a copy of the ports repository on GitHub and then merged in SVN. We welcome pull requests there as well. __________________________________________________________________ Ports Collection Links About FreeBSD Ports URL: https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/index.html Ports Management Team URL: https://www.freebsd.org/portmgr/index.html Contact: René Ladan Contact: FreeBSD Ports Management Team The FreeBSD Ports Management Team, tasked with overseeing the Ports Tree and its committers, reports that the following events happened during 2019Q3: The number of ports grew to just under 38,000 during the last quarter. We have just over 2,000 open ports PRs, of which 400 are unassigned. In this period, 169 committers made 7,340 commits to HEAD and 561 commits to the quarterly branch. This shows that the trend of last quarter of increased activity is continuing. During the last quarter, we welcomed Santhosh Raju (fox@) and Dmitri Goutnik (dmgk@) to the team, and said goodbye to gabor@. During the last quarter, feld@ decided to step down from the portmgr@ and ports-secteam@ teams. We would like to thank them for their past services. In the last three months, bapt@ put on his engineering hat and released a new version of pkg (1.12), added support for overlays to the Ports Tree, fixed two Make targets (deinstall-depends and reinstall), and cleaned up bsd.sites.mk. On the infrastructure side, USES=pure became obsolete and has therefore been removed, and two new USES, xorg and xorg-cat have been added and replace the old bsd.xorg.mk. Two new keywords, ldconfig and ldconfig-linux, were added to simplify formatting of package lists. A number of default versions changed: Lazarus to 2.0.4, Linux to CentOS 7, LLVM to 9.0, Perl to 5.30, PostgreSQL to 11, and Ruby to 2.6. Of the big user-visible ports, Firefox got updated to 69.0.1, Firefox-esr to 68.1.0, Chromium to 76.0.3809.132, and Xfce to 4.14. During the last quarter, antoine@ ran 48 exp-runs to test package updates, test updating bsd.java.mk, test the new ldconfig and ldconfig-linux keywords, test default version updates, test the new xorg and xorg-cat USES, test base updates, and test various improvements to Go and Ruby. __________________________________________________________________ XFCE 4.14 update Links XFCE 4.14 announce URL: https://xfce.org/about/news/?post=1565568000 Contact: Guido Falsi On September 19th the XFCE desktop environment ports have been updated to the recently released XFCE 4.14 version. These updates include upgrades of all the main XFCE components to the latest versions which have been migrated to GTK3, with few exceptions. Base components still require and link to GTK2 in addition to GTK3 to allow older GTK2 XFCE applications, for example panel plugins, to keep working. Due to this change the gtk-xfce-engine theme is deprecated since it only supports GTK2. The XFCE metaport by default installs the greybird theme, but it is not enabled by default. This new version also includes now it's own xfce4-screensaver program which is installed by default. Finally the default Display Manager on which XFCE depends has been changed to LightDM. Some regressions were reported in bugzilla. In particular the one affecting most users is a regression in the window manager: on specific graphic display hardware the window manager fails to properly draw window decorations, which appear black and blocky on affected systems. This problem has also been reported in the upstream bug tracker and a solution is being sought. If anyone is experiencing this display glitch and is able to test, please contact xfce@freebsd.org to help trying to figure out a solution. __________________________________________________________________ Third-Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. ClonOS: virtualization platform on top of FreeBSD Operating System Links ClonOS 19.09 URL: https://clonos.tekroutine.com/download.html CBSD URL: https://www.bsdstore.ru/ Contact: Oleg Ginzburg What is ClonOS? ClonOS is a turnkey open-source platform based on FreeBSD and the CBSD framework. ClonOS offers a complete web UI for an easy control, deployment and management of FreeBSD jails containers and bhyve/Xen hypervisor virtual environments. ClonOS is currently the only available platforms which allow both Xen and bhyve hypervisors to coexist on the same host. Since ClonOS is a FreeBSD-based platform, it has the ability to create and manage jails natively, allowing you to run FreeBSD applications without losing performance. ClonOS/CBSD 2019Q3 Status Report * Added support for cloud-init (Linux/BSD VMs) and cloudbase-init (Windows VMs). It gives the ability to use FreeBSD as IaaS platform for instant deployment and usage of virtual machines based on bhyve hypervisor. * Project started to use own cloud images for better stability and resiliency. * New mirrors in France, US and Canada were added for distributing ISO/cloud-init images in addition to Russia, Latvia and Ukraine. * Now we're using Jenkins CI for testing regular ClonOS builds: Update clonos packages (Thanks to Daniel Shafer) * New pkg repository was deployed to support ClonOS installation from packages (at this moment only FreeBSD-12 packages are available) ClonOS package repo (Thanks to Daniel Shafer) Open issues and tasks: * Volunteers, contributors and testers are urgently needed to distribute ClonOS on FreeBSD environments. * We'd like to expand our mirrors number geographically, your help and contribution will be much appriciated. * We're urgently looking for hosting sponsorship for various developing and testing activities. __________________________________________________________________ ENA FreeBSD Driver Update Links ENA README URL: https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README Contact: Michal Krawczyk Contact: Maciej Bielski Contact: Marcin Wojtas ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. ENAv2 has been under development for FreeBSD, similar to Linux and DPDK. Since the last update internal review and improvements of the patches were done, followed by validation on various AWS instances. Completed since the last update: * Verification and review of the NETMAP support * Mapping of the memory as WC on A1 instances in order to enable LLQ mode Todo: * Upstream of NETMAP support * Upstream of the fix for LLQ mode on A1 instances Amazon.com Inc __________________________________________________________________ Nomad pot driver - Orchestrating jails via nomad Links Nomad pot driver URL: https://github.com/trivago/nomad-pot-driver Pot project URL: https://github.com/pizzamig/pot Contact: Luca Pizzamiglio Contact: Esteban Barrios An experimental project has started to provide jail orchestration based on nomad and the jail framework pot, similarly to how orchestration works with docker. This model allows us to split the jail creation and the jail deployment. Jail images can be created and exported using the pot framework. The images can be deployed and orchestrated using nomad. A driver has been developed to allow nomad to interact with pot. One of the goals of this project is to use non-persistent jails as containers, allowing us to: * define containers similar to Docker (but not identical, because the underlaying OS is different) * identify potential missing features in FreeBSD to support such a computational model In the next quarter, we will launch the first service based on this project. Next steps are: * provide more guides and howtos * improve stability, extending the tests suite * improving tooling to create/manage images This project was sponsored by trivago N.V.. __________________________________________________________________ sysctlinfo Links gitlab.com/alfix/sysctlinfo URL: https://gitlab.com/alfix/sysctlinfo Contact: Alfonso Sabato Siciliano The FreeBSD kernel maintains a Management Information Base (MIB) where a component (object) represents a parameter of the system. The sysctl system call explores the MIB to find an object by its Object Identifier (OID) and calls its handler to get or set the value of the parameter. It is often necessary to find an object not to call its handler but to get its info (description, type, name, next object, etc.), so the kernel provides an undocumented interface implemented in kern_sysctl.c. sysctlinfo is a new interface to explore the sysctl MIB and to pass the info of an object to the userland. The project provides: a README, a manual, helper macros, examples, tests and converted tools. Primarily sysctlinfo provides a new set of sysctl nodes (corresponding to the kernel interface) to handle an object up to CTL_MAXNAME levels: sysctl.entryfakename, sysctl.entrydesc, sysctl.entrylabel, sysctl.entrykind, sysctl.entryfmt and sysctl.entrynextleaf. Moreover new features have been implemented: the support for the capability mode, sysctl.entryname, sysctl.entryidbyname and sysctl.entrynextnode. To get all the info about an object the kernel needs to find it many times, then the new sysctl.entryallinfo* nodes were written, they are 30% more efficient. Finally, *byname nodes were added: they search the object by its name avoiding to call sysctl.name2oid (or similar) to explore the MIB just to find the corresponding OID. sysctlinfo can be installed via sysutils/sysctlinfo-kmod or by applying the sysctlinfo.diff patch (more efficient than the module because uses a shared lock). The interface is used by deskutils/sysctlview 1.5, sysutils/nsysctl 1.2 and the converted version of sysctl(8), sysctlbyname(3), sysctlnametomib(3), they should be used to get the value of an object with 23/24 levels or if some level-name has only the '\0' character. In the future a new byname node will be added to allow sysctlbyname() to manage a CTLTYPE_NODE with a no-NULL handler, example sysctlbyname("kern.proc.pid.\"). __________________________________________________________________ From owner-freebsd-current@freebsd.org Tue Nov 26 13:54:39 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8F78F1B74F3 for ; Tue, 26 Nov 2019 13:54:39 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Mll33MDhz3MgB for ; Tue, 26 Nov 2019 13:54:39 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from mail-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 3EA8B14114 for ; Tue, 26 Nov 2019 13:54:39 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: by mail-oi1-f170.google.com with SMTP id v138so16696847oif.6 for ; Tue, 26 Nov 2019 05:54:39 -0800 (PST) X-Gm-Message-State: APjAAAVK5Q8L06m1W/fdWucAQZ7op7DAlt/tETtEVk46RaOtoYQkf/6W rvakI7uyu/WhnQOzyJMCOCpgSyvEdsQZkEkexvM= X-Google-Smtp-Source: APXvYqz3IGHdMc7cqLvs3pOo4iI/3wzLd+r5PmWnDPiaZX2+wZQSMsacU0DLeAMaCH/Hje1Z66mJVl6UtD+RzwvPdDE= X-Received: by 2002:a05:6808:611:: with SMTP id y17mr3615962oih.24.1574776478417; Tue, 26 Nov 2019 05:54:38 -0800 (PST) MIME-Version: 1.0 References: <4e366b17-25ae-5b89-79ad-e1e113149494@blastwave.org> In-Reply-To: <4e366b17-25ae-5b89-79ad-e1e113149494@blastwave.org> From: Mitchell Horne Date: Tue, 26 Nov 2019 08:54:27 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: GCC 8.x or 9.x for FreeBSD rv64imafdc ?? To: Dennis Clarke Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 13:54:39 -0000 On Tue, Nov 26, 2019 at 3:57 AM Dennis Clarke wrote: > > > ---------------------------------------------------------------- > I will cross post this as there are very few options left. > ---------------------------------------------------------------- > rv64imafdc folks : > > I will send this out to the only people and places that are likely to > not simply be a black hole from which nothing ever returns. However > most of my messages do just die on the mail lists with no reply from > anyone ever and that is very true for the gcc maillists for anything > RISC-V related. I wish I knew why. > > I am able to checkout and cross compile FreeBSD 13.0-CURRENT r354873 > however there is no compiler. I looked. The output destination rootfs > shows no signs of LLVM/Clang and certainly not gcc of any flavor. > > I do see wonderful things like : > > > https://github.com/freebsd-riscv/riscv-gcc/commit/be9abee2aaa919ad8530336569d17b5a60049717 > > > However nothing actually usable by any user out here in the more or less > real world that is not inside SiFive or similar. > > So is there any place at all that one may attain a compiler or am I left > to decipher the horrific mess that is known as the Canadian cross > compiler bootstrap which has never worked for me. > As of r354660, clang is built as part of buildworld. If you are using r354873 then you should have it as /usr/bin/clang, perhaps you just need to regenerate your rootfs. Cheers, Mitchell > -- > Dennis Clarke > RISC-V/SPARC/PPC/ARM/CISC > UNIX and Linux spoken > GreyBeard and suspenders optional > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Tue Nov 26 18:00:11 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2EADC1BD64D for ; Tue, 26 Nov 2019 18:00:11 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47MsBL332yz45XH for ; Tue, 26 Nov 2019 18:00:10 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x432.google.com with SMTP id w9so23632747wrr.0 for ; Tue, 26 Nov 2019 10:00:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=VJSRZQ9A9tsg4J9XjePb7Rt7QL+aXDPv3oIIY4P0+Is=; b=MIhCcmglV1jGTEcgFaPpxOy6d1djMh/dnyrUyhQX8Ij9PfOicf90V47ATdJ2tliN9y Qhk1gEPxaMsbZOmIqfuT6b8ZjEEgX1MTO7B7BDPIP9XhXQqY7LabMhAWWU9GCjdCbhsx D1Yhj9ljNvpRS+IMBouJWQSaO7ooCg0qWVwKkRKFmRFtR34ybycQU7Yu83JS0TR4YcZv Z7S4SWRI0qvt4eJhgdVcigb/TEEChHeMI/ITFbNMd16KbVMlDu7LDdV5ytiZ8rV8KhPq 99/p70E6F/I8VhgAsuFbDNpKVlVG8gJTa27nAMXYE3viT+VUkKMHX6r6fQbscoAGdtcB v73w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=VJSRZQ9A9tsg4J9XjePb7Rt7QL+aXDPv3oIIY4P0+Is=; b=tCJ6/J4e+o1POEfq8MjTDy3+tHE01KQsTdmSxREoUENkYAhdyBdkOPibAv2eK/x/h3 x6e6qMMJ5jod7DvATAuJa/ipoP33AxkYiUtHJqSzddIPII6x4wjzGvdesRMDSMKXisO3 Kg/ioeerrCJ/TJxlwT4u3Hvu2igNmYSA6u82AIDzVkBLIQ3FLV/e0Mz9/isbmcrCb8N2 Bsuwkq5pNYrtwk1Y97/yTjdmJx7VwEo2o8z6iHDrqAj8/GYCH0wWIA6FXCN9Ne40TeXv A96Apqd2d3vVZtgRvawcw28DrMbBPCsJwIRkfzkg2RTeZ6RH+rubX+yy4b+n6/gs8RXl oa1Q== X-Gm-Message-State: APjAAAVpuavourGAm3eUfdXkYv3zpor1YSA57pOArHzi0+npR4v79dVu CPMNo3tewl0U1R459NTxiBzrX88M4Sw= X-Google-Smtp-Source: APXvYqw72i5rGlgIQjGDDRC72OT5SjDVX2qAtmLM+REDV3na9K87NcmrE4hd2i/KDlRxactwmoQ2kA== X-Received: by 2002:adf:e5c5:: with SMTP id a5mr39721810wrn.103.1574791207312; Tue, 26 Nov 2019 10:00:07 -0800 (PST) Received: from [192.168.1.7] (host-2-100-169-93.as13285.net. [2.100.169.93]) by smtp.gmail.com with ESMTPSA id w188sm4167833wmg.32.2019.11.26.10.00.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Nov 2019 10:00:06 -0800 (PST) To: FreeBSD CURRENT From: Graham Perrin Subject: =?UTF-8?Q?Firefox=3a_recommendations_=e2=80=93_Pocket?= Message-ID: <906002a4-40af-f3f0-ebf5-8318a5c4779f@gmail.com> Date: Tue, 26 Nov 2019 18:00:05 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 47MsBL332yz45XH X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=MIhCcmgl; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::432 as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[93.169.100.2.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ip: (-9.39), ipnet: 2a00:1450::/32(-2.70), asn: 15169(-1.95), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[2.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 18:00:11 -0000 For a few months I got recommendations from Pocket. No longer. Is the code removed? Or has Mozilla become stricter about enforcing regional restrictions? (I'm in the UK.) From owner-freebsd-current@freebsd.org Tue Nov 26 19:04:03 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 775F61BED40 for ; Tue, 26 Nov 2019 19:04:03 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from jax4mhfb01.myregisteredsite.com (jax4mhfb01.myregisteredsite.com [64.69.218.94]) (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 47Mtc15701z490J for ; Tue, 26 Nov 2019 19:04:00 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from jax4mhob05.myregisteredsite.com (jax4mhob05.myregisteredsite.com [64.69.218.85]) by jax4mhfb01.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id xAQIwitD009090 for ; Tue, 26 Nov 2019 13:58:45 -0500 Received: from mailpod.hostingplatform.com (atl4qobmail01pod2.registeredsite.com [10.30.77.35]) by jax4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id xAQIwd23014400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 26 Nov 2019 13:58:39 -0500 Received: (qmail 5410 invoked by uid 0); 26 Nov 2019 18:58:39 -0000 X-TCPREMOTEIP: 99.253.169.68 X-Authenticated-UID: dclarke@blastwave.org Received: from unknown (HELO ?172.16.35.2?) (dclarke@blastwave.org@99.253.169.68) by 0 with ESMTPA; 26 Nov 2019 18:58:39 -0000 Subject: Re: [sw-dev] GCC 8.x or 9.x for FreeBSD rv64imafdc ?? To: sw-dev@groups.riscv.org, FreeBSD CURRENT References: <5bca6745-1c09-3ba7-3b4a-2456ea2e1081@blastwave.org> From: Dennis Clarke Cc: Ruslan Bukin Message-ID: <1d824d98-dc81-706c-9741-41f363b81323@blastwave.org> Date: Tue, 26 Nov 2019 18:58:38 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Thunderbird/71.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47Mtc15701z490J X-Spamd-Bar: ++++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dclarke@blastwave.org has no SPF policy when checking 64.69.218.94) smtp.mailfrom=dclarke@blastwave.org X-Spamd-Result: default: False [6.39 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; GREYLIST(0.00)[pass,body]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.49)[ipnet: 64.69.218.0/23(0.84), asn: 19871(1.67), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[blastwave.org]; RBL_MAILSPIKE_WORST(2.00)[94.218.69.64.rep.mailspike.net : 127.0.0.10]; NEURAL_SPAM_MEDIUM(1.00)[1.000,0]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; RCVD_IN_DNSWL_NONE(0.00)[94.218.69.64.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:19871, ipnet:64.69.218.0/23, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Spam: Yes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2019 19:04:03 -0000 On 11/26/19 10:18 AM, Bruce Hoult wrote: > I think there are very few people who have experience with the > intersection of FreeBSD and RISC-V. > [warning] long rambling reply full of enthusiasm and hand waving :) Thank you for the reply and yes ! There are very few but it works I tell you it really does work and that is with a ZFS zpool. At least on QEMU for the moment and by Christmas time on the SiFive board. Maybe. Sort of waiting for a new board to pop up with SAS/SATA ports and more memory but Christmas may be here first. I simply can not go forwards with ZFS without memory and lots of it : root@callisto:~ # root@callisto:~ # uname -apKU FreeBSD callisto 13.0-CURRENT FreeBSD 13.0-CURRENT r350568 QEMU riscv riscv64 1300038 1300038 root@callisto:~ # zpool list ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) no pools available root@callisto:~ # > Hopefully Ruslan will reply. > Yes I have a compiler tarball from him that sort of works. When I say "sort of" I mean that I can compile some simple things and everything seems to work however I need to carefully specify where to find libgcc and even libc as there are some oddball paths stuck in his bootstrap result. Easy to work around. May even be enough to get a new bootstrap going of gcc 9.2.0 but I have not been able to get past libgmp. Yet. Maybe later today. Maybe tomorrow. :-\ For now I have been messing with r350568 with ZFS and a gcc from Ruslan but for anything after that I have nothing. I just drag around a tarball and hope for the best. However today I hear that I am slightly blind and that clang does exist in the rootfs : vesta# pwd /opt/rv64/rootfs vesta# ls -lap usr/bin/clang -r-xr-xr-x 3 root wheel 63383544 Nov 26 08:00 usr/bin/clang vesta# vesta# readelf -delV usr/bin/clang ELF Header: Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: RISC-V Version: 0x1 Entry point address: 0x6d48a Start of program headers: 64 (bytes into file) Start of section headers: 63381560 (bytes into file) Flags: 0x5, RVC, double-float ABI Size of this header: 64 (bytes) Size of program headers: 56 (bytes) Number of program headers: 8 Size of section headers: 64 (bytes) Number of section headers: 31 Section header string table index: 30 Section Headers: . . . Dynamic section at offset 0x3c5ac08 contains 30 entries: Tag Type Name/Value 0x0000000000000001 (NEEDED) Shared library: [libz.so.6] 0x0000000000000001 (NEEDED) Shared library: [libexecinfo.so.1] 0x0000000000000001 (NEEDED) Shared library: [libncursesw.so.8] 0x0000000000000001 (NEEDED) Shared library: [libthr.so.3] 0x0000000000000001 (NEEDED) Shared library: [libc++.so.1] 0x0000000000000001 (NEEDED) Shared library: [libcxxrt.so.1] 0x0000000000000001 (NEEDED) Shared library: [libm.so.5] 0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1] 0x0000000000000001 (NEEDED) Shared library: [libc.so.7] 0x000000000000000c (INIT) 0x16d40 0x000000000000000d (FINI) 0x2b7d086 0x0000000000000019 (INIT_ARRAY) 0x3c6b038 0x000000000000001b (INIT_ARRAYSZ) 2976 (bytes) . . . Not too sure how that is going to work with no RUNPATH or RPATH and it needs libgcc. However looking I do see libgcc_s.so.1 in /lib : vesta# ls -l lib/libgcc_s.so.1 -r--r--r-- 1 root wheel 94360 Nov 26 07:58 lib/libgcc_s.so.1 vesta# So this may actually work and be enough to bootstrap with. Maybe. > I see the gcc in that project is pretty old, 6.1.0. I have no idea > whether it would be easier to get 6.1.0 running natively inside > freebsd-riscv and then use it to build a newer gcc, or maybe enough > RISC-V improvements have been made to gcc in the last four years and > 16856 commits that it's better to rebase Ruslan's changes to current > gcc first. Well actually I do have 8.x of some flavour and only from Ruslan. > Maybe Ruslan has a native compiler working. Or maybe not. > > I'm sorry I can't be more helpful but at least it's not a black hole. Not a black hole is a damn fine thing !! Better than I expected in fact. In truth I just need some tools to get off the ground and maybe figure out how pi became pretty much 2.000 thus : root@callisto:/home/dclarke/foo # cat pi.c /************************************************* * The Open Group Base Specifications Issue 6 * IEEE Std 1003.1, 2004 Edition *************************************************/ #define _XOPEN_SOURCE 600 #include #include #include int main ( int argc, char *argv[]) { long double pi128 = 3.1415926535897932384626433832795028841971693993751L; double pi64 = M_PI; printf (" the sizeof(pi128) is %i\n", sizeof(pi128) ); printf (" the sizeof(pi64) is %i\n", sizeof(pi64) ); printf ("pi128 may be %44.38Lg\n", pi128 ); printf ("pi64 may be %18.16g\n", pi64 ); return ( EXIT_SUCCESS ); } The assembly looks perfect as does the static data : # cat pi.s .file "pi.c" .option nopic .text .section .rodata .align 3 .LC2: .string " the sizeof(pi128) is %i\n" .align 3 .LC3: .string " the sizeof(pi64) is %i\n" .align 3 .LC4: .string "pi128 may be %44.38Lg\n" .align 3 .LC5: .string "pi64 may be %44.38Lg\n" .text .align 1 .globl main .type main, @function main: addi sp,sp,-64 sd ra,56(sp) sd s0,48(sp) addi s0,sp,64 mv a5,a0 sd a1,-64(s0) sw a5,-52(s0) lui a5,%hi(.LC0) ld a4,%lo(.LC0)(a5) sd a4,-32(s0) ld a5,%lo(.LC0+8)(a5) sd a5,-24(s0) lui a5,%hi(.LC1) fld fa5,%lo(.LC1)(a5) fsd fa5,-40(s0) li a1,16 lui a5,%hi(.LC2) addi a0,a5,%lo(.LC2) call printf li a1,8 lui a5,%hi(.LC3) addi a0,a5,%lo(.LC3) call printf ld a2,-32(s0) ld a3,-24(s0) lui a5,%hi(.LC4) addi a0,a5,%lo(.LC4) call printf ld a1,-40(s0) lui a5,%hi(.LC5) addi a0,a5,%lo(.LC5) call printf li a5,0 mv a0,a5 ld ra,56(sp) ld s0,48(sp) addi sp,sp,64 jr ra .size main, .-main .section .rodata .align 4 .LC0: .word 3306619320 .word 2221509004 .word 3041149649 .word 1073779231 .align 3 .LC1: .word 1413754136 .word 1074340347 .ident "GCC: (GNU) 8.2.0" However the output is weird : # ./pi the sizeof(pi128) is 16 the sizeof(pi64) is 8 pi128 may be 2.0000076293945362811600603241536472604 pi64 may be 3.141592653589793 However the in memory data is flawless : # echo "16o 1074340347p 1413754136pq" | dc 400921FB 54442D18 # echo "16o 1073779231p 3041149649p 2221509004p 3306619320pq" | dc 4000921F B54442D1 8469898C C51701B8 I did file a bug : Bug 242067 - libc: r354823 riscv64 has a fault in printf() where IEEE754-2008 fp128 data is output wrong https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242067 Which seems to happen down inside _ldtoa.c under gdtoa.c and I did single step all the way through the process on IBM PowerPC64 FreeBSD as well as amd64. Very weird output. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional ps: currently locked in battle with this https://www.twitch.tv/lastmiles From owner-freebsd-current@freebsd.org Wed Nov 27 04:17:27 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3EFAC1C98D0 for ; Wed, 27 Nov 2019 04:17:27 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47N6tb0txGz4d4r; Wed, 27 Nov 2019 04:17:27 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id F1AFF7DC6; Wed, 27 Nov 2019 04:17:26 +0000 (UTC) From: Jan Beich To: Graham Perrin Cc: FreeBSD CURRENT Subject: Re: Firefox: recommendations =?utf-8?Q?=E2=80=93?= Pocket References: <906002a4-40af-f3f0-ebf5-8318a5c4779f@gmail.com> Date: Wed, 27 Nov 2019 05:17:26 +0100 In-Reply-To: <906002a4-40af-f3f0-ebf5-8318a5c4779f@gmail.com> (Graham Perrin's message of "Tue, 26 Nov 2019 18:00:05 +0000") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2019 04:17:27 -0000 Graham Perrin writes: > For a few months I got recommendations from Pocket. > > No longer. Check browser.newtabpage.activity-stream.feeds.section.topstories in about:config I have no clue how it's enabled by default on Tier1 platforms. > Is the code removed? Or has Mozilla become stricter about enforcing > regional restrictions? No clue. Wrong list. gecko@ doesn't touch Pocket code/prefs. > (I'm in the UK.) VPN or did you define the following? pref("browser.search.region", "US"); pref("browser.search.countryCode", "US"); From owner-freebsd-current@freebsd.org Wed Nov 27 17:51:43 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 604CE1B317F for ; Wed, 27 Nov 2019 17:51:43 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47NSy63QSrz4LnJ for ; Wed, 27 Nov 2019 17:51:42 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id s5so27722202wrw.2 for ; Wed, 27 Nov 2019 09:51:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=s2TBN2soWXa6ef0kQYGJjt6gdt4+S2SYt+bGsYriCrY=; b=i1VJql3muPD9eCNyWed+765EBCbOK27KNjFh9vTvTCuyGnut4cKhRD2rRcrFp+I3Ae hAYU+CdnGlSqbVMfnlTlp8PzyM7ygs/tobqybIovVxoiWcz6vrpKzcxgMejZSBUSZtQZ 4Ro2IP+0+hmHv4rVDsfLbHFdct422SGRRfh17jZluYsXknEsbXur/eqg8Whs8jvK1aAQ dV1vhZI9St2hFJVo3bEOAdZnRbig1PL0O7o8FOcRhYBL46iGfPD0nhc2iQQ6vjn0HyQ4 zuNPXjJvfbhfLRwzt5STeUhDEGG2F8K5cBtJ3m62yGpiveH9L/Y9foBDgeliiEUYk15Q y6JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=s2TBN2soWXa6ef0kQYGJjt6gdt4+S2SYt+bGsYriCrY=; b=A842+Ur1jlYM6fYMOZ1QDatoSD1L4f9kStYk3qmkDnG89q7DBwHz/m7aTelpBwyH76 TjBHG5SUnABwt+2yJPLpw6KUfkBHAJMFI61FbnlMIa65Ms0Cdg0opUDlquRJLo9Fs27F muxe2R+qhTF6HUU9W4BwEFZYAYJtjWlmkgEq+leXqQQOpS2v3yUmIMgGC9qNLUiWfflF meLRGqx82l7YvBNmz88KSWFrNJ0EPEp7+Aqr/qF6Oy6Us88gdHzxNhyzVZxWsIx+uJCk gLKOFX8wvcupxj+ARDH7Mzz3m286jnMhGsS7qQOz4zRjSOijuhRXRf3fpVQfLLs2DAb4 BWwA== X-Gm-Message-State: APjAAAUwbjCQYfX4xbMNxVRHS30sOQCSk5bJ0f0RYqsbaX+mIzz2dUJ9 hi4rKSAehDVJFKjSibv/5n2JXg33Lb0= X-Google-Smtp-Source: APXvYqy3bkAWQmWiBRP917BnjaK56FeEEWjJqscwIlKblUwK/QbWhP4enmmOfVSNFIe0Br+mqcgi7g== X-Received: by 2002:adf:f50b:: with SMTP id q11mr43911003wro.343.1574877099968; Wed, 27 Nov 2019 09:51:39 -0800 (PST) Received: from [192.168.1.7] (host-2-100-169-93.as13285.net. [2.100.169.93]) by smtp.gmail.com with ESMTPSA id v20sm7746368wmj.32.2019.11.27.09.51.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Nov 2019 09:51:39 -0800 (PST) Subject: Re: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk To: Hans Petter Selasky Cc: FreeBSD Current References: <21c59b77-5ed3-362e-e36a-322a5a9f65c6@gmail.com> <363d65d5-1b49-ca53-5531-185bf5374fb5@selasky.org> From: Graham Perrin Message-ID: <4a47721c-6f9a-5a8c-640f-56eff478378c@gmail.com> Date: Wed, 27 Nov 2019 17:51:38 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: <363d65d5-1b49-ca53-5531-185bf5374fb5@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 47NSy63QSrz4LnJ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=i1VJql3m; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::433 as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[93.169.100.2.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.11), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2019 17:51:43 -0000 On 26/11/2019 08:15, Hans Petter Selasky wrote: > On 2019-11-26 05:54, Warner Losh wrote: >> So when I committed the sysdir stuff I forgot to add it to the install >> list. I've fixed it now. Either upgrade, or just copy src/share/mk/ >> bsd.sysdir.mk to /usr/share/mk >> >> Warner > > Or: > > make -m /usr/src/share/mk > > --HPS > I updated source to r355121, still getting an error (below). Did I misunderstand the advice? ---- root@momh167-gjp4-8570p:/usr/src # make -m /usr/src/share/mk -j2 buildkernel KERNCONF=GENERIC-NODEBUG … ===> Ports module graphics/gpu-firmware-kmod (all) cd ${PORTSDIR:-/usr/ports}/graphics/gpu-firmware-kmod; env  -u CC -u CXX  -u CPP  -u MAKESYSPATH  -u MK_AUTO_OBJ  -u MAKEOBJDIR MAKEFLAGS="-j 2 -J 15,16 -j 2 -J 15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNCONF=GENERIC-NODEBUG KERNEL=kernel TARGET=amd64 TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/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::/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src  OSVERSION=1300060 WRKDIRPREFIX=/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B clean build ===>  Cleaning for gpu-firmware-kmod-g20191015 ===>  License AMD INTEL accepted by the user ===>   gpu-firmware-kmod-g20191015 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by gpu-firmware-kmod-g20191015 for building ===>  Extracting for gpu-firmware-kmod-g20191015 => SHA256 Checksum OK for FreeBSDDesktop-kms-firmware-g20191015-81315fa_GH0.tar.gz. ===>  Patching for gpu-firmware-kmod-g20191015 ===>  Configuring for gpu-firmware-kmod-g20191015 ===>  Building for gpu-firmware-kmod-g20191015 ===> i915kmsfw (all) ===> i915kmsfw/bxtdmc (all) make[6]: "/usr/src/sys/conf/kmod.mk" line 77: Could not find bsd.sysdir.mk make[6]: Fatal errors encountered -- cannot continue make[6]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa/i915kmsfw/bxtdmc *** Error code 1 Stop. make[5]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa/i915kmsfw *** Error code 1 Stop. make[4]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/usr/ports/graphics/gpu-firmware-kmod/work/kms-firmware-81315fa ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[3]: stopped in /usr/ports/graphics/gpu-firmware-kmod *** [all] Error code 1 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 1 error make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG *** [buildkernel] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildkernel] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src root@momh167-gjp4-8570p:/usr/src # date ; uname -v Wed Nov 27 09:08:01 GMT 2019 FreeBSD 13.0-CURRENT #37 r354945: Thu Nov 21 19:11:47 GMT 2019 root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG root@momh167-gjp4-8570p:/usr/src # bectl list BE       Active Mountpoint Space Created r350684  -      -          1.66M 2019-08-07 19:01 r354082b -      -          108G  2019-10-27 14:08 r354616b -      -          1.37M 2019-11-16 17:35 r354945  -      -          1.29M 2019-11-21 13:06 r354945a -      -          1.39M 2019-11-22 02:26 r354945b -      -          1.61M 2019-11-25 06:04 r355107  -      -          1.32M 2019-11-26 07:59 r355121  NR     /          30.8G 2019-11-27 00:35 root@momh167-gjp4-8570p:/usr/src # From owner-freebsd-current@freebsd.org Thu Nov 28 02:44:51 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C4BE11C16F7 for ; Thu, 28 Nov 2019 02:44:51 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47NhnG54sDz3xGb; Thu, 28 Nov 2019 02:44:50 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1574909082; bh=YcT0x2PFT9Xc1voSEZeDd1RYcdfYRuq4a+tXmwg bx10=; b=RkIP01gRxtFfezhImcGwP7nslFC5z+Ghj5TlWXwzoECjvCEaGHjzDgq tmeSK2R8Hmf74hmU8H0/RMQ3FLPkiffcSTohc3Z2QFC/O/F5e4bJ6OUkkED4lY02 wIg3+Htgp6xQJPSaqy62nh3QgWVgbNzb5kc1uaWOKW5tpuVmbnFg= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 7767D12675; Wed, 27 Nov 2019 21:44:42 -0500 (EST) To: freebsd-current , jeff@freebsd.org From: Michael Butler Subject: SVN r355148/9 breaks build Message-ID: <3e4daebb-cd5d-a9b3-daa1-d335f18e9ec8@protected-networks.net> Date: Wed, 27 Nov 2019 21:44:41 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-NZ Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47NhnG54sDz3xGb X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protected-networks.net header.s=201508 header.b=RkIP01gR; dmarc=none; spf=pass (mx1.freebsd.org: domain of imb@protected-networks.net designates 202.12.127.228 as permitted sender) smtp.mailfrom=imb@protected-networks.net X-Spamd-Result: default: False [-6.22 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[protected-networks.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DKIM_TRACE(0.00)[protected-networks.net:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-3.72)[ip: (-9.80), ipnet: 202.12.127.0/24(-4.90), asn: 5716(-3.87), country: US(-0.05)]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 02:44:51 -0000 Something missing from a header here? Building /usr/obj/usr/src/amd64.amd64/sys/VM01/uma_core.o --- uma_core.o --- /usr/src/sys/vm/uma_core.c:1864:39: error: use of undeclared identifier 'sysctl___vm_uma' zone->uz_oid = SYSCTL_ADD_NODE(NULL, SYSCTL_STATIC_CHILDREN(_vm_uma), ^ /usr/src/sys/sys/sysctl.h:245:44: note: expanded from macro 'SYSCTL_STATIC_CHILDREN' #define SYSCTL_STATIC_CHILDREN(oid_name) (&sysctl__##oid_name.oid_children) ^ :154:1: note: expanded from here sysctl___vm_uma ^ /usr/src/sys/vm/uma_core.c:1864:15: error: assigning to 'struct sysctl_oid *' from incompatible type 'void' zone->uz_oid = SYSCTL_ADD_NODE(NULL, SYSCTL_STATIC_CHILDREN(_vm_uma), ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 errors generated. *** [uma_core.o] Error code 1 imb From owner-freebsd-current@freebsd.org Thu Nov 28 03:23:21 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6088D1C264C for ; Thu, 28 Nov 2019 03:23:21 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: from mail-qk1-f195.google.com (mail-qk1-f195.google.com [209.85.222.195]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Njdh42T1z40Jr; Thu, 28 Nov 2019 03:23:20 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: by mail-qk1-f195.google.com with SMTP id e187so21549289qkf.4; Wed, 27 Nov 2019 19:23:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EHQSCiZ9JWDWQR1fcq8jwYdFu14mnKyza+5DQ2v6W2Y=; b=jOwu0AUlGNZi3TVc0vA+ib0J2T3IBiiWL5HauKpQaC5kv6gITlrH8Ba/JICqVrr9zy gDgdyhN4aYX1OBIXHFVQIVtyWKpQLso3jD0PG5C2QVImV4Hx0c3PoQLcERty8QFjz3pH IN1gamNDbkpL+rgkebyHRxrSuCRrTkSSJ06YlPYXu8MnvQf6LdkT7ZzNMAVNY/6qr9qU BqmUbFZxqQKtK9n4vXPFmm6sZijEtMG2dBEnvfkjL1FadC5AXvKecC6+DqdUfCJ4wbdU bwL3ImLlbdQ40hyMnwhPVMesxFR/i54OR47e2xFgZDAMLGEYCzPaVRc6X3XZ+whHSLzS Uo7Q== X-Gm-Message-State: APjAAAV1sFOB4JRMf0ANR9J57Z3KDM0WCCLQ+prTvf00WitZjVP3lHkA 8dnMQQCXNqEq3+990PObnmhvbLVgLB0= X-Google-Smtp-Source: APXvYqylBwjMzYr9jy/Wx5Cit3Cu8rWDnpLVMyOncRzWFWy7X4wXnP5WLy3qbT3y8YFFOcFQzR2Ngw== X-Received: by 2002:a37:67c5:: with SMTP id b188mr8086407qkc.199.1574911398816; Wed, 27 Nov 2019 19:23:18 -0800 (PST) Received: from mail-qk1-f181.google.com (mail-qk1-f181.google.com. [209.85.222.181]) by smtp.gmail.com with ESMTPSA id e6sm7783224qkg.89.2019.11.27.19.23.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Nov 2019 19:23:18 -0800 (PST) Received: by mail-qk1-f181.google.com with SMTP id a137so19713157qkc.7; Wed, 27 Nov 2019 19:23:18 -0800 (PST) X-Received: by 2002:a37:bf82:: with SMTP id p124mr8167657qkf.337.1574911398098; Wed, 27 Nov 2019 19:23:18 -0800 (PST) MIME-Version: 1.0 References: <3e4daebb-cd5d-a9b3-daa1-d335f18e9ec8@protected-networks.net> In-Reply-To: <3e4daebb-cd5d-a9b3-daa1-d335f18e9ec8@protected-networks.net> From: Ryan Libby Date: Wed, 27 Nov 2019 19:23:06 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: SVN r355148/9 breaks build To: Michael Butler Cc: freebsd-current , jeff@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Njdh42T1z40Jr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rlibby@gmail.com designates 209.85.222.195 as permitted sender) smtp.mailfrom=rlibby@gmail.com X-Spamd-Result: default: False [-3.88 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[195.222.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.88)[ip: (-4.24), ipnet: 209.85.128.0/17(-3.16), asn: 15169(-1.95), country: US(-0.05)]; FORGED_SENDER(0.30)[rlibby@freebsd.org,rlibby@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[195.222.85.209.rep.mailspike.net : 127.0.0.17]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[rlibby@freebsd.org,rlibby@gmail.com] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 03:23:21 -0000 On Wed, Nov 27, 2019 at 6:44 PM Michael Butler wrote: > > Something missing from a header here? > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/uma_core.o > --- uma_core.o --- > /usr/src/sys/vm/uma_core.c:1864:39: error: use of undeclared identifier > 'sysctl___vm_uma' > zone->uz_oid = SYSCTL_ADD_NODE(NULL, > SYSCTL_STATIC_CHILDREN(_vm_uma), > ^ > /usr/src/sys/sys/sysctl.h:245:44: note: expanded from macro > 'SYSCTL_STATIC_CHILDREN' > #define SYSCTL_STATIC_CHILDREN(oid_name) > (&sysctl__##oid_name.oid_children) > ^ > :154:1: note: expanded from here > sysctl___vm_uma > ^ > /usr/src/sys/vm/uma_core.c:1864:15: error: assigning to 'struct > sysctl_oid *' from incompatible type 'void' > zone->uz_oid = SYSCTL_ADD_NODE(NULL, > SYSCTL_STATIC_CHILDREN(_vm_uma), > ^ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 2 errors generated. > *** [uma_core.o] Error code 1 > > imb > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Ah, SYSCTL_NODE(_vm, OID_AUTO, uma, ...) is accidentally under INVARIANTS and needs to move out. I'll patch this up in an hour if jeff or someone else doesn't beat me to it. From owner-freebsd-current@freebsd.org Thu Nov 28 04:16:51 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D8A971C396A for ; Thu, 28 Nov 2019 04:16:51 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: from mail-qt1-f195.google.com (mail-qt1-f195.google.com [209.85.160.195]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47NkqQ743cz42Pv; Thu, 28 Nov 2019 04:16:50 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: by mail-qt1-f195.google.com with SMTP id y10so27773494qto.3; Wed, 27 Nov 2019 20:16:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KABTs5Ezt1Lm63iNm70JOgks7EBX5sAKnzzuImMmZKw=; b=aHY8tTMm0qNmgvD+8w7gvG7SPYF4zPCjGHJthsfgFznDH7TN+vXhESfyoxCYdgP2Kz MCcQ46QRVrRvoNoDEzYdTSKMzzuypzkD/GQkNnApuDxAyi5nN1Bor2hjW0EZPg9SGADc LEOyEnNeW0rWA338OUbyc+ZmLZS+XVzgE4/qNk8tdYhblqPvxfyxAcaeOxTYFlww0zgo 4OC87mm3drdwybVLzU9r2xCrkIwcEq0399usGqX62lx7UM5KLJIeUIcJGw2taWA8l47M fnwdPovDJUsFfgLGPD3vHla/GSEO4Hh883XVRhJkjf/nIyd8V0O36ZcSt5pcu0OFzP0M kvzA== X-Gm-Message-State: APjAAAVOofDpUQaeCLxiXLsoW/CDTPLix8ZBdSizcU22av+zOd3St/Y3 oKm9IsSkcFYFajTxeqFwcdC+2eH0SAQ= X-Google-Smtp-Source: APXvYqy543ETQ69xt9PDYvUUMav5TV2AwHXrqWLCbah1xOXPHMJtQQ0RLFYZjSLdSQLDmpN9b96OYw== X-Received: by 2002:ac8:2598:: with SMTP id e24mr36009782qte.189.1574914609158; Wed, 27 Nov 2019 20:16:49 -0800 (PST) Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com. [209.85.222.177]) by smtp.gmail.com with ESMTPSA id i17sm8703816qtm.53.2019.11.27.20.16.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Nov 2019 20:16:49 -0800 (PST) Received: by mail-qk1-f177.google.com with SMTP id i3so21587762qkk.9; Wed, 27 Nov 2019 20:16:48 -0800 (PST) X-Received: by 2002:a37:bf82:: with SMTP id p124mr8338319qkf.337.1574914608673; Wed, 27 Nov 2019 20:16:48 -0800 (PST) MIME-Version: 1.0 References: <3e4daebb-cd5d-a9b3-daa1-d335f18e9ec8@protected-networks.net> In-Reply-To: From: Ryan Libby Date: Wed, 27 Nov 2019 20:16:37 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: SVN r355148/9 breaks build To: Michael Butler Cc: freebsd-current , jeff@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47NkqQ743cz42Pv X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rlibby@gmail.com designates 209.85.160.195 as permitted sender) smtp.mailfrom=rlibby@gmail.com X-Spamd-Result: default: False [-3.82 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[195.160.85.209.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_GOOD(0.00)[195.160.85.209.rep.mailspike.net : 127.0.0.18]; IP_SCORE(-1.82)[ip: (-3.95), ipnet: 209.85.128.0/17(-3.16), asn: 15169(-1.95), country: US(-0.05)]; FORGED_SENDER(0.30)[rlibby@freebsd.org,rlibby@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[rlibby@freebsd.org,rlibby@gmail.com] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 04:16:51 -0000 On Wed, Nov 27, 2019 at 7:23 PM Ryan Libby wrote: > > On Wed, Nov 27, 2019 at 6:44 PM Michael Butler > wrote: > > > > Something missing from a header here? > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/uma_core.o > > --- uma_core.o --- > > /usr/src/sys/vm/uma_core.c:1864:39: error: use of undeclared identifier > > 'sysctl___vm_uma' > > zone->uz_oid = SYSCTL_ADD_NODE(NULL, > > SYSCTL_STATIC_CHILDREN(_vm_uma), > > ^ > > /usr/src/sys/sys/sysctl.h:245:44: note: expanded from macro > > 'SYSCTL_STATIC_CHILDREN' > > #define SYSCTL_STATIC_CHILDREN(oid_name) > > (&sysctl__##oid_name.oid_children) > > ^ > > :154:1: note: expanded from here > > sysctl___vm_uma > > ^ > > /usr/src/sys/vm/uma_core.c:1864:15: error: assigning to 'struct > > sysctl_oid *' from incompatible type 'void' > > zone->uz_oid = SYSCTL_ADD_NODE(NULL, > > SYSCTL_STATIC_CHILDREN(_vm_uma), > > ^ > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > 2 errors generated. > > *** [uma_core.o] Error code 1 > > > > imb > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Ah, SYSCTL_NODE(_vm, OID_AUTO, uma, ...) is accidentally under > INVARIANTS and needs to move out. > > I'll patch this up in an hour if jeff or someone else doesn't beat me to it. Should be fixed in r355166. Thanks for the report. From owner-freebsd-current@freebsd.org Thu Nov 28 09:43:26 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B791C1CAEF0; Thu, 28 Nov 2019 09:43:26 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Nt4F60KBz4Kwc; Thu, 28 Nov 2019 09:43:25 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wm1-x32f.google.com with SMTP id z19so10960669wmk.3; Thu, 28 Nov 2019 01:43:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xI7O7tW7yg5xJPC3tIY4r5a3pCvrxjHlIYP1qOysTvg=; b=EOr2NuXdoRC9qjsObYGDPRK6FkJDgm5nanIF+QXIc2FK78PNp/W3YKuRq9Xq7AAJba dBCHdSs8+8s6OxNu9wk0BzAg/RKYXTWuTl8dj9DPKoAspr1RkwItAXDyhT0rR7MSchf+ 0xeJFDMjmIeZLLN0v8yqn+b47WLw/R8lKyrAP0IzCgwBnx/QGFsEHG7lptiFPZKKlo4Y HVySWZyyG4l/8F9+K+fHQ/6j29jx7tyLdGT0XbhsRljvLNYcDLJmkQ/NWM5E2XHLeRa2 ezV+KtxV8mIuuq1zv078Ur7nrZkISqMqr5KYWGTVs7Wus8bcTwFvCAAkpPUnCK26Bl/a to7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xI7O7tW7yg5xJPC3tIY4r5a3pCvrxjHlIYP1qOysTvg=; b=AG3jOvXtHoGRYa+/dWrBcuTupKjEMEfXq3jxG92yWvpdKI9SUueQNb6Q4M0EqMdlnF dO+5Vvsy8c5tRFnZRMAUm6C09WkwPcgr4nbFwgr8YwUHFdfOlT4lKYy/DS0L0cJfcDXG g7p64W4lkzyDDjO7xZGd2iEsFMyie8w7uxzX3AtKwr5wTo73GEMF7nIK6dB4owGvg8VX 1Ta8g3hNR69kj+Y4/aaNwGOp+1L/aPuBfPQb/nBNebamgDUJLdg/k5+HWpVufKgvdYih 1wO6WtKHMXVZUdbB1xq6VZt+jive8G5t4ShdkZWQXoeDuqudwKHWXr6rzkQO+DJI5RDy Kztw== X-Gm-Message-State: APjAAAUh7CbL9cPFc/Gzp3HBJakeuL6hO0+umVtPc2QKI0jnybntU1xf 5JeH/AzbkGqoqJXPNBe/+aN+/R9gY4ovsZsE3Wuzr8ZGr5M= X-Google-Smtp-Source: APXvYqwM5cT2ZLi3FAgdSC8KZS7CLmKc4f8vqqoEt3cqLZHeQpmAjbtjqmT9sQTslMciLLsc1thUcJFGd0MCBvYKyRk= X-Received: by 2002:a1c:2c43:: with SMTP id s64mr5239576wms.135.1574934203877; Thu, 28 Nov 2019 01:43:23 -0800 (PST) MIME-Version: 1.0 From: Andrey Fesenko Date: Thu, 28 Nov 2019 12:43:09 +0300 Message-ID: Subject: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Nt4F60KBz4Kwc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=EOr2NuXd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::32f as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; IP_SCORE(0.00)[ip: (-8.90), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[f.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 09:43:26 -0000 Hello, Around starting 20191114 r354699 (memstick tested), my desktop not boot normally. Boot only loader menu (black and white mode) after start i'm see load modules, after this monitor gray, and 15-20s disabled, system block not disable but run silently. system not boot. If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 release, system boot normally My notebook x220 work fine any loaders. desktop BIOS Information Vendor: American Megatrends Inc. Version: F2 Release Date: 05/03/2013 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 4.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z87MX-D3H Version: To be filled by O.E.M. Serial Number: To be filled by O.E.M. UUID: 03de0294-0480-057d-0c06-7a0700080009 Wake-up Type: Power Switch SKU Number: To be filled by O.E.M. Family: To be filled by O.E.M. From owner-freebsd-current@freebsd.org Thu Nov 28 12:01:39 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B61BC1CF2D0 for ; Thu, 28 Nov 2019 12:01:39 +0000 (UTC) (envelope-from akgloria@portugalmail.pt) Received: from a.smtp.portugalmail.pt (dellbld07.srv.portugalmail.net [195.170.168.71]) by mx1.freebsd.org (Postfix) with ESMTP id 47Nx7l2CyNz4Tsm for ; Thu, 28 Nov 2019 12:01:38 +0000 (UTC) (envelope-from akgloria@portugalmail.pt) X-Virus-Scanned: Sooma amavisd filtered X-Spam-Flag: NO X-Spam-Score: -0.998 X-Spam-Level: X-Spam-Status: No, score=-0.998 tagged_above=-99 required=5 tests=[ALL_TRUSTED=-1, FREEMAIL_FROM=0.001, TVD_SPACE_RATIO=0.001] autolearn=unavailable autolearn_force=no Received: from [192.168.1.54] (bl12-160-76.dsl.telepac.pt [85.245.160.76]) (Authenticated sender: akgloria@portugalmail.pt) by a.smtp.portugalmail.pt (Postfix) with ESMTPA id 1BE19147554 for ; Thu, 28 Nov 2019 12:01:38 +0000 (WET) To: freebsd-current@freebsd.org From: =?UTF-8?B?QW5kcsOpIEdsw7NyaWE=?= Subject: unsub Message-ID: Date: Thu, 28 Nov 2019 12:01:40 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 47Nx7l2CyNz4Tsm X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of akgloria@portugalmail.pt designates 195.170.168.71 as permitted sender) smtp.mailfrom=akgloria@portugalmail.pt X-Spamd-Result: default: False [1.33 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.170.168.0/24:c]; FREEMAIL_FROM(0.00)[portugalmail.pt]; HFILTER_HELO_IP_A(1.00)[a.smtp.portugalmail.pt]; HFILTER_HELO_NORES_A_OR_MX(0.30)[a.smtp.portugalmail.pt]; TO_DN_NONE(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[76.160.245.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[portugalmail.pt]; ASN(0.00)[asn:2860, ipnet:195.170.168.0/24, country:PT]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.15)[-0.150,0]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[portugalmail.pt]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(0.00)[ipnet: 195.170.168.0/24(3.17), asn: 2860(0.21), country: PT(0.05)]; NEURAL_SPAM_LONG(0.38)[0.377,0]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 12:01:39 -0000 From owner-freebsd-current@freebsd.org Thu Nov 28 12:03:27 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 972D71CF60D for ; Thu, 28 Nov 2019 12:03:27 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10011301.me.com (pv50p00im-ztdg10011301.me.com [17.58.6.40]) (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 47Nx9p5pfnz4V5q for ; Thu, 28 Nov 2019 12:03:26 +0000 (UTC) (envelope-from tsoome@me.com) Received: from [192.168.150.41] (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10011301.me.com (Postfix) with ESMTPSA id 50804640FA3; Thu, 28 Nov 2019 12:03:23 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H From: Toomas Soome In-Reply-To: Date: Thu, 28 Nov 2019 14:03:21 +0200 Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Andrey Fesenko X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-28_01:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=763 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911280106 X-Rspamd-Queue-Id: 47Nx9p5pfnz4V5q X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[40.6.58.17.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-4.16), ipnet: 17.58.0.0/20(-2.16), asn: 714(-2.33), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 12:03:27 -0000 hi! I did try to reach you, but mail did bounce back=E2=80=A6 unicast ping me:) rgds, toomas > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: >=20 > Hello, >=20 > Around starting 20191114 r354699 (memstick tested), my desktop not > boot normally. Boot only loader menu (black and white mode) after > start i'm see load modules, after this monitor gray, and 15-20s > disabled, system block not disable but run silently. system not boot. >=20 > If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > release, system boot normally >=20 > My notebook x220 work fine any loaders. >=20 > desktop > BIOS Information > Vendor: American Megatrends Inc. > Version: F2 > Release Date: 05/03/2013 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 16 MB > Characteristics: > PCI is supported > BIOS is upgradeable > BIOS shadowing is allowed > Boot from CD is supported > Selectable boot is supported > BIOS ROM is socketed > EDD is supported > 5.25"/1.2 MB floppy services are supported (int 13h) > 3.5"/720 kB floppy services are supported (int 13h) > 3.5"/2.88 MB floppy services are supported (int 13h) > Print screen service is supported (int 5h) > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > ACPI is supported > USB legacy is supported > BIOS boot specification is supported > Targeted content distribution is supported > UEFI is supported > BIOS Revision: 4.6 >=20 > Handle 0x0001, DMI type 1, 27 bytes > System Information > Manufacturer: Gigabyte Technology Co., Ltd. > Product Name: Z87MX-D3H > Version: To be filled by O.E.M. > Serial Number: To be filled by O.E.M. > UUID: 03de0294-0480-057d-0c06-7a0700080009 > Wake-up Type: Power Switch > SKU Number: To be filled by O.E.M. > Family: To be filled by O.E.M. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Nov 28 13:08:21 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 104EF1A8F78 for ; Thu, 28 Nov 2019 13:08:21 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Nycg6887z4YHH for ; Thu, 28 Nov 2019 13:08:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1574946491; bh=nniMw+ziwcbxxeOauf6RQ6ET6A1CFL4j34AYuZcDGzI=; h=X-UI-Sender-Class:Date:From:To:Subject; b=FEmDA8+0CcfnnGjFHAxIwKpHYeLu5gaP6Td/B37wW+Kgy6vsLEmkbCtaHpW/kfM/E YkOAEmIhLCuv2ARA4VQlFPrO+CcMRl/1hTJF1xy+tcAzu71tvtEMG2sdEGtn0JNT1C AU3t1avJgPLsCRbe97neukJnGEkbqZlwYGpUH+hM= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from thor.intern.walstatt.dynvpn.de ([78.54.42.166]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N7iCg-1hnD3736OY-014jw7 for ; Thu, 28 Nov 2019 13:43:59 +0100 Date: Thu, 28 Nov 2019 13:43:23 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: WifI support missing: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter Message-ID: <20191128134350.6cd493ce@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:COe1hf2OwbOVNE6Xfae0Zdm3hPeMb8ERxakCU4DuXhx5Avztknp 6fA7y6GPGhEZtYV5iQrnJpaMuoltfFwOObk+8oOsdKdlyemxPwNqagH78cWE3yiEagPJR4N 4BIt02OjlCfaC3SnzdGv6K04zptija3vGXe7aX4ZZhMN+5Sy4U4ew6Q76BlkTN8Y4cxj8/u Ocu7Fn9dWtz/ziPodG/Jg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:A5GonvVFRC8=:AEtMX9jzXqQm+paSPnndPz H6oFd9++oYGxwdqQBN4SD0Wbk3Y0vVEV6X1q2YrslRMWhD72hl3JZlWubT038zZ7J/oU9jwLa jC5gLQbotVxjcg5EWKHUR70GuGr9JgyEVG4gyBycvAZrsVzmPs7Mcu89i4wjhYOsgVoPaA0Cn 3/yy1RYyXfovAq2hCekXnR1P80Rty49a39dnEjGR1O30puEmyEME/a4euGYxcvgKtgnsxzgQw xGUrhCia/B4yGh/Xj+PZzrGLyXA2vff7l9ABmLTyPaBpkIRiXd76qLSwsdQCG+1PSNI9mPDtG q/pOV8dOH88IL+UqE0WC9+GJYw3mtCsa/1H1oA+IGpBwIQ/E11R8zXxfWgtmZu0eqkZXV8/zx 9Lh6s6VAgw1rkK5Tk4CMvu5RefzL0h+FEZPoVGQlKUdXnXZUEaqJEuWCHCIFWP2j8+zleHvTS zNHKBk/RRX3rgTS+PkGn19FufEdT/FuUYKGLZPWCOwptMOgjouEUEzcn5llRD5JMtkxgcU+i3 7RDB7NyEynqL+KGlNsQvK76FTE757k9MLjEedCUdHPySPS9aw1vtv0UseVpVlrYSk+I95bfbu hB/9CAdPqHGLjwv22gQnZO54BAML/d9tdLAW/XPYHihspA58CyGm3JYeWxtBFLOx1pafuN57/ GNItZmdxp2nBgh3VI49H1eLmpEW/fOX526PhmuwjvjB8vL5wT4Fcnp6MKIoJh5YX8GqSnFGzv iP/+uw9qNKnT0AHbxA0aafvtaQoss9gJUY5AMUYDTmn0PkmSR81qeqRit/I0VTquRD4it03E2 I3R7qbdhs2Mk2gKmZwu1KAqcc79kWXMEElUU/LoEezOIrnUKH5AwxM2e2x3bhgiYyb/4+oCIu ZSC2Jk0CzPJogUTPoKRtXcRj0RcqwY9D6nbQiSzVxRZwHuMpDcmePK8PFOgiEnAlNPn6M2XvT alo8pUXz+X6nP7itU7u/esLMJCrv+O3UjEBiLTkULWz80gMkKhP+riW186LXCx4z11OzoIrRC Z8ezJwKlkryjMdD9RLFCV0WmIUgt4+nUbMEbVwTbrOIcZtKPZPeo9WjsVSLf5C+EIyzU+jK9k kNEUU2pmNk0ud8W7gY7KwcCEqzfEwTzXbjJKkmgoD7gApCrEjX6oFfwgA/UBCopPG2E4fgL+2 GatLGZ4jOdhHpqBhkmlZ3eQNiC621dQ00JvikA8m/yHZsa5g4IVUmtPx1vH1DxB91d7HmpCX0 K6KWWDc7zY921ibwqWK8ikrKre71TM8lxzikqla+a926e3cvwm0yNTwyau2E= X-Rspamd-Queue-Id: 47Nycg6887z4YHH X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.net header.s=badeba3b8450 header.b=FEmDA8+0; dmarc=none; spf=none (mx1.freebsd.org: domain of ohartmann@walstatt.org has no SPF policy when checking 212.227.17.21) smtp.mailfrom=ohartmann@walstatt.org X-Spamd-Result: default: False [-3.51 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmx.net:s=badeba3b8450]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt.org]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; IP_SCORE(-1.21)[ip: (-7.10), ipnet: 212.227.0.0/16(-1.24), asn: 8560(2.29), country: DE(-0.01)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmx.net:+]; MIME_BASE64_TEXT(0.10)[]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[21.17.227.212.list.dnswl.org : 127.0.3.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[166.42.54.78.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 13:08:21 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMjU2DQoNCkhlbGxv LA0KDQpmb3Igb3ZlciB0d28geWVhcnMgd2UgaGF2ZSBhIHNtYWxsIHJvdXRlciBwcm9qZWN0IGJh c2VkIG9uIEZyZWVCU0QuIFRoZSBoYXJkd2FyZSBpcyBlcXVpcHRlZA0Kd2l0aCBhIFdpRmkgbVBD SWUgY2FyZCBhbmQgcmVwb3J0cyBpdHNlbGYgdG8gMTItU1RBQkxFLzEzLUNVUlJFTlQgYXM6DQoN ClsuLi5dDQpub25lMkBwY2kwOjE6MDowOiAgICAgICBjbGFzcz0weDAyODAwMCBjYXJkPTB4MDAw MDAwMDAgY2hpcD0weDAwM2MxNjhjIHJldj0weDAwIGhkcj0weDAwDQogICAgdmVuZG9yICAgICA9 ICdRdWFsY29tbSBBdGhlcm9zJw0KICAgIGRldmljZSAgICAgPSAnUUNBOTg2eC85ODh4IDgwMi4x MWFjIFdpcmVsZXNzIE5ldHdvcmsgQWRhcHRlcicNCiAgICBjbGFzcyAgICAgID0gbmV0d29yaw0K ICAgIGJhciAgIFsxMF0gPSB0eXBlIE1lbW9yeSwgcmFuZ2UgNjQsIGJhc2UgMHhmNzYwMDAwMCwg c2l6ZSAyMDk3MTUyLCBlbmFibGVkDQpbLi4uXQ0KDQpUaGUgYXRoLWRyaXZlciBmb3VuZCBpbiBy ZWNlbnQgMTItU1RBQkxFLzEzLUNVUlJFTlQgZG8gbm90IHN1cHBvcnQgdGhpcyBjaGlwIGFsdGhv dWdoIGl0IHNlZW1zDQp2ZXJ5IGNvbW1vbiBhbmQgd2VsbCBzdXBwb3J0ZWQgYnkgc2V2ZXJhbCBM aW51eCBkaXN0cmlidXRpb25zIGluY2x1ZGluZyB0aGUgT3BlbldSVCByb3V0ZXINCnByb2plY3Qg KEkgdGhpbmsgdGhhdCBpcyB0aGUgYXRoMTBrIGRyaXZlciBzdWl0ZSBhcyBmYXIgYXMgSSByZWNh bGwpLg0KDQpUaGFua3MgaW4gYWRhdm5jZSwNCg0Kb2gNCg0KLSAtLSANCk8uIEhhcnRtYW5uDQoN CkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJlcm1pdHRsdW5nIG1laW5lciBE YXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1hcmt0LSBvZGVyIE1laW51bmdz Zm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUt LS0tLQ0KDQppSFVFQVJZSUFCMFdJUVN5OElCeEFQRGtxVkJhVEo0NE4xWlpQYmE1UndVQ1hkL0JC Z0FLQ1JBNE4xWlpQYmE1DQpSN051QVFDdCs0eFh5TEh6UW5WMStuRXdaUU9FOXhHRzhBVkx4S1l6 bGJhYXN4ZjNDZ0QrTjNNeER2cXhQVXAzDQpDdy9vc0tNcTNWVXkyU3RtZFhPTDI2UFIrVTR2SEFF PQ0KPVZkMk8NCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-current@freebsd.org Thu Nov 28 18:20:36 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5F3831B1F0B; Thu, 28 Nov 2019 18:20:36 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47P5Xz0ByPz3P5s; Thu, 28 Nov 2019 18:20:34 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wm1-x341.google.com with SMTP id a131so7525512wme.5; Thu, 28 Nov 2019 10:20:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+vwxV5TZzszkuN1ruxhUQAKmp7LOFGivhbvieE8ymes=; b=C2PS1Q+xkEwrwOECzp9KIpT2a7/rhMbY4Q+2xCUyUqOfq+WcRPxJF2FTES6IlUUYMq fkfgq4gl2xvbPchXYVUqfjcKYEeegys3iHzGVrvMFcfUbnwbHDm/k2Vx+sdTDdRfzTSs I3rhEToqAp3WqkL+9y5+T4yAOnAe2xL9lkIYRCPXBI4nQayGicpY3Mky3cNbDTQDIuBT PgQn5OlySGB55uqrYaJ++qhrx2v3ZX3Y3ov+nzPcwZc9npCHmL+MhrrBfvckNMIVP72O WqqwuSxUh0ZCjC9ZgdYX7e4NPiPWpdZPplwIYu9w/KwcyK9hpch5Dqvnb69l4igyaN1X KuLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+vwxV5TZzszkuN1ruxhUQAKmp7LOFGivhbvieE8ymes=; b=gMImXnFM2j42QWHLLwpInoSIWQEXi5vUpkHFuTUJT7ScIOFvKu2rP7d9wu+O4eTjaJ F/7+RZenLR59lUJw3keN9kzZwddfxGzbc3h8yyuMTn8LbHfqbZyokrdI6rGRkQHs5Qqs eLlEuNWJAmEpyRW4ykbVk2bV5wN2WlhBCr9raJjzR892NpE1IrxE37tWMWFuf29q33P3 TkYD0+vS2p+eOCBWu5mUuNS6Nmn5cAgWENCjPow08lO7wS6IO2YJNVuTnI+IKbEJRTV4 lOn0NGJ0n2oZAZwKRudxp93kMexVkvWHBtFgywqXGpTYqHZyeghOpXS/WlH3rjg3HNqb UKyg== X-Gm-Message-State: APjAAAXLwqo2RqBiKdufgLdkaWSr4n7fQSgPOxIKCpBH3HNN1T20TjIl BMlgoCDrQQC7x7YwxjeVhGLljY54HMIpbBpe9Mc5xI5J3O4= X-Google-Smtp-Source: APXvYqxrglBfhTNRoq6i1ZSnFv75dGLIwFvvjDLtzt8vXBuge9UPdq9sNsS9D0VtSmucsPHHQrpUDv2FiAa/8E7jL44= X-Received: by 2002:a1c:f415:: with SMTP id z21mr10919292wma.140.1574965233481; Thu, 28 Nov 2019 10:20:33 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Andrey Fesenko Date: Thu, 28 Nov 2019 21:20:22 +0300 Message-ID: Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: Eugene Grosbein Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47P5Xz0ByPz3P5s X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=C2PS1Q+x; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::341 as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (2.86), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[1.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 18:20:36 -0000 On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > boot normally. Boot only loader menu (black and white mode) after > > start i'm see load modules, after this monitor gray, and 15-20s > > disabled, system block not disable but run silently. system not boot. > > So loader works. Try breaking to loader prompt and do: > > set hw.vga.acpi_ignore_no_vga=1 > boot > Hm.... new test, new problems. Old and new efi, if breaking to loader prompt work only alphabet keys, nums not work :) (on notebook loader work fine) If make echo 'hw.vga.acpi_ignore_no_vga=1' > /boot/loader.conf on flash, and reboot, not fix boot. From owner-freebsd-current@freebsd.org Thu Nov 28 20:17:13 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4C3181B5FFE; Thu, 28 Nov 2019 20:17:13 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com [IPv6:2a00:1450:4864:20::342]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47P87W6bqPz42G8; Thu, 28 Nov 2019 20:17:10 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wm1-x342.google.com with SMTP id p17so6938732wma.1; Thu, 28 Nov 2019 12:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=18W98a8dfQ6ztFrfx5TxmFHXzLjV4AeiR2oUuc+n9Tw=; b=qDxFiWsd9W9qVEp/L6wswZyBEkPWbr6qek+xZEV2rfSAEdjZF1yUyEpWnjg19GyEEN nRMJd95LifZlWVQWvLk/JQYeGubThIQ402diD82RrnCchNok6jdcFT1F924cTI/gyYid XQOd497nFmTLiu0L2bVnyts31eJ58WFhVdngUDDJdRMAaWn+Q0je1/SQvdI86k+oSqny eKvhxb5j/mWZgrAkJnLm8j4Zdi83OhzPXAjK0TH+jmaUaIwEzm+TEX8w1bHeeKTNDSVb HOyTdsQIVMhgaDtlCm8JwYkwSrczcPDQarqnFBNS32VW2S5IG0IUlHDHbnnshQvIEg+W /a/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=18W98a8dfQ6ztFrfx5TxmFHXzLjV4AeiR2oUuc+n9Tw=; b=aP9RwcuyzK0+nXpdKmQbSMPCve34m2lCygPom96eGZ/QZq6kFld2a3Q6qJzCLnmyB1 g74hNGXkv1orBRV42Ea13nN4lplZbNe4Za4+2tvexC53+jY5+DMZtKA+0ZVLPKVMRJPl ZVe7+sGz6O/+DjR0UyXR7OXd9AznarQTD0cFacEsZ6arMM2+ViRDq58NeaMMKxdf0KnM 1D4OFU4xk1W9NqYWIHGoUw3Si5ej/xsrAGjn5JxQ+4I3Q02GXHbNFpKQp0rGcwfQ9K9M +j1CzTccXplHZNz8oNco4FQa8B6+jRk/n444WUBiYVP52+M/3NIMUJs2o+F14hYMXLjz Mrhw== X-Gm-Message-State: APjAAAXToxflz77Z1dEM/cIfL9faWNl9Qs8v0y3YDTykKEd42j4wO1Pp ptnQgDka4X/nfY9evRg4yid8h9++HnnfRLptvS3YYlqR0p4= X-Google-Smtp-Source: APXvYqyPtTzq6zeR9xsP72HIRTTX18fvVeB6qIzzpK7qO+4/NVh9TKBASnWFZDc35PdZKk5GSn3kvVN+WR6ZBaaR8AA= X-Received: by 2002:a1c:2c43:: with SMTP id s64mr7746286wms.135.1574972227378; Thu, 28 Nov 2019 12:17:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Andrey Fesenko Date: Thu, 28 Nov 2019 23:16:56 +0300 Message-ID: Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: Toomas Soome Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47P87W6bqPz42G8 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qDxFiWsd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::342 as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-1.99 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(0.00)[+ip6:2a00:1450:4000::/36:c]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.64), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(0.00)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; URIBL_PBL(0.01)[bsdnir.info]; RCVD_IN_DNSWL_NONE(0.00)[2.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:17:13 -0000 On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > hi! > > I did try to reach you, but mail did bounce back=E2=80=A6 > > unicast ping me:) > > rgds, > toomas > > > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > boot normally. Boot only loader menu (black and white mode) after > > start i'm see load modules, after this monitor gray, and 15-20s > > disabled, system block not disable but run silently. system not boot. > > > > If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > > release, system boot normally > > > This video boot second version (Name: "loader.efi") 545 KB https://bsdnir.info/files/efi_fail.mp4 From owner-freebsd-current@freebsd.org Thu Nov 28 20:18:47 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E06A1B633F for ; Thu, 28 Nov 2019 20:18:47 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-hyfv10011601.me.com (pv50p00im-hyfv10011601.me.com [17.58.6.43]) (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 47P89L5H78z42h7 for ; Thu, 28 Nov 2019 20:18:46 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-hyfv10011601.me.com (Postfix) with ESMTPSA id 24CED380E80; Thu, 28 Nov 2019 20:18:43 +0000 (UTC) From: Toomas Soome Message-Id: <49B58A7F-0DE2-4BEB-8A8C-D996962FDDE1@me.com> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H Date: Thu, 28 Nov 2019 22:18:41 +0200 In-Reply-To: Cc: freebsd-current , freebsd-hackers@freebsd.org To: Andrey Fesenko References: X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-28_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=608 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911280176 X-Rspamd-Queue-Id: 47P89L5H78z42h7 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.59 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; R_SPF_ALLOW(0.00)[+ip4:17.58.0.0/16]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(0.00)[me.com,quarantine]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[43.6.58.17.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(0.00)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(0.00)[ip: (-3.91), ipnet: 17.58.0.0/20(-2.16), asn: 714(-2.33), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; URIBL_PBL(0.01)[bsdnir.info]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:18:47 -0000 > On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: >=20 > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome > wrote: >>=20 >> hi! >>=20 >> I did try to reach you, but mail did bounce back=E2=80=A6 >>=20 >> unicast ping me:) >>=20 >> rgds, >> toomas >>=20 >>> On 28. Nov 2019, at 11:43, Andrey Fesenko = wrote: >>>=20 >>> Hello, >>>=20 >>> Around starting 20191114 r354699 (memstick tested), my desktop not >>> boot normally. Boot only loader menu (black and white mode) after >>> start i'm see load modules, after this monitor gray, and 15-20s >>> disabled, system block not disable but run silently. system not = boot. >>>=20 >>> If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 >>> release, system boot normally >>>=20 >>=20 >=20 > This video boot second version (Name: "loader.efi") 545 KB > https://bsdnir.info/files/efi_fail.mp4 = 403 Forbidden :=3D) rgds, toomas= From owner-freebsd-current@freebsd.org Thu Nov 28 20:19:05 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6CE1C1B6391; Thu, 28 Nov 2019 20:19:05 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47P89g6kMhz42mN; Thu, 28 Nov 2019 20:19:03 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wr1-x441.google.com with SMTP id c14so7908678wrn.7; Thu, 28 Nov 2019 12:19:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3WEPQvh+urOXzuhx7smg8ad5bbFkaiT4T9Azlh/witM=; b=qRd3BmloExBKkFN8vPPrwyD8zcaKXaBlU4csD0QnXoqKmD77qaINDEXXksHgTS1OVk /zFCRWG5jU185vScMjW1Ewt4BU17XnCidUIHbJRESmsgwCkMFSyortf2/m38HHJv6Qio lQNA3qjTKuagF38Onovs48Lf/JXgxsCGCSUihueb4xWdSBHzdIb2J7cVndBZ1Mk7rSkD 00UyFc2Dclt1wXtpODMr73BFb7+SmxC4Nn4q1mqD4yp67CIY9+CXJEpYv+B2CvIgeqPi 4zbQT4rrhBwZWaNT/OY9/qqRGUl/Mp501nWyeLdNFos84ksK/7WsKS00m09nDupj3fH8 OS3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3WEPQvh+urOXzuhx7smg8ad5bbFkaiT4T9Azlh/witM=; b=rmkjT1irKTlG4wB+bUXFXU/wLkn+2jJLKBBnSLAK+tHHthlY/EmkVO3974e8g8wY5Y rYQDqoCQR52n218bJbg7tWceoV/NDAlb0vFEKmYsd3qXJVNdc7kwaqzHlCO3lRd9iC5F dJRXuxvWltSA0s8RgFqVVVBSJy9DPmy/iezSgglJ7LeNMnDxPnzEAusiQg0YXRxrEIDZ 71qXdOuxParq4pg4eTKvHHc7PRHny+7bGhPHWg0zEhWrlXgG2TRXF7sTU8VR85aR1sj6 1zv2WUqxTMyBTpvezDWVPk9uzzacbkTwU3HGh0fmgBIajeiMS/Psqa8wIRFpXkNbeGSA ySAQ== X-Gm-Message-State: APjAAAX6i8z/xfXnN1puRJAA0dYY4B4fHXXLUkRh6vmHa6V0V59v/TmM LIYHx8wJMewnjIFu/IsPDHEUFDe+ygM5o8mZp5qiT/UlAY8= X-Google-Smtp-Source: APXvYqxqZ89/5tXASBofsq2fptWl+iIY9KVr/qCJf8xUGXsyL22k15hL+Y3dEyXKuMHJ8t/6PNf5FGJlnkuBoXBjO9I= X-Received: by 2002:adf:ff84:: with SMTP id j4mr9355766wrr.27.1574972337491; Thu, 28 Nov 2019 12:18:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Andrey Fesenko Date: Thu, 28 Nov 2019 23:18:46 +0300 Message-ID: Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: Eugene Grosbein Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47P89g6kMhz42mN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qRd3Bmlo; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::441 as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (2.53), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[1.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:19:05 -0000 On Thu, Nov 28, 2019 at 9:20 PM Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > > > Hello, > > > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > > boot normally. Boot only loader menu (black and white mode) after > > > start i'm see load modules, after this monitor gray, and 15-20s > > > disabled, system block not disable but run silently. system not boot. > > > > So loader works. Try breaking to loader prompt and do: > > > > set hw.vga.acpi_ignore_no_vga=1 > > boot > > > > Hm.... new test, new problems. Old and new efi, if breaking to loader > prompt work only alphabet keys, nums not work :) (on notebook loader > work fine) > If make > echo 'hw.vga.acpi_ignore_no_vga=1' > /boot/loader.conf > > on flash, and reboot, not fix boot. Correction number and underline work, but set hw.vga.acpi_ignore_no_vga not fix boot From owner-freebsd-current@freebsd.org Thu Nov 28 20:20:30 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 96BEE1B673F; Thu, 28 Nov 2019 20:20:30 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47P8CK6Q51z436r; Thu, 28 Nov 2019 20:20:29 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wr1-x441.google.com with SMTP id w15so1565578wru.4; Thu, 28 Nov 2019 12:20:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=D51YHK1w32jujqOU/ZtQn6G9ZBYhpHhxYNjlVP4L8yc=; b=V1ifRpj5Pr16dqjTd4IVIobwzcPvfIX7huwoE9p1k/F8q+HyF71UurGpow23E6BMzW cDMxcDATfckAGRSFAbwtAcSRqREhZ8kYdpuY5nz1rvoOj6nlKlTajR4JxeW2eYdgShwZ f/ajq5+QIWDOpBhgd7esIhaYsIROGkAsjdwrTi/dYYSvTE+OqtYrNqCoR9m7OKsW7gPh 5BElPpMumarvcAU4wucFSsUQ2NhBtx7GCGYw5dq2ATll52GWMzQH63P3B83vbm3MS7P/ 6GH2XbS877x9vaxlMZOhjogpy97C1CN+r3NEhto0aT5TiyYbLeT1N+c0k+4IdrjsYKPf GXYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=D51YHK1w32jujqOU/ZtQn6G9ZBYhpHhxYNjlVP4L8yc=; b=TL3ZRtDpu6TsYg1mjFteFOpde3gUgQinDzQ3Eh/FMBxfwDBwFa7cLOx01zLyw86ILA IikOnm6YJSSkkXiEKQ3AK0SP8Lplkszrec85wbw/NaKD5AKDxKfLzpykq7nKtKpL2GVG piGZpPXn4WdjLpJiQIGEjzJ9h3IOgpziEqaId8ws+47s1/lmEe7v/fuMTWehtY9wQoOf L9DxUuH8+Qb5djM9tmpmBHKFDPxShSBX/yawEoc+mgGBAHrTeKDqHoKHLKbp1WlqXOzV 3DAITr4IfRUmkMGegWTvgCD4Mve4pcx9ugnD4Vmi6WZoZ3ZHvMX42C0pfML4FviEjaul AaWg== X-Gm-Message-State: APjAAAWB6q/3/DEa1lbn8TOjSLgj3GWKZhh5mlqOotbsAkW6odmqqL8o tB7MNAkNhccglO3lsO86MM0xHXqpegT/fsdjv7ZT4Oht X-Google-Smtp-Source: APXvYqwxvjEuZn+VLxeMmW/K53OyPIqYbiTE0w1VKJ0fRzqIzHmfKnyfeJTRrQ4jwkpZvpjr+/6dovJxmvDmZqjXs2c= X-Received: by 2002:adf:de86:: with SMTP id w6mr29486131wrl.115.1574972428256; Thu, 28 Nov 2019 12:20:28 -0800 (PST) MIME-Version: 1.0 References: <49B58A7F-0DE2-4BEB-8A8C-D996962FDDE1@me.com> In-Reply-To: <49B58A7F-0DE2-4BEB-8A8C-D996962FDDE1@me.com> From: Andrey Fesenko Date: Thu, 28 Nov 2019 23:20:17 +0300 Message-ID: Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: Toomas Soome Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47P8CK6Q51z436r X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=V1ifRpj5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::441 as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-1.99 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.53), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(0.00)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; URIBL_PBL(0.01)[bsdnir.info]; RCVD_IN_DNSWL_NONE(0.00)[1.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:20:30 -0000 Fixed On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > > > > On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > > hi! > > I did try to reach you, but mail did bounce back=E2=80=A6 > > unicast ping me:) > > rgds, > toomas > > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > Hello, > > Around starting 20191114 r354699 (memstick tested), my desktop not > boot normally. Boot only loader menu (black and white mode) after > start i'm see load modules, after this monitor gray, and 15-20s > disabled, system block not disable but run silently. system not boot. > > If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > release, system boot normally > > > > This video boot second version (Name: "loader.efi") 545 KB > https://bsdnir.info/files/efi_fail.mp4 > > > 403 Forbidden > > :=3D) > > rgds, > toomas From owner-freebsd-current@freebsd.org Thu Nov 28 20:31:36 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 58F521B6FA6 for ; Thu, 28 Nov 2019 20:31:36 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-hyfv10011601.me.com (pv50p00im-hyfv10011601.me.com [17.58.6.43]) (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 47P8S74p3yz43tZ for ; Thu, 28 Nov 2019 20:31:35 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-hyfv10011601.me.com (Postfix) with ESMTPSA id 4ECB7380EDD; Thu, 28 Nov 2019 20:31:33 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H From: Toomas Soome In-Reply-To: Date: Thu, 28 Nov 2019 22:31:30 +0200 Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8C721EA7-09EA-4154-AC29-273B3A881FA4@me.com> References: <49B58A7F-0DE2-4BEB-8A8C-D996962FDDE1@me.com> To: Andrey Fesenko X-Mailer: Apple Mail (2.3601.0.10) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-28_07:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=601 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911280178 X-Rspamd-Queue-Id: 47P8S74p3yz43tZ X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.59 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; R_SPF_ALLOW(0.00)[+ip4:17.58.0.0/16:c]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(0.00)[me.com,quarantine]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[43.6.58.17.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(0.00)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (-4.17), ipnet: 17.58.0.0/20(-2.16), asn: 714(-2.33), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; URIBL_PBL(0.01)[bsdnir.info]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:31:36 -0000 > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: >=20 > Fixed >=20 Thanks. And yea, that one is nasty. I have some guess but nothing too = solid=E2=80=A6 it may take time to get figured out. Have you tested BIOS boot? rgds, toomas > On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: >>=20 >>=20 >>=20 >> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: >>=20 >> On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: >>=20 >>=20 >> hi! >>=20 >> I did try to reach you, but mail did bounce back=E2=80=A6 >>=20 >> unicast ping me:) >>=20 >> rgds, >> toomas >>=20 >> On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: >>=20 >> Hello, >>=20 >> Around starting 20191114 r354699 (memstick tested), my desktop not >> boot normally. Boot only loader menu (black and white mode) after >> start i'm see load modules, after this monitor gray, and 15-20s >> disabled, system block not disable but run silently. system not boot. >>=20 >> If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 >> release, system boot normally >>=20 >>=20 >>=20 >> This video boot second version (Name: "loader.efi") 545 KB >> https://bsdnir.info/files/efi_fail.mp4 >>=20 >>=20 >> 403 Forbidden >>=20 >> :=3D) >>=20 >> rgds, >> toomas From owner-freebsd-current@freebsd.org Thu Nov 28 20:52:37 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C9061B7A2E for ; Thu, 28 Nov 2019 20:52:37 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) (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 47P8wK6HZmz44w8 for ; Thu, 28 Nov 2019 20:52:33 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id F279B4000D for ; Thu, 28 Nov 2019 21:52:30 +0100 (CET) Received: from [192.168.1.132] (h-201-140.A785.priv.bahnhof.se [98.128.201.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id DB0644000C for ; Thu, 28 Nov 2019 21:52:30 +0100 (CET) From: Peter Eriksson Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Best way to print something from the kernel at 1s intervals? Message-Id: Date: Thu, 28 Nov 2019 21:52:30 +0100 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 47P8wK6HZmz44w8 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=liu.se; spf=pass (mx1.freebsd.org: domain of pen@lysator.liu.se designates 130.236.254.3 as permitted sender) smtp.mailfrom=pen@lysator.liu.se X-Spamd-Result: default: False [-2.55 / 15.00]; ARC_NA(0.00)[]; SUBJECT_ENDS_SPACES(0.50)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.lysator.liu.se]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; MV_CASE(0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[3.254.236.130.list.dnswl.org : 127.0.11.2]; DMARC_POLICY_ALLOW(-0.50)[liu.se,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:2843, ipnet:130.236.0.0/16, country:SE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-1.55)[ipnet: 130.236.0.0/16(-4.28), asn: 2843(-3.42), country: SE(-0.03)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 20:52:37 -0000 I=E2=80=99ve been looking into the =E2=80=9Ckernel looks to be hung at = reboot=E2=80=9D problem at bit. Adding a lot of printf() calls to the = relevant parts it looks like it actually isn=E2=80=99t hung but busy = unmounting filesystems (which we have thousands of), flushing disk = caches, calling registered callbacks and stuff and sometimes it takes a = bit longer than usual - probably due to ZFS having stuff queued up that = needs to be written to disk before it finishes=E2=80=A6 Anyway, I=E2=80=99d like to propose that we add some kind of = counter/printf() calls in that code area so we can see that things are = indeed progressing. However, I=E2=80=99d probably prefer not to print = _every_ filesystem (or registered callbacks - a lot of those...) - that = generates a lot of output (tried that :-) but something like: Unmounting filesystems: 1234 done (With the "1234 done=E2=80=9D updated something like once per second). What=E2=80=99s the right/best way to do that from the kernel? In user = space I=E2=80=99d just call time(&t) at some convenient points and only = print something if =E2=80=9Ct=E2=80=9D has changed. :-) - Peter From owner-freebsd-current@freebsd.org Thu Nov 28 21:01:19 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B01491B7EE0; Thu, 28 Nov 2019 21:01:19 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47P96Q48FGz45Kq; Thu, 28 Nov 2019 21:01:18 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: by mail-wr1-x442.google.com with SMTP id b6so2987971wrq.0; Thu, 28 Nov 2019 13:01:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=fW6J4PxiMto8xq31NanXnNJZ+AFybLygTbISDpFw8R8=; b=dfWkVps3y7lg5OUJhnTeCOjOnayj4iwpGMAOGlZOaUVJrKEi8zflTlo0W0Uwu+q6IN vSWJs/pr32b718RlWzgUNB0jEHWS81UPW5VCtMycDskJvEHqwzZ9BqgRnvXrMdAFct08 MAg6imo/ta6KHhd8JyiG4iDKac/Gk5cZuWEeVLaMMlxcNHSXgeAQiWtkMp+SSW9Mz2hu vlWuZXFBWyp41vWHd2ZjbAAWmVGgC8K3Y0zJTuRVqkCjVJLsBrQd5KOBJjKGdnKCqQu3 ouXFLwctSlh7Wow+VxxfLmEMhFhFC7XmQM6zpVS4jPd+7T9X513zn4ojcIs4/R+e1OtA yn8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=fW6J4PxiMto8xq31NanXnNJZ+AFybLygTbISDpFw8R8=; b=BsQ7ZhfFV2oSMjgR+WUFnW6xBUyNy2KRZXdlFKw2q547hSRdHcGNuLx6DQ7a95RMV/ /aplVVI06X0/siJKRH3GPeGHyPd6gArwH0LBRWeFaImP0y0Qr0DGuonWwXoXN+Lz24AI zYnpQKPp3zIfA3LwQUSEdhedSh8RZH2jl0+uLMmAwF58bDGLNePWZ/W8N+w8tW7BhjAY JZJG1acP4Qi1KaGms1W3pVdc/rlP7E5eBbmRUHdoS4iJLycBTiDOmCV6eKrxCLOaf3id 8cKAfl0H4fm/PWK9cC3UkgyR51PG8YmQRreiF0LVc9R5j8y2EhMnNKSH6+Jii8oc7+UB igrw== X-Gm-Message-State: APjAAAUXk1/iHCWMzh2xetoK2ob3GhJv9HM8BzV24cMTAs/i/yQEAxuy mFgQGWxGnplSzLXKjT/pG5Hec6CWGjNWZaA5HC0= X-Google-Smtp-Source: APXvYqysshI1oTvQW0XGx2t2FikrDUn/wgdiIkTAidQ3R9i9qKLikmE8kJBRABzz4pYjYXPbQuY4XU9KWJKjQkG/caA= X-Received: by 2002:adf:ff84:: with SMTP id j4mr9501629wrr.27.1574974876789; Thu, 28 Nov 2019 13:01:16 -0800 (PST) MIME-Version: 1.0 References: <49B58A7F-0DE2-4BEB-8A8C-D996962FDDE1@me.com> <8C721EA7-09EA-4154-AC29-273B3A881FA4@me.com> In-Reply-To: <8C721EA7-09EA-4154-AC29-273B3A881FA4@me.com> From: Andrey Fesenko Date: Fri, 29 Nov 2019 00:01:05 +0300 Message-ID: Subject: Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H To: Toomas Soome Cc: freebsd-current , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47P96Q48FGz45Kq X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=dfWkVps3; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of f0andrey@gmail.com designates 2a00:1450:4864:20::442 as permitted sender) smtp.mailfrom=f0andrey@gmail.com X-Spamd-Result: default: False [-1.99 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(0.00)[+ip6:2a00:1450:4000::/36]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(0.00)[gmail.com,none]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.49), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.95), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(0.00)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; URIBL_PBL(0.01)[bsdnir.info]; RCVD_IN_DNSWL_NONE(0.00)[2.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 21:01:19 -0000 On Thu, Nov 28, 2019 at 11:31 PM Toomas Soome wrote: > > > > > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > > > Fixed > > > > Thanks. And yea, that one is nasty. I have some guess but nothing too sol= id=E2=80=A6 it may take time to get figured out. > > Have you tested BIOS boot? > > rgds, > toomas > > > On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > >> > >> > >> > >> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > >> > >> On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > >> > >> > >> hi! > >> > >> I did try to reach you, but mail did bounce back=E2=80=A6 > >> > >> unicast ping me:) > >> > >> rgds, > >> toomas > >> > >> On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > >> > >> Hello, > >> > >> Around starting 20191114 r354699 (memstick tested), my desktop not > >> boot normally. Boot only loader menu (black and white mode) after > >> start i'm see load modules, after this monitor gray, and 15-20s > >> disabled, system block not disable but run silently. system not boot. > >> > >> If i'm change efi (EFI/BOOT/bootx64.efi), 20191031-r354207 or 12.1 > >> release, system boot normally > >> > >> > >> > >> This video boot second version (Name: "loader.efi") 545 KB > >> https://bsdnir.info/files/efi_fail.mp4 > >> > >> > >> 403 Forbidden > >> > >> :=3D) > >> > >> rgds, > >> toomas > BIOS boot fine, loader colored, installer start normal. From owner-freebsd-current@freebsd.org Thu Nov 28 21:09:07 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C41911B8420 for ; Thu, 28 Nov 2019 21:09:07 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-22.consmr.mail.gq1.yahoo.com (sonic301-22.consmr.mail.gq1.yahoo.com [98.137.64.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 47P9HQ6KYXz45py for ; Thu, 28 Nov 2019 21:09:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: InjXviUVM1kToZR51lcPXy.WowW2NOsJ.j.ubeEv2.mln0dV_lOsKS4HqjU2OZK Xu7ZB_Cbm5aQXlaTmADzWrE_bK.JoXwL467DV.J9Z._i8FjHsUzN_RaTBGtZlhQccUDW1S9r0kz4 069VpgVzWhDXPbj6EhjX9LWsW38xZkhgdgZiGIV2XPKxdTn4CZ1ibhqOAB3_hZWIVlqx.O6GVQxn 4Hm46ynZgQRsrQWzUiWYnqVI2uyZosS0haxSyXSvtWxuLJTr5DUw.Qf5nj4i.2Cau_uKHZnLZj1R _6D3mGU2pOO9YMU3KylDnjelNKy6F3iwo2jJcMumKWRlYwZXIj4f9fGahoCBS9Wj.N3yvLPz.r_u 3jEQ4ZCl8f1YCMUSYGWBzDctSDmakaSsZixwuGkz_mfCa6NpjydPxP.h2yZKkFdcHQ8fIj.eAqiv rlPDcqsxl9WfLZwn3l0e18RI.OPTs5z8lT_xvP6._Yli528ZRYkjTMtdGCGja_DW7H_KcgB9S0Z5 RcOIYymUCBQQuIFo7UuPqucWMLOcOdOIzr4Lvi_.6xAYtyUMx961vUCNeW5YbAjI5krAmzRvl_bt D89GhMqR7ST6qj_AjvLDDdDBydEl30HopqYKCSvp_X.sTg7I2WffN7NtgJY8l5wyDXyj29M81wzO O6aLOX1_PQZOseILm.UA9dlksDlpSo1nXxEYZpIr5E0n9dNFpJHAzkH2RUX1cy5O4pJ._Y9IeHCj Rn0pH23kvf9cBLyL0gj0DMOQ1uOdHKFwkSfVOeUBq.H4mcaCxIVjloPPW.LYwEtKxhfcuTLhkrwI C2FCU1bWSIpariaKlKA7hCU7aeoZARBWHeOlN7o4ol5_y3HaEkwqzdebT5lQv4N9GJy016Faa_3J M5YFTnZkVIy9_HvY10usJTRu87fG6xpYBcrdz5lycHRwVBBRV8mWUcJVjF.iaF7yhSs5GtrcA7X1 jNdfjUQ2n3Wr1jZUEmqUVZVOAVG1_td39b.cQYGo.uFJCgFfdeo2Rtqst4K05vKHT71d.6w6HJrJ CA1UJXe7KZjH_bRqF4DWEDSnWr2gTutRnkTSCn1l4LUN9pbCmvJxJIQUVseOS1TApSr28owISuu2 _bePWHk.kddpcrj.t.5BWwR1Jt8UA63jA8r67l0fE9puq3Y_RIuVVaJerDpfKQ_Th1q1YwXMcg78 fM24zezcB1.OZhffwNdccDDiaknZJ92xR8FytWnYgkXsDpaCHWg1MfS7R5kmDtVa6.q2X8qcdbOl g1kdJdWlBrfD74eCfhrH0jjozpytxUtuEGLSyMwKMUG.x99jarZb1uv50TbyWKrOWt5HjdWiN99s bIRCEX9OZaOPszvl32gShu6lz0iGikUfzipjoSaFgsU59sW2a3dsRRtvIRMNvrFx2G3Doih3Qk4U eB0ygmdk9d4JUcDp3LXy78B6neQpvKD0AI6a1 Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.gq1.yahoo.com with HTTP; Thu, 28 Nov 2019 21:09:04 +0000 Received: by smtp402.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 17ff6fe9fcd5c78ff9a126d9173bdbad; Thu, 28 Nov 2019 21:08:59 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: svn commit: r352558 - head/usr.bin/top Message-Id: <1BDFB387-930D-4F4D-8729-A5850F1C15B9@yahoo.com> Date: Thu, 28 Nov 2019 13:08:57 -0800 To: "daichi@freebsd.org" , svn-src-head@freebsd.org, FreeBSD Current X-Mailer: Apple Mail (2.3601.0.10) References: <1BDFB387-930D-4F4D-8729-A5850F1C15B9.ref@yahoo.com> X-Rspamd-Queue-Id: 47P9HQ6KYXz45py X-Spamd-Bar: / X-Spamd-Result: default: False [0.64 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (5.43), ipnet: 98.137.64.0/21(0.87), asn: 36647(0.70), country: US(-0.05)]; NEURAL_SPAM_MEDIUM(0.40)[0.405,0]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.74)[0.736,0]; RCVD_IN_DNSWL_NONE(0.00)[148.64.137.98.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 21:09:07 -0000 > Author: daichi > Date: Fri Sep 20 17:37:23 2019 > New Revision: 352558 > URL: > https://svnweb.freebsd.org/changeset/base/352558 > > > Log: > top(1): support multibyte characters in command names (ARGV array) > depending on locale. > > - add setlocale() > - remove printable() function > - add VIS_OCTAL and VIS_SAFE to the flag of strvisx() to display > non-printable characters that do not use C-style backslash sequences > in three digit octal sequence, or remove it > > This change allows multibyte characters to be displayed according to > locale. If it is recognized as a non-display character according to the > locale, it is displayed in three digit octal sequence. > Initially picking on tab characters as an example of what is probably a somewhat broader issue . . . Ever since this change, characters like tabs that do not fit in the next character cell when output, but for which they are !isprintable(...), now mess up the top display. Again using tab as an example: line wrapping from the text having been shifted over by more than one character cell. top does not track the line wrapping result in how it decides what to output for the following display updates. As stands I type "hh" to referesh the display when I care about clearing up the messy display. The removed !isprintable handling functionality had its uses and an alternative is needed for some types of characters if the display is not to be messed up by what some command lines that are echoed have in them. I picked on tab because it was obviously involved in some examples that I watched update. I'm not claiming tab is the only character that ends up with e cursor in an unexpected place now. In fact . . . Looking around I found: VIS_SAFE Only encode "unsafe" characters. Unsafe means control char- acters which may cause common terminals to perform unexpected functions. Currently this form allows space, tab, newline, backspace, bell, and return - in addition to all graphic characters - unencoded. So tab, newline, backspace, bell, and return are not encoded or replaced now but do not have top's expected cursor position result. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Fri Nov 29 01:07:48 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 68BDC1BE6C2 for ; Fri, 29 Nov 2019 01:07:48 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47PGZq3fVpz4Jp9 for ; Fri, 29 Nov 2019 01:07:47 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 19B968D4A15D for ; Fri, 29 Nov 2019 01:07:40 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id AA40BE707B5 for ; Fri, 29 Nov 2019 01:07:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id An_0z5LxEy6e for ; Fri, 29 Nov 2019 01:07:34 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:9ccd:796c:3f6:2446]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 285B0E707B3 for ; Fri, 29 Nov 2019 01:07:33 +0000 (UTC) From: "Bjoern A. Zeeb" To: "FreeBSD Current" Subject: various VM panics (arm64) / hangs after init (arm64/x86) Date: Fri, 29 Nov 2019 01:07:32 +0000 X-Mailer: MailMate (2.0BETAr6142) Message-ID: <8E3B0C4F-B17D-4803-9B6F-1C1F9AAFAF68@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47PGZq3fVpz4Jp9 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-5.11 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zabbadoz.net]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(-2.81)[ip: (-8.92), ipnet: 195.201.0.0/16(-3.53), asn: 24940(-1.58), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 01:07:48 -0000 Hi, over the last days both on x86 as well as on arm64 I had various strange “hangs” or panics. I’ll try to find svn revisions which do compile and try and see if I can do a bit of bisect (the first two attempts did not compile; should try the CI system). Given it is all new setups from the last week, I do not have previous behaviour (or 12.x one only). (a) on x86 and arm64 I have “hangs” after starting init around the re-mount; one of the later “hangs” on arm64 was: Initially I thought it was related to USB as not compiling that in made the problem go away on x86 (where the console was frozen in a 1 VCPU VM so I couldn’t debug). On Arm64 I can now press ^T and see that it actually is waiting hard .. (and removing USB from the kernel did move the problem slightly but not make it go away). (notice real time) load: 0.45 cmd: sysctl 27 [objtrm] 1711.61r 0.00u 0.00s 0% 0k (b) The quickest I found so far was on arm64/head from an hour ago; this is with and without an md_image or other modules loaded and GENERIC rather than GENERIC-NODEBUG (reproduced in two consecutive boots); it seems to sometimes matter whether I boot with hw.ncpu=4 or hw.ncpu=1: ---<>--- KDB: debugger backends: ddb KDB: current backend: ddb Type Physical Virtual #Pages Attr ConventionalMemory 000000200000 200000 00007eea WB RuntimeServicesData 0000080ea000 80ea000 0000002c WB RUNTIME ConventionalMemory 000008116000 8116000 000e46e9 WB LoaderData 0000ec7ff000 ec7ff000 00008696 WB LoaderCode 0000f4e95000 f4e95000 0000008d WB RuntimeServicesData 0000f4f22000 f4f22000 00000001 WB RUNTIME Reserved 0000f4f23000 f4f15000 00000006 WB RuntimeServicesData 0000f4f29000 f4f29000 00000001 WB RUNTIME Reserved 0000f4f2a000 f4f2a000 00000002 WB LoaderData 0000f4f2c000 f4f2c000 00003014 WB RuntimeServicesCode 0000f7f40000 f7f40000 00000010 WB RUNTIME LoaderData 0000f7f50000 f4f2c000 000000b0 WB Physical memory chunk(s): 0x00200000 - 0xf4f22fff, 3917 MB (1002787 pages) 0xf4f29000 - 0xf4f29fff, 0 MB ( 1 pages) 0xf4f2c000 - 0xf7f3ffff, 48 MB ( 12308 pages) 0xf7f50000 - 0xf7ffffff, 0 MB ( 176 pages) Excluded memory regions: 0x080ea000 - 0x08115fff, 0 MB ( 44 pages) NoAlloc 0xec800000 - 0xf0f38fff, 71 MB ( 18233 pages) NoAlloc 0xf4f22000 - 0xf4f2bfff, 0 MB ( 10 pages) NoAlloc 0xf7f40000 - 0xf7f4ffff, 0 MB ( 16 pages) NoAlloc Found 6 CPUs in the device tree Copyright (c) 1992-2019 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-arm64-base13-nanopct4 #1 r355193M 11d01e051405-c509697(master): Fri Nov 29 00:31:57 UTC 2019 .. FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLVM 9.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. Preloaded elf kernel "/boot/kernel/kernel" at 0xffff00000450c000. Preloaded md_image "/base13-nanopct4-r355193" at 0xffff000004514e80. Preloaded elf module "/boot/kernel/nullfs.ko" at 0xffff000004514ee0. Preloaded elf module "/boot/kernel/geom_eli.ko" at 0xffff000004515638. module firmware already present! panic: page 0xfffffd00ec54c170 has object cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff0000006dee8c lr = 0xffff0000001066c8 sp = 0xffff0000000103f0 fp = 0xffff000000010600 db_trace_self_wrapper() at vpanic+0x18c pc = 0xffff0000001066c8 lr = 0xffff0000003b563c sp = 0xffff000000010610 fp = 0xffff0000000106c0 vpanic() at panic+0x44 pc = 0xffff0000003b563c lr = 0xffff0000003b53ec sp = 0xffff0000000106d0 fp = 0xffff000000010750 panic() at vm_page_alloc_check+0x78 pc = 0xffff0000003b53ec lr = 0xffff000000692b2c sp = 0xffff000000010760 fp = 0xffff000000010760 vm_page_alloc_check() at vm_page_alloc_domain_after+0x2a4 pc = 0xffff000000692b2c lr = 0xffff000000692298 sp = 0xffff000000010770 fp = 0xffff0000000107f0 vm_page_alloc_domain_after() at kmem_back_domain+0xec pc = 0xffff000000692298 lr = 0xffff00000067de6c sp = 0xffff000000010800 fp = 0xffff000000010850 kmem_back_domain() at kmem_malloc_domainset+0xc0 pc = 0xffff00000067de6c lr = 0xffff00000067dd48 sp = 0xffff000000010860 fp = 0xffff0000000108d0 kmem_malloc_domainset() at vm_ksubmap_init+0x54 pc = 0xffff00000067dd48 lr = 0xffff00000067d1d8 sp = 0xffff0000000108e0 fp = 0xffff000000010920 vm_ksubmap_init() at cpu_startup+0x1c pc = 0xffff00000067d1d8 lr = 0xffff0000006ea77c sp = 0xffff000000010930 fp = 0xffff000000010930 cpu_startup() at mi_startup+0x12c pc = 0xffff0000006ea77c lr = 0xffff00000034e2d4 sp = 0xffff000000010940 fp = 0xffff0000000109a0 mi_startup() at virtdone+0x58 pc = 0xffff00000034e2d4 lr = 0xffff0000000010c8 sp = 0xffff0000000109b0 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at 0 FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 13.0-arm64-base13-nanopct4 #1 r355193M 11d01e051405-c509697(master): Fri Nov 29 00:31:57 UTC 2019 .. FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLVM 9.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. Preloaded elf kernel "/boot/kernel/kernel" at 0xffff0000014b2000. module firmware already present! panic: page 0xfffffd00ec551f68 has object cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff0000006dee8c lr = 0xffff0000001066c8 sp = 0xffff0000000103f0 fp = 0xffff000000010600 db_trace_self_wrapper() at vpanic+0x18c pc = 0xffff0000001066c8 lr = 0xffff0000003b563c sp = 0xffff000000010610 fp = 0xffff0000000106c0 vpanic() at panic+0x44 pc = 0xffff0000003b563c lr = 0xffff0000003b53ec sp = 0xffff0000000106d0 fp = 0xffff000000010750 panic() at vm_page_alloc_check+0x78 pc = 0xffff0000003b53ec lr = 0xffff000000692b2c sp = 0xffff000000010760 fp = 0xffff000000010760 vm_page_alloc_check() at vm_page_alloc_domain_after+0x2a4 pc = 0xffff000000692b2c lr = 0xffff000000692298 sp = 0xffff000000010770 fp = 0xffff0000000107f0 vm_page_alloc_domain_after() at kmem_back_domain+0xec pc = 0xffff000000692298 lr = 0xffff00000067de6c sp = 0xffff000000010800 fp = 0xffff000000010850 kmem_back_domain() at kmem_malloc_domainset+0xc0 pc = 0xffff00000067de6c lr = 0xffff00000067dd48 sp = 0xffff000000010860 fp = 0xffff0000000108d0 kmem_malloc_domainset() at vm_ksubmap_init+0x54 pc = 0xffff00000067dd48 lr = 0xffff00000067d1d8 sp = 0xffff0000000108e0 fp = 0xffff000000010920 vm_ksubmap_init() at cpu_startup+0x1c pc = 0xffff00000067d1d8 lr = 0xffff0000006ea77c sp = 0xffff000000010930 fp = 0xffff000000010930 cpu_startup() at mi_startup+0x12c pc = 0xffff0000006ea77c lr = 0xffff00000034e2d4 sp = 0xffff000000010940 fp = 0xffff0000000109a0 mi_startup() at virtdone+0x58 pc = 0xffff00000034e2d4 lr = 0xffff0000000010c8 sp = 0xffff0000000109b0 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at 0 db> (c) then one before on a GENERIC-NODEBUG kernel was along these lines with hw.ncpu=4 and an md_image loaded: .. Release APs...gic0: Start searching for Re-Distributor gic0: Start searching for Re-Distributor gic0: Start searching for Re-Distributor gic0: CPU1 Re-Distributor has been found gic0: CPU3 Re-Distributor has been found gic0: CPU2 Re-Distributor has been found gic0: CPU1 Re-Distributor woke up gic0:P Re-Distributor woke up gic0: CPU1 enabled CPU interface via system registers gic0: CPU2 enabled CPU interface via system registers gic0: CPU3 Re-Distributor woke up gic0: CPU3 enabled CPU interface via system registers done F@tal data abort: CPU 0: ARM Cortex-A53 r0p4 affinity: 0 x0: fffffd00015f2fb8 Instruction Set Attributes 0 = x1: ffff00005abed508 Instruction Set Attributes 1 = <> x2: 0 x3: ffff00005abed50c Processor Features 0 = x4: 2 Processor Features 1 = <> x5: ffff000000c7a2a0 x6: ffff000000c7a2a8 Memory Model Features 0 = x7: ffff000000c7a2b0 Memory Model Features 1 = <8bit VMID> Memory Model Features 2 = <32bit CCIDX,48bit VA> x9: 3d Debug Features 0 = <2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3,Debugv8> x10: fffffd00015f2e00 Debug Features 1 = <> x11: 2 Auxiliary Features 0 = <> x12: fffffd0000802b40 Auxiliary Features 1 = <> x13: 100 CPU 1: ARM Cortex-A53 r0p4 affinity: 1 x14: 1 CPU 2: ARM Cortex-A53 r0p4 affinity: 2 x15: 0 CPU 3: ARM Cortex-A53 r0p4 affinity: 3 x16: 1 x17: ffff000000c7a2a0 regulator: shutting dowN vbus_py`Ec x18: ffff00005abed4e0 x19: fffffd0000802a80 x20: ffffffff x21: 18 x22: 3d x23: fffffd0000819000 x24: fffffd000214d218 x25: a x26: 3d x27: ffff000000a6f000 x28: 2 x29: ffff00005abed580 sp: ffff00005abeD4e lr: ffff0000006a42a0 elr: ffff0000006a4384 spsr: 80000145 far: a esr: 96000044 panic: vm_fault failed: ffff0000006a4384 cpuid = 3 time = 1 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff00000070cb6c lr = 0xffff00000010695c db_trace_self_wrapper() at vpanic+0x18c0xffff00005abed0e0 pc = 0xffff00000010695c lr = 0xffff0000003ca864 sp = 0xffff00005abed0f0 fp = 0xffff00005abed1a0 vpanic() at panic+0x44 pc = 0xffff0000003ca864 lr = 0xffff0000003ca6d4 sp = 0xffff00005abed1b0 fp = 0xffff00005abed230 panic() at d@`@_abort+0x1e0 pc = 0xffff0000003ca6d4 lr = 0xffff000000728c34 sp = 0xffff00005abed240 fp = 0xffff00005abed2f0 data_abort() at do_eH1h_sync+0x144 pc = 0xffff000000728c34 lr = 0xffff000000727e50 sp = 0xffff00005abed300 fp = 0xffff00005abed330 do_el1h_sync() at @andHe_el1h_sync+0x78 pc = 0xffff000000727e50 lr = 0xffff00000070f078 sp = 0xffff00005abed340 fp = 0xffff00005abed450 handle_el1h_sync() ad zone_import+0x264 pc = 0xffff00000070f078 lr = 0xffff0000006a429c sp = 0xffff00005abed460 fp = 0xffff00005abed580 zone_import() at cache_alloc+0x480 pc = 0xffff0000006a429c lr = 0xffff00000069f748 sp = 0xffff00005abed590 fp = 0xffff00005abed5e0 cache_alloc() at uma_zalloc_arg+0x60 pc = 0xffff00000069f748 lr = 0xffff00000069efb8 sp = 0xffff00005abed5f0 fp = 0xffff00005aBed6 uma_zalloc_arg() at malloc+0x70 pc = 0xffff00000069efb8 lr = 0xffff0000003a4320 sp = 0xffff00005abed630 fp = 0xffff00005abed660 malloc() at crdup+0x20 pc = 0xffff0000003a4320 lr = 0xffff0000003ba0e0 sp = 0xffff00005abed670 fp8 xffff00005abed680 crdup() at vfs_mount_alloc+0xe4 pc = 0xffff0000003ba0e0 hr 8 xffff00000049002c sp = 0xffff00005abed690 fp = 0xffff00005abed6c0 vfs_mount_alloc() at vfs_mountroot+0x220 pc = 0xffff00000049002c lr = 0xffff000000494204 sp = 0xffff00005abed6d0 fp = 0xffff00005abed880 vfs_mountroot() at start_init+0x"4 pc =0xDDdD000000494204 lr = 0xffff0000003604b0 sp = 0xffff00005abed890 fp = 0xffff00005abed940 start_init() at fork_exit+0x90 pc = 0xffff0000003604b0 lr = 0xffff000000389598 sp = 0xffff00005abed950 fp = 0xffff00005abed980 fork_exit() at fo`k_trampoline+0x10 pc = 0xffff000000389598 lr = 0xffff000000727b8c s` < xDDff00005abed990 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at zone_import+0x34c: undefined f900056c I do have more of these kinds of things .. and I can probably produce more by rebuilding the kernel and playing with a few parameters.. Any hints or suggestions welcome. /bz From owner-freebsd-current@freebsd.org Fri Nov 29 06:25:52 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4758E1C509E for ; Fri, 29 Nov 2019 06:25:52 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47PPdq2Z8fz4XG1 for ; Fri, 29 Nov 2019 06:25:51 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-lj1-x235.google.com with SMTP id a13so7539739ljm.10 for ; Thu, 28 Nov 2019 22:25:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+YJIPZwUR2s6/g7hArDXUClFsOwMJqL/F7UdtxFO5uY=; b=drQqKBlL4gjrnvyVbQfRP7E+LYjhDxmgPv/F5P93zay+lDOOiK78u6KZs/uq2EEipE ienbCC1PsKRPFZ+3EOqhgxUHDiRWkSco4GjrV4MVOGZ4GPCO5p1Y55grsezeyjsCbvqD OLNipRfX+XgrDgzzUSMEtOhZ/5YJ07cj8i6XtCrPx7UUFF8w/Eze80mN2qorDJegDhRV XEKhViIauRHrUbFAuXU2NYdPTxH9nMFXcJPduksyzMobbuFlqnCb/E/AyzYSjQAvgEi+ ahxUHub+DGhpNm3tuhW2A55VDS9yZB4Ld5x78z0KQP7CqcszmUtCkiJ81Bv3dZjwvJDW cZbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+YJIPZwUR2s6/g7hArDXUClFsOwMJqL/F7UdtxFO5uY=; b=hcXojuMn+hiQl3EIiqTA0vUyRQq6UHlNLopco7Wia7HRvcl8s6iU4Bo0VWF/QnqzL8 WdiBget79hTsxSGPoQqcLQZfRcEIObE1/I6juEpkLvqKzjW0S6o/69ysAj5CcT85ejF1 SP+4kOcaevcFUKquDlIGTDA6+RmERnDXrd1TFZ4B1CAP4BbdP3fWv2/VlbfpbHllcNTq WVXZPNs6m7YM0nsulTV9ONH+/YLWHuYQ1ZTRobqukw7ooh+EBAd8KEXOn9ycYSHAc2bT vv6R2bq+hUXGCJ99j+A2KFmQXfaIzupEuQRn7klMzMq7n9CdUXq/YVpAsodL2TjC+Ars d8WA== X-Gm-Message-State: APjAAAW44gfZ/FzlN+pwYhVzIW4GuMgyrC92w32EtHq0ducTGNVshkDl mMD+JZTwCANWEZMzi8fHhJ4qTJMSl8+/IWiQKOeRRwI= X-Google-Smtp-Source: APXvYqx0F4wGv9ruV+n3iFMMEPuz6T9eqGHY1oT8a9II+P5UQE4ChwrQI46U8YETz63MxWCdLoh9P1PN/7sUX5pBwbA= X-Received: by 2002:a2e:91c1:: with SMTP id u1mr7866764ljg.181.1575008747686; Thu, 28 Nov 2019 22:25:47 -0800 (PST) MIME-Version: 1.0 From: Clay Daniels Date: Fri, 29 Nov 2019 00:25:36 -0600 Message-ID: Subject: 13.0-CURRENT r355121 snapshot .img Works Great! To: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 47PPdq2Z8fz4XG1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=drQqKBlL; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2a00:1450:4864:20::235 as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; SUBJECT_ENDS_EXCLAIM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.46), ipnet: 2a00:1450::/32(-2.69), asn: 15169(-1.94), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 06:25:52 -0000 drmn0: successfully loaded firmware image with name: amdgpu/polaris~ AMD Ryzen 7 3700x cpu with MSI 570 series Motherboard & Video Card [Home built machine] Able to make drm-kmod from ports Third week in a row with no problems! Clay From owner-freebsd-current@freebsd.org Fri Nov 29 19:13:39 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 66B781B965D for ; Fri, 29 Nov 2019 19:13:39 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.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 47Pkgk3C7Sz4DFN for ; Fri, 29 Nov 2019 19:13:37 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id xATJDR3A017793; Fri, 29 Nov 2019 11:13:27 -0800 (PST) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id xATJDQId017792; Fri, 29 Nov 2019 11:13:26 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201911291913.xATJDQId017792@gndrsh.dnsmgr.net> Subject: Re: Best way to print something from the kernel at 1s intervals? In-Reply-To: To: Peter Eriksson Date: Fri, 29 Nov 2019 11:13:26 -0800 (PST) CC: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 47Pkgk3C7Sz4DFN X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [3.34 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.04)[ip: (0.14), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.03), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.60)[0.602,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.80)[0.803,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 19:13:39 -0000 > I?ve been looking into the ?kernel looks to be hung at reboot? problem at bit. Adding a lot of printf() calls to the relevant parts it looks like it actually isn?t hung but busy unmounting filesystems (which we have thousands of), flushing disk caches, calling registered callbacks and stuff and sometimes it takes a bit longer than usual - probably due to ZFS having stuff queued up that needs to be written to disk before it finishes? > > Anyway, I?d like to propose that we add some kind of counter/printf() calls in that code area so we can see that things are indeed progressing. However, I?d probably prefer not to print _every_ filesystem (or registered callbacks - a lot of those...) - that generates a lot of output (tried that :-) but something like: > > Unmounting filesystems: > 1234 done > (With the "1234 done? updated something like once per second). > > What?s the right/best way to do that from the kernel? In user space I?d just call time(&t) at some convenient points and only print something if ?t? has changed. :-) How about updated every 128 unmounts? if ((i & 0x7f) == i) printf("%i done\n:"); > > - Peter -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Fri Nov 29 19:15:06 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4FB351B97EE for ; Fri, 29 Nov 2019 19:15:06 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.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 47PkjN6yWNz4DPB for ; Fri, 29 Nov 2019 19:15:04 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id xATJF3pZ017810; Fri, 29 Nov 2019 11:15:03 -0800 (PST) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id xATJF3hg017809; Fri, 29 Nov 2019 11:15:03 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201911291915.xATJF3hg017809@gndrsh.dnsmgr.net> Subject: Re: Best way to print something from the kernel at 1s intervals? In-Reply-To: <201911291913.xATJDQId017792@gndrsh.dnsmgr.net> To: "Rodney W. Grimes" Date: Fri, 29 Nov 2019 11:15:03 -0800 (PST) CC: Peter Eriksson , freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 47PkjN6yWNz4DPB X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [3.60 / 15.00]; ARC_NA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.73)[0.729,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.04)[ip: (0.14), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.03), country: US(-0.05)]; NEURAL_SPAM_LONG(0.93)[0.933,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 19:15:06 -0000 > > I?ve been looking into the ?kernel looks to be hung at reboot? problem at bit. Adding a lot of printf() calls to the relevant parts it looks like it actually isn?t hung but busy unmounting filesystems (which we have thousands of), flushing disk caches, calling registered callbacks and stuff and sometimes it takes a bit longer than usual - probably due to ZFS having stuff queued up that needs to be written to disk before it finishes? > > > > Anyway, I?d like to propose that we add some kind of counter/printf() calls in that code area so we can see that things are indeed progressing. However, I?d probably prefer not to print _every_ filesystem (or registered callbacks - a lot of those...) - that generates a lot of output (tried that :-) but something like: > > > > Unmounting filesystems: > > 1234 done > > (With the "1234 done? updated something like once per second). > > > > What?s the right/best way to do that from the kernel? In user space I?d just call time(&t) at some convenient points and only print something if ?t? has changed. :-) > > How about updated every 128 unmounts? > > if ((i & 0x7f) == i) printf("%i done\n:"); if ((i & 0x7f) == 0) printf("%i done\n:"); > > > > - Peter > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Fri Nov 29 21:09:54 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 380581BBFD7 for ; Fri, 29 Nov 2019 21:09:54 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x541.google.com (mail-pg1-x541.google.com [IPv6:2607:f8b0:4864:20::541]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47PnFs2Wvyz4JfY for ; Fri, 29 Nov 2019 21:09:53 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg1-x541.google.com with SMTP id i5so6711564pgj.9 for ; Fri, 29 Nov 2019 13:09:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=4SJPx1OsDcAocEmbjiXcLXr6k1b2epD2De29sc4hVNw=; b=SjIsEtS574Q0rUhmrMkMYLHNQsiMtm+WwdAf4q3lSRmId6qH38DVB+iHOyuTIHbnRQ Fsw5t3mcSdpl5XqN+gclaa6anI77oRC/OoRxUNcVkmNyQBz4eRhx82ESxAZDoWU7tw7n FVgLcswC8oxnf16KFv9vhhcLz1Glrnvx5yviu3ipONDTbQI0uZ+uJyXRIJ7lB+Oh7kgO PCGpjedaAUixjsk2bf2rsKG+VTKqH4/LfxHKpke4r8KitWSo/UUmLZklG7lyU3tiAM/X nKATdoHSkc2aQ/6zcsbxlwST4QPZzB6rghctKlhsUShx0AELn16+thXPphKcjJncB3t1 ytGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=4SJPx1OsDcAocEmbjiXcLXr6k1b2epD2De29sc4hVNw=; b=pJcQ7yEJam4XwZOt3S7JlhQ6S7YP1vcrMthwFlut/gsLRWZ/Pm8fCq/orT2Y/A/BR7 UzGTkp4486JQrFg6yQZPLkRoKxdE0qEWGNQTmTHdfp1OBbL5p+DY2TOM5a0HIvVJgbKW Wf7D7M0L7/m7W5hYu1pJqqNs8eukRcrl4JKerPYyP3SMcFRnRiMfEB6iDHZgOU8nVr9S M+Wade0uPfU/xXIPNoR89GppZFuaMr96DaTYqgoVIS+H1SOcTHqs9WyOJJuIb50bMQmi Zsxj6b53Fz/DJTWkXqd17pSOGUfRivnfXx2FWqJqeY67BbfRJOXTsLV3C75kZAQ3cQFD OaHQ== X-Gm-Message-State: APjAAAUV7w1AFlqFywcAcYT3D3NMcv7XJlX93Tq71MY90fPYD18uQD22 ajiUeLBEsjgdEUotBhW4A8vptSmH X-Google-Smtp-Source: APXvYqz7l58+8BlwOoqO0n/Qmri2gRQp0wKs7NkDq1q3am+rjcK0uSSw3MIy5gqGqpkURRpVf3wv0w== X-Received: by 2002:a62:8202:: with SMTP id w2mr13605503pfd.100.1575061790842; Fri, 29 Nov 2019 13:09:50 -0800 (PST) Received: from ?IPv6:2607:fb90:b211:2efc:51d8:e8c0:ed26:2642? ([2607:fb90:b211:2efc:51d8:e8c0:ed26:2642]) by smtp.gmail.com with ESMTPSA id v16sm16485697pje.1.2019.11.29.13.09.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Nov 2019 13:09:50 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Enji Cooper Mime-Version: 1.0 (1.0) Subject: Re: Best way to print something from the kernel at 1s intervals? Date: Fri, 29 Nov 2019 13:09:44 -0800 Message-Id: References: Cc: freebsd-current@freebsd.org In-Reply-To: To: Peter Eriksson X-Mailer: iPhone Mail (17A878) X-Rspamd-Queue-Id: 47PnFs2Wvyz4JfY X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=SjIsEtS5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::541 as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-1.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-0.75), ipnet: 2607:f8b0::/32(-2.25), asn: 15169(-1.94), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 21:09:54 -0000 > On Nov 28, 2019, at 12:52, Peter Eriksson wrote: >=20 > =EF=BB=BFI=E2=80=99ve been looking into the =E2=80=9Ckernel looks to be hu= ng at reboot=E2=80=9D problem at bit. Adding a lot of printf() calls to the r= elevant parts it looks like it actually isn=E2=80=99t hung but busy unmounti= ng filesystems (which we have thousands of), flushing disk caches, calling r= egistered callbacks and stuff and sometimes it takes a bit longer than usual= - probably due to ZFS having stuff queued up that needs to be written to di= sk before it finishes=E2=80=A6 >=20 > Anyway, I=E2=80=99d like to propose that we add some kind of counter/print= f() calls in that code area so we can see that things are indeed progressing= . However, I=E2=80=99d probably prefer not to print _every_ filesystem (or r= egistered callbacks - a lot of those...) - that generates a lot of output (t= ried that :-) but something like: >=20 > Unmounting filesystems: > 1234 done > (With the "1234 done=E2=80=9D updated something like once per second). >=20 > What=E2=80=99s the right/best way to do that from the kernel? In user spac= e I=E2=80=99d just call time(&t) at some convenient points and only print so= mething if =E2=80=9Ct=E2=80=9D has changed. :-) Can you use DTrace instead to get the information you need? Cheers, -Enji= From owner-freebsd-current@freebsd.org Fri Nov 29 22:10:45 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 40DF91BDB61 for ; Fri, 29 Nov 2019 22:10:45 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) (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 47Ppc368jqz4MTp for ; Fri, 29 Nov 2019 22:10:43 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 7094F40014; Fri, 29 Nov 2019 23:10:37 +0100 (CET) Received: from [192.168.1.132] (h-201-140.A785.priv.bahnhof.se [98.128.201.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 43EC240011; Fri, 29 Nov 2019 23:10:37 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: Best way to print something from the kernel at 1s intervals? From: Peter Eriksson In-Reply-To: Date: Fri, 29 Nov 2019 23:10:36 +0100 Cc: Enji Cooper Content-Transfer-Encoding: quoted-printable Message-Id: <057870D3-B59E-47FB-A832-A72DC6F54AFA@lysator.liu.se> References: To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 47Ppc368jqz4MTp X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=liu.se; spf=pass (mx1.freebsd.org: domain of pen@lysator.liu.se designates 2001:6b0:17:f0a0::3 as permitted sender) smtp.mailfrom=pen@lysator.liu.se X-Spamd-Result: default: False [-1.69 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.lysator.liu.se]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.f.7.1.0.0.0.b.6.0.1.0.0.2.list.dnswl.org : 127.0.11.2]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[liu.se,none]; IP_SCORE(-0.20)[ipnet: 2001:6b0::/32(-0.54), asn: 1653(-0.44), country: EU(-0.00)]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:1653, ipnet:2001:6b0::/32, country:EU]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 22:10:45 -0000 I love dtrace, but I seriously doubt that it could be used it for this. = This is the absolutely last code that executes at kernel = shutdown/reboot. All other processes are terminated when this is = happening... Basically the code done in kern_reboot() (and stuff it calls) in = /usr/src/sys/kern/kern_shutdown.c This code in kern_reboot(): ... > EVENTHANDLER_INVOKE(shutdown_pre_sync, howto); > > /* > * Now sync filesystems > */ > if (!cold && (howto & RB_NOSYNC) =3D=3D 0 && once =3D=3D 0) { > once =3D 1; > bufshutdown(show_busybufs); > } > > print_uptime(); > > cngrab(); > > /* > * Ok, now do things that assume all filesystem activity has > * been completed. > */ > EVENTHANDLER_INVOKE(shutdown_post_sync, howto); > > if ((howto & (RB_HALT|RB_DUMP)) =3D=3D RB_DUMP && !cold && = !dumping) > doadump(TRUE); > > /* Now that we're going to really halt the system... */ > EVENTHANDLER_INVOKE(shutdown_final, howto); What I=E2=80=99ve seen is that the three different EVENTHANDLER_INVOKE() = all can cause a lot of calls that can take a long time. As can = bufshutdown(), probably when it calls vfs_unmountall() to unmount all = filesystems. We=E2=80=99re talking like 5-20 minutes (or more). I=E2=80=99ve not = really timed it. I have a feeling it sometimes is due to transactions stored up in the = ZFS filesystems that the system tries to =E2=80=9Crun=E2=80=9D so it = doesn=E2=80=99t have to do it at mount() time after the reboot. If I = reset the machine while it is busy doing this then sometimes the =E2=80=9C= zfs mount -a=E2=80=9D takes very long time at boot instead. Hmm.. I should be able to use the getnanouptime() call to get a = =E2=80=9Cclock=E2=80=9D to look for (it=E2=80=99s used in = print_uptime()). As long as the clock isn=E2=80=99t stopped at this time = in the shutdown sequence atleast :-) *Time to write some code and test this* :-) - Peter > On 29 Nov 2019, at 22:09, Enji Cooper wrote: >=20 >=20 >> On Nov 28, 2019, at 12:52, Peter Eriksson wrote: >>=20 >> =EF=BB=BFI=E2=80=99ve been looking into the =E2=80=9Ckernel looks to = be hung at reboot=E2=80=9D problem at bit. Adding a lot of printf() = calls to the relevant parts it looks like it actually isn=E2=80=99t hung = but busy unmounting filesystems (which we have thousands of), flushing = disk caches, calling registered callbacks and stuff and sometimes it = takes a bit longer than usual - probably due to ZFS having stuff queued = up that needs to be written to disk before it finishes=E2=80=A6 >>=20 >> Anyway, I=E2=80=99d like to propose that we add some kind of = counter/printf() calls in that code area so we can see that things are = indeed progressing. However, I=E2=80=99d probably prefer not to print = _every_ filesystem (or registered callbacks - a lot of those...) - that = generates a lot of output (tried that :-) but something like: >>=20 >> Unmounting filesystems: >> 1234 done >> (With the "1234 done=E2=80=9D updated something like once per = second). >>=20 >> What=E2=80=99s the right/best way to do that from the kernel? In user = space I=E2=80=99d just call time(&t) at some convenient points and only = print something if =E2=80=9Ct=E2=80=9D has changed. :-) >=20 > Can you use DTrace instead to get the information you need? > Cheers, > -Enji From owner-freebsd-current@freebsd.org Fri Nov 29 22:22:29 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 08DB51BE34F for ; Fri, 29 Nov 2019 22:22:29 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47Ppsc5yHCz4NQy for ; Fri, 29 Nov 2019 22:22:28 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1575066147; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=h0tYAkqNAiZzDjii1VDD1EdiEll66Sw4z8uIZzuMYhUWe3Ij3pEfUCQH0+QXIOvgqdYMrKSuAePhD nGMLFHzC60wx0zYZHdFrrghu+xJRE0YxrfHQNbzsH6D6oI6Ft+vaX/On8/8s7Ag1AiZSFMFUwKICo+ juRawbbD/EJCoKUPffwihYJsEIoH1LkE1FX0aD2YCQbfIXDnrz8cBeTP95Z5s0WgTwa3AadOjFFMM0 DZ45Ew2TgdqZJsJbCRhiWJL/MaThM4lX6q0ZQJmTOP4lq/rLyePBGvCtsGeiI6e3167g6awigYRif1 C/Hu4i1GxUgOwU1bYPKdaujdwozueOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=d2iuLSDbprIeWW+b5WOC3IZl+c8O03rACeJNXnFDsXM=; b=qhK634vCluWPNVfGkzcKF1fH0+Z/GoII0jZrLPJi0nc7YlSaMpjf3lTbgHblzXz6SwfHw1/tRC0JP HMIOXA03n7O/XNbs+5pjguLKMcuh5nuicfwoAkXVgd1lFQK0T4kxWrOzk1rjVjfcA8oca0vCRCSEEz KaRdeg8lwF4S/ropex6mjBeyKLgO/1HYQH3gFzX+idKfl3bl9vM+/CFwZslCrZAPQP5a4Qnp7t43WG bQTBG8M+Ku+NBZ/FWi0XpD7oBRbAXzJCr/wl5RLtpaOj4tix2xkQIxM8JWJyrjW3g2eG2L++lE/rY1 sIQczjyfQTk82EZ0u/k4dvYOlSYjxhQ== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=d2iuLSDbprIeWW+b5WOC3IZl+c8O03rACeJNXnFDsXM=; b=QCjnT54+NNqTyD/fBIkHDFNWNqm1LqSoueO9sOaC3fIzdJNTWhlw6bd0V0BQ3RIAsesEFczTQN+tx 20gh4kHsv4Pj8H+9mPSym1fNZC3Qn6LFesIMGytC8RXgs2nZnPMs2BzRg8BYV3VJ5yoQzrR13o4YAP 8TC7UGYFyRxf/TFnuBWEI52M3e1QiZd5p/RmsSXW25Tp+KhVyq6vJxkkprsRQFbDJm6ghXJ03hsXgb YrVF4mHNI8wiT5YJiy4kCvWVb7F9mIYOCRqzosuzEKMX4xa7aKQJjg9aODJMmx7O/shPrwEqRDchk7 3lKOI4vBjrCQRheU6cn6S2Fo7lGK3gg== X-MHO-RoutePath: aGlwcGll X-MHO-User: b77d07af-12f6-11ea-829e-79a40d15cccd X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id b77d07af-12f6-11ea-829e-79a40d15cccd; Fri, 29 Nov 2019 22:22:26 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xATMMNR0085726; Fri, 29 Nov 2019 15:22:23 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Best way to print something from the kernel at 1s intervals? From: Ian Lepore To: Peter Eriksson , freebsd-current@freebsd.org Date: Fri, 29 Nov 2019 15:22:23 -0700 In-Reply-To: <057870D3-B59E-47FB-A832-A72DC6F54AFA@lysator.liu.se> References: <057870D3-B59E-47FB-A832-A72DC6F54AFA@lysator.liu.se> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47Ppsc5yHCz4NQy X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.79 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.89)[-0.887,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US]; NEURAL_HAM_LONG(-0.91)[-0.907,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2019 22:22:29 -0000 On Fri, 2019-11-29 at 23:10 +0100, Peter Eriksson wrote: > I love dtrace, but I seriously doubt that it could be used it for > this. This is the absolutely last code that executes at kernel > shutdown/reboot. All other processes are terminated when this is > happening... > > Basically the code done in kern_reboot() (and stuff it calls) in > /usr/src/sys/kern/kern_shutdown.c > > This code in kern_reboot(): > ... > > EVENTHANDLER_INVOKE(shutdown_pre_sync, howto); > > > > /* > > * Now sync filesystems > > */ > > if (!cold && (howto & RB_NOSYNC) == 0 && once == 0) { > > once = 1; > > bufshutdown(show_busybufs); > > } > > > > print_uptime(); > > > > cngrab(); > > > > /* > > * Ok, now do things that assume all filesystem activity has > > * been completed. > > */ > > EVENTHANDLER_INVOKE(shutdown_post_sync, howto); > > > > if ((howto & (RB_HALT|RB_DUMP)) == RB_DUMP && !cold && > > !dumping) > > doadump(TRUE); > > > > /* Now that we're going to really halt the system... */ > > EVENTHANDLER_INVOKE(shutdown_final, howto); > > What I’ve seen is that the three different EVENTHANDLER_INVOKE() all > can cause a lot of calls that can take a long time. As can > bufshutdown(), probably when it calls vfs_unmountall() to unmount all > filesystems. > > We’re talking like 5-20 minutes (or more). I’ve not really timed it. > > I have a feeling it sometimes is due to transactions stored up in the > ZFS filesystems that the system tries to “run” so it doesn’t have to > do it at mount() time after the reboot. If I reset the machine while > it is busy doing this then sometimes the “zfs mount -a” takes very > long time at boot instead. > > Hmm.. I should be able to use the getnanouptime() call to get a > “clock” to look for (it’s used in print_uptime()). As long as the > clock isn’t stopped at this time in the shutdown sequence atleast :-) > > *Time to write some code and test this* :-) > If you want to throttle something to once a second (or some number of integer seconds) the kernel has a global variable named time_sec, (in sys/time.h), watch for it to change. -- Ian From owner-freebsd-current@freebsd.org Sat Nov 30 20:04:42 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 539741B5BC9 for ; Sat, 30 Nov 2019 20:04:42 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from MailHost (unknown [80.211.33.142]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47QMm96hLNz4QLX for ; Sat, 30 Nov 2019 20:04:41 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from root (uid 0) (envelope-from salvadore@FreeBSD.org) id 2773 by MailHost (DragonFly Mail Agent v0.11+); Sat, 30 Nov 2019 21:04:10 +0100 To: freebsd-current@FreeBSD.org Subject: Call for 2019Q4 quarterly status reports Date: Sat, 30 Nov 2019 21:04:10 +0100 Message-Id: <5de2cb3a.2773.38fdc211@MailHost> From: X-Rspamd-Queue-Id: 47QMm96hLNz4QLX X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.89 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.917,0]; ASN(0.00)[asn:31034, ipnet:80.211.0.0/17, country:IT]; NEURAL_HAM_LONG(-0.98)[-0.977,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Nov 2019 20:04:42 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 1, 2020, for work done since the last round of Quarterly Reports: October, 2019 - December, 2019. Starting with this quarter, reports will be collected during the last month of every quarter (instead of the first month of the next quarter, as was previously the case). Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarterly@FreeBSD.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2019Q4 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)