From nobody Mon Sep 6 05:50:21 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EE090179CF09 for ; Mon, 6 Sep 2021 05:50:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H2yDK5yH2z3qQH for ; Mon, 6 Sep 2021 05:50:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id N0YMmrmvGps7PN7WTmnXzP; Mon, 06 Sep 2021 05:50:25 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id N7WRmKCGHU9pxN7WSmJSJw; Mon, 06 Sep 2021 05:50:25 +0000 X-Authority-Analysis: v=2.4 cv=Bbi7bph2 c=1 sm=1 tr=0 ts=6135ac21 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=QCccru2TAAAA:8 a=JAf30KXuAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=iYvezse-Q5tlZEVPOWAA:9 a=CjuIK1q_8ugA:10 a=rCjsK_HQOcgUb9vb-KUg:22 a=GEL62FyrTCmHtEug2d3R:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 950CCB8; Sun, 5 Sep 2021 22:50:23 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 1865oLlJ013110; Sun, 5 Sep 2021 22:50:23 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109060550.1865oLlJ013110@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Oleg V. Nauman" cc: current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> Comments: In-reply-to "Oleg V. Nauman" message dated "Sun, 05 Sep 2021 19:43:52 +0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Sep 2021 22:50:21 -0700 X-CMAE-Envelope: MS4xfNDU3LEq8fbuiBVvfbjSfhxV7BfsHTiOa8rPNuDh8x1ozUCmhz9tSNwAOxka86UwQT9IS7R1u8uSHET+Jvr8d7LsWC6TB/ziEM2hKcDqVMASnV8D8ofL b/tjPG6G5zHZ/SpvWw1uS/3OFtK+hk79P+Lwd9F/CP+/3YWuza7TaZsBvd5TRc7lXaJxX54qJ8wIu4L0OkpnrhkfM3FQ+AqXka2fTzC+49uX9PUBagc5Pj6N X-Rspamd-Queue-Id: 4H2yDK5yH2z3qQH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > Sorry I hadn't noticed this yesterday (so I could have repported it > > then), but after updating the "head" slice of my laptopp from: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > to: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > the WLAN LED doesn't light up. > > I am also experiencing issues with wlan after my current update to > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > demonstrating the same behavior - wlan can not associate. > You can mitigate it by using security/wpa_supplicant from ports as replacemen > t > of wpa_supplicant in base. > > ..... > > > > I note that exactly the same hardware works OK in stable/12 and stable/13. > > > > Peace, > > david > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. > > From nobody Mon Sep 6 07:13:22 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D6B7C17A21E0 for ; Mon, 6 Sep 2021 07:13:25 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H30452TlMz4lGP for ; Mon, 6 Sep 2021 07:13:25 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x434.google.com with SMTP id d6so7613107wrc.11 for ; Mon, 06 Sep 2021 00:13:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=zUb7vlM/ZKQ2rdMgRkLE6DjVvDSonMPjUjPWPvwB8NU=; b=duPOvmxxfkk3xR23WRo8lWl3Sr/CI6JFQwcLXXWOrVeA+jwB3/vQjFPcfa2RQ08rSw V2OcCvZhJp37ath0iPxHynHdmeldyd4pe7wuklyCFFXkdL2VjIjoqSTm0ZjLij8O/RbO W2UrPFpJR+r35Y7caBg765k5VEFTG6jCz6hWStrnQn3SLBpVBf6qGnn8614ak10/f3Q0 n9YIzHtNDPWeCcRP521kRGDFAlNFfVnrwuT5s5aiKvguqQ6KusV2UNCWRjyYbESE3uH3 EA4/eqpLdl8nWMMBRhgBu+rSmqfwP9xbHuMuLB/vQGVlyvQqu8plXwsczrzk/+cqBuZN ZYEQ== 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=zUb7vlM/ZKQ2rdMgRkLE6DjVvDSonMPjUjPWPvwB8NU=; b=NhvNl5ta94vk9jM0nuVnBuHa60k6jUQvio7Nux71m6P9EFf2p+h4OjmfE9G051DUVr JYYovGu3JesWNFTKFnjLZ4mJhFf3E05kBw1hDg7z8MxoMC7uMesQ9RiCtWUACgLyKCGQ LdKQdXonw3ttMxYF5zVEHOtYHr40+ytQLlqGEyit+XTFQLh4EZrMJPAsHgVqRd/9RA8v ftM6AWy+4O0uM3hgb+HJ2n1SmD39ojOLLugAwYorndVmYxAlMd+RZIgtWXJxULdnpUv4 2WJczGzComSF7MgE//7ULXlcSXQTPyWu1qx3WcTGP7X/eMi/6sPARqLcliR6hIFB40Z5 jhog== X-Gm-Message-State: AOAM5322M/r83aQjc3qfV/PEwchlwwcS/yGc9NYPPiBialabuFK3hj1y D3HH8L4bpus5Y9qIiMfzaWOKJ/AAsFG8MQ== X-Google-Smtp-Source: ABdhPJxkjtBNI8Sa1O194mKcgS1Bcbhrg6+3tfYrxRDd1y4Qdt8OIqT5sZ9xL7IolbZUv8zrypEZ6A== X-Received: by 2002:adf:ed0c:: with SMTP id a12mr11670354wro.102.1630912403624; Mon, 06 Sep 2021 00:13:23 -0700 (PDT) Received: from ?IPv6:2001:470:1f1c:a0::2? (tunnel642390-pt.tunnel.tserv1.lon2.ipv6.he.net. [2001:470:1f1c:a0::2]) by smtp.gmail.com with ESMTPSA id m12sm6912383wrq.29.2021.09.06.00.13.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 00:13:23 -0700 (PDT) Subject: wlan0 functional for me with n249159-bb61ccd530b (was: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0) To: freebsd-current@freebsd.org References: From: Graham Perrin Message-ID: <0fec63a1-8150-0393-9d07-2cd8658f3656@gmail.com> Date: Mon, 6 Sep 2021 08:13:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 4H30452TlMz4lGP X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=duPOvmxx; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::434 as permitted sender) smtp.mailfrom=grahamperrin@gmail.com X-Spamd-Result: default: False [-3.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; 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]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::434:from]; NEURAL_HAM_SHORT(-0.71)[-0.711]; 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_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On 05/09/2021 14:36, David Wolfskill wrote: > a reality check would almost certainly be helpful. :-) No problem here; . n248984-08b9cc316a3 (2021-08-28) upgraded to n249159-bb61ccd530b (2021-09-05), Functional ☑ but (an old bug) wrongly connected to an open network when I manually bring up wlan0: > 256957 – Wi-Fi: rc.conf(5) NOAUTO, ifconfig(8) up and unwanted WLAN connections to open networks ---- Below, ignore the dates of creation (most are false): root@mowa219-gjp4-8570p-freebsd:~ # bectl list BE                    Active Mountpoint Space Created default               -      -          789M  2021-08-26 16:33 n247565-b49ba74deeb-f -      -          36.7G 2021-08-26 19:50 n247798-f39dd6a9784-a -      -          22.9M 2021-08-26 22:54 n247798-f39dd6a9784-e -      -          328M  2021-08-26 22:55 n247798-f39dd6a9784-j -      -          4.98G 2021-08-26 22:55 n248139-3a57f08b504-b -      -          1.21G 2021-08-26 22:54 n248269-941650aae97-b -      -          524M  2021-08-26 22:54 n248269-941650aae97-d -      -          260M  2021-08-26 22:55 n248269-941650aae97-e -      -          40.5M 2021-08-26 22:54 n248269-941650aae97-f -      -          5.02G 2021-08-26 22:54 n248984-08b9cc316a3-d -      -          997M  2021-09-03 08:00 n249159-bb61ccd530b-a NR     /          46.9G 2021-09-06 00:24 root@mowa219-gjp4-8570p-freebsd:~ # From nobody Mon Sep 6 08:08:30 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8A59A17BB956 for ; Mon, 6 Sep 2021 08:08:48 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: from mail-io1-f46.google.com (mail-io1-f46.google.com [209.85.166.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H31Hz3T0Zz3Jgh for ; Mon, 6 Sep 2021 08:08:47 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-io1-f46.google.com with SMTP id e186so7620554iof.12 for ; Mon, 06 Sep 2021 01:08:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ChAvvNFVIu3+5PyteIa4O3XfsWoiYLgooAIRQxrF1y4=; b=VyfDNcKtAkGvIfmCJo7djidLnhyVG7ymxSJl6apPPqjMsZuJiF+kdRtXmICCD0eWAd Akmwev0gSRmhyPzjaBigjAiXvflvF8TBd0c6RpHKI4O1UN6lmvbNs+4lx+Ref59/junS 74ox6lRcPLbRnm3RWN7IieGwo0zkuZwgITuTuiVIeAV0v7fNB4tptKjdYsxvn7xSQ0I5 kIPq5HHXQzhrfD67DrWlBRwW33USGMYKK9KBcNlIF7p/Pyo/efJLqAO5eFTlbw4bP2N5 0OlTDe4WhhVeIM8Lm/5t/WiDUe6heB3tX+LNoZ1XZPXQF3xPlV3ICJO7ETaw16wc5u4O Es6w== X-Gm-Message-State: AOAM531VQ+LEOIq/kIzpKpdPAfIRkpMWw5eqEniO5Q0NZ7XTL97kLSb6 PT2XIJ5qgQ0ZWmVVhV0R5s/YPHNMCsXN30x3wdjJLGPE6EWT/A== X-Google-Smtp-Source: ABdhPJzVpq+LmWmgRr/QWeVG/1n4956pNUXdTRfaQqE+s62kBXpkmTLf9BpDK6miyznsGcfYCs3dacqP/9AdkFHg1ds= X-Received: by 2002:a6b:7a03:: with SMTP id h3mr8656611iom.39.1630915721099; Mon, 06 Sep 2021 01:08:41 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Jeremie Le Hen Date: Mon, 6 Sep 2021 10:08:30 +0200 Message-ID: Subject: -CURRENT compilation time To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H31Hz3T0Zz3Jgh X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jlehen@gmail.com designates 209.85.166.46 as permitted sender) smtp.mailfrom=jlehen@gmail.com X-Spamd-Result: default: False [-2.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.995]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.46:from]; FORGED_SENDER(0.30)[jlh@freebsd.org,jlehen@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.46:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jlh@freebsd.org,jlehen@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hey, I want to build -CURRENT again from sources. It's been a long time since I hadn't done that. I'm shocked by the compilation time. I started the whole thing on Friday night and Monday morning it's still in stage 4.2 (building libraries). Through occasional glancing at the screen over the weekend, it seems obvious to me that the compilation time is utterly dominated by LLVM. Compiling C++ seems extremely CPU heavy and this is made worse by the fact LLVM is built twice (once for build/cross tools, once for the actual world). So OK, my CPU is not the most powerful out there but it's still decent [1]. So I have a couple of questions coming to my mind: 1. Is there any optimization I could benefit from? (I'm sure there's a knob to use the existing compiler instead of building a cross-compiler.) 2. More generally, isn't this compilation time not considered as a problem for developers? This seems to terribly slow down the iteration time for people working on the build system. I wouldn't be surprised if this drove people away from working on/improving that area. [1] https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-6260U+%40+1.80GHz&id=2671 Cheers, -- Jeremie Le Hen jlh@FreeBSD.org From nobody Mon Sep 6 08:16:14 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 826CD17993EE for ; Mon, 6 Sep 2021 08:16:31 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H31Sv2wR2z3PVk; Mon, 6 Sep 2021 08:16:31 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-il1-x136.google.com with SMTP id h29so6071572ila.2; Mon, 06 Sep 2021 01:16:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=89FHPpW/1QV75gd1dBU7ccAM+xU7ekZiMn3XaIYoPdc=; b=G9BMthXJfcmWFFRnSUTlaB/9uqttQH9+I6xRoqIOhzSYpzGe0ASXDbNEmgO+p0Xdm2 3WtQO1HBSCHwpshbsmx3q3XjGYxlLLtQayVg1Unei1LP7nnWtaIZNUX1ewnal5FIRIn7 2/QKcqx5gXuhU4MiU1WoTbR/b7GYxMqclMqZGIpGu8W235ar9PyR73mvnuA3oD2YG83C Mzg4NPKKJni9O1ZxZ/TW61lhSpr4zrjs1UXBgqVHwlk4mejwpLNx8k1b8Bhi1N7LzfjI FW8W3l6a7gulkawq/8xVDC2JAs1Uz9dmbb9/uMXe4FQZivEsyqYBxri4kp9tFAuEP+r7 wIXw== 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=89FHPpW/1QV75gd1dBU7ccAM+xU7ekZiMn3XaIYoPdc=; b=mPzcmxF4oUiDwlKJ5PvVXwhRnS74A941xBFJm2u6Mj3nS6ysTNd+oKqF41BgQrxK4J 6/EujQtBd3IYiAZXgwatcPlpyWkrRZ+AfIsrx1LxEZYFwqn+jvY4pt9h3xzgfCGKqaRd rRIgBHgbuPlT274EYS/eXd2Q9XngN36WaCyh4PNkPMgPw8AlmC7HIXkVttqaSzgj1TyQ BzXq++yKWT6EedTc9NXt5MT4Ggv4mxB2tUlSEREsEMwl8COVGtDWEaur3qKx30ELS6oq 1DEG5FCvSIoHlOBsVdIwS50vkFwN32AS+CEF0leo/Y0xQcFp8xlfFk29I2jTpgeujiGV HmSw== X-Gm-Message-State: AOAM532Zzsb3YgyuYygL0/ubNYuNKWe8gNZ+nHlUC+MVVl4vrB1gvzfa gG19XF5fLQJsyOoEC6ANqBuHzW6q1cIAYakKGV3kmY9V0bGuWQ== X-Google-Smtp-Source: ABdhPJwlgIB+u8e6io+IkbnqpLSv7rZmFpoz+x4OOvLurDoHhi6BKRLNlEfbdZlVLTGd5M4gBOdopStaa3WMsKloXJE= X-Received: by 2002:a92:c532:: with SMTP id m18mr4318591ili.63.1630916185117; Mon, 06 Sep 2021 01:16:25 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Michael Schuster Date: Mon, 6 Sep 2021 10:16:14 +0200 Message-ID: Subject: Re: -CURRENT compilation time To: Jeremie Le Hen Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000df582105cb4f4345" X-Rspamd-Queue-Id: 4H31Sv2wR2z3PVk X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --000000000000df582105cb4f4345 Content-Type: text/plain; charset="UTF-8" Jeremie, a few observations (from the POV of someone who builds current ~ once a month) On Mon, Sep 6, 2021 at 10:09 AM Jeremie Le Hen wrote: > Hey, > > I want to build -CURRENT again from sources. It's been a long time > since I hadn't done that. I'm shocked by the compilation time. > > I started the whole thing on Friday night and Monday morning it's > still in stage 4.2 (building libraries). Through occasional glancing > at the screen over the weekend, it seems obvious to me that the > compilation time is utterly dominated by LLVM. Do you actually measure anything? have you looked into what your I/O is doing? How about swap? Compiling C++ seems > extremely CPU heavy and this is made worse by the fact LLVM is built > twice (once for build/cross tools, once for the actual world). > > So OK, my CPU is not the most powerful out there but it's still decent [1]. > I didn't check the specs: how many cores does your box have, and how many are you actually using (-j N)? IME, htop gives a good idea of how busy the CPUs really are. > So I have a couple of questions coming to my mind: > 1. Is there any optimization I could benefit from? (I'm sure there's a > knob to use the existing compiler instead of building a > cross-compiler.) > look at the build man page (https://www.freebsd.org/cgi/man.cgi?build(7)) for some tips on how to configure your environment. 2. More generally, isn't this compilation time not considered as a > problem for developers? This seems to terribly slow down the iteration > time for people working on the build system. I wouldn't be surprised > if this drove people away from working on/improving that area. > > [1] > https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-6260U+%40+1.80GHz&id=2671 > > Cheers, > -- > Jeremie Le Hen > jlh@FreeBSD.org > > regards Michael -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion' --000000000000df582105cb4f4345-- From nobody Mon Sep 6 08:47:19 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 73DEB17AA9A4 for ; Mon, 6 Sep 2021 08:47:29 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H328d2LH6z3qgb; Mon, 6 Sep 2021 08:47:29 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4H328V3rkpz6gN7; Mon, 6 Sep 2021 10:47:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:date:date:message-id:from:from :references:subject:subject:received; s=bjowvop61wgh; t= 1630918040; x=1632732441; bh=bF6FfWx4mKZrRJlCXMrgPI7cCWPANDIiJ5X /QOMyYoY=; b=NiKWmQB1KiG80jJ5JdWNmgmb3/QhGgo1VP9nbA98JAbWyMcTUKN Sn6j5NHMTTz371ckS0vg3CxTU3rqtQ5A99bNdPZbaF6ppdRn/n9mL1gFvKMh2HvZ mXM5bvU9y0wFqkX9Bt4oYRBalDEZZ37sFMEaOZR/N1f9vSWgR0yMF7kb9PRrd9nI 2lkLGtCgYB3lAbCg/2Q7RjmIedDV0T8crHOXKTyXUYoeKQuSJoJqGIftykeW364M xMuaatUSTMonAguNPEQP/IF91/vh+g99tHnZno8idfwpPCskHd0yVTw+JKKL2juI 9AaxrOQ/HYMvEDzREzlFXjPrf/W2wU1wlGg== Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id NHRU_h-wbvqG; Mon, 6 Sep 2021 10:47:20 +0200 (CEST) Subject: Re: -CURRENT compilation time To: Jeremie Le Hen , FreeBSD Current References: Message-ID: Date: Mon, 6 Sep 2021 10:47:19 +0200 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H328d2LH6z3qgb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: mad@madpilot.net From: Guido Falsi via freebsd-current X-Original-From: Guido Falsi X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org On 06/09/21 10:08, Jeremie Le Hen wrote: > Hey, > > I want to build -CURRENT again from sources. It's been a long time > since I hadn't done that. I'm shocked by the compilation time. > > I started the whole thing on Friday night and Monday morning it's > still in stage 4.2 (building libraries). Through occasional glancing > at the screen over the weekend, it seems obvious to me that the > compilation time is utterly dominated by LLVM. Compiling C++ seems > extremely CPU heavy and this is made worse by the fact LLVM is built > twice (once for build/cross tools, once for the actual world). > > So OK, my CPU is not the most powerful out there but it's still decent [1]. > > So I have a couple of questions coming to my mind: > 1. Is there any optimization I could benefit from? (I'm sure there's a > knob to use the existing compiler instead of building a > cross-compiler.) I'm routinely compiling head once a month or so on an "i7-6700 CPU @ 3.40GHz" (from dmesg), slightly more powerful than an i5 but this is a relatively old one so not top notch anymore. It usually takes less than 4 hours. I also build a NanoBSD image from scratch from time to time to an even older i5, which takes a little longer, but always under 6 hours, so the build times you report look anomalous. So as already suggested make sure yiu are using parallel make jobs (-j option to make) and memory is large enough (I think you need at least 2 GiB for make job is the minimum to not risk thrashing. You should really enable meta mode (look for WITH_META_MODE in src.conf(5)). It will not help the first time but will help a lot in future recompilations with an already populated /usr/obj. You could also investigate using ccache, which again will only help for successive rebuilds, and will consume a fair amount of disk space. Another consideration, my builds are happening on SSD disks, with swap on SSD, if you have everything on spinning media that is also a slowing factor. If you have plenty of ram you could build in ram, which is what I'm doing with poudriere for ports and it really speeds things up (even SSD disks tend to get slower when hit with a constant high load of mixed read/write accesses, which poudriere with parallel builds sometime causes) Hope this helps! -- Guido Falsi From nobody Mon Sep 6 09:43:06 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0AFB7179C72E for ; Mon, 6 Sep 2021 09:43:13 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H33Nw6w4yz4fNt for ; Mon, 6 Sep 2021 09:43:12 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id CCABE20C22 for ; Mon, 6 Sep 2021 09:43:12 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 8C9AE2C8F0 for ; Mon, 6 Sep 2021 10:43:11 +0100 (BST) Subject: Re: -CURRENT compilation time To: freebsd-current@freebsd.org References: From: David Chisnall Message-ID: Date: Mon, 6 Sep 2021 10:43:06 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 06/09/2021 09:08, Jeremie Le Hen wrote: > Compiling C++ seems > extremely CPU heavy and this is made worse by the fact LLVM is built > twice (once for build/cross tools, once for the actual world). Note that you need to build LLVM twice only if you are actively debugging LLVM reproduceable deployment images. You actually don't need to build it at all, you can use an external toolchain to skip the first build and you can compile WITHOUT_TOOLCHAIN to avoid building the version that's installed and then install a toolchain from packages: https://wiki.freebsd.org/ExternalToolchain David From nobody Mon Sep 6 09:57:49 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A3E3417A555E for ; Mon, 6 Sep 2021 09:57:58 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 4H33jy3j9yz4mJQ; Mon, 6 Sep 2021 09:57:58 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1mNBNu-0005Uz-0C; Mon, 06 Sep 2021 11:57:50 +0200 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1mNBNt-0000um-VP; Mon, 06 Sep 2021 11:57:49 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: from [Authenticated alias (650894)] by runbox.com with http (RMM6); Mon, 06 Sep 2021 09:57:49 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "David Chisnall" CC: "freebsd-current" Subject: Re: -CURRENT compilation time Date: Mon, 06 Sep 2021 02:57:49 -0700 (PDT) X-RMM-Aliasid: 650894 X-Mailer: RMM6 In-Reply-To: Message-Id: X-Rspamd-Queue-Id: 4H33jy3j9yz4mJQ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, 6 Sep 2021 10:43:06 +0100, David Chisnall wr= ote: > On 06/09/2021 09:08, Jeremie Le Hen wrote: > > Compiling C++ seems > > extremely CPU heavy and this is made worse by the fact LLVM is built > > twice (once for build/cross tools, once for the actual world). >=20 > Note that you need to build LLVM twice only if you are actively=20 > debugging LLVM reproduceable deployment images. You actually don't need= =20 > to build it at all, you can use an external toolchain to skip the first=20 > build and you can compile WITHOUT_TOOLCHAIN to avoid building the=20 > version that's installed and then install a toolchain from packages: >=20 > https://wiki.freebsd.org/ExternalToolchain >=20 > David If only that suggestion was topmost in UPDATING and repeated in each security advisory...=20= From nobody Mon Sep 6 10:14:20 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4D88717AF200 for ; Mon, 6 Sep 2021 10:14:33 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H34551kBHz4tNP; Mon, 6 Sep 2021 10:14:33 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: by mail-lf1-f43.google.com with SMTP id s10so12518866lfr.11; Mon, 06 Sep 2021 03:14:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qq+BqNvYqWxJD9pY9HdLm0AIb+hMCFxPdB80G72FUzQ=; b=t1uI0N8jvQhV5ST0B3HoWmd4REgz01X4AC+WYc4+7xullbthoDp88qOAl/GSN0LgmT PjHg+ixGOEe7rHjui3xPZbD6N8YTjxtr35fvRoWWLJ4Hv2r0DN3m42kTY/6GiYxVuGKc s3+3omoJLtrOgkdPh9DuQwk2pl7MC/NH6Iu+GhyeW5kiQESexuui9lIc2XaSL//FuBLe dzt+Zg1N80WyjvpmRtQtQxO7HXwgsUBsdKbryKLeIIM6IQkkM9Y0aS8Qaeebvb+pS4ES nSZVZrpLuSYv027CuZDQa08hR9xd5XAEXstKSYQ7GEbMWGJMl+uJ9A4TEvDRqlyr669C J2Sg== X-Gm-Message-State: AOAM531sbAgidf1iJgPtndLt5TBONVstCFdUAv2uJOH8pJqug5tdgk7I VRD7I+3qHBSrfAf8exXUYaGFNxuHy+cWH1KV+i5k/U9utOo= X-Google-Smtp-Source: ABdhPJxNXXLzP2qk/f0hhAX+kG952AgnxqR+v0PYQKYUggpIZAqMr64QCeWqoawJ7XQ7AfbIcbAdHtseH2ajMW0oC5U= X-Received: by 2002:ac2:4e98:: with SMTP id o24mr8933852lfr.295.1630923271361; Mon, 06 Sep 2021 03:14:31 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Wolfram Schneider Date: Mon, 6 Sep 2021 12:14:20 +0200 Message-ID: Subject: Re: -CURRENT compilation time To: Jeremie Le Hen Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H34551kBHz4tNP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, 6 Sept 2021 at 10:10, Jeremie Le Hen wrote: > > Hey, > > I want to build -CURRENT again from sources. It's been a long time > since I hadn't done that. I'm shocked by the compilation time. > > I started the whole thing on Friday night and Monday morning it's > still in stage 4.2 (building libraries). Through occasional glancing > at the screen over the weekend, it seems obvious to me that the > compilation time is utterly dominated by LLVM. Compiling C++ seems > extremely CPU heavy and this is made worse by the fact LLVM is built > twice (once for build/cross tools, once for the actual world). > > So OK, my CPU is not the most powerful out there but it's still decent [1]. > > So I have a couple of questions coming to my mind: > 1. Is there any optimization I could benefit from? (I'm sure there's a > knob to use the existing compiler instead of building a > cross-compiler.) > 2. More generally, isn't this compilation time not considered as a > problem for developers? This seems to terribly slow down the iteration > time for people working on the build system. I wouldn't be surprised > if this drove people away from working on/improving that area. > > [1] https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-6260U+%40+1.80GHz&id=2671 Hi, I ran buildworld yesterday on a 3 CPU VM (AMD EPYC 2.4GHz) and the runtime was 2h. We spent most of the time in "stage 4.2: building libraries", in my case 62% of the CPU time and 75% of the real time. I guess the build time on your laptop should be around 6 hours if everything is ok. time make -j $(sysctl -n hw.ncpu) buildworld > log.buildworld 2>&1 tail -n 5 log.buildworld -------------------------------------------------------------- >>> World build completed on Sat Sep 4 20:58:00 UTC 2021 >>> World built in 7235 seconds, ncpu: 3, make -j3 -------------------------------------------------------------- 7235.61 real 20527.30 user 915.88 sys egrep '>>> stage| real ' log.buildworld >>> stage 1.1: legacy release compatibility shims 0.28 real 0.18 user 0.10 sys >>> stage 1.2: bootstrap tools 165.99 real 472.58 user 11.56 sys >>> stage 2.1: cleaning up the object tree 21.47 real 36.96 user 14.14 sys 15.87 real 29.14 user 11.87 sys >>> stage 2.3: build tools 2.42 real 3.79 user 0.62 sys >>> stage 3: cross tools 9.92 real 18.49 user 1.75 sys >>> stage 3.1: recording build metadata 0.07 real 0.01 user 0.06 sys >>> stage 4.1: building includes 16.62 real 36.46 user 9.48 sys >>> stage 4.2: building libraries 5440.89 real 15724.60 user 482.58 sys >>> stage 4.3: building lib32 shim libraries 615.91 real 1654.77 user 164.58 sys >>> stage 4.4: building everything 937.23 real 2540.06 user 205.47 sys -Wolfram -- Wolfram Schneider https://wolfram.schneider.org From nobody Mon Sep 6 11:44:09 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 50C2C17BAA7B for ; Mon, 6 Sep 2021 11:44:22 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H364j4lybz3v1l for ; Mon, 6 Sep 2021 11:44:21 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: by mail-ej1-x632.google.com with SMTP id i21so12983196ejd.2 for ; Mon, 06 Sep 2021 04:44:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kaguV57komlvcZtGFpL5qwVIPMFL1PX9KRjNsN0sA5w=; b=YhcmcCYhSOOQkpfSLn0h2LWcy5ABfoBWV+SmjPvYtIIufNdCN1XoIpKHUtCVNRrI97 i1j6DCT+Lhy1o/ZnQRQ/DsTQ2tzZB6qUH65tcOuOS2KKTeE7DxXLm4jpfy+z/dOxZQ1d RhMReITHj3dVcaKcNyrK8QSqUQ+RbTq9ohs26Ez/LSH/AT0OlmdR/4JSeHZTiKM7SU9/ qawuJNwcG0OhqR0n8S932WfLgU8toLjDFTlddD7uvuXqWKNmFiY+s5xsqz7LgkQT/imW kEaGNH3TAzVdWHaK8mN0ktqsuVlT6pVlEUsKUisVtlZsamQ8YEertjGvFr9A3eamTfz/ GxUA== 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=kaguV57komlvcZtGFpL5qwVIPMFL1PX9KRjNsN0sA5w=; b=jmXGyDr3vCTMD6YmIMqrSTlfruJuZbjn++1sJF7S99HfrgDqFVxesj8PNNV/24LMfy zdWdAm5jFqMV1TpIy0lAYESXpmKvVtuPWCRNmtbAzXZT5/+fOTqVSdiYwVuIjvvZmyT+ Pp9PueR5bs1EFRU4f7A1tQ7EzHhmKYT1KuCrCh6wSXOqbnhzz7pALXNNI0dbyFsytrMQ afNg9zKx61sSUSDluLx+h9N20/ySHMmJgxzjdU6Uq61JM12l3Nj6S6bPJs0pV9Oh3CXE XxmAe5LHxKbvkCRj9wB/xbpECc2RMKwMBAbm5YyS/5LZGS9r4os9VYZhzDtUKycVAOM6 L5kA== X-Gm-Message-State: AOAM531sCJ50vLGH2jKegmVMDvMDzuUg5kaao5idzpFFpplwI6nomHIv W31ALvBbFttOYKlpghREIzYa7shHdcE5RXKqai+dokXp+ho= X-Google-Smtp-Source: ABdhPJxjxl6pXIsp4Ry9LqJMk0/XRtba86hiCmKlBKs/b/Pa0aGEXAsJ2f/temQChimneDYAhkyGTl2DvNtT6OlsRHI= X-Received: by 2002:a17:906:3181:: with SMTP id 1mr12858962ejy.388.1630928660760; Mon, 06 Sep 2021 04:44:20 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> In-Reply-To: <202109060550.1865oLlJ013110@slippy.cwsent.com> From: Idwer Vollering Date: Mon, 6 Sep 2021 13:44:09 +0200 Message-ID: Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 To: Cy Schubert Cc: "Oleg V. Nauman" , current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H364j4lybz3v1l X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=YhcmcCYh; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of vidwer@gmail.com designates 2a00:1450:4864:20::632 as permitted sender) smtp.mailfrom=vidwer@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::632:from]; NEURAL_HAM_SHORT(-1.00)[-0.999]; 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:dkim] X-ThisMailContainsUnwantedMimeParts: N Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > writes: > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > then), but after updating the "head" slice of my laptopp from: > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > amd64 1400032 1400032 > > > > > > to: > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > amd64 1400032 1400032 > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > > the WLAN LED doesn't light up. > > > > I am also experiencing issues with wlan after my current update to > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > demonstrating the same behavior - wlan can not associate. > > You can mitigate it by using security/wpa_supplicant from ports as replacemen > > t > > of wpa_supplicant in base. > > > > ..... > > > > > > I note that exactly the same hardware works OK in stable/12 and stable/13. > > > > > > Peace, > > > david > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. wpa_supplicant stops in wpa_driver_bsd_scan() - https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948f94b86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 Here's some selected output from /var/log/messages. Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): Sep 6 13:29:40 wpa_supplicant[45348]: Successfully initialized wpa_supplicant Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument Sep 6 13:29:40 syslogd: last message repeated 1 times Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to associate with (SSID='' freq=2447 MHz) Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add supported operating classes IE Sep 6 13:29:46 kernel: wlan1: link state changed to UP Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer space available Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key negotiation completed with [PTK=CCMP GTK=CCMP] Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] After (built from main): Sep 6 12:19:50 wpa_supplicant[1236]: Successfully initialized wpa_supplicant Sep 6 12:19:50 kernel: wlan1: Ethernet address: Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument Sep 6 12:19:50 syslogd: last message repeated 1 times Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web: https://nwtime.org > > The need of the many outweighs the greed of the few. > > > > > > > > > From nobody Mon Sep 6 13:23:21 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0EBD317BE0CF for ; Mon, 6 Sep 2021 13:23:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H38H06Wrbz4sd6 for ; Mon, 6 Sep 2021 13:23:24 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4003a.ext.cloudfilter.net ([10.228.9.183]) by cmsmtp with ESMTP id MyWImriKBps7PNEaqmny2e; Mon, 06 Sep 2021 13:23:24 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NEaomWJvUcHSBNEapmKoJ6; Mon, 06 Sep 2021 13:23:24 +0000 X-Authority-Analysis: v=2.4 cv=I4EG+Psg c=1 sm=1 tr=0 ts=6136164c a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=QCccru2TAAAA:8 a=JAf30KXuAAAA:8 a=s1G7sxBSAAAA:20 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=wtw-BJkFRuQ0aqCkN2gA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=rCjsK_HQOcgUb9vb-KUg:22 a=GEL62FyrTCmHtEug2d3R:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 5CC2C354; Mon, 6 Sep 2021 06:23:21 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186DNLMQ010404; Mon, 6 Sep 2021 06:23:21 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061323.186DNLMQ010404@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Idwer Vollering cc: Cy Schubert , "Oleg V. Nauman" , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> Comments: In-reply-to Idwer Vollering message dated "Mon, 06 Sep 2021 13:44:09 +0200." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 06:23:21 -0700 X-CMAE-Envelope: MS4xfI3doK4c7VZ+Ko+qoXvj0tWMRfldGBTOUdticfvVoJtgxBMUzmdFGzadWgJqg2Mabrl3olAzdQh+fzNEkOr9e3bAQLWDbzu4psB0iRLwoES6wNYk0VW0 FMOMitlgs7tj9UogocP7iSQTh9UHDMPB6kqCiqAjEV9b9fxHmuPYjzpoHGEVIh35npWsNoOzEf93WBwJvtZgGaZfzaLGWeq/22gf7QLuhvVqmlvpPlimJdtH SU7eh1KfC7yiaSSbuN54Ag== X-Rspamd-Queue-Id: 4H38H06Wrbz4sd6 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message , Idwer Vollering writes: > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > writes: > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > > then), but after updating the "head" slice of my laptopp from: > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > amd64 1400032 1400032 > > > > > > > > to: > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > amd64 1400032 1400032 > > > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > > > the WLAN LED doesn't light up. > > > > > > I am also experiencing issues with wlan after my current update to > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > > demonstrating the same behavior - wlan can not associate. > > > You can mitigate it by using security/wpa_supplicant from ports as replac > emen > > > t > > > of wpa_supplicant in base. > > > > > > ..... > > > > > > > > I note that exactly the same hardware works OK in stable/12 and stable/ > 13. > > > > > > > > Peace, > > > > david > > > > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. > > wpa_supplicant stops in wpa_driver_bsd_scan() - > https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948f94b > 86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 > > Here's some selected output from /var/log/messages. > > Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): > > Sep 6 13:29:40 wpa_supplicant[45348]: Successfully > initialized wpa_supplicant > Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, > op=20, val=0, arg_len=7]: Invalid argument > Sep 6 13:29:40 syslogd: last message repeated 1 times > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to > associate with (SSID='' freq=2447 MHz) > Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add > supported operating classes IE > Sep 6 13:29:46 kernel: wlan1: link state changed to UP > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with > > Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer > space available > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key > negotiation completed with [PTK=CCMP GTK=CCMP] > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: > CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] > > After (built from main): > > Sep 6 12:19:50 wpa_supplicant[1236]: Successfully > initialized wpa_supplicant > Sep 6 12:19:50 kernel: wlan1: Ethernet address: > Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, > op=20, val=0, arg_len=7]: Invalid argument > Sep 6 12:19:50 syslogd: last message repeated 1 times > Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: > CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 Is there a wpa_supplicant.core dump in / ? Can you also send me a sanitized copy of wpa_supplicant.conf, please? I'm interested in the lines proto=, key_mgmt=, pairwise=, group=, eap=, and phase2=. You may not be using eap= or phase2=, which is fine. I'd like to see if there are any differences from what was tested. Though, looking at your outputs above you're probably using something like: proto=RSN WPA key_mgmt=WPA-PSK pairwise=CCMP group=CCMP Is this correct? If you try ports/securitiy/wpa_supplicant-devel (same codebase as in 14-CURRENT), does it work? (ports/security/wpa_supplicant is the old 2.9 codebase.) What is your AP set for? 802.11g, 802.11n, 802.11ac? -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. From nobody Mon Sep 6 14:50:18 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B895217A6A7B for ; Mon, 6 Sep 2021 14:50:31 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3BCV4brXz3rKd for ; Mon, 6 Sep 2021 14:50:30 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: by mail-ej1-x636.google.com with SMTP id bt14so14010275ejb.3 for ; Mon, 06 Sep 2021 07:50:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+vM9EpVcRTrw02BNPVOaEM5Fyt8xp7GTwcoG+c2CFuE=; b=aIwhpHqNp1dFC31rCzcesHhbT3MpY59JsmAUCGrP27sKxudQooPlEGGiSeUTLJPxVm SIf7mxkcxocrbWYtBZBiHQDaMqEucEDHLvgdWa0KmnhXvbZ+EHYYo+n82JE9TfwTGgwu baP9qmBGOXB4EsBL18YW7m3B1CGZcmVXHWQz5IvDCyS3uHQ+ryIWMupzF0NBC3Zq2aUW ENrBgCcyg8adp1xKtq3MJ2NcRR3cKwS0jVlndEiV7fOtwWE+t/L6HIE9hU6cqG8fvhDJ GZuAbJHpL4JKgPtVAKBN8YQXAWLBiUz9nOchOXb1KCQEoxdU+IomVAhn+DMVc+WWlBB1 NHmw== 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=+vM9EpVcRTrw02BNPVOaEM5Fyt8xp7GTwcoG+c2CFuE=; b=RUGL+sF9Ud1/v2EXiElQQD3kJasGfegtaPE3OJub51qJwQj8R/X6KIdyvuW/2CIvZE B81Z3OzdsDoUkRz00dP8efQKGev8+xQCyzFGOyNPYLAjt136miC1614usHfjH4khhyM5 lfK5KgmXYhh1qt6F9gas3Sv9NvfEmbm09txX8fO/O6aS2SM/6pTAnB52uBMnIE3qlzNj JcEgFap1ivqbS4nBl2RcIGENyFFFTdGLKdVl7K0XUDQ7IRJb/x9I20r9yhoh8pRhYyem pCNBhQ12ZlcTfCSQ2wL5zvHO2Iu1T8YzY6qPctYPUE2MSHieb2D1I1pzUOOG0QqjlnK8 Ui+Q== X-Gm-Message-State: AOAM531qUvfk31kDBUJgYo3Htr2ckd/Rhl/iRSe3YLVBGsJowR0Pd7qp JBh0yW+0uIDiYaqx0jZ74h2G4PndLLTEQUrZvy0= X-Google-Smtp-Source: ABdhPJy3o3d/vYMkKS3idaZ1qVulIkGU8IgR/rD7cKpeEPDIeN/j2+nTmUniNNLzhLwt0yjE3pFyD5dYWbBFw+LxLkA= X-Received: by 2002:a17:906:3157:: with SMTP id e23mr14266704eje.29.1630939829544; Mon, 06 Sep 2021 07:50:29 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> <202109061323.186DNLMQ010404@slippy.cwsent.com> In-Reply-To: <202109061323.186DNLMQ010404@slippy.cwsent.com> From: Idwer Vollering Date: Mon, 6 Sep 2021 16:50:18 +0200 Message-ID: Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 To: Cy Schubert Cc: "Oleg V. Nauman" , current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H3BCV4brXz3rKd X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=aIwhpHqN; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of vidwer@gmail.com designates 2a00:1450:4864:20::636 as permitted sender) smtp.mailfrom=vidwer@gmail.com X-Spamd-Result: default: False [-3.98 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::636:from]; NEURAL_HAM_SHORT(-0.98)[-0.981]; 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:dkim] X-ThisMailContainsUnwantedMimeParts: N There's no core dump in /, wpa_supplicant connects to 802.11b/g/n (there's no way to lock this, instead of having a mix of standards) on 2,4GHz. /etc/wpa_supplicant.conf: network={ ssid="some ssid" scan_ssid=1 key_mgmt=WPA-PSK psk="some key" } Op ma 6 sep. 2021 om 15:23 schreef Cy Schubert : > > In message om> > , Idwer Vollering writes: > > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > > > > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > > writes: > > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > > > then), but after updating the "head" slice of my laptopp from: > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > > amd64 1400032 1400032 > > > > > > > > > > to: > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > > > amd64 1400032 1400032 > > > > > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > > > > the WLAN LED doesn't light up. > > > > > > > > I am also experiencing issues with wlan after my current update to > > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > > > demonstrating the same behavior - wlan can not associate. > > > > You can mitigate it by using security/wpa_supplicant from ports as replac > > emen > > > > t > > > > of wpa_supplicant in base. > > > > > > > > ..... > > > > > > > > > > I note that exactly the same hardware works OK in stable/12 and stable/ > > 13. > > > > > > > > > > Peace, > > > > > david > > > > > > > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. > > > > wpa_supplicant stops in wpa_driver_bsd_scan() - > > https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948f94b > > 86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 > > > > Here's some selected output from /var/log/messages. > > > > Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): > > > > Sep 6 13:29:40 wpa_supplicant[45348]: Successfully > > initialized wpa_supplicant > > Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, > > op=20, val=0, arg_len=7]: Invalid argument > > Sep 6 13:29:40 syslogd: last message repeated 1 times > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to > > associate with (SSID='' freq=2447 MHz) > > Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add > > supported operating classes IE > > Sep 6 13:29:46 kernel: wlan1: link state changed to UP > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with > > > > Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer > > space available > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key > > negotiation completed with [PTK=CCMP GTK=CCMP] > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: > > CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] > > > > After (built from main): > > > > Sep 6 12:19:50 wpa_supplicant[1236]: Successfully > > initialized wpa_supplicant > > Sep 6 12:19:50 kernel: wlan1: Ethernet address: > > Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, > > op=20, val=0, arg_len=7]: Invalid argument > > Sep 6 12:19:50 syslogd: last message repeated 1 times > > Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: > > CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 > > Is there a wpa_supplicant.core dump in / ? > > Can you also send me a sanitized copy of wpa_supplicant.conf, please? I'm > interested in the lines proto=, key_mgmt=, pairwise=, group=, eap=, and > phase2=. You may not be using eap= or phase2=, which is fine. I'd like to > see if there are any differences from what was tested. Though, looking at > your outputs above you're probably using something like: > > proto=RSN WPA > key_mgmt=WPA-PSK > pairwise=CCMP > group=CCMP > > Is this correct? > > If you try ports/securitiy/wpa_supplicant-devel (same codebase as in > 14-CURRENT), does it work? (ports/security/wpa_supplicant is the old 2.9 > codebase.) > > What is your AP set for? 802.11g, 802.11n, 802.11ac? > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web: https://nwtime.org > > The need of the many outweighs the greed of the few. > > From nobody Mon Sep 6 15:28:36 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D109617BA4A3 for ; Mon, 6 Sep 2021 15:28:45 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3C3c3cdHz4ZQn for ; Mon, 6 Sep 2021 15:28:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 186FSaoG086644 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 6 Sep 2021 08:28:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 186FSaBp086643 for freebsd-current@freebsd.org; Mon, 6 Sep 2021 08:28:36 -0700 (PDT) (envelope-from sgk) Date: Mon, 6 Sep 2021 08:28:36 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: BUG in libm's powf Message-ID: <20210906152836.GA86615@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4H3C3c3cdHz4ZQn X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.36 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; 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_SPAM_SHORT(0.64)[0.643]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N Paul Zimmermann has identified a bug in Openlibm's powf(), which is identical to FreeBSD's libm. Both derived from fdlibm. https://github.com/JuliaMath/openlibm/issues/212. Consider % cat h.c #include #include int main(void) { float x, y, z; x = 0x1.ffffecp-1F; y = -0x1.000002p+27F; z = 0x1.557a86p115F; printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); return 0; } % cc -o h -fno-builtin h.c -lm && ./h 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 Note, clang seems to have a builtin for powf(), but one cannot count of clang being the only consumer of libm. With the patch at the end of this email, I get % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun -lmath && ./h 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be 5.540807e+34 Watch for copy and paste whitespace corruption. --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 03:29:00.956878000 -0800 +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 @@ -136,7 +136,7 @@ /* |y| is huge */ if(iy>0x4d000000) { /* if |y| > 2**27 */ /* over/underflow if x is not close to one */ - if(ix<0x3f7ffff7) return (hy<0)? sn*huge*huge:sn*tiny*tiny; + if(ix<0x3f7ffff6) return (hy<0)? sn*huge*huge:sn*tiny*tiny; if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; /* now |1-x| is tiny <= 2**-20, suffice to compute log(x) by x-x^2/2+x^3/3-x^4/4 */ -- Steve From nobody Mon Sep 6 15:41:13 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4273E17C0B69 for ; Mon, 6 Sep 2021 15:41:17 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H3CL50ctFz4g92 for ; Mon, 6 Sep 2021 15:41:17 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4002a.ext.cloudfilter.net ([10.228.9.250]) by cmsmtp with ESMTP id NDc6ms7egps7PNGkGmoMlI; Mon, 06 Sep 2021 15:41:16 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NGkEmjUS0xCNkNGkFmKbNy; Mon, 06 Sep 2021 15:41:16 +0000 X-Authority-Analysis: v=2.4 cv=Xe/qcK15 c=1 sm=1 tr=0 ts=6136369c a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=QCccru2TAAAA:8 a=JAf30KXuAAAA:8 a=s1G7sxBSAAAA:20 a=QyJNKcYFpOw-pVCj0cAA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 a=rCjsK_HQOcgUb9vb-KUg:22 a=GEL62FyrTCmHtEug2d3R:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A44C442C; Mon, 6 Sep 2021 08:41:13 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186FfDRR024955; Mon, 6 Sep 2021 08:41:13 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061541.186FfDRR024955@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Idwer Vollering cc: Cy Schubert , "Oleg V. Nauman" , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> <202109061323.186DNLMQ010404@slippy.cwsent.com> Comments: In-reply-to Idwer Vollering message dated "Mon, 06 Sep 2021 16:50:18 +0200." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 08:41:13 -0700 X-CMAE-Envelope: MS4xfK/WZk6a5KbPwMTO2UTE5oBeYd99Wep+Nu4GkcV9nffFRbf3A6vuJ5rFZRYt8Rf7OKChDAtX4j2RZD/WAD2Wxhy9fd7Wn5aV1UYSQjW4inT+ydbdBsDt 856zRCqoDLKuR3PbddVOXuEKNXa4HSTHtex1Um0tGO44tEWW7BVU6y9HAwtjfmUv4JPc7eZC5lTiLNcaOzGuB5fj638/cRV15hrKm6TSNL7GKBWce8o3MlIV Zm+lzAvYQ1GdpSlqPgazBA== X-Rspamd-Queue-Id: 4H3CL50ctFz4g92 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N I changed mine to be the same as yours. I can connect. (I use iwn(4) and ath(4) here.) Do you reboot every time you test or simply this? service netif stop wlan0 service netif start wlan0 If simply above, does a reboot have it work again? The reason I ask is, I discovered, today, a quirk in 14-CURRENT, regardless of the wpa_supplicant installed. It will always associate following a reboot however when running the above two commands to stop and start wlan0 I can reproduce your problem. The workaround for now is when running the above two commands to also ifconfig wlan0 down; ifconfig wlan0 up. Can you try ifconfig wlan0 down; ifconfig wlan0 up after stopping/starting wlan0? You may need to wait 2-3 seconds between down and up. If this occurs at boot, try the ifconfig down and up anyway (to help narrow down the problem). -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. In message , Idwer Vollering writes: > There's no core dump in /, wpa_supplicant connects to 802.11b/g/n > (there's no way to lock this, instead of having a mix of standards) on > 2,4GHz. > > /etc/wpa_supplicant.conf: > network={ > ssid="some ssid" > scan_ssid=1 > key_mgmt=WPA-PSK > psk="some key" > } > > Op ma 6 sep. 2021 om 15:23 schreef Cy Schubert : > > > > In message c > > om> > > , Idwer Vollering writes: > > > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert >: > > > > > > > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > > > writes: > > > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > > > > then), but after updating the "head" slice of my laptopp from: > > > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CA > NARY > > > > > > amd64 1400032 1400032 > > > > > > > > > > > > to: > > > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CA > NARY > > > > > > amd64 1400032 1400032 > > > > > > > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does n > ot: > > > > > > the WLAN LED doesn't light up. > > > > > > > > > > I am also experiencing issues with wlan after my current update to > > > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > > > > demonstrating the same behavior - wlan can not associate. > > > > > You can mitigate it by using security/wpa_supplicant from ports as re > plac > > > emen > > > > > t > > > > > of wpa_supplicant in base. > > > > > > > > > > ..... > > > > > > > > > > > > I note that exactly the same hardware works OK in stable/12 and sta > ble/ > > > 13. > > > > > > > > > > > > Peace, > > > > > > david > > > > > > > > > > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a c > lue. > > > > > > wpa_supplicant stops in wpa_driver_bsd_scan() - > > > https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948 > f94b > > > 86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 > > > > > > Here's some selected output from /var/log/messages. > > > > > > Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): > > > > > > Sep 6 13:29:40 wpa_supplicant[45348]: Successfully > > > initialized wpa_supplicant > > > Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, > > > op=20, val=0, arg_len=7]: Invalid argument > > > Sep 6 13:29:40 syslogd: last message repeated 1 times > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to > > > associate with (SSID='' freq=2447 MHz) > > > Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add > > > supported operating classes IE > > > Sep 6 13:29:46 kernel: wlan1: link state changed to UP > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with > > > > > > > Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer > > > space available > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key > > > negotiation completed with [PTK=CCMP GTK=CCMP] > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: > > > CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] > > > > > > After (built from main): > > > > > > Sep 6 12:19:50 wpa_supplicant[1236]: Successfully > > > initialized wpa_supplicant > > > Sep 6 12:19:50 kernel: wlan1: Ethernet address: > > > Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, > > > op=20, val=0, arg_len=7]: Invalid argument > > > Sep 6 12:19:50 syslogd: last message repeated 1 times > > > Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: > > > CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 > > > > Is there a wpa_supplicant.core dump in / ? > > > > Can you also send me a sanitized copy of wpa_supplicant.conf, please? I'm > > interested in the lines proto=, key_mgmt=, pairwise=, group=, eap=, and > > phase2=. You may not be using eap= or phase2=, which is fine. I'd like to > > see if there are any differences from what was tested. Though, looking at > > your outputs above you're probably using something like: > > > > proto=RSN WPA > > key_mgmt=WPA-PSK > > pairwise=CCMP > > group=CCMP > > > > Is this correct? > > > > If you try ports/securitiy/wpa_supplicant-devel (same codebase as in > > 14-CURRENT), does it work? (ports/security/wpa_supplicant is the old 2.9 > > codebase.) > > > > What is your AP set for? 802.11g, 802.11n, 802.11ac? > > > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: https://FreeBSD.org > > NTP: Web: https://nwtime.org > > > > The need of the many outweighs the greed of the few. > > > > From nobody Mon Sep 6 15:45:31 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id ABEA917C3BE8 for ; Mon, 6 Sep 2021 15:45:35 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3CR31HyVz4k2Y for ; Mon, 6 Sep 2021 15:45:35 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-qk1-x735.google.com with SMTP id b64so7307172qkg.0 for ; Mon, 06 Sep 2021 08:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=vFOtBvTXGmCAhzYCKvWM+FJMWuPK0yAjfQ+kX5UpY3c=; b=UqlUbBbK5AtVaq07FZ45NnnIgFf7ADeup3Pjoelk/9NK+sIZoQTlEkzPC5Sf8yoYYN 6fy7OoyCvSmQBMCAnYteGzvAAW9FiPDBJgjls1H3qIJ3ufj/twYxPRhTCIThwTkaxheQ giB+unyGseyTjrOLoBR+Af72gYw6+688YN71aOwMg/c5OrKeTLxy1p0ihqNQTZQUWDV9 hWWRRjg+x7b7cQhc8onB1g7hsTmmU2pCW6IO4KaoufRvvOsh/Hrw7UdTQ+eHzcEs31w9 b/5HmV14ZloA43cQEwjJlAO1H0Sw9SRlT5xAJLv5A+FEoyDy9hjCkMgmncsC0yQ/wPag Zu0Q== 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=vFOtBvTXGmCAhzYCKvWM+FJMWuPK0yAjfQ+kX5UpY3c=; b=IOuWluee5DAkV+T4GG+S0tGfTovivEDXzmXWQ+ySn1eXbkuLKW3G7wdZKBnV/xn4fh lftsuDfuJ0kAEbBHmKK3jUzpV/MX/tNXoz6336nG0OLOCEHOzS5g2QMOmN93MkpJaz2C yup1Tf5zKon4j14QLeJTZLvblOdky9+UHAG2usNqo3HIq2bTGhcfp5fJt5bJQ6n97Faf GAxv1OAE21FfbkaasiZGgZF2aJJfvjFe/CEFRYWrhqB5dcIxDIsU00/jPKeD+OwOETVR 6myPWeGD0YFfMW+aYi0g/uV4QIzyNvO0c2pAzXlZTjelt22dDRFpl2Lq14GJuO1h0fHj SYOg== X-Gm-Message-State: AOAM532I3UQshbti22TivSe5NbXMF3t6kPlvMKhEoiI9ny646IFTR9K0 s8JhEGlzaRDA6s7yadiGRq3xc7q6f7s= X-Google-Smtp-Source: ABdhPJwPaRoXYdUo0ztKwe+y7WD8VOK9xp1uT1GTfhL7tJEGYWXd//mKXx5zL7AEFTE/8qx8DReF8A== X-Received: by 2002:a37:a405:: with SMTP id n5mr11727585qke.218.1630943134664; Mon, 06 Sep 2021 08:45:34 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id c2sm5423619qte.22.2021.09.06.08.45.34 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 08:45:34 -0700 (PDT) To: current@freebsd.org From: Karel Gardas Subject: Install to ZFS root is using device names hence failing when device tree is changed. Message-ID: <73602bc2-44d9-f45e-e91e-fb0bd30dd640@gmail.com> Date: Mon, 6 Sep 2021 17:45:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org 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: 4H3CR31HyVz4k2Y X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=UqlUbBbK; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gardask@gmail.com designates 2607:f8b0:4864:20::735 as permitted sender) smtp.mailfrom=gardask@gmail.com X-Spamd-Result: default: False [-3.52 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::735:from]; NEURAL_HAM_SHORT(-0.52)[-0.521]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Hello, just installed 14-current snapshot from 2.9. on uefi amd64 machine. Installed from USB memstick which was detected as da0 into the ssd hanging on usb3 in external enclosure which was detected as da1. ZFS root pool is then using /dev/da1p3 as swap and /dev/da1p1 as /boot/efi and probably also something as root zpool. Anyway, expected thing happen. When I pulled out USB stick identified as da0 on reboot, the drive on USB3 switch from da1 to da0 and result is unbootable system with complains about various /dev/da1xx drives missing for swap efi boot etc. Would be great if ZFS root install was using kind of device uuids or serial numbers or so so such device change would not disrupt freebsd from running correctly. Thanks, Karel From nobody Mon Sep 6 14:36:43 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D064617C7956 for ; Mon, 6 Sep 2021 15:49:58 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3CX50sTYz4n9B for ; Mon, 6 Sep 2021 15:49:56 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 186EahPG032620 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 17:36:43 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 186EahEh032619; Mon, 6 Sep 2021 17:36:43 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: Cy Schubert Cc: Idwer Vollering , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Date: Mon, 06 Sep 2021 17:36:43 +0300 Message-ID: <5606886.Zv9zXsTiuT@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: <202109061323.186DNLMQ010404@slippy.cwsent.com> References: <202109061323.186DNLMQ010404@slippy.cwsent.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4H3CX50sTYz4n9B X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of oleg@theweb.org.ua has no SPF policy when checking 66.63.164.214) smtp.mailfrom=oleg@theweb.org.ua X-Spamd-Result: default: False [-0.30 / 15.00]; TO_DN_SOME(0.00)[]; HAS_XAW(0.00)[]; HFILTER_HELO_IP_A(1.00)[sigill.theweb.org.ua]; HFILTER_HELO_NORES_A_OR_MX(0.30)[sigill.theweb.org.ua]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; CTE_CASE(0.50)[]; ASN(0.00)[asn:8100, ipnet:66.63.164.0/23, country:US]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[oleg]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[theweb.org.ua]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 2021 M09 6, Mon 16:23:21 EEST Cy Schubert wrote: > In message om> > > , Idwer Vollering writes: > > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert : > > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > > > > > writes: > > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > > > then), but after updating the "head" slice of my laptopp from: > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CAN > > > > > ARY > > > > > amd64 1400032 1400032 > > > > > > > > > > to: > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CAN > > > > > ARY > > > > > amd64 1400032 1400032 > > > > > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does > > > > > not: > > > > > the WLAN LED doesn't light up. > > > > > > > > I am also experiencing issues with wlan after my current update to > > > > > > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > > > demonstrating the same behavior - wlan can not associate. > > > > You can mitigate it by using security/wpa_supplicant from ports as > > > > replac > > > > emen > > > > > > t > > > > of wpa_supplicant in base. > > > > > > > > ..... > > > > > > > > > I note that exactly the same hardware works OK in stable/12 and > > > > > stable/ > > > > 13. > > > > > > > Peace, > > > > > david > > > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a > > > clue. > > > > wpa_supplicant stops in wpa_driver_bsd_scan() - > > https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948f > > 94b 86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 > > > > Here's some selected output from /var/log/messages. > > > > Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): > > > > Sep 6 13:29:40 wpa_supplicant[45348]: Successfully > > initialized wpa_supplicant > > Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, > > op=20, val=0, arg_len=7]: Invalid argument > > Sep 6 13:29:40 syslogd: last message repeated 1 times > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to > > associate with (SSID='' freq=2447 MHz) > > Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add > > supported operating classes IE > > Sep 6 13:29:46 kernel: wlan1: link state changed to UP > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with > > > > > Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer > > space available > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key > > negotiation completed with [PTK=CCMP GTK=CCMP] > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: > > CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] > > > > After (built from main): > > > > Sep 6 12:19:50 wpa_supplicant[1236]: Successfully > > initialized wpa_supplicant > > Sep 6 12:19:50 kernel: wlan1: Ethernet address: > > Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, > > op=20, val=0, arg_len=7]: Invalid argument > > Sep 6 12:19:50 syslogd: last message repeated 1 times > > Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: > > CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 > > Is there a wpa_supplicant.core dump in / ? No > > Can you also send me a sanitized copy of wpa_supplicant.conf, please? I'm > interested in the lines proto=, key_mgmt=, pairwise=, group=, eap=, and > phase2=. You may not be using eap= or phase2=, which is fine. # grep -E -2 "proto=|key_mgmt=|pairwise=|group=|eap=|phase2=" /etc/ wpa_supplicant.conf network={ priority=0 key_mgmt=NONE } Config of active wireless network looks like network={ ssid=",,," scan_ssid=0 psk="..." priority=4 } Global section of /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant eapol_version=2 ap_scan=1 fast_reauth=1 > I'd like to > see if there are any differences from what was tested. Though, looking at > your outputs above you're probably using something like: > > proto=RSN WPA > key_mgmt=WPA-PSK > pairwise=CCMP > group=CCMP > > Is this correct? > > If you try ports/securitiy/wpa_supplicant-devel (same codebase as in > 14-CURRENT), does it work? No it fals to associate with same symptoms as wpa_supplicant from base. > (ports/security/wpa_supplicant is the old 2.9 > codebase.) > > What is your AP set for? 802.11g, 802.11n, 802.11ac? 802.11gn From nobody Mon Sep 6 12:40:24 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3188017C7B30 for ; Mon, 6 Sep 2021 15:50:04 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3CXB2pgbz4n54 for ; Mon, 6 Sep 2021 15:50:02 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 186CeOjd004375 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 15:40:24 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 186CeOZo004374; Mon, 6 Sep 2021 15:40:24 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: Cy Schubert Cc: current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Date: Mon, 06 Sep 2021 15:40:24 +0300 Message-ID: <2790202.slGk94SIus@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: <202109060550.1865oLlJ013110@slippy.cwsent.com> References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4H3CXB2pgbz4n54 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of oleg@theweb.org.ua has no SPF policy when checking 66.63.164.214) smtp.mailfrom=oleg@theweb.org.ua X-Spamd-Result: default: False [-0.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[oleg]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HFILTER_HELO_IP_A(1.00)[sigill.theweb.org.ua]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[theweb.org.ua]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; HFILTER_HELO_NORES_A_OR_MX(0.30)[sigill.theweb.org.ua]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:8100, ipnet:66.63.164.0/23, country:US]; CTE_CASE(0.50)[] X-ThisMailContainsUnwantedMimeParts: N On 2021 M09 6, Mon 08:50:21 EEST Cy Schubert wrote: > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > writes: > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > then), but after updating the "head" slice of my laptopp from: > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > amd64 1400032 1400032 > > > > > > to: > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > > amd64 1400032 1400032 > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > > the WLAN LED doesn't light up. > > > > I am also experiencing issues with wlan after my current update to > > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > demonstrating the same behavior - wlan can not associate. > > You can mitigate it by using security/wpa_supplicant from ports as > > replacemen t > > of wpa_supplicant in base. > > > > ..... > > > > > I note that exactly the same hardware works OK in stable/12 and > > > stable/13. > > > > > > Peace, > > > david > > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. /var/log/messages:Sep 6 15:21:55 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:21:56 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:21:57 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:22:44 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:30:11 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:30:32 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:30:34 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 /var/log/messages:Sep 6 15:30:50 asus wpa_supplicant[310]: wlan0: CTRL-EVENT- SCAN-FAILED ret=-1 retry=1 Compare it to successful association attempt while I was using wpa_supplicant from ports: /var/log/messages:Sep 6 15:19:21 asus wpa_supplicant[326]: wlan0: Authentication with MAC timed out. /var/log/messages:Sep 6 15:19:21 asus wpa_supplicant[326]: wlan0: CTRL-EVENT- DISCONNECTED bssid=MAC reason=3 locally_generated=1 /var/log/messages:Sep 6 15:19:21 asus wpa_supplicant[326]: wlan0: CTRL-EVENT- SSID-TEMP-DISABLED id=0 ssid="..." auth_failures=1 duration=10 reason=CONN_FAILED /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: wlan0: CTRL-EVENT- SSID-REENABLED id=0 ssid="..." /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: wlan0: Trying to associate with MAC (SSID='...' freq=2447 MHz) /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: Failed to add supported operating classes IE /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: wlan0: Associated with MAC /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: wlan0: WPA: Key negotiation completed with MAC [PTK=CCMP GTK=CCMP] /var/log/messages:Sep 6 15:19:31 asus wpa_supplicant[326]: wlan0: CTRL-EVENT- CONNECTED - Connection to MAC completed [id=0 id_str=] wlan related settings from /etc/rc.conf wlans_ath0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" Thank you From nobody Mon Sep 6 16:26:34 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8E60E17A53A3 for ; Mon, 6 Sep 2021 16:26:42 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3DLT22NSz52k3 for ; Mon, 6 Sep 2021 16:26:40 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 186GQYpw062179 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 19:26:34 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 186GQYK3062178; Mon, 6 Sep 2021 19:26:34 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: Cy Schubert , current@freebsd.org Cc: Idwer Vollering Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Date: Mon, 06 Sep 2021 19:26:34 +0300 Message-ID: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: <202109061541.186FfDRR024955@slippy.cwsent.com> References: <202109061541.186FfDRR024955@slippy.cwsent.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4H3DLT22NSz52k3 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of oleg@theweb.org.ua has no SPF policy when checking 66.63.164.214) smtp.mailfrom=oleg@theweb.org.ua X-Spamd-Result: default: False [1.59 / 15.00]; TO_DN_SOME(0.00)[]; HAS_XAW(0.00)[]; HFILTER_HELO_IP_A(1.00)[sigill.theweb.org.ua]; HFILTER_HELO_NORES_A_OR_MX(0.30)[sigill.theweb.org.ua]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8100, ipnet:66.63.164.0/23, country:US]; CTE_CASE(0.50)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[oleg]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.89)[0.892]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[theweb.org.ua]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On 2021 M09 6, Mon 18:41:13 EEST Cy Schubert wrote: > I changed mine to be the same as yours. I can connect. (I use iwn(4) and > ath(4) here.) a ) regular reboot - wlan can not associate b ) service netif restart - wlan can not associate c ) service netif stop wlan0 ; service netif start wlan0 - wlan can not associate d ) ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up - wlan associated e ) regular reboot with ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up added to /etc/rc.local - wlan associated Thank you. > > Do you reboot every time you test or simply this? > > service netif stop wlan0 > service netif start wlan0 > > If simply above, does a reboot have it work again? > > The reason I ask is, I discovered, today, a quirk in 14-CURRENT, regardless > of the wpa_supplicant installed. It will always associate following a > reboot however when running the above two commands to stop and start wlan0 > I can reproduce your problem. The workaround for now is when running the > above two commands to also ifconfig wlan0 down; ifconfig wlan0 up. > > Can you try ifconfig wlan0 down; ifconfig wlan0 up after stopping/starting > wlan0? You may need to wait 2-3 seconds between down and up. From nobody Mon Sep 6 16:44:13 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5244D17988ED for ; Mon, 6 Sep 2021 16:44:23 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3Dkt0N0qz3CMt for ; Mon, 6 Sep 2021 16:44:22 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-ed1-x52b.google.com with SMTP id q3so10228736edt.5 for ; Mon, 06 Sep 2021 09:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=40KSNtDq0GuURSTDnTVwj0vE9w0Pa/p76UUeAAn6JnI=; b=OKXJa7NKVykT4/xhHi27Tt23gK3oNB9jZb8mYNQ8cBmZn6U8bY7JgD50hfLU1ypIcx gVoFOANgLVjG4XYKnavyJ+rlIn0exzKoiFeSjtxKjdOyM5+UtouDa15s6W5S0D6dkXCB TvTrhTIyOByiu0zIBMFiHcwmhEiBZl+bYDIds7pVWCSPJUxGzDu179u6ilk5tWXBVi2A 6MTABvmGcSLXBOnsXmHvQUSGCTSV6RystlqN+3NP3FpbkbUsdHMc4m28rT6vn1kzm6KT CcluGCAxJf+UMdyLPfklZoH/CftNILhdNW6cZofd+YYODygWXa44VNr54p+D5FELxJMX Nswg== 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=40KSNtDq0GuURSTDnTVwj0vE9w0Pa/p76UUeAAn6JnI=; b=TzwTTQ1Sa5iMVEszMIngfJ12vTtH9L06Y0MaNHA4V+d8O32NXsEwGzIH9EPNumBBo/ 1ZMha8GgMN6CzY3H3b/zCWRXvLUMdhNhllzHxF8n705ye70ZZf+LJKQpbUH8z+pZ6eO7 k7AjO8VaGBCxT4fsAm0bqwjlokQ2C2z61+iEyTGX6jSW1R5LTE44oEB4hhFOf9f/dCkp blOYcJRBinq5Rg+qBizYFZ1o7vRQZCnkH5XrYsL04TE4JHuXl3oPCGfuXaYCx5DGD/VL Msy+BcM13eODdkq7pwJMcxBboE8XC44kGTXzEAdiOmnr2mh96h591ZxYFZjGD1ZMKx4R WMdw== X-Gm-Message-State: AOAM531nZSn6nKrao06W8uP24T4XGx99zI2z7c+cGwvPBVwaIQZLXEcc QqQMieJ3B2G7XIKNMu4+vVXtXBwmkvg= X-Google-Smtp-Source: ABdhPJwItk9Me3P1pnxPysDM4tcVrapRZoz/44A834SO3ZAK38lCBKrviHk2SpHu/EcdRQUT+t+OMQ== X-Received: by 2002:a05:6402:10d7:: with SMTP id p23mr14322344edu.74.1630946654495; Mon, 06 Sep 2021 09:44:14 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id f26sm5033211eds.90.2021.09.06.09.44.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 09:44:14 -0700 (PDT) To: freebsd-current@freebsd.org From: Karel Gardas Subject: EFI/loader show garbage in console when set to some resolution in loader.conf Message-ID: Date: Mon, 6 Sep 2021 18:44:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org 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: 4H3Dkt0N0qz3CMt X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=OKXJa7NK; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gardask@gmail.com designates 2a00:1450:4864:20::52b as permitted sender) smtp.mailfrom=gardask@gmail.com X-Spamd-Result: default: False [-3.55 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; 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]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52b:from]; NEURAL_HAM_SHORT(-0.55)[-0.550]; 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_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Hello, I'm attempting to set EFI console resolution in loader to 1920x1920. This is working fine on all 3 tested* combinations when interrupting loader with '3' key and then issueing 'gop set 11' command and then 'boot' command. However I'd like to make that permanent and here issue comes. I've tried both: - edit /boot/loader.conf by adding  'exec="gop set 11"' - edit /boot/loader.conf by adding  'efi_max_resolution="1920x1920"' neither of those works on neither of 3 tested combinations where tested combinations are: (1) 13.0 release (2) 13.0-p4 (stable) (3) 14.0 snapshot from 2.9. The behavior is still the same. Screen blanks (like it would do gop set 11), then switches to text mode to show loader UI and when kernel is loaded it correctly shows that efi resolution is 1920x1920 but then when kernels boot, it produce just garbage to the console like loader and kernel resolution would be off by some unknown number... Is this is known issue, is there a known workaround for it? Or shall I report it properly to bugzilla? Thanks! Karel From nobody Mon Sep 6 16:59:55 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E2E7F17A2128 for ; Mon, 6 Sep 2021 17:00:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st43p00im-ztbu10063701.me.com (st43p00im-ztbu10063701.me.com [17.58.63.178]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3F505wD4z3KTC for ; Mon, 6 Sep 2021 17:00:04 +0000 (UTC) (envelope-from tsoome@me.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1630947598; bh=K5Nxaz70YY8wp/orzyIrCjpEXMH62cB9OC6LKrEzDWk=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=wNWuTIQ1PqRB37Ib2ausfZHu+1uLJ/OfffAv6ZCcs5Emyocagv42rNah6JFWS/Y6+ 7mPED553Etnfr8WWJNz1bkpP1WXFy/+Di+HTeCriR+ZNd1nadfa4eAx0hWcc+0noLD As9XJfhtGVUjHG+XfyGYOxlqKEABUKYs79KXkRSRArnp4MOTraKLSflXj2QTLkAAuc 698icP5NuvIhTGXkhNP+6Kqn/G7QlXc+wAEdH3LEyVlxPQgYH1nFfiI6g0CfPexBiD efTwjbSyMAPtZhsx/Vj5f40fIUDWaN4yJ0NpPMtLHJl2B2Dq/PaMJNlFgEwluPNWav 9+fFXnzdC1Hzg== Received: from smtpclient.apple (148-52-235-80.sta.estpak.ee [80.235.52.148]) by st43p00im-ztbu10063701.me.com (Postfix) with ESMTPSA id 461729A027E; Mon, 6 Sep 2021 16:59:57 +0000 (UTC) Message-Id: <31B6298E-7B3D-45FD-87CB-E541C019C5F7@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_8A07169A-DE07-495E-9721-302F83C1AA6C" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: EFI/loader show garbage in console when set to some resolution in loader.conf Date: Mon, 6 Sep 2021 19:59:55 +0300 In-Reply-To: Cc: freebsd-current@freebsd.org To: Karel Gardas References: X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.790 definitions=2021-09-06_08:2021-09-03,2021-09-06 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2009150000 definitions=main-2109060109 X-Rspamd-Queue-Id: 4H3F505wD4z3KTC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: tsoome@me.com From: Toomas Soome via freebsd-current X-Original-From: Toomas Soome X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail=_8A07169A-DE07-495E-9721-302F83C1AA6C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 6. Sep 2021, at 19:44, Karel Gardas wrote: >=20 > Hello, >=20 > I'm attempting to set EFI console resolution in loader to 1920x1920. = This is working fine on all 3 tested* combinations when interrupting = loader with '3' key and then > issueing 'gop set 11' command and then 'boot' command. >=20 > However I'd like to make that permanent and here issue comes. I've = tried both: >=20 > - edit /boot/loader.conf by adding > 'exec=3D"gop set 11"' >=20 > - edit /boot/loader.conf by adding > 'efi_max_resolution=3D"1920x1920"' >=20 > neither of those works on neither of 3 tested combinations where = tested combinations are: if you have this setting, what does gop get report? With the versions = listed below, was the loader in ESP updated too? >=20 > (1) 13.0 release > (2) 13.0-p4 (stable) > (3) 14.0 snapshot from 2.9. >=20 > The behavior is still the same. Screen blanks (like it would do gop = set 11), then switches to text mode to show loader UI and when kernel > is loaded it correctly shows that efi resolution is 1920x1920 but then = when kernels boot, it produce just garbage to the console like loader = and kernel resolution would be off > by some unknown number... >=20 > Is this is known issue, is there a known workaround for it? Or shall I = report it properly to bugzilla? >=20 > Thanks! > Karel >=20 what you get from: dmesg | grep efifb rgds, toomas --Apple-Mail=_8A07169A-DE07-495E-9721-302F83C1AA6C-- From nobody Mon Sep 6 17:16:04 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E4EF417AA2B4; Mon, 6 Sep 2021 17:15:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 4H3FR91smjz3Qfg; Mon, 6 Sep 2021 17:15:49 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:becd] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:becd]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id BB3F4132F; Mon, 6 Sep 2021 17:15:48 +0000 (UTC) Subject: Re: PAM module for loading ZFS keys on login To: freebsd-current@freebsd.org, Greg , FreeBSD Hackers References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> <20210906140137.iGt2J%steffen@sdaoden.eu> From: Eric McCorkle Message-ID: Date: Mon, 6 Sep 2021 13:16:04 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210906140137.iGt2J%steffen@sdaoden.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4H3FR91smjz3Qfg X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of eric@metricspace.net has no SPF policy when checking 2001:470:1f11:617::107) smtp.mailfrom=eric@metricspace.net X-Spamd-Result: default: False [-0.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[eric]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(1.00)[0.997]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Honestly, I think the best approach to this is the autounmountd unload keys thing. There's just too many ways the sessions thing can go wrong. The autounmountd solution gets the job done, and it tolerates possible failures better than anything else I can think of, barring some kind of major kernel-side awareness of sessions. There's potentially a gap between the user logging out and the keys being unloaded, but that's not much of a problem when you consider the most likely use case. The thing to keep in mind with the primary use case I've suggested for the ZFS key load/unload stuff is that it's not so much about preventing the Adversary from gaining access to data is it is about constraining when they need to be active to pull off an exfiltration. This is the real reason you see it on secure systems: it makes the Adversary's job a lot harder, while at the same time making the jobs of defensive ops and DFIR folks a whole lot easier. Say I've got sensitive files in my home directory. On a base system, the Adversary just has to circumvent OS file protections, but they can do this at any time. This means your DFIR folks have to dig through a huge amount of history. If I have to be logged in for the keys to be present, then the Adversary has to have some kind of monitoring to detect when I am, and then has a constrained window in which to pull off the attack. Both of these increase the likelihood of detection, while also constraining the window of time the DFIR folks have to examine. This isn't changed much by having the system wait some small time interval after I'm logged out to unmount my home directory and unload my keys. (If anything, it introduces another potential vector for detection: the unmounting/unloading will fail if someone is still accessing my data after I'm gone.) On 9/6/21 10:01 AM, Steffen Nurpmeso wrote: > Eric McCorkle wrote in > : > |Interesting, I wasn't aware of the upstream module. I'd say that's > > It's existence was the reason i have readded (now optional, and > a tad different) session support for my pam_xdg PAM module, > because i was thinking that, if such a many-eyes-seen thing of > a software project that claims to be and aims at being enterprise, > ships such a terrible and terribly broken thing, then i can also > offer session tracking. But my manual at least states > > CAVEATS > On Unix systems any “daemonized” program or script is reparented to the > program running with PID 1, most likely leaving the PAM user session > without PAM recognizing this. Yet careless such code may hold or expect > availability of resources of the session it just left, truly performing > cleanup when sessions end seems thus unwise. Since so many PAM modules > do support session tracking and cleanup pam_xdg.so readded optional sup‐ > port for this. > > But the real solution would be PAM session tracking in-kernel, > somehow, wouldn't it? > Also, on FreeBSD and OpenPAM many separate files exist in > /etc/pam.d for things which might open a session, whereas linuxpam > at least has /etc/pam.d/common-session; it has many common- things > in fact, and in /etc/pam.d/sshd i for example see > > # > # /etc/pam.d/sshd - openssh service module configuration > # > > auth include common-auth > > account include common-account > > password include common-password > > session include common-session > > --steffen > | > |Der Kragenbaer, The moon bear, > |der holt sich munter he cheerfully and one by one > |einen nach dem anderen runter wa.ks himself off > |(By Robert Gernhardt) > From nobody Mon Sep 6 17:31:33 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BC03B17B43AB for ; Mon, 6 Sep 2021 17:31:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H3FnP0N0Jz3p3G for ; Mon, 6 Sep 2021 17:31:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id NH54msGecps7PNIT2mok7K; Mon, 06 Sep 2021 17:31:36 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NIT1m561TdCHGNIT2moGze; Mon, 06 Sep 2021 17:31:36 +0000 X-Authority-Analysis: v=2.4 cv=SdyUytdu c=1 sm=1 tr=0 ts=61365078 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=QCccru2TAAAA:8 a=0DU4wlSrt08kT7HQN4IA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 a=rCjsK_HQOcgUb9vb-KUg:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 0D6CCED; Mon, 6 Sep 2021 10:31:34 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186HVXr5004438; Mon, 6 Sep 2021 10:31:33 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061731.186HVXr5004438@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Oleg V. Nauman" cc: Cy Schubert , current@freebsd.org, Idwer Vollering Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> References: <202109061541.186FfDRR024955@slippy.cwsent.com> <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> Comments: In-reply-to "Oleg V. Nauman" message dated "Mon, 06 Sep 2021 19:26:34 +0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 10:31:33 -0700 X-CMAE-Envelope: MS4xfDQRUpQTgbDLlmb6HaYABnzO2jNeHEzYT8v2J0N9mchBLk2vtwQAi5HTJGDaR9VVg2EZ9J+4TCpXbqH/Pda5VeDKWPy7niRc+cKkOx6U8zwqwCB5VcYV i/mqrMZu9oMr/T/iiHRyJbrrEmMDmO+E2/muhaTGrTYoplxz9XM2m8HWucz9nSr5L5vDyjiu4ZWhckruLwI0drtj1AuxGCEa+IHKuv2PZvch8w6AtGwBxAHs pE10fIiV5NUs0TGT5BuwIQ== X-Rspamd-Queue-Id: 4H3FnP0N0Jz3p3G X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N One last favour to ask, can you try this with the wpa_supplicant-devel port, please? I'm trying to narrow down if this is related to the options in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the same using wpa_supplicant-devel, this tells me to look at the code instead of Makefiles. I can reproduce the service netif restart problem using the old wpa_supplicant 2.9, so at least here there is no change in behaviour. Though on my sandbox machine the ifconfig dow/up is not required -- though even the older wpa_supplicant 2.9 behaves the same on my laptop, (no regression experienced here). To help point to either Makefile.inc or contrib/wpa, can you please try the wpa_supplicant-devel port. This will tell me where to look next. Fifteen seconds isn't needed. Two or three, even no wait, will do. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. In message <3000346.ZmR5Pbtf01@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 6, Mon 18:41:13 EEST Cy Schubert wrote: > > I changed mine to be the same as yours. I can connect. (I use iwn(4) and > > ath(4) here.) > > a ) regular reboot - wlan can not associate > b ) service netif restart - wlan can not associate > c ) service netif stop wlan0 ; service netif start wlan0 - wlan can not > associate > d ) ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up - wlan associated > e ) regular reboot with ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up > added to /etc/rc.local - wlan associated > > Thank you. > > > > > Do you reboot every time you test or simply this? > > > > service netif stop wlan0 > > service netif start wlan0 > > > > If simply above, does a reboot have it work again? > > > > The reason I ask is, I discovered, today, a quirk in 14-CURRENT, regardless > > of the wpa_supplicant installed. It will always associate following a > > reboot however when running the above two commands to stop and start wlan0 > > I can reproduce your problem. The workaround for now is when running the > > above two commands to also ifconfig wlan0 down; ifconfig wlan0 up. > > > > Can you try ifconfig wlan0 down; ifconfig wlan0 up after stopping/starting > > wlan0? You may need to wait 2-3 seconds between down and up. > > From nobody Mon Sep 6 17:45:11 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A19BD17BBBFE for ; Mon, 6 Sep 2021 17:45:14 +0000 (UTC) (envelope-from markm@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3G5649Hgz3vHf; Mon, 6 Sep 2021 17:45:14 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from smtpclient.apple (unknown [IPv6:2a02:8011:300b:42:dc61:2981:dbd1:7b7b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: markm) by smtp.freebsd.org (Postfix) with ESMTPSA id 0334E24ECD; Mon, 6 Sep 2021 17:45:13 +0000 (UTC) (envelope-from markm@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_DCC37491-D84C-4F18-B0D8-DE4B098021AD"; protocol="application/pgp-signature"; micalg=pgp-sha512 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: BUG in libm's powf From: Mark Murray In-Reply-To: <20210906152836.GA86615@troutmask.apl.washington.edu> Date: Mon, 6 Sep 2021 18:45:11 +0100 Cc: freebsd-current@freebsd.org Message-Id: <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> References: <20210906152836.GA86615@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.3654.120.0.1.13) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_DCC37491-D84C-4F18-B0D8-DE4B098021AD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi I've opened a Phab ticket for this. I hope that's OK? https://reviews.freebsd.org/D31865 M > On 6 Sep 2021, at 16:28, Steve Kargl = wrote: >=20 > Paul Zimmermann has identified a bug in Openlibm's powf(), > which is identical to FreeBSD's libm. Both derived from > fdlibm. https://github.com/JuliaMath/openlibm/issues/212. >=20 > Consider >=20 > % cat h.c > #include > #include > int > main(void) > { > float x, y, z; > x =3D 0x1.ffffecp-1F; > y =3D -0x1.000002p+27F; > z =3D 0x1.557a86p115F; > printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); > return 0; > } >=20 > % cc -o h -fno-builtin h.c -lm && ./h > 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 >=20 > Note, clang seems to have a builtin for powf(), but one cannot > count of clang being the only consumer of libm. With the patch > at the end of this email, I get >=20 > % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun -lmath = && ./h > 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be 5.540807e+34 >=20 > Watch for copy and paste whitespace corruption. >=20 > --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 03:29:00.956878000 = -0800 > +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 > @@ -136,7 +136,7 @@ > /* |y| is huge */ > if(iy>0x4d000000) { /* if |y| > 2**27 */ > /* over/underflow if x is not close to one */ > - if(ix<0x3f7ffff7) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > + if(ix<0x3f7ffff6) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; > /* now |1-x| is tiny <=3D 2**-20, suffice to compute > log(x) by x-x^2/2+x^3/3-x^4/4 */ >=20 >=20 > -- > Steve >=20 -- Mark R V Murray --Apple-Mail=_DCC37491-D84C-4F18-B0D8-DE4B098021AD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 Comment: GPGTools - http://gpgtools.org iQEzBAEBCgAdFiEEyzPHvybPbOpU9MCxQlsJDh9CUqAFAmE2U6cACgkQQlsJDh9C UqDiPgf/TFqUqY43Quu2WJD1I51lnxkFi2QywwPENaIxMv3RvrhjD/3D59oeLTrA RO8HW0v4qDnRxGAFkHRHJnxcRgi2KI7WEEYVZ0IZ2OQLb1RamgkSUeoMoHCJcgTF gPFF4JAANDAnldP/0lVZrOGttENvNo0wJqbWCaWtG6Z8lex6k5XDNej8pNxqo8/z FTe5LRucg6IuPpmrhf/3XQkNnFf1yEaDAnsrbtqaelkz2aRzVTuhUajk4c5FRFsM F4kqRWsvz/urjrkEbfwCxQKO7lFt6LJGsWDOZ7BB96zAAX04r9Lb0FZbNrWT8cWn sQYIXhBMVbYKi/T7i55QTS3FlLXGxg== =Bs0m -----END PGP SIGNATURE----- --Apple-Mail=_DCC37491-D84C-4F18-B0D8-DE4B098021AD-- From nobody Mon Sep 6 17:49:01 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3531A17BEF43 for ; Mon, 6 Sep 2021 17:49:14 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3G9h6QdQz4RxL for ; Mon, 6 Sep 2021 17:49:12 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 186Hn1CH084602 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 20:49:01 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 186Hn1JK084601; Mon, 6 Sep 2021 20:49:01 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: Cy Schubert , current@freebsd.org Cc: Idwer Vollering Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Date: Mon, 06 Sep 2021 20:49:01 +0300 Message-ID: <2780735.SSXfckUlLJ@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: <202109061731.186HVXr5004438@slippy.cwsent.com> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4H3G9h6QdQz4RxL X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of oleg@theweb.org.ua has no SPF policy when checking 66.63.164.214) smtp.mailfrom=oleg@theweb.org.ua X-Spamd-Result: default: False [-0.30 / 15.00]; TO_DN_SOME(0.00)[]; HAS_XAW(0.00)[]; HFILTER_HELO_IP_A(1.00)[sigill.theweb.org.ua]; HFILTER_HELO_NORES_A_OR_MX(0.30)[sigill.theweb.org.ua]; HAS_ORG_HEADER(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; CTE_CASE(0.50)[]; ASN(0.00)[asn:8100, ipnet:66.63.164.0/23, country:US]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[oleg]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[theweb.org.ua]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: > One last favour to ask, can you try this with the wpa_supplicant-devel > port, please? I'm trying to narrow down if this is related to the options > in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the > same using wpa_supplicant-devel, this tells me to look at the code instead > of Makefiles. > > I can reproduce the service netif restart problem using the old > wpa_supplicant 2.9, so at least here there is no change in behaviour. > Though on my sandbox machine the ifconfig dow/up is not required -- though > even the older wpa_supplicant 2.9 behaves the same on my laptop, (no > regression experienced here). > > To help point to either Makefile.inc or contrib/wpa, can you please try the > wpa_supplicant-devel port. This will tell me where to look next. I can confirm that wpa_supplicant from security/wpa_supplicant-devel port demonstrating the same behavior as wpa_supplicant from base - "ifconfig wlan0 down ; sleep 5 ; ifconfig wlan0 up" mitigate wlan association issue. > > Fifteen seconds isn't needed. Two or three, even no wait, will do. Thank you From nobody Mon Sep 6 17:53:18 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 92BDD179B435 for ; Mon, 6 Sep 2021 17:53:19 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3GGR2rcSz4WLV; Mon, 6 Sep 2021 17:53:19 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 186HrIiW087480 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 10:53:18 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 186HrIcj087479; Mon, 6 Sep 2021 10:53:18 -0700 (PDT) (envelope-from sgk) Date: Mon, 6 Sep 2021 10:53:18 -0700 From: Steve Kargl To: Mark Murray Cc: freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: <20210906175318.GA87474@troutmask.apl.washington.edu> References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> X-Rspamd-Queue-Id: 4H3GGR2rcSz4WLV X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Fine with me. I don't have a phabricator account and bugzilla reports seems to get lost in the ether. -- steve On Mon, Sep 06, 2021 at 06:45:11PM +0100, Mark Murray wrote: > Hi > > I've opened a Phab ticket for this. I hope that's OK? > > https://reviews.freebsd.org/D31865 > > M > > > On 6 Sep 2021, at 16:28, Steve Kargl wrote: > > > > Paul Zimmermann has identified a bug in Openlibm's powf(), > > which is identical to FreeBSD's libm. Both derived from > > fdlibm. https://github.com/JuliaMath/openlibm/issues/212. > > > > Consider > > > > % cat h.c > > #include > > #include > > int > > main(void) > > { > > float x, y, z; > > x = 0x1.ffffecp-1F; > > y = -0x1.000002p+27F; > > z = 0x1.557a86p115F; > > printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); > > return 0; > > } > > > > % cc -o h -fno-builtin h.c -lm && ./h > > 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 > > > > Note, clang seems to have a builtin for powf(), but one cannot > > count of clang being the only consumer of libm. With the patch > > at the end of this email, I get > > > > % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun -lmath && ./h > > 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be 5.540807e+34 > > > > Watch for copy and paste whitespace corruption. > > > > --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 03:29:00.956878000 -0800 > > +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 > > @@ -136,7 +136,7 @@ > > /* |y| is huge */ > > if(iy>0x4d000000) { /* if |y| > 2**27 */ > > /* over/underflow if x is not close to one */ > > - if(ix<0x3f7ffff7) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > > + if(ix<0x3f7ffff6) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > > if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; > > /* now |1-x| is tiny <= 2**-20, suffice to compute > > log(x) by x-x^2/2+x^3/3-x^4/4 */ > > > > > > -- > > Steve > > > > -- > Mark R V Murray > -- Steve From nobody Mon Sep 6 17:55:07 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5E1A7179CBA3 for ; Mon, 6 Sep 2021 17:55:09 +0000 (UTC) (envelope-from markm@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3GJY0Z3Vz4Xcg; Mon, 6 Sep 2021 17:55:09 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from smtpclient.apple (unknown [IPv6:2a02:8011:300b:42:dc61:2981:dbd1:7b7b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: markm) by smtp.freebsd.org (Postfix) with ESMTPSA id 81DC4246F6; Mon, 6 Sep 2021 17:55:08 +0000 (UTC) (envelope-from markm@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_54C874FF-9B6C-4A93-88B4-E933BDD0A7E2"; protocol="application/pgp-signature"; micalg=pgp-sha512 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: BUG in libm's powf From: Mark Murray In-Reply-To: <20210906175318.GA87474@troutmask.apl.washington.edu> Date: Mon, 6 Sep 2021 18:55:07 +0100 Cc: freebsd-current@freebsd.org Message-Id: References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.3654.120.0.1.13) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_54C874FF-9B6C-4A93-88B4-E933BDD0A7E2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks! And it's committed! M > On 6 Sep 2021, at 18:53, Steve Kargl = wrote: >=20 > Fine with me. I don't have a phabricator account and > bugzilla reports seems to get lost in the ether. >=20 > -- > steve >=20 > On Mon, Sep 06, 2021 at 06:45:11PM +0100, Mark Murray wrote: >> Hi >>=20 >> I've opened a Phab ticket for this. I hope that's OK? >>=20 >> https://reviews.freebsd.org/D31865 >>=20 >> M >>=20 >>> On 6 Sep 2021, at 16:28, Steve Kargl = wrote: >>>=20 >>> Paul Zimmermann has identified a bug in Openlibm's powf(), >>> which is identical to FreeBSD's libm. Both derived from >>> fdlibm. https://github.com/JuliaMath/openlibm/issues/212. >>>=20 >>> Consider >>>=20 >>> % cat h.c >>> #include >>> #include >>> int >>> main(void) >>> { >>> float x, y, z; >>> x =3D 0x1.ffffecp-1F; >>> y =3D -0x1.000002p+27F; >>> z =3D 0x1.557a86p115F; >>> printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); >>> return 0; >>> } >>>=20 >>> % cc -o h -fno-builtin h.c -lm && ./h >>> 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 >>>=20 >>> Note, clang seems to have a builtin for powf(), but one cannot >>> count of clang being the only consumer of libm. With the patch >>> at the end of this email, I get >>>=20 >>> % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun -lmath = && ./h >>> 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be 5.540807e+34 >>>=20 >>> Watch for copy and paste whitespace corruption. >>>=20 >>> --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 03:29:00.956878000 = -0800 >>> +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 >>> @@ -136,7 +136,7 @@ >>> /* |y| is huge */ >>> if(iy>0x4d000000) { /* if |y| > 2**27 */ >>> /* over/underflow if x is not close to one */ >>> - if(ix<0x3f7ffff7) return (hy<0)? sn*huge*huge:sn*tiny*tiny; >>> + if(ix<0x3f7ffff6) return (hy<0)? sn*huge*huge:sn*tiny*tiny; >>> if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; >>> /* now |1-x| is tiny <=3D 2**-20, suffice to compute >>> log(x) by x-x^2/2+x^3/3-x^4/4 */ >>>=20 >>>=20 >>> -- >>> Steve >>>=20 >>=20 >> -- >> Mark R V Murray >>=20 >=20 >=20 >=20 > -- > Steve >=20 -- Mark R V Murray --Apple-Mail=_54C874FF-9B6C-4A93-88B4-E933BDD0A7E2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 Comment: GPGTools - http://gpgtools.org iQEzBAEBCgAdFiEEyzPHvybPbOpU9MCxQlsJDh9CUqAFAmE2VfsACgkQQlsJDh9C UqAjVwf+OyV1HRj+qGQyQvnneKNd+FIznK82ZjKfMppRgSrHdPndUqJiMgn5VYGn SbUSQhwL0iqVUz6apIqZ7o9jQMBJE4YyemWgbcLl/l3KsgkKL6tn5n07iKFgO3EM cRBPmNGmoTaGeZLO/KhO7DXLA5OxQ3SifDK52AkODAMHwxIv//oPwq3O3tYSFnl+ C1Zx4QVZ8546UUJp5FV/MGyGZ8OU1Kf/wJPG7Tf3SHpHbAlpZQFM3XY4h70KPHme C0cdV5FK4qLtcaaERaR+dwpN7PZma4HttHNnB6deyTzQ3UKHWcoaaht8OsvUAky/ KNEx/b/5jUauEtcfjERaXmyKtLHunA== =4mRH -----END PGP SIGNATURE----- --Apple-Mail=_54C874FF-9B6C-4A93-88B4-E933BDD0A7E2-- From nobody Mon Sep 6 17:57:31 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2B71D179EF8E for ; Mon, 6 Sep 2021 17:57:41 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3GMS2M8Cz4b9N for ; Mon, 6 Sep 2021 17:57:40 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-ej1-x634.google.com with SMTP id me10so14810266ejb.11 for ; Mon, 06 Sep 2021 10:57:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=vFOtBvTXGmCAhzYCKvWM+FJMWuPK0yAjfQ+kX5UpY3c=; b=kQQXG1gglv1h/lBF+fMGC//a+LcDiphFn7/qaL3iudeKDPdBqx6S+L8ib5opEVor/Q 8T1qp97Pm3+pC8aOzOSjQN9kEGY+5e17TZa0MH/hlz2DL0nd4LJ3gZWFdsoHW8Pobuu9 S6ZD10dDvmUHovvNrHZbaSB5P1r8J78FON4tyXf7IjDEBVmKuhi3YuX9SaSAEuHPDLIM 7dc0PX9KLe2yVOV53oT9Aet7JN3pP22KDntZeO5mj7e87+LtQVnnz3Q6vepmeZIFWMRN NVqbp51KPAIhNJuntNK2FWMcbW7FwzsMSl/8agTTiBi65D6U+3wTu05vHjuFtPLkfm3l +mPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=vFOtBvTXGmCAhzYCKvWM+FJMWuPK0yAjfQ+kX5UpY3c=; b=FsHAswawA05nUaovGNqvnfM7Sz5ieDMB8GcvRVxXsybxIsQIspSRlTmjEHFTBoy3qH nxaCVGKiHHLwh5ezQNTmCVV95KfqaMybrBCiLy6gTvHOx5YIr/i94GkiE+sjc9vtECiv AJjBgQ5RrdevumppTOWgKiuFDNsTSVDppnbBo18UjLFNnn1CC4Oei01Fyj/vzypAYVx1 RjymlDCnhgqkP+aQcgPtHhJ7qunoovg9oZbrYd+fW+j72vO+MrbXXd1HDH4Ah2Gps0Us iitBmX2+dIDF32ZJYGINb63LCmpMNl7Q6hovQ3/1y9mwFkmSNbbs5fkUOu4xaVG9nhLF VzWw== X-Gm-Message-State: AOAM530O7/MSA7WizLCYtyy76FxypofQ1m18u6VbFgsbgDjLcyhB3dEy wpdf7Qs9drLFqTsdyBPigIIEu9Oikpk= X-Google-Smtp-Source: ABdhPJyVM8uzzYZtseXmXdW3Qn0fbwS6MNZ79I1TkhSdY78a0buwpzL0wVlutxJLz9FOQyQG/7qx0A== X-Received: by 2002:a17:906:31ca:: with SMTP id f10mr14307452ejf.73.1630951053141; Mon, 06 Sep 2021 10:57:33 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id r8sm5027545eds.39.2021.09.06.10.57.32 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 10:57:32 -0700 (PDT) From: Karel Gardas Subject: Install to ZFS root is using device names hence failing when device tree is changed. To: freebsd-current@freebsd.org Message-ID: <0f8c2244-41e8-9994-d519-edf33762148e@gmail.com> Date: Mon, 6 Sep 2021 19:57:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org 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: 4H3GMS2M8Cz4b9N X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=kQQXG1gg; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gardask@gmail.com designates 2a00:1450:4864:20::634 as permitted sender) smtp.mailfrom=gardask@gmail.com X-Spamd-Result: default: False [-3.96 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; 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]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::634:from]; NEURAL_HAM_SHORT(-0.96)[-0.957]; 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_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Hello, just installed 14-current snapshot from 2.9. on uefi amd64 machine. Installed from USB memstick which was detected as da0 into the ssd hanging on usb3 in external enclosure which was detected as da1. ZFS root pool is then using /dev/da1p3 as swap and /dev/da1p1 as /boot/efi and probably also something as root zpool. Anyway, expected thing happen. When I pulled out USB stick identified as da0 on reboot, the drive on USB3 switch from da1 to da0 and result is unbootable system with complains about various /dev/da1xx drives missing for swap efi boot etc. Would be great if ZFS root install was using kind of device uuids or serial numbers or so so such device change would not disrupt freebsd from running correctly. Thanks, Karel From nobody Mon Sep 6 18:04:59 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 297EB17A4D2C for ; Mon, 6 Sep 2021 18:05:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3GWx5x2xz4gDn; Mon, 6 Sep 2021 18:05:01 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 186I4xk1087714 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 11:05:00 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 186I4x57087713; Mon, 6 Sep 2021 11:04:59 -0700 (PDT) (envelope-from sgk) Date: Mon, 6 Sep 2021 11:04:59 -0700 From: Steve Kargl To: Mark Murray Cc: freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: <20210906180459.GA87487@troutmask.apl.washington.edu> References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4H3GWx5x2xz4gDn X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N No, thank you for the quick response. Of course, a one character diff might be easier to review. :-) -- steve On Mon, Sep 06, 2021 at 06:55:07PM +0100, Mark Murray wrote: > Thanks! > > And it's committed! > > M > > > On 6 Sep 2021, at 18:53, Steve Kargl wrote: > > > > Fine with me. I don't have a phabricator account and > > bugzilla reports seems to get lost in the ether. > > > > -- > > steve > > > > On Mon, Sep 06, 2021 at 06:45:11PM +0100, Mark Murray wrote: > >> Hi > >> > >> I've opened a Phab ticket for this. I hope that's OK? > >> > >> https://reviews.freebsd.org/D31865 > >> > >> M > >> > >>> On 6 Sep 2021, at 16:28, Steve Kargl wrote: > >>> > >>> Paul Zimmermann has identified a bug in Openlibm's powf(), > >>> which is identical to FreeBSD's libm. Both derived from > >>> fdlibm. https://github.com/JuliaMath/openlibm/issues/212. > >>> > >>> Consider > >>> > >>> % cat h.c > >>> #include > >>> #include > >>> int > >>> main(void) > >>> { > >>> float x, y, z; > >>> x = 0x1.ffffecp-1F; > >>> y = -0x1.000002p+27F; > >>> z = 0x1.557a86p115F; > >>> printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); > >>> return 0; > >>> } > >>> > >>> % cc -o h -fno-builtin h.c -lm && ./h > >>> 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 > >>> > >>> Note, clang seems to have a builtin for powf(), but one cannot > >>> count of clang being the only consumer of libm. With the patch > >>> at the end of this email, I get > >>> > >>> % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun -lmath && ./h > >>> 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be 5.540807e+34 > >>> > >>> Watch for copy and paste whitespace corruption. > >>> > >>> --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 03:29:00.956878000 -0800 > >>> +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 > >>> @@ -136,7 +136,7 @@ > >>> /* |y| is huge */ > >>> if(iy>0x4d000000) { /* if |y| > 2**27 */ > >>> /* over/underflow if x is not close to one */ > >>> - if(ix<0x3f7ffff7) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > >>> + if(ix<0x3f7ffff6) return (hy<0)? sn*huge*huge:sn*tiny*tiny; > >>> if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; > >>> /* now |1-x| is tiny <= 2**-20, suffice to compute > >>> log(x) by x-x^2/2+x^3/3-x^4/4 */ > >>> > >>> > >>> -- > >>> Steve > >>> > >> > >> -- > >> Mark R V Murray > >> > > > > > > > > -- > > Steve > > > > -- > Mark R V Murray > -- Steve From nobody Mon Sep 6 18:21:55 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F18D517ACE2E for ; Mon, 6 Sep 2021 18:22:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4H3GvT5v8Cz4nhX for ; Mon, 6 Sep 2021 18:21:57 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id NH54mArnyczbLNJFlmKUw2; Mon, 06 Sep 2021 18:21:57 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NJFkm5PyWdCHGNJFlmoQYZ; Mon, 06 Sep 2021 18:21:57 +0000 X-Authority-Analysis: v=2.4 cv=SdyUytdu c=1 sm=1 tr=0 ts=61365c45 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=QCccru2TAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=2lwzVihPj1q7mMlt1dkA:9 a=CjuIK1q_8ugA:10 a=rCjsK_HQOcgUb9vb-KUg:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A8C0612C; Mon, 6 Sep 2021 11:21:55 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186ILt9b005261; Mon, 6 Sep 2021 11:21:55 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061821.186ILt9b005261@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Oleg V. Nauman" cc: Cy Schubert , current@freebsd.org, Idwer Vollering , phlip@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <2780735.SSXfckUlLJ@sigill.theweb.org.ua> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> Comments: In-reply-to "Oleg V. Nauman" message dated "Mon, 06 Sep 2021 20:49:01 +0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 11:21:55 -0700 X-CMAE-Envelope: MS4xfLg8DfEEddHQo+qSpP8KV+JrVX2dKDWGJvKxoojHEuGdvlxksEIzf7lbdp9/pBA1G8trz3q3bD2B1kRx0noIkzxpJLe8+gIeyUyptB3qIDLSlWDKbajZ yKhHoKohCQC9J82mY/dZ7HdC276o0aVM4UnhE1k6vMeuop9ebXTOndAElSPZm6n9tkDCOEN/9TnAVSrhKOIA0cnxWUTfsLD2B9rjsiAsyKQTJC41HaMoR6CQ gl24JhWPj4dswgJxYYfmUXezNEThW7lGs1putc04iwI2RKI/CpFEf7rVwwPnNbYt X-Rspamd-Queue-Id: 4H3GvT5v8Cz4nhX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <2780735.SSXfckUlLJ@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: > > One last favour to ask, can you try this with the wpa_supplicant-devel > > port, please? I'm trying to narrow down if this is related to the options > > in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the > > same using wpa_supplicant-devel, this tells me to look at the code instead > > of Makefiles. > > > > I can reproduce the service netif restart problem using the old > > wpa_supplicant 2.9, so at least here there is no change in behaviour. > > Though on my sandbox machine the ifconfig dow/up is not required -- though > > even the older wpa_supplicant 2.9 behaves the same on my laptop, (no > > regression experienced here). > > > > To help point to either Makefile.inc or contrib/wpa, can you please try the > > wpa_supplicant-devel port. This will tell me where to look next. > > I can confirm that wpa_supplicant from security/wpa_supplicant-devel port > demonstrating the same behavior as wpa_supplicant from base - "ifconfig wlan0 > > down ; sleep 5 ; ifconfig wlan0 up" mitigate wlan association issue. Thank you. This is an issue that I'll need to chase down with our upstream. In the mean time while work on this/bring it to upstream's attention this should circumvent the issue: diff --git a/libexec/rc/rc.d/wpa_supplicant b/libexec/rc/rc.d/wpa_supplicant index 8a86fec90e4d..cfe5f1ab27c6 100755 --- a/libexec/rc/rc.d/wpa_supplicant +++ b/libexec/rc/rc.d/wpa_supplicant @@ -12,6 +12,7 @@ name="wpa_supplicant" desc="WPA/802.11i Supplicant for wireless network devices" +start_postcmd="wpa_poststart" rcvar= ifn="$2" @@ -27,6 +28,12 @@ is_ndis_interface() esac } +wpa_poststart() { + ifconfig ${ifn} down + sleep 3 + ifconfig ${ifn} up +} + if is_wired_interface ${ifn} ; then driver="wired" elif is_ndis_interface ${ifn} ; then I'll have more questions later (need to start working on another job) but I'd like to learn more about your configuration to understand why it works at boot for myself and phlip@ and not for you and the others here on -current who have experienced the same issue. Understanding what triggers this will go a long way to resolving it. (cc'd philip@) BTW, my laptop is configured so that wlan0 (iwn0) and bge0 are members of lagg0. Whereas on my sandbox wlan0 (ath0) is used directly. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. From nobody Mon Sep 6 18:44:54 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AE2F517BA515 for ; Mon, 6 Sep 2021 18:44:56 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3HQ04GjWz3F1S for ; Mon, 6 Sep 2021 18:44:56 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-ed1-x52c.google.com with SMTP id v5so10581760edc.2 for ; Mon, 06 Sep 2021 11:44:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=1GlYtpjmi1KgXWvWa56C6NK1K0HXzVYyR8lXQA2aFi0=; b=gl1Yrmi+FijzFzCXfYfZgOhz9CdurODqceLeOwrJUuQ5Y4j85LEvC/ahrbaRmHQ1UD yhBQ//rXw0aLKHp6M8W9yASQ+v+1kPZ9KxN/ItSgdcIJDKcQTafw8RxaL0z4nJWg99eQ CPmCHjs/k/2R5u1ksweTdwXCpeCGF4lp2J8a3tBIMPLlSQCgYxjFLQd7BnqHSwwxY1L1 ExWkxrIn4RxfasAdgkp+QdnFt7oSklXl+IqkTtvIz0m28qAKtDtYMKf2dlJbugWopUgE XUwiEL45feC9PMK7pLRKDYmcPPXz4DrgD5h42yj4Zp3D5os88IIC3sw28hrOfMub/xnL /kmA== 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-language; bh=1GlYtpjmi1KgXWvWa56C6NK1K0HXzVYyR8lXQA2aFi0=; b=fM+SqQZSSihIW+7j5q6XzTe0OPnJmsCtEgpdauHlfq7gzEfq7FIg72+p5UFiv99uDF MctdHZXa2a+5m00tmUhZg+RC2iaC3puRvvFsvuuM5nOKsIOHeIkZ72jdGsdMIEp0d7nB xQpBoLxA7ru6WwXMOGzqsyFidzlOSe/f6RA/H8MC7SihBu3kwbcpXUFpcjHHBqvHcR6C qWMJBDPNvDpn+qPLQWCMc+pZG1xnMyiGrp+wwRXtWtnwaQKw+jTkTAp4dqyiPlXutfn2 GVIywepSmUzDckBpIeLLuLsdX47AtzUC5u+GIFE/fXa2Nk4cw1SU4k/34rMl7jiiKwhu QnXQ== X-Gm-Message-State: AOAM531OShMqBDMEq4RthodgfAOYfQwc1UCSxsJfi4TWQ6THfNhDlqRs oXHHARMyF7tgJe5v7jG6UROb4wTAYr4= X-Google-Smtp-Source: ABdhPJxr4eHByulQ8eKJmWNMZpD19Ff+x7eOLD4txBttFeHkUB3AjEkpUpO0xZyv7KdS4BkzOsgMdQ== X-Received: by 2002:aa7:c790:: with SMTP id n16mr14788093eds.223.1630953895285; Mon, 06 Sep 2021 11:44:55 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id s23sm5071838eds.12.2021.09.06.11.44.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 11:44:54 -0700 (PDT) Subject: Re: EFI/loader show garbage in console when set to some resolution in loader.conf To: Toomas Soome Cc: freebsd-current@freebsd.org References: <31B6298E-7B3D-45FD-87CB-E541C019C5F7@me.com> From: Karel Gardas Message-ID: Date: Mon, 6 Sep 2021 20:44:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <31B6298E-7B3D-45FD-87CB-E541C019C5F7@me.com> Content-Type: multipart/alternative; boundary="------------644B97A551094B7E0B15F0C2" Content-Language: en-US X-Rspamd-Queue-Id: 4H3HQ04GjWz3F1S X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y This is a multi-part message in MIME format. --------------644B97A551094B7E0B15F0C2 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 9/6/21 6:59 PM, Toomas Soome wrote: > > >> On 6. Sep 2021, at 19:44, Karel Gardas > > wrote: >> >> Hello, >> >> I'm attempting to set EFI console resolution in loader to 1920x1920. >> This is working fine on all 3 tested* combinations when interrupting >> loader with '3' key and then >> issueing 'gop set 11' command and then 'boot' command. >> >> However I'd like to make that permanent and here issue comes. I've >> tried both: >> >> - edit /boot/loader.conf by adding >> 'exec="gop set 11"' >> >> - edit /boot/loader.conf by adding >> 'efi_max_resolution="1920x1920"' >> >> neither of those works on neither of 3 tested combinations where >> tested combinations are: > > if you have this setting, what does gop get report? With the versions > listed below, was the loader in ESP updated too? Good question. I'm not entirely sure if my 13.x installation is not update from 12.x. It probably is. IIRC I followed the update procedure recommended, but certainly 13.0 -> 13.0-p4 is just `fetch` and `install` matter. If you like me to update ESP bootloader, I'm happy to follow your instructions how to do that. Anyway, my 14.0-CURRENT is fresh install to separate drive in an attempt to duplicate issue also on current to report it here. So gop get reports this (manually rewritten by hand): - FreeBSD 14.0 - current: EDID 1920x1920 1920x1920 1920x1200 1920x1080 1600x1200 1600x900 1280x1024 1280x960 1280x720 mode 4: 1024x768x32, stride=1024 frame buffer: address=d0000000, size=300000 color mark: R=00ff0000, G=0000ff00, B=000000ff - FreeBSD 13.0-p4: EDID 1920x1920 1920x1920 1920x1200 1920x1080 1600x1200 1600x900 1280x1024 1280x960 1280x720 mode 4: 1024x768x32, stride 1024 frame buffer: address=d0000000, size 300000 color mark: R00ff0000, G=0000ff00, B000000ff > >> >> (1) 13.0 release >> (2) 13.0-p4 (stable) >> (3) 14.0 snapshot from 2.9. >> >> The behavior is still the same. Screen blanks (like it would do gop >> set 11), then switches to text mode to show loader UI and when kernel >> is loaded it correctly shows that efi resolution is 1920x1920 but >> then when kernels boot, it produce just garbage to the console like >> loader and kernel resolution would be off >> by some unknown number... >> >> Is this is known issue, is there a known workaround for it? Or shall >> I report it properly to bugzilla? >> >> Thanks! >> Karel >> > > what you get from: dmesg | grep efifb > - FreebSD 14.0-current: VT(efifb): resolution 1920x1920 - FreeBSD 13.0-p4: VT(efifb): resolution 1920x1920 Thanks, Karel --------------644B97A551094B7E0B15F0C2-- From nobody Mon Sep 6 19:34:13 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 65A4517A2C12 for ; Mon, 6 Sep 2021 19:34:32 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3JWD2RMwz3lgk; Mon, 6 Sep 2021 19:34:32 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: by mail-lf1-f45.google.com with SMTP id n2so5591037lfk.0; Mon, 06 Sep 2021 12:34:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VkyF9caspzEBP5P13JiTOUtwsEcRZclme04YPSHqb+U=; b=mdxwLdORintYV2jSacWskdQgq+9MKYCuxvUOR1CKlkNpI3qkjnRwCb92hrCgDcoLxQ z72glShnFnd6Xln1COHs+HmhErHgIlhFEBzM3ciYINwFG/g833AQhAPl3El47cA3LPub fS3L5ZZvwsfGTSnBY2qplYbANhUleVjw+uYGc4yFW34lBzw9mEGaXqNBWEwG7v8Hmr2V VuoSefBmPeZZT8gmgOUPdW+u0HLeYVfJGaLhdR8Snkq1/1PnxqC/EHzALtVknxSdViCx rccBYnNbmUg0LVT4qZUkF3AiofBNWHSTbgW+yAAmlOBb+OourMybzjuD7G75fb7jdZdR C4tQ== X-Gm-Message-State: AOAM531srCGAS5ETuSF0x3B5uyYdn2MVDskqsBs5/kG4nljdTElyl5ku 6RCK39YffoOS+S3wlmNAod5CrUeUOyPtdoD1vAwmjRnHTOk= X-Google-Smtp-Source: ABdhPJwGPEE8+A643xSji3kMNYydFdefXr+glFJMJHI9D4d7iBuahw0BAdf0iSFGg21zvTsDoobYX2mElvjZ6OFpD44= X-Received: by 2002:a05:6512:31c9:: with SMTP id j9mr2575238lfe.322.1630956864741; Mon, 06 Sep 2021 12:34:24 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Wolfram Schneider Date: Mon, 6 Sep 2021 21:34:13 +0200 Message-ID: Subject: Re: -CURRENT compilation time To: David Chisnall Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H3JWD2RMwz3lgk X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, 6 Sept 2021 at 11:44, David Chisnall wrote: > > On 06/09/2021 09:08, Jeremie Le Hen wrote: > > Compiling C++ seems > > extremely CPU heavy and this is made worse by the fact LLVM is built > > twice (once for build/cross tools, once for the actual world). > > Note that you need to build LLVM twice only if you are actively > debugging LLVM reproduceable deployment images. You actually don't need > to build it at all, you can use an external toolchain to skip the first > build and you can compile WITHOUT_TOOLCHAIN to avoid building the > version that's installed and then install a toolchain from packages: > > https://wiki.freebsd.org/ExternalToolchain I did a test on a 16 core (32 VCPU) machine (Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz). With the option WITHOUT_TOOLCHAIN=yes the world build time is 2.5 times faster (real or user+sys), down from 48 min to 19.5 min real time. time make -j16 buildworld -------------------------------------------------------------- >>> World build completed on Mon Sep 6 12:00:45 UTC 2021 >>> World built in 2862 seconds, ncpu: 32, make -j16 -------------------------------------------------------------- 2862.04 real 41234.87 user 1582.66 sys time make -j16 WITHOUT_TOOLCHAIN=yes buildworld -------------------------------------------------------------- >>> World build completed on Mon Sep 6 11:32:41 UTC 2021 >>> World built in 1181 seconds, ncpu: 32, make -j16 -------------------------------------------------------------- 1180.73 real 16076.27 user 988.73 sys -Wolfram -- Wolfram Schneider https://wolfram.schneider.org From nobody Mon Sep 6 20:35:26 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0941217A8A52 for ; Mon, 6 Sep 2021 20:35:30 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3KsX4Wk0z4ZTT; Mon, 6 Sep 2021 20:35:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 186KZQ9J088301 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 13:35:26 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 186KZQYZ088300; Mon, 6 Sep 2021 13:35:26 -0700 (PDT) (envelope-from sgk) Date: Mon, 6 Sep 2021 13:35:26 -0700 From: Steve Kargl To: Gordon Bergling Cc: Mark Murray , freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: <20210906203526.GA88286@troutmask.apl.washington.edu> References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> <20210906180459.GA87487@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4H3KsX4Wk0z4ZTT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.37 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.63)[0.626]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote: > could you turn to test program into an AFT test to prevent further regressions? > > —Gordon > I cannot tell if you are addressing Mark or me. For me, I know nothing about ATF. I do, however, suspect that this won't regress as I'm one of the few people who actually looks at threshold issues in libm. -- Steve From nobody Mon Sep 6 20:40:21 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D5DCC17ADA79 for ; Mon, 6 Sep 2021 20:40:32 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3KzN59lCz4dYc for ; Mon, 6 Sep 2021 20:40:32 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1mNLPh-000NRD-61; Mon, 06 Sep 2021 22:40:21 +0200 Date: Mon, 6 Sep 2021 22:40:21 +0200 From: Kurt Jaeger To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> <20210906180459.GA87487@troutmask.apl.washington.edu> <20210906203526.GA88286@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210906203526.GA88286@troutmask.apl.washington.edu> X-Rspamd-Queue-Id: 4H3KzN59lCz4dYc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi! > On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote: > > could you turn to test program into an AFT test to prevent further regressions? > > I cannot tell if you are addressing Mark or me. > For me, I know nothing about ATF. man 7 atf has more details. -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Mon Sep 6 21:21:31 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 46F7D1799123 for ; Mon, 6 Sep 2021 21:21:51 +0000 (UTC) (envelope-from contact@shiori.com.br) Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) (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 4H3Lv13J9Cz4sKS for ; Mon, 6 Sep 2021 21:21:49 +0000 (UTC) (envelope-from contact@shiori.com.br) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shiori.com.br; s=key1; t=1630963301; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=VeiQ9655r1dXEygKtZi3P9Bxeb6likn+LWGvZOUcNZo=; b=gvyRnSmsZLB2+9pz1pJWmpMv/UGqg9MhqKnKSUrHLzyooNhJZlZIDtdYy0yk9uTKKus3rc b1qsB6vkjLocMiOag2oxFWpfft49f19XE7ycz4JCu/I27+fdxwRRgMn7gm8Y0pPknB8i5+ aQhhTusCINL4kx6JHn7DF+tofb+1LP8= To: Cy Schubert Cc: current@freebsd.org, Idwer Vollering , "Oleg V. Nauman" Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-Reply-To: <202109061821.186ILt9b005261@slippy.cwsent.com> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> Date: Mon, 06 Sep 2021 18:21:31 -0300 Message-ID: <86tuix4cys.fsf@shiori.com.br> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: contact@shiori.com.br X-Rspamd-Queue-Id: 4H3Lv13J9Cz4sKS X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=shiori.com.br header.s=key1 header.b=gvyRnSms; dmarc=pass (policy=quarantine) header.from=shiori.com.br; spf=pass (mx1.freebsd.org: domain of contact@shiori.com.br designates 94.23.1.103 as permitted sender) smtp.mailfrom=contact@shiori.com.br X-Spamd-Result: default: False [-3.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[shiori.com.br:s=key1]; RCVD_IN_DNSWL_LOW(-0.10)[94.23.1.103:from]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_MISSING_CHARSET(2.50)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip4:94.23.1.103]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[shiori.com.br:+]; DMARC_POLICY_ALLOW(-0.50)[shiori.com.br,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:16276, ipnet:94.23.0.0/16, country:FR]; FREEMAIL_CC(0.00)[freebsd.org,gmail.com,theweb.org.ua]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[94.23.1.103:from] Reply-To: contact@shiori.com.br From: Filipe da Silva Santos via current X-Original-From: Filipe da Silva Santos X-ThisMailContainsUnwantedMimeParts: N --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > I'll have more questions later (need to start working on another job) but= =20 > I'd like to learn more about your configuration to understand why it work= s=20 > at boot for myself and phlip@ and not for you and the others here on=20 > -current who have experienced the same issue. Understanding what triggers= =20 > this will go a long way to resolving it. Hello, Cy, I have a Intel AC 3168 and can reproduce both problem and solution. I'd love to help with testing and info with the new version. Cheers! =2D- Filipe da Silva Santos 102E 1944 2189 31FF 06EB 3F79 760B AE45 F7B3 008E --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJKBAEBCAA0FiEEEC4ZRCGJMf8G6z95dguuRfezAI4FAmE2hlwWHGNvbnRhY3RA c2hpb3JpLmNvbS5icgAKCRB2C65F97MAjj3KD/sHU5m+gC+R/BlAceV2GoH086o8 dmhLYYoHKKhb3o9gvmEYwnbFJrtGmWvlpf1n9APvvDLV+XfJy/OtxL+v4ZHF9PEH bmM8TN/i+Lbx+8lPT+F8b99VTJX1+wGuqtY4WwCSunJhWDzDqM3YR58VbvCYGTkd dvTjJhepIKmALTGp4NqrE4lGZVAfl9rLmNTgunPH6FW/R71/2CHsMZqcGOVn3lCL 7A/ItBs/qfJwD2Te+RzeBwZ+HKcRfqHju8yoi5Og+uPP1ql/7D0c7n52FGXaFkj7 ilBLG+yHMsEQjsjAUGL4V6jZUfrEf+uUtJJcHct5ABc0owZ6fgjfZRbfXCXXJdXF duxRuU7O0P/5JZArhtczxkENZhhU76GBU/6VFcGo7wgfFvhAIHcXdOaxIzfrTC8Z 3ixrhvGTFvkN0w9U/E1MD+HwBLfOBnEOSJLZ27m+JTSvzMjn30HqKCAg52Y+05aD oECyeVAzZkUkZxtqUgFFeq5RXAuHDmXaYeEvUg8MY2ltFsjvhCFlPMxtanONQsHd L0s+IhWpQ8rbU/ZNsR9ipQ20vQ2XAJQbT3T0K31Q3mWXehHzqP8iBsCRKKGV7xag xcpSK8qYJK9Ht1VvNo9I/FWXtJXbBjRQpjKYqx1+1BEFeXAIIr2m4nN7wTnA2DiK RojG1JxS5Li9Sdwieg== =vlH1 -----END PGP SIGNATURE----- --=-=-=-- From nobody Mon Sep 6 21:44:18 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3232017A532B; Mon, 6 Sep 2021 21:44:09 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-74-106-232-4.bltmmd.fios.verizon.net [74.106.232.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4H3MNm3cKLz3HZN; Mon, 6 Sep 2021 21:44:08 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:becd] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:becd]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 5062912FB; Mon, 6 Sep 2021 21:44:02 +0000 (UTC) Subject: Re: PAM module for loading ZFS keys on login To: freebsd-current@freebsd.org, Greg , FreeBSD Hackers References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> <20210906140137.iGt2J%steffen@sdaoden.eu> <20210906185354.D5ymE%steffen@sdaoden.eu> From: Eric McCorkle Message-ID: <61e11d16-17d2-5f5e-a02a-ba1f1b56bbc7@metricspace.net> Date: Mon, 6 Sep 2021 17:44:18 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210906185354.D5ymE%steffen@sdaoden.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H3MNm3cKLz3HZN X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of eric@metricspace.net has no SPF policy when checking 74.106.232.4) smtp.mailfrom=eric@metricspace.net X-Spamd-Result: default: False [-0.32 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[eric]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.68)[0.680]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:701, ipnet:74.106.224.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I looked at the upstream one too. Mine is simple because I modified libzfs to be able to take the key directly in the key location override argument. If you look at my patch, it adds a "direct" key location, which basically works like "direct:keydata", where "keydata" is your key. In the case of the PAM module, this ends up being "direct:password". It looks like they essentially pull in all the libzfs logic for preparing keys. If you notice, they go directly to lzc_load_key (that is basically a thin wrapper around the ioctl). It's worth noting that apparently they change the key to the dataset when the user changes their password. Anyway, I've seen enough. I'm going to abandon the review for my PAM module and use the upstream one. I'm going to keep the review for the autounmountd patch live, though. On 9/6/21 2:53 PM, Steffen Nurpmeso wrote: > Eric McCorkle wrote in > : > ... > >> This patch creates a new PAM module that will load a ZFS key upon a > >> successful login: https://reviews.freebsd.org/D31844. It will use the > >> user's auth token as the key argument to loading a ZFS encryption key on > >> a user-specific ZFS data set. > ... > > Without knowing about libzfs i personally was stunned about the > simplicity of your patch, having read the upstream one. > > --steffen > | > |Der Kragenbaer, The moon bear, > |der holt sich munter he cheerfully and one by one > |einen nach dem anderen runter wa.ks himself off > |(By Robert Gernhardt) > From nobody Mon Sep 6 22:21:19 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B100217B61F0 for ; Mon, 6 Sep 2021 22:21:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3NCj3ZrQz3kVq; Mon, 6 Sep 2021 22:21:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 186MLJOZ088627 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Sep 2021 15:21:20 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 186MLJQR088626; Mon, 6 Sep 2021 15:21:19 -0700 (PDT) (envelope-from sgk) Date: Mon, 6 Sep 2021 15:21:19 -0700 From: Steve Kargl To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: <20210906222119.GA88619@troutmask.apl.washington.edu> References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> <20210906180459.GA87487@troutmask.apl.washington.edu> <20210906203526.GA88286@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4H3NCj3ZrQz3kVq X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Mon, Sep 06, 2021 at 10:40:21PM +0200, Kurt Jaeger wrote: > Hi! > > > On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote: > > > could you turn to test program into an AFT test to prevent further regressions? > > > > I cannot tell if you are addressing Mark or me. > > For me, I know nothing about ATF. > > man 7 atf > > has more details. > % man 7 atf No manual entry for atf % grep -i tests /etc/src.conf WITHOUT_GOOGLETEST="YES" WITHOUT_TESTS="YES" -- Steve From nobody Mon Sep 6 22:47:27 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4D6E9179BDB2 for ; Mon, 6 Sep 2021 22:47:32 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4H3Nnw1NgVz3thc for ; Mon, 6 Sep 2021 22:47:32 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id NHQgmAszMczbLNNOlmLCl1; Mon, 06 Sep 2021 22:47:31 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NNOkmQ6o5U9pxNNOlmM04s; Mon, 06 Sep 2021 22:47:31 +0000 X-Authority-Analysis: v=2.4 cv=Bbi7bph2 c=1 sm=1 tr=0 ts=61369a83 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=a_qd0PwhAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=Dr2m5JgQK5LG87V2HAwA:9 a=JOWeiY5itpwPQvuQ8dm/GawRuwE=:19 a=CjuIK1q_8ugA:10 a=vEXHPetyIDmorGAAYsTw:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id ED9B9F2; Mon, 6 Sep 2021 15:47:28 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186MlRGL004952; Mon, 6 Sep 2021 15:47:28 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109062247.186MlRGL004952@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Filipe da Silva Santos cc: Cy Schubert , current@freebsd.org, Idwer Vollering , "Oleg V. Nauman" Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <86tuix4cys.fsf@shiori.com.br> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <86tuix4cys.fsf@shiori.com.br> Comments: In-reply-to Filipe da Silva Santos message dated "Mon, 06 Sep 2021 18:21:31 -0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 15:47:27 -0700 X-CMAE-Envelope: MS4xfJ2sXwfZqmM/9CqTFMMf/sQLolV0AsV+WT0PE/sXbU3fCSVzROZ5qRPD6Y9ToYl4l4SV5xKXGvSKnsIlFiysgergVgwpoBxD6tFD4icmBZQZ9E0SnxT7 /6zLFDzvJLmEv20DKeuWQbOX9LldKokXJhYUu4ke30syTAdNlq31P07089E0Mi28SGl+j70hUanQYsKlwp7JM3DwTGcmme88coMyvxlnnZebIEoikkC1+BBE hmbUgMsFvs0JqcbmGKEVXJ92odj545xkrDcaD3MQ8k5rbcALY4gzWVbYciJ3UOb1 X-Rspamd-Queue-Id: 4H3Nnw1NgVz3thc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <86tuix4cys.fsf@shiori.com.br>, Filipe da Silva Santos writes: > --=-=-= > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > > I'll have more questions later (need to start working on another job) but= > =20 > > I'd like to learn more about your configuration to understand why it work= > s=20 > > at boot for myself and phlip@ and not for you and the others here on=20 > > -current who have experienced the same issue. Understanding what triggers= > =20 > > this will go a long way to resolving it. > > Hello, Cy, > I have a Intel AC 3168 and can reproduce both problem and solution. > > I'd love to help with testing and info with the new version. Can you also try the security/wpa_supplicant and security/wpa_supplicant-dev el ports, both without the ifconfig mitigation patch? This will more than confirm that this is an upstream problem and not in the FreeBSD Makefiles. This would be of great help as I cannot reproduce the problem at boot but after boot using service netif (which the old wpa_supplicant 2.9 also had). An additional confirmation that the -devel port has the same problem would help a lot. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. From nobody Tue Sep 7 05:24:28 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F19B317A44B8 for ; Tue, 7 Sep 2021 05:24:32 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3Yc06Xf7z3vvp for ; Tue, 7 Sep 2021 05:24:32 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1mNTau-000NzW-BV; Tue, 07 Sep 2021 07:24:28 +0200 Date: Tue, 7 Sep 2021 07:24:28 +0200 From: Kurt Jaeger To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: BUG in libm's powf Message-ID: References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> <20210906180459.GA87487@troutmask.apl.washington.edu> <20210906203526.GA88286@troutmask.apl.washington.edu> <20210906222119.GA88619@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210906222119.GA88619@troutmask.apl.washington.edu> X-Rspamd-Queue-Id: 4H3Yc06Xf7z3vvp X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi! > > > On Mon, Sep 06, 2021 at 10:22:02PM +0200, Gordon Bergling wrote: > > > > could you turn to test program into an AFT test to prevent further regressions? > > > > > > I cannot tell if you are addressing Mark or me. > > > For me, I know nothing about ATF. > > > > man 7 atf > > > > has more details. > % man 7 atf > No manual entry for atf > % grep -i tests /etc/src.conf > WITHOUT_GOOGLETEST="YES" > WITHOUT_TESTS="YES" https://www.freebsd.org/cgi/man.cgi?query=atf -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Tue Sep 7 07:01:11 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E28F0179F1E8 for ; Tue, 7 Sep 2021 07:01:48 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3bmD1Xdbz4vSs for ; Tue, 7 Sep 2021 07:01:48 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ua1-x935.google.com with SMTP id a14so5036716uao.0 for ; Tue, 07 Sep 2021 00:01:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=tOOs1+QZ9sALvkGt9tug6gQYr/16AApqhjZM0ZRIsew=; b=A6QXBm3jKnE2gD+oRLjfgZ0aNUOuZVT0XerOAM5xPRB1EOpUYcP17e6GfBFXKKiNhI lAgJ9yNs2DPp1IWavUVh93iN9j3PSPUcK26TZVVHmIVpuya8jK7ol63EUzYpMG84Hhw8 aDztXMlUAn88DyzlFcGisuaL9AX49AFZxsSsYxwWZRy6lUl2NnG+ruMVe8wKeIUPpnF9 hWb/ilf8+CqvQ633i1gQpvKzJA+WLpw3QLXtRcoU2T82rcqJe1gsa4QZn6++sBzIylnr Z6Si6SP0ShECjzVFXxM0ijWKY+HwB9B7KqFWr27BixXBKroNLlxzjGs4WAl9pfJhE94t pypg== 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=tOOs1+QZ9sALvkGt9tug6gQYr/16AApqhjZM0ZRIsew=; b=pTcaysJQm2H7drA82r1M0Uh3SBKr2iVjI/9K4Pzx6Oh1cCIulKvzvGm9H4x9QaLpOZ z31hD28+GgzAjBf2CQUAtV41D02gWa28/mWXe50Lct+KLhTWNM9NjKvFTERD/xN8xt04 XxTHLTEf4lrKw2A+bwmtkifAXO1DRKeDCWvChCA+iAMYuyw1fYgs1xP6Iv98+YeMswzF oUNc0fLm9MV/3O5oJ70gbli92FtaQ5vt+iCFGdOBKYegbwzb0H0+RA26ftsWqKvFEAkt Z+JYD4iqQ+HBIK3EKWypvLxMitofW6zVDT8ni2vr4TO/O9AKZ4ymXFZnpr86rkksEDOH 2aqw== X-Gm-Message-State: AOAM533Uye4YzpBxxTWuBgljGzxtK5t7x1xOaFkFEUOeA/IQwgeCarul Aen14NtSv4MZAcQEcsUjy+tPiO0AxD2d5wSlVtwDZKkHZd4= X-Google-Smtp-Source: ABdhPJzafWeBHYo2itDVt1466+0o9rrtdSfHWm3tsmLB3aEvdmXirAE84AwU5+9veVccv2Lhf5CL3Z1kElrOPlB4mBk= X-Received: by 2002:ab0:1323:: with SMTP id g32mr7468011uae.63.1630998107588; Tue, 07 Sep 2021 00:01:47 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Mehmet Erol Sanliturk Date: Tue, 7 Sep 2021 10:01:11 +0300 Message-ID: Subject: Move the Handbook into source tree To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d50cf505cb6256c5" X-Rspamd-Queue-Id: 4H3bmD1Xdbz4vSs X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=A6QXBm3j; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mesanliturk@gmail.com designates 2607:f8b0:4864:20::935 as permitted sender) smtp.mailfrom=mesanliturk@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,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]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::935:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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]; TAGGED_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y --000000000000d50cf505cb6256c5 Content-Type: text/plain; charset="UTF-8" Dear All , in many of my messages to FreeBSD mailing lists I am mentioning the following view : "Please move the Handbook into source tree , and Maintain it with respect to current release without mixing sliding releases : If you do this , maintenance of a correct Handbook is IMPOSSIBLE because maintenance of associated IF statements about releases . " When we look at the following web pages , we see the following : https://www.freebsd.org/cgi/man.cgi FreeBSD Manual Pages In the second box of "All sections" line , there are lines about all of the FreeBSD releases with many more other systems . In spite of this , in the following page : https://docs.freebsd.org/en/books/handbook/ FreeBSD Handbook The FreeBSD Documentation Project " Abstract Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 13.0-RELEASE, FreeBSD 12.2-RELEASE and FreeBSD 11.4-RELEASE. ... " A Handbook which ( for me , exactly , for the others , perhaps ) with many errors ... I think that , it is NOT extraordinarily a difficult process to move the Handbook into source tree and maintaining it with respect to per release and insert into the above web page a part similar to the manual pages to display the requested Handbook with respect to releases . In the present case , previous handbooks are lost , because of the difficulty of finding them . Thank you very much and my best wishes for you and humanity in these pandemic days ... Mehmet Erol Sanliturk --000000000000d50cf505cb6256c5-- From nobody Tue Sep 7 08:00:24 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C60DC17B97E8 for ; Tue, 7 Sep 2021 08:00:27 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3d3v58zfz3k3b; Tue, 7 Sep 2021 08:00:27 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from smtpclient.apple (unknown [IPv6:2a02:8011:300b:42:3945:6114:66c5:7d7c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: markm) by smtp.freebsd.org (Postfix) with ESMTPSA id 141872BD0D; Tue, 7 Sep 2021 08:00:26 +0000 (UTC) (envelope-from markm@FreeBSD.org) Content-Type: multipart/signed; boundary="Apple-Mail=_4A7A40C0-32F8-4D72-82D1-26C88E567736"; protocol="application/pgp-signature"; micalg=pgp-sha512 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: BUG in libm's powf From: Mark Murray In-Reply-To: Date: Tue, 7 Sep 2021 09:00:24 +0100 Cc: Steve Kargl , freebsd-current@freebsd.org Message-Id: References: <20210906152836.GA86615@troutmask.apl.washington.edu> <01D81389-45D1-4278-8DC1-7995D34D0276@FreeBSD.org> <20210906175318.GA87474@troutmask.apl.washington.edu> <20210906180459.GA87487@troutmask.apl.washington.edu> To: Gordon Bergling X-Mailer: Apple Mail (2.3654.120.0.1.13) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_4A7A40C0-32F8-4D72-82D1-26C88E567736 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 6 Sep 2021, at 21:22, Gordon Bergling wrote: >=20 > could you turn to test program into an AFT test to prevent further = regressions? Certainly! M >=20 > =E2=80=94Gordon >=20 >> Am 06.09.2021 um 20:04 schrieb Steve Kargl = : >>=20 >> No, thank you for the quick response. >>=20 >> Of course, a one character diff might be easier to review. :-) >>=20 >> -- >> steve >>=20 >> On Mon, Sep 06, 2021 at 06:55:07PM +0100, Mark Murray wrote: >>> Thanks! >>>=20 >>> And it's committed! >>>=20 >>> M >>>=20 >>>> On 6 Sep 2021, at 18:53, Steve Kargl = wrote: >>>>=20 >>>> Fine with me. I don't have a phabricator account and >>>> bugzilla reports seems to get lost in the ether. >>>>=20 >>>> -- >>>> steve >>>>=20 >>>> On Mon, Sep 06, 2021 at 06:45:11PM +0100, Mark Murray wrote: >>>>> Hi >>>>>=20 >>>>> I've opened a Phab ticket for this. I hope that's OK? >>>>>=20 >>>>> https://reviews.freebsd.org/D31865 >>>>>=20 >>>>> M >>>>>=20 >>>>>> On 6 Sep 2021, at 16:28, Steve Kargl = wrote: >>>>>>=20 >>>>>> Paul Zimmermann has identified a bug in Openlibm's powf(), >>>>>> which is identical to FreeBSD's libm. Both derived from >>>>>> fdlibm. https://github.com/JuliaMath/openlibm/issues/212. >>>>>>=20 >>>>>> Consider >>>>>>=20 >>>>>> % cat h.c >>>>>> #include >>>>>> #include >>>>>> int >>>>>> main(void) >>>>>> { >>>>>> float x, y, z; >>>>>> x =3D 0x1.ffffecp-1F; >>>>>> y =3D -0x1.000002p+27F; >>>>>> z =3D 0x1.557a86p115F; >>>>>> printf("%e %e %e <-- should be %e\n", x, y, powf(x,y), z); >>>>>> return 0; >>>>>> } >>>>>>=20 >>>>>> % cc -o h -fno-builtin h.c -lm && ./h >>>>>> 9.999994e-01 -1.342177e+08 inf <-- should be 5.540807e+34 >>>>>>=20 >>>>>> Note, clang seems to have a builtin for powf(), but one cannot >>>>>> count of clang being the only consumer of libm. With the patch >>>>>> at the end of this email, I get >>>>>>=20 >>>>>> % cc -o h -fno-builtin h.c -L/home/kargl/trunk/math/libm/msun = -lmath && ./h >>>>>> 9.999994e-01 -1.342177e+08 5.540807e+34 <-- should be = 5.540807e+34 >>>>>>=20 >>>>>> Watch for copy and paste whitespace corruption. >>>>>>=20 >>>>>> --- /usr/src/lib/msun/src/e_powf.c 2021-02-21 = 03:29:00.956878000 -0800 >>>>>> +++ src/e_powf.c 2021-09-06 08:17:09.800008000 -0700 >>>>>> @@ -136,7 +136,7 @@ >>>>>> /* |y| is huge */ >>>>>> if(iy>0x4d000000) { /* if |y| > 2**27 */ >>>>>> /* over/underflow if x is not close to one */ >>>>>> - if(ix<0x3f7ffff7) return (hy<0)? = sn*huge*huge:sn*tiny*tiny; >>>>>> + if(ix<0x3f7ffff6) return (hy<0)? = sn*huge*huge:sn*tiny*tiny; >>>>>> if(ix>0x3f800007) return (hy>0)? sn*huge*huge:sn*tiny*tiny; >>>>>> /* now |1-x| is tiny <=3D 2**-20, suffice to compute >>>>>> log(x) by x-x^2/2+x^3/3-x^4/4 */ >>>>>>=20 >>>>>>=20 >>>>>> -- >>>>>> Steve >>>>>>=20 >>>>>=20 >>>>> -- >>>>> Mark R V Murray >>>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> -- >>>> Steve >>>>=20 >>>=20 >>> -- >>> Mark R V Murray >>>=20 >>=20 >>=20 >>=20 >> -- >> Steve >>=20 >=20 -- Mark R V Murray --Apple-Mail=_4A7A40C0-32F8-4D72-82D1-26C88E567736 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 Comment: GPGTools - http://gpgtools.org iQEzBAEBCgAdFiEEyzPHvybPbOpU9MCxQlsJDh9CUqAFAmE3HBgACgkQQlsJDh9C UqDG9gf/T0G4KdTGPNMwq+dluUJyADTKzQyKfbMZWvaT8BmKa4KuMSzmlcuFfEmO j4BV/F+ppYdWjNUQqLmCdnfZqsO9V7TWsMYjnsswTKPMIi/2wxVNni54teVfmXt3 LFtdgjki3XKxBnq1XvuKnNsE3PTjJG4TYb8+NZJvHuDNSux5bIZHs06lmFbUW+Er 1KvBDU60O5bHPfIQkSlozfM5G+ApwvNQtY2IgVnkSf9I6usVVPHhZ40t6YicCVc+ +fTz3tHF2o3tKypbxS7vlBPrrXW1PZtWXkwP+BH5j/Fh+FLSaFsqrpBCnrtIfzbc BSRzhNtjrQnkKs5zrbeIWnNENGxogw== =jpbp -----END PGP SIGNATURE----- --Apple-Mail=_4A7A40C0-32F8-4D72-82D1-26C88E567736-- From nobody Tue Sep 7 08:13:23 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 053F91799453 for ; Tue, 7 Sep 2021 08:13:33 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4H3dM014mvz3qlN for ; Tue, 7 Sep 2021 08:13:32 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-d24b235c.06-431-73746f70.bbcust.telenor.se ([92.35.75.210] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1mNWEN-000O8I-Vl; Tue, 07 Sep 2021 10:13:23 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alvermark.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=P4cIrCY72omfJMVwvlMLbiha2Jm6wq3NOJbGhO6DFY4=; b=YRG/LYmF2O6NUvSZzXgjS/T+81 QRaQ9GKw9VOlNe/ElwxaHF/OLy9j0h7jYQvIyyRWsls5WtDj38jxKhJ0kt1BLc6/QOpKbxwcVrTPw GFwZpp8xWSBDF0H95mbWeLmw3+KimMdYYEFCZK9E8V9ffBB5+6Zdl9eql3pLBNlM7r2yue5iy5DQf EkT8Quh6En0lUMqS2tSh0M9w7OHom/2p6Y4LT0vxsofis770mz5GwJs1lzHJyMcjI9y0swLo0mJ9K HRp05CWAeLVMuph+xhbWOCZnUD4Uui18xkTax1dNR8USbFpLMs0TzrchfoWiuHhgdDLRR9XF2GMxm obDcJhig==; Received: from 92-244-0-135.customers.ownit.se ([92.244.0.135] helo=[192.168.1.221]) by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1mNWEN-000C6Z-GZ; Tue, 07 Sep 2021 10:13:23 +0200 Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 To: Cy Schubert Cc: current@freebsd.org References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> From: Jakob Alvermark Message-ID: <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> Date: Tue, 7 Sep 2021 10:13:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <202109061821.186ILt9b005261@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4H3dM014mvz3qlN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=alvermark.net header.s=x header.b="YRG/LYmF"; dmarc=none; spf=pass (mx1.freebsd.org: domain of jakob@alvermark.net designates 185.34.136.138 as permitted sender) smtp.mailfrom=jakob@alvermark.net X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[alvermark.net:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 9/6/21 8:21 PM, Cy Schubert wrote: > In message <2780735.SSXfckUlLJ@sigill.theweb.org.ua>, "Oleg V. Nauman" > writes: >> On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: >>> One last favour to ask, can you try this with the wpa_supplicant-devel >>> port, please? I'm trying to narrow down if this is related to the options >>> in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the >>> same using wpa_supplicant-devel, this tells me to look at the code instead >>> of Makefiles. >>> >>> I can reproduce the service netif restart problem using the old >>> wpa_supplicant 2.9, so at least here there is no change in behaviour. >>> Though on my sandbox machine the ifconfig dow/up is not required -- though >>> even the older wpa_supplicant 2.9 behaves the same on my laptop, (no >>> regression experienced here). >>> >>> To help point to either Makefile.inc or contrib/wpa, can you please try the >>> wpa_supplicant-devel port. This will tell me where to look next. >> I can confirm that wpa_supplicant from security/wpa_supplicant-devel port >> demonstrating the same behavior as wpa_supplicant from base - "ifconfig wlan0 >> >> down ; sleep 5 ; ifconfig wlan0 up" mitigate wlan association issue. > Thank you. > > This is an issue that I'll need to chase down with our upstream. In the > mean time while work on this/bring it to upstream's attention this should > circumvent the issue: > > diff --git a/libexec/rc/rc.d/wpa_supplicant b/libexec/rc/rc.d/wpa_supplicant > index 8a86fec90e4d..cfe5f1ab27c6 100755 > --- a/libexec/rc/rc.d/wpa_supplicant > +++ b/libexec/rc/rc.d/wpa_supplicant > @@ -12,6 +12,7 @@ > > name="wpa_supplicant" > desc="WPA/802.11i Supplicant for wireless network devices" > +start_postcmd="wpa_poststart" > rcvar= > > ifn="$2" > @@ -27,6 +28,12 @@ is_ndis_interface() > esac > } > > +wpa_poststart() { > + ifconfig ${ifn} down > + sleep 3 > + ifconfig ${ifn} up > +} > + > if is_wired_interface ${ifn} ; then > driver="wired" > elif is_ndis_interface ${ifn} ; then > > I'll have more questions later (need to start working on another job) but > I'd like to learn more about your configuration to understand why it works > at boot for myself and phlip@ and not for you and the others here on > -current who have experienced the same issue. Understanding what triggers > this will go a long way to resolving it. > > (cc'd philip@) > > BTW, my laptop is configured so that wlan0 (iwn0) and bge0 are members of > lagg0. Whereas on my sandbox wlan0 (ath0) is used directly. > Hi, I have the same. wlan0 does not associate after boot. (This is with iwm, AC 9260) My workaround is simply 'ifconfig wlan0 up'. After a few seconds wpa_supplicant associates and another few secods later I have a DHCP IP address. Jakob From nobody Tue Sep 7 08:29:11 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8BDD017A36A9 for ; Tue, 7 Sep 2021 08:29:32 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "vtr.rulingia.com", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3djS0KHfz4SNd for ; Tue, 7 Sep 2021 08:29:31 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (2001-44b8-31fc-0d00-acf2-4588-8a2b-0f2c.static.ipv6.internode.on.net [IPv6:2001:44b8:31fc:d00:acf2:4588:8a2b:f2c]) by vtr.rulingia.com (8.16.1/8.15.2) with ESMTPS id 1878THcN053056 (version=TLSv1.3 cipher=AEAD-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 7 Sep 2021 18:29:22 +1000 (AEST) (envelope-from peter@rulingia.com) DKIM-Filter: OpenDKIM Filter v2.10.3 vtr.rulingia.com 1878THcN053056 X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.16.1/8.16.1) with ESMTPS id 1878TBFH060958 (version=TLSv1.3 cipher=AEAD-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 7 Sep 2021 18:29:11 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.16.1/8.16.1/Submit) id 1878TBN8060957; Tue, 7 Sep 2021 18:29:11 +1000 (AEST) (envelope-from peter) Date: Tue, 7 Sep 2021 18:29:11 +1000 From: Peter Jeremy To: Karel Gardas Cc: current@freebsd.org Subject: Re: Install to ZFS root is using device names hence failing when device tree is changed. Message-ID: References: <73602bc2-44d9-f45e-e91e-fb0bd30dd640@gmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OT7cbrfI1ovS+ZD8" Content-Disposition: inline In-Reply-To: <73602bc2-44d9-f45e-e91e-fb0bd30dd640@gmail.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp X-Rspamd-Queue-Id: 4H3djS0KHfz4SNd X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --OT7cbrfI1ovS+ZD8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2021-Sep-06 17:45:31 +0200, Karel Gardas wrote: >just installed 14-current snapshot from 2.9. on uefi amd64 machine.=20 >Installed from USB memstick which was detected as da0 into the ssd=20 >hanging on usb3 in external enclosure which was detected as da1. > >ZFS root pool is then using /dev/da1p3 as swap and /dev/da1p1 as=20 >/boot/efi and probably also something as root zpool. > >Anyway, expected thing happen. When I pulled out USB stick identified as= =20 >da0 on reboot, the drive on USB3 switch from da1 to da0 and result is=20 >unbootable system with complains about various /dev/da1xx drives missing= =20 >for swap efi boot etc. Can you give more details about exactly what the errors and when they occur during the boot cycle. In particular: * Low-level boot (anything prior to the FreeBSD kernel) knows nothing about da0 or da1, so any problems there are associated with your BIOS config, not FreeBSD. * The swap partition will, by default, appear as a hard-wired device name in /etc/fstab - that will definitely need updating. This will prevent the "swapon" working but won't prevent the boot. * ZFS doesn't care about device names - it looks for ZFS labels on all possible devices. --=20 Peter Jeremy --OT7cbrfI1ovS+ZD8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAmE3ItBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzS77hAAnereonMj6kw09hRqbStQbnqlreI/Nzbl3+jSzUKZXr3Y0Tl0zrDeVrxG 3yJu8L7JnYfgDOIDRCiiHSjZeMdaGjwVNBxNBNuVQDA4l8wedU7Fn5eHX8GEIWG1 dW4j6k+WONpbT3rlr4uztjUxDLeLuCpEaGAtEFXPYi5C4ZH18mZbg0SEeQjyJFaN xupWgFXGULjM6IKFB760e7hfvHqqVXi6pTTlv2N3OMN8p0hDr94300hTiKgUJA7U ymTtoOO8k3uN4ke0cRjp8Imvhjr7zonePrK1MhIKOiyiWeSXQ9uULN6WVm9lSv/J 6mlyERvtgtkbDSREij3zeWNeN0XUwgpcpBgodWuk2uxUqrSfZb5cAgrVGdcF0mgt EFvP5KMWC4lyXkLMDbXs+ZNGYidHd+nP/dUCqe+sAo2XDgOQk7wl+Np580ydxpJb ir12S4M2tWa6/qJMjGjocZ5Z+WyhrsruzyJ8/IBed/g7spnCzslTiT1IO5qF2XDw H5fZqTdA3TrZhYVShsEcY42H45Md+Q6kWzZaslYOtA838nD2ay2XNdL2coZchjVk IC7Jvo/HgA+RnJ1tWM1UB0Lxh0eGgwmxUJQAU1SZVGIo9plZenMd7Irvvj5cpOHH pwTXmEXoftZpoVjM0VPyNIvKhIq74ydoAcymzKEtNGRCUtuhzws= =D/dt -----END PGP SIGNATURE----- --OT7cbrfI1ovS+ZD8-- From nobody Tue Sep 7 09:16:49 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 53AA3179C55F for ; Tue, 7 Sep 2021 09:16:51 +0000 (UTC) (envelope-from theraven@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3fm31tSxz4lcP for ; Tue, 7 Sep 2021 09:16:51 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 1A5452C75F for ; Tue, 7 Sep 2021 09:16:51 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id B23902C91D for ; Tue, 7 Sep 2021 10:16:50 +0100 (BST) Subject: Re: Move the Handbook into source tree To: freebsd-current@freebsd.org References: From: David Chisnall Message-ID: Date: Tue, 7 Sep 2021 10:16:49 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N Hi, I think there are two conflated things here: - Moving the handbook into the source tree. - Creating branches in the handbook that track particular releases. The first one is largely irrelevant to anyone other than people contributing to the handbook, so I'll focus on the second: This is quite an easy way of having a per-release snapshot but it means that the handbook will diverge for different releases over time. If the new docs are documenting things that are new, that's fine, but if new docs are added to -CURRENT for things in a release, then they will need to follow the same MFC process as code flowing from current to releases, which brings up the potential of merge conflicts and so on. This is made even more complex in cases where code is MFC'd. Typically (unfortunately) docs are added to the handbook after a feature is committed and so things will need to be MFC'd at the same time as other features are MFC'd or later if they're written after the original MFC. I see two possible workflows, the current and the proposed one, both of which have disadvantages: - With the current workflow, you need to explicitly track which release things apply to in the document. - With your proposed workflow, you need to explicitly track which release things apply to by merging them at the correct time. It's not clear to me that either of these is necessarily easier than the other. David On 07/09/2021 08:01, Mehmet Erol Sanliturk wrote: > Dear All , > > in many of my messages to FreeBSD mailing lists I am mentioning the > following view : > > "Please move the Handbook into source tree , and > Maintain it with respect to current release without mixing sliding > releases : If you do this , > maintenance of a correct Handbook is IMPOSSIBLE because maintenance of > associated IF statements about releases . > " > > When we look at the following web pages , we see the following : > > https://www.freebsd.org/cgi/man.cgi > FreeBSD Manual Pages > > In the second box of "All sections" line , there are lines about all of > the FreeBSD releases > with many more other systems . > > In spite of this , in the following page : > > https://docs.freebsd.org/en/books/handbook/ > FreeBSD Handbook > The FreeBSD Documentation Project > > > " > Abstract > > Welcome to FreeBSD! This handbook covers the installation and day to day > use of > FreeBSD 13.0-RELEASE, FreeBSD 12.2-RELEASE and FreeBSD 11.4-RELEASE. ... > " > > A Handbook which ( for me , exactly , for the others , perhaps ) with many > errors ... > > > I think that , it is NOT extraordinarily a difficult process to move the > Handbook into source > tree and maintaining it with respect to per release and insert into the > above web page a part > similar to the manual pages to display the requested Handbook with respect > to releases . > In the present case , previous handbooks are lost , because of the > difficulty of finding them . > > Thank you very much and my best wishes for you and humanity in these > pandemic days ... > > > Mehmet Erol Sanliturk > From nobody Tue Sep 7 09:34:13 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7B06317A7339 for ; Tue, 7 Sep 2021 09:34:17 +0000 (UTC) (envelope-from gardask@gmail.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3g890frvz4snq for ; Tue, 7 Sep 2021 09:34:17 +0000 (UTC) (envelope-from gardask@gmail.com) Received: by mail-ej1-x62b.google.com with SMTP id bt14so18456067ejb.3 for ; Tue, 07 Sep 2021 02:34:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=0YU2jwlMYChcmCwWFsR+gQm8O5ftYkSf15drpaKcE0s=; b=dVBs5x7/0sBskbs6M8+mSoT9a5upkIMeBBO74+qkZ/3OcA1JkudA3w6qu7F9AyLgnE NbhbM61G0I1PKH7J9l/KQ9Hlz6gxofDHBzeijkfWVHLh9RaS9SkxZFpgbH4KmEHpm2WQ zo3R4Si3JTEaUViG3+BbiL5QkxYNP3AW3n0ZwMD9CCCDZLT4nCOrPn2fAnD6nfFzhu1V EfLIoADxIl1rUhagtTkI2bZVvtbuCuWo8vIsHIgGFcdNz0oZIYyIqBQC7y2rnTanzAbw PJd9yNVZIwp8r67Xlg7lIJacRX0sCv8Eou1ezXU6w0sC+Q1DCiYFV7XHkvy93kvNiWvC 8W+A== 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-language :content-transfer-encoding; bh=0YU2jwlMYChcmCwWFsR+gQm8O5ftYkSf15drpaKcE0s=; b=KYJREH0ALyBCV2ouw1fJYeJOlElPvuGq+xoXCK8/n0LsfVGDxF6jrtp1xTau161Rrf cFKHP951QIJIIX2VUDCdu9IG0g1OmiI5xStJl4YLdfFDFzF/Za0i7WAKEI1LiFBe6sDM 88vSjd5OezguQDimWTTg7TE6bwFpFLfZIHD3rqCklIu+iklToDNsTQQ7jdAqXWaOusMI FeN/f0h9J0jCZ4hb7OEH22bOjnElJ2AuUhFFc3V6fQ0dOmA54XPPuelfqV4f7IMuVQPv chQMuT0vHDz85mp6VrWgtAR8nw1+fqoj3M3G8xp4TkllJ9gL5Re5g738nFcfaWqliYvs WHSw== X-Gm-Message-State: AOAM5309gnXtLcZMe4E/vtr9Jac3CUh5S8RKJ9wj8g0PmvZU2mSDhIS2 yxxsxD+Yv/ZedxpZH/eG4qmCAQIm0rU= X-Google-Smtp-Source: ABdhPJyN7gBNog32d5AU5Gm9l+9Czn4RoTJNrPDDEE/bfRQ2GafwvC2WvHCGcTBHfXovGtqnp8l6AA== X-Received: by 2002:a17:906:6808:: with SMTP id k8mr18226667ejr.138.1631007254586; Tue, 07 Sep 2021 02:34:14 -0700 (PDT) Received: from [10.0.30.5] ([31.47.99.1]) by smtp.gmail.com with ESMTPSA id q15sm5218763ejx.3.2021.09.07.02.34.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Sep 2021 02:34:14 -0700 (PDT) Subject: Re: Install to ZFS root is using device names hence failing when device tree is changed. To: Peter Jeremy Cc: current@freebsd.org References: <73602bc2-44d9-f45e-e91e-fb0bd30dd640@gmail.com> From: Karel Gardas Message-ID: <68531cbc-87a9-7a1a-8de5-922b2402de02@gmail.com> Date: Tue, 7 Sep 2021 11:34:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H3g890frvz4snq X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 9/7/21 10:29 AM, Peter Jeremy wrote: > On 2021-Sep-06 17:45:31 +0200, Karel Gardas wrote: >> just installed 14-current snapshot from 2.9. on uefi amd64 machine. >> Installed from USB memstick which was detected as da0 into the ssd >> hanging on usb3 in external enclosure which was detected as da1. >> >> ZFS root pool is then using /dev/da1p3 as swap and /dev/da1p1 as >> /boot/efi and probably also something as root zpool. >> >> Anyway, expected thing happen. When I pulled out USB stick identified as >> da0 on reboot, the drive on USB3 switch from da1 to da0 and result is >> unbootable system with complains about various /dev/da1xx drives missing >> for swap efi boot etc. > > Can you give more details about exactly what the errors and when they > occur during the boot cycle. In particular: > * Low-level boot (anything prior to the FreeBSD kernel) knows nothing > about da0 or da1, so any problems there are associated with your > BIOS config, not FreeBSD. Low level boot is all right since kernel is booting. What's broken is root/zfs mount and swap enablement. > * The swap partition will, by default, appear as a hard-wired device > name in /etc/fstab - that will definitely need updating. This will > prevent the "swapon" working but won't prevent the boot. ACK. Good to know. > * ZFS doesn't care about device names - it looks for ZFS labels on all > possible devices. I think you are wrong here. Let's see zpool status: karel@freebsd:~ $ zpool status pool: zroot state: ONLINE config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 da1p4 ONLINE 0 0 0 errors: No known data errors Now, let's reboot and see error on serial console when install da0 is not attached: Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.5: at usbus0 umass0 numa-domain 0 on uhub1 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:9:0: Attached to scbus9 da0 at umass-sim0 bus 0 scbus9 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 2017010000C7 da0: 400.000MB/s transfers da0: 238475MB (488397168 512 byte sectors) da0: quirks=0x2 Dual Console: Serial Primary, Video Secondary No suitable dump device was found. Setting hostuuid: 8cdf33eb-6866-42ae-a49d-ae7ee4c0c33c. Setting hostid: 0xdf6467d8. no pools available to import swapon: /dev/da1p3: No such file or directory Starting file system checks: Can't open `/dev/da1p1' /dev/da1p1: UNEXPECTED INCONSISTENCY; RUN fsck_msdosfs MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: msdosfs: /dev/da1p1 (/boot/efi) Automatic file system check failed; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! 2021-09-07T11:23:23.710549+02:00 - init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: So this is problematic /efi parition, if I remove it from the /etc/fstab I get this boot: .... Wow! It boots well, so you were indeed right. Checking zpool status reveals: karel@freebsd:~ $ zpool status pool: zroot state: ONLINE config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 da0p4 ONLINE 0 0 0 errors: No known data errors karel@freebsd:~ $ so indeed, ZFS on FreeBSD is similar to this on Solaris. On Linux I got different experience (e.g. /dev/sdaX hardwired and failing to boot) hence I've been in impression that this is also a case of FreeBSD when code is shared thorough OpenZFS project. Great to know and thanks for kicking me into it. So just /efi partition mount is the culprit here... Thanks! Karel From nobody Tue Sep 7 10:49:14 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0CD7417A8BD2 for ; Tue, 7 Sep 2021 10:49:52 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3hqM6hBdz3pC5; Tue, 7 Sep 2021 10:49:51 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ua1-x929.google.com with SMTP id g2so5323737uad.4; Tue, 07 Sep 2021 03:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=APKxKwY2oRB335uXudLuiZhm2fBTlAMxC0IE4rLL838=; b=UqwIWg+TaiK7aZ4CQF0fITVKJ2OxRl2hWm6DVR6/xdXJJBPHWO3cJYM3QW2H3ke+OS 1HMV+tzJRHwQTMllmdL/dB9hLV9K/BlA85sUJrn7CUR1zWV85VeOtQ01aUw1iVat6tLl OiXMDQ3wU4k3mSG3ECghTemmN1Fw7i4FTu1j5YWNRN9YVGkX0/umKiCfSq6SNX6JXZyR KjELv6w50D67qoeooMeaWk+dxA4MB2PVyQYrvYTFUvzgd0W3cDCfz+SgfXEfGL4TAAZe MLV2xthdNjFmJUSEh9mmhovkHB8ELLMi3JtfHuNbK3Mvz1G9xS+EI5/VzLCVLU0Nnu1+ V05g== 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=APKxKwY2oRB335uXudLuiZhm2fBTlAMxC0IE4rLL838=; b=Jk1YwSagizH9D2bFKx/fFXwTXC6/XlIFu673/W6lO90PB6ShsrqFy1fiKBoErCoa6U VzhcLRk1ucUudODQhhanT42Mx5WsueoNNdne1m8w5h7nx7rESKL9ldtxqBykT55zd2Do XEzVxOfrI4rL0yIK4kt/l5PZmi4ZenksxuvSw0EWOP8OrGbHuDo9c5uRYZm+aw7Tn+mh figXotRwBDF63jBPkRUZ1zh5yE2nj2pTHoEEMtI2/vzxWxZTI6v5rEB4/AxvEzU1wRlw wehHSlhVHFS+DXMcyHL1mqs4pgSV1EHI9qBLFrfZo5Hw9VLBBU7oPsvV1cdYIGbriAar KB8g== X-Gm-Message-State: AOAM532ufBB3iWVvEEdr4hv2I9SW+D1C8vooHInvSK7aq9ine76iRYym rqTLiT3lkq61Rb3LfAFdXHUS3RW0sk7u1DuwOJPW6TzuJag= X-Google-Smtp-Source: ABdhPJyacGxwPuuD3zSJQiwEAzoF/eCGU8ItoLgUWhaxKaLM4SN9KAgmHzeBbHCUsCqsQbmRh7GC+rppegnhfvr3x1o= X-Received: by 2002:ab0:1323:: with SMTP id g32mr7796391uae.63.1631011791064; Tue, 07 Sep 2021 03:49:51 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mehmet Erol Sanliturk Date: Tue, 7 Sep 2021 13:49:14 +0300 Message-ID: Subject: Re: Move the Handbook into source tree To: David Chisnall Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000006e526305cb658635" X-Rspamd-Queue-Id: 4H3hqM6hBdz3pC5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --0000000000006e526305cb658635 Content-Type: text/plain; charset="UTF-8" On Tue, Sep 7, 2021 at 12:17 PM David Chisnall wrote: > Hi, > > I think there are two conflated things here: > > - Moving the handbook into the source tree. > - Creating branches in the handbook that track particular releases. > > The first one is largely irrelevant to anyone other than people > contributing to the handbook, so I'll focus on the second: > > This is quite an easy way of having a per-release snapshot but it means > that the handbook will diverge for different releases over time. If the > new docs are documenting things that are new, that's fine, but if new > docs are added to -CURRENT for things in a release, then they will need > to follow the same MFC process as code flowing from current to releases, > which brings up the potential of merge conflicts and so on. > > This is made even more complex in cases where code is MFC'd. Typically > (unfortunately) docs are added to the handbook after a feature is > committed and so things will need to be MFC'd at the same time as other > features are MFC'd or later if they're written after the original MFC. > > I see two possible workflows, the current and the proposed one, both of > which have disadvantages: > > - With the current workflow, you need to explicitly track which > release things apply to in the document. > - With your proposed workflow, you need to explicitly track which > release things apply to by merging them at the correct time. > > It's not clear to me that either of these is necessarily easier than the > other. > > David > > My primary training is "Mathematics ( Option : Statistics and Operations Research ) , then Computer Engineering and Sciences . https://en.wikipedia.org/wiki/Operations_research Operations research When we think in this context , propositions are ( NOT EXACT ) but as alternatives or an alternative . It is possible to think of moving the Handbook into the source tree because manual pages are within the source tree . It may even be possible to construct some parts of the Handbook by utilizing the manual pages . In that way , errors due to repetitions will be eliminated easily . Therefore the main problem is not the way of the implementation of separate handbooks but maintaining separate handbooks and achieving correct and usable information in them . My proposition is also considering "branching" of a new release . If the Handbook is directly within the source tree or it is coupled into it in such a way that branching covers it . I think implementers will make their own decisions in the best way to realize it successfully and easily . Mehmet Erol Sanliturk > On 07/09/2021 08:01, Mehmet Erol Sanliturk wrote: > > Dear All , > > > > in many of my messages to FreeBSD mailing lists I am mentioning the > > following view : > > > > "Please move the Handbook into source tree , and > > Maintain it with respect to current release without mixing sliding > > releases : If you do this , > > maintenance of a correct Handbook is IMPOSSIBLE because maintenance > of > > associated IF statements about releases . > > " > > > > When we look at the following web pages , we see the following : > > > > https://www.freebsd.org/cgi/man.cgi > > FreeBSD Manual Pages > > > > In the second box of "All sections" line , there are lines about all of > > the FreeBSD releases > > with many more other systems . > > > > In spite of this , in the following page : > > > > https://docs.freebsd.org/en/books/handbook/ > > FreeBSD Handbook > > The FreeBSD Documentation Project > > > > > > " > > Abstract > > > > Welcome to FreeBSD! This handbook covers the installation and day to day > > use of > > FreeBSD 13.0-RELEASE, FreeBSD 12.2-RELEASE and FreeBSD 11.4-RELEASE. ... > > " > > > > A Handbook which ( for me , exactly , for the others , perhaps ) with > many > > errors ... > > > > > > I think that , it is NOT extraordinarily a difficult process to move the > > Handbook into source > > tree and maintaining it with respect to per release and insert into the > > above web page a part > > similar to the manual pages to display the requested Handbook with > respect > > to releases . > > In the present case , previous handbooks are lost , because of the > > difficulty of finding them . > > > > Thank you very much and my best wishes for you and humanity in these > > pandemic days ... > > > > > > Mehmet Erol Sanliturk > > > > --0000000000006e526305cb658635-- From nobody Mon Sep 6 18:53:54 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AFC2017BC8C2; Tue, 7 Sep 2021 11:29:16 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3jhr3s9yz4X2l; Tue, 7 Sep 2021 11:29:16 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from kent.sdaoden.eu (kent.sdaoden.eu [10.5.0.2]) by sdaoden.eu (Postfix) with ESMTPS id A980F1605B; Mon, 6 Sep 2021 20:53:56 +0200 (CEST) Received: by kent.sdaoden.eu (Postfix, from userid 1000) id 8CC13F98; Mon, 6 Sep 2021 20:53:54 +0200 (CEST) Date: Mon, 06 Sep 2021 20:53:54 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Eric McCorkle Cc: freebsd-current@freebsd.org, Greg , FreeBSD Hackers Subject: Re: PAM module for loading ZFS keys on login Message-ID: <20210906185354.D5ymE%steffen@sdaoden.eu> In-Reply-To: References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> <20210906140137.iGt2J%steffen@sdaoden.eu> Mail-Followup-To: Eric McCorkle , freebsd-current@freebsd.org, Greg , FreeBSD Hackers User-Agent: s-nail v14.9.22-175-gc118a4a5c7 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Rspamd-Queue-Id: 4H3jhr3s9yz4X2l X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Eric McCorkle wrote in : ... >> This patch creates a new PAM module that will load a ZFS key upon a >> successful login: https://reviews.freebsd.org/D31844. It will use the >> user's auth token as the key argument to loading a ZFS encryption key on >> a user-specific ZFS data set. ... Without knowing about libzfs i personally was stunned about the simplicity of your patch, having read the upstream one. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Mon Sep 6 14:01:37 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3FB6917BCB87; Tue, 7 Sep 2021 11:29:17 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3jhr3k8bz4X5P; Tue, 7 Sep 2021 11:29:16 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from kent.sdaoden.eu (kent.sdaoden.eu [10.5.0.2]) by sdaoden.eu (Postfix) with ESMTPS id 7B9C716056; Mon, 6 Sep 2021 16:01:39 +0200 (CEST) Received: by kent.sdaoden.eu (Postfix, from userid 1000) id 8D281F7B; Mon, 6 Sep 2021 16:01:37 +0200 (CEST) Date: Mon, 06 Sep 2021 16:01:37 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: freebsd-current@freebsd.org Cc: Eric McCorkle , Greg , FreeBSD Hackers Subject: Re: PAM module for loading ZFS keys on login Message-ID: <20210906140137.iGt2J%steffen@sdaoden.eu> In-Reply-To: References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> Mail-Followup-To: freebsd-current@freebsd.org, Eric McCorkle , Greg , FreeBSD Hackers User-Agent: s-nail v14.9.22-175-gc118a4a5c7 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4H3jhr3k8bz4X5P X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of steffen@sdaoden.eu designates 217.144.132.164 as permitted sender) smtp.mailfrom=steffen@sdaoden.eu X-Spamd-Result: default: False [-2.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+a:c]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sdaoden.eu]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_CONTAINS_FROM(1.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N Eric McCorkle wrote in : |Interesting, I wasn't aware of the upstream module. I'd say that's It's existence was the reason i have readded (now optional, and a tad different) session support for my pam_xdg PAM module, because i was thinking that, if such a many-eyes-seen thing of a software project that claims to be and aims at being enterprise, ships such a terrible and terribly broken thing, then i can also offer session tracking. But my manual at least states CAVEATS On Unix systems any =E2=80=9Cdaemonized=E2=80=9D program or script i= s reparented to the program running with PID 1, most likely leaving the PAM user session without PAM recognizing this. Yet careless such code may hold or ex= pect availability of resources of the session it just left, truly perform= ing cleanup when sessions end seems thus unwise. Since so many PAM modu= les do support session tracking and cleanup pam_xdg.so readded optional = sup=E2=80=90 port for this. But the real solution would be PAM session tracking in-kernel, somehow, wouldn't it? Also, on FreeBSD and OpenPAM many separate files exist in /etc/pam.d for things which might open a session, whereas linuxpam at least has /etc/pam.d/common-session; it has many common- things in fact, and in /etc/pam.d/sshd i for example see # # /etc/pam.d/sshd - openssh service module configuration # auth include common-auth account include common-account password include common-password session include common-session --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Tue Sep 7 11:37:44 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6211517C1B4E; Tue, 7 Sep 2021 11:37:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3jtt0Fv6z4cyC; Tue, 7 Sep 2021 11:37:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 187Bbinv033457 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 7 Sep 2021 14:37:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 187Bbinv033457 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 187Bbiin033455; Tue, 7 Sep 2021 14:37:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 7 Sep 2021 14:37:44 +0300 From: Konstantin Belousov To: freebsd-current@freebsd.org, FreeBSD Hackers Subject: Re: PAM module for loading ZFS keys on login Message-ID: References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> <20210906140137.iGt2J%steffen@sdaoden.eu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210906140137.iGt2J%steffen@sdaoden.eu> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.5 X-Spam-Checker-Version: SpamAssassin 3.4.5 (2021-03-20) on tom.home X-Rspamd-Queue-Id: 4H3jtt0Fv6z4cyC X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-1.40 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; R_SPF_SOFTFAIL(0.00)[~all]; NEURAL_SPAM_SHORT(0.59)[0.590]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N On Mon, Sep 06, 2021 at 04:01:37PM +0200, Steffen Nurpmeso wrote: > Eric McCorkle wrote in > : > |Interesting, I wasn't aware of the upstream module. I'd say that's > > It's existence was the reason i have readded (now optional, and > a tad different) session support for my pam_xdg PAM module, > because i was thinking that, if such a many-eyes-seen thing of > a software project that claims to be and aims at being enterprise, > ships such a terrible and terribly broken thing, then i can also > offer session tracking. But my manual at least states > > CAVEATS > On Unix systems any “daemonized” program or script is reparented to the > program running with PID 1, most likely leaving the PAM user session > without PAM recognizing this. Yet careless such code may hold or expect > availability of resources of the session it just left, truly performing > cleanup when sessions end seems thus unwise. Since so many PAM modules > do support session tracking and cleanup pam_xdg.so readded optional sup‐ > port for this. If you use reaper facility, that would ensure that all (grand-)children of your session are always reparented to the reaper and not to init. In other words, you can reliable know when the session ends. See procctl(2) PROC_REAP_* commands. I believe that reaper-like functionality is available on all current Unix-like systems, even if under different names. > > But the real solution would be PAM session tracking in-kernel, > somehow, wouldn't it? > Also, on FreeBSD and OpenPAM many separate files exist in > /etc/pam.d for things which might open a session, whereas linuxpam > at least has /etc/pam.d/common-session; it has many common- things > in fact, and in /etc/pam.d/sshd i for example see > > # > # /etc/pam.d/sshd - openssh service module configuration > # > > auth include common-auth > > account include common-account > > password include common-password > > session include common-session > > --steffen > | > |Der Kragenbaer, The moon bear, > |der holt sich munter he cheerfully and one by one > |einen nach dem anderen runter wa.ks himself off > |(By Robert Gernhardt) > From nobody Tue Sep 7 12:16:41 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 14DA317A3742 for ; Tue, 7 Sep 2021 12:16:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3klh5Qtvz4vcW for ; Tue, 7 Sep 2021 12:16:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.16.1/8.15.2) with ESMTP id 187CGgbE033077; Tue, 7 Sep 2021 12:16:42 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.16.1/8.16.1/Submit) id 187CGfZ9033076; Tue, 7 Sep 2021 05:16:41 -0700 (PDT) (envelope-from david) Date: Tue, 7 Sep 2021 05:16:41 -0700 From: David Wolfskill To: Jakob Alvermark Cc: Cy Schubert , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Message-ID: Mail-Followup-To: David Wolfskill , Jakob Alvermark , Cy Schubert , current@freebsd.org References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KFILaPCwQuQzS74/" Content-Disposition: inline In-Reply-To: <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> X-Rspamd-Queue-Id: 4H3klh5Qtvz4vcW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --KFILaPCwQuQzS74/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > ...=20 > wlan0 does not associate after boot. (This is with iwm, AC 9260) >=20 > My workaround is simply 'ifconfig wlan0 up'. >=20 > After a few seconds wpa_supplicant associates and another few secods=20 > later I have a DHCP IP address. > .... I just tried that (running main-n249159-bb61ccd530b7), and that (also) works for me -- in case that data point is of use. Peace, david --=20 David H. Wolfskill david@catwhisker.org Life is not intended to be a zero-sum game. See https://www.catwhisker.org/~david/publickey.gpg for my public key. --KFILaPCwQuQzS74/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAmE3WChfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PcmKCggAkPao7p4Dfdqkrb4hURk2j1+bsGVJC7ugudsx39dDSpFHxHPme9RnuZBd Hh/6NwcZDwa/8DkMFFBwmIUrDa/4MszNa5mWEJMdtB4w1Ii72HM3mVmkDF8kKwBV qhoJuCFfZcqrRE2gwl0EkrBACqMNJLwVzPTU3d6h/7mdQBXvGfs8HInXcKJyjvrO eyJzcTa/zzDfe30E30A8ZEkBLdWryaLAl9YaXWFPVJW58E2oRXaFIoq/h+quxYja E+jKdx5NObwxUTN7MyPJ8uoF+0JmGQfqXQ1aDaUYyT/wlpbvDtf20BMSjqhe8J6M e7xaWKsigED6t/jZ+8wc3xWNp8pRgg== =+F6q -----END PGP SIGNATURE----- --KFILaPCwQuQzS74/-- From nobody Tue Sep 7 12:19:58 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C088E17A6C55 for ; Tue, 7 Sep 2021 12:20:07 +0000 (UTC) (envelope-from SRS0=+ZyR=N5=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3kqV1H60z3Dpj; Tue, 7 Sep 2021 12:20:06 +0000 (UTC) (envelope-from SRS0=+ZyR=N5=klop.ws=ronald-lists@realworks.nl) Date: Tue, 7 Sep 2021 14:19:58 +0200 (CEST) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=klop.ws; s=rw1; t=1631017198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=g2ww7D03MSp8W87uhjauwMIjg7M6Ce6qMFOL1roUnWQ=; b=evPiN+6GBrNIWmTH8cD7UPoX8/X++DpX8Nq+GCX3g3zvojrZ9Z7YGt8Ei4vJqHXHgqZk31 a2MdUnag8dnIx0Cw== From: Ronald Klop To: David Chisnall Cc: freebsd-current@freebsd.org Message-ID: <998976926.153.1631017198576@mailrelay> In-Reply-To: References: Subject: Re: -CURRENT compilation time List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_152_1487084900.1631017198448" X-Mailer: Realworks (575.798.39f740e) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4H3kqV1H60z3Dpj X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw1 header.b=evPiN+6G; dmarc=pass (policy=none) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw1]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DKIM_TRACE(0.00)[klop.ws:+]; RCPT_COUNT_TWO(0.00)[2]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[194.109.157.24:from]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; RWL_MAILSPIKE_POSSIBLE(0.00)[194.109.157.24:from]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; TAGGED_FROM(0.00)[ZyR=N5=klop.ws=ronald-lists]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=@realworks.nl] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y ------=_Part_152_1487084900.1631017198448 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: David Chisnall Datum: maandag, 6 september 2021 11:43 Aan: freebsd-current@freebsd.org Onderwerp: Re: -CURRENT compilation time > > On 06/09/2021 09:08, Jeremie Le Hen wrote: > > Compiling C++ seems > > extremely CPU heavy and this is made worse by the fact LLVM is built > > twice (once for build/cross tools, once for the actual world). > > Note that you need to build LLVM twice only if you are actively debugging LLVM reproduceable deployment images. You actually don't need to build it at all, you can use an external toolchain to skip the first build and you can compile WITHOUT_TOOLCHAIN to avoid building the version that's installed and then install a toolchain from packages: > > https://wiki.freebsd.org/ExternalToolchain > > David > > > > > Hi, I'm very interested in a base without llvm because of compile times. So I tried this in a jail with 14-current and pkg llvm12 installed. /etc/make.conf: WITHOUT_TOOLCHAIN=yes CROSS_TOOLCHAIN=llvm12 Buildworld, installworld and etcupdate went fine. "yes | make delete-old" removes the toolchain from base. Afterwards you can't do buildworld anymore. # make buildworld sh: cc: not found make: "/home/ronald/dev/freebsd/share/mk/bsd.compiler.mk" line 200: warning: "cc -v 2>&1 | grep "gcc version"" returned non-zero status make: "/home/ronald/dev/freebsd/share/mk/bsd.compiler.mk" line 204: Unable to determine compiler type for CC=cc. Consider setting COMPILER_TYPE. What am I missing? Regards, Ronald. ------=_Part_152_1487084900.1631017198448-- From nobody Tue Sep 7 12:30:10 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2112B17AD923; Tue, 7 Sep 2021 12:30:13 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3l386TDbz3Klk; Tue, 7 Sep 2021 12:30:12 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from kent.sdaoden.eu (kent.sdaoden.eu [10.5.0.2]) by sdaoden.eu (Postfix) with ESMTPS id B027716056; Tue, 7 Sep 2021 14:30:11 +0200 (CEST) Received: by kent.sdaoden.eu (Postfix, from userid 1000) id 28864FB1; Tue, 7 Sep 2021 14:30:10 +0200 (CEST) Date: Tue, 07 Sep 2021 14:30:10 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Konstantin Belousov Cc: freebsd-current@freebsd.org, FreeBSD Hackers Subject: Re: PAM module for loading ZFS keys on login Message-ID: <20210907123010.iuiKD%steffen@sdaoden.eu> In-Reply-To: References: <67F44CFE-2496-4B13-8583-8A80D9ED3A4A@unrelenting.technology> <20210906140137.iGt2J%steffen@sdaoden.eu> Mail-Followup-To: Konstantin Belousov , freebsd-current@freebsd.org, FreeBSD Hackers User-Agent: s-nail v14.9.22-175-gc118a4a5c7 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4H3l386TDbz3Klk X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N Konstantin Belousov wrote in : |On Mon, Sep 06, 2021 at 04:01:37PM +0200, Steffen Nurpmeso wrote: |> Eric McCorkle wrote in |> : |>|Interesting, I wasn't aware of the upstream module. I'd say that's |>=20 |> It's existence was the reason i have readded (now optional, and |> a tad different) session support for my pam_xdg PAM module, |> because i was thinking that, if such a many-eyes-seen thing of |> a software project that claims to be and aims at being enterprise, |> ships such a terrible and terribly broken thing, then i can also |> offer session tracking. But my manual at least states |>=20 |> CAVEATS |> On Unix systems any =E2=80=9Cdaemonized=E2=80=9D program or scri= pt is reparented \ |> to the |> program running with PID 1, most likely leaving the PAM user \ |> session |> without PAM recognizing this. Yet careless such code may \ ... |If you use reaper facility, that would ensure that all (grand-)children |of your session are always reparented to the reaper and not to init. In |other words, you can reliable know when the session ends. See |procctl(2) PROC_REAP_* commands. | |I believe that reaper-like functionality is available on all current |Unix-like systems, even if under different names. Ah it is really, really cool what becomes possible (everywhere;)! So (Open)PAM should maybe (configurably) enable this does for all programs which actually use modules which use session management. #?0|kent:free-src.git$ git grep PROC_REAP_ origin/main | grep -vE '\.2:|:tests/' | sed -E 's/^(.+:.+):.+$/\1/' | sort -u origin/main:sys/compat/freebsd32/freebsd32_misc.c origin/main:sys/kern/kern_procctl.c origin/main:sys/sys/procctl.h origin/main:usr.bin/timeout/timeout.c I do not have systemd here, but on Linux situation seems similar: #?0|kent:x$ tar -xf /x/balls/shadow/shadow-4.8.1.tar.xz #?0|kent:x$ grep -r REAP shadow-4.8.1/ #?1|kent:x$ tar -xf /x/balls/linux-pam/Linux-PAM-1.5.1.tar.xz #?0|kent:x$ grep -r REAP Linux-PAM-1.5.1/ [yes, pam_unix defines UNIX_REAP, not PR_SET_CHILD_SUBREAPER] #?0|kent:x$ tar -xf /x/balls/openssh/openssh-8.7p1.tar.gz #?0|kent:x$ grep -r REAP openssh-8.7p1/ #?1|kent:x$ Maybe this is why systemd flies, i would guess it does, and this gives you then reliable session management. I did not really know that actually, .. consciously. This is really cool, but still also that upstream OpenZFS module, and my one, and who knows which other PAM module also, perform really bad sad and bitter session counting via counter files, ... but that is a different topic. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Tue Sep 7 13:51:21 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6EC1317BBBAC for ; Tue, 7 Sep 2021 13:51:24 +0000 (UTC) (envelope-from theraven@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3mrr1DMmz4Tgb; Tue, 7 Sep 2021 13:51:24 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 050B02EE3F; Tue, 7 Sep 2021 13:51:24 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 5EB782C923; Tue, 7 Sep 2021 14:51:23 +0100 (BST) Subject: Re: -CURRENT compilation time To: Wolfram Schneider Cc: freebsd-current@freebsd.org References: From: David Chisnall Message-ID: Date: Tue, 7 Sep 2021 14:51:21 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 06/09/2021 20:34, Wolfram Schneider wrote: > With the option WITHOUT_TOOLCHAIN=yes the world build time is 2.5 > times faster (real or user+sys), down from 48 min to 19.5 min real > time. Note that building LLVM with the upstream CMake + Ninja build system is *significantly* faster on a decent multicore machine than the FreeBSD bmake-based in-tree version. One of the things I'd love to prototype if I had time is a CMake-based build system for FreeBSD so that we could get all of the tooling integration from the compile_commands.json, reuse LLVM's (and any other contrib things that use CMake) build system without having to recreate it, and be able to use ninja, to build. David From nobody Tue Sep 7 15:09:04 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5D24317A4F63 for ; Tue, 7 Sep 2021 15:46:12 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from wnew1-smtp.messagingengine.com (wnew1-smtp.messagingengine.com [64.147.123.26]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3qPG4P79z537h for ; Tue, 7 Sep 2021 15:46:10 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.west.internal (Postfix) with ESMTP id 9CD022B004D2 for ; Tue, 7 Sep 2021 11:09:35 -0400 (EDT) Received: from imap44 ([10.202.2.94]) by compute4.internal (MEProxy); Tue, 07 Sep 2021 11:09:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=50INiqxUvMjQpBck2j0Gqe+7E1Jpz6X MeIwcurBIqZg=; b=qVsdCdMI1qYQjmkSvYkbQtl4FE6kp2IHzVyRnEQlxo8T4TU ien0fIEzuZiuzgF6dBefVNl3c0tEpNMYKQn7O8CY+aZJBNDdxDp1DcA8bwOJRp0K 6tQJXxm77kQk5I0m09UbhSoZCQvCPs2bQBt9i3BKo90oTzW2lLdybw45N62swOvR YvIPxRoNl1A7o6J1+B+Am8f3ylPKZxY3ZFvEKHuY7rP8MBQNJROzEUGwnDVeMMAo 4tO0DNYJCmcnGMml6SORgmVLAtZCT/EKU9Xy5NVd6+bnk0bc5RV7Qy4ggjSd3Lrk tBEjNJLFngL1EoAkWVZCSvGiuBMgTrv1yRFHIng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=50INiq xUvMjQpBck2j0Gqe+7E1Jpz6XMeIwcurBIqZg=; b=dY1W3P/5KCWzG/yHpqlJ2t Xp2oSg8kqLdZ0uORTYu0ll/+E8cy1GPKB85RNKB82N+irTB4OUHCjROPktyi2uQN or2Jyh2lDcCDBWSXziu6sDoOY6WrP20r7uSaNzNrhjf13LVl3N3v8MQsUHA5EJFq xvp0eWZLNzkxuoQkmRHLOV5aWzOST4AFFn3IhD+MzeaiRp2T4zQrteA841tNyRhs 7zT6t2fx+citZ/zXsz/dAIlnNiTHMlYxGjKWy8Ijuln9wRmesReWfeq1Yqb1VdPe BvYSLlLiBfxUZ8nMjNKK93fMfTFZR0nzJ05sRIL7LFOroY+yK+0wVHLfAxFWfR2w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudefhedgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfffgrvhgvucevohhtthhlvghhuhgsvghrfdcuoegutghh sehskhhunhhkfigvrhhkshdrrghtqeenucggtffrrghtthgvrhhnpeekffefvdefteekff eggfffvdefuefguefhhffhudefvdetgfeileeujeffhedvjeenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegutghhsehskhhunhhkfigvrhhksh drrght X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0189DFA0AA4; Tue, 7 Sep 2021 11:09:24 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1126-g6962059b07-fm-20210901.001-g6962059b List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Message-Id: <8c172da5-f21c-4a01-ad38-e8cb2c102126@www.fastmail.com> In-Reply-To: References: Date: Tue, 07 Sep 2021 15:09:04 +0000 From: "Dave Cottlehuber" To: freebsd-current Subject: Re: -CURRENT compilation time Content-Type: text/plain X-Rspamd-Queue-Id: 4H3qPG4P79z537h X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=skunkwerks.at header.s=fm3 header.b=qVsdCdMI; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="dY1W3P/5"; dmarc=none; spf=pass (mx1.freebsd.org: domain of dch@skunkwerks.at designates 64.147.123.26 as permitted sender) smtp.mailfrom=dch@skunkwerks.at X-Spamd-Result: default: False [-3.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[skunkwerks.at:s=fm3,messagingengine.com:s=fm3]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEFALL_USER(0.00)[dch]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[skunkwerks.at]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[skunkwerks.at:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.26]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_WWW(0.50)[]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.26:from] X-ThisMailContainsUnwantedMimeParts: N On Tue, 7 Sep 2021, at 13:51, David Chisnall wrote: > One of the things I'd love to prototype if I had time is a CMake-based > build system for FreeBSD so that we could get all of the tooling > integration from the compile_commands.json, reuse LLVM's (and any other > contrib things that use CMake) build system without having to recreate > it, and be able to use ninja, to build. This would be a worthy FreeBSD foundation project IMHO. A+ Dave From nobody Tue Sep 7 16:51:37 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7BAFB17C3874 for ; Tue, 7 Sep 2021 16:51:56 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3rs8350lz3PYV for ; Tue, 7 Sep 2021 16:51:56 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: by mail-lf1-f43.google.com with SMTP id m28so20759597lfj.6 for ; Tue, 07 Sep 2021 09:51:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4GptLE+6/97K4RDvaYcvGhMFMh162wVOOhABQbcEHFg=; b=nsjBDRLW4vq/D1i97qpxqTnvwnoN7BGKLfz/eOynf1iDwAtWzCDrjJ+ouk/N9LmjHQ BfmbrEO02ANhutv4J2y8Rj3fpzeTZHCnE14Tm162DKQdpyTJioWqbQXA7Bn1jB7VW9xx tiDO60kEOahzBb3hC4kn7H2r2pzYPFC/E1jZ/W6ubjV9RBRJLrRIc3Qv//3B+5YztdWk ME4oXC2kriv+DtQ31hDV/nMOJQRRGRdRBWK0qeRhKwhAFbRbbnrvDejrd+bSdHz2arUP ClcdaywWl3z6MFo/ATW8uwq0canFIF0HcqHC6S6CSpFEo7SL2qV62EcJqT4CSL9cP/gf pYXA== X-Gm-Message-State: AOAM533LsVqw8qwARvC0xI0fDl0hgGYYaA9/IEE4YhkORgoU0bJHR83s s3nlZzUsRfkVxSvO+zYNLPMmzdL5L39gBtzRBdA= X-Google-Smtp-Source: ABdhPJzvSI0dlIQ1y+Zwkw6Dv/rTiPp/GLB8x9wSgfv+TQ0HDeDtdSKqUyRZ8+sP6SXkw2vbyZUcrgFo25Z5kTWmXbE= X-Received: by 2002:a05:6512:31c9:: with SMTP id j9mr5705511lfe.322.1631033508616; Tue, 07 Sep 2021 09:51:48 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Wolfram Schneider Date: Tue, 7 Sep 2021 18:51:37 +0200 Message-ID: Subject: Re: Move the Handbook into source tree To: Mehmet Erol Sanliturk Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H3rs8350lz3PYV X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N We have 3 main repos: src, ports and doc. There are good reasons why we are doing this, and it will not change in the near future. For further questions and details, please ask on the freebsd-docs mailing list. You are right that the documentation on our web site is mostly for -current, the state of the art of the code base. If you need the documentation for our supported releases please check our Documentation Archive at https://docs.freebsd.org/doc/ and select your favourite release, e.g. the handbook for FreeBSD 13.0 https://docs.freebsd.org/doc/13.0-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/ the handbook for FreeBSD 12.0 https://docs.freebsd.org/doc/12.0-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/ -Wolfram On Tue, 7 Sept 2021 at 09:03, Mehmet Erol Sanliturk wrote: > > Dear All , > > in many of my messages to FreeBSD mailing lists I am mentioning the > following view : > > "Please move the Handbook into source tree , and > Maintain it with respect to current release without mixing sliding > releases : If you do this , > maintenance of a correct Handbook is IMPOSSIBLE because maintenance of > associated IF statements about releases . > " > > When we look at the following web pages , we see the following : > > https://www.freebsd.org/cgi/man.cgi > FreeBSD Manual Pages > > In the second box of "All sections" line , there are lines about all of > the FreeBSD releases > with many more other systems . > > In spite of this , in the following page : > > https://docs.freebsd.org/en/books/handbook/ > FreeBSD Handbook > The FreeBSD Documentation Project > > > " > Abstract > > Welcome to FreeBSD! This handbook covers the installation and day to day > use of > FreeBSD 13.0-RELEASE, FreeBSD 12.2-RELEASE and FreeBSD 11.4-RELEASE. ... > " > > A Handbook which ( for me , exactly , for the others , perhaps ) with many > errors ... > > > I think that , it is NOT extraordinarily a difficult process to move the > Handbook into source > tree and maintaining it with respect to per release and insert into the > above web page a part > similar to the manual pages to display the requested Handbook with respect > to releases . > In the present case , previous handbooks are lost , because of the > difficulty of finding them . > > Thank you very much and my best wishes for you and humanity in these > pandemic days ... > > > Mehmet Erol Sanliturk -- Wolfram Schneider https://wolfram.schneider.org From nobody Tue Sep 7 17:02:55 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1283F17A08CD for ; Tue, 7 Sep 2021 17:03:00 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3s5v70Mfz3kGJ; Tue, 7 Sep 2021 17:02:59 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f1d:3e00:f487:ceed:62ab:471d] (p200300cd5f1d3e00f487ceed62ab471d.dip0.t-ipconnect.de [IPv6:2003:cd:5f1d:3e00:f487:ceed:62ab:471d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 6DCF86EA; Tue, 7 Sep 2021 17:02:59 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: Date: Tue, 7 Sep 2021 19:02:55 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.0.3 Subject: Re: -CURRENT compilation time Content-Language: en-US To: David Chisnall Cc: freebsd-current@freebsd.org References: From: Stefan Esser In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------f6NOA8XUrhd0cCeYQNQu0wi7" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------f6NOA8XUrhd0cCeYQNQu0wi7 Content-Type: multipart/mixed; boundary="------------Tw95KMSahg9CK1dM4r00hn2R"; protected-headers="v1" From: Stefan Esser To: David Chisnall Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: -CURRENT compilation time References: In-Reply-To: --------------Tw95KMSahg9CK1dM4r00hn2R Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 07.09.21 um 15:51 schrieb David Chisnall: > On 06/09/2021 20:34, Wolfram Schneider wrote: >> With the option WITHOUT_TOOLCHAIN=3Dyes the world build time is 2.5 >> times faster (real or user+sys), down from 48 min to 19.5 min real >> time. >=20 > Note that building LLVM with the upstream CMake + Ninja build system is= > *significantly* faster on a decent multicore machine than the FreeBSD > bmake-based in-tree version. >=20 > One of the things I'd love to prototype if I had time is a CMake-based = build > system for FreeBSD so that we could get all of the tooling integration = from the > compile_commands.json, reuse LLVM's (and any other contrib things that = use > CMake) build system without having to recreate it, and be able to use n= inja, to > build. Wouldn't this break META_MODE? I'd rather be able to continue building the world within a few minutes (generally much less than 10 minutes, as long as there is no major LLVM upgrade) than have a faster LLVM build and then a slower build of the wor= ld ... Regards, STefan --------------Tw95KMSahg9CK1dM4r00hn2R-- --------------f6NOA8XUrhd0cCeYQNQu0wi7 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmE3mz8FAwAAAAAACgkQR+u171r99URs /ggAsN89gDn4FwsdXJJiW+zfQHcbCLH3uus3lg7S0034dNKTIjX5qBbOTOSpSo6MJQQOTFXfGmJT YgcyOtkzNnlMSXBNmFIL7UrzULR/Ztp0kwo2W800EG4CxLYwfaynkwNmumj0p5PBDrI6vq3ftI/C Q2bhOrTLr/PLLVUN04cJjbizU6G5+LVe0AshBhYpYlkd4W+fKf6JP2F585fcFN8ZFxvIZVOiBQ1i Ik8HmdVd4V2is/R87I7IqR5uT+PyZFN/FyzCmt0RJtUrmKfnoOMnYmBBubduXxaPY9a0G7gO/EU/ OE7ogSqQdaDLdZ0RVeN7mWcMzqkt5utDdbzB7gGSIw== =SmNW -----END PGP SIGNATURE----- --------------f6NOA8XUrhd0cCeYQNQu0wi7-- From nobody Tue Sep 7 17:34:00 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2CCB017AF89C for ; Tue, 7 Sep 2021 17:34:07 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H3snq0Pmrz3vFT for ; Tue, 7 Sep 2021 17:34:07 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4002a.ext.cloudfilter.net ([10.228.9.250]) by cmsmtp with ESMTP id NYB0mssiOps7PNez0msD2A; Tue, 07 Sep 2021 17:34:06 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NeyymshyTxCNkNeyzmOpgL; Tue, 07 Sep 2021 17:34:06 +0000 X-Authority-Analysis: v=2.4 cv=Xe/qcK15 c=1 sm=1 tr=0 ts=6137a28e a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=JAf30KXuAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=QMYJMLOKKsA0EwvInIcA:9 a=CjuIK1q_8ugA:10 a=UJ0tAi3fqDAA:10 a=GEL62FyrTCmHtEug2d3R:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 3CAFA144; Tue, 7 Sep 2021 10:34:04 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 187HY0WH004342; Tue, 7 Sep 2021 10:34:01 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109071734.187HY0WH004342@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: David Wolfskill , Jakob Alvermark , Cy Schubert , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> Comments: In-reply-to David Wolfskill message dated "Tue, 07 Sep 2021 05:16:41 -0700." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Sep 2021 10:34:00 -0700 X-CMAE-Envelope: MS4xfJsWDWELqvFFjTXqtNVwjM70IOcRjzEujSxlWJ8EfEcAYjqGHqANWiPDE+VI0j8DMpG7XG9FbufnOFnbqdL5UMv4E1b6xHX1aM70y0Lu1hx43FupBbIS 8mQ3WaubIiqPa8xbKW+QO2sGElsGyrsRyuUXgjL2Oi1Mdf1M7J2YmaE1ohcMPTRWBIUMSh18wNNn3L/vopckl4rfyBSBH+sQFi95xs4gxpNwIgsU0KkXm1Uz zaimuXVCSDdiLG8y5uKMwcf9ykawGBdbFNKD8h9riNg= X-Rspamd-Queue-Id: 4H3snq0Pmrz3vFT X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message , David Wolfskill writes: -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. > On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > > ...=20 > > wlan0 does not associate after boot. (This is with iwm, AC 9260) > >=20 > > My workaround is simply 'ifconfig wlan0 up'. > >=20 > > After a few seconds wpa_supplicant associates and another few secods=20 > > later I have a DHCP IP address. > > .... > > I just tried that (running main-n249159-bb61ccd530b7), and that (also) > works for me -- in case that data point is of use. Hi, Commit 5fcdc19a8111 has addressed this. From nobody Tue Sep 7 18:44:09 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A0F8117B0965 for ; Tue, 7 Sep 2021 18:44:46 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H3vML3rPwz4lbB; Tue, 7 Sep 2021 18:44:46 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-vk1-xa2e.google.com with SMTP id g34so71928vkd.11; Tue, 07 Sep 2021 11:44:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O0g0+swz0B7I1ik533WRZMgehPI2+YSfmD0+g7aOf6s=; b=EI2B9PPUVQVhTaCxBUxAgmKlcpt73AM/Gs67sMhkst8AjZi72kBYgYiy4M+0lHD1KP +iwOE4dgQQgexar9buMseZHWAHT9NmFdn1UEFZvn1yNkSvMrjgM8mtYLTKCmxSwJ3nXW vag21I8c12c8+uRaJJXm9QYYXEvhewHAl+uj82/LKldcqWcWV0wD8eoapairBqB9kEM0 zcCa7fpstAGaAomaCWoQPUK8lgGla1eebEFv1Gsl8Fmkz+E3o+iFyHlZ5ThYPntSajhN 0l6asLBePg3V/998ZVmGCTnM03IJpVRoz8IOm6BlyeBdY+5KgVL0B6LM2DCfBP8ASDOQ fnyg== 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=O0g0+swz0B7I1ik533WRZMgehPI2+YSfmD0+g7aOf6s=; b=mdXdKfnuUrgtjPenC4nh9pbeZTPIv8Npn/cDPLNQbx4Rt6qv7+lI9GW+IKDjCDd6dD TcWQL//9xe9zGEQmXRieHrU03nXW6ExpT6I522tHyu8Jdhy7/DQ4hEHnbJ4ylnUvE0at h9thn4tSfoicX8Nuv9g/cBzl2djN1TpFzKbNS037/CEw/UxM0Ltdf2PvhPHzzkdXtxZY 0bHoa74zSVtEeI3sPsQJJYN3uiRkJeEs/CIxlziIuCzjowEDi1Qrx/nfzTYZDPZ9SmyF s/DgGnyX3seVzPZ1NRMk5FAX/yd+22zFULJVT/QVYh4XDL8I8QqUIy7B9z2Suo4wx6Bn f8qA== X-Gm-Message-State: AOAM531nsQK54Yp6zcMXG72YBmU+Fpf7BfVcAo/u8AiQEqNNYbECYM8b f4liXUhEXYIsAlZRoQpaH4dGiuakBhUqKME9q3GhGwiIv5Q= X-Google-Smtp-Source: ABdhPJysZIka9b8LlxR4T2CmCr3OADq0fnQFEtN/HhQ/n1nvnZb9tEHfDgy2OBC+UOpM7fNtszNAtV2MXvs3cKDcdhs= X-Received: by 2002:a1f:2f87:: with SMTP id v129mr9365294vkv.4.1631040285482; Tue, 07 Sep 2021 11:44:45 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mehmet Erol Sanliturk Date: Tue, 7 Sep 2021 21:44:09 +0300 Message-ID: Subject: Re: Move the Handbook into source tree To: Wolfram Schneider Cc: freebsd-current Content-Type: multipart/alternative; boundary="000000000000d4a37d05cb6c28bf" X-Rspamd-Queue-Id: 4H3vML3rPwz4lbB X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --000000000000d4a37d05cb6c28bf Content-Type: text/plain; charset="UTF-8" On Tue, Sep 7, 2021 at 7:51 PM Wolfram Schneider wrote: > We have 3 main repos: src, ports and doc. There are good reasons why > we are doing this, and it will not change in the near future. For > further questions and details, please ask on the freebsd-docs mailing > list. > > You are right that the documentation on our web site is mostly for > -current, the state of the art of the code base. If you need the > documentation for our supported releases please check our > Documentation Archive at > > https://docs.freebsd.org/doc/ > > and select your favourite release, e.g. > > the handbook for FreeBSD 13.0 > > https://docs.freebsd.org/doc/13.0-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/ > > the handbook for FreeBSD 12.0 > > https://docs.freebsd.org/doc/12.0-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/ > > -Wolfram > > On Tue, 7 Sept 2021 at 09:03, Mehmet Erol Sanliturk > wrote: > > > > Dear All , > > > > in many of my messages to FreeBSD mailing lists I am mentioning the > > following view : > > > > "Please move the Handbook into source tree , and > > Maintain it with respect to current release without mixing sliding > > releases : If you do this , > > maintenance of a correct Handbook is IMPOSSIBLE because maintenance of > > associated IF statements about releases . > > " > > > > When we look at the following web pages , we see the following : > > > > https://www.freebsd.org/cgi/man.cgi > > FreeBSD Manual Pages > > > > In the second box of "All sections" line , there are lines about all of > > the FreeBSD releases > > with many more other systems . > > > > In spite of this , in the following page : > > > > https://docs.freebsd.org/en/books/handbook/ > > FreeBSD Handbook > > The FreeBSD Documentation Project > > > > > > " > > Abstract > > > > Welcome to FreeBSD! This handbook covers the installation and day to day > > use of > > FreeBSD 13.0-RELEASE, FreeBSD 12.2-RELEASE and FreeBSD 11.4-RELEASE. ... > > " > > > > A Handbook which ( for me , exactly , for the others , perhaps ) with > many > > errors ... > > > > > > I think that , it is NOT extraordinarily a difficult process to move the > > Handbook into source > > tree and maintaining it with respect to per release and insert into the > > above web page a part > > similar to the manual pages to display the requested Handbook with > respect > > to releases . > > In the present case , previous handbooks are lost , because of the > > difficulty of finding them . > > > > Thank you very much and my best wishes for you and humanity in these > > pandemic days ... > > > > > > Mehmet Erol Sanliturk > > > If you consider me , now at home there is 4.4BSD Lite ( Version 2.0 . Released Sept 1995 ) as a memorial . I could not find any previous release because it is likely that I left them in my university during my retirement to allow them to install them in university student laboratories . Trouble is NOT ME , because since 1970 I have been in the computing area ( starting my work since 1966 ) . My PhD thesis is "A multimedia information management system ( 1995 )" getting two vetoes ( both of them being virtual ) , one PhD sufficiency examination because of "This thesis proposition is in very much upper level with respect to a PhD thesis requirements" , another veto in thesis defense because "We need to mention that , although this thesis is excellent , it is impossible to complete it as a PhD thesis due to its very complicated difficulty level . If we do not mention this , later on , if anyone sees our "Thesis defense evaluation report" may say that "How such a jury does not recognize the difficulty level of this thesis and does not mention it ." If all of you say "YES" , I will mention this point and say "NO" , but if any one of you says "NO" , my vote is "YES" . " They asked : "How did you do it ?" ... 'based on my vast experience and theoretical works performed previously " ... ( my primary work area is "Theoretical Computing Sciences" ) "Why did you not use simulation ? " ... "for me , writing a simulator is much more difficult than writing its own implementation sufficient to show its feasibility and usability ." ... Then trouble is an unusable handbook due to many errors spreaded over it due to its SLIDING nature of consisting of THREE separate releases . You may say that "The discussion area is in "docs" list . For me "NO" , because "It is a FreeBSD System Design Problem, not a 'docs' problem " , because use of FreeBSD is based on use of a handbook , because FreeBSD is not doing anything by itself , the only user doing everything . For this , the Handbook is a vital component for use of it . When tracking the mailing lists ( I am one of them , nearly the start of the Internet at least in my country Turkey ) mostly people are using it based on their experience or by reading sources . How can WE acquire such an expertise or is it possible that everyone will read the sources and use it ? I have mentioned this point very long ago , and I am repeating this point continuously without any tangible result . This difficulty is driving FreeBSD to a very small user base and then causing prevention of acceptance by large masses . I am not able to install FreeBSD due to its very complicated install system . I am not able to use FreeBSD due to its uncomprehensible *.conf files and incompatible KDE system ( for my needs . I do not use other ones because of my needs ) . ... There is a necessity to produce a ( usable , correct information containing handbook ) because everything is based on descriptions . It is not like Linux . I am installing Linux ( Fedora KDE , before Mandriva ) without using extra documentation . When it comes to FreeBSD , I am maintaining a thickest folder filled with flash cards . A new release is coming , requiring you to modify these cards . >From where ? From the Handbook ? Thank you very much . Mehmet Erol Sanliturk > > -- > Wolfram Schneider https://wolfram.schneider.org > --000000000000d4a37d05cb6c28bf-- From nobody Tue Sep 7 22:28:56 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 74B7217A59C1 for ; Tue, 7 Sep 2021 22:29:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-25.consmr.mail.gq1.yahoo.com (sonic304-25.consmr.mail.gq1.yahoo.com [98.137.68.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 4H40LH2cpRz3DSh for ; Tue, 7 Sep 2021 22:29:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1631053744; bh=pewqeb1039HC/ZgcQXBOUGwS/p6de9mHmbAlwJwjraM=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=P6obVC2SVawTjefRqa1C314pjqZWteA48dZ++cIAUTrgizn2la5xU6nUqolxXNMEz6CDWbH/zIywrqLEfYdRwNyj8lYUgP85KODPqSTCwSVUJfILFOreoUnEVkyrr1GI2n28aHEhWRFTteszKQLdmqNyJNWGNQANxYUorzME8EQ/H9yZioDwwNU0zAF8ofxWTgP/EgPEJ4L0I6nc/X4DBzxsEI4ave27WXWJNKeuReN4ZoQCLSmXg8ar8OeKGdlQlTBcnHej6/N5FmfHWYqd1eVC8MHkgzXbngprqE1GetNkOPltED4GEkN02UR4LfhkKbwjDaaZTlbmbzVSwL1UVw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1631053744; bh=gXXgoQVqh6XRNuOuGPInWUaOQ1bgTmj7ENngv9vAR14=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=XAoG074OOCqGPrkhBLvXEbsd8FvTOP1ZqmdsNGAwxK9PQIcV+PYeCxAUQONpDKzwdYEcyXkUSx/lEKvugb30KjJNn7DjkiIwNuKPfrMaYVisvpdPuw/h0cL4rVJbC/F9t4OpOHnzgovSL02gyMfu9IatU0ETVSNQbGtOGoagP8jeqlGseKRZ19KMGsz3wLrQli2i4TJaB2CoLcuM6rHvtovbIB9ptz+73qWQdREmmg+nv734IvMn6u1IZ6HCyaFnaOfbsv8j0D44uiMwTF9p3KQ+NYPiXzIb5ltt/dvoPn+s+caAgzrdSb66/8ebz+189SVqNx/4jP8FWxdv6fTYWw== X-YMail-OSG: Cmg3EwQVM1lghM40EYd4IenrSwtRcbsL_vsTbZ.NIyKvRPUDF36tEuhP9UkYV1z cZXb8AsLZi.NFITXlQIq0Z9F0Bm_m8jmAcghFVradrCYDERt_gBgz76lrGbzkcn6gPVfcgmR5JYv KheiYEYZFBL6yPBi63n3mLgPzlrzdid_wcSm5I42puID2l3lJ7UpSDI3an.0uFyi.ShZi7RSaV_g eASH8k8En_Tt..aDp9db.ZreCVdS3.PDdfxgcxxtmo4Pjdt2mtwU.A7.AJmztSWV2ATfWp.IE0VC orfEXlzotSZdpa2Kns75XLtFxCduGtRmVrK6UJ4eneCowpoKd3AZ2HjJudhncbodVQWbprHvk1Jq L3A3LrGRea7IyRKWekTQnwI1VxQwmNAF22i3zB43p8aQ946eD.RoMmB0Gj7lg_BHjZOT55uaV512 VBCwuqJYQydKLM6ekYA7dPCbFl7L89afEEo5De0q7xMVoNRiBpCBPo0Gyu1qTq9VKTcM2KFUp7I2 n4YCDJtvA7KkRQQIvmVjMPhlY5hOrV2uCzCT1PsKpBu20j5aNjONikAU4GwTXgLRKBAa2UPbmHfb _kekQYRM.g3rAcOZtowkX9mD1TxNbPXGTpU5KwIlanvr7sMNFaoagk4zEKzYMxiHIaS0KvUARL6L 8F.Fs8CK3EhR.flkHv_HWI5_Fuv1W8_H8IEshuqxY78gQi2C2jdZOm_W4k0ndlxAj10tRHdUdIbF FPYcxUz1SjukCljXuBJIFV47jUDPFRT5b25hTPIEb14YbfOzEzQlIavn5fwOKZ8vmNUH37IuVsQy NUCtgHNa9g2H3eamOrfeDZ77TKr3kqqgrvgJamK7JrGq6SX5hz3K5j2ZfT4qUQglBX7UDVxVmgDj vd5cPbC4pJ_V4dFAlaEPiUKPwHzEU.2jZx4q8G6TaZD6HvZ0zikoyO7_Rov5MRfgWUZAyLvHhXTs CBnqW5YpfKWorvVKE1QAIM61GUDEipx8U_DJDtA_hh3rOikz_fepp5ujfOWyKf5fNnqb9QWs2sc1 zxJ9JLGPvhDwxAF7CmF4KJbN4dKvfbMUzBHNM.thq0_Oy5dQrpt6jMAwxj2OwH5VwU6qFQBCHIlD Tj003EYieRc3wrIhbgeAdCnbiDZM3E0xtDFqkCWuF5lrxv9_.Su8HG9weGt.4DT_HPO.DSE4c6RO 8JyDYvt8mlJqwb8hSr7laIqzc8rNiH.7SDzuA1mok3FWJurDqRwD8QXhFYIVCuiwpJD2FnTxQ9nn pFic_Dt9E5Vmtn94DfEdyVowng0ouMkYh8yRUakx.F2OincIe5eQA2ZF2BzBNe_lOiyMzivgZYqh DU3rOj2NKwJRHSinI521QDv3WrwsULUOmPqZxtKvcYFSt7P9xZVgXO5I1gi0HmYUWsgMdkFPimKi 7fc1IDEeuEXrL7XmyJjIiLAevoIbZGf9v9MnfE24PVP9ljyhv4btOh58ohmHAgAuI4A1JKDaPtwv u3JYKoc78lYvnnbdnyDFNWlv5mg8MB9bYzTlaDCs8aSCmSxDzkRRoeGXkD_kvQHzuEmgwsg7409q MDrPDVCO01cEUl4OXOZoKskH7Tk7k9FirTeoaooTzSfKNexgi.dgIruwOI1OueYHqGCsf3dmEWs1 ZRiIcv5TeVrcsMAIthS9C7PsuI0EK7iWrYc3TF9zihgVekMqgk5XV53.dlX.bvs6Fjsg4_DmlxH_ BDfkXCPf29ENKLBm02NAVLgqccvLQcuMn6YBmV8V2xNY5Djy8c0mjUK8ZuSSaS1vK03JueFoakQU nQFSXLJ1dkh5Yi8rlCHrp2CSPkd2eX.QCVF481rxgsNpBNEi2A.VSSCpo634hcno962e0RqIBpNi imHCW4oWP6.hvG.wBCocTY_fxJ3Oa8bDhfe4XFlZlUsAOdQlUJzjQUzHHYeRKLiyN5WnY3P24r7d 0qClyn.HAwfmXViv.KcJO8Pw.KOYBE.ARfpC0441cP0_0jDKeXH3RCBgMJKFv5FrLHhffTZJEkcl BmZgKrcYuRr968wRFl1VbNuYUUeElDEg61XZzkL5gq9aL.5_f0BOtFi_XiC7Wt0KI0qIqvWu5GHm TRPnrSJus9DFU.IqfJK92_8k0tJw2cmon6Vrly8D.BJFxkScZxdeTIY4iKGnn_Dt2egiE.MQ.SzE vILfbEZ_.UnLvofYwXpcDrhOiA7gVQHYTGSL0cQuKKYe5ki5a6i58gY39btVKnvLNUrpyHDt9Bor LHXoXp.UbMNzqVDAtB64xk_6z83hgyXFyxYhlnU137IzwsqY2dGkS7nKYe_s8K9YZhrCIYol2DET zDBLY5W1SDoOY X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Tue, 7 Sep 2021 22:29:04 +0000 Received: by kubenode524.mail-prod1.omega.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID b1c895aa9a30f9d2b5cddaa07d4a2616; Tue, 07 Sep 2021 22:28:58 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: -CURRENT compilation time Message-Id: Date: Tue, 7 Sep 2021 15:28:56 -0700 To: David Chisnall , freebsd-current X-Mailer: Apple Mail (2.3654.120.0.1.13) References: X-Rspamd-Queue-Id: 4H40LH2cpRz3DSh X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=P6obVC2S; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.68.206 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; 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)[98.137.68.206:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; 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/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.206:from] Reply-To: marklmi@yahoo.com From: Mark Millard via freebsd-current X-Original-From: Mark Millard X-ThisMailContainsUnwantedMimeParts: N > From: David Chisnall =20 > Date: Tue, 7 Sep 2021 14:51:21 +0100 > On 06/09/2021 20:34, Wolfram Schneider wrote: > > With the option WITHOUT_TOOLCHAIN=3Dyes the world build time is 2.5 > > times faster (real or user+sys), down from 48 min to 19.5 min real > > time. >=20 > Note that building LLVM with the upstream CMake + Ninja build system = is=20 > *significantly* faster on a decent multicore machine than the FreeBSD=20= > bmake-based in-tree version. Just examples of llvm12 builds from my checking this . . . poudriere-devel llvm12 buil times, nothing else being built, all prerequisites already built (not that such are trivial): amd64 ThreadRipper 1950X with 128 GiByte of RAM, optane 1.4T media, 32 = FreeBSD cpus: [00:00:07] [01] [00:00:00] Building devel/llvm12 | llvm12-12.0.1_4 [00:22:54] [01] [00:22:47] Finished devel/llvm12 | llvm12-12.0.1_4: = Success for: ---Begin OPTIONS List--- =3D=3D=3D> The following configuration options are available for = llvm12-12.0.1_4: BE_AMDGPU=3Don: AMD GPU backend (required by mesa) CLANG=3Don: Build clang COMPILER_RT=3Don: Sanitizer libraries DOCS=3Don: Build and/or install documentation EXTRAS=3Don: Extra clang tools GOLD=3Don: Build the LLVM Gold plugin for LTO LIT=3Don: Install lit and FileCheck test tools LLD=3Don: Install lld, the LLVM linker LLDB=3Don: Install lldb, the LLVM debugger OPENMP=3Don: Install libomp, the LLVM OpenMP runtime library PYCLANG=3Doff: Install python bindings to libclang =3D=3D=3D=3D> Options available for the single BACKENDS: you have to = select exactly one of them BE_FREEBSD=3Doff: Backends for FreeBSD architectures BE_NATIVE=3Don: Backend(s) for this architecture (X86) BE_STANDARD=3Doff: All non-experimental backends =3D=3D=3D> Use 'make config' to modify these settings ---End OPTIONS List--- Note the BE_NATIVE use. Also poudriere.conf has: ZPOOL=3Dzoptb USE_TMPFS=3Dyes ALLOW_MAKE_JOBS=3Dyes For reference: # uname -apKU FreeBSD amd64_ZFS 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #1 = releng/13.0-n244760-940681634ee1-dirty: Mon Aug 30 11:28:31 PDT 2021 = root@amd64_ZFS:/usr/obj/BUILDs/13_0R-amd64-nodbg-clang/usr/13_0R-src/amd64= .amd64/sys/GENERIC-NODBG amd64 amd64 1300139 1300139 The swap/paging space stayed unused. aarch64 Honycomb with 64 GiByte of RAM, optane 480 GiByte media, 16 = FreeBSD cpus: [00:00:15] [01] [00:00:00] Building devel/llvm12 | llvm12-12.0.1_4 [00:58:07] [01] [00:57:52] Finished devel/llvm12 | llvm12-12.0.1_4: = Success for: ---Begin OPTIONS List--- =3D=3D=3D> The following configuration options are available for = llvm12-12.0.1_4: BE_AMDGPU=3Don: AMD GPU backend (required by mesa) CLANG=3Don: Build clang DOCS=3Don: Build and/or install documentation EXTRAS=3Don: Extra clang tools LIT=3Don: Install lit and FileCheck test tools LLD=3Don: Install lld, the LLVM linker OPENMP=3Don: Install libomp, the LLVM OpenMP runtime library PYCLANG=3Doff: Install python bindings to libclang =3D=3D=3D=3D> Options available for the single BACKENDS: you have to = select exactly one of them BE_FREEBSD=3Doff: Backends for FreeBSD architectures BE_NATIVE=3Don: Backend(s) for this architecture (AArch64) BE_STANDARD=3Doff: All non-experimental backends =3D=3D=3D> Use 'make config' to modify these settings ---End OPTIONS List--- Note the BE_NATIVE use. Also poudriere.conf has: ZPOOL=3Dzopt0 USE_TMPFS=3D"data" ALLOW_MAKE_JOBS=3Dyes For reference: # uname -apKU FreeBSD CA72_16Gp_ZFS 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #4 = releng/13.0-n244760-940681634ee1-dirty: Mon Aug 30 11:35:45 PDT 2021 = root@CA72_16Gp_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/ar= m64.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1300139 1300139 The swap/paging space stayed unused. I've not yet figured out a good way to time just an analogous subset of buildworld . It would need to be stable/13 or main [so: 14] targetted to involve building an llvm12 based set of material. releng/13.0 is llvm11 based. One point is that likely the system builds libc++ and such but devel/llvm12 does not: devel/llvm12 likely is bound to the system libc++ and such. This may make "analogous subset of buildworld" harder to isolate. So I've not made it to well-measured differences in time-used yet. > One of the things I'd love to prototype if I had time is a CMake-based=20= > build system for FreeBSD so that we could get all of the tooling=20 > integration from the compile_commands.json, reuse LLVM's (and any = other=20 > contrib things that use CMake) build system without having to recreate=20= > it, and be able to use ninja, to build. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From nobody Tue Sep 7 22:42:53 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id CD0AA17AE329 for ; Tue, 7 Sep 2021 22:43:01 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H40fD4FKkz3L1C for ; Tue, 7 Sep 2021 22:43:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 187Mgr7G019623 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 7 Sep 2021 15:42:53 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 187Mgr4j019622 for freebsd-current@freebsd.org; Tue, 7 Sep 2021 15:42:53 -0700 (PDT) (envelope-from sgk) Date: Tue, 7 Sep 2021 15:42:53 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: killall, symlinks, and signal delivery? Message-ID: <20210907224242.GA19450@troutmask.apl.washington.edu> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4H40fD4FKkz3L1C X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.93 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; 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_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.926]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N I have stumbled about a quandry, which I hope someone can shed some light upon. In my day job, I often generate a sequence of images and display these images with ImageMagick's display command. From my csh prompt, a quick and dirty foreach() loop % foreach i (*.png) > display $i & > sleep 3 > end Instead of moving the cursor to each image and hitting 'q' to close the images. I normally kill all of the processes at one time. This used to work: % killall display Now I geit, for example, % display z.miff & % killall display No matching processes belonging to you were found % ps -Ukargl | grep display 19463 1 S 0:00.02 display z.miff (magick) 19465 1 S+ 0:00.00 grep display % ls -l /usr/local/bin/display lrwxr-xr-x 1 root wheel - 6 Jun 1 14:18 /usr/local/bin/display@ -> magick So, there are two possibilities: (1) display was once an independent program and not a symlink to magick. Thus, killall just worked. Or, (2) killall no longer works because command associated with process 19463 is not really 'display' and the symlink isn't resolved to actually kill 'magick'. So, just chekcing (2), here. Is this a change in behvior for FreeBSD? -- Steve From nobody Tue Sep 7 23:20:30 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DF0C917BF9F1 for ; Tue, 7 Sep 2021 23:21:52 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4H41W45hfrz3n0w for ; Tue, 7 Sep 2021 23:21:52 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id Ne23mBm2lczbLNkPYmPSIi; Tue, 07 Sep 2021 23:21:52 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NkPWmZG6uU9pxNkPXmQLP6; Tue, 07 Sep 2021 23:21:52 +0000 X-Authority-Analysis: v=2.4 cv=Bbi7bph2 c=1 sm=1 tr=0 ts=6137f410 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=IkcTkHD0fZMA:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=qFSmBd4IDbBuJr8jT88A:9 a=QEXdDO2ut3YA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [127.0.0.1] (unknown [209.52.88.199]) by spqr.komquats.com (Postfix) with ESMTPSA id 7B8CB5F4; Tue, 7 Sep 2021 16:21:49 -0700 (PDT) Date: Tue, 07 Sep 2021 16:20:30 -0700 From: Cy Schubert To: freebsd-current@freebsd.org, Steve Kargl Subject: Re: killall, symlinks, and signal delivery? In-Reply-To: <20210907224242.GA19450@troutmask.apl.washington.edu> References: <20210907224242.GA19450@troutmask.apl.washington.edu> Message-ID: <6C88F561-B045-4D09-B61D-D91096AF0C4B@cschubert.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-CMAE-Envelope: MS4xfI36hZBMMwP7QRMBGdrbGD0MlH+U5Cnpm2EOClXTTgO+EHcX+Vm06/kVXUA4XwRZkmBwX3Re9aT0EdS+2Dj7XRKQ2TlCSm1IHZioJFaXq7agHSaMef2g xm/vHKyWcC+1nRRW0X6J0nXJpmYA1wcN06x8ofnMS4h2JMkUdEni5CuPnf4F83opc6dg8D7UcyhgLexmkaUZB36dL54ND0FesTqgqc2YQwo9cpJsQr7d4Jb4 wRkGUKRqe7lZuTBjfS4SJhROVJTzhb8SAfxa6brNPlk= X-Rspamd-Queue-Id: 4H41W45hfrz3n0w X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On September 7, 2021 3:42:53 PM PDT, Steve Kargl wrote: >I have stumbled about a quandry, which I hope someone >can shed some light upon=2E In my day job, I often >generate a sequence of images and display these images >with ImageMagick's display command=2E From my csh prompt, >a quick and dirty foreach() loop > >% foreach i (*=2Epng) >> display $i & >> sleep 3 >> end > >Instead of moving the cursor to each image and hitting >'q' to close the images=2E I normally kill all of the >processes at one time=2E This used to work: > >% killall display > >Now I geit, for example,=20 > >% display z=2Emiff & >% killall display >No matching processes belonging to you were found >% ps -Ukargl | grep display >19463 1 S 0:00=2E02 display z=2Emiff (magick) >19465 1 S+ 0:00=2E00 grep display >% ls -l /usr/local/bin/display=20 >lrwxr-xr-x 1 root wheel - 6 Jun 1 14:18 /usr/local/bin/display@ -> ma= gick > >So, there are two possibilities: >(1) display was once an independent program and not a > symlink to magick=2E Thus, killall just worked=2E Or, >(2) killall no longer works because command associated > with process 19463 is not really 'display' and the > symlink isn't resolved to actually kill 'magick'=2E > >So, just chekcing (2), here=2E Is this a change in behvior >for FreeBSD? > It's likely your app is replacing its process name (argv[0]) to something = else=2E ps auxww may give you a hint what it might be now=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 nobody Wed Sep 8 00:00:36 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0571217A9E38 for ; Wed, 8 Sep 2021 00:00:41 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H42Mr5l3Gz4V5X for ; Wed, 8 Sep 2021 00:00:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 18800aPo026761 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 7 Sep 2021 17:00:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 18800avr026760; Tue, 7 Sep 2021 17:00:36 -0700 (PDT) (envelope-from sgk) Date: Tue, 7 Sep 2021 17:00:36 -0700 From: Steve Kargl To: Cy Schubert Cc: freebsd-current@freebsd.org Subject: Re: killall, symlinks, and signal delivery? Message-ID: <20210908000036.GA24175@troutmask.apl.washington.edu> References: <20210907224242.GA19450@troutmask.apl.washington.edu> <6C88F561-B045-4D09-B61D-D91096AF0C4B@cschubert.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6C88F561-B045-4D09-B61D-D91096AF0C4B@cschubert.com> X-Rspamd-Queue-Id: 4H42Mr5l3Gz4V5X X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Sep 07, 2021 at 04:20:30PM -0700, Cy Schubert wrote: > On September 7, 2021 3:42:53 PM PDT, Steve Kargl wrote: > >I have stumbled about a quandry, which I hope someone > >can shed some light upon. In my day job, I often > >generate a sequence of images and display these images > >with ImageMagick's display command. From my csh prompt, > >a quick and dirty foreach() loop > > > >% foreach i (*.png) > >> display $i & > >> sleep 3 > >> end > > > >Instead of moving the cursor to each image and hitting > >'q' to close the images. I normally kill all of the > >processes at one time. This used to work: > > > >% killall display > > > >Now I geit, for example, > > > >% display z.miff & > >% killall display > >No matching processes belonging to you were found > >% ps -Ukargl | grep display > >19463 1 S 0:00.02 display z.miff (magick) > >19465 1 S+ 0:00.00 grep display > >% ls -l /usr/local/bin/display > >lrwxr-xr-x 1 root wheel - 6 Jun 1 14:18 /usr/local/bin/display@ -> magick > > > >So, there are two possibilities: > >(1) display was once an independent program and not a > > symlink to magick. Thus, killall just worked. Or, > >(2) killall no longer works because command associated > > with process 19463 is not really 'display' and the > > symlink isn't resolved to actually kill 'magick'. > > > >So, just chekcing (2), here. Is this a change in behvior > >for FreeBSD? > > > > It's likely your app is replacing its process name > (argv[0]) to something else. ps auxww may give you a > hint what it might be now. Yes, that's likely. So, it could be a change in behavior for ImageMagick. Your suggested ps command doesn't provide anything new. ps shows the command that I entered, namely, 'display coarse_sand.jpg'. But, it also shows '(magick)', which is the actual name of the program. I'm guessing argv[0] = "magick". % ps 24333 7 I 0:00.43 display coarse_sand.jpg (magick) % killall magick does the job of killing the displayed image. -- Steve From nobody Wed Sep 8 01:10:47 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0D77F17A7E75 for ; Wed, 8 Sep 2021 01:11:01 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4H43x06ZQpz4rqQ for ; Wed, 8 Sep 2021 01:11:00 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 1881AmUn013960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Sep 2021 02:10:48 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 1881AmGW013959; Wed, 8 Sep 2021 02:10:48 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202109080110.1881AmGW013959@donotpassgo.dyslexicfish.net> Date: Wed, 08 Sep 2021 02:10:47 +0100 Organization: Dyslexic Fish To: sgk@troutmask.apl.washington.edu, Cy.Schubert@cschubert.com Cc: freebsd-current@FreeBSD.org Subject: Re: killall, symlinks, and signal delivery? References: <20210907224242.GA19450@troutmask.apl.washington.edu> <6C88F561-B045-4D09-B61D-D91096AF0C4B@cschubert.com> <20210908000036.GA24175@troutmask.apl.washington.edu> In-Reply-To: <20210908000036.GA24175@troutmask.apl.washington.edu> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Wed, 08 Sep 2021 02:10:48 +0100 (BST) X-Rspamd-Queue-Id: 4H43x06ZQpz4rqQ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Steve Kargl wrote: > Yes, that's likely. So, it could be a change in behavior > for ImageMagick. Your suggested ps command doesn't provide I don't know when the change was made, but the pkg for ImageMagik 6.9.12.12 has "display" as a stand-alone binary, whilst the pkg for 7.0.11.12 has it as a softlink. So yeah, either an upstream change, or a port change. Cheers, Jamie From nobody Wed Sep 8 08:57:50 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2097117B8F70 for ; Wed, 8 Sep 2021 08:57:53 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4GHj0Stgz3G0G; Wed, 8 Sep 2021 08:57:53 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id DED7082A9; Wed, 8 Sep 2021 08:57:52 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id E07EC2C94B; Wed, 8 Sep 2021 09:57:51 +0100 (BST) Subject: Re: -CURRENT compilation time To: Stefan Esser Cc: freebsd-current@freebsd.org References: From: David Chisnall Message-ID: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> Date: Wed, 8 Sep 2021 09:57:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 07/09/2021 18:02, Stefan Esser wrote: > Wouldn't this break META_MODE? I have never managed to get META_MODE to work but my understanding is that META_MODE is addressing a problem that doesn't really exist in any other build system that I've used: that dependencies are not properly tracked. When I do a build of LLVM with the upstream build system with no changes, it takes Ninja approximately a tenth of a second to stat all of the relevant files and tell me that I have no work to do. META_MODE apparently lets the FreeBSD build system extract these dependencies and do something similar, but it's not enabled by default and it's difficult to make work. > I'd rather be able to continue building the world within a few minutes > (generally much less than 10 minutes, as long as there is no major LLVM > upgrade) than have a faster LLVM build and then a slower build of the world ... The rest of this thread has determined that building LLVM accounts for half of the build time in a clean FreeBSD build. LLVM's CMake is not a great example: it has been incrementally improved since CMake 2.8 and doesn't yet use any of the modern CMake features that allow encapsulating targets and providing import / export configurations. In spite of that, it generates a ninja file that compiles *significantly* faster than the bmake-based system in FreeBSD. In other projects that I've worked on with a similar-sized codebase to FreeBSD that use CMake + Ninja, I've never had the same problems with build speed that I have with FreeBSD. Working on LLVM, I generally spend well under 10% of my time either waiting for builds or fighting the build system. Working on FreeBSD, I generally spend over 90% of my time waiting for builds or fighting the build system. This means that my productivity contributing to FreeBSD is almost zero. For reference, changes to LLVM typically build for me in under 30 seconds with Ninja, unless I've changed a header that everything In particular, building FreeBSD on a 10-24 core machine has very long periods where a number of the cores are completely idle. Ninja also has a few other nice features that improve performance relative to bmake: - It lets you put jobs in different pools. In LLVM this is used to put link and compile jobs in different pools because linking with LLD uses multiple threads and a lot more memory than compilation, so a 10-core machine may want to do 12 compile jobs in parallel but only 2 link jobs. This makes it much easier to completely saturate the machine. - Ninja provides each parallel build task with a separate pipe for stdout and stderr, and does not print their output unless a build step fails (or unless you build with -v). With bmake, if a parallel build fails I have to rerun the build without -j, because the output is interleaved with succeeding jobs and it's difficult to see what actually failed. With ninja, the output is from each failed job, with no interleaving. David From nobody Wed Sep 8 10:52:36 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F313017C3757 for ; Wed, 8 Sep 2021 10:52:41 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4Jr964HDz4YvS; Wed, 8 Sep 2021 10:52:41 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ed1-x52b.google.com with SMTP id g22so2240032edy.12; Wed, 08 Sep 2021 03:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=o38/Mw8M1npDGO6wr9G5BT/YR+I2XzfRBLaZ+RSGzCE=; b=R3jIDVHc/EiTjo2k87Ltttk5+x+c9fokRCf3xAhy0cv63pEreGYCwGvKyyahm65ek9 47dXQJOr4E9N/bkWDJyiNqUqk8e1iCDOk/1nF4hobK2B5SETGUcoq6o2q6864O3ZASsI vHVAUNmg0abFXHUq0bujVQiO1SigQgLM4mrgwN7X+cY6iA6SrjlYHiLSPuD82oP9C1qS S3/1mmmmm3xZbDDhF0h4Exr0TzyVfuGFgkE+mJzwpyPWQ3hG074MLNggbRJHLolZbHnK 38jwnFaeUafEqEl73RF3vJuUxuL5bUls1egcTsCI9LEKDhor+muSAgECiBXLtmD67oqO 1jrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=o38/Mw8M1npDGO6wr9G5BT/YR+I2XzfRBLaZ+RSGzCE=; b=qdGcvHsw2e2IjbEh4LxoZRZcuUBEuM/7Fr2tgxEY04VIb0aUvaJYUTBIcPdcn+4bR6 88Ljc/8KUfCZ1BNbvNJfYiTZSICpMHKVjX9IqjxCQkLascsEEhudxRKAp8ae06c99tlb 0i+tkZV8W7AQB1ahj3Cxtl95bLIjuG46KxZqIH+rX/bk9bBHVnV79OMXHLXuoAsrVSss WnS7AXWYAFJcVgEuJFKcq/aATJYoxAGD84HgolN1WFI1TOH5kdrzJSa7iii5j1Ym7xMY 7e3MNgH6nBMAaOCQ3aU6Ee+cbaOc8wfFHbMW/jSzpJ/xu+LlNc2evsYjeyX0j75ClUYC iyMQ== X-Gm-Message-State: AOAM533CJtaalCkPRSmM/PRIqLy02hlnPdxWRWTzaITob136NkydyHBn oYLLg113SeEqZox1RB8dVMh/EZfHI9s= X-Google-Smtp-Source: ABdhPJyV/EyAkS42tWQt7/KoIfg2xkvd+9vG+tNJpQnyQ6iDIQDJQmEpWLnYRI6wAJRsxCBlv2/weA== X-Received: by 2002:aa7:c14b:: with SMTP id r11mr3214007edp.108.1631098360690; Wed, 08 Sep 2021 03:52:40 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id c2sm579957edk.50.2021.09.08.03.52.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Sep 2021 03:52:40 -0700 (PDT) Date: Wed, 8 Sep 2021 12:52:36 +0200 From: Gary Jennejohn To: David Chisnall Cc: Stefan Esser , freebsd-current@freebsd.org Subject: Re: -CURRENT compilation time Message-ID: <20210908105236.1abb8f9a@ernst.home> In-Reply-To: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H4Jr964HDz4YvS X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Wed, 8 Sep 2021 09:57:50 +0100 David Chisnall wrote: > On 07/09/2021 18:02, Stefan Esser wrote: > > Wouldn't this break META_MODE? > > I have never managed to get META_MODE to work but my understanding > is that META_MODE is addressing a problem that doesn't really exist > in any other build system that I've used: that dependencies are not > properly tracked. > META_MODE requires filemon(4) to be in the kernel or loaded as a module. make(1) will use if it's available with .MAKE.MODE=meta. > When I do a build of LLVM with the upstream build system with no > changes, it takes Ninja approximately a tenth of a second to stat > all of the relevant files and tell me that I have no work to do. > META_MODE apparently lets the FreeBSD build system extract these > dependencies and do something similar, but it's not enabled by > default and it's difficult to make work. > > > I'd rather be able to continue building the world within a few > > minutes (generally much less than 10 minutes, as long as there is > > no major LLVM upgrade) than have a faster LLVM build and then a > > slower build of the world ... > > The rest of this thread has determined that building LLVM accounts > for half of the build time in a clean FreeBSD build. LLVM's CMake > is not a great example: it has been incrementally improved since > CMake 2.8 and doesn't yet use any of the modern CMake features that > allow encapsulating targets and providing import / export > configurations. > > In spite of that, it generates a ninja file that compiles > *significantly* faster than the bmake-based system in FreeBSD. In > other projects that I've worked on with a similar-sized codebase to > FreeBSD that use CMake + Ninja, I've never had the same problems > with build speed that I have with FreeBSD. > > Working on LLVM, I generally spend well under 10% of my time either > waiting for builds or fighting the build system. Working on > FreeBSD, I generally spend over 90% of my time waiting for builds or > fighting the build system. This means that my productivity > contributing to FreeBSD is almost zero. > > For reference, changes to LLVM typically build for me in under 30 > seconds with Ninja, unless I've changed a header that everything > > In particular, building FreeBSD on a 10-24 core machine has very > long periods where a number of the cores are completely idle. > > Ninja also has a few other nice features that improve performance > relative to bmake: > > - It lets you put jobs in different pools. In LLVM this is used to > put link and compile jobs in different pools because linking with > LLD uses multiple threads and a lot more memory than compilation, so > a 10-core machine may want to do 12 compile jobs in parallel but > only 2 link jobs. This makes it much easier to completely saturate > the machine. > - Ninja provides each parallel build task with a separate pipe for > stdout and stderr, and does not print their output unless a build > step fails (or unless you build with -v). With bmake, if a parallel > build fails I have to rerun the build without -j, because the output > is interleaved with succeeding jobs and it's difficult to see what > actually failed. With ninja, the output is from each failed job, > with no interleaving. > ninja sounds really neat and it's available as /usr/ports/devel/ninja. Seems to me that there was an earlier mail about getting CMAKE to work with FreeBSD builds. Could be worthwhile to look into getting ninja to work also. But I could understand that there might be push-back, since the project prefers to use utilities from the source tree. -- Gary Jennejohn From nobody Wed Sep 8 11:18:49 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5BA3017A757B for ; Wed, 8 Sep 2021 11:19:09 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4KQg5rKyz4j1N for ; Wed, 8 Sep 2021 11:19:07 +0000 (UTC) (envelope-from vidwer@gmail.com) Received: by mail-ej1-x62e.google.com with SMTP id t19so3401107ejr.8 for ; Wed, 08 Sep 2021 04:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IrRTyWKsVwu2tQq7pLa++dzsRTou7gUj3XSlupxW80A=; b=m3uAl0i6FgK+ew4phWqig1ylbDPfIh7DRTPA315lFgA7ouUEN4/Y/uSze9VS/jCK1h CeANJwzE1u3cYrgwGtZVVd9PsvcKdlSKma9XSoljCvnayt6dMt/0bVCNgiv+1OvC6evJ OleDm8ufCP+1wr30d0cpK/HmlcHD+Fry0Ur0hv7fYy/GW75HyYB4r1tqLum2S6zmyIMp 30m5hqwRBDAKw84hkK6t0EPWCuEuybvUiTYjjJtQZRS7YpJkuUSrIxmSh/5Xb/LCLKLa 6JqV/K3mJ3Aumzm6ejQf4dv7WEKSjDmH8o0svTM83/tnA46cR0mSGxa6NnKwSpzWyNqq 5RhA== 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=IrRTyWKsVwu2tQq7pLa++dzsRTou7gUj3XSlupxW80A=; b=eYgQK8TbcmLFCSCCiQvbRU5MQtqz0fa6Ak91WEBz6BaotEDvHkujdkQS/aixwXb5wT 7kRnwxxVVJRW35OVSqnTK2PRF54pfWM1WlnTNhNQW41mh2Etga4hNerJGOwpgSRj6l6q KLNVCu5k3nzEjFLnxXAUKVrfAvkq1HgHozFbElt01WV1DvrMRV1fAd+RBs7sgmyk0pf9 /lfLVbK2uYpSpGcordSzeCgX4FtU0iRoyyIWuWgDz2FHDfzt2CwGU9ssIIJutZwAeeCi 0GFYcuFB58OyQqAb7EEOo56wV6PcY6SetY1lovwwO7kSJUYUZso2T54jVCVGrIfjbfqu qvhQ== X-Gm-Message-State: AOAM5309BwgVaU2lQjmpGbNhe8L/lMwh/uBWruaSpwkG5eTQQUCRBgMB 9TWwQzweYtSK+ysfIfynsiyt+263KZy/TuU4TL30pw7J X-Google-Smtp-Source: ABdhPJx2hEL5jPYnkjxTkeoa0Hw0/vb8sIjYkDChKwVfw6P05yLoAgmMO7ZRQRkeoPZTWigjouUJueFdgWJvY4fVPgM= X-Received: by 2002:a17:906:4cc1:: with SMTP id q1mr3326017ejt.415.1631099940924; Wed, 08 Sep 2021 04:19:00 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> <202109071734.187HY0WH004342@slippy.cwsent.com> In-Reply-To: <202109071734.187HY0WH004342@slippy.cwsent.com> From: Idwer Vollering Date: Wed, 8 Sep 2021 13:18:49 +0200 Message-ID: Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 To: Cy Schubert Cc: David Wolfskill , Jakob Alvermark , current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H4KQg5rKyz4j1N X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=m3uAl0i6; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of vidwer@gmail.com designates 2a00:1450:4864:20::62e as permitted sender) smtp.mailfrom=vidwer@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62e:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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:dkim] X-ThisMailContainsUnwantedMimeParts: N I can confirm this commit has addressed the wpa_supplicant 'breakage'. Thanks for fixing it. Op di 7 sep. 2021 om 19:37 schreef Cy Schubert : > > In message , David Wolfskill writes: > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web: https://nwtime.org > > The need of the many outweighs the greed of the few. > > On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > > > ...=20 > > > wlan0 does not associate after boot. (This is with iwm, AC 9260) > > >=20 > > > My workaround is simply 'ifconfig wlan0 up'. > > >=20 > > > After a few seconds wpa_supplicant associates and another few secods=20 > > > later I have a DHCP IP address. > > > .... > > > > I just tried that (running main-n249159-bb61ccd530b7), and that (also) > > works for me -- in case that data point is of use. > > Hi, > > Commit 5fcdc19a8111 has addressed this. > > > > From nobody Wed Sep 8 12:31:57 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 3CBB117AADA6 for ; Wed, 8 Sep 2021 12:32:00 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4M2m0ypbz3N44; Wed, 8 Sep 2021 12:32:00 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id ECC8C9E34; Wed, 8 Sep 2021 12:31:59 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id C6A342C951; Wed, 8 Sep 2021 13:31:58 +0100 (BST) Subject: Re: -CURRENT compilation time To: gljennjohn@gmail.com Cc: Stefan Esser , freebsd-current@freebsd.org References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> From: David Chisnall Message-ID: <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> Date: Wed, 8 Sep 2021 13:31:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210908105236.1abb8f9a@ernst.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 08/09/2021 11:52, Gary Jennejohn wrote: > Seems to me that there was an earlier mail about getting CMAKE to work > with FreeBSD builds. Could be worthwhile to look into getting ninja > to work also. But I could understand that there might be push-back, > since the project prefers to use utilities from the source tree. CMake is a build-system generator, Ninja is a build system. Usually the two are used together: CMake generates Ninja files, Ninja runs the build. Ninja is explicitly designed not to be written by hand. CMake can also emit other things, including POSIX Makefiles, but the Ninja build is usually the fastest. CMake and Ninja are both in package systems for Windows, macOS, *BSD, and all Linux distros that I've seen, unlike bmake, so universally easy to depend on for cross-builds. Cross compiling with bmake is much harder harder from anything that isn't FreeBSD. David From nobody Wed Sep 8 12:47:11 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 69BB117B3A60 for ; Wed, 8 Sep 2021 12:47:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4MNd2M1rz3jyT for ; Wed, 8 Sep 2021 12:47:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2a.google.com with SMTP id u1so1881120vsq.10 for ; Wed, 08 Sep 2021 05:47:29 -0700 (PDT) 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=kKpOSByUqJ1dvhI5Hrmq0LSlIc/yGFemZYP9Ei9g5Tc=; b=iwTdfBp4chSEJ2JAdr2hUBt2SuH4QoTEkujNKoqClrtq0KUVHrKb2tr8AKXO4+owrt rCMDLKZB48ziwQl6Z4o5Kiwl2YsuecFEFe0JFQvedhnrn5TBP8W4laUpwSBEL3cvYZj/ 6Uzrr1PJGVMjLqfF6DOAFmk69EMtbiwtS3KAcIdtdGLiLTUEjzRYN7sMbuxGj51f/5L1 f2uC0NLPGHU3l89amvEWdHNSvI//y/fT0iPCJKn1jMSEzPs1eFL2NLCWpXETEEebiWhS dm2wFKV6o08wdLfhvhubPC0TKaKwWVJZakreCcp+95mqGxKDZg1kOoHbHF40YHOU0uUk ND7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kKpOSByUqJ1dvhI5Hrmq0LSlIc/yGFemZYP9Ei9g5Tc=; b=YkQYmwVFL9YRBQNkXM7dSV3qXRgYVXT6Gj05SR6ZtRN31RLgs/hg+bkEso2y+PmNwB 32lzhJ8LlRKfriNPV+vEWbXLM1XB2WG5jO2MiG9+bXoYat3N717g9gcV3Qh81tDfycrN x99sEby/liuaC4T2dOhPI+qwv8e1sId1GYBDbjfra5CHlo5p5h7kViMYVQmgyS3BZrHp nSBQoxPwTZGRsjGcg294SswKRWDhgVIXAfk7saopPLKTZUpbhonfdjpMYFPgZx6jT/w1 wXtOdeDBCdwQh4lInIvQzDiNd4RX/eoKqfG5E7wvoSEbPMOR6837KckL2LHgexrrlU8U ppUg== X-Gm-Message-State: AOAM530b/Lcg5yBAOJUAVonqvHppgqyK4ZQ6UbOKYBnJaeNhYDS/ZIq+ X84tBsLb1Yu4OeCgbxif3uTgOu9PrAB3S0mXOPS0+Iu+S+GCQ3j0 X-Google-Smtp-Source: ABdhPJzU+61K7azshQugufkYmEdwdkJ+ARaxen9oBIuj37jGjLEAC51CUnjzAiVj0aB+UzjNXnKIePhtsQ/zgOKXhI0= X-Received: by 2002:a05:6102:2f6:: with SMTP id j22mr1747720vsj.12.1631105242913; Wed, 08 Sep 2021 05:47:22 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> In-Reply-To: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> From: Warner Losh Date: Wed, 8 Sep 2021 06:47:11 -0600 Message-ID: Subject: Re: -CURRENT compilation time To: David Chisnall Cc: Stefan Esser , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000098786c05cb7b4836" X-Rspamd-Queue-Id: 4H4MNd2M1rz3jyT X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000098786c05cb7b4836 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 8, 2021 at 2:59 AM David Chisnall wrote: > On 07/09/2021 18:02, Stefan Esser wrote: > > Wouldn't this break META_MODE? > > I have never managed to get META_MODE to work but my understanding is > that META_MODE is addressing a problem that doesn't really exist in any > other build system that I've used: that dependencies are not properly > tracked. > It does track the dependencies. It uses filemon(4) to do this so that every dependency is tracked. This is better than what other build systems do because no dependencies are missed. > When I do a build of LLVM with the upstream build system with no > changes, it takes Ninja approximately a tenth of a second to stat all of > the relevant files and tell me that I have no work to do. META_MODE > apparently lets the FreeBSD build system extract these dependencies and > do something similar, but it's not enabled by default and it's difficult > to make work. > META_MODE does the same thing, and it's just as fast as ninja make. And it has the advantage that, unlike meson, it isn't rebuilding the makefiles all the time. And apart from loading filmon, it was quite easy to enable last time I was using it (though I did have trouble finding the right docs). > > I'd rather be able to continue building the world within a few minutes > > (generally much less than 10 minutes, as long as there is no major LLVM > > upgrade) than have a faster LLVM build and then a slower build of the > world ... > > The rest of this thread has determined that building LLVM accounts for > half of the build time in a clean FreeBSD build. LLVM's CMake is not a > great example: it has been incrementally improved since CMake 2.8 and > doesn't yet use any of the modern CMake features that allow > encapsulating targets and providing import / export configurations. > > In spite of that, it generates a ninja file that compiles > *significantly* faster than the bmake-based system in FreeBSD. In other > projects that I've worked on with a similar-sized codebase to FreeBSD > that use CMake + Ninja, I've never had the same problems with build > speed that I have with FreeBSD. > The speed is comparable to META_MODE, but much faster than the default. It suffers a bit because our buildworld stuff is a kinda sorts not quite good enough dependency tracker and it's layered on top of that. > Working on LLVM, I generally spend well under 10% of my time either > waiting for builds or fighting the build system. Working on FreeBSD, I > generally spend over 90% of my time waiting for builds or fighting the > build system. This means that my productivity contributing to FreeBSD > is almost zero. > > For reference, changes to LLVM typically build for me in under 30 > seconds with Ninja, unless I've changed a header that everything > > In particular, building FreeBSD on a 10-24 core machine has very long > periods where a number of the cores are completely idle. > > Ninja also has a few other nice features that improve performance > relative to bmake: > > - It lets you put jobs in different pools. In LLVM this is used to > put link and compile jobs in different pools because linking with LLD > uses multiple threads and a lot more memory than compilation, so a > 10-core machine may want to do 12 compile jobs in parallel but only 2 > link jobs. This makes it much easier to completely saturate the machine. > This is nice. > - Ninja provides each parallel build task with a separate pipe for > stdout and stderr, and does not print their output unless a build step > fails (or unless you build with -v). With bmake, if a parallel build > fails I have to rerun the build without -j, because the output is > interleaved with succeeding jobs and it's difficult to see what actually > failed. With ninja, the output is from each failed job, with no > interleaving. > META_MODE does this too. It's the primary reason I use it, along with the speed. The big downside of ninja make is that it requires you to have some other, higher-level build system to generate the Makefiles. And my experience to date with meson is a mixed bag: it's quite a bit better than normal bmake for some things, and quite a bit worse for others in terms of the code you need to write to get things done, or the efforts required to debug mistakes. I've not used cmake as the ninja makefile generator, so I have no comments on it. Doing the conversion to at least meson would be a quite large job, at least by my initial estimates. Hacking bmake to generate ninja makefiles looks to be quite a bit simpler... But looks can be deceiving. Warner --00000000000098786c05cb7b4836-- From nobody Wed Sep 8 12:50:37 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0675817B6114 for ; Wed, 8 Sep 2021 12:50:42 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4MSK5TYtz3mJF; Wed, 8 Sep 2021 12:50:41 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f18:5600:5449:cc68:8dc4:e518] (p200300cd5f1856005449cc688dc4e518.dip0.t-ipconnect.de [IPv6:2003:cd:5f18:5600:5449:cc68:8dc4:e518]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 26CB49E41; Wed, 8 Sep 2021 12:50:41 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: Date: Wed, 8 Sep 2021 14:50:37 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 Subject: Re: -CURRENT compilation time Content-Language: en-US To: David Chisnall References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> From: Stefan Esser Cc: freebsd-current@freebsd.org In-Reply-To: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------52cROGg8SECfscciZvLSd0YI" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------52cROGg8SECfscciZvLSd0YI Content-Type: multipart/mixed; boundary="------------i8YLwYeOMxFAkQNdHxy8K044"; protected-headers="v1" From: Stefan Esser To: David Chisnall Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: -CURRENT compilation time References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> In-Reply-To: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> --------------i8YLwYeOMxFAkQNdHxy8K044 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 08.09.21 um 10:57 schrieb David Chisnall: > On 07/09/2021 18:02, Stefan Esser wrote: >> Wouldn't this break META_MODE? >=20 > I have never managed to get META_MODE to work but my understanding is t= hat > META_MODE is addressing a problem that doesn't really exist in any othe= r build > system that I've used: that dependencies are not properly tracked. META_MODE allows for complex interdependencies. They are no issue in the GPL/Linux world, since components are not integrated in the same way as has been practice in BSD for many decades. > When I do a build of LLVM with the upstream build system with no change= s, it > takes Ninja approximately a tenth of a second to stat all of the releva= nt files > and tell me that I have no work to do.=C2=A0 META_MODE apparently lets = the FreeBSD > build system extract these dependencies and do something similar, but i= t's not > enabled by default and it's difficult to make work. I tend to disagree on the last 5 words of your last sentence. It took me just a few seconds to activate, and it has worked without faul= t since. There are only 2 trivial steps. But it is easy to miss the fact, that WITH_META_MODE has to be added to /etc/src-env.conf, not /etc/src.conf: 1) Add "WITH_META_MODE=3Dyes" to /etc/src-env.conf (create file, if it do= es not exist) 2) Add "device filemon" to your kernel configuration or to the kld_load variable in /etc/rc.conf to load the kernel module (The kernel module can of course also be manually loaded at any time.) >> I'd rather be able to continue building the world within a few minutes= >> (generally much less than 10 minutes, as long as there is no major LLV= M >> upgrade) than have a faster LLVM build and then a slower build of the = world ... >=20 > The rest of this thread has determined that building LLVM accounts for = half of > the build time in a clean FreeBSD build.=C2=A0 LLVM's CMake is not a gr= eat example: > it has been incrementally improved since CMake 2.8 and doesn't yet use = any of > the modern CMake features that allow encapsulating targets and providin= g import > / export configurations. The build of LLVM is skipped if META_MODE is enabled, except if there really was a change to some LLVM header that causes a complete rebuild. A further speed-up can be had with ccache, but I found that it does not seem to make that much of a difference on my system. > In spite of that, it generates a ninja file that compiles *significantl= y* > faster than the bmake-based system in FreeBSD.=C2=A0 In other projects = that I've > worked on with a similar-sized codebase to FreeBSD that use CMake + Nin= ja, I've > never had the same problems with build speed that I have with FreeBSD. Possible, but if I watch the LLVM build with top or systat, I see that all my cores are busy, nearly throughout the full build. There are two methods that could theoretically speed-up the build: 1) make use of idle CPU cores 2) reduce the number of object files to build I do not see that there is much potential for 1), since there is a high degree of parallelism: >>> World build completed on Wed Sep 1 13:40:14 CEST 2021 >>> World built in 99 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 98.69 real 741.61 user 234.55 sys >>> World build completed on Thu Sep 2 23:22:04 CEST 2021 >>> World built in 98 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 98.34 real 780.41 user 228.67 sys >>> World build completed on Fri Sep 3 19:09:39 CEST 2021 >>> World built in 165 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 164.84 real 1793.62 user 241.11 sys >>> World build completed on Sun Sep 5 20:23:29 CEST 2021 >>> World built in 135 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 135.59 real 695.45 user 214.76 sys >>> World build completed on Mon Sep 6 21:10:44 CEST 2021 >>> World built in 478 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 479.22 real 11374.40 user 474.19 sys >>> World build completed on Wed Sep 8 11:51:03 CEST 2021 >>> World built in 652 seconds, ncpu: 32, make -j32 -------------------------------------------------------------- 652.14 real 17857.03 user 753.41 sys Calculating "(user + sys) / real" I get factors between 10 (in case of only minor changes) to 28 for larger recompiles (e.g. if lots of source files depend on an updated header), with 32 the theoretical limit for all cores continuously active during the build. META_MODE does not understand that updated build tools do not always require a full rebuild, but special cases have been added to the Makefile to reduce the number of unnecessary rebuilds. > Working on LLVM, I generally spend well under 10% of my time either wai= ting for > builds or fighting the build system.=C2=A0 Working on FreeBSD, I genera= lly spend > over 90% of my time waiting for builds or fighting the build system.=C2= =A0 This > means that my productivity contributing to FreeBSD is almost zero. >=20 > For reference, changes to LLVM typically build for me in under 30 secon= ds with > Ninja, unless I've changed a header that everything You should get the same effect from META_MODE. And META_MODE allows to execute make in any subtree of a larger source tree, provided there is a Makefile for that part of the sources, e.g.: $ cd /usr/src/usr.bin/clang/lld $ make -j 32 [...] $ touch /usr/src/contrib/llvm-project/lld/Common/Strings.cpp $ time make -j 32 Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/Common/String= s.o Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld.full Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld.debug Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld real 0m1.699s user 0m1.454s sys 0m3.745s This assumes that your world is up-to-date in general, which should be the case when working on a single component, e.g. one of the programs belonging to CLANG/LLVM. Compiling a single file and linking a single target does of course not allow for any parallelism. $ cd /usr/src/usr.bin/clang $ time make -j 32 > /dev/null real 0m24.650s user 8m58.381s sys 0m34.786s Some files have changed between the last "make buildworld" and now, but it takes less than 10 minutes of CPU time (i.e. 1 minute real time on a system with 6 cores / 12 threads) to update the obj directory. My system got an overall parallelism of 24 on that run ... And thereafter, there is hardly any overhead caused by bmake: $ time make -j 32 > /dev/null real 0m0.064s user 0m0.453s sys 0m0.029s The overhead for scanning all LLVM components if there was no change is absolutely negligible. Now lets touch a header that is included in a number of files: $ touch /usr/src/contrib/llvm-project/lld/include/lld/Common/Strings.h $ time make -j 32 | wc 41 82 3130 real 0m17.727s user 2m56.021s sys 0m8.237s The ratio of user+sys to real is a little above 10, which is not too bad if you consider that the link phase needs to wait for all object files. I really do not see that there is much to gain, here ... > In particular, building FreeBSD on a 10-24 core machine has very long p= eriods > where a number of the cores are completely idle. I do not observe this, and I'm using a 16 core / 32 thread CPU, which would be busy on all cores with just 16 parallel threads, just not taking advantage of SMT. And I see an overall factor (and load average) of 10 for small changes (with lots of I/O and little processing), 28 and beyond if larger parts of the system need to be rebuild. (BTW: This is a system with SATA drives in a RAIDZ1 configuration, which limits the I/O rate way below what an SSD based system might get.) > Ninja also has a few other nice features that improve performance relat= ive to > bmake: >=20 > =C2=A0- It lets you put jobs in different pools.=C2=A0 In LLVM this is = used to put link > and compile jobs in different pools because linking with LLD uses multi= ple > threads and a lot more memory than compilation, so a 10-core machine ma= y want > to do 12 compile jobs in parallel but only 2 link jobs.=C2=A0 This make= s it much > easier to completely saturate the machine. That may be an advantage on systems with relatively small RAM (compared t= o the number of threads supported in parallel). But I do see compilations and linking executing in parallel, i.e. just on= e linker activation while compiles run in parallel. Due to the multi-thread= ed execution of LLD that might cause the load average to slightly exceed the= number of threads, but only for a relatively short period of time. > =C2=A0- Ninja provides each parallel build task with a separate pipe fo= r stdout and > stderr, and does not print their output unless a build step fails (or u= nless > you build with -v).=C2=A0 With bmake, if a parallel build fails I have = to rerun the > build without -j, because the output is interleaved with succeeding job= s and > it's difficult to see what actually failed.=C2=A0 With ninja, the outpu= t is from > each failed job, with no interleaving. This makes it easier to spot the error line, but I've got used to the way= the output is formatted by a parallel make run. I always redirect the output into a file (either with nohup or with tee, depending on whether I plan to watch the build). I hardly ever have to us= e a single threaded build to spot an error, it is generally obvious from th= e build log in that file. But I do agree that separate output per build job makes this easier, just= not enough that I'd want to rework the whole build system. And especially= not if it breaks META_MODE. Regards, STefan --------------i8YLwYeOMxFAkQNdHxy8K044-- --------------52cROGg8SECfscciZvLSd0YI Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmE4sZ0FAwAAAAAACgkQR+u171r99URf yggAsMj51OT20hc/Xx+6LjiohXJh9AXXHO3JCfp/LFguuGSYl5zWfzL34oxsrEh10oQA1Dv+wGPX iAfpoZEjnd8KDH9KQOBgrziLmAYsDQ0bsIOgzlc8T07GmYqaGBgAzhf9JOeuowElhOf3wcy3CTi8 U+UwK5keUmcylBOnHYwdTZXlS5aaAW75y7iO9UrKbLFMV9j2Ge7MocOhOpUCf2P3GKBK2IUL5bHI Zr2NxlbmWolE6dvBn7a9bGOpoCL/8WHAHliZI8z7Dc+tr8Yw80ZFvLiTDpd0yXz1UBJ/hidrOB9L C3XcuEq5XHEKilfpgZzJfS4VBhxL5OtSvj2ogFYyYQ== =DHeo -----END PGP SIGNATURE----- --------------52cROGg8SECfscciZvLSd0YI-- From nobody Wed Sep 8 13:17:51 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 573D917C3C08 for ; Wed, 8 Sep 2021 13:17:57 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4H4N3n1XHLz4RRP for ; Wed, 8 Sep 2021 13:17:57 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id Nwb9mCn4oczbLNxSemQpMK; Wed, 08 Sep 2021 13:17:56 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NxScmdnAbU9pxNxSdmSF3q; Wed, 08 Sep 2021 13:17:56 +0000 X-Authority-Analysis: v=2.4 cv=Bbi7bph2 c=1 sm=1 tr=0 ts=6138b804 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=JAf30KXuAAAA:8 a=6Y_4qqUgK98lGMoaPawA:9 a=CjuIK1q_8ugA:10 a=UJ0tAi3fqDAA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 a=GEL62FyrTCmHtEug2d3R:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 99EF9D3E; Wed, 8 Sep 2021 06:17:53 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 188DHphS014656; Wed, 8 Sep 2021 06:17:51 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109081317.188DHphS014656@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Idwer Vollering cc: Cy Schubert , David Wolfskill , Jakob Alvermark , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> <202109071734.187HY0WH004342@slippy.cwsent.com> Comments: In-reply-to Idwer Vollering message dated "Wed, 08 Sep 2021 13:18:49 +0200." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Sep 2021 06:17:51 -0700 X-CMAE-Envelope: MS4xfNpm9K+znV8d2R3O47WFwuPasIRCsa2p4AUA0uL9xX6t48QragV1eeixdHV731mcO/CKMDOIGv6L0zIvUkK0bERPMU8cnAU8DV6/yyZw/1Yi4Ykkrzug lS3+Vu7ljHntTsvjz53Fv6GGcjl+pNsj3p61Fd7JNHLQo8dkkEsBZ2FKR7zkHDDRffM+o3YIRhk26tXgqx+Bjob4gFDErj3A4v9nPOu+ffAueDwMqC+JteTb Y5vae5K+quOwbUKxqy3IkIfS7aA3htUX65ATAd2cQuvz7lt1erZA586mixR9Iqcl X-Rspamd-Queue-Id: 4H4N3n1XHLz4RRP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Sorry for the breakage. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. In message , Idwer Vollering writes: > I can confirm this commit has addressed the wpa_supplicant 'breakage'. > Thanks for fixing it. > > Op di 7 sep. 2021 om 19:37 schreef Cy Schubert : > > > > In message , David Wolfskill writes > : > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: https://FreeBSD.org > > NTP: Web: https://nwtime.org > > > > The need of the many outweighs the greed of the few. > > > On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote: > > > > ...=20 > > > > wlan0 does not associate after boot. (This is with iwm, AC 9260) > > > >=20 > > > > My workaround is simply 'ifconfig wlan0 up'. > > > >=20 > > > > After a few seconds wpa_supplicant associates and another few secods=20 > > > > later I have a DHCP IP address. > > > > .... > > > > > > I just tried that (running main-n249159-bb61ccd530b7), and that (also) > > > works for me -- in case that data point is of use. > > > > Hi, > > > > Commit 5fcdc19a8111 has addressed this. > > > > > > > > From nobody Wed Sep 8 14:24:59 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0E6E617BC67A for ; Wed, 8 Sep 2021 14:25:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4PYW6gxJz4ph8 for ; Wed, 8 Sep 2021 14:25:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe32.google.com with SMTP id a21so2159635vsp.12 for ; Wed, 08 Sep 2021 07:25:19 -0700 (PDT) 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=B/IQGIAgwlwwSRTu7NmVN1H1yVQY/nRglstzqJ/BStc=; b=a5WMSI7H98/uhHCV0b1m0C2l1mrSpr5cJrUDCDIoDgR3kSwvkMKjqKAZkt9GvABCUK 8SOexcVzBiDmLyV+/l5wIvi+234ZhuLC8w9Qq0huAgE38E6eI6Y3XUFYJOb8K2IElzJ6 KsftKosG2Eh5lWQqEb+tF1V1cM1FVaDDKxM1Y03xGZjahu0IO/jiWqQ0bojEiGh+Q0MX RVxjVaaCrdTa4YrN6iEVDvWsXYOiTEoUWVMPzBTvtftwpN76FVHUt6ukLfuycPbCgs6c 3xbKYSsA0XfbWSr5Cce4m6AqO1MwepfvNc04jh73x2T74y0gRvtVj9faIuzJXdBG4u66 95Ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B/IQGIAgwlwwSRTu7NmVN1H1yVQY/nRglstzqJ/BStc=; b=TnEPTxcJK+BW34WSyZcycISEsGAG7CWLJtzgmThSI8cAge/BFrteHDlc7mkLD2qYtt RfVKmY0kS8OvKwVQFApIJOaEditA2iHx6zS71T+DtHxl3USuc/dV0n907hW0pu+02mPf CwAzjeuRVX5T3p1dh939G9QwoiXwAoE/qrtS3+ilkWPfWfIkI5ZgXOsi7mLavY4DfUeT mgyI56USD2RB609oPTyQVwdJIi9H1wLgAgN+ejIBqOHrz2uak1pN7lF0vlZIY17XQYu2 WZ+mRwTa8qY8VuX+T23xJhTYYSZXWJmMEPYXn2Puuf+JFyAIxNulnQB1056lZU2euxT1 Zmyw== X-Gm-Message-State: AOAM530V09mFhKzxN+A48Z6CF7XStbtUjotbnuL2Fft9wa0f7Dpolwi1 6W5pBAO2M/FDsVHpOIDPGBk+x5pahYIla1xgv928tA== X-Google-Smtp-Source: ABdhPJzyBGqRbNHRG/fzN4oOCTvLnwd3FIp9/NKiTdozNf9vIHHM9a9ztnMjg3mPj0deYWBqq7CWrOW/j1SFF1K/gD0= X-Received: by 2002:a05:6102:2f6:: with SMTP id j22mr2240203vsj.12.1631111112657; Wed, 08 Sep 2021 07:25:12 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> In-Reply-To: From: Warner Losh Date: Wed, 8 Sep 2021 08:24:59 -0600 Message-ID: Subject: Re: -CURRENT compilation time To: Stefan Esser Cc: David Chisnall , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000759f6505cb7ca611" X-Rspamd-Queue-Id: 4H4PYW6gxJz4ph8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000759f6505cb7ca611 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 8, 2021, 6:52 AM Stefan Esser wrote: > Am 08.09.21 um 10:57 schrieb David Chisnall: > > On 07/09/2021 18:02, Stefan Esser wrote: > >> Wouldn't this break META_MODE? > > > > I have never managed to get META_MODE to work but my understanding is > that > > META_MODE is addressing a problem that doesn't really exist in any other > build > > system that I've used: that dependencies are not properly tracked. > > META_MODE allows for complex interdependencies. They are no issue in the > GPL/Linux world, since components are not integrated in the same way as > has been practice in BSD for many decades. > > > When I do a build of LLVM with the upstream build system with no > changes, it > > takes Ninja approximately a tenth of a second to stat all of the > relevant files > > and tell me that I have no work to do. META_MODE apparently lets the > FreeBSD > > build system extract these dependencies and do something similar, but > it's not > > enabled by default and it's difficult to make work. > > I tend to disagree on the last 5 words of your last sentence. > > It took me just a few seconds to activate, and it has worked without fault > since. > > There are only 2 trivial steps. But it is easy to miss the fact, that > WITH_META_MODE has to be added to /etc/src-env.conf, not /etc/src.conf: > > 1) Add "WITH_META_MODE=yes" to /etc/src-env.conf (create file, if it does > not exist) > > 2) Add "device filemon" to your kernel configuration or to the kld_load > variable in /etc/rc.conf to load the kernel module > > (The kernel module can of course also be manually loaded at any time.) > > >> I'd rather be able to continue building the world within a few minutes > >> (generally much less than 10 minutes, as long as there is no major LLVM > >> upgrade) than have a faster LLVM build and then a slower build of the > world ... > > > > The rest of this thread has determined that building LLVM accounts for > half of > > the build time in a clean FreeBSD build. LLVM's CMake is not a great > example: > > it has been incrementally improved since CMake 2.8 and doesn't yet use > any of > > the modern CMake features that allow encapsulating targets and providing > import > > / export configurations. > > The build of LLVM is skipped if META_MODE is enabled, except if there > really was a change to some LLVM header that causes a complete rebuild. > > A further speed-up can be had with ccache, but I found that it does not > seem to make that much of a difference on my system. > > > In spite of that, it generates a ninja file that compiles *significantly* > > faster than the bmake-based system in FreeBSD. In other projects that > I've > > worked on with a similar-sized codebase to FreeBSD that use CMake + > Ninja, I've > > never had the same problems with build speed that I have with FreeBSD. > > Possible, but if I watch the LLVM build with top or systat, I see that > all my cores are busy, nearly throughout the full build. There are two > methods that could theoretically speed-up the build: > > 1) make use of idle CPU cores > > 2) reduce the number of object files to build > > I do not see that there is much potential for 1), since there is a high > degree of parallelism: > > >>> World build completed on Wed Sep 1 13:40:14 CEST 2021 > >>> World built in 99 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 98.69 real 741.61 user 234.55 sys > > >>> World build completed on Thu Sep 2 23:22:04 CEST 2021 > >>> World built in 98 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 98.34 real 780.41 user 228.67 sys > > >>> World build completed on Fri Sep 3 19:09:39 CEST 2021 > >>> World built in 165 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 164.84 real 1793.62 user 241.11 sys > > >>> World build completed on Sun Sep 5 20:23:29 CEST 2021 > >>> World built in 135 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 135.59 real 695.45 user 214.76 sys > > >>> World build completed on Mon Sep 6 21:10:44 CEST 2021 > >>> World built in 478 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 479.22 real 11374.40 user 474.19 sys > > >>> World build completed on Wed Sep 8 11:51:03 CEST 2021 > >>> World built in 652 seconds, ncpu: 32, make -j32 > -------------------------------------------------------------- > 652.14 real 17857.03 user 753.41 sys > > Calculating "(user + sys) / real" I get factors between 10 (in case > of only minor changes) to 28 for larger recompiles (e.g. if lots > of source files depend on an updated header), with 32 the theoretical > limit for all cores continuously active during the build. > > META_MODE does not understand that updated build tools do not always > require a full rebuild, but special cases have been added to the > Makefile to reduce the number of unnecessary rebuilds. > > > Working on LLVM, I generally spend well under 10% of my time either > waiting for > > builds or fighting the build system. Working on FreeBSD, I generally > spend > > over 90% of my time waiting for builds or fighting the build system. > This > > means that my productivity contributing to FreeBSD is almost zero. > > > > For reference, changes to LLVM typically build for me in under 30 > seconds with > > Ninja, unless I've changed a header that everything > > You should get the same effect from META_MODE. > > And META_MODE allows to execute make in any subtree of a larger source > tree, provided there is a Makefile for that part of the sources, e.g.: > > $ cd /usr/src/usr.bin/clang/lld > $ make -j 32 > [...] > $ touch /usr/src/contrib/llvm-project/lld/Common/Strings.cpp > $ time make -j 32 > Building > /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/Common/Strings.o > Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld.full > Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld.debug > Building /usr/obj/usr/git/src/amd64.amd64/usr.bin/clang/lld/ld.lld > > real 0m1.699s > user 0m1.454s > sys 0m3.745s > > This assumes that your world is up-to-date in general, which should be > the case when working on a single component, e.g. one of the programs > belonging to CLANG/LLVM. Compiling a single file and linking a single > target does of course not allow for any parallelism. > > $ cd /usr/src/usr.bin/clang > $ time make -j 32 > /dev/null > real 0m24.650s > user 8m58.381s > sys 0m34.786s > > Some files have changed between the last "make buildworld" and now, but > it takes less than 10 minutes of CPU time (i.e. 1 minute real time on > a system with 6 cores / 12 threads) to update the obj directory. My > system got an overall parallelism of 24 on that run ... > > And thereafter, there is hardly any overhead caused by bmake: > > $ time make -j 32 > /dev/null > real 0m0.064s > user 0m0.453s > sys 0m0.029s > > The overhead for scanning all LLVM components if there was no change is > absolutely negligible. > > Now lets touch a header that is included in a number of files: > > $ touch /usr/src/contrib/llvm-project/lld/include/lld/Common/Strings.h > $ time make -j 32 | wc > 41 82 3130 > > real 0m17.727s > user 2m56.021s > sys 0m8.237s > > The ratio of user+sys to real is a little above 10, which is not too bad > if you consider that the link phase needs to wait for all object files. > > I really do not see that there is much to gain, here ... > > > In particular, building FreeBSD on a 10-24 core machine has very long > periods > > where a number of the cores are completely idle. > > I do not observe this, and I'm using a 16 core / 32 thread CPU, which > would be busy on all cores with just 16 parallel threads, just not > taking advantage of SMT. And I see an overall factor (and load average) > of 10 for small changes (with lots of I/O and little processing), > 28 and beyond if larger parts of the system need to be rebuild. > (BTW: This is a system with SATA drives in a RAIDZ1 configuration, > which limits the I/O rate way below what an SSD based system might > get.) > > > Ninja also has a few other nice features that improve performance > relative to > > bmake: > > > > - It lets you put jobs in different pools. In LLVM this is used to put > link > > and compile jobs in different pools because linking with LLD uses > multiple > > threads and a lot more memory than compilation, so a 10-core machine may > want > > to do 12 compile jobs in parallel but only 2 link jobs. This makes it > much > > easier to completely saturate the machine. > > That may be an advantage on systems with relatively small RAM (compared to > the number of threads supported in parallel). > > But I do see compilations and linking executing in parallel, i.e. just one > linker activation while compiles run in parallel. Due to the multi-threaded > execution of LLD that might cause the load average to slightly exceed the > number of threads, but only for a relatively short period of time. > > > - Ninja provides each parallel build task with a separate pipe for > stdout and > > stderr, and does not print their output unless a build step fails (or > unless > > you build with -v). With bmake, if a parallel build fails I have to > rerun the > > build without -j, because the output is interleaved with succeeding jobs > and > > it's difficult to see what actually failed. With ninja, the output is > from > > each failed job, with no interleaving. > > This makes it easier to spot the error line, but I've got used to the way > the output is formatted by a parallel make run. > > I always redirect the output into a file (either with nohup or with tee, > depending on whether I plan to watch the build). I hardly ever have to use > a single threaded build to spot an error, it is generally obvious from the > build log in that file. > > But I do agree that separate output per build job makes this easier, just > not enough that I'd want to rework the whole build system. And especially > not if it breaks META_MODE. > Meta mode for me creates target.meta files with the build output in them, so it is easy to find after the fact. Warner Regards, STefan > --000000000000759f6505cb7ca611-- From nobody Wed Sep 8 20:32:16 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0A8E817A1236 for ; Wed, 8 Sep 2021 20:32:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4Yj86cbdz4Xn5 for ; Wed, 8 Sep 2021 20:32:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe33.google.com with SMTP id p14so3208842vsm.2 for ; Wed, 08 Sep 2021 13:32:28 -0700 (PDT) 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=c/IAp0TEC5eUUH3jEdCmkW2Q0s38p7L5AUAONcC0Ey0=; b=OVVywxMrLQdklGQ3FtZMzDXlBapkkqEuL+YNj6vLevY0SlqNxe/c35BvFHXu/Dixg4 0FsdiD6TwW3gnJPfC8H3Nzne6smqISfm0Y3n+zsiOKOVSqM45BreERyTnLiV227MbidJ K6WbZILI013XlUR0st16tCK3gyrLTR7qMGLhc0M9EqDstuFBSQ3UmSkPapUlGssaO95I aTa5R05hKUsyimGzTgxklpOjt+AsJz+DdMljBX59hAE2hFmc8K8BIIaWjGJmkEkj8Mrj IkdZKF+HHQt1aiYMu1swybFlIdlXRPOrobZQgLHhSsIyocH8YFDK3uJF/A4j0wnY/xbb dctQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c/IAp0TEC5eUUH3jEdCmkW2Q0s38p7L5AUAONcC0Ey0=; b=AGsfVF5voFhLAhen5QxUbuejzDYgfNxYlxGPaQgMBc0HIoCNZehwGw0CaTy/BZFKro 2GSry5z22a/7pe8HHsLngKzGbgk099C2wF+dg4oDMJ7BwMhMZsC93Ei+k+fmyUklwVel avoFyzq98BaPbfU6EouWlfC4mfweGzP/t8BLjaKsS/NPIwdJxTBSDDZABEQcHXa+nofS tttTqvL6I5etaIQlfR4QQklZ4kvX4KoAWb74SVylrJ8la7Ao6/5SfVN/YnXO4optW1jt aONHgfC4KPmyQm4pzroUT+gSHZQSnXTNaF9aglid2te+17jVYeCaVV8QELJm+8VPfsfK 1Qhw== X-Gm-Message-State: AOAM533Eprh2oZeFTXc6KdHhOWLPdmqAKbWteb5F2+NZxTkJkJqe17Lw 97bCBvUA7ywqI/GLTRXFfNUlm0F7KlwOL/RAFO6cqQ== X-Google-Smtp-Source: ABdhPJwRRfqLnyiqYQjpNzaACGpJ0mQSVcrsBWPAtg377EXnotps/Je/Qi9jug6xxeMDowtvWXLNTXTtmpsMSx6M60Y= X-Received: by 2002:a05:6102:2f6:: with SMTP id j22mr3801563vsj.12.1631133148062; Wed, 08 Sep 2021 13:32:28 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> In-Reply-To: <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> From: Warner Losh Date: Wed, 8 Sep 2021 14:32:16 -0600 Message-ID: Subject: Re: -CURRENT compilation time To: David Chisnall Cc: Gary Jennejohn , Stefan Esser , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000df39f105cb81c784" X-Rspamd-Queue-Id: 4H4Yj86cbdz4Xn5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000df39f105cb81c784 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 8, 2021, 6:33 AM David Chisnall wrote: > On 08/09/2021 11:52, Gary Jennejohn wrote: > > Seems to me that there was an earlier mail about getting CMAKE to work > > with FreeBSD builds. Could be worthwhile to look into getting ninja > > to work also. But I could understand that there might be push-back, > > since the project prefers to use utilities from the source tree. > > CMake is a build-system generator, Ninja is a build system. Usually the > two are used together: CMake generates Ninja files, Ninja runs the > build. Ninja is explicitly designed not to be written by hand. > > CMake can also emit other things, including POSIX Makefiles, but the > Ninja build is usually the fastest. > > CMake and Ninja are both in package systems for Windows, macOS, *BSD, > and all Linux distros that I've seen, unlike bmake, so universally easy > to depend on for cross-builds. Cross compiling with bmake is much > harder harder from anything that isn't FreeBSD. > This may be true. I've never had a problem on mac or linux, but my windows experience is thin. I got looking at the problem, btw, to see if ninja was faster than meta mode. Ninja files aren't horrible to generate, but I never got past the early proof of concept phase... it seemed possible to implement a make ninja target... I'd wanted to use this day to day if it was better than meta. Mason, however looked much harder to generate, but I didn't spend a lot of time on it. I would think this sort of work would be more of a one shot. Didn't look at cmake at all, but I imagine it would be similar... Warner > --000000000000df39f105cb81c784-- From nobody Wed Sep 8 23:04:46 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C79D517C2EFD for ; Wed, 8 Sep 2021 23:04:57 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4d543sV9z3JsG for ; Wed, 8 Sep 2021 23:04:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 188N4krh031495 for ; Thu, 9 Sep 2021 08:04:47 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 9 Sep 2021 08:04:46 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: -CURRENT compilation time Message-Id: <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> In-Reply-To: References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H4d543sV9z3JsG X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.35 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.81)[-0.814]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.93)[-0.932]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[sakura.ne.jp]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Wed, 8 Sep 2021 14:32:16 -0600 Warner Losh wrote: > On Wed, Sep 8, 2021, 6:33 AM David Chisnall wrote: > > > On 08/09/2021 11:52, Gary Jennejohn wrote: > > > Seems to me that there was an earlier mail about getting CMAKE to work > > > with FreeBSD builds. Could be worthwhile to look into getting ninja > > > to work also. But I could understand that there might be push-back, > > > since the project prefers to use utilities from the source tree. > > > > CMake is a build-system generator, Ninja is a build system. Usually the > > two are used together: CMake generates Ninja files, Ninja runs the > > build. Ninja is explicitly designed not to be written by hand. > > > > CMake can also emit other things, including POSIX Makefiles, but the > > Ninja build is usually the fastest. > > > > CMake and Ninja are both in package systems for Windows, macOS, *BSD, > > and all Linux distros that I've seen, unlike bmake, so universally easy > > to depend on for cross-builds. Cross compiling with bmake is much > > harder harder from anything that isn't FreeBSD. > > > > This may be true. I've never had a problem on mac or linux, but my windows > experience is thin. > > I got looking at the problem, btw, to see if ninja was faster than meta > mode. Ninja files aren't horrible to generate, but I never got past the > early proof of concept phase... it seemed possible to implement a make > ninja target... I'd wanted to use this day to day if it was better than > meta. > > Mason, however looked much harder to generate, but I didn't spend a lot of > time on it. I would think this sort of work would be more of a one shot. > Didn't look at cmake at all, but I imagine it would be similar... > > Warner > > > What about devel/samurai, ninja-compatible build tool written in C? devel/ninja/Makefile has USES= python in it, so it maybe require python to run or at least build. In addition, ports framework can use it instead of ninja. See {PORTSDIR}/Mk/Uses/ninja.mk. -- Tomoaki AOKI From nobody Wed Sep 8 23:10:27 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7E85617C75D5 for ; Wed, 8 Sep 2021 23:10:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4dCp2xWcz3NGF for ; Wed, 8 Sep 2021 23:10:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vk1-xa2e.google.com with SMTP id g18so18161vkq.8 for ; Wed, 08 Sep 2021 16:10:46 -0700 (PDT) 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=6R+US1J5vdq2sl50WIq+m/8rNobl1+SvKVrVArsMtj4=; b=hPoeNCDcZH1Prd4srEccIXTwGZ6m9wzzBQn1Ixp5OSk2aSUH4fkgf7U9+MEp4MwNPf XP2w8e2IqgS8vX6Vogj5gEsMaQPhr0CZFMV+YQAGWcFJmaLIu2G7nsCBrJSpjJojweg1 ZfVjJHucX3Pi/XLRjciwwdaxFlGNLI0ptbnblZvEAtX7cXYvC0L7Be6JkrC6MmfA6VFw gp+c34fXvnLvRW6qQk2IJKXlPnfXlQiXZ2GtTMBp9+ZqIlBCpWfTGF4DTCMP9GX7fDb/ Q5ly6BCKGJiQnrSSFnrEZ5+mzNgIOZYb+SlKCb7XpQSJurn/2Vv8E6J1B4prDwlGRUqS C0yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6R+US1J5vdq2sl50WIq+m/8rNobl1+SvKVrVArsMtj4=; b=TcY6NUqbRtZ1xkbk8Kzy//Q4mwUANqeGm4P7uliZ6FdFtpjRIGf4kHebm31+rwOxmP 8sgzzUnyqe2P4QyEALPDRanaseNx0QifzgsfT7xjARqUcM0m22OIQuMgKugBidxRwp6j CqDLAFP8glpK8PZU4Cc7z+ElAICGOkvHcqGlELS3dlZcLyGJYXfn1HK3T6jJMb+XTtU7 gY0+kFKku8y0a7Q2zBSJxsWexc+gsVxTvyv17cCKz+sTnoz7EEKlRwekOguRl1+u5ijO 9Ee4zUI/T71gZHLms4sdKTCJEihuo+DHqmIXAlD+RsuWNWs7aEIFkuaBN86B6y+X/f6V Zj+w== X-Gm-Message-State: AOAM533of2Bjo/WhIOhzJVLXH9MFYDozinq1G+dhWjIwBQWFlZh86TTY P8EpJA2RUxgRg3qK0e9IcmmOYcYjSWzWkB8VpBmDfqNs6cw= X-Google-Smtp-Source: ABdhPJy9QBEbnMoJDULqbG3+hJYgH4ZP0SKYa+6fuHnbT9UfKP/e9YDpwo5i3M1B3vcmZWA2yg4crQjjdz+IbSSzpG8= X-Received: by 2002:a05:6122:d95:: with SMTP id bc21mr295889vkb.23.1631142639669; Wed, 08 Sep 2021 16:10:39 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> In-Reply-To: <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> From: Warner Losh Date: Wed, 8 Sep 2021 17:10:27 -0600 Message-ID: Subject: Re: -CURRENT compilation time To: Tomoaki AOKI Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000009de6fc05cb83fd8d" X-Rspamd-Queue-Id: 4H4dCp2xWcz3NGF X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000009de6fc05cb83fd8d Content-Type: text/plain; charset="UTF-8" On Wed, Sep 8, 2021, 5:06 PM Tomoaki AOKI wrote: > On Wed, 8 Sep 2021 14:32:16 -0600 > Warner Losh wrote: > > > On Wed, Sep 8, 2021, 6:33 AM David Chisnall > wrote: > > > > > On 08/09/2021 11:52, Gary Jennejohn wrote: > > > > Seems to me that there was an earlier mail about getting CMAKE to > work > > > > with FreeBSD builds. Could be worthwhile to look into getting ninja > > > > to work also. But I could understand that there might be push-back, > > > > since the project prefers to use utilities from the source tree. > > > > > > CMake is a build-system generator, Ninja is a build system. Usually > the > > > two are used together: CMake generates Ninja files, Ninja runs the > > > build. Ninja is explicitly designed not to be written by hand. > > > > > > CMake can also emit other things, including POSIX Makefiles, but the > > > Ninja build is usually the fastest. > > > > > > CMake and Ninja are both in package systems for Windows, macOS, *BSD, > > > and all Linux distros that I've seen, unlike bmake, so universally > easy > > > to depend on for cross-builds. Cross compiling with bmake is much > > > harder harder from anything that isn't FreeBSD. > > > > > > > This may be true. I've never had a problem on mac or linux, but my > windows > > experience is thin. > > > > I got looking at the problem, btw, to see if ninja was faster than meta > > mode. Ninja files aren't horrible to generate, but I never got past the > > early proof of concept phase... it seemed possible to implement a make > > ninja target... I'd wanted to use this day to day if it was better than > > meta. > > > > Mason, however looked much harder to generate, but I didn't spend a lot > of > > time on it. I would think this sort of work would be more of a one shot. > > Didn't look at cmake at all, but I imagine it would be similar... > > > > Warner > > > > > > > What about devel/samurai, ninja-compatible build tool written in C? > > devel/ninja/Makefile has USES= python in it, so it maybe require python > to run or at least build. > > In addition, ports framework can use it instead of ninja. > See {PORTSDIR}/Mk/Uses/ninja.mk. > I'll have to take a look next time I play with this stuff Warner -- > Tomoaki AOKI > > --0000000000009de6fc05cb83fd8d-- From nobody Wed Sep 8 23:58:20 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AF96817B83CC for ; Wed, 8 Sep 2021 23:58:41 +0000 (UTC) (envelope-from contact@shiori.com.br) Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) (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 4H4fH31LHmz3tlf for ; Wed, 8 Sep 2021 23:58:38 +0000 (UTC) (envelope-from contact@shiori.com.br) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shiori.com.br; s=key1; t=1631145511; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=VmMS1kgLUVHp+3K2qhAkpbWHyTAZoplDpJSiJPtAXjs=; b=IP0LUXTxDo8CjRLZuj8Ab1gI601oOhFzirOZ9owx2uVH9jBJuMotF9kpj+5nea9mBFVCP8 s3aNXYTPJuiH1/FcjyZZ+klJvrWcDwlDXCvMcFHLt2QtTrcUyyGvniWUgZ9BWjHcZzwMA9 y4QZmVIoAoHlcpwHUVScLn+fa0OHNvc= To: Cy Schubert Cc: current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-Reply-To: <202109071734.187HY0WH004342@slippy.cwsent.com> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> <202109071734.187HY0WH004342@slippy.cwsent.com> Date: Wed, 08 Sep 2021 20:58:20 -0300 Message-ID: <86ilzaoc0z.fsf@shiori.com.br> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: contact@shiori.com.br X-Rspamd-Queue-Id: 4H4fH31LHmz3tlf X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=shiori.com.br header.s=key1 header.b=IP0LUXTx; dmarc=pass (policy=quarantine) header.from=shiori.com.br; spf=pass (mx1.freebsd.org: domain of contact@shiori.com.br designates 188.165.223.204 as permitted sender) smtp.mailfrom=contact@shiori.com.br X-Spamd-Result: default: False [-3.60 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[shiori.com.br:s=key1]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_MISSING_CHARSET(2.50)[]; R_SPF_ALLOW(-0.20)[+ip4:188.165.223.204]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[shiori.com.br:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[shiori.com.br,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:16276, ipnet:188.165.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[188.165.223.204:from] Reply-To: contact@shiori.com.br From: Filipe da Silva Santos via current X-Original-From: Filipe da Silva Santos X-ThisMailContainsUnwantedMimeParts: N --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, thank you for the support, and sorry for the late feedback. The procedure `wpa_poststart' didn't solve the regression on my system. wlan0 doesn't seem to come up. I have the following output on my log: | Sep 8 19:09:43 misaka wpa_supplicant[23325]: ioctl[SIOCS80211, op=3D103,= val=3D0, arg_len=3D128]: Operation now in progress | Sep 8 19:09:43 misaka wpa_supplicant[23325]: wlan0: CTRL-EVENT-SCAN-FAIL= ED ret=3D-1 retry=3D1 Here is a sanitized version of my wpa_supplicant.conf: ctrl_interface=3D/var/run/wpa_supplicant eapol_version=3D1 ap_scan=3D1 fast_reauth=3D1 country=3DBR network=3D{ ssid=3D"********" psk=3D"****************" priority=3D5 } [...] and rc.conf related settings: [...] ifconfig_wlan0=3D"WPA powersave 10.0.0.110 netmask 0xffffff00 broadcast 10.= 0.0.255" defaultrouter=3D"10.0.0.1" wlans_iwm0=3D"wlan0" create_args_wlan0=3D"country BR regdomain FCC" [...] The last fix still works, although `sleep' isn't necessary. @@ -29,6 +29,7 @@ } =20 wpa_poststart() { + ifconfig ${ifn} down ifconfig ${ifn} up } Cheers, =2D- Filipe da Silva Santos 102E 1944 2189 31FF 06EB 3F79 760B AE45 F7B3 008E --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJKBAEBCAA0FiEEEC4ZRCGJMf8G6z95dguuRfezAI4FAmE5Th0WHGNvbnRhY3RA c2hpb3JpLmNvbS5icgAKCRB2C65F97MAjrcND/4lszQU/OeCzDfvTwIqi2sYo++7 PfohX0encfad3e1xOFyxfcmXHDMso8B6Ag8K5I8lRzH+B3IKQiL81iTB3a4ptp7H BroPhR6aIa4pYVZrjbUjenmjjxgks3fMRcQ/Z9cvnpypE1VlqQJakZYeb/iwh/KO h57RLfYSHuu6nTfijzXQIxmez0Zy8sbeQ3eIWJTrHTjUsPp5tYys/jGBp4ezwW6F gi/sDPLG8jz7u8gxuT0DraPBvhb7vYG8ebyLwO9z71Evxb7hxr9XYy0pHKV7nHok cZ8xmfAIpqMaS9FUWaXlg5Zw767GirkIJVqEet9JjI8kxqOpPBs7Aw4tOMSR8bXa skkkJvvOhKU+e4SqdPoTEVenawdfSEfkpUkpa7u0R+Jegx/20tA+c1uSr1cHyk3F tigg4ldkrQCVZYStGyodvh9VFwTWouPN3A3yFvE6GLi6gAN6CeA5Tl8E7IQ8bzem OrNrkDCNd+5o8UdMfzkaRdphHJ1D7RuU/YR85HsVwJaunloWUovbzORmqURm7hIT iwq7VmnIzGBP1SRDuYSjOg292xqtVcBps9LpFOMqywu3DcqxkzF8p4EU1ygwg6pF fHYSUw9Q2YcYtH7Txpl/fXkfhknOqSSiatZyEnXX+uytw5785kdQcC9RTT88xdKf miFci4KIGG+89tKTiQ== =7YpB -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Sep 9 01:08:50 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D24D617AF164 for ; Thu, 9 Sep 2021 01:09:13 +0000 (UTC) (envelope-from dan@banta.info) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4grT1Mblz4lGJ for ; Thu, 9 Sep 2021 01:09:13 +0000 (UTC) (envelope-from dan@banta.info) Received: by mail-lf1-x132.google.com with SMTP id c8so241142lfi.3 for ; Wed, 08 Sep 2021 18:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=banta-info.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mX/sFEauWH6zC7/ccUQlfzwgCM/n0+9adJtL1AYyn+M=; b=BW3cEp/uVxKfT5c6mFcaomrTNxUXRKA2viiocY/uBKIwm6psrT9crHM210zPN8NNh9 wzuINmiUXNNN6sWVcBM8dC7goIZo4gc8GhNzs5FY3m4vp1lU0wUQm6Yc43QSXMhMS7wC ruUg5cqRw7+dhBlJfNia/FO6PVdnA3nkB4PHE5ifdaldobpOIGTb0EcU7nPj9RGMd1Lw AcCVvPvKPl30XuLDlgNbKDa2MaUc5l75ocHu5fqUjFBH7ZyhLfFzV8t9870KUs+DJkmt u9p/PURhLqYRh7t7EBEZtPISg00Spmx6kXq+cwbzQOUKYM0RS96Mco2TZqT1M4Rov1Y6 QxNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mX/sFEauWH6zC7/ccUQlfzwgCM/n0+9adJtL1AYyn+M=; b=58vXJGeNg/Zg8Mx2Z26s/Nm88kyVd/XQpa2hWTGla3kOO7itnsB1wfMnppmMgtLHha n0irDzaz/cVueIjt74MqfyXH+QcuHRMSvXojxkMEII+EedlWPYUL+kkcGhcsL9hB3Z5l eZ8nmuIsKxlLdbBqELpqNujTFGw47X/acD7UNbl7Sh/k9nRChaXqxu1je3Vvyh3G6a4/ DrGKaX+ZoPK+UyTVfVNNM7PLbISDrS+9p9xBehO3EnGdIVXJULompYGxigyuiBt29CZN E++zPkFtxxKndrBedJHmGnms5opCVq2b8jaV0wmtN2wCwHL7h9KaFej5DURlHrRpvO/x zgng== X-Gm-Message-State: AOAM533uYQ1x57QKx0o40hXlfVu/vQEFHM3HhH5HFEbHDof6XyPzcFMz xZ4UIyCUNQI59Ri6wDpr24llkW0P1xqcrGAC5hw5xszf+IvL4NFH X-Google-Smtp-Source: ABdhPJwjAoMiUo5/uBwSovq/Y4UIHFt33sEWCL1hAWPcVYPSE+8poYXHwYnqcp/5ZrSMvgsv4IjpaEq1XkRU+6d6694= X-Received: by 2002:a19:6b18:: with SMTP id d24mr396955lfa.84.1631149745707; Wed, 08 Sep 2021 18:09:05 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: "Banta, Dan" Date: Wed, 8 Sep 2021 21:08:50 -0400 Message-ID: Subject: Re: Call for participation To: Warner Losh Cc: FreeBSD Current , FreeBSD Hackers , FreeBSD Ports Content-Type: multipart/alternative; boundary="0000000000002b324d05cb85a59d" X-Rspamd-Queue-Id: 4H4grT1Mblz4lGJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=banta-info.20150623.gappssmtp.com header.s=20150623 header.b="BW3cEp/u"; dmarc=none; spf=pass (mx1.freebsd.org: domain of dan@banta.info designates 2a00:1450:4864:20::132 as permitted sender) smtp.mailfrom=dan@banta.info X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[banta-info.20150623.gappssmtp.com:s=20150623]; FREEFALL_USER(0.00)[dan]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[banta.info]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[banta-info.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::132:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000002b324d05cb85a59d Content-Type: text/plain; charset="UTF-8" Warner, Thank you for asking and I am interested. Regards, Dan On Thu, Sep 2, 2021 at 10:46 AM Warner Losh wrote: > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would come in phase 2 since phase 1 was limited to moving away > from subversion and to git. > > Now's the time for phase 2. The deferred items included better CI > pipelines, better integration with popular hosting sites like github and > gitlab, a look at the tools we have today and how they fit together, and a > bunch of other items that were less well defined. I've spent the last > several months looking at the different practices in open source, > looking at our tools, etc. We have bits and pieces of many of these items, > but are missing some glue between what we have. Other areas need more > extensive work. > > To coordinate this work, I'll be leading a team to look at what we can do > in the short term, the medium term and where we think we want to be in the > long term. I plan on having bi-weekly meetings to discuss different issues > that come up, to coordinate work and experiments and to give some structure > to encouragement for progress to be made. > > This will be a collaborative effort between the developers and the user > community that contributes patches to any part of FreeBSD (the base, ports > and docs). If you are interested in participating, please drop me a line. > We'll have a core office hours to talk about this soon, and I'd like to > start discussions with those that are interested before hand, as well as > invite people to participate in the office hours. After that, we'll have a > kick off meeting that's open to everybody who can respectfully contribute. > > Looking forward to hearing from you. > > Warner > --0000000000002b324d05cb85a59d-- From nobody Thu Sep 9 03:18:47 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AAE0117A013F for ; Thu, 9 Sep 2021 03:18:51 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (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 4H4kk33vvWz3tn1 for ; Thu, 9 Sep 2021 03:18:51 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id O6Qgmukyzps7POAaRmyfXS; Thu, 09 Sep 2021 03:18:51 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id OAaPmQx9TdCHGOAaQmySMY; Thu, 09 Sep 2021 03:18:51 +0000 X-Authority-Analysis: v=2.4 cv=SdyUytdu c=1 sm=1 tr=0 ts=61397d1b a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=a_qd0PwhAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=IpLs3_Jh_ziu9vFamdIA:9 a=CjuIK1q_8ugA:10 a=vEXHPetyIDmorGAAYsTw:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 00D1CB86; Wed, 8 Sep 2021 20:18:48 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 1893Il8H014439; Wed, 8 Sep 2021 20:18:47 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109090318.1893Il8H014439@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: contact@shiori.com.br cc: Cy Schubert , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <86ilzaoc0z.fsf@shiori.com.br> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> <202109071734.187HY0WH004342@slippy.cwsent.com> <86ilzaoc0z.fsf@shiori.com.br> Comments: In-reply-to Filipe da Silva Santos via current message dated "Wed, 08 Sep 2021 20:58:20 -0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Sep 2021 20:18:47 -0700 X-CMAE-Envelope: MS4xfJop4GXM/YWzQP1H4WF43EsStRGeI+HmiNTcrvpoQgdfU7B7LRdcMWipianYzINpMEBxnE6R7XSupYaAFFy3BJ6UjK4n21N6YOE1a/Zbhi1gy3X6mAkJ 1/GjDCwckP3wvjLbAjbuSM8kw8Q1z1gea9qHvFzyGUR/ex0mcYViTLSNS7J6Rh5sWWximM0zsQalmeDUDLvaq21YODFJw1eaArIs8OFLrxCPlP6/rKhs0Tje X-Rspamd-Queue-Id: 4H4kk33vvWz3tn1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <86ilzaoc0z.fsf@shiori.com.br>, Filipe da Silva Santos via current w rites: > Hi, thank you for the support, and sorry for the late feedback. > > The procedure `wpa_poststart' didn't solve the regression on my system. > wlan0 doesn't seem to come up. > > I have the following output on my log: > > | Sep 8 19:09:43 misaka wpa_supplicant[23325]: ioctl[SIOCS80211, op=3D103,= > val=3D0, arg_len=3D128]: Operation now in progress > | Sep 8 19:09:43 misaka wpa_supplicant[23325]: wlan0: CTRL-EVENT-SCAN-FAIL= > ED ret=3D-1 retry=3D1 > > Here is a sanitized version of my wpa_supplicant.conf: > > ctrl_interface=3D/var/run/wpa_supplicant > eapol_version=3D1 > ap_scan=3D1 > fast_reauth=3D1 > country=3DBR > network=3D{ > ssid=3D"********" > psk=3D"****************" > priority=3D5 > } > [...] > > and rc.conf related settings: > > [...] > ifconfig_wlan0=3D"WPA powersave 10.0.0.110 netmask 0xffffff00 broadcast 10.= > 0.0.255" > defaultrouter=3D"10.0.0.1" > > wlans_iwm0=3D"wlan0" > create_args_wlan0=3D"country BR regdomain FCC" > [...] > > The last fix still works, although `sleep' isn't necessary. > > @@ -29,6 +29,7 @@ > } > =20 > wpa_poststart() { > + ifconfig ${ifn} down > ifconfig ${ifn} up > } > d06d7eb09131 has taken care of this. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. From nobody Thu Sep 9 09:31:03 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 21CEA17BABD1 for ; Thu, 9 Sep 2021 09:31:06 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4tzZ0HMPz3PKV for ; Thu, 9 Sep 2021 09:31:06 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id DD42223DAB for ; Thu, 9 Sep 2021 09:31:05 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-148-130-214.range86-148.btcentralplus.com [86.148.130.214]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 340D62C973 for ; Thu, 9 Sep 2021 10:31:05 +0100 (BST) Subject: Re: -CURRENT compilation time To: freebsd-current@freebsd.org References: <2cfb912a-618b-9f06-9cef-d2fe1d78fe97@FreeBSD.org> <20210908105236.1abb8f9a@ernst.home> <746cf2d1-0192-a55d-c3f8-ac7fc7120b47@FreeBSD.org> <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> From: David Chisnall Message-ID: <4b5b1ae0-9fa3-ad80-9bd0-9802270e104b@FreeBSD.org> Date: Thu, 9 Sep 2021 10:31:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210909080446.d223e9e16b90b5600f962757@dec.sakura.ne.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 09/09/2021 00:04, Tomoaki AOKI wrote: > devel/ninja/Makefile has USES= python in it, so it maybe require python > to run or at least build. You could probably remove that line without anyone noticing. Ninja uses Python for precisely one thing (or, at least, did last time I looked): There is a debugging mode that will generate a visualisation of all of the dependencies in the project and run a web server that allows you to view this visualisation in your web browser. In about 10 years of using Ninja, I have used this functionality precisely once, and that was immediately after poking the code to find out why it had a Python dependency, discovering this mode existed, and looking to see what it did. Nothing on the build paths depends on Python and Ninja doesn't require Python to build itself. David From nobody Thu Sep 9 13:10:13 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B8D0917C6244 for ; Thu, 9 Sep 2021 13:10:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H4zrS425cz3PM8 for ; Thu, 9 Sep 2021 13:10:16 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ed1-x52e.google.com with SMTP id j13so2559267edv.13 for ; Thu, 09 Sep 2021 06:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:message-id:reply-to:mime-version :content-transfer-encoding; bh=IJ2tr5eVPsnu0eFI9/uqHxbaNty7wY7hyOqfgPF2aBg=; b=VLpsUD/kXrGVT8B01QQ+Y1SVAoE4DErlO8mmim4oU/YwrnWTEZHAe0e2O8mic9uK5b 9BY8QVpWH0byhh993rUIqhNDfyQ660uYKy9UdWAYdsWqY2cmg48zHRbZ1hOrWCPOcxxO xE7dmaIVDL0USeKacc0rFbVcWrIhhg2H1mwZ4NxYbJQ2d4XhIC96E0UNKE2ZsLfVV/Ui SLzxjgQv+wzkuA2RgFxBqHy7ZYyp64qDXfYUiILxuTTiOESwBgRako9D3PErV22Pos5o Tdkeho5mnywcM6ixbrslJNGj0SOyuzlW+t5fLxyBW1Dia97T2FLqKIQ5zLbo1CfOhYzE a+ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=IJ2tr5eVPsnu0eFI9/uqHxbaNty7wY7hyOqfgPF2aBg=; b=wxl/hPv76TJ5L6mpiHdC3cFUE2nqzpRhxpF7MxPT71nSTBz/B2CpYhBqKny0mcakJI T8GgePYl0DU9cmX/XI6/tCwqNE6U+tt0GKSncFhmgVnKmpAQ9OTcUghBhirY0Bu2EFg0 hCXQW1VJu0V2lztqNQzTLFt8if5x/Aowpq2StwpXkMyO7lCfkyjdaLOI1CZpQft20HAW bM1lA8ajjTRzfdwTgG+X+jk/SEoVGtCXe9zEVHM3WsJV8KMpG7hOsUx2Nac1q4wlhSo8 SISFUVUZINafFcLW6Po+n2IOhsQtS4ddFWvJ9CU2QGJj667JZSjaZ7NoPi+Gk3ScVXXh tAEw== X-Gm-Message-State: AOAM532ToYcUmSoo6DRhT3AEGr/1QruGtqFJNDfHMxu0F4RNzxhL2WBU eMw4OVI0k0yL/QpvBBmieKvgrGPl5wA= X-Google-Smtp-Source: ABdhPJwRMqjwN1ZYV9Ljg0P3KIv0FOlPgOk/zsSkQZCn9RCaCbKpDj0r5FYfz/6TnnMU820LaXchyg== X-Received: by 2002:aa7:c313:: with SMTP id l19mr3114353edq.131.1631193015689; Thu, 09 Sep 2021 06:10:15 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id x11sm1037487edq.58.2021.09.09.06.10.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Sep 2021 06:10:14 -0700 (PDT) Date: Thu, 9 Sep 2021 15:10:13 +0200 From: Gary Jennejohn To: current@freebsd.org Subject: error installing stand/i386/loader_4th in HEAD Message-ID: <20210909131013.3196ad52@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H4zrS425cz3PM8 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b="VLpsUD/k"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::52e as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-3.01 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; REPLYTO_ADDR_EQ_FROM(0.00)[]; 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]; NEURAL_HAM_SHORT(-0.47)[-0.471]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.23:received]; 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]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.54)[-0.538]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52e:from]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I got a very strange error while trying to make installworld on HEAD: stand/i386/loader_4th (install) /tmp/install.rIhHqnPC/sh: cc not found *** Error code 127 This from a tree which I updated at 08:37 UTC. According to uname -a the tree is at commit main-n249276-fc29a8b9d95. I booted the new kernel from this tree. I've never seen this error before. Why in the world would install need cc? Note that I copied the contents of /usr/src/etc/mtree to /etc/mtree before starting the installation. -- Gary Jennejohn From nobody Thu Sep 9 14:00:39 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 23D9217B6BB3 for ; Thu, 9 Sep 2021 14:00:42 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H50yf0Vbxz3vy1; Thu, 9 Sep 2021 14:00:42 +0000 (UTC) (envelope-from se@freebsd.org) Received: from [IPV6:2003:cd:5f15:5000:3d57:6c49:27f6:fd8d] (p200300cd5f1550003d576c4927f6fd8d.dip0.t-ipconnect.de [IPv6:2003:cd:5f15:5000:3d57:6c49:27f6:fd8d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 99FD5267AC; Thu, 9 Sep 2021 14:00:41 +0000 (UTC) (envelope-from se@freebsd.org) Message-ID: Date: Thu, 9 Sep 2021 16:00:39 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 Content-Language: en-US From: Stefan Esser To: FreeBSD CURRENT Subject: fetch -v error output broken? Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------b2WyyyqEiTC752530x8KGCyi" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------b2WyyyqEiTC752530x8KGCyi Content-Type: multipart/mixed; boundary="------------QK0Odmm9ZXU3HqtVuNf8hwND"; protected-headers="v1" From: Stefan Esser To: FreeBSD CURRENT Message-ID: Subject: fetch -v error output broken? --------------QK0Odmm9ZXU3HqtVuNf8hwND Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have just opened PR 258387 for this issue, which occurred during testin= g of a port with invalid MASTER_SITE. The error output of "fetch -v" should be server messages, but it appears = that the buffer gets overwritten with data of unknown origin (mostly NUL bytes= ), e.g.: $ fetch -v http://distcache.us-west.freebsd.org/x 2>&1 | hd 00000000 72 65 73 6f 6c 76 69 6e 67 20 73 65 72 76 65 72 |resolving se= rver| 00000010 20 61 64 64 72 65 73 73 3a 20 64 69 73 74 63 61 | address: di= stca| 00000020 63 68 65 2e 75 73 2d 77 65 73 74 2e 66 72 65 65 |che.us-west.= free| 00000030 62 73 64 2e 6f 72 67 3a 38 30 0a 72 65 71 75 65 |bsd.org:80.r= eque| 00000040 73 74 69 6e 67 20 68 74 74 70 3a 2f 2f 64 69 73 |sting http:/= /dis| 00000050 74 63 61 63 68 65 2e 75 73 2d 77 65 73 74 2e 66 |tcache.us-we= st.f| 00000060 72 65 65 62 73 64 2e 6f 72 67 2f 78 0a 0d 0a 00 |reebsd.org/x= =2E...| 00000070 67 69 6e 78 00 00 00 0a 34 30 34 20 4e 6f 74 20 |ginx....404 = Not | 00000080 46 6f 75 6e 64 0d 0a 00 00 00 00 00 10 02 00 50 |Found.......= =2E..P| 00000090 95 14 01 c9 00 00 00 00 00 00 00 00 0a 0d 0a 00 |............= =2E...| 000000a0 74 6c 65 3e 34 30 34 20 4e 6f 74 20 46 6f 75 6e |tle>404 Not = Foun| 000000b0 64 0d 0a 00 00 00 00 00 10 02 00 50 95 14 01 c9 |d..........P= =2E...| 000000c0 00 00 00 00 00 00 00 00 0a 34 30 34 20 4e 6f 74 |.........404= Not| 000000d0 20 46 6f 75 6e 64 0d 0a 00 0a 00 00 00 00 00 10 | Found......= =2E...| 000000e0 02 00 50 95 14 01 c9 00 00 00 00 00 00 00 00 0a |..P.........= =2E...| 000000f0 6e 67 69 6e 78 0d 0a 00 3e 0d 0a 00 0a 00 00 00 |nginx...>...= =2E...| 00000100 00 00 10 02 00 50 95 14 01 c9 00 00 00 00 00 00 |.....P......= =2E...| 00000110 00 00 0a 0d 0a 00 72 3e 6e 67 69 6e 78 0d 0a 00 |......r>ngin= x...| 00000120 3e 0d 0a 00 0a 00 00 00 00 00 10 02 00 50 95 14 |>...........= =2EP..| 00000130 01 c9 00 00 00 00 00 00 00 00 0a 0d 0a 00 72 3e |............= =2E.r>| 00000140 6e 67 69 6e 78 0d 0a 00 3e 0d 0a 00 0a 00 00 00 |nginx...>...= =2E...| 00000150 00 00 10 02 00 50 95 14 01 c9 00 00 00 00 00 00 |.....P......= =2E...| 00000160 00 00 0a 66 65 74 63 68 3a 20 68 74 74 70 3a 2f |...fetch: ht= tp:/| 00000170 2f 64 69 73 74 63 61 63 68 65 2e 75 73 2d 77 65 |/distcache.u= s-we| 00000180 73 74 2e 66 72 65 65 62 73 64 2e 6f 72 67 2f 78 |st.freebsd.o= rg/x| 00000190 3a 20 4e 6f 74 20 46 6f 75 6e 64 0a |: Not Found.= | 0000019c The expected output is returned by wget, e.g.: $ wget -d http://distcache.us-west.freebsd.org/x [...] 404 Not Found Registered socket 3 for persistent reuse. Skipping 146 bytes of body: [ 404 Not Found

404 Not Found

nginx
] done. 2021-09-09 15:37:02 ERROR 404: Not Found. Part of the HTML response can be found in the fetch output, too: "r>nginx" is obviously a fragment of "
nginx
", but "r>ngi= nx" appears twice, 40 bytes apart. "tle>404 Not Found" is a fragment of "404 Not Found", with= "404 Not Found" appearing a total of 3 times ... This could be a result of recent changes to the memcpy function, which us= ed to allow overlapping buffers, but does not anymore on -CURRENT. But the 4 occurences of memcpy() in libfetch/http.c and libfetch/common.c= seem to be sane, and I did not look any further for the source of the data cor= ruption. --------------QK0Odmm9ZXU3HqtVuNf8hwND-- --------------b2WyyyqEiTC752530x8KGCyi Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmE6E4cFAwAAAAAACgkQR+u171r99URX Wgf/aLxaqQxKaP6/UukWgoUNpRe7h2R9CNEeKDxz8woeh2IlmTBsIEOmOPl91h1TbJq8Yq2WRcLL 9Umf5T4i6CV7czP55JfDoa0O7GvxqiUXzjchEry55CyW7OEnIxYYQ5+zHJ+mFX0WwB/XJA3OWUSk PZfomPKCfzdikPD5zzP7ESPq+ijn2OTYtPV3taHvildx+qkFbpD0c/y/RPxj3VwhxCFJWCCW3/81 AHuDjbsFPsYdpdTw49yxY0WUDEvogZ+jwAL4f1B7MfGPQMmk9H73cxjxc9nZzjrp8oQQeE4qZlUk 08/osc7fAJIslvUWtw1qUZkfVnPUGnJh/yQisyr5ag== =7loH -----END PGP SIGNATURE----- --------------b2WyyyqEiTC752530x8KGCyi-- From nobody Thu Sep 9 14:52:33 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A434817A95AC for ; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H526X4NNRz4lCY; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from aniel.nours.eu (nours.eu [IPv6:2001:41d0:8:3a4d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 6325726AB4; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id D9D2AB3F31; Thu, 9 Sep 2021 16:52:33 +0200 (CEST) Date: Thu, 9 Sep 2021 16:52:33 +0200 From: Baptiste Daroussin To: Stefan Esser Cc: FreeBSD CURRENT Subject: Re: fetch -v error output broken? Message-ID: <20210909145233.bx5yp3ghj2qaadbb@aniel.nours.eu> References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Thu, Sep 09, 2021 at 04:00:39PM +0200, Stefan Esser wrote: > I have just opened PR 258387 for this issue, which occurred during testing > of a port with invalid MASTER_SITE. > > The error output of "fetch -v" should be server messages, but it appears that > the buffer gets overwritten with data of unknown origin (mostly NUL bytes), e.g.: > I figured the same this morning and fixed it in: 635eb7ac799 Best regards, Bapt From nobody Thu Sep 9 15:07:08 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6480F17B2F3C for ; Thu, 9 Sep 2021 15:07:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H52RZ22RPz4sH7 for ; Thu, 9 Sep 2021 15:07:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-lj1-x236.google.com with SMTP id r3so3496691ljc.4 for ; Thu, 09 Sep 2021 08:07:22 -0700 (PDT) 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=LEX77bKHlqO9i5FmxvwUBEf6hYht2m3tB+U6KeMUVUI=; b=rGH5sQW4jeSaCD97F5mXyfiKo1gGWdD9pVYLkZTyl/CQAa18+0b5MYyNeC+uub9qAI RdxhvXeczKxDPkEcvdNx/xgQ1I5FEhNcQuZifU7VeXQ80hpHkt4CkuUb30oEJNmv/2Mj 3FfsG3nuZ/fFrh98e354UOJ6ewYIqFlSpkM1SzK3vSJIH2DB5YAnR0i/ai+pz8xv4bQs ToGL5zOVG07LFhmejva7nCsOpSSLzOoA3MyZPPHh4eaKc4IUfl10tz47zYq8ljqLlf+S 1p1dvfXJieL8xWL6AOW4FZb1hr+i5qJuU0K2qaobYJfMngrZqA+wA2Ecae2yU8jFlIKN Ub6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LEX77bKHlqO9i5FmxvwUBEf6hYht2m3tB+U6KeMUVUI=; b=mpvOoB4dOqgn8cegy14fORJ56WEoGMp3NBPNNCqCKnOoFJbWCahVEWf00Ya0TGNwfj sJ6WxtjukNJC0t1qoOCWvITTwGmGWodfCIkX4JfzIUnhMXr+8mWkRWmjPNnnkoBldaQE lPpp6HNMxmZVpjOoNcHoipMhJSFP8VQw0KJPA13SE3ZlJAcB1BRdf5Q2n0oTep/6lkjq o2oD4cwY9Gd0W0W4YfF5V9hnDI5/vxd7ma9pjzLMrRWicRfQ7YHNX32FRwOa8b6bbH6a vXiT7i9PWe6lUF45LvKQXnHbWRivoXG9R88pE4NjqXMELds4HVdGwiEqM+4ya2MUOeBw JZMw== X-Gm-Message-State: AOAM533+nmd3Y3bawqrJJo1qgsla+hS0oJOtwnPQpeupEDcMOYBPknPw mMswMa8oKuSUxP4lf655RYRA/SQUriavW20g4CBabRQ42S0= X-Google-Smtp-Source: ABdhPJyQfK2agtsKULRdRMh8rDiREjDk7PPNA8BclJsFY9dHY/Nit2EKlvGpHAWuzrkmSxxwWi7Utov/eVEr1zLVTWo= X-Received: by 2002:a2e:99da:: with SMTP id l26mr213985ljj.339.1631200040762; Thu, 09 Sep 2021 08:07:20 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210909131013.3196ad52@ernst.home> In-Reply-To: <20210909131013.3196ad52@ernst.home> From: Warner Losh Date: Thu, 9 Sep 2021 09:07:08 -0600 Message-ID: Subject: Re: error installing stand/i386/loader_4th in HEAD To: Gary Jennejohn Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000fcd78105cb915a1f" X-Rspamd-Queue-Id: 4H52RZ22RPz4sH7 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000fcd78105cb915a1f Content-Type: text/plain; charset="UTF-8" On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn wrote: > I got a very strange error while trying to make installworld on HEAD: > > stand/i386/loader_4th (install) > /tmp/install.rIhHqnPC/sh: cc not found > *** Error code 127 > > This from a tree which I updated at 08:37 UTC. According to uname -a > the tree is at commit main-n249276-fc29a8b9d95. > > I booted the new kernel from this tree. > > I've never seen this error before. Why in the world would install need > cc? > The usual cause of this error is time skew. There were some build issues that I've fixed that I was sure I merged to stable/13, but I'll check when I get home. Note that I copied the contents of /usr/src/etc/mtree to /etc/mtree before > starting the installation. > I don't think that matters Warner -- > Gary Jennejohn > > --000000000000fcd78105cb915a1f-- From nobody Thu Sep 9 16:03:12 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 658B917AE298 for ; Thu, 9 Sep 2021 16:03:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H53h524sTz3gyH for ; Thu, 9 Sep 2021 16:03:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ej1-x630.google.com with SMTP id n27so4633373eja.5 for ; Thu, 09 Sep 2021 09:03:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=TRa8ivVbn2oEmL+s5V9HwphUBlh2njKtD45cWc5jec4=; b=WI4J0hLIumfGxcKqvWuW7hjSg8aGpUqw4LYWa6XQRZgPTl4JFGb33Dcc94zyQD5EHf WGE/lmAcDp7gGDXUKQvXW0iOJawI4eUWlsx8Bh//l3LSHtk+8q9zLcAW3erXjFCuOQwU +PpkAPButQFsj5cQWoRhsnd56Qscb9s8bS7BqmkNhGfc4MK2jP7vBx2+xQ07IsKjw+rn be2QYyHGXsH51BPpt+MLnuJ083jh9F9mrQYpDx17D2pFzEbO9Tjgrf2mO0jA0wf84U0B C0Jx7/FdJozVr0kQVr108Jedcdwi+YTDVuqdOp3JyyVgnRG39ySC5ImgGeArwZlIfSX7 S0gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=TRa8ivVbn2oEmL+s5V9HwphUBlh2njKtD45cWc5jec4=; b=UdZzV1rfC1O5h2FdEOCVelSekdnITDlQycZy4/Ud0qlFJ1yD4CWLcWbSPVVu5GnpA1 xmkzfKm9sokbo7l0iDc/mfHlHJQ3cUakB+4lRIUdRuplZJK6qqDCoGK1Q7QoO0fDTsnT W0AzJ3V/b00N48VtutLHUNytyLrfRuSSSbK8tlu7D3i2OhOtTeybCw8WkLpk5TPm4azW mpJd9Nb+FuL6Wis5md4REBtqUnpKHXQ/6c4O/tIDq0iNECgKYQlvuSdS76WhrufMmwox t2XVHLibWHUdFm4RUmxcZaxjSb+3x8Axw9cVedTjaekKi/2vpTWLQVLuFc41XD62iSUw syyA== X-Gm-Message-State: AOAM533N13/0Pc4umbvArm0JzHo2Q6CSRQTB3Iepkhzv7evC+ELAdvz+ jvh6jrIEdpREli649MPpclw= X-Google-Smtp-Source: ABdhPJzvhc2yIl2b3SxirtbjizTpW9e4oE65R84rUDZzGxff+EdcqD29y8DUvlTQrj9GrY85saXdLw== X-Received: by 2002:a17:906:9b87:: with SMTP id dd7mr4342803ejc.99.1631203396210; Thu, 09 Sep 2021 09:03:16 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id t5sm1259063edd.66.2021.09.09.09.03.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Sep 2021 09:03:15 -0700 (PDT) Date: Thu, 9 Sep 2021 18:03:12 +0200 From: Gary Jennejohn To: Warner Losh Cc: FreeBSD Current Subject: Re: error installing stand/i386/loader_4th in HEAD Message-ID: <20210909160312.6f0df4a5@ernst.home> In-Reply-To: References: <20210909131013.3196ad52@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H53h524sTz3gyH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 9 Sep 2021 09:07:08 -0600 Warner Losh wrote: > On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn wrote: > > > I got a very strange error while trying to make installworld on HEAD: > > > > stand/i386/loader_4th (install) > > /tmp/install.rIhHqnPC/sh: cc not found > > *** Error code 127 > > > > This from a tree which I updated at 08:37 UTC. According to uname -a > > the tree is at commit main-n249276-fc29a8b9d95. > > > > I booted the new kernel from this tree. > > > > I've never seen this error before. Why in the world would install need > > cc? > > > > The usual cause of this error is time skew. There were some build issues > that I've fixed that I was sure I merged to stable/13, but I'll check > when I get home. > Thanks. I'll check the times set under /usr/src and /usr/obj. -- Gary Jennejohn From nobody Thu Sep 9 16:37:30 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7CBAD17BFD00 for ; Thu, 9 Sep 2021 16:37:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H54Rz2jN9z3t9f for ; Thu, 9 Sep 2021 16:37:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-lf1-x135.google.com with SMTP id l10so4910974lfg.4 for ; Thu, 09 Sep 2021 09:37:51 -0700 (PDT) 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=E2N3aPqXn+bXq5S1UypgMECEb/uCFeC9qpbfW7OlMDc=; b=wCIzkK5QEffEqqewZTLBFA8/DigW04BcFp8Vq2N05oltyiMS204eM0QqswP1Taj/0p Y+0mZgEU9jLyiuwjSMSaTqVkn3ZgKkc1RfDfIXcylYJLkc/ZxGs6OVZJvB9hx3vyCcAC m2BcpoDsTjZL+R6G5g4YXCd5u3Fg9tojRCC/dpwU8KZF2a/bALoUn5B7/JRFFnP7MPzB B2PL/Y3LUiXnjBqoZ0nmi/KeGlcukGBs3p4nPjlQ6DBp+QsMvsmHMSoy6v2ZAmLM1dfx sNskkly54NKp8JY07Oj3YKVconW/2tSOKhdkLRut6VwSMJagLtXU89p3vFZ53IIG4Baq 43mA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E2N3aPqXn+bXq5S1UypgMECEb/uCFeC9qpbfW7OlMDc=; b=mi8IvTaJ76suCDn6xMu1IiezQWqt3HDqYiawQ7cWOO91ms5A/ww2wmXKd3+i2cn3r/ sSNQCFtpXhrm2pMRy3rppsjxriadB23UFEdn28EWssGugySTwV7bDAJyfcmXR4QXRLxp ZbIdyCk3QpMJd1s566o/KaqRwsM5DYzjAne1pk6j+BTIB9JdiO66HUsMwdxGoiPDwpfv z5Ds1Qj5FlSWMu9WZgRVJ37lGb9OhaeF+Dn2vnr6p4VnTWKWRRz0DDxVHoCF21T+7BnU kFW78wNzh+tux0kyG3MZ/Q652KI6dWCkC/o5YEClhL+YJaZhx4flcuRg5zba3FVa0T15 63HQ== X-Gm-Message-State: AOAM532mrnWexqlLQhWYtBuzt/4+rRwV+nXnIExVVR08fcfLVMxfAnjT YHIKC3tsdwxxPRYXOdUgu2IqAfr0YIcbXUOcp2qAtc42DKg= X-Google-Smtp-Source: ABdhPJyrj/fsv7P8t/vfsnBybKF9cHwK0UKPGfPEtMNr0oKRE5Bh09K7rQacTPVRySquI60/oQhx7DMn1VofGTVMTGk= X-Received: by 2002:a05:6512:687:: with SMTP id t7mr522144lfe.399.1631205463823; Thu, 09 Sep 2021 09:37:43 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210909131013.3196ad52@ernst.home> <20210909160312.6f0df4a5@ernst.home> In-Reply-To: <20210909160312.6f0df4a5@ernst.home> From: Warner Losh Date: Thu, 9 Sep 2021 10:37:30 -0600 Message-ID: Subject: Re: error installing stand/i386/loader_4th in HEAD To: Gary Jennejohn Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000003a3aae05cb929e0d" X-Rspamd-Queue-Id: 4H54Rz2jN9z3t9f X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000003a3aae05cb929e0d Content-Type: text/plain; charset="UTF-8" On Thu, Sep 9, 2021, 10:03 AM Gary Jennejohn wrote: > On Thu, 9 Sep 2021 09:07:08 -0600 > Warner Losh wrote: > > > On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn > wrote: > > > > > I got a very strange error while trying to make installworld on HEAD: > > > > > > stand/i386/loader_4th (install) > > > /tmp/install.rIhHqnPC/sh: cc not found > > > *** Error code 127 > > > > > > This from a tree which I updated at 08:37 UTC. According to uname -a > > > the tree is at commit main-n249276-fc29a8b9d95. > > > > > > I booted the new kernel from this tree. > > > > > > I've never seen this error before. Why in the world would install need > > > cc? > > > > > > > The usual cause of this error is time skew. There were some build issues > > that I've fixed that I was sure I merged to stable/13, but I'll check > > when I get home. > > > > Thanks. I'll check the times set under /usr/src and /usr/obj. > If you have a reliable way to reproduce this, I'd be quite interested if it isn't a typical "oops" on dates Warner -- > Gary Jennejohn > --0000000000003a3aae05cb929e0d-- From nobody Thu Sep 9 16:55:56 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id ECDD417C74F0 for ; Thu, 9 Sep 2021 16:56:32 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp1.goneo.de (smtp1.goneo.de [85.220.129.30]) (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 4H54sW6c9Sz4TVV; Thu, 9 Sep 2021 16:56:31 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-054-046-104.78.54.pool.telefonica.de [78.54.46.104]) by smtp1.goneo.de (Postfix) with ESMTPSA id 1DFC8203E69F; Thu, 9 Sep 2021 18:56:24 +0200 (CEST) Date: Thu, 9 Sep 2021 18:55:56 +0200 From: FreeBSD User To: Ed Maste Cc: FreeBSD CURRENT Subject: Re: ar: warning: can't open file: ccopy.pieo: No such file or directory Message-ID: <20210909185623.199c4042@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20210811113956.64df7c5a@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H54sW6c9Sz4TVV X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.30) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [-0.06 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[85.220.129.30:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.86)[-0.862]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[walstatt-de.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; HAS_ORG_HEADER(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[78.54.46.104:received]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N Am Wed, 11 Aug 2021 15:03:54 -0400 Ed Maste schrieb: > On Wed, 11 Aug 2021 at 05:41, FreeBSD User wrote: > > > > Hallo, > > > > latest upgrade of CURRENT sources renders buildworld into failure, box is running > > FreeBSD 14.0-CURRENT #1 main-n248614-67f508db84b: Wed Aug 11 07:29:11 CEST 2021 amd64: > > Assuming this was with BEARSSL enabled, it should be fixed with: > > commit 879675e9a0d84880cad9834e2ef98e8724c5532c > Author: Warner Losh > Date: Wed Aug 11 10:59:28 2021 -0600 > > stand: Add MK_PIE=no to defs.mk > > There's no need to build both pie and non-pie .o's for stand. There's > some other build thing with MK_BEAR_SSL=yes and/or MK_LOADER_VERIEXEC=yes > that causes the pie build to fail that the 'ar' stage now. Since we don't > need the PIE stuff and the non-PIE stuff, disable PIE for the boot loader. > > Reviewed by: emaste > Sponsored by: Netflix > Hello again, I think I face the very same problem on 14-CURRENT boxes building either 13-STABLE sources or 13-STABLE poudriere jails, when on the 14-CURRENT box WITH_BEARSSL is enabled in the 14-CURRENT host's /etc/src.conf. I have two scenarios: Building 13-STABLE for FreeBSD-pkg-base (having WITH_BEARSSL enabled in the src.conf dor the 13-STABLE source tree) and Building poudriere jail from a dedicated source tree for 13-STABLE (/pool/sources/13-STABLE/src) with WITH_BEARSSL enabled. The latter scenario sounds ridiculous to have BEARSSL enabled, but we use the very same src.conf file for both the packages for FreeBSD pkg base and so for the poudriere jail built from the same source tree. For a couple of weeks now I'm unable to build both the packages nor the jails. The question would be: is the solution you offered above and fixed the problem I had initailly also applicable to 13-STABLE without breakage of something else? Tahnk you very much in advance, O. Hartmann -- O. Hartmann From nobody Thu Sep 9 18:01:05 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6BAD517BD660 for ; Thu, 9 Sep 2021 18:01:47 +0000 (UTC) (envelope-from bcantrall@ameritech.net) Received: from sonic313-23.consmr.mail.gq1.yahoo.com (sonic313-23.consmr.mail.gq1.yahoo.com [98.137.65.86]) (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 4H56Jn4lsgz4pN3 for ; Thu, 9 Sep 2021 18:01:45 +0000 (UTC) (envelope-from bcantrall@ameritech.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ameritech.net; s=s2048; t=1631210498; bh=XtKZYHBooaCuYOeTG7bMuFkhB11JxJyFg4B46ebfWTI=; h=Date:From:Reply-To:To:Subject:References:From:Subject:Reply-To; b=jUVp2nmWdpfu+n/xLW6Q2WtGUEvPXdo9w5yUBjt7EMZtXQb0Ro1QyT1AAs0ol7iFw5OhL7SveCzHtzLnw2l2LHu7M0T1sikVz5zmbyxDldmpBKlMCy3NkVOhzNActI3BIbaRRFY8lmpUekENiCYzsHqOfPY5QeUzfSk9iDLtP4L9sqaK1AKVepCHOg2DmwSIRk2VJCCQuqEXIyYj/MHliJ8oWx0s5BuGzE94HtgqtfhWmAIzXkKflS9U5b3gOClVJWR/jT9u+T49ZTdDpfV9dScvfWjPi1VEkNiC7fDOJ63jAbzhJ0nM9ItLHSDUQDy3uBJKh03WZk0s+M47dFTq2Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1631210498; bh=jG0/a1eyDfmhi50gUlRkoVI7LrShIdR8MI9Lls0+6gJ=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=sFoy+6SxMDGDR2K8ttyJNvnpS/aCJmFe/Mz3embAv8VzkQBoIYzej+loobMkYOUFk/l9C6N0cKS76Q7JzPZfPn/tCqrZP/HAVGNsXlXF60f+GKFyBH3TR5B939NpzJ7GQKmMl1Vab+HZySB/WWuozsFRxJv7IJygdxFlvNv91NJoebyCByvt0pjaYGhkQJL0RH/o6f4PEK0qroohhe0mRezIxGQ0NJNtxqZLVi8/r5kUG7xrFHmzh25obdQplc0cT0x3qybqIU5tcUusMhv+CQzc8c3mjbbsb72qjL7DRKwayYXaTYg6tZ6ADxkYU/jp66IUh2/KViwSonv029NNrA== X-YMail-OSG: 34pTpZwVM1kM7zADH7BrSHE6LWnwrkb0A4cw_6iv_OnbTQbsu6MffJ1vDZlk6vc F7P_CToVhiGm_paB_63cz1JDwjctTcmmxceeMPFvp69yVvUTkfnCpL3OZEVRXZKyFaEhfLUsd5hB mLEO_Oe6yQugY3bul6P9H9ecvGRwjjPEPtn37FGKkKe2f9GnJ11m7h4NVfV6f2bImcvXTHRrQ5gN yvE0Wg5HLGRS2LJvEIB1bEwxgv5LPYUGQkjYzE0nhx8k1k85RCYLP1wjhVf6Q4ZRco19zDmRqeww J65Cy.nkmbi1JEzm.K3K65mfUllnT8kdcLmfG7mZKQ3M7qonsij7YJ.DIYL.zgIdTazsKOvFAB35 8UaCHk5_ZGGaurSjh7O0olqM2I_UT2tnFQmDSNZwS3QpJTuVuJI9s.LNuPdE4JLcYpOP4C3U1hAs 8PGKlyYnj_rLE0UJRG9d.5XhcIJFqU0TQnrQF9fCwFevTVbSYyA4O0913fek4xDut13gt240iCM2 BQZKRmiUdfSGWb8NSWdwd.dm9fySNs.MvnVckrXbNrkkbcbbJ3RU4UEYvhIEoolLJQigawjjji9i AiCyura1dCOj7BI6bGmFndu_denmtWQvs.hpgx7AvDuHWhBJLarOTIr1rpDRruTmi6VZ0aUbirEQ 0mcvvY8xKXkfXLJidTkh730J0qIeq9Sffug79jrZj6cFDF_5Tzvpg.pN4FWF6IBLqbtoc58JWKPG MEkji98ao0gOWLBAncDmTEQu2y0rAm4maeaW352gh9nrqLEA7aJ25N_g7atHf9vlIPUK.gY5p4es W8qcq05huNXZ9wCmLxP3LJVYNL3QQucoK1bD4lzN9TqyFU0krKE8xZd9R4FCsxZqFFv0zAdGP0Wr GCwslpKoPqNXj_Zv177rzTOQpD6wQnaB3_FpGVyU.4WPGgx1w_lrrQIC5AQrA4FRj.R0LjYHH3ZA 0Bf.S9EXUqNLAgYCOpVNm9RUC1sEDN.ixoOVMcZgOXKgxrjGSg3VCrWMU0wfClTqeA75IV26xtBM PhKX3GHUftlpQYIUv0T3HAY3wJteu2_q_ze7uZfG90iQyl2QX_rXYNa0vauT0yVarYla2WB1Fco. rDEW_Lf35iszknNpSYJ3o4pVfOfA3RFXkF1Ir1_LDGs8PDLAwV1rK81zpqm3n4CkBeKPthspYE2B CYd9sIpsrYmmx.PJ5CMySeq7wLlm_dYyGUJrI2TOcOLhQJmvxly_hQtbF1ulayRlygHFYrCm0Rzu OyTcV1hD.QSBl7YhhuMPAn_XRh1PsRkkEo_OIFw.WKkBFSBqa_na98QfC8eE_4xakwC19BvB.Zsy yo3ErK_WQ3LH2.SUPOuTuh1_2i7NPoE8_Uo_hwSDwdzttVRgyxW8ergN4hjtLsiTMNMerkpuZFY0 mvRrfPtmCJKA5EzMJoSmHwULdp9xoI8NEZBBcUl.SxbfsaQ3xajYg3hWa.z7.Y5gd6k2141rhFbe 1MzsBwApIKEhyWN_GZiKjc1vE3QZ9T7Xt4HOn582BytaRgW1Wh7m8yR0qCB4qdnMyFhNLdh84LlJ MRjMpiWkLXYLSfKHMsXDEi5kl.YjmKV.Ds8uIfBLxWA3tQY.vSX0yX3jgh9iqhgSXnNNsFkBFRn_ jp9Uy2gB0sle6O3hkpQzkBiGEV6kcvnkEP_7.Py_oc2vUinYNCxp.1OCzEGuBJeMW1ZzEiOJKMk9 En8mCDVXR3G99l90_Hjt5fvtSswZ8bAbgAAD2_rPCUYwXHfBbAdUpvEdp9yk8v.2iaGYHl4g84aM mZK8C.IVWmcFL.nvBzx8bo5VU5TYnsYQAbrHBRIeIbg6YDJpTYLOe.IaI2K11ZHXcbB9kQ_E_5av 49CX6KN3M4jBpGfAcbxLFcKaNihpmHpgqatQUZv7GXOsmAW6p.HRS5l2yBM93Y2sY4UsWVt91E8i omuDk8quUgWoman3ONOH83rQURW0Bc_7C7ErUVthVtWNDLLGLFlpCTFGHGaaSOiZvBK9bq3in3W7 PGsaNoxPL1v1DZnAF4aWSZNyxkZ4mUrGyUCYwlyGTY52jWjn5YzIRkmuRoETp_tvgIFH2gm4DgaS 4dXcx6oD3LmuDCDCR4XcgZahmUO7qBYldv26.gmEUD8U4WauoGoa1SdDOYQML88QNzFj6dvchMy5 a3bMEsMF_XvZrWsAfDo41qPrpvplnLoeLCxfk4E9YaM4VK0pMGLkdsb3KgRt613.pM9ydZPo4pQX rKtgxYaOpFuNvVgKYUV1RfGCSZP0RkbLdoJH82iypsdW0Cd0vDPr66wMSdVGSEWKFGeWp.wJ.CiI FnCQCTlPwfYHj8o0g2o78Kb2RF4jEuKjz63Hp9x3xB1Vllb6pNhXwCnvCSTv5h1KxKh2AzUdG1T_ 7ag-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Thu, 9 Sep 2021 18:01:38 +0000 Date: Thu, 9 Sep 2021 18:01:05 +0000 (UTC) From: Bruce Cantrall Reply-To: Bruce Cantrall To: "freebsd-current@freebsd.org" Message-ID: <883334800.502175.1631210465576@mail.yahoo.com> Subject: FreeBSD Port: www/php74-opcache had to be disabled after "service apache24 reload" core dumped List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_502174_1958451137.1631210465572" References: <883334800.502175.1631210465576.ref@mail.yahoo.com> X-Mailer: WebService/1.1.18924 YMailNorrin X-Rspamd-Queue-Id: 4H56Jn4lsgz4pN3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ameritech.net header.s=s2048 header.b=jUVp2nmW; dmarc=none; spf=none (mx1.freebsd.org: domain of bcantrall@ameritech.net has no SPF policy when checking 98.137.65.86) smtp.mailfrom=bcantrall@ameritech.net X-Spamd-Result: default: False [-0.79 / 15.00]; HAS_REPLYTO(0.00)[bcantrall@ameritech.net]; FREEMAIL_FROM(0.00)[ameritech.net]; URI_COUNT_ODD(1.00)[1]; DKIM_TRACE(0.00)[ameritech.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[ameritech.net]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[ameritech.net:s=s2048]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.994]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_REPLYTO(0.00)[ameritech.net]; DMARC_NA(0.00)[ameritech.net]; NEURAL_SPAM_MEDIUM(0.50)[0.500]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.86:from]; TO_DN_EQ_ADDR_ALL(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.86:from]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y ------=_Part_502174_1958451137.1631210465572 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Not sure where I should go to suggest a bug fix about a weird apache24 = reload issue.=C2=A0=C2=A0 On FreeBSD 12.2 servers that run apache24, we recently noticed apache24 kep= t crashing when we tried to do a "service apache24 reload".=C2=A0 It would = core dump and the only thing you could do is to restart it, which got it go= ing again, but the next time you tried a reload it would crash again.=C2=A0= (We reload it twice a day in cron after updating Let's Encrypt certificate= s.) We thought there is some issue with shared memory that caused the core dump= s.=C2=A0=C2=A0This happened on multiple servers after an upgrade to a newer= version of=C2=A0php74-opcache.=C2=A0=C2=A0We had to disable opcache as the= workaround. Workaround to allow "service apache24 reload" to work again:=C2=A0vi /usr/l= ocal/etc/php/ext-10-opcache.ini and add following line:opcache.enable=3D0 and then restart apache24 then reload works. Working version of apache24 and php74-opcache: # uname -a && pkg info -x opcache apache24 php74-7.4FreeBSD server1 12.2-RE= LEASE-p7 FreeBSD 12.2-RELEASE-p7 GENERIC=C2=A0 amd64php74-opcache-7.4.22_1a= pache24-2.4.48mod_php74-7.4.22_1php74-7.4.22_1 broken=C2=A0version of apache24 and php74-opcache: $ uname -a && pkg info -x opcache apache24 php74-7.4FreeBSD server3 12.2-RE= LEASE-p7 FreeBSD 12.2-RELEASE-p7 GENERIC=C2=A0 amd64php74-opcache-7.4.23 **= ***************************************************************************= *************************************************apache24-2.4.48mod_php74-7= .4.22_1php74-7.4.23 Debugger info:# gdb /usr/local/sbin/httpd /httpd.core GNU gdb (GDB) 10.2 [GDB v10.2 for FreeBSD] Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd12.2". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: =C2=A0=C2=A0=C2=A0=C2=A0.For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/httpd... (No debugging symbols found in /usr/local/sbin/httpd) [New LWP 100953] Core was generated by `/usr/local/sbin/httpd -DNOHTTPACCEPT'. Program terminated with signal SIGSEGV, Segmentation fault. #0=C2=A0 0x0000000801994080 in ?? () from /usr/local/libexec/apache24/libph= p7.so (gdb) where #0=C2=A0 0x0000000801994080 in ?? () from /usr/local/libexec/apache24/libph= p7.so #1=C2=A0 0x00000008022293ab in ?? () from /usr/local/lib/php/20190902/opcac= he.so #2=C2=A0 0x0000000801c7bef6 in ?? () from /usr/local/libexec/apache24/libph= p7.so #3=C2=A0 0x0000000801c607d2 in zend_llist_apply_with_del () from /usr/local= /libexec/apache24/libphp7.so #4=C2=A0 0x0000000801c7bed7 in ?? () from /usr/local/libexec/apache24/libph= p7.so #5=C2=A0 0x0000000801bf5489 in php_module_startup () from /usr/local/libexe= c/apache24/libphp7.so #6=C2=A0 0x0000000801d07bc5 in ?? () from /usr/local/libexec/apache24/libph= p7.so #7=C2=A0 0x0000000801d07426 in ?? () from /usr/local/libexec/apache24/libph= p7.so #8=C2=A0 0x000000000025c9cf in ap_run_post_config () #9=C2=A0 0x000000000025b7f6 in main () I hope this helps someone else. Thanks,Bruce C ------=_Part_502174_1958451137.1631210465572-- From nobody Thu Sep 9 19:15:03 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7166E17B7D0F for ; Thu, 9 Sep 2021 19:15:33 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp4-2.goneo.de (smtp4-2.goneo.de [85.220.129.61]) (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 4H57xw6D7tz3lBn for ; Thu, 9 Sep 2021 19:15:32 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-054-046-104.78.54.pool.telefonica.de [78.54.46.104]) by smtp4.goneo.de (Postfix) with ESMTPSA id CFB112040D99 for ; Thu, 9 Sep 2021 21:15:30 +0200 (CEST) Date: Thu, 9 Sep 2021 21:15:03 +0200 From: FreeBSD User To: FreeBSD CURRENT Subject: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden Message-ID: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H57xw6D7tz3lBn X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.61) smtp.mailfrom=freebsd@walstatt-de.de X-Spamd-Result: default: False [1.67 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[78.54.46.104:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.77)[0.771]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[walstatt-de.de]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.99)[0.994]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; RCVD_TLS_ALL(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[85.220.129.61:from] X-ThisMailContainsUnwantedMimeParts: N Hello, after upgrading 14-CURRENT to recent sources September, the 8th 2021, we realizes today a strange non-standard behaviour when connecting attempts from several clients to 14-CURRENT based machines were made involving sshd. First discovered on 13-STABLE clients (NanoBSD, router/fw appliance). With non-public-key authentication we copy the config partition tar'ed over to a backup system. This worked great until yesterday. Today the connection is dropped immediately, /var/log/auth.log (sshd log on 14-CURRENT) states: Sep 9 19:19:10 <4.6> thor sshd[1350]: Failed password for user01 from 192.168.11.111 port 24332 ssh2 A usual ssh login attempt also fails this way: Permission denied, please try again. The same behaviour is to observe with Xubuntu 20.04 clients and several other FreeBSD 13.0-RELENG and 13-STABLE clients. Also 14-CURRENT-to-14-CURRENT connection attempts are negative! The only working scheme right now is public key authentication and that is for some scenarios not applicable. What has changed in the recent 14-CURRENT OpenSSH update that dramatically that working schematics do not work any more? By the way, on the target host's sshd, on all instances, settings like these [...] PasswordAuthentication yes ChallengeResponseAuthentication yes UsePAM yes are set explicitely, while "UsePAM" produces an error: /etc/ssh/sshd_config line 89: Unsupported option UsePAM this sound ridiculous, since the usage of that tag is documented in the man page as well as present in the example sshd_config and set yes by default. What is wrong here? How can the sshd issue be fixed? Kind regards and thanks in advance, O. Hartmann -- O. Hartmann From nobody Thu Sep 9 20:12:09 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 259F117B21B4 for ; Thu, 9 Sep 2021 20:10:03 +0000 (UTC) (envelope-from pj@smo.de) Received: from mail.adebahr.de (mail.adebahr.de [185.66.179.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.adebahr.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H598p740nz4Wc9 for ; Thu, 9 Sep 2021 20:10:02 +0000 (UTC) (envelope-from pj@smo.de) Received: from localhost (localhost [127.0.0.1]) by mail.adebahr.de (Postfix) with ESMTP id 08868601DF68B; Thu, 9 Sep 2021 22:09:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smo.de; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject; s=mail; t= 1631218194; x=1633032595; bh=ChoV6QhOYVDzJssZgjw8D+Tx7aU+eLR9c34 ObuJAS/c=; b=Ho3hbUAiWT3q0hGqfPVuj/J1yrfN5dydrjceccBeuLt3oEvEJr4 JUcolDzyTHDmVD8GL9dfYzi8HWfrPVcgUwOmP3xBnVOeCEjewNMWIfgrFuHIAe5h vp9waBK47Kg94kFtnQuaRDHhEbIwPBx/Q8wbD4WJMWm4mH2Ldlar+WlM= Received: from mail.adebahr.de ([127.0.0.1]) by localhost (mail.adebahr.de [127.0.0.1]) (amavisd-new, port 10026) with LMTP id UzQUyEwKfH48; Thu, 9 Sep 2021 22:09:54 +0200 (CEST) Received: from skjaldbreidur.intern.smo.de (pd9515da9.dip0.t-ipconnect.de [217.81.93.169]) by mail.adebahr.de (Postfix) with ESMTPSA id C3928601DD67D; Thu, 9 Sep 2021 22:09:54 +0200 (CEST) Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden To: FreeBSD User , FreeBSD CURRENT References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> From: Philipp Ost Message-ID: <8e25f7ef-3c20-a078-4b47-81b17585df25@smo.de> Date: Thu, 9 Sep 2021 22:12:09 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 In-Reply-To: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H598p740nz4Wc9 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 9/9/21 9:15 PM, FreeBSD User wrote: [...] > What has changed in the recent 14-CURRENT OpenSSH update that dramatically that working > schematics do not work any more? OpenSSH has been updated to v8.7p1: https://cgit.freebsd.org/src/commit/?id=19261079b74319502c6ffa1249920079f0f69a72 One of the more prominent changes is the deprecation of SHA1. There's some additional information here: https://lists.freebsd.org/archives/freebsd-hackers/2021-September/000289.html HTH Philipp From nobody Thu Sep 9 22:27:11 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id CF4C917C79EF for ; Thu, 9 Sep 2021 22:27:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H5DCb70JYz3jW5 for ; Thu, 9 Sep 2021 22:27:39 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 189MRB67076101 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 9 Sep 2021 15:27:12 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 189MRBFh076100; Thu, 9 Sep 2021 15:27:11 -0700 (PDT) (envelope-from sgk) Date: Thu, 9 Sep 2021 15:27:11 -0700 From: Steve Kargl To: Jamie Landeg-Jones Cc: Cy.Schubert@cschubert.com, freebsd-current@freebsd.org Subject: Re: killall, symlinks, and signal delivery? Message-ID: <20210909222711.GA76095@troutmask.apl.washington.edu> References: <20210907224242.GA19450@troutmask.apl.washington.edu> <6C88F561-B045-4D09-B61D-D91096AF0C4B@cschubert.com> <20210908000036.GA24175@troutmask.apl.washington.edu> <202109080110.1881AmGW013959@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202109080110.1881AmGW013959@donotpassgo.dyslexicfish.net> X-Rspamd-Queue-Id: 4H5DCb70JYz3jW5 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N On Wed, Sep 08, 2021 at 02:10:47AM +0100, Jamie Landeg-Jones wrote: > Steve Kargl wrote: > > > Yes, that's likely. So, it could be a change in behavior > > for ImageMagick. Your suggested ps command doesn't provide > > I don't know when the change was made, but the pkg for ImageMagik 6.9.12.12 > has "display" as a stand-alone binary, whilst the pkg for 7.0.11.12 has it > as a softlink. > > So yeah, either an upstream change, or a port change. > Yes, indeed, we have a winner. On my laptop, I have ImageMagick6 and on my desktop ImagMagick7. 'killall display' works as expected on mu laptop and fails on my desktop. Thanks for the insights! -- Steve From nobody Thu Sep 9 23:37:39 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BF48117A9ACD for ; Thu, 9 Sep 2021 23:38:13 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5Fn13zszz4Zfp for ; Thu, 9 Sep 2021 23:38:13 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f49.google.com with SMTP id n24so43216ion.10 for ; Thu, 09 Sep 2021 16:38:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tRhkoKFK+yVG6pb74dbrU/gYJR8G/sSYjmlmdePaw74=; b=bmORMwrwFPZ4ExPTYwmgt/JzDtt51t769hI4T4zvj1Xi3rtJi0DcRE+AyRodlZ5Zxp wB+3zwqHsahp0kgwGDOlcSrOMKYIT3kYT8hT+pswUD+tLktdm2Qw6UdEO//yeUQJsWLp r0+y8QpgMX2UzpHBr0k0XJHbBYvemR/NKNfRQp2txtHmSHxmmFDXw192MHoSrxWH7IAQ sxcIUtT0RIpT8cwNqmea0l6/yDVsSDv2M/hKRBmfGwjqWYH7zzmy/yxk3UMkEezbnaiU Sz0qeq0jz31iEE0UTQ6PALcISHrt/EGP/o+NlOqknGKTOq+V1UNKCDcJ/2oTVDwumCzd 9kzA== X-Gm-Message-State: AOAM531QI1By1/33BmfIdmD+V2tPzQ/wIipezhR0k6KE28Jp+RV2j4J9 kOSWQ1+ci6LytsZtXHR/XdcM+mC+NSteg586ClTVbQG0 X-Google-Smtp-Source: ABdhPJwDqgQ96BoO6c9YT6wfmPd7uFgHdZPjtkWQiiSxe9tESkZg9jCycbMZBUPV4qNCxWd3yu/PzvJ1pf4t5Ih+ALA= X-Received: by 2002:a6b:ba42:: with SMTP id k63mr4688761iof.37.1631230687533; Thu, 09 Sep 2021 16:38:07 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> From: Ed Maste Date: Thu, 9 Sep 2021 19:37:39 -0400 Message-ID: Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden To: FreeBSD User Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H5Fn13zszz4Zfp X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 9 Sept 2021 at 15:18, FreeBSD User wrote: > > /etc/ssh/sshd_config line 89: Unsupported option UsePAM Sorry, it turns out I had the wrong version of config.h in my commit. I'm running a build now and will commit it once a test with that change passes. I will look into all of the reported issues, but I'd be much obliged if you can rebuild sshd and try again (once the config.h commit lands). From nobody Fri Sep 10 04:41:36 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 93F5317B62F0 for ; Fri, 10 Sep 2021 04:42:12 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp4-2.goneo.de (smtp4.goneo.de [IPv6:2001:1640:5::8:59]) (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 4H5NWm3NB9z4fK0 for ; Fri, 10 Sep 2021 04:42:12 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from thor.intern.walstatt.dynvpn.de (dynamic-089-012-135-018.89.12.pool.telefonica.de [89.12.135.18]) by smtp4.goneo.de (Postfix) with ESMTPSA id D866B2040D83; Fri, 10 Sep 2021 06:42:03 +0200 (CEST) Date: Fri, 10 Sep 2021 06:41:36 +0200 From: FreeBSD User To: Philipp Ost Cc: FreeBSD CURRENT Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden Message-ID: <20210910064203.4f754d72@thor.intern.walstatt.dynvpn.de> In-Reply-To: <8e25f7ef-3c20-a078-4b47-81b17585df25@smo.de> References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> <8e25f7ef-3c20-a078-4b47-81b17585df25@smo.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H5NWm3NB9z4fK0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Am Thu, 9 Sep 2021 22:12:09 +0200 Philipp Ost schrieb: > On 9/9/21 9:15 PM, FreeBSD User wrote: > [...] > > What has changed in the recent 14-CURRENT OpenSSH update that dramatically that working > > schematics do not work any more? > > OpenSSH has been updated to v8.7p1: > > https://cgit.freebsd.org/src/commit/?id=19261079b74319502c6ffa1249920079f0f69a72 > > One of the more prominent changes is the deprecation of SHA1. > > There's some additional information here: > https://lists.freebsd.org/archives/freebsd-hackers/2021-September/000289.html > > HTH > Philipp > I was and I'm aware of the published changes and deprecating SHA1 would imply non-use of SHA1-based public keys. But public key authentication works fine, for pure ssh and ssh-based rsync (scp untested). Password authentication doesn't work anymore either for pure ssh, scp and rsync. I can not find any hints to dramatic changes to that and this authentication scheme doesn't even work with the standard/vanilla sshd_config for the 14-CURRENT server side. And beware: this problem is present only in relations, were recent 14-CURRENT is the ssh server. oh -- O. Hartmann From nobody Fri Sep 10 08:29:46 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 113C817A0E3F for ; Fri, 10 Sep 2021 08:29:54 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5TZT5YhXz4h7j; Fri, 10 Sep 2021 08:29:53 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ej1-x62b.google.com with SMTP id e21so2602567ejz.12; Fri, 10 Sep 2021 01:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=UOTXNqPYhv/j5M1Xm3fXPTiHWoxkVQ2BNL4ZDkdrt7c=; b=FOHO0sfhhaqlL9tAW3uanpV+hWREDyBidO9a8uIk4va2SGlCDFm0WsT71ldnxpnnhZ hJW0Dc5aodDhGJojYnBTfYgyEd2+FqQKEqxl61g4csRTyVbLuPO7TakAy7/CPpGQ68JU GkleRoJ0X7Zl9JOENwNUdyvqFxHZBbATcOOmCEt9ygtADZ23n2NNkWiHiokKtjRLlvFy TU71wlSWrn4qP4pCk7vzwFfepxxcYHFLNNGIxKv3yLiQpV8p4bEsRblbwtQKaMmKuwc5 7k4ZUCIu8BQdtDuf/NYEwrZeZur4u5bju/JUbbkR+excrixSfiXfanSzEZ1zZlKpSq5L Zi1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=UOTXNqPYhv/j5M1Xm3fXPTiHWoxkVQ2BNL4ZDkdrt7c=; b=Dk59KKsULrELgs3kRwURDGNX25XO0RSSH2d+MThv+Kd2sslK9MXnBQXG4N4+MpDML4 W0Y3WQvkv7obnFgZDxbAmCDMT+zxXBDdJtjgiTeWH4jLWNbSJ9ju1BRW10RVnuncPKWy NXctJo0KSLBMTR2ZDYRtRZSZQdEsjrSbqOvt+7iKzOZwMCAw/RartP0UMojxG4FIUGe6 STPrTCW6gm/aSbiPNVxe+mplJUMnfJ/yLVQ24k+hHphol1aG1hjFx7b9+DMmYnEixsfR HktvYw3HpF+H1D3NALYpAZWaUIfoTyCLzTSu1VedDiNg5oW84z3+a1iSwPAnj9V5ZjI/ Udgg== X-Gm-Message-State: AOAM533xNMbNmZV/4Jv+yHKgmBIGiqjvCNiungL/Epl4+smGYcvmyVDn D1N4qgtVyLimCerU53IfSGf28kpCzpc= X-Google-Smtp-Source: ABdhPJwnESNmLCCdQgVu0SJMCApnNZi/CxBTw9NmWkokkn8b//dfjLyInvQ8gWc49UuzqFs/0cBv8Q== X-Received: by 2002:a17:906:a59:: with SMTP id x25mr8067880ejf.33.1631262587274; Fri, 10 Sep 2021 01:29:47 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id eg14sm2431658edb.64.2021.09.10.01.29.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Sep 2021 01:29:46 -0700 (PDT) Date: Fri, 10 Sep 2021 10:29:46 +0200 From: Gary Jennejohn To: Ed Maste Cc: FreeBSD CURRENT Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden Message-ID: <20210910082946.3f31c6e7@ernst.home> In-Reply-To: References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H5TZT5YhXz4h7j X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 9 Sep 2021 19:37:39 -0400 Ed Maste wrote: > On Thu, 9 Sept 2021 at 15:18, FreeBSD User wrote: > > > > /etc/ssh/sshd_config line 89: Unsupported option UsePAM > > Sorry, it turns out I had the wrong version of config.h in my commit. > > I'm running a build now and will commit it once a test with that > change passes. I will look into all of the reported issues, but I'd be > much obliged if you can rebuild sshd and try again (once the config.h > commit lands). > This is interesting. Was the config.h in the patch the same as the one you committed? When I ran my tests one machine was running the new ssh (from the patch) and the other was running the old ssh, and I didn't have any connection errors. -- Gary Jennejohn From nobody Fri Sep 10 10:04:37 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A6C4217B5E23 for ; Fri, 10 Sep 2021 10:04:40 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5Wgr3n97z3Qnv for ; Fri, 10 Sep 2021 10:04:40 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ej1-x629.google.com with SMTP id i21so3170311ejd.2 for ; Fri, 10 Sep 2021 03:04:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=1o5Trwx4bdTt622s0peh6DJrNSBKqHbKKvoBC3bfiWA=; b=GaV+ojq/9vi8bOcCc+wmobmC1Xmgumf4eAwPqpPvFv1IhBpHHVjOuDnXMbjtl2mUAA 32GdXUplTXQ9tdQqcSlH0hBJNHsNlH5I5vuOiUIr80kOG6RXaC9ppe4paHkZz0a61H6i VZZT3AjkBJylGg5Cajo9FiC6uGcFyiPJZhJtpplzKco38RbsT9g+WqpKtGkyDngKCHh5 crQqY33jL8iD8IILYLffMHVIkeQSzIqgauW8JOuaC6KiSHQGu+ILI7Tw1l4ALo+ph6E/ 69hnTN30BwVwrpPzHCtCgi4EAMWayrjRpiBaW3QCNvuMrlAJx2P0kp8mjMpTi5CgrHdR dcRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=1o5Trwx4bdTt622s0peh6DJrNSBKqHbKKvoBC3bfiWA=; b=s/13ZgaqJ2NNxh5YeP+DkOgLyiQF6fOVOXMMZexK91Y+00D5LOG/ZeR54IXPVeVzAm R/K5tIITSsHnHPyWKDSGT3h2onbgxyTxPTcKnmi/WkMLyGYl7vtrTd/jC2hcRmIakSEH v/lGzxivQc8YnQWrG1vPCU1EhY5XNbH+J7vFIHsmVlpMaxaU06BdhfGFTr4MHrZDbU7T hs3Olv9DMWJ/VRFj/qtkw03JH8GZcRKJZIeX61iaU6qPYCa6AN9LeoH/HqtLC5klfwSw DSO/4DPr8Z37HxWp+Fo5bDZWL9oJTlB2h5pCYbLE/rVZpf9Ttka39OAkAV5MQI3vTma7 8qbg== X-Gm-Message-State: AOAM532C3A9M18cpeucr9uMKMHU22+HFGbBhba8k1R3qCOvMIke+AxuR TjGfSVvTPLETkCeimzsLuRniOVHlfaY= X-Google-Smtp-Source: ABdhPJwcaA7uWnTCnGkgpXk7kBH4yPDjJnYwF5W2IME8OyAHP4PFMawIp2siB90SxDkMj1OOjWBk6A== X-Received: by 2002:a17:907:75f5:: with SMTP id jz21mr8765583ejc.95.1631268279630; Fri, 10 Sep 2021 03:04:39 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id bm1sm2282983ejb.38.2021.09.10.03.04.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Sep 2021 03:04:38 -0700 (PDT) Date: Fri, 10 Sep 2021 12:04:37 +0200 From: Gary Jennejohn To: Warner Losh Cc: FreeBSD Current Subject: Re: error installing stand/i386/loader_4th in HEAD Message-ID: <20210910100437.3fb6c59f@ernst.home> In-Reply-To: References: <20210909131013.3196ad52@ernst.home> <20210909160312.6f0df4a5@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H5Wgr3n97z3Qnv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, 9 Sep 2021 10:37:30 -0600 Warner Losh wrote: > On Thu, Sep 9, 2021, 10:03 AM Gary Jennejohn wrote: > > > On Thu, 9 Sep 2021 09:07:08 -0600 > > Warner Losh wrote: > > > > > On Thu, Sep 9, 2021, 7:11 AM Gary Jennejohn > > wrote: > > > > > > > I got a very strange error while trying to make installworld on HEAD: > > > > > > > > stand/i386/loader_4th (install) > > > > /tmp/install.rIhHqnPC/sh: cc not found > > > > *** Error code 127 > > > > > > > > This from a tree which I updated at 08:37 UTC. According to uname -a > > > > the tree is at commit main-n249276-fc29a8b9d95. > > > > > > > > I booted the new kernel from this tree. > > > > > > > > I've never seen this error before. Why in the world would install need > > > > cc? > > > > > > > > > > The usual cause of this error is time skew. There were some build issues > > > that I've fixed that I was sure I merged to stable/13, but I'll check > > > when I get home. > > > > > > > Thanks. I'll check the times set under /usr/src and /usr/obj. > > > > If you have a reliable way to reproduce this, I'd be quite interested if > it isn't a typical "oops" on dates > Well, the dates under /usr/obj are all more recent than under /usr/src/stand/i386/loader_4th. Seems like installworld should not fail the installation based on the dates alone. Since I'm having probelms with ssh I'm going to update the tree and do a buildworld. I'll see what happens after that. -- Gary Jennejohn From nobody Fri Sep 10 10:53:07 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DC14217CAB93 for ; Fri, 10 Sep 2021 10:53:10 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5Xlp076mz3vw7 for ; Fri, 10 Sep 2021 10:53:10 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ej1-x629.google.com with SMTP id n27so3386542eja.5 for ; Fri, 10 Sep 2021 03:53:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:message-id:reply-to:mime-version :content-transfer-encoding; bh=YZn2xn21nquMLhxtpMrE+kruR6RfBx/dnT3gdCMH7SI=; b=cY6JHGD8KTayYp3d99Y6qr4cn6a/bzPZp9BZLO6IPMMCnf58m0TbPvJPRB3IEZHe/v CjHHhj9xWl8qXdfjL4Quba50lv3sJVHccdWapK2KbPFJu1qlTYcspf6wrAh6BCWdkJFP +yFCz6TL+0VeJFu0GCh/8L4sHYxKaLkBX1SFqCB0HWFjdF4GugCYW4dVl9PPHTEGgAEl cz6BlTygnf4KtW+xcoLnlFmY71j1QTvCSnLOlcOggdGQm2vv60WJF1URMwkZl8+y8ndm /n7ibLmzyNtSFArFBWDsD4CA5oFQdyqtw1JX9U/5XilPwWZyDXtFIWG6Xa5RTvYDpPhc s66A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=YZn2xn21nquMLhxtpMrE+kruR6RfBx/dnT3gdCMH7SI=; b=pO+iKuuEmd036BvRwXPwO6M+p9kCTr77YTCjW9H3VPhpR85k3kGqoaWey0h9shBflU hOUw9jMTSVLXEdbp9fQj4kVw5khhnuBehR0/FphUcq7/2AiIGTWTJauVX+gWOv0F1KRJ BUVo68RQtclK3R3+9oBV7C3kJvEwyvcrYz0Gv+1ESzBgkKiLRlBQQklWfm/Fx3aa5LQv E3i9OM4ILlU6IrCl9YeHNQtLurfqE/mYjc7ZCCuhipIxvjaFDo2KqZB7P909n0fSq+l+ L7nv9zlWYvKI3FcoFh6vh0OAjeRvHW1ZElh6a4K364WN6/wLcPVYsgPMFRuu789LKZil 0b5g== X-Gm-Message-State: AOAM530JB+6/WKIHU/LVBl60LgN9N8bb24e+zVJbcXG6oGbtcPQRoVQx mKHnOmboCcxompBJhSmv/qODIfLmGeY= X-Google-Smtp-Source: ABdhPJy5N0yg3OmZy/7/79iI6BDad/B5xgDBsfAjP/o+dFn5B0dRNE2k8gxYv0fY8NZRq7veiXNKJA== X-Received: by 2002:a17:906:2691:: with SMTP id t17mr3757528ejc.522.1631271189119; Fri, 10 Sep 2021 03:53:09 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id lm21sm2305314ejb.58.2021.09.10.03.53.08 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Sep 2021 03:53:08 -0700 (PDT) Date: Fri, 10 Sep 2021 12:53:07 +0200 From: Gary Jennejohn To: current@freebsd.org Subject: compile failure in /usr/src/stand/libsa Message-ID: <20210910105307.6fef0726@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H5Xlp076mz3vw7 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=cY6JHGD8; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::629 as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; 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]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.23:received]; 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]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::629:from]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N So, a new problem with buildworld in HEAD. Building in /usr/src/stand/libsa fails because dosfs.c, ufs.c and geli/gelidev.c can't find disk.h. But disk.h is located in ../common. I had to modify all three of these files to get the compile to finish by using ../common/disk.h. In /usr/src/stand/defs.mk I find LDRSRC= ${BOOTSRC}/common and defs.mk is included in /usr/src/stand/Makefile.inc. So it seems like the C-files under libsa should find the includes. However, I'm not sure whether LDSRC is the correct value to be using in defs.mk, because I'm not sure what it means. I saw this error on two different machines with the latst HEAD tree. -- Gary Jennejohn From nobody Fri Sep 10 11:02:57 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 00EC717A0279 for ; Fri, 10 Sep 2021 11:03:07 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5XzF6xSyz4V9t; Fri, 10 Sep 2021 11:03:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id q3so1911187edt.5; Fri, 10 Sep 2021 04:03:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=CBDVb3YIkNtWqhegXFw4Y6BEokeJdj4YkHqqHODg46U=; b=L65MTCHj2ARnPbhjxYUUsMKzue7sLU0AD3GHLbDjVHkFP/fBQ5gf9NIuB1ibZVdq9i g9YdJoSwmJeQO2/+2u3cUZ8pzo2k2DNBT2HSpKS+XpdAxHzt2QVWdfAL42TeSKwr6X3F 4LU24+VITo3gZzyVzrcXsR6GrV0FP7VbdBcguWG/45MScgzPO6oTmwGBQpL9FO2CtzL2 lzQjR4yMz1tUj9Cs1Z8sLyYB6nhLVQo0Ppn2++Dn2qN7Q/my3GLmpPwkfHvMKa0HPN9V 1e6+UQOX325MA8+pZI3OscU6O8QyH5OvpApbJOpsvI9UxyKoZGri2BkeCBYTXg4bjsJw 4QGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=CBDVb3YIkNtWqhegXFw4Y6BEokeJdj4YkHqqHODg46U=; b=nKS/Ystmykvg3aINJO9h6x8KHQ5XxoMWUO7GwxSuu1mS+1nwA/MEOG33xOi6UtWSI2 DPRyc2y8WFwSsy/OLOI6GeD9IjrLYJz7t1MQVd1Va8PfZ/diNWGqetnVEE9AFn/zwtAq OHSctua8R9wYYS43W4zP49d95HAmrbkrPziNvFG9pdR38ghfC9yj1QtxKMOws1QDI4Tp O2GyV79plpjggUxTt0hNTIMdFN4sMkS+JUiDlNGWWrb7jsw9PUkwIxQqjP+XnP4zVd60 QdE8qoer1ekaHx9OIbTpZEdXR1x9izOxqRcIz74Y4WbFI9bl8zb4Q2i1Gq18nF7Ng0tm KkWA== X-Gm-Message-State: AOAM531GEmIY6OsMZmnDOpwPeAbPT0WVPQm3LCVh8JuKbSxR91H4oBah lfE1nStzkKDyQZC9SOYwvpv2mw/JlAg= X-Google-Smtp-Source: ABdhPJzLLEhcn8UkFEAMfcHcUBV4aLQADWZUoRYt5oeD09RPjSK4dwm22gnc5hUdpxDPBIhjI7Nuug== X-Received: by 2002:a05:6402:4256:: with SMTP id g22mr5272255edb.89.1631271779453; Fri, 10 Sep 2021 04:02:59 -0700 (PDT) Received: from ernst.home (p5b023517.dip0.t-ipconnect.de. [91.2.53.23]) by smtp.gmail.com with ESMTPSA id q15sm2276039ejx.3.2021.09.10.04.02.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Sep 2021 04:02:58 -0700 (PDT) Date: Fri, 10 Sep 2021 13:02:57 +0200 From: Gary Jennejohn To: Ed Maste Cc: FreeBSD CURRENT Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden Message-ID: <20210910110257.5556af40@ernst.home> In-Reply-To: <20210910082946.3f31c6e7@ernst.home> References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> <20210910082946.3f31c6e7@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4H5XzF6xSyz4V9t X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=L65MTCHj; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::52d as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-1.98 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; REPLYTO_ADDR_EQ_FROM(0.00)[]; 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)[91.2.53.23:received]; 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]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.984]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52d:from]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, 10 Sep 2021 10:29:46 +0200 Gary Jennejohn wrote: > On Thu, 9 Sep 2021 19:37:39 -0400 > Ed Maste wrote: > > > On Thu, 9 Sept 2021 at 15:18, FreeBSD User wrote: > > > > > > /etc/ssh/sshd_config line 89: Unsupported option UsePAM > > > > Sorry, it turns out I had the wrong version of config.h in my commit. > > > > I'm running a build now and will commit it once a test with that > > change passes. I will look into all of the reported issues, but I'd be > > much obliged if you can rebuild sshd and try again (once the config.h > > commit lands). > > > > This is interesting. > > Was the config.h in the patch the same as the one you committed? > > When I ran my tests one machine was running the new ssh (from the > patch) and the other was running the old ssh, and I didn't have any > connection errors. > I now have two HEAD systems running the latest world and ssh works again. Yay! -- Gary Jennejohn From nobody Fri Sep 10 11:50:59 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EA9CC17B8B92 for ; Fri, 10 Sep 2021 11:51:09 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021101.me.com (pv50p00im-ztdg10021101.me.com [17.58.6.44]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H5Z2j5d56z4kyp for ; Fri, 10 Sep 2021 11:51:09 +0000 (UTC) (envelope-from tsoome@me.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1631274662; bh=rGhupYsLG7M+6rKCf20Yq+eeRVy2taDQumBGDyOZzdg=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=wesNFjQAOAA+aXER2wUMZvVMXLjwvBqHvoW9vR/cJ8adkQOKVzJicsaRHzfliVtc9 I1r5JqyZgwYdIu4qJblldO7vFd8PuuPT7zFQoInxrFug9zCusek9/wTF4J5JnhkrEz L5xg7nvdlMwYkgarYoW6RegScy1TmW6F0ynJ4tlymPNea1j3RAp1zQxQXiwRHjd6I9 c6LiNoJzS7JnEh45az8+dKehokWpYO9aCZrhmWtBbmU3DVkyK+n90urTqt/wJCCtBl UYp3twGQ61tBRoF4sMS1e1wwNkAC3f9YSkeTDPXO757Ltbh9RxRidvGnafdf5ZfhGD TZSU19yGcapzg== Received: from smtpclient.apple (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10021101.me.com (Postfix) with ESMTPSA id DAE95180358; Fri, 10 Sep 2021 11:51:01 +0000 (UTC) Message-Id: <6B76ACF0-3896-49F4-8061-C1C94B850ADB@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_2D482388-E716-47A9-9D8F-E9E38D97FC7D" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: compile failure in /usr/src/stand/libsa Date: Fri, 10 Sep 2021 14:50:59 +0300 In-Reply-To: <20210910105307.6fef0726@ernst.home> Cc: current@freebsd.org To: gljennjohn@gmail.com References: <20210910105307.6fef0726@ernst.home> X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.790 definitions=2021-09-10_04:2021-09-09,2021-09-10 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2009150000 definitions=main-2109100072 X-Rspamd-Queue-Id: 4H5Z2j5d56z4kyp X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: tsoome@me.com From: Toomas Soome via current X-Original-From: Toomas Soome X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail=_2D482388-E716-47A9-9D8F-E9E38D97FC7D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 10. Sep 2021, at 13:53, Gary Jennejohn = wrote: >=20 > So, a new problem with buildworld in HEAD. >=20 > Building in /usr/src/stand/libsa fails because dosfs.c, ufs.c and > geli/gelidev.c can't find disk.h. But disk.h is located in ../common. >=20 > I had to modify all three of these files to get the compile to finish > by using ../common/disk.h. >=20 > In /usr/src/stand/defs.mk I find LDRSRC=3D ${BOOTSRC}/common and = defs.mk > is included in /usr/src/stand/Makefile.inc. So it seems like the = C-files > under libsa should find the includes. >=20 > However, I'm not sure whether LDSRC is the correct value to be using > in defs.mk, because I'm not sure what it means. >=20 > I saw this error on two different machines with the latst HEAD tree. >=20 > --=20 > Gary Jennejohn >=20 Could you paste the compiler command line used to build ufs.c for = example? I=E2=80=99m expecting to see something: cc -O2 -pipe -fno-common -nostdinc = -I/usr/obj/usr/src/amd64.amd64/stand/libsa -I/usr/src/stand/libsa = -D_STANDALONE -I/usr/src/sys -Ddouble=3Djagged-little-pill = -Dfloat=3Dfloaty-mcfloatface -ffunction-sections -fdata-sections = -DLOADER_GELI_SUPPORT -I/usr/src/stand/libsa/geli -DLOADER_DISK_SUPPORT = -ffreestanding -mno-mmx -mno-sse -mno-avx -mno-avx2 -msoft-float -fPIC = -mno-red-zone -mno-relax -I. -Iinclude -DBZ_NO_STDIO -DBZ_NO_COMPRESS = -DHAVE_MEMCPY -I/usr/src/sys/contrib/zlib -I/usr/src/stand/common = -DWEAK_REFS -DHAS_ZSTD_ZFS -I/usr/src/stand/common = -I/usr/src/sys/cddl/boot/zfs -I/usr/src/sys/crypto/skein = -I/usr/src/sys/contrib/openzfs/include = -I/usr/src/sys/contrib/openzfs/include/os/freebsd/zfs -Wformat -Wall -g = -gz=3Dzlib -MD -MF.depend.ufs.o -MTufs.o -std=3Dgnu99 = -Wno-format-zero-length -Wsystem-headers -Werror -Wno-pointer-sign = -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable = -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality = -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef = -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Wno-parentheses -Oz -Qunused-arguments = -c /usr/src/stand/libsa/ufs.c -o ufs.o rgds, toomas= --Apple-Mail=_2D482388-E716-47A9-9D8F-E9E38D97FC7D-- From nobody Fri Sep 10 13:04:30 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 75C4917B0944 for ; Fri, 10 Sep 2021 13:05:02 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f44.google.com (mail-io1-f44.google.com [209.85.166.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H5bgy2nzjz3NFQ for ; Fri, 10 Sep 2021 13:05:02 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f44.google.com with SMTP id n24so2195212ion.10 for ; Fri, 10 Sep 2021 06:05:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zkfE3+1kYSOuaRgvwzXVRv95qFvYj+8RuFmUFjYk1ZU=; b=kNH6hBb3szjgNNmTn6KXgmtm5Imm3QovUQf6K4E20JHfoAfp3iPTbXQUoE+3agA5C8 HA84KwkGevETDiWe0KCMgZn9HPi0/ve+yAG/sNxPQx+9BhQzwe1tBJdoOQCD95nZ1JlY cCwNukYptGlh3h52qnjebCL15s62oMhns+KFPiffeYK1AMMsPcAJTQ06JXfNaOgBJ4xT 2RrYR9khHQuo04xMNCMj/3TPjKrTO/21t7c28HjW9Gw/fF/EgfkhA/tFk1pGlLCdfdcU Ww6Ns6B6wefGXYyYR86b8zQj8C66X3VX10QeiISRdGWsZWueFI+uLMPJL8a39dWcy+Ne y1/g== X-Gm-Message-State: AOAM530lKz0xMUTVRv0UFvEsA8uK6w6bHZKa8bqy+mSGVg5EAvDcK6t6 AUdcPO5jV8ZkUfPW3iE9yWQ6Lo8VW990ppRBMTs= X-Google-Smtp-Source: ABdhPJxO4F5w43bVvhg2auvl0MbvcNA2GN6Do0rWSxoSgrsX7k4ru1bxnkDbTZimqroPsGrIh3mN4gnvvxnv1tVUNN0= X-Received: by 2002:a6b:c1:: with SMTP id 184mr7064921ioa.48.1631279101716; Fri, 10 Sep 2021 06:05:01 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> <20210910082946.3f31c6e7@ernst.home> In-Reply-To: <20210910082946.3f31c6e7@ernst.home> From: Ed Maste Date: Fri, 10 Sep 2021 09:04:30 -0400 Message-ID: Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden To: gljennjohn@gmail.com Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H5bgy2nzjz3NFQ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, 10 Sept 2021 at 04:29, Gary Jennejohn wrote: > > Was the config.h in the patch the same as the one you committed? No it wasn't - USE_PAM was #defined in config.h after applying the patch, while the committed version accidentally did not. From nobody Sat Sep 11 16:54:47 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B493017CD32F for ; Sat, 11 Sep 2021 16:55:05 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4H6Jkx11Smz4nNc; Sat, 11 Sep 2021 16:55:05 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-io1-f52.google.com with SMTP id b7so6455896iob.4; Sat, 11 Sep 2021 09:55:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=RER+2kw+SF1FWMJ5gtRxNuZ8fvLebe90Noy9T1e0j0s=; b=h9byY+wPaeLypWYGxn5zwd3dQXQ4GS9Q7DexaJjktji7q4g28uqTomS8x5lkGVD4xQ XPi/hLygdR1j5IrrsgpZWHkHzgeudEmRP2BF3j8XvbsKc6DeFTltjuCvMhI4Lx2QS4Tk F6ShqSGeRyuISnL3T7veC2orWsFadGMg2kTUShdtZ476ws1YNEcRY1UkEV389gedFtXC aho3kV4EIN77c2N26P+VG4sbeJwg6afAtq5PY6ysQACxw08T3FDZbwD1j6wUVdgVO+CN sseKtGHRmvMO/G2GRuuM/klqOkzybedPdd1ubIKPuad7UuJcYifTRFjhy0GKDB7IPURb MUvw== X-Gm-Message-State: AOAM530fZICJB3H7j515NdGca4OYPhPc7qIZWdKn6IV96/5l+bXnP5j3 uh+8M/DzPKPkwhwCVlom9SjTcpomfxAxtdZhxH86upkY1lPQDA== X-Google-Smtp-Source: ABdhPJzfQi6tnhn2Sx7ID2UtRfcku+ZJEF3o75G4hAQVPp7t3R7W/QxjQtrfr99uUTPkugAtMyZRdWBrxd502zh1XGE= X-Received: by 2002:a5d:9958:: with SMTP id v24mr845727ios.201.1631379297694; Sat, 11 Sep 2021 09:54:57 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Jeremie Le Hen Date: Sat, 11 Sep 2021 18:54:47 +0200 Message-ID: Subject: undefined symbol: rand_range To: FreeBSD Current Cc: donner@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4H6Jkx11Smz4nNc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jlehen@gmail.com designates 209.85.166.52 as permitted sender) smtp.mailfrom=jlehen@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.52:from]; FORGED_SENDER(0.30)[jlh@freebsd.org,jlehen@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.52:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jlh@freebsd.org,jlehen@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N Hey folks, I'm getting the error below when compiling -CURRENT. Anyone else having this error? --- perf.full --- cc -target x86_64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src.git/amd64.amd64/tmp -B/usr/obj/usr/src.git/amd64.amd64/tmp/usr/bin -O -pipe -fno-common -march=core2 -fPIE -g -gz=zlib -std=gnu99 -Wno-format-zero-length -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -pie -o perf.full perf.o util.o -lalias ld: error: undefined symbol: rand_range >>> referenced by perf.c:122 (/usr/src.git/tests/sys/netinet/libalias/perf.c:122) >>> perf.o:(main) >>> referenced by perf.c:123 (/usr/src.git/tests/sys/netinet/libalias/perf.c:123) >>> perf.o:(main) >>> referenced by perf.c:126 (/usr/src.git/tests/sys/netinet/libalias/perf.c:126) >>> perf.o:(main) >>> referenced 13 more times ld: error: undefined symbol: addr_eq >>> referenced by perf.c:164 (/usr/src.git/tests/sys/netinet/libalias/perf.c:164) >>> perf.o:(main) >>> referenced by perf.c:165 (/usr/src.git/tests/sys/netinet/libalias/perf.c:165) >>> perf.o:(main) >>> referenced by perf.c:246 (/usr/src.git/tests/sys/netinet/libalias/perf.c:246) >>> perf.o:(main) >>> referenced 3 more times cc: error: linker command failed with exit code 1 (use -v to see invocation) -- Jeremie Le Hen jlh@FreeBSD.org From nobody Sun Sep 12 05:52:51 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B68E117A8A2B for ; Sun, 12 Sep 2021 06:12:10 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (mx.uats.od.ua [81.25.226.133]) by mx1.freebsd.org (Postfix) with ESMTP id 4H6fQd620fz3rNT for ; Sun, 12 Sep 2021 06:12:09 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.uats.od.ua (Postfix) with ESMTPS id 855437CE5B for ; Sun, 12 Sep 2021 08:52:51 +0300 (EEST) Received: from [78.26.168.228] ([78.26.168.228]) by uats.od.ua (Horde Framework) with HTTP; Sun, 12 Sep 2021 08:52:51 +0300 Date: Sun, 12 Sep 2021 08:52:51 +0300 Message-ID: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> From: Yuri Tcherkasov To: freebsd-current@freebsd.org Subject: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Disposition: inline X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: 855437CE5B.A95A3 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: tyv@uats.od.ua X-Spam-Status: No X-Rspamd-Queue-Id: 4H6fQd620fz3rNT X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of tyv@uats.od.ua has no SPF policy when checking 81.25.226.133) smtp.mailfrom=tyv@uats.od.ua X-Spamd-Result: default: False [0.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[uats.od.ua]; NEURAL_SPAM_SHORT(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15595, ipnet:81.25.226.0/24, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[78.26.168.228:received] X-ThisMailContainsUnwantedMimeParts: N Hi I'm binary upgrade FreeBSD from 10.2 to 13.0 After upgrate all workin well, but I need add one more routing table. So add to GENERIC kernel options ROUTETABLES=2 and recompile it. After normaly recompile can't configure ipfw nat with error ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument Returning original kernel instataling with upgrade resolve problem with nat but multiple route I can't use. Anybody can help me? Thanx! -- -- Yuri Tcherkasov E-Mail: tyv@uats.od.ua From nobody Sun Sep 12 10:57:35 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 7ACE517B477E for ; Sun, 12 Sep 2021 10:57:50 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [5.45.198.240]) (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 4H6mmG286Hz4fXT for ; Sun, 12 Sep 2021 10:57:49 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from iva5-8cd627e71aff.qloud-c.yandex.net (iva5-8cd627e71aff.qloud-c.yandex.net [IPv6:2a02:6b8:c0c:7b87:0:640:8cd6:27e7]) by forward100j.mail.yandex.net (Yandex) with ESMTP id B244E64F3086; Sun, 12 Sep 2021 13:57:40 +0300 (MSK) Received: from iva8-a4a480c9f089.qloud-c.yandex.net (iva8-a4a480c9f089.qloud-c.yandex.net [2a02:6b8:c0c:da5:0:640:a4a4:80c9]) by iva5-8cd627e71aff.qloud-c.yandex.net (mxback/Yandex) with ESMTP id 24MbcrI9Eu-veEWJ246; Sun, 12 Sep 2021 13:57:40 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1631444260; bh=fRAb5eTGUUXmfDVrrxz9idxNv9RwReAn5jhpe3seHAc=; h=To:References:Date:Subject:Cc:From:Message-Id:In-Reply-To; b=k3HY5xoDqy0eBNzDSjSJDXNr65lNtGvSMfLTx9yzxfxh26IicwCH/wQo253GBgZtC BADz7iZW3kdn8HqVeOb4PQZ44S196YOKdi4mB9ikG2qElDXpzpalFS4jD3qcAiAgqW k5mYFV4+ekOYpbk9ofoEc6eTjMvwh8bZfD3mzXXk= Received: by iva8-a4a480c9f089.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id bEEhdHyGCH-vduOvNaj; Sun, 12 Sep 2021 13:57:40 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument From: "Alexander V. Chernikov" In-Reply-To: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> Date: Sun, 12 Sep 2021 11:57:35 +0100 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> To: Yuri Tcherkasov X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4H6mmG286Hz4fXT X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: >=20 > Hi >=20 > I'm binary upgrade FreeBSD from 10.2 to 13.0 >=20 > After upgrate all workin well, but I need add one more routing table. = So add to > GENERIC kernel You can add 'net.fibs=3D2' in the loader.conf, there is no need to = recompile the kernel. You can also set in runtime via sysctl. >=20 > options ROUTETABLES=3D2 >=20 > and recompile it. > After normaly recompile can't configure ipfw nat with error >=20 > ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument Could you share the particular command failing? >=20 > Returning original kernel instataling with upgrade resolve problem = with nat but multiple route I can't use. >=20 > Anybody can help me? >=20 > Thanx! >=20 > --=20 > -- > Yuri Tcherkasov > E-Mail: tyv@uats.od.ua >=20 >=20 From nobody Sun Sep 12 10:46:13 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5CDA117BA328 for ; Sun, 12 Sep 2021 11:05:35 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (mx.uats.od.ua [81.25.226.133]) by mx1.freebsd.org (Postfix) with ESMTP id 4H6mxC1Sswz4kBC for ; Sun, 12 Sep 2021 11:05:35 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.uats.od.ua (Postfix) with ESMTPS id C6D2C807EC; Sun, 12 Sep 2021 13:46:13 +0300 (EEST) Received: from [78.26.168.228] ([78.26.168.228]) by uats.od.ua (Horde Framework) with HTTP; Sun, 12 Sep 2021 13:46:13 +0300 Date: Sun, 12 Sep 2021 13:46:13 +0300 Message-ID: <20210912134613.Horde.or3k1wSFhXiRHu4UDhLi1JR@uats.od.ua> From: Yuri Tcherkasov To: "Alexander V. Chernikov" Cc: freebsd-current@freebsd.org Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: C6D2C807EC.A8209 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: tyv@uats.od.ua X-Spam-Status: No X-Rspamd-Queue-Id: 4H6mxC1Sswz4kBC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N Thanx, i try. Цитирую "Alexander V. Chernikov" : >> On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: >> >> Hi >> >> I'm binary upgrade FreeBSD from 10.2 to 13.0 >> >> After upgrate all workin well, but I need add one more routing >> table. So add to >> GENERIC kernel > You can add 'net.fibs=2' in the loader.conf, there is no need to > recompile the kernel. > You can also set in runtime via sysctl. >> >> options ROUTETABLES=2 >> >> and recompile it. >> After normaly recompile can't configure ipfw nat with error >> >> ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument > Could you share the particular command failing? > >> >> Returning original kernel instataling with upgrade resolve problem >> with nat but multiple route I can't use. >> >> Anybody can help me? >> >> Thanx! >> >> -- >> -- >> Yuri Tcherkasov >> E-Mail: tyv@uats.od.ua >> >> -- -- Yuri Tcherkasov E-Mail: tyv@uats.od.ua From nobody Sun Sep 12 10:46:36 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 357F817BA658 for ; Sun, 12 Sep 2021 11:05:59 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (mx.uats.od.ua [81.25.226.133]) by mx1.freebsd.org (Postfix) with ESMTP id 4H6mxd6QWwz4kbL for ; Sun, 12 Sep 2021 11:05:57 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.uats.od.ua (Postfix) with ESMTPS id 8A869807FC for ; Sun, 12 Sep 2021 13:46:36 +0300 (EEST) Received: from [78.26.168.228] ([78.26.168.228]) by uats.od.ua (Horde Framework) with HTTP; Sun, 12 Sep 2021 13:46:36 +0300 Date: Sun, 12 Sep 2021 13:46:36 +0300 Message-ID: <20210912134636.Horde.Lu8R8q2rjm87zWANyAS74jl@uats.od.ua> From: Yuri Tcherkasov To: freebsd-current@freebsd.org Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: 8A869807FC.A70C6 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: tyv@uats.od.ua X-Spam-Status: No X-Rspamd-Queue-Id: 4H6mxd6QWwz4kbL X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of tyv@uats.od.ua has no SPF policy when checking 81.25.226.133) smtp.mailfrom=tyv@uats.od.ua X-Spamd-Result: default: False [0.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[uats.od.ua]; NEURAL_SPAM_SHORT(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15595, ipnet:81.25.226.0/24, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[78.26.168.228:received] X-ThisMailContainsUnwantedMimeParts: N Thanx, i try. Цитирую "Alexander V. Chernikov" : >> On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: >> >> Hi >> >> I'm binary upgrade FreeBSD from 10.2 to 13.0 >> >> After upgrate all workin well, but I need add one more routing >> table. So add to >> GENERIC kernel > You can add 'net.fibs=2' in the loader.conf, there is no need to > recompile the kernel. > You can also set in runtime via sysctl. >> >> options ROUTETABLES=2 >> >> and recompile it. >> After normaly recompile can't configure ipfw nat with error >> >> ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument > Could you share the particular command failing? > >> >> Returning original kernel instataling with upgrade resolve problem >> with nat but multiple route I can't use. >> >> Anybody can help me? >> >> Thanx! >> >> -- >> -- >> Yuri Tcherkasov >> E-Mail: tyv@uats.od.ua >> >> -- -- Yuri Tcherkasov E-Mail: tyv@uats.od.ua From nobody Sun Sep 12 10:51:38 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 446C117BFFB5 for ; Sun, 12 Sep 2021 11:10:58 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (mx.uats.od.ua [81.25.226.133]) by mx1.freebsd.org (Postfix) with ESMTP id 4H6n3Q0nPfz4q2J for ; Sun, 12 Sep 2021 11:10:58 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.uats.od.ua (Postfix) with ESMTPS id EBA0280863; Sun, 12 Sep 2021 13:51:38 +0300 (EEST) Received: from [78.26.168.228] ([78.26.168.228]) by uats.od.ua (Horde Framework) with HTTP; Sun, 12 Sep 2021 13:51:38 +0300 Date: Sun, 12 Sep 2021 13:51:38 +0300 Message-ID: <20210912135138.Horde.jU7HSS-HXDDbodinjUouo3z@uats.od.ua> From: Yuri Tcherkasov To: "Alexander V. Chernikov" Cc: freebsd-current@freebsd.org Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: EBA0280863.A7F3D X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: tyv@uats.od.ua X-Spam-Status: No X-Rspamd-Queue-Id: 4H6n3Q0nPfz4q2J X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N The command is root@gw:/home/tyv # ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports ipfw nat 1 config ip 195.138.73.206 same_ports unreg_only reset root@gw:/home/tyv # Цитирую "Alexander V. Chernikov" : >> On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: >> >> Hi >> >> I'm binary upgrade FreeBSD from 10.2 to 13.0 >> >> After upgrate all workin well, but I need add one more routing >> table. So add to >> GENERIC kernel > You can add 'net.fibs=2' in the loader.conf, there is no need to > recompile the kernel. > You can also set in runtime via sysctl. >> >> options ROUTETABLES=2 >> >> and recompile it. >> After normaly recompile can't configure ipfw nat with error >> >> ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument > Could you share the particular command failing? > >> >> Returning original kernel instataling with upgrade resolve problem >> with nat but multiple route I can't use. >> >> Anybody can help me? >> >> Thanx! >> >> -- >> -- >> Yuri Tcherkasov >> E-Mail: tyv@uats.od.ua >> >> -- -- Yuri Tcherkasov E-Mail: tyv@uats.od.ua From nobody Sun Sep 12 12:01:04 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E2C6217AFB58 for ; Sun, 12 Sep 2021 12:01:19 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) (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 4H6p9W4rtVz3NKl; Sun, 12 Sep 2021 12:01:19 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from myt5-6c0659e8c6cb.qloud-c.yandex.net (myt5-6c0659e8c6cb.qloud-c.yandex.net [IPv6:2a02:6b8:c12:271e:0:640:6c06:59e8]) by forward105j.mail.yandex.net (Yandex) with ESMTP id E5CFF4EC8A9E; Sun, 12 Sep 2021 15:01:09 +0300 (MSK) Received: from myt5-ca5ec8faf378.qloud-c.yandex.net (myt5-ca5ec8faf378.qloud-c.yandex.net [2a02:6b8:c12:2514:0:640:ca5e:c8fa]) by myt5-6c0659e8c6cb.qloud-c.yandex.net (mxback/Yandex) with ESMTP id ETSM8OVuvc-19EaPANs; Sun, 12 Sep 2021 15:01:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1631448069; bh=XadKwvEPTmtr5c5m3to6XQY4NYGQ2rDwsF+1haQZIPM=; h=To:In-Reply-To:References:Date:Subject:Cc:Message-Id:From; b=Jxjp7dGeWe24hOac7CKDz2z3Q5vfRA8rl4w9SRUdMRaiDszyE14BFSpucQPOOVC43 F1FbuhZQHOtKAV6OHhMrz7rmXWwjt8jFOEGNHbm1zCQw/CdjIZZCF98VcIdTETj3St CD7pOO/MWNxaQIgUhNmVFF/5Fbik/E21NYE5YUhA= Received: by myt5-ca5ec8faf378.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id cLlHi08bZJ-18jSh2i0; Sun, 12 Sep 2021 15:01:09 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) From: "Alexander V. Chernikov" Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_802CCEF6-5691-47CE-8611-50E44CDB9464" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument Date: Sun, 12 Sep 2021 13:01:04 +0100 In-Reply-To: <20210912135138.Horde.jU7HSS-HXDDbodinjUouo3z@uats.od.ua> Cc: freebsd-current@freebsd.org, nc@freebsd.org To: Yuri Tcherkasov References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> <20210912135138.Horde.jU7HSS-HXDDbodinjUouo3z@uats.od.ua> X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Rspamd-Queue-Id: 4H6p9W4rtVz3NKl X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --Apple-Mail=_802CCEF6-5691-47CE-8611-50E44CDB9464 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 12 Sep 2021, at 11:51, Yuri Tcherkasov wrote: >=20 > ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports Looks pretty close to https://reviews.freebsd.org/D23450 = I guess rebuilding the ipfw(8) binary should help. --Apple-Mail=_802CCEF6-5691-47CE-8611-50E44CDB9464-- From nobody Sun Sep 12 11:52:52 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C53CF17B818B for ; Sun, 12 Sep 2021 12:12:12 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (mx.uats.od.ua [81.25.226.133]) by mx1.freebsd.org (Postfix) with ESMTP id 4H6pQ41KyGz3k10 for ; Sun, 12 Sep 2021 12:12:12 +0000 (UTC) (envelope-from tyv@uats.od.ua) Received: from mx.uats.od.ua (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.uats.od.ua (Postfix) with ESMTPS id 56CF180952 for ; Sun, 12 Sep 2021 14:52:52 +0300 (EEST) Received: from [78.26.168.228] ([78.26.168.228]) by uats.od.ua (Horde Framework) with HTTP; Sun, 12 Sep 2021 14:52:52 +0300 Date: Sun, 12 Sep 2021 14:52:52 +0300 Message-ID: <20210912145252.Horde.rFIZnmVH4z8WVcSq-riqX6I@uats.od.ua> From: Yuri Tcherkasov To: freebsd-current@freebsd.org Subject: Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument References: <20210912085251.Horde.dJZ_ni5aqZJvfo8nNMVOcBL@uats.od.ua> <20210912135138.Horde.jU7HSS-HXDDbodinjUouo3z@uats.od.ua> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: 56CF180952.A4582 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: tyv@uats.od.ua X-Spam-Status: No X-Rspamd-Queue-Id: 4H6pQ41KyGz3k10 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of tyv@uats.od.ua has no SPF policy when checking 81.25.226.133) smtp.mailfrom=tyv@uats.od.ua X-Spamd-Result: default: False [0.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[uats.od.ua]; NEURAL_SPAM_SHORT(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15595, ipnet:81.25.226.0/24, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[78.26.168.228:received] X-ThisMailContainsUnwantedMimeParts: N Thanx very much Цитирую "Alexander V. Chernikov" : >> On 12 Sep 2021, at 11:51, Yuri Tcherkasov wrote: >> >> ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports > > Looks pretty close to https://reviews.freebsd.org/D23450 > > > I guess rebuilding the ipfw(8) binary should help. -- -- Yuri Tcherkasov E-Mail: tyv@uats.od.ua