From owner-freebsd-current@freebsd.org Sun Nov 22 07:06:58 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E80EB47EAEA for ; Sun, 22 Nov 2020 07:06:58 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) 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 4Cf1YZ24KWz4fFB for ; Sun, 22 Nov 2020 07:06:57 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id a65so14280399wme.1 for ; Sat, 21 Nov 2020 23:06:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=bZ50jNEgxC9DyN0oTAwaT5vkxRDZK1PGvWPmbfxFxBw=; b=aRrItPibJYLd+xP8q9q/tGUHQ9U/Vh9bKWrAnJlw0xWUmcAXPXIFOYHs7tOF7roBS7 cHBioqzSuy5nP7fWFX0lSsDhgkftkc8fvHaO32v56Zf66k7pLLwBITelbvOJE7U8U8jd 2dlMMRqoxONN6BF0qyyaX8h4PnKNGIUOcW0LLSHkwtVZdoeus1Tz9Rws03gWmYc9UzWx gjGonlogFYsC2ZTSKGPwZKRg8jIDszkoE1w6Uc9Dc2AQdAmdSAwfqLJikzOqq3fZVaj3 pJuuJ0Zlq37S2nA5zhzx4tKZX+unI8dY3CsOPMqTEo4yF/I4O/0m2tj4AtffFuhCGXju O0pQ== X-Gm-Message-State: AOAM530GDybDt6en8IE/qwjF9YfS4XNt1yt+bI1IDDjAVQg+m8ov74YJ KYkSm1wIzwGYB2ox9tzBAn65XHL9buU= X-Google-Smtp-Source: ABdhPJwF/Ohm2niYeRNssXbTJWeBXLQHprmavk8dDE+Vo7nwdmG7d18SoLOEp0dtZkcDqoM3Vfk0xA== X-Received: by 2002:a1c:b304:: with SMTP id c4mr17695551wmf.20.1606028816001; Sat, 21 Nov 2020 23:06:56 -0800 (PST) Received: from [192.168.1.11] (79-66-147-78.dynamic.dsl.as9105.com. [79.66.147.78]) by smtp.gmail.com with ESMTPSA id d3sm12231680wrg.16.2020.11.21.23.06.54 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 21 Nov 2020 23:06:54 -0800 (PST) Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 From: Graham Perrin To: FreeBSD-CURRENT References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> Message-ID: <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> Date: Sun, 22 Nov 2020 07:06:54 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4Cf1YZ24KWz4fFB X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32a:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[79.66.147.78:received]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32a:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32a:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 07:06:59 -0000 On 20/11/2020 09:57, Graham Perrin wrote: > On 16/11/2020 09:27, Graham Perrin wrote: >> Attempting to build r367615 on Friday 13th: >> >> … >> >> ===> lib/libprocstat/zfs (install) >> install -U  -C -o root -g wheel -m 444 >> /usr/src/lib/libprocstat/libprocstat.h >> /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ >> ===> lib/libc (obj,all,install) >> install -U  -C -o root -g wheel -m 444   libc.a >> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/ >> install -U  -s -o root -g wheel -m 444   -S  libc.so.7 >> /usr/obj/usr/src/amd64.amd64/tmp/lib/ >> install -U  -o root -g wheel -m 444    libc.so.7.debug >> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/ >> install: short write to >> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/libc.so.7.debug: >> 393216 bytes written, 7462472 bytes asked to write >> *** [_libinstall] Error code 71 >> >> make[4]: stopped in /usr/src/lib/libc >> 1 error >> >> make[4]: stopped in /usr/src/lib/libc >> root@mowa219-gjp4-8570p:/usr/src # > > The same problem – short write to > /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/libc.so.7.debug – > when attempting buildworld of r367847. > > If it's relevant: I'm using r367081 for these attempts. The same problem when attempting buildworld of r367923. Prior to this I performed a fresh checkout of /usr/src What might cause these failures? If it's relevant: I have compression set to gzip-9 for the ZFS dataset that mounts at /usr From owner-freebsd-current@freebsd.org Sun Nov 22 08:09:55 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F4902E8BA2 for ; Sun, 22 Nov 2020 08:09:55 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 4Cf2yB4S12z4j1Z for ; Sun, 22 Nov 2020 08:09:54 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32b.google.com with SMTP id a186so12124118wme.1 for ; Sun, 22 Nov 2020 00:09:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=94khHTj2e8CKAc+brC8y19N6A+/XlVQXO1vd2/hYprU=; b=SS7lQ9G5hB6gUuvfDVweERDQcZf81f4+1nGlkvFYkJQVM/Wu1mkArTbwcqa3sXNoIR iSU9fxjcBHM7zmWZOXZHvKeDcLrza30cSUUa7T0zXHPTBEXj/PSsUhUFEqw9RTGIdHoP 4QpYapocUV26W87ugq+Pd+/ZqO5fP7pjfW4njo1G9ZtmT5LfUIsHlCPs8h5Dtj9Iavjf 84tVKGeW56YmpgsqDReEPV3tyxo+T1GOUpR0n3siF+qTcbMaflFgfYc7FvVIcURyRhYy OoI+tCInq90qRo9tLMLxzwMXLkph8zJkLGPdTdmd4hG2mLEr0U+2qyDF3QJj4GxCl6tS An2Q== X-Gm-Message-State: AOAM533dzOkEiSKsZtIeeWVeDTvi1rpceSB0HoVv76mNqIPonmapmtoG m4CImG7c7JqRpQQdiCYAASQfjL+mCOo= X-Google-Smtp-Source: ABdhPJxEsnGUMxjxDp5esyN9AT/DEjF4Xp1VizW9HwZAtN9g3xDytIaPiTaW++kySz9ROarELb2jBw== X-Received: by 2002:a7b:c3ce:: with SMTP id t14mr18592422wmj.170.1606032591559; Sun, 22 Nov 2020 00:09:51 -0800 (PST) Received: from [192.168.1.11] (79-66-147-78.dynamic.dsl.as9105.com. [79.66.147.78]) by smtp.gmail.com with ESMTPSA id q81sm2529842wme.34.2020.11.22.00.09.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 Nov 2020 00:09:50 -0800 (PST) Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 To: Konstantin Belousov Cc: FreeBSD-CURRENT References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <20201116093249.GU39170@kduck.mit.edu> <8824a8de-99a7-be93-2273-01941c3dda97@gmail.com> From: Graham Perrin Message-ID: Date: Sun, 22 Nov 2020 08:09:50 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4Cf2yB4S12z4j1Z X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; 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]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32b:from]; 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=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[79.66.147.78:received]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32b:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32b:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 08:09:55 -0000 On 17/11/2020 00:39, Konstantin Belousov wrote: > On Mon, Nov 16, 2020 at 10:56:06AM +0000, Graham Perrin wrote: >> On 16/11/2020 09:32, Benjamin Kaduk wrote: >>> On Mon, Nov 16, 2020 at 09:27:29AM +0000, Graham Perrin wrote: >>>> Attempting to build r367615 on Friday 13th: >>>> >>>> … >>>> >>>> ===> lib/libprocstat/zfs (install) >>>> install -U  -C -o root -g wheel -m 444 >>>> /usr/src/lib/libprocstat/libprocstat.h >>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ >>>> ===> lib/libc (obj,all,install) >>>> install -U  -C -o root -g wheel -m 444   libc.a >>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/ >>>> install -U  -s -o root -g wheel -m 444   -S  libc.so.7 >>>> /usr/obj/usr/src/amd64.amd64/tmp/lib/ >>>> install -U  -o root -g wheel -m 444    libc.so.7.debug >>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/ >>>> install: short write to >>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/libc.so.7.debug: >>>> 393216 bytes written, 7462472 bytes asked to write >>>> *** [_libinstall] Error code 71 >>> Is your disk/filesystem full? >>> >>> -Ben >> AVAIL: 204G > And what is the type of filesystem you are _installing_ to ? > Also what is the type of filesystem for /tmp, and how much space do you > have there ? root@mowa219-gjp4-8570p:~ # zfs get available,compression copperbowl/tmp copperbowl/usr NAME            PROPERTY     VALUE           SOURCE copperbowl/tmp  available    221G            - copperbowl/tmp  compression  off             local copperbowl/usr  available    221G            - copperbowl/usr  compression  gzip-9          local root@mowa219-gjp4-8570p:~ # zfs list NAME                                           USED  AVAIL REFER  MOUNTPOINT copperbowl                                     213G   221G 88K  /copperbowl copperbowl/ROOT                               97.5G   221G 88K  none copperbowl/ROOT/Waterfox                       348M   221G 59.3G  / copperbowl/ROOT/r367081e                      1.61M   221G 38.0G  / copperbowl/ROOT/r367081f                      97.2G   221G 39.2G  / copperbowl/VirtualBox                          288K   221G 288K  /usr/local/VirtualBox copperbowl/iocage                             4.35G   221G 3.68M  /copperbowl/iocage copperbowl/iocage/download                     359M   221G 88K  /copperbowl/iocage/download copperbowl/iocage/download/12.0-RELEASE        359M   221G 359M  /copperbowl/iocage/download/12.0-RELEASE copperbowl/iocage/images                        88K   221G 88K  /copperbowl/iocage/images copperbowl/iocage/jails                       2.75G   221G 88K  /copperbowl/iocage/jails copperbowl/iocage/jails/jbrowsers             2.75G   221G 92K  /copperbowl/iocage/jails/jbrowsers copperbowl/iocage/jails/jbrowsers/root        2.75G   221G 3.99G  /copperbowl/iocage/jails/jbrowsers/root copperbowl/iocage/log                          100K   221G 100K  /copperbowl/iocage/log copperbowl/iocage/releases                    1.24G   221G 88K  /copperbowl/iocage/releases copperbowl/iocage/releases/12.0-RELEASE       1.24G   221G 88K  /copperbowl/iocage/releases/12.0-RELEASE copperbowl/iocage/releases/12.0-RELEASE/root  1.24G   221G 1.24G  /copperbowl/iocage/releases/12.0-RELEASE/root copperbowl/iocage/templates                     88K   221G 88K  /copperbowl/iocage/templates copperbowl/poudriere                          35.9G   221G 88K  /copperbowl/poudriere copperbowl/poudriere/data                     1.73G   221G 96K  /usr/local/poudriere/data copperbowl/poudriere/data/.m                    88K   221G 88K  /usr/local/poudriere/data/.m copperbowl/poudriere/data/cache                224K   221G 224K  /usr/local/poudriere/data/cache copperbowl/poudriere/data/logs                1.71G   221G 1.71G  /usr/local/poudriere/data/logs copperbowl/poudriere/data/packages            24.3M   221G 24.3M  /usr/local/poudriere/data/packages copperbowl/poudriere/data/wrkdirs               88K   221G 88K  /usr/local/poudriere/data/wrkdirs copperbowl/poudriere/jails                    2.05G   221G 88K  /copperbowl/poudriere/jails copperbowl/poudriere/jails/head               2.05G   221G 2.05G  /usr/local/poudriere/jails/head copperbowl/poudriere/ports                    32.1G   221G 88K  /copperbowl/poudriere/ports copperbowl/poudriere/ports/default            32.1G   221G 32.1G  /usr/local/poudriere/ports/default copperbowl/tmp                                 808K   221G 808K  /tmp copperbowl/usr                                70.4G   221G 88K  /usr copperbowl/usr/home                           67.5G   221G 61.9G  /usr/home copperbowl/usr/ports                          1.83G   221G 1.83G  /usr/ports copperbowl/usr/src                            1.06G   221G 1.06G  /usr/src copperbowl/var                                4.14G   221G 88K  /var copperbowl/var/audit                            88K   221G 88K  /var/audit copperbowl/var/crash                          3.81G   221G 3.81G  /var/crash copperbowl/var/log                            15.7M   221G 15.7M  /var/log copperbowl/var/mail                            136K   221G 136K  /var/mail copperbowl/var/tmp                             319M   221G 319M  /var/tmp copperbowl/vm-bhyve                            116K   221G 116K  /copperbowl/vm-bhyve root@mowa219-gjp4-8570p:~ # From owner-freebsd-current@freebsd.org Sun Nov 22 08:57:19 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BC2412E92F0 for ; Sun, 22 Nov 2020 08:57:19 +0000 (UTC) (envelope-from peter@libassi.se) Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [93.188.3.37]) (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 4Cf40t0vyxz4l32 for ; Sun, 22 Nov 2020 08:57:17 +0000 (UTC) (envelope-from peter@libassi.se) Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id EF24C10D1850 for ; Sun, 22 Nov 2020 09:57:14 +0100 (CET) Received: from s630.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id D0A2A2E324F2 for ; Sun, 22 Nov 2020 09:57:14 +0100 (CET) Received: from s470.loopia.se (unknown [172.22.191.6]) by s630.loopia.se (Postfix) with ESMTP id C2D6913B9320 for ; Sun, 22 Nov 2020 09:57:14 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s630.loopia.se ([172.22.191.6]) by s470.loopia.se (s470.loopia.se [172.22.190.10]) (amavisd-new, port 10024) with LMTP id Mpyw5FJVMYIW for ; Sun, 22 Nov 2020 09:57:14 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: peter@libassi.se X-Loopia-Originating-IP: 78.82.167.128 Received: from [10.79.0.17] (c-80a7524e.03-77-73746f30.bbcust.telenor.se [78.82.167.128]) (Authenticated sender: peter@libassi.se) by s630.loopia.se (Postfix) with ESMTPSA id 094AA13B930B for ; Sun, 22 Nov 2020 09:57:14 +0100 (CET) From: Peter Libassi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\)) Subject: r367927 buildkernel stops on isp.o undeclared ATPDPSIZE Message-Id: Date: Sun, 22 Nov 2020 09:57:13 +0100 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.3654.20.0.2.21) X-Rspamd-Queue-Id: 4Cf40t0vyxz4l32 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:smtp.outgoing.loopia.se]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[93.188.3.37:from]; ASN(0.00)[asn:39570, ipnet:93.188.2.0/23, country:SE]; R_DKIM_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; FREEFALL_USER(0.00)[peter]; 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]; DMARC_NA(0.00)[libassi.se]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[93.188.3.37:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[93.188.3.37:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[93.188.3.37:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 08:57:19 -0000 svnlite info /usr/src Path: . Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 367927 Node Kind: directory Schedule: normal Last Changed Author: rew Last Changed Rev: 367927 Last Changed Date: 2020-11-22 06:00:28 +0100 (Sun, 22 Nov 2020) make -j4 buildkernel KERNCONF=3D"GENERIC-NODEBUG=E2=80=9D --- isp.o --- /usr/src/sys/dev/isp/isp.c:750:50: error: use of undeclared identifier = 'ATPDPSIZE' icbp->icb_xchgcnt =3D MIN(isp->isp_maxcmds / 2, = ATPDPSIZE); ^ /usr/src/sys/dev/isp/isp.c:750:50: error: use of undeclared identifier = 'ATPDPSIZE' 2 errors generated. *** [isp.o] Error code 1 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG --- modules-all --- ctfconvert -L VERSION -g ar5212_eeprom.o *** [modules-all] Error code 2 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG --- isp_freebsd.o --- ctfconvert -L VERSION -g isp_freebsd.o --- if_ipw.o --- ctfconvert -L VERSION -g if_ipw.o 2 errors make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG /Peter= From owner-freebsd-current@freebsd.org Sun Nov 22 12:00:32 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 224672EE5C5 for ; Sun, 22 Nov 2020 12:00:32 +0000 (UTC) (envelope-from dim@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cf84J0S62z4tkK; Sun, 22 Nov 2020 12:00:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id DCD77447C; Sun, 22 Nov 2020 12:00:31 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::3004:f601:e73a:11ee] (unknown [IPv6:2001:470:7a58:0:3004:f601:e73a:11ee]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D32465B63C; Sun, 22 Nov 2020 13:00:29 +0100 (CET) From: Dimitry Andric Message-Id: <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_9EB2C2C6-D171-4411-AA34-F3E171D63D51"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 Date: Sun, 22 Nov 2020 13:00:22 +0100 In-Reply-To: <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> Cc: FreeBSD-CURRENT To: Graham Perrin References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> X-Mailer: Apple Mail (2.3445.104.17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 12:00:32 -0000 --Apple-Mail=_9EB2C2C6-D171-4411-AA34-F3E171D63D51 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 22 Nov 2020, at 08:06, Graham Perrin wrote: >=20 > On 20/11/2020 09:57, Graham Perrin wrote: >> On 16/11/2020 09:27, Graham Perrin wrote: >>> Attempting to build r367615 on Friday 13th: >>>=20 >>> =E2=80=A6 >>>=20 >>> =3D=3D=3D> lib/libprocstat/zfs (install) >>> install -U -C -o root -g wheel -m 444 = /usr/src/lib/libprocstat/libprocstat.h = /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ >>> =3D=3D=3D> lib/libc (obj,all,install) >>> install -U -C -o root -g wheel -m 444 libc.a = /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/ >>> install -U -s -o root -g wheel -m 444 -S libc.so.7 = /usr/obj/usr/src/amd64.amd64/tmp/lib/ >>> install -U -o root -g wheel -m 444 libc.so.7.debug = /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/ >>> install: short write to = /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/libc.so.7.debug: = 393216 bytes written, 7462472 bytes asked to write >>> *** [_libinstall] Error code 71 >>>=20 >>> make[4]: stopped in /usr/src/lib/libc >>> 1 error >>>=20 >>> make[4]: stopped in /usr/src/lib/libc >>> root@mowa219-gjp4-8570p:/usr/src # >>=20 >> The same problem =E2=80=93 short write to = /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debug/lib/libc.so.7.debug =E2=80=93= when attempting buildworld of r367847. >>=20 >> If it's relevant: I'm using r367081 for these attempts. >=20 > The same problem when attempting buildworld of r367923. Prior to this = I performed a fresh checkout of /usr/src >=20 > What might cause these failures? >=20 > If it's relevant: I have compression set to gzip-9 for the ZFS dataset = that mounts at /usr I'd guess it's an unintended side-effect of https://svnweb.freebsd.org/base?view=3Drevision&revision=3D366697 ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on size"). If you only revert usr.bin/xinstall to r366696, and then rebuild it, does it still occur? -Dimitry --Apple-Mail=_9EB2C2C6-D171-4411-AA34-F3E171D63D51 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCX7pS1gAKCRCwXqMKLiCW ozcCAKC7GdRuJS1KkKTnYS0KbpXYPSvn/wCg+PjMaL4W1avI4hZPo8kEa0rswZk= =ZTiZ -----END PGP SIGNATURE----- --Apple-Mail=_9EB2C2C6-D171-4411-AA34-F3E171D63D51-- From owner-freebsd-current@freebsd.org Sun Nov 22 16:06:35 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9EB0246CBF9 for ; Sun, 22 Nov 2020 16:06:35 +0000 (UTC) (envelope-from kevans@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CfFXC40hGz3QDt; Sun, 22 Nov 2020 16:06:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 77322659B; Sun, 22 Nov 2020 16:06:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f170.google.com with SMTP id k4so14129483qko.13; Sun, 22 Nov 2020 08:06:35 -0800 (PST) X-Gm-Message-State: AOAM533ck68whQsXEiGmGCSF4XVufo7NatADi+8xMELFf1Y8aiYD7D8S QzQGlhBQoCi9BC1w87suMq/klmKkvyWBg05Qo4Y= X-Google-Smtp-Source: ABdhPJyD3BwMU4YGtneF7VrFl1Xf2cxqZ6ZlR7+fuGS6fP6M0KfvP6OjTyHFbxgMlpM1AnAVEzsqWmZG74m1DXBKz34= X-Received: by 2002:ae9:e00e:: with SMTP id m14mr25038845qkk.34.1606061195105; Sun, 22 Nov 2020 08:06:35 -0800 (PST) MIME-Version: 1.0 References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> In-Reply-To: <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> From: Kyle Evans Date: Sun, 22 Nov 2020 10:06:24 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 To: Dimitry Andric Cc: Graham Perrin , FreeBSD-CURRENT , Alex Richardson , Ryan Moeller , Matthew Macy Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 16:06:35 -0000 On Sun, Nov 22, 2020 at 6:00 AM Dimitry Andric wrote: > > On 22 Nov 2020, at 08:06, Graham Perrin wrote: > > > > On 20/11/2020 09:57, Graham Perrin wrote: > >> On 16/11/2020 09:27, Graham Perrin wrote: > >>> Attempting to build r367615 on Friday 13th: > >>> > >>> =E2=80=A6 > >>> > >>> =3D=3D=3D> lib/libprocstat/zfs (install) > >>> install -U -C -o root -g wheel -m 444 /usr/src/lib/libprocstat/libpr= ocstat.h /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ > >>> =3D=3D=3D> lib/libc (obj,all,install) > >>> install -U -C -o root -g wheel -m 444 libc.a /usr/obj/usr/src/amd6= 4.amd64/tmp/usr/lib/ > >>> install -U -s -o root -g wheel -m 444 -S libc.so.7 /usr/obj/usr/s= rc/amd64.amd64/tmp/lib/ > >>> install -U -o root -g wheel -m 444 libc.so.7.debug /usr/obj/usr/s= rc/amd64.amd64/tmp/usr/lib/debug/lib/ > >>> install: short write to /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/debu= g/lib/libc.so.7.debug: 393216 bytes written, 7462472 bytes asked to write > >>> *** [_libinstall] Error code 71 > >>> > >>> make[4]: stopped in /usr/src/lib/libc > >>> 1 error > >>> > >>> make[4]: stopped in /usr/src/lib/libc > >>> root@mowa219-gjp4-8570p:/usr/src # > >> > >> The same problem =E2=80=93 short write to /usr/obj/usr/src/amd64.amd64= /tmp/usr/lib/debug/lib/libc.so.7.debug =E2=80=93 when attempting buildworld= of r367847. > >> > >> If it's relevant: I'm using r367081 for these attempts. > > > > The same problem when attempting buildworld of r367923. Prior to this I= performed a fresh checkout of /usr/src > > > > What might cause these failures? > > > > If it's relevant: I have compression set to gzip-9 for the ZFS dataset = that mounts at /usr > > I'd guess it's an unintended side-effect of > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D366697 > ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on > size"). > Almost certainly -- before, we would never attempt to mmap() on ZFS. Tossing arichardson@ into CC as the committer Tossing mmacy@ and freqlabs@ into CC as ZFS folks Looking through sys/contrib/openzfs, there's special handling for mmap on linux because it bypasses the page cache and relies on caching in ARC. AFAICT the FreeBSD side seems to handle write() to mmap'd regions, but doesn't do anything with VOP_MMAPPED which might be needed to sync the file when it's mmap'd for reading like this. My understanding of how this is supposed to actually work on FreeBSD is limited, though, so I defer... Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Sun Nov 22 17:42:27 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0BF7E46EF56 for ; Sun, 22 Nov 2020 17:42:27 +0000 (UTC) (envelope-from arichardson.kde@gmail.com) Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.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 4CfHfp6Rl3z3lmK; Sun, 22 Nov 2020 17:42:26 +0000 (UTC) (envelope-from arichardson.kde@gmail.com) Received: by mail-ej1-f49.google.com with SMTP id s25so20085677ejy.6; Sun, 22 Nov 2020 09:42:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=A1HIgrjD+Fqa5VOpOff3G0t4lfxvTRbKshqIsuUwdJc=; b=Ahd9x7yFWiEzXa4UnsQ22PZfYRC3vc+wuJ8+lmulbwnXzn8z8lpn7w+hj8joUZx1o4 9/53uRTqTMG+Sj4+7FTnR26WsUaC1ccxUkp4cV2n/2HISVnX1wBRhqpaGdzhJO8ecE4w Gg18Qp0AFVxLx4Be1NtElhRrxRL8t6xt2m94BER0paSUvbUO//R45quOT6bmdqx/9scH 3l/sjMlZ5LKJcI40bifH+ZL8ZIqRYAFp/mYZXmonJCihBUMoWRf/A/PNyIXGwkxnbxrc 6vMCUfypRhebvApLy5bQB9PfbJQrHqpuVF7AaqaRhmuxYPAUdJXW6Xne+xpMPQk75j6p CXYA== X-Gm-Message-State: AOAM5328howLXppPFeAQLTSv/fuGQVZQa5GnA+jtQXhoYk/6Zr7WY+n3 h7YJO/nNOG9oFEJ57bChVjkGttopydDahRSa X-Google-Smtp-Source: ABdhPJxRNBlSP93JVc6LdA5/J7BK8E/jkk7u6GV+GRNIjLJViSxrR9xfe6xD9n3TWi7l9dG+zHoZ1Q== X-Received: by 2002:a17:906:bcf9:: with SMTP id op25mr39735969ejb.223.1606066945273; Sun, 22 Nov 2020 09:42:25 -0800 (PST) Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com. [209.85.128.44]) by smtp.gmail.com with ESMTPSA id b21sm3770186ejg.93.2020.11.22.09.42.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 Nov 2020 09:42:24 -0800 (PST) Received: by mail-wm1-f44.google.com with SMTP id a65so15161337wme.1; Sun, 22 Nov 2020 09:42:24 -0800 (PST) X-Received: by 2002:a1c:f219:: with SMTP id s25mr3200782wmc.67.1606066944546; Sun, 22 Nov 2020 09:42:24 -0800 (PST) MIME-Version: 1.0 References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> In-Reply-To: From: Alexander Richardson Date: Sun, 22 Nov 2020 17:42:12 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 To: Kyle Evans Cc: Dimitry Andric , Graham Perrin , FreeBSD-CURRENT , Ryan Moeller , Matthew Macy Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4CfHfp6Rl3z3lmK X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_FROM(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2020 17:42:27 -0000 On Sun, 22 Nov 2020 at 16:06, Kyle Evans wrote: > > On Sun, Nov 22, 2020 at 6:00 AM Dimitry Andric wrote: > > > > On 22 Nov 2020, at 08:06, Graham Perrin wrote: > > > > > > On 20/11/2020 09:57, Graham Perrin wrote: > > >> On 16/11/2020 09:27, Graham Perrin wrote: > > >>> Attempting to build r367615 on Friday 13th: > > >>> > > >>> =E2=80=A6 > > >>> > > >>> =3D=3D=3D> lib/libprocstat/zfs (install) > > >>> install -U -C -o root -g wheel -m 444 /usr/src/lib/libprocstat/lib= procstat.h /usr/obj/usr/src/amd64.amd64/tmp/usr/include/ > > >>> =3D=3D=3D> lib/libc (obj,all,install) > > >>> install -U -C -o root -g wheel -m 444 libc.a /usr/obj/usr/src/am= d64.amd64/tmp/usr/lib/ > > >>> install -U -s -o root -g wheel -m 444 -S libc.so.7 /usr/obj/usr= /src/amd64.amd64/tmp/lib/ > > >>> install -U -o root -g wheel -m 444 libc.so.7.debug /usr/obj/usr= /src/amd64.amd64/tmp/usr/lib/debug/lib/ > > >>> install: short write to /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/de= bug/lib/libc.so.7.debug: 393216 bytes written, 7462472 bytes asked to write > > >>> *** [_libinstall] Error code 71 > > >>> > > >>> make[4]: stopped in /usr/src/lib/libc > > >>> 1 error > > >>> > > >>> make[4]: stopped in /usr/src/lib/libc > > >>> root@mowa219-gjp4-8570p:/usr/src # > > >> > > >> The same problem =E2=80=93 short write to /usr/obj/usr/src/amd64.amd= 64/tmp/usr/lib/debug/lib/libc.so.7.debug =E2=80=93 when attempting buildwor= ld of r367847. > > >> > > >> If it's relevant: I'm using r367081 for these attempts. > > > > > > The same problem when attempting buildworld of r367923. Prior to this= I performed a fresh checkout of /usr/src > > > > > > What might cause these failures? > > > > > > If it's relevant: I have compression set to gzip-9 for the ZFS datase= t that mounts at /usr > > > > I'd guess it's an unintended side-effect of > > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D366697 > > ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on > > size"). > > > > Almost certainly -- before, we would never attempt to mmap() on ZFS. > > Tossing arichardson@ into CC as the committer > Tossing mmacy@ and freqlabs@ into CC as ZFS folks > > Looking through sys/contrib/openzfs, there's special handling for mmap > on linux because it bypasses the page cache and relies on caching in > ARC. AFAICT the FreeBSD side seems to handle write() to mmap'd > regions, but doesn't do anything with VOP_MMAPPED which might be > needed to sync the file when it's mmap'd for reading like this. My > understanding of how this is supposed to actually work on FreeBSD is > limited, though, so I defer... > I'm quite surprised by this, I simply re-used the logic that bin/cp also ha= s. However, it's possible that this is no longer used in cp due to copy_file_r= ange? To be honest I'm not sure whether mmap() even improves performance compared to read/write since the all the MMU setup might be quite expensive and the data might not even be available so we end up copying anyway. Maybe we should change install to use read/write unconditionally? It might also make sense to factor out the copy_file_range+read/write fallback logic in bin/cp to a library that can be used in usr.bin/install. Alex From owner-freebsd-current@freebsd.org Mon Nov 23 12:18:25 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 16F4F2EA08E for ; Mon, 23 Nov 2020 12:18:25 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 4CfmQS234Sz3nYX; Mon, 23 Nov 2020 12:18:24 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id 64so4965617wra.11; Mon, 23 Nov 2020 04:18:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=8jd8rDvl16dNdsUrJPN/qLCQpxtTt+vIIT2wXI4GdyQ=; b=V92x2vd7TXkIQkZifVc9k7E9QuZPNyhXrj6IzuplKpYoPfJ+r7MbCWNtvi0oqfQu5m nBJ2FaxgZ0O0OK62OpzUg23ilSquieuKH+BcA5ZEXYr7UnnKt82seJ1OQ7tKYk26e16X ij75fuOVeY3+d3tTAQ3SqiMQgGPlvQeO0x7JeT00lEEKQRmjdEQSzfV4IY1ucfQP4lmD aFTPiIC8NjzTfM4jhhvxA3dyLfRpmyq+1oQoeOY6a+u5csMU+AqFQYMdrmqkRzsTCS46 SdKxe5eHQBhGKB3qNy5rEKdBYr+4DYGaxHhpIucXI1YhoQRixOwVlyWBXPIN1HRrfRqA 2v8w== X-Gm-Message-State: AOAM532/fwaUsKMU83OAXhlLRa2eNyNEF8Vvajv9TMzydQcTUxW7sjui rMOInufkduJbg8WvhpWBFHe0Susbdn5dVA== X-Google-Smtp-Source: ABdhPJzG20QCJdeVxeeslQxQOcZpPCZJL62BCZMYVygl/cNBig4/L7vhYlAZmEBPRfQN1lIdd3chmw== X-Received: by 2002:adf:c3c8:: with SMTP id d8mr30428339wrg.366.1606133901986; Mon, 23 Nov 2020 04:18:21 -0800 (PST) Received: from [10.8.23.162] ([192.173.128.34]) by smtp.gmail.com with ESMTPSA id e5sm18668610wrs.84.2020.11.23.04.18.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Nov 2020 04:18:21 -0800 (PST) Subject: usr.bin/xinstall r366697 versus: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 To: Dimitry Andric Cc: FreeBSD-CURRENT , Kyle Evans , Alex Richardson , Ryan Moeller , Matthew Macy References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> From: Graham Perrin Message-ID: <9b6bbf0b-93d2-123e-ee5c-f8de660b150a@gmail.com> Date: Mon, 23 Nov 2020 12:18:20 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4CfmQS234Sz3nYX X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCPT_COUNT_FIVE(0.00)[6]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.50)[-0.502]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::42e:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::42e:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::42e:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2020 12:18:25 -0000 On 22/11/2020 12:00, Dimitry Andric wrote: > … > I'd guess it's an unintended side-effect of > https://svnweb.freebsd.org/base?view=revision&revision=366697 > ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on > size"). > > If you only revert usr.bin/xinstall to r366696, and then rebuild it, > does it still occur? > > -Dimitry Thank you! Success with r366696: ---- root@mowa219-gjp4-8570p:~ # date ; uname -v Sun Nov 22 14:36:10 GMT 2020 FreeBSD 13.0-CURRENT #71 r367081: Tue Oct 27 23:56:28 GMT 2020 root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG root@mowa219-gjp4-8570p:~ # svn up /usr/src && portsnap auto Updating '/usr/src': At revision 367936. Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. Fetching snapshot tag from ipv4.aws.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. root@mowa219-gjp4-8570p:~ # svn update -r366696 /usr/src/usr.bin/xinstall Updating '/usr/src/usr.bin/xinstall': U    /usr/src/usr.bin/xinstall/xinstall.c Updated to revision 366696. root@mowa219-gjp4-8570p:~ # cd /usr/src/usr.bin/xinstall/ root@mowa219-gjp4-8570p:/usr/src/usr.bin/xinstall # make echo xinstall.full: /usr/lib/libc.a /usr/lib/libmd.a >> .depend cc  -O2 -pipe -fno-common   -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -g -MD  -MF.depend.xinstall.o -MTxinstall.o -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 -Winline -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    -c /usr/src/usr.bin/xinstall/xinstall.c -o xinstall.o cc  -O2 -pipe -fno-common   -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -g -MD  -MF.depend.getid.o -MTgetid.o -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 -Winline -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    -c /usr/src/contrib/mtree/getid.c -o getid.o cc -O2 -pipe -fno-common -I/usr/src/contrib/mtree -I/usr/src/lib/libnetbsd -g -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 -Winline -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    -o xinstall.full xinstall.o getid.o -L/usr/obj/usr/src/amd64.amd64/lib/libmd -lmd objcopy --only-keep-debug xinstall.full install.debug objcopy --strip-debug --add-gnu-debuglink=install.debug xinstall.full xinstall gzip -cn /usr/src/usr.bin/xinstall/install.1 > install.1.gz ===> tests (all) echo '#! /usr/libexec/atf-sh' > install_test.tmp cat /usr/src/usr.bin/xinstall/tests/install_test.sh >>install_test.tmp chmod +x install_test.tmp mv install_test.tmp install_test root@mowa219-gjp4-8570p:/usr/src/usr.bin/xinstall # make install install  -s -o root -g wheel -m 555   xinstall /usr/bin/install install  -o root -g wheel -m 444  install.debug /usr/lib/debug/usr/bin/install.debug install  -o root -g wheel -m 444 install.1.gz /usr/share/man/man1/ ===> tests (install) install  -o root  -g wheel -m 555  install_test /usr/tests/usr.bin/xinstall/install_test installing DIRS testsFILESDIR install  -d -m 0755 -o root  -g wheel  /usr/tests/usr.bin/xinstall install  -o root  -g wheel -m 444  Kyuafile /usr/tests/usr.bin/xinstall/Kyuafile root@mowa219-gjp4-8570p:/usr/src/usr.bin/xinstall # cd /usr/src && make -j3 buildworld && make -j3 buildkernel KERNCONF=GENERIC-NODEBUG … -------------------------------------------------------------- >>> Kernel build for GENERIC-NODEBUG completed on Sun Nov 22 22:43:02 GMT 2020 -------------------------------------------------------------- >>> Kernel(s)  GENERIC-NODEBUG built in 4973 seconds, ncpu: 4, make -j3 -------------------------------------------------------------- root@mowa219-gjp4-8570p:/usr/src # beadm create r367936a Created successfully root@mowa219-gjp4-8570p:/usr/src # beadm activate r367936a Activated successfully root@mowa219-gjp4-8570p:/usr/src # exit logout grahamperrin@mowa219-gjp4-8570p:~ % exit From owner-freebsd-current@freebsd.org Mon Nov 23 19:18:39 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 04E6846A32C for ; Mon, 23 Nov 2020 19:18:39 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (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 4CfxlL21Hzz4gYw; Mon, 23 Nov 2020 19:18:38 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf1-f53.google.com with SMTP id d17so25319080lfq.10; Mon, 23 Nov 2020 11:18:38 -0800 (PST) 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=THrgWD3wMrti/wOZbqEg5aGdMDmILpUY5UzG/iLmxdk=; b=fyMKskyYTMKJE7zZqNR7/DcIehY/F9Mz9Gn1XwmIBNMkCXzYSXez3m0XaQvXX3Bu5K XvRCpG/KneGdfaRCYzNdoG8uQSGUCyFPmCMt7+rsdBO73R3/969H+yvyxSBid+iD87W0 2Upy9XvHQ2tnVKdAZ6ympFljudU86VkxHhrv5A6YvdmVHNOwO/JySRSpql3Zuti6TjM9 F3j58wRVbPcb5yxWaf7Ia3rzhARCzVGwwDEvFid/yAc7R5856kGasd3tUhbwEA52+h4j fgJun6ZbA3eyvgPXmwRXGJrlE4EHVrf47aqbkG2IiL8731PjoIJX1gGDt5B9jemZfPAg K43g== X-Gm-Message-State: AOAM532RgTRUI9nwebmfVsG4RMxf6j2ZfJxgY3gtfPFRtW3CZwc0TbvV PjzYsXw9r/Q2tdvBKiizv0QFQw2HySGDNg== X-Google-Smtp-Source: ABdhPJxY99jjj2agbl3Y8EbOCf7wesQwswq72i5WZIe4we7/yxUtw/xKEb/yvJRHCLo+Ja5qcPYDAQ== X-Received: by 2002:a05:6512:3e7:: with SMTP id n7mr227395lfq.585.1606159116138; Mon, 23 Nov 2020 11:18:36 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id d9sm61884ljc.63.2020.11.23.11.18.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Nov 2020 11:18:35 -0800 (PST) Subject: Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71 To: Kyle Evans , Dimitry Andric Cc: Graham Perrin , FreeBSD-CURRENT , Alex Richardson , Ryan Moeller , Matthew Macy References: <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> From: Andriy Gapon Message-ID: Date: Mon, 23 Nov 2020 21:18:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Firefox/60.0 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CfxlL21Hzz4gYw X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.91 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.91)[-0.915]; RCPT_COUNT_SEVEN(0.00)[7]; FORGED_SENDER(0.30)[avg@FreeBSD.org,agapon@gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[93.72.151.96:received]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.167.53:from]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[avg@FreeBSD.org,agapon@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[FreeBSD.org]; SPAMHAUS_ZRD(0.00)[209.85.167.53:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.53:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.53:from]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2020 19:18:39 -0000 On 22/11/2020 18:06, Kyle Evans wrote: > On Sun, Nov 22, 2020 at 6:00 AM Dimitry Andric wrote: >> I'd guess it's an unintended side-effect of >> https://svnweb.freebsd.org/base?view=revision&revision=366697 >> ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on >> size"). >> > > Almost certainly -- before, we would never attempt to mmap() on ZFS. > > Tossing arichardson@ into CC as the committer > Tossing mmacy@ and freqlabs@ into CC as ZFS folks > > Looking through sys/contrib/openzfs, there's special handling for mmap > on linux because it bypasses the page cache and relies on caching in > ARC. AFAICT the FreeBSD side seems to handle write() to mmap'd > regions, but doesn't do anything with VOP_MMAPPED which might be > needed to sync the file when it's mmap'd for reading like this. My > understanding of how this is supposed to actually work on FreeBSD is > limited, though, so I defer... Last time I checked mmap worked correctly with ZFS, that was before the switch. Perhaps, there was an undetected issue -- this can be tested, e.g., by applying the install change to stable/12. Perhaps, the ZFS switch came with a regression. -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Nov 24 21:19:15 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AE5FE46A243 for ; Tue, 24 Nov 2020 21:19:15 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4CgcN26mHsz3JnH for ; Tue, 24 Nov 2020 21:19:14 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E7C4E5C00ED for ; Tue, 24 Nov 2020 16:19:13 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 24 Nov 2020 16:19:13 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudegkedgudeglecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehgtderre dttddvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshesiiih gihsthdrnhgvtheqnecuggftrfgrthhtvghrnhepvefghffftdefkeelleehtdejledvhf dvgeeijeevfffguddvhfetgeejueejueeinecukfhppeekvddrjedtrdeluddruddtuden ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthh dqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 8BE45328005D for ; Tue, 24 Nov 2020 16:19:13 -0500 (EST) Date: Tue, 24 Nov 2020 21:19:11 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: git tools for building in base? Message-ID: Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CkLQyaeIKf1Zy19b" Content-Disposition: inline X-Rspamd-Queue-Id: 4CgcN26mHsz3JnH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.25:from]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.111.4.25:from]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.25:from]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; 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.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.111.4.25:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2020 21:19:15 -0000 --CkLQyaeIKf1Zy19b Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, As subject - what will there be in base to interact with the new git repo? I mean, right now, for svn there is svnlite. What for git? Shouldn't it be in base before the move to git?=20 thanks, --=20 J. --CkLQyaeIKf1Zy19b Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl+9eMIACgkQs8o7QhFz NAXuYQ/7Bc1GPxAW9XdTs+wrX8TX3SY5J24U4BX6xqQeX14IqhgBZtknHVjeMZF9 OnwdvVVb1vkYSmU8uAlzqNuMOR9D9BmyFmPFbPLq00wiYVw1KJ2zFinRtlzyobDN kKKrrxwp/NBQXpt1lv9ZKja5gtReWIe6hk0FNpjK69tDc0Q5G6cCMb/D9VXz1JmT HfEnSgeK2h3/D++4FGU7HNtXB3fXdJNbuNpQ1JRh3sXmsh0wYOeHNXTag6GZXT9h 3gGZwBg8Su7pCFfHPpbsTqwRbHSU/uQoYGNOHzbrTDssbknPf1b2Aa31ETp56yi2 wKxOtwJ9fmsA7ssmEpKcBZr0pGMW20A8lNTGJe70mRuBCiuh3cfuI+8I0m2YHWvq oVuinz9950hzlfWVpzpC0NeDLljqm3r6ytoBMeFN4WBzKvXr5NCPd/eMp8XGvXFv qneqXY9kMXV271uL7JuEFl0CqqgOrUX5ZCfr7Tm0jWOiU+LFnAJCDA0YYSU9R0kd lA0tXtAO4DBRSBJ5pBwGZXjdBxbQ1W52NoU64gVgDxydlxqzuGbiUtLFmc0uN5HP aOwrRxJW+zVq+VC6qe4VKecOiv8m6UBdRDxNrXwAE0J03dv/J+g5gE9rHjrbJROJ B2kBT+s13dcR1h7etnOlXL7RwxYIywNPOg0AqMFsEvL0UbsDz60= =CRNV -----END PGP SIGNATURE----- --CkLQyaeIKf1Zy19b-- From owner-freebsd-current@freebsd.org Wed Nov 25 04:59:28 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 791AC47513C for ; Wed, 25 Nov 2020 04:59:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 4Cgpb3578mz4XgG for ; Wed, 25 Nov 2020 04:59:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x732.google.com with SMTP id q5so2212153qkc.12 for ; Tue, 24 Nov 2020 20:59:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=K48TESnQXWjdPU6hyW6OXao+bN8x1715DYe4STbf0ZQ=; b=B08D92uR95I2dj9PHz4hQbo8GBf32ur2xYwJPN0t/Uqf025H7QRTfXiIwDlZzaUWxt m6V5kiG5NaPqgqCvv2w1ztAqbhmu3x/c+/te+PRfNN0vOVqqnWTsvGowdS8NenoUF9La oLT72WYcBAU39rDHLRDLja0LXqPtZM6k4Hs0IO3nPq5rx/abp6T7Mlyqe1lGqGsaHC5z 9A1OiXRuM3E9qtyT443XdYzgr4GGllpP3C2DO5c6MfyOLIcMp04iy/PNldC+C4MBB9l3 d7dhZrz2STE2hGrDvDuqH2ItfcZKyU/JMhLkB41OoXbz7lAIOK7oUD31jozFegyq4UGs kE3g== X-Gm-Message-State: AOAM532SxT2JD+1Q3K8dTASqZmxKRf/AZxxd1b9WIuo2lH7OiZQcuekj luV6LY0MqPTI0g4b0mz47Jq6rbQp+Z7+DOHPTU5nfZGXgzM= X-Google-Smtp-Source: ABdhPJyz3WF2w3VF+QCU4S0BQC0iGvcETMB1dYOt6E3hxS9ihxO4ll6IB7fZaQN4j0E+TQQbt7xGnjTLYiQeqxd3Tzg= X-Received: by 2002:ae9:f311:: with SMTP id p17mr1730437qkg.206.1606280366445; Tue, 24 Nov 2020 20:59:26 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Tue, 24 Nov 2020 21:59:15 -0700 Message-ID: Subject: Re: git tools for building in base? To: FreeBSD Current X-Rspamd-Queue-Id: 4Cgpb3578mz4XgG X-Spamd-Bar: - X-Spamd-Result: default: False [-1.98 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::732:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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)[bsdimp.com]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::732:from:127.0.2.255]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-0.99)[-0.987]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::732:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 04:59:28 -0000 On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote: > As subject - what will there be in base to interact with the new git repo? > I mean, right now, for svn there is svnlite. What for git? > 'pkg add git' is your choice now. > Shouldn't it be in base before the move to git? > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't quite there yet, however, so it's not in base. When we migrated from CVS to Subversion, we didn't grow svnlite in the base for many months after the conversion. We hope to have it finished in time for 13.0. Warner From owner-freebsd-current@freebsd.org Wed Nov 25 05:53:56 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0B21F477701 for ; Wed, 25 Nov 2020 05:53:56 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from p-impout005.msg.pkvw.co.charter.net (p-impout005aa.msg.pkvw.co.charter.net [47.43.26.136]) (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 4Cgqnv17RQz4bsq for ; Wed, 25 Nov 2020 05:53:54 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.177.163]) by cmsmtp with ESMTP id hnYckuVZAhO0AhnYdkvxpe; Wed, 25 Nov 2020 05:41:35 +0000 X-Authority-Analysis: v=2.3 cv=e/Z4tph/ c=1 sm=1 tr=0 a=xqrt2BZAGHte7XHhrxJgbA==:117 a=xqrt2BZAGHte7XHhrxJgbA==:17 a=HpEJnUlJZJkA:10 a=DBwwDor5xuMA:10 a=eczb3fP_mknLTsj4ceoA:9 a=pHzHmUro8NiASowvMSCR:22 a=Ew2E2A-JSTLzCXPT_086:22 From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: git tools for building in base? References: Mail-Followup-To: freebsd-current@freebsd.org X-CMAE-Envelope: MS4wfHv1kxHiYRf4dEyIy7axjuh5lS66g39UUT4cA/LQAHwqna9B0sz5FWTMydpIPz6I8bZP/kg9hrIkKlIjsmWsLIdN7WhVc20dpifqsoMX56Dj3iX1/oDk kbUrQgLzBxGME4LJ3ndXmO6EoQ2YN5deev4ZZ9FaOqGPomVBQLbCnMZp X-Rspamd-Queue-Id: 4Cgqnv17RQz4bsq X-Spamd-Bar: +++++++ X-Spamd-Result: default: False [7.11 / 15.00]; FREEMAIL_FROM(0.00)[twc.com]; MISSING_DATE(1.00)[]; TO_DN_NONE(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:47.43.26.0/24]; RECEIVED_SPAMHAUS_PBL(0.00)[96.28.177.163:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[47.43.26.136:from]; ASN(0.00)[asn:40294, ipnet:47.43.24.0/21, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.91)[0.912]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[twc.com]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[47.43.26.136:from:127.0.2.255]; MISSING_MID(2.50)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_COUNT_TWO(0.00)[2]; GREYLIST(0.00)[pass,body]; MAILMAN_DEST(0.00)[freebsd-current] X-Spam: Yes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Wed, 25 Nov 2020 05:53:56 -0000 X-List-Received-Date: Wed, 25 Nov 2020 05:53:56 -0000 from tech-lists: > As subject - what will there be in base to interact with the new git repo? > I mean, right now, for svn there is svnlite. What for git? > Shouldn't it be in base before the move to git? Good question, and I hope the developers and others in charge are reading your post. You could be sure to have the ports tree downloaded and in place, ready for action to build and install git if you haven't already. They (ports tree) will stay on svn for some time after freebsd-current switches to git. I am not sure if there is or will be a lite version of git. Current could add this if feasible at any time, but stable and release might not be able to do this between releases (security update?). NetBSD users face a similar problem with their upcoming switch from cvs to hg (Mercurial). Tom From owner-freebsd-current@freebsd.org Wed Nov 25 11:12:45 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3188047DE7D for ; Wed, 25 Nov 2020 11:12:45 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward501j.mail.yandex.net (forward501j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::111]) (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 4Cgysl6lPPz4tJW for ; Wed, 25 Nov 2020 11:12:43 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mxback18j.mail.yandex.net (mxback18j.mail.yandex.net [IPv6:2a02:6b8:c04:106:0:640:832a:56af]) by forward501j.mail.yandex.net (Yandex) with ESMTP id AAE1133800BF; Wed, 25 Nov 2020 14:12:38 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback18j.mail.yandex.net (mxback/Yandex) with ESMTP id 5XOtOb0qYj-CcpuuuwF; Wed, 25 Nov 2020 14:12:38 +0300 Received: by myt6-7b46a58f2373.qloud-c.yandex.net with HTTP; Wed, 25 Nov 2020 14:12:37 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Guy Yur , "freebsd-current@freebsd.org" In-Reply-To: <9b1bb259-1307-7776-cc0b-e7a8eced6ac3@gmail.com> References: <9b1bb259-1307-7776-cc0b-e7a8eced6ac3@gmail.com> Subject: Re: adding existing ipv6 network route returns ENOMEM instead of EEXIST if loopback route also exists MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 25 Nov 2020 11:12:37 +0000 Message-Id: <4229351606302594@mail.yandex.ru> Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Rspamd-Queue-Id: 4Cgysl6lPPz4tJW X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0::/52]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[ipfw.ru:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FORGED_SENDER(0.30)[melifaro@freebsd.org,melifaro@ipfw.ru]; RCVD_IN_DNSWL_LOW(-0.10)[2a02:6b8:0:801:2::111:from]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a02:6b8:0:801:2::111:from]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[melifaro@freebsd.org,melifaro@ipfw.ru]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[ipfw.ru:s=mail]; FREEFALL_USER(0.00)[melifaro]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; SPAMHAUS_ZRD(0.00)[2a02:6b8:0:801:2::111:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 11:12:45 -0000 21.11.2020, 22:48, "Guy Yur" : > Hi, > > When adding a route with a netmask, add_route() in route_ctl.c > adds the route with destination address masked. > If the add failed (for example, the route exists) it calls > lookup_prefix() with the original unmasked destination. Thank you for the report! Indeed, there is a problem w.r.t non-masked dst handling. I'll look into that in the end of this week. > > In a scenario where a loopback route was added followed > by the network route being added, if the network route > is added again and the network route destination is the > same as the loopback route, lookup_prefix() will match on > the loopback route, not finding the network route and > add_route() will return ENOMEM instead of EEXIST. > Adding the route with just the network part returns EEXIST as expected. > > Example: > # route -6 add -host fd53::1111 -prefixlen 128 ::1 > # route -6 add -net fd53::1111 -prefixlen 64 ::1 > # route -6 add -net fd53::1111 -prefixlen 64 ::1 > route: writing to routing socket: Cannot allocate memory > add net fd53::1111: gateway ::1 fib 0: Cannot allocate memory > # route -6 add -net fd53:: -prefixlen 64 ::1 > add net fd53::: gateway ::1 fib 0: route already in table > > I was testing https://reviews.freebsd.org/D15406 > changes applied to r367863. > The changes call rtinit to add prefix route when > interface address is added/updated and uses the > interface address as the destination. > rtinit returned ENOMEM instead of EEXIST > causing dhcpcd to printCannot allocate memory. > > route commands above showing the problem were run > in r367863 without D15406 changesas well. > > Thanks, > Guy Yur > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Nov 25 13:16:03 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EE7BE469B20 for ; Wed, 25 Nov 2020 13:16:03 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 4Ch1c24FRnz3H2B for ; Wed, 25 Nov 2020 13:16:02 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 893A6C15 for ; Wed, 25 Nov 2020 08:16:00 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 25 Nov 2020 08:16:00 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehtddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurddutddu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtg hhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id B284A328005A for ; Wed, 25 Nov 2020 08:15:59 -0500 (EST) Date: Wed, 25 Nov 2020 13:15:58 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: git tools for building in base? Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="g99HmVnPWfOMvg/t" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Ch1c24FRnz3H2B X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[64.147.123.24:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; MIME_GOOD(-0.20)[multipart/signed,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)[4]; DMARC_NA(0.00)[zyxst.net]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 13:16:04 -0000 --g99HmVnPWfOMvg/t Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: >On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote: > >> As subject - what will there be in base to interact with the new git rep= o? >> I mean, right now, for svn there is svnlite. What for git? >> >'pkg add git' is your choice now. > >> Shouldn't it be in base before the move to git? > >We will have got (from OpenBSD: Game Of Trees) in the future. It isn't >quite there yet, however, so it's not in base.=20 Do you agree that this situation is a bad look for an *operating system* ? Having to depend on a third-party tool to stay up-to-date and secure. In multiple locations it is said that installing a port is *at your own=20 risk*. Personally, I'd like the official updating tool to have had the=20 same level of analysis (and so the same level of "risk") on it as the base = OS,=20 (and also be under the same licence). I mean, shouldn't all the basic tools be present in an OS, at least in=20 order to update it? And *then* migrate to the update method? >When we migrated from CVS to Subversion, we didn't grow svnlite in=20 >the base for many months after the conversion. A mistake then and a mistake now with svn to git IMO. --=20 J. --g99HmVnPWfOMvg/t Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl++WQQACgkQs8o7QhFz NAXz0Q//TTLfDe4CKPH/W3w8WSGMlkufuR1dR/CfBNMns9T3rMxWFW+qbctR3d4B YdfGyhDHYP00e3haoX2SwfYXWYv/5gnbc9X6gReLLwkk16weqfWUwR7/oNaMGZo8 jbT+VsQxUmM7gMqUauNGnN1Lw4fCcl2CWA/QrrgPe7phACFnT+8ED5SiIff6ab/V 9k20tlETVITIZ13A7BsbLLjHLvUs5vHhbCEj2jvnj6c/5kFf4KyR+SsRqbdW2LoH nId7kLQBKgXfyY+b0ES1yfM6jAJ4XdEmgVRbGldt1XDti8BYaYy737ZZjQY8Obms CoVqtoGaZvCKyryGhBCXD7bWzKTKxoAl6JhN1b4pjhbOtPY8m4aTI5iTXJgh2j5F pTWQZXDAnjqq4tnvfmX7Qjygyv8nQ7TpKDUmFQ1bh5RiHpopoYvfLH5KXluC017B UVSdasSg9YTvGSVNuC7kalPdgRlGNA2PE5lSkfOtKQKx3N6vZLYzwKjitmxb2DxR ZORXi2nS5r/kMRNm5v+69q01F/pdFM68IOhvvo0akAw9d4FaG8zQscVqv17tckTD Aq8/DrORDik8n6v3zRntPco2mrWv0oUwSs3BQ7+9KCJ/ufXcEcoOdg7tkx3m3Hja dBWUR3CDNEEp4LZVsjw+0UhdRjz+cobXgJFipAuT1xwUriXaI0U= =NXGQ -----END PGP SIGNATURE----- --g99HmVnPWfOMvg/t-- From owner-freebsd-current@freebsd.org Wed Nov 25 15:00:53 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 30CB246BD49 for ; Wed, 25 Nov 2020 15:00:53 +0000 (UTC) (envelope-from bapt@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ch3x110gQz3NB9; Wed, 25 Nov 2020 15:00:53 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from ivaldir.etoilebsd.net (etoilebsd.net [178.32.217.76]) (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 F114B7ADF; Wed, 25 Nov 2020 15:00:52 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by ivaldir.etoilebsd.net (Postfix, from userid 1001) id F22E2EACDD; Wed, 25 Nov 2020 16:00:50 +0100 (CET) Date: Wed, 25 Nov 2020 16:00:50 +0100 From: Baptiste Daroussin To: Warner Losh Cc: FreeBSD Current Subject: Re: git tools for building in base? Message-ID: <20201125150050.bz62hatil6sbhdwn@ivaldir.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kk7yk32gsw4hup6b" Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 15:00:53 -0000 --kk7yk32gsw4hup6b Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote: >=20 > > As subject - what will there be in base to interact with the new git re= po? > > I mean, right now, for svn there is svnlite. What for git? > > >=20 > 'pkg add git' is your choice now. pkg install not pkg add >=20 >=20 > > Shouldn't it be in base before the move to git? > > >=20 > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't > quite there yet, however, so it's not in base. When we migrated from CVS = to > Subversion, we didn't grow svnlite in the base for many months after the > conversion. We hope to have it finished in time for 13.0. >=20 > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --kk7yk32gsw4hup6b Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAl++caAACgkQY4mL3PG3 Plomag//cKB1hlEKPCuOgt8o5Ir7RLfe0lvvmpBuRfg9pS9HfVW8IIwft8gC3I6C 2edvzEKjXjxYr7EcHyib2aplgA7tIFw1RP8dKV60CMqc+VMsrN/bAb/l9a+N0sgi BRnatupOY8fQgrPzhsFF9gcYNKqPL4QB6FE3q1RIqv6Qpmp1bNYhs7FVLOOYKi3K i32PQGwv+FvcaCZ/DzkzVMgAvwDJoGMZSvChEzr9EM5NCIHERLvuQYaxBT35N4ix iZlNcpACq8jAehbGCQg1rcs+Y7FcWyUjeeWxZF4LXf7ujADR784QkOL0xth6uPpc pGWiILvVAU4EBrQRXlcd05JUTIJDQ4EN9sTGg7lT8VqADYIx/RJuyV17K7mEbSEJ MIgIwlkr3Nza5AhULHc+yBsYRdQEUontHNShpi0S/A3wTQbCNjoHrKBARx9p5Rl8 PRUVQ5oABwJntcpfMm52gWKmtN38lsism7lXq5s/5vOA5ubXj3A6Ygk65d/0cjZB +cbJGC+GphW4zJUzYcol8AvhDvZq1sjQVlYognCXvwYwvooP3sidIo4e8XDt9Q5I 4XUnl/QdvsnPTQomwnbDj+PgPvbuqxAk4ghvqnCYHhLqNh2VTu8eAaBJ4mcUGSUw ObAEghxzPSh0+Cy9+tgSxRyR/aCl8e8galusaWxZ76fA8WoZL1M= =Id8c -----END PGP SIGNATURE----- --kk7yk32gsw4hup6b-- From owner-freebsd-current@freebsd.org Wed Nov 25 15:05:50 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6A15D46C176 for ; Wed, 25 Nov 2020 15:05:50 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 4Ch42k2K0vz3NXt for ; Wed, 25 Nov 2020 15:05:50 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qk1-x72e.google.com with SMTP id v143so4963764qkb.2 for ; Wed, 25 Nov 2020 07:05:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=7SWHFxXw1fJ+JF4MLUiSoBczZDQd9kjHVKpi/DbaOfI=; b=tepQnP+2g7/SEo0FP8zhK70N30/MJVcUuN6cqUKox4+qNUD7Cp+XXOEchLRDH6+U2P BZqoX6gtq3Z7MK/k1h0fiuh7aQrfJXdSjgFRgX2rB7VTnkRBY0KtOj4Sc5KVEiQVoQ5D TqiEiDoE5p8SI6X2M1ghlioK73dKZovpJ5M/rEFqD3YJ4onhaGzYf3cV59nzV9CuwtUh uCwbwuyVhQJKGO35I+2tmgxe/KxWgCOd1gIrPyvpN/pvn09y38stmjxPmeWOV1xSOrCK bvqACrstEpmYbZExedZGZNbhoobjNQ5D3nkRdj95D0A8ohZpt5iYd9xnTenh8UMrSvax sArA== X-Gm-Message-State: AOAM531QLFS3PO8IPni8TfiXaXgU6xErwwMHlAS1rPA01HvvkVI3lCu6 rg0Fje5S8289xNJqvuM0L/O6uA== X-Google-Smtp-Source: ABdhPJzNfsqMF/eYuRrlcvtouJJoZSFpIgQ6FforvCJtLExNM+rllhlhj7wNIfpSA/s0jb9/Xhhwqg== X-Received: by 2002:a05:620a:88e:: with SMTP id b14mr3782106qka.434.1606316749506; Wed, 25 Nov 2020 07:05:49 -0800 (PST) Received: from mutt-hbsd (pool-100-16-222-53.bltmmd.fios.verizon.net. [100.16.222.53]) by smtp.gmail.com with ESMTPSA id z23sm2541184qtq.66.2020.11.25.07.05.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Nov 2020 07:05:48 -0800 (PST) Date: Wed, 25 Nov 2020 10:05:48 -0500 From: Shawn Webb To: Baptiste Daroussin Cc: Warner Losh , FreeBSD Current Subject: Re: git tools for building in base? Message-ID: <20201125150548.vkqgtlqnawgwujbn@mutt-hbsd> X-Operating-System: FreeBSD mutt-hbsd 13.0-CURRENT-HBSD FreeBSD 13.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xFF2E67A277F8E1FA References: <20201125150050.bz62hatil6sbhdwn@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dcdzsxpdt2tnhx4x" Content-Disposition: inline In-Reply-To: <20201125150050.bz62hatil6sbhdwn@ivaldir.net> X-Rspamd-Queue-Id: 4Ch42k2K0vz3NXt X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 15:05:50 -0000 --dcdzsxpdt2tnhx4x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 25, 2020 at 04:00:50PM +0100, Baptiste Daroussin wrote: > On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > > On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote: > >=20 > > > As subject - what will there be in base to interact with the new git = repo? > > > I mean, right now, for svn there is svnlite. What for git? > > > > >=20 > > 'pkg add git' is your choice now. >=20 > pkg install not pkg add There's also fetch for a one-time download of the ports tree (bootstrapping ports, for example). A HardenedBSD user would do this: fetch -o ports.tar.gz \ https://git-01.md.hardenedbsd.org/HardenedBSD/hardenedbsd-ports/archive= /master.tar.gz mkdir -p /usr/ports tar -xf ports.tar.gz --strip-components 1 -C /usr/ports Something similar could be done in FreeBSDlandia. Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 https://git-01.md.hardenedbsd.org/HardenedBSD/pubkeys/src/branch/master/Sha= wn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --dcdzsxpdt2tnhx4x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAl++cskACgkQ/y5nonf4 4fpLwRAAiQ95LEaEN4gEM5impEDeR+FTPkHVXuYZ9mqa9znGDg5SHYOxD0/gVQc+ M+Za/32/EDbfiYjCsWnjTReYkyn6Wc7QPhs33ZheXTgGQAkicz3FOBor/chTDWNY wIcWJ9JIvGCUY4cjJvVWYwzxBZwFNzD+GWhGiGjnQlKx9WDK+gSD/lhBsplZOcSv cS7P+9jE+5EXnT+m4XBrBFrtq8p+GS+hE8SWsn4u0B2DilS0HkXPLALIT/pNM+ut BoJOcVkepW27aJCrmX6Jz1h83U5GDRLTHvoNsoGbNnWfgYCbcy9l3UQvW9Nc/0DK jtPLwv6B3jUMX4gJiEZ8l4kELnpQ1wD7WwjzKLF9/yQvuiCOdDqJLMlwgyu3hy03 5zJV82hTw5SvhdmFq96M977SRTzwBfXFxCtJMqBPHTwDOfXbmY4W2YNhL+ZsGOIy tT2Fkep3DgrEC0TeSy3t9F6C8ZwzoAxx8PeI7V/LvDgppWC8hsSMK0wq8IDT0+Xb tfR9LB/WXHLlbOVtxgnjKhkaywG6EF0Y6456DxDHXtzKhwVykZW/BIgsoEWavWrF ozlCECOMK9tAzfKzJPEM1tiKZ0Zu8TD2SDCLunzw07+TPgTSH+UCEFXYLqnX1iwX VHqWuHW14p/bBGCFFDn4qRUd/FVIn2eh/PWmxS2eminnqCvrYYg= =COxO -----END PGP SIGNATURE----- --dcdzsxpdt2tnhx4x-- From owner-freebsd-current@freebsd.org Wed Nov 25 15:09:26 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C13AF46C5FC for ; Wed, 25 Nov 2020 15:09:26 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ch46t12tbz3P95 for ; Wed, 25 Nov 2020 15:09:25 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id E968117099; Wed, 25 Nov 2020 15:09:24 +0000 (UTC) Date: Wed, 25 Nov 2020 15:09:23 +0000 From: Mark Linimon To: Warner Losh Cc: FreeBSD Current Subject: Re: git tools for building in base? Message-ID: <20201125150923.GA10797@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 4Ch46t12tbz3P95 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_LOW(-0.10)[18.222.6.11:from]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[18.222.6.11:from]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[linimon]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[18.222.6.11:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 15:09:26 -0000 On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > We hope to have it finished in time for 13.0. I also feel that it should be more a "requirement". I don't see the rush in getting 13.0 out the door. There is a lot to get working (especially in ports-land). mcl From owner-freebsd-current@freebsd.org Wed Nov 25 16:25:17 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A700046E34C for ; Wed, 25 Nov 2020 16:25:17 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (mail.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ch5pN2mW3z3jZr for ; Wed, 25 Nov 2020 16:25:16 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1khxbO-008Y7t-R4; Wed, 25 Nov 2020 17:25:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.16.1/8.16.1) with ESMTP id 0APGNolF031877 for ; Wed, 25 Nov 2020 17:23:50 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.16.1/8.16.1/Submit) id 0APGNogn031876 for freebsd-current@freebsd.org; Wed, 25 Nov 2020 17:23:50 +0100 (CET) (envelope-from news) To: freebsd-current@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.current Subject: Re: git tools for building in base? Date: Wed, 25 Nov 2020 16:23:50 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (FreeBSD) X-Rspamd-Queue-Id: 4Ch5pN2mW3z3jZr X-Spamd-Bar: / X-Spamd-Result: default: False [-0.80 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[news]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a04:c9c7:0:1073:217:a4ff:fe3b:e77c:from]; 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)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a04:c9c7:0:1073:217:a4ff:fe3b:e77c:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[inka.de]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[naddy@mips.inka.de,news@mips.inka.de]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:202113, ipnet:2a04:c9c7::/32, country:DE]; FROM_NEQ_ENVFROM(0.00)[naddy@mips.inka.de,news@mips.inka.de]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 16:25:17 -0000 On 2020-11-25, Warner Losh wrote: >> Shouldn't it be in base before the move to git? > > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't > quite there yet, however, so it's not in base. Since got can't fetch from http(s) yet, there was talk of setting up anon-ssh access. What became of that? devel/got, for those who want to play. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-current@freebsd.org Wed Nov 25 17:35:25 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6D27246FD66 for ; Wed, 25 Nov 2020 17:35:25 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 4Ch7MJ2mmXz3nYs for ; Wed, 25 Nov 2020 17:35:24 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id p22so2700743wmg.3 for ; Wed, 25 Nov 2020 09:35:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ccwhWA+1gEZ9IObMWH75frJweU99QCUy+daPEG1xdOY=; b=qNA6V4rFWN2fkJsqUEoFtvnjhbw7wIdO77+dBWCXNd09+liDEgnM6QIzMPiXtbUcFV Pqe6+8yDCx3dP0A4BNF9VKiL0OrlTQRBf4ihiX4G9sa6+sPxSBZHl/Y0zLZWzMuH5dAa wnicvqfZn8Erq5bhQIQV0GVXRu1LsYadelIEE5KJAW0/JicRPzw7Ng7L3ZYiB6bhNwmd NQDle/RzJdw9QxsDgpt+tIrEL1ycxoUpraeDpLK3pM5udvhuPPTLDc5w2EDLOtn/WBFK 6J/oXycT+rfBUS26FkBE+q9Z7c5HVSmFvf+2CH5pR1N4ri3iWUnvd3kcqbBWIiR6UAsT kOrA== X-Gm-Message-State: AOAM533/DO8AR+rfa4DnBQtQgPuLiZHw+VJ83Ag/897RYgDAV7dNPHD8 YU2gPEf9Fz+ire8xL3tT7we2lidUPmw= X-Google-Smtp-Source: ABdhPJy7DlEmHONucqR3XQl068UhWA12S8EQTYAv4h5kZpIAcdZjgcdPUudxOlwXtxyl0SQD4mwxyw== X-Received: by 2002:a1c:a185:: with SMTP id k127mr5204650wme.23.1606325722320; Wed, 25 Nov 2020 09:35:22 -0800 (PST) Received: from [192.168.1.11] (79-66-147-78.dynamic.dsl.as9105.com. [79.66.147.78]) by smtp.gmail.com with ESMTPSA id k1sm5560182wrp.23.2020.11.25.09.35.21 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 Nov 2020 09:35:21 -0800 (PST) Subject: zpool export: umount failed, device inexplicably busy (lsof found nothing) From: Graham Perrin To: freebsd-current@freebsd.org References: <4125dad7-b1ea-bf20-4996-6a138ff202eb@gmail.com> Message-ID: Date: Wed, 25 Nov 2020 17:35:20 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <4125dad7-b1ea-bf20-4996-6a138ff202eb@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4Ch7MJ2mmXz3nYs X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; 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)[79.66.147.78:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32c:from]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32c:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32c:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 17:35:25 -0000 On 11/10/2020 11:21, Graham Perrin wrote: > > On 06/10/2020 21:29, Graham Perrin wrote: >> lsof finds no open file. >> >> How else might I tell why the device is busy? >> >> Mobile hard disk drive, USB. > > The same problem this morning, > > ---- > > root@momh167-gjp4-8570p:~ # zpool export Transcend > cannot unmount '/Volumes/t500': umount failed > root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/ > lsof: WARNING: device cache mismatch: /dev/usb/0.5.2 > lsof: WARNING: /root/.lsof_momh167-gjp4-8570p was updated. > root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/ > root@momh167-gjp4-8570p:~ # usbconfig -d 0.5 dump_all_desc > ugen0.5: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) > pwr=SAVE (0mA) > >   bLength = 0x0012 >   bDescriptorType = 0x0001 >   bcdUSB = 0x0300 >   bDeviceClass = 0x0009  >   bDeviceSubClass = 0x0000 >   bDeviceProtocol = 0x0003 >   bMaxPacketSize0 = 0x0009 >   idVendor = 0x0424 >   idProduct = 0x5434 >   bcdDevice = 0x3082 >   iManufacturer = 0x0002  >   iProduct = 0x0003  >   iSerialNumber = 0x0001  <1239567> >   bNumConfigurations = 0x0001 > >  Configuration index 0 > >     bLength = 0x0009 >     bDescriptorType = 0x0002 >     wTotalLength = 0x001f >     bNumInterfaces = 0x0001 >     bConfigurationValue = 0x0001 >     iConfiguration = 0x0000  >     bmAttributes = 0x00e0 >     bMaxPower = 0x0000 > >     Interface 0 >       bLength = 0x0009 >       bDescriptorType = 0x0004 >       bInterfaceNumber = 0x0000 >       bAlternateSetting = 0x0000 >       bNumEndpoints = 0x0001 >       bInterfaceClass = 0x0009  >       bInterfaceSubClass = 0x0000 >       bInterfaceProtocol = 0x0000 >       iInterface = 0x0000  > >      Endpoint 0 >         bLength = 0x0007 >         bDescriptorType = 0x0005 >         bEndpointAddress = 0x0081  >         bmAttributes = 0x0013  >         wMaxPacketSize = 0x0002 >         bInterval = 0x0008 >         bRefresh = 0x0000 >         bSynchAddress = 0x0000 > >       Additional Descriptor > >       bLength = 0x06 >       bDescriptorType = 0x30 >       bDescriptorSubType = 0x00 >        RAW dump: >        0x00 | 0x06, 0x30, 0x00, 0x00, 0x02, 0x00 > > > > > root@momh167-gjp4-8570p:~ # zpool export Transcend > cannot unmount '/Volumes/t500': umount failed > root@momh167-gjp4-8570p:~ # umount /Volumes/t500 > umount: unmount of /Volumes/t500 failed: Device busy > root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/ > root@momh167-gjp4-8570p:~ # > > ---- > > When this last occurred, I could export the pool after signing out > from KDE. > The problem seemed to be consistently reproducible but (fingers crossed) no problem yesterday or today. Previously: most often using OpenZFS in base. Now using OpenZFS from ports, with r367936. If the problem recurs: is it _ever_ sane to get nothing listed by lsof for a volume that can not be unmounted? From owner-freebsd-current@freebsd.org Wed Nov 25 18:19:29 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 30BBE470971 for ; Wed, 25 Nov 2020 18:19:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x844.google.com (mail-qt1-x844.google.com [IPv6:2607:f8b0:4864:20::844]) (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 4Ch8L83sshz3qdR for ; Wed, 25 Nov 2020 18:19:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x844.google.com with SMTP id l7so2257496qtp.8 for ; Wed, 25 Nov 2020 10:19:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yyGJs/p60y0jM0bEebOqG86Bul/BP2Bg64Le3t2CVFI=; b=YEuvmITblNiiG24JSNdLsM7WLRmJTl2gqXqYcBXq8BprtUEfi+aNo+jr1vyF5kTNyJ um0XAC1wLR5uZbnOOIFpfn/0fQbpwsQOQ7GlrR8pWU/jmos0sO5DCT9Nu92lov7ZJXr/ 7/e3l1UFjXsmE2X6RhqwaOJEtbxUr8TbwpUvgSxQpjhlrszkGLztsY50s0yzvKr3Jd8D vH9NcrbLXuzcoJetZDmcpE19WdZEAAj9u0C9Llsza1ng0FKSMODv1FdvsVyDuVkRtQdh W53PqPG1mveCNfGpogeSPLxL92+LUNUxGe4oEpSdbmxZA9LM68NZM8ertTn5+0VQelDl 4slQ== X-Gm-Message-State: AOAM533mhSZofKigSYTymWCMp/L2lae8mw5iVX+Btv0as7xWlei432F5 ASMvSPGORYdjDoepgTpe96G1mZl9nsvyuKF69SuuCythzB1eRQ== X-Google-Smtp-Source: ABdhPJxqfs9dPHfgLQb+scmqexUer97tU++4ggVcYZ0j6a3e6cltdgSYpVKedlWG/mmKDFXjrj1gsmg1fHlzbaTHa+Q= X-Received: by 2002:ac8:7619:: with SMTP id t25mr136468qtq.244.1606328367341; Wed, 25 Nov 2020 10:19:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Wed, 25 Nov 2020 11:19:16 -0700 Message-ID: Subject: Re: git tools for building in base? To: FreeBSD Current X-Rspamd-Queue-Id: 4Ch8L83sshz3qdR X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::844:from]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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)[bsdimp.com]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::844:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::844:from]; NEURAL_SPAM_SHORT(1.00)[1.000]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 18:19:29 -0000 On Wed, Nov 25, 2020 at 6:16 AM tech-lists wrote: > Hi, > > On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > >On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote: > > > >> As subject - what will there be in base to interact with the new git > repo? > >> I mean, right now, for svn there is svnlite. What for git? > >> > >'pkg add git' is your choice now. > > > >> Shouldn't it be in base before the move to git? > > > >We will have got (from OpenBSD: Game Of Trees) in the future. It isn't > >quite there yet, however, so it's not in base. > > Do you agree that this situation is a bad look for an *operating system* ? > Having to depend on a third-party tool to stay up-to-date and secure. > In the long term, perhaps. During a short-term transition, it seems acceptable. > In multiple locations it is said that installing a port is *at your own > risk*. Personally, I'd like the official updating tool to have had the > same level of analysis (and so the same level of "risk") on it as the base > OS, > (and also be under the same licence). > You can establish your own chain of trust to the sources, you can start here https://mirrors.edge.kernel.org/pub/software/scm/git/ if building from ports or installing a package is deemed to be too insecure. > I mean, shouldn't all the basic tools be present in an OS, at least in > order to update it? And *then* migrate to the update method? > git is a perfectly fine tool. Moving to git has a number of advantages to the project, so we must weigh the many different factors in doing that and not let a single item gate the entire process if that single item doesn't add enough value. -current is for bleeding edge users, and the cost / benefit analysis is skewed heavily towards the convenience of the developers when a choice needs to be made. In this case, the choice was made to progress with the cutover of the repo while allowing the natural development of got to proceed in parallel. One way to help this situation would be to contribute code to OpenBSD's got to help it mature to the point we can include it in the base system. There's logistical issues as well: today got only clones via ssh, and the typical distribution of git is via the git or https protocols (though developers often push commits via ssh). To overcome these limitations, we'd have to stand up additional infrastructure to allow for anonymous ssh into mirrors. This is in the planning stages, but is taking a back seat at the moment to getting the basic infrastructure up and running. > >When we migrated from CVS to Subversion, we didn't grow svnlite in > >the base for many months after the conversion. > > A mistake then and a mistake now with svn to git IMO. It wasn't considered a mistake at the time, nor do I consider this a mistake now. At the time Peter Wemm did the cutover, moving to a SCM that had atomic commits was considered a higher priority than necessarily needing svn in the base system. So our adaptation of svn back in the day proceeded in parallel with a repackaging of svn to allow a minimal version to be included with the base system. Warner From owner-freebsd-current@freebsd.org Wed Nov 25 18:20:59 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8109347112F for ; Wed, 25 Nov 2020 18:20:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 4Ch8Mt44cTz3qql for ; Wed, 25 Nov 2020 18:20:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x736.google.com with SMTP id h20so5617577qkk.4 for ; Wed, 25 Nov 2020 10:20:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sdTsIXvr9CWvPeMYwYpeQ9vWEYyQ1sJ5AtClY9fjbD0=; b=YMvOhYqKou4ezIDMGpl5ggj9avvUYXfCBkaU09CcFO7XdEUj9H+nhZFnU920qbWmfQ r+NAjDu14IgWS3bu2AEDlLwoXgQPy7qNPCqPAU6j6S1c7XnXlx8Um2QlaG2Rz+IITgnE r994XC0MLO8BeEjae5WN/2f/3q60iiGjw0h0/hGZSml2jUKGhiMyGG9m0K4AdLz5shUx bZO2tHlhLh9Bu+dOa2FBHV43mZGN+8eQFVg2Pj9poWzwPTTaPI/IMw8zm8NAN2q3yOUh PzwqUc+Q5mjptmNErshXx1ptzwv9RSdyHQJOfjmzz50V2kHIqxjWyhDQuiZqEHffwEkK ABWg== X-Gm-Message-State: AOAM530Mg7uTq3TUvFszHG55dfOAfR4Z5oD9MOgqvo82XZRoGifMdrWC mm5sBFVUM4548FSbcYJWjM0E6X/pnQ0oh770jR4WDRlCJkg= X-Google-Smtp-Source: ABdhPJy87f7sE/une1o1LGJmA9OCZ0T7EPgNdmLVYLW0zgXP2Gh8yf3XzRgwQNQ6btc6jxQS8WhBZ0w+8aOgeRFjF5M= X-Received: by 2002:a37:9b01:: with SMTP id d1mr121906qke.89.1606328457512; Wed, 25 Nov 2020 10:20:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Wed, 25 Nov 2020 11:20:46 -0700 Message-ID: Subject: Re: git tools for building in base? To: Christian Weisgerber Cc: FreeBSD Current X-Rspamd-Queue-Id: 4Ch8Mt44cTz3qql X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::736:from]; NEURAL_SPAM_SHORT(1.00)[1.000]; 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)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::736:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::736:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 18:20:59 -0000 On Wed, Nov 25, 2020 at 9:25 AM Christian Weisgerber wrote: > On 2020-11-25, Warner Losh wrote: > > >> Shouldn't it be in base before the move to git? > > > > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't > > quite there yet, however, so it's not in base. > > Since got can't fetch from http(s) yet, there was talk of setting > up anon-ssh access. What became of that? > It's on the list, but at a lower priority than getting the basics in place. > devel/got, for those who want to play. > Yes. You can also play with the github FreeBSD mirror via ssh, but you have to create an account. Warner From owner-freebsd-current@freebsd.org Wed Nov 25 18:22:44 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4D680471607 for ; Wed, 25 Nov 2020 18:22:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (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 4Ch8Pv4HYtz3r3Y for ; Wed, 25 Nov 2020 18:22:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf2e.google.com with SMTP id ek7so1382023qvb.6 for ; Wed, 25 Nov 2020 10:22:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6vGyrZpS1GRZPOXalGbo33iJKPCdYTKSw63QK5HSav4=; b=qj0SLCVS4BqhEesA2Ts2wiI4Zavk5u3o4W9pe813v0qcj9pbw+ZX9OgnsJ7chW8cot 3i2My40+RN/+3n3Prtdsunvv3UrJeEH+BJC57W/dNUBJNzqe1KDh77y/TnieWQ9JmKTY ldkxGVFxjGYG5m2TN+lt8bynT0LixDnGb5tSs1Y+crKbc9b5BzbKW7HfAEmJRTAk4Cw2 XuXbjT+/ZtH8UKMl9n0Fj8jGisjG/p/cVfbmdDvaKAGQuEjY7Q2ZlIDA1lSj9EnkYa3c RpQFFSmAhX0Rimp6QoFKFa8IFL4n/QIeNTdFrTAx+2Genjis0RjXgl3AMB/jfxmgPyYw PUsw== X-Gm-Message-State: AOAM530tGwQf4VZFnbJTKMkViDRFrlp1CzX+QzoOWAEfF0PfQS1qIw6f mwHBHjsiwBfXRbRya7TsdCorFoAgw/0N95JpxOnx7Sn47kA= X-Google-Smtp-Source: ABdhPJwlSatYrkCXiRg/XURqzV3HpOaeRBLii5QquhfNCTX+JJzQtGy9YaAfCnlL/bVmh4o0RJ14XU6Ucy3XMIB7OKE= X-Received: by 2002:ad4:4e13:: with SMTP id dl19mr4821193qvb.24.1606328562414; Wed, 25 Nov 2020 10:22:42 -0800 (PST) MIME-Version: 1.0 References: <20201125150923.GA10797@lonesome.com> In-Reply-To: <20201125150923.GA10797@lonesome.com> From: Warner Losh Date: Wed, 25 Nov 2020 11:22:31 -0700 Message-ID: Subject: Re: git tools for building in base? To: Mark Linimon Cc: FreeBSD Current X-Rspamd-Queue-Id: 4Ch8Pv4HYtz3r3Y X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::f2e:from]; NEURAL_SPAM_SHORT(1.00)[1.000]; 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)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::f2e:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f2e:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Nov 2020 18:22:44 -0000 On Wed, Nov 25, 2020 at 8:09 AM Mark Linimon wrote: > On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote: > > We hope to have it finished in time for 13.0. > > I also feel that it should be more a "requirement". > > I don't see the rush in getting 13.0 out the door. There is a lot to > get working (especially in ports-land). > Without someone dedicated to make it happen, it can't be more than a 'hope to have it finished' item. Warner From owner-freebsd-current@freebsd.org Thu Nov 26 00:10:46 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 49ECF477C0E for ; Thu, 26 Nov 2020 00:10:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (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 4ChJ7T0RHkz4ds5 for ; Thu, 26 Nov 2020 00:10:44 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D497F1BA2 for ; Wed, 25 Nov 2020 19:10:42 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 25 Nov 2020 19:10:42 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehuddgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesghdtreertd dtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseiihiig shhtrdhnvghtqeenucggtffrrghtthgvrhhnpeevgffhffdtfeekleelhedtjeelvdfhvd egieejveffgfduvdfhteegjeeujeeuieenucfkphepkedvrdejtddrledurddutddunecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtghhqd hlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id E79133064AAA for ; Wed, 25 Nov 2020 19:10:41 -0500 (EST) Date: Thu, 26 Nov 2020 00:10:40 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: possible usb3-connected hard drive spin down causing lag Message-ID: Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oXU/D8KvidHymqLE" Content-Disposition: inline X-Rspamd-Queue-Id: 4ChJ7T0RHkz4ds5 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.19:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.19:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.19:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.19:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 00:10:46 -0000 --oXU/D8KvidHymqLE Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I have a usb3-connected harddrive. dmesg shows this: [...] da0: Fixed Direct Access SPC-4 SCSI device [...] running current-r367806-arm64 I think it might be auto-spinning-down or auto-sleeping. It's making initial interaction lag of 2-3 seconds. Is there a=20 sysctl or something somewhere where I can tell it to never=20 sleep? Or is that something I'd need to contact the=20 manufacturer about? Or is there an alternative strategy=20 like tmpfs. It's not a "green" drive but I guess it might be "green" in that it's usb3 powered. I have vfs.read_max=3D128 in /etc/sysctl.conf zdb has ashift=3D12 In case it's relevant, the filesystem on the disk is zfs. Once "woken up", inferaction is quick, as expected.=20 thanks, --=20 J. --oXU/D8KvidHymqLE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl++8nYACgkQs8o7QhFz NAXGCBAAn9ArO+8vJM7rPsUEm1wZQeYTI9Xdxe56hOj9/MyvhH/NvbgS6MQUL0J4 LhgXlZGtPWMIK4oucE8vWUn8mA7pXB5pdlxy0ZjJEvK8iFaHk+FUkg6S/S5cRX/L tSj4btKaPRedxDn7af8EMZkVKHuqWdCP1tpvKl5exacS7gSPDS4Q0RLjsYg8Asog K7ftK9jggoGnIK+Yiya+ovvbl07I/jrj9PKhGjhzOo3n/USfsEBdck6SuW4H9+Ct YZaVkN7IcIVWuLNSkNbyTm3GP53S+IIjqNiL29OXSdgAB52UZ2WNs6tDtGY93Ee/ 4xBKlsc10Sje4zL/hsRyaIyjlxsV5WKnuOGzX/iWoIwCCGbj23UDfnWZLQjQUAeg YkIPQax9UmZ1S6rJoQo269XHdyc31kModA1BvTKxYY2lfjxSkhmyLgRC30lLtz9w Pb/OmttarG+e5F4YkwEd6cGBon7Yvi9oty9DqVPCGOQ5swljSiYAJvqO6OETDVA5 Jv9G7IhXXp06LQhER4QGGl5n76+Fnxfvn11Wdt/sTKlXPpCLgyLe7jsUSQlRoUJd hEO4Ve5pB88rLt2/liF9Q4rCD59uXMnvZsjSQUrvB4OgGwnlS0a5FiUz6rO+2UdF T3VCxJaxUWiWHu33IhUlWfDWYYXwM0YVX0Dwo/AWCqXR+IBh9Uk= =pUhE -----END PGP SIGNATURE----- --oXU/D8KvidHymqLE-- From owner-freebsd-current@freebsd.org Thu Nov 26 08:07:33 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D14ED4A4C75 for ; Thu, 26 Nov 2020 08:07:33 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (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 4ChVjX2Yg8z3NjG for ; Thu, 26 Nov 2020 08:07:27 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x344.google.com with SMTP id d142so1225187wmd.4 for ; Thu, 26 Nov 2020 00:07:27 -0800 (PST) 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=fQfFWpjdcnYPSB8ASjolOjxjZf5tCAEPXLDnvXzBVE8=; b=RPk5qPnd3y2GLtf7l/4W/a2FwWDN/ifhuiOZwO7xvJOFlOcbIfRuFA1oPnl+Vd0ClQ SSBXhi5+cT8parBKR29lb8fuHrCI8YjT44+ERQRjcwgfez8vj3ZAiSzm5pj5oKYvtUKq Ue0LGZwtKjRgVk275ZL35lswodbQWU9TAk+A8C9RigmlCIMfgCDzVPQ/KvPqfZbkZmGR JcfuKnRe3NQRana7pMM66Xi1P6z0aqCMXSJUyq4qdl+paZADi35QFmnLxDc5ETGJmbQX uIjEAo9DICCV1pm7dWDh0XFGffYG+DaKLv4HWcYEsGZgQE7Ounn9X32Kyf/rzbDUe33d AWJw== X-Gm-Message-State: AOAM532/UIwp/Qrqgy9Snm2gfly3kqSPmEysQ/T51wCTjfecPPo8I484 M3WMcdT0QCu9XSAuoajWLaisC/Twv3A= X-Google-Smtp-Source: ABdhPJxNYiJ2MPFt6bqTgN+LJTd85XwB1LH2whxVCYRbeJGcUjQK7jp7285gJeSAuOlVHr/gm0srOA== X-Received: by 2002:a1c:4e06:: with SMTP id g6mr1861242wmh.119.1606378046320; Thu, 26 Nov 2020 00:07:26 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id a184sm6812627wmf.8.2020.11.26.00.07.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 00:07:25 -0800 (PST) Date: Thu, 26 Nov 2020 09:07:24 +0100 From: Gary Jennejohn To: tech-lists Cc: freebsd-current@freebsd.org Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201126080724.1cb3a8af@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4ChVjX2Yg8z3NjG X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(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]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; 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]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::344:from]; 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=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.14:received]; FROM_HAS_DN(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)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::344:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2a00:1450:4864:20::344:query timed out,91.2.53.14:query timed out]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::344:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 08:07:33 -0000 On Thu, 26 Nov 2020 00:10:40 +0000 tech-lists wrote: > Hi, > > I have a usb3-connected harddrive. dmesg shows this: > [...] > da0: Fixed Direct Access SPC-4 SCSI device > [...] > > running current-r367806-arm64 > > I think it might be auto-spinning-down or auto-sleeping. It's > making initial interaction lag of 2-3 seconds. Is there a sysctl or > something somewhere where I can tell it to never sleep? Or is that > something I'd need to contact the manufacturer about? Or is there > an alternative strategy like tmpfs. It's not a "green" drive but I > guess it might be "green" in that it's usb3 powered. > > I have vfs.read_max=128 in /etc/sysctl.conf > zdb has ashift=12 > > In case it's relevant, the filesystem on the disk is zfs. Once > "woken up", inferaction is quick, as expected. > thanks, > I'd be interested in an answer to this question myself. I have several USB-attached UFS2 disks which spin down after a few minutes. But, based on some quick searches, this behavior is either a "feature" of the disk itself - seems common with so-called green disks - or of the controller in the external enclosure or docking station. This behavior makes sense for drives used with laptops, but for desktop computers not so useful. There are some sysctl's relevant to spindown, but they appear to only come into play during suspend or shutdown. The ones relevant to USB which I found are: kern.cam.ada.spindown_suspend: Spin down upon suspend kern.cam.ada.spindown_shutdown: Spin down upon shutdown There may be commands which a user can send the disk/controller to disable this behavior, but I didn't find any with my simple searches. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Nov 26 08:14:16 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 563E34A5501 for ; Thu, 26 Nov 2020 08:14:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 4ChVsM4YwBz3PFw for ; Thu, 26 Nov 2020 08:14:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x734.google.com with SMTP id n132so921621qke.1 for ; Thu, 26 Nov 2020 00:14:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZAIhaEJJ3VTZdnE1c7ccxLWtZxEbnsJlxYyM5G4jlUY=; b=puTLzyt4g2Nu4YyKntE9P4mi7eazpovM8Yp+PJpkRu9jWZgpYaLA+We6153vLZgNXO pE5gWWU++ush0aOqqtJ8xJ+OaHG+tq7KWGRrudct+V4ZStc8w/VDyDuLzP6ctvTbt39R 9WOZdI6diOr5CQFArx2HPKh3ghMjkGaDCTZsa68X/TsIbKftRvXfG6POhnP2T28KQZoS 6uo/HXkbGy+UinsyERj7P3AHMK894STxk2yppQv44en6Ya6pv+JIvCUTasp2Rz5qKmKb NBna8BM2eUykqmYQ7D8c403PNSffbo5KdKJ9SW5KkR05l1nwntn4vRlYnBFajkRHGBHX S5Zw== X-Gm-Message-State: AOAM5309pOC8yDqkoQloqH+Mp0GkUlDBjp8SChbpMv0xsvCb5kYWXT5q knxR7unecHXinfNqtO/9Uu9e5RKQW/PK3MH35XPbbg== X-Google-Smtp-Source: ABdhPJz2rsL3/5/Oj/BbUWaBZEotznkCF6TlLFhH3C1LysQcuO8lvX52tMvYNd4UScWiCCQX1S390MfdKQLzTE932rg= X-Received: by 2002:a37:78c:: with SMTP id 134mr2006468qkh.359.1606378453475; Thu, 26 Nov 2020 00:14:13 -0800 (PST) MIME-Version: 1.0 References: <20201126080724.1cb3a8af@ernst.home> In-Reply-To: <20201126080724.1cb3a8af@ernst.home> From: Warner Losh Date: Thu, 26 Nov 2020 01:14:02 -0700 Message-ID: Subject: Re: possible usb3-connected hard drive spin down causing lag To: Gary Jennejohn Cc: tech-lists , FreeBSD Current X-Rspamd-Queue-Id: 4ChVsM4YwBz3PFw X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; 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)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::734:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::734:from]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::734:from]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 08:14:16 -0000 On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn wrote: > On Thu, 26 Nov 2020 00:10:40 +0000 > tech-lists wrote: > > > Hi, > > > > I have a usb3-connected harddrive. dmesg shows this: > > [...] > > da0: Fixed Direct Access SPC-4 SCSI device > > [...] > > > > running current-r367806-arm64 > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > making initial interaction lag of 2-3 seconds. Is there a sysctl or > > something somewhere where I can tell it to never sleep? Or is that > > something I'd need to contact the manufacturer about? Or is there > > an alternative strategy like tmpfs. It's not a "green" drive but I > > guess it might be "green" in that it's usb3 powered. > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > zdb has ashift=12 > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > "woken up", inferaction is quick, as expected. > > thanks, > > > > I'd be interested in an answer to this question myself. I have > several USB-attached UFS2 disks which spin down after a few minutes. > > But, based on some quick searches, this behavior is either a "feature" > of the disk itself - seems common with so-called green disks - or of > the controller in the external enclosure or docking station. > > This behavior makes sense for drives used with laptops, but for > desktop computers not so useful. > > There are some sysctl's relevant to spindown, but they appear to only > come into play during suspend or shutdown. The ones relevant to USB > which I found are: > > kern.cam.ada.spindown_suspend: Spin down upon suspend > kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > There may be commands which a user can send the disk/controller to > disable this behavior, but I didn't find any with my simple searches. > For SAS drives, there's a mode page that controls this behavior. You might see if the sysutil/ataidle port/package does what you want. Warner From owner-freebsd-current@freebsd.org Thu Nov 26 09:12:11 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 340704A6613 for ; Thu, 26 Nov 2020 09:12:11 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 4ChX8B143Wz3hdP for ; Thu, 26 Nov 2020 09:12:09 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr1-x435.google.com with SMTP id m6so1298815wrg.7 for ; Thu, 26 Nov 2020 01:12:09 -0800 (PST) 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=C2Ofi1OhYw8ydAAIC6UmkN4Pir5JprIZYlJSsOW09qo=; b=tXHw9cJNB8jksZadGk2tewMsAYwVEqdhQh6p9weXkwZpihrYQY6gzZtu40Zq6gCC+3 HD0bYipUG1kt3gcuIQfrx62aSabROjrnpcRsV12lzRRLltZfMqMPgbxMm06iF7UIkz8Y BBznJi0rmzKA5SsltM3osZiMj+qzP18agsRtB19ESnIBKVQpchrDuRKFm2s9LEI5eyaq 5OWbwbb55adAzt921VvV4PGqdSTuHYT8UTROXUBrFnoxbfYutBBFv2H6U+AiYIWX+mQh o04UIeELAsDTtDNtKQ8Ba16Gx+Kk5BTjJC/9UuKGx7ca4ybBt6J/Hc+tSzOt13/2d1Pu VIDw== X-Gm-Message-State: AOAM530PbDtvqeJ6cJT1EHB8AqXSdd/+KLIpHBn3QUFxEz7UUhmzOkIK MGdsFMH5zC+MnS1LJlONG5IlrAvh5Eo= X-Google-Smtp-Source: ABdhPJzeX0/IRh1djxfon1WQwpCwP4XHGM9hXBgBNN0MeKGieD9sYR/kLjtIe5dVToSJBFuQlFioxw== X-Received: by 2002:a5d:474f:: with SMTP id o15mr2504576wrs.377.1606381928115; Thu, 26 Nov 2020 01:12:08 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id q1sm8149322wrj.8.2020.11.26.01.12.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 01:12:07 -0800 (PST) Date: Thu, 26 Nov 2020 10:12:06 +0100 From: Gary Jennejohn To: Warner Losh Cc: tech-lists , FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201126091206.0dcd5b33@ernst.home> In-Reply-To: References: <20201126080724.1cb3a8af@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4ChX8B143Wz3hdP X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.65 / 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)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; 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]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::435:from]; 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=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.14:received]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.35)[0.347]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::435:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::435:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 09:12:11 -0000 On Thu, 26 Nov 2020 01:14:02 -0700 Warner Losh wrote: > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn wrote: > > > On Thu, 26 Nov 2020 00:10:40 +0000 > > tech-lists wrote: > > > > > Hi, > > > > > > I have a usb3-connected harddrive. dmesg shows this: > > > [...] > > > da0: Fixed Direct Access SPC-4 SCSI device > > > [...] > > > > > > running current-r367806-arm64 > > > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > > making initial interaction lag of 2-3 seconds. Is there a sysctl or > > > something somewhere where I can tell it to never sleep? Or is that > > > something I'd need to contact the manufacturer about? Or is there > > > an alternative strategy like tmpfs. It's not a "green" drive but I > > > guess it might be "green" in that it's usb3 powered. > > > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > > zdb has ashift=12 > > > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > > "woken up", inferaction is quick, as expected. > > > thanks, > > > > > > > I'd be interested in an answer to this question myself. I have > > several USB-attached UFS2 disks which spin down after a few minutes. > > > > But, based on some quick searches, this behavior is either a "feature" > > of the disk itself - seems common with so-called green disks - or of > > the controller in the external enclosure or docking station. > > > > This behavior makes sense for drives used with laptops, but for > > desktop computers not so useful. > > > > There are some sysctl's relevant to spindown, but they appear to only > > come into play during suspend or shutdown. The ones relevant to USB > > which I found are: > > > > kern.cam.ada.spindown_suspend: Spin down upon suspend > > kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > > > There may be commands which a user can send the disk/controller to > > disable this behavior, but I didn't find any with my simple searches. > > > > For SAS drives, there's a mode page that controls this behavior. > > You might see if the sysutil/ataidle port/package does what you want. > Thanks, Warner, but that port is not in my HEAD ports tree. It's also not in the HEAD pkg repository. Many the name has changed? My disks are all SATA in various USB3 enclosures/docking stations. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Nov 26 09:46:48 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E0BFD4A7086 for ; Thu, 26 Nov 2020 09:46:48 +0000 (UTC) (envelope-from dim@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ChXw85x6Sz3kZB; Thu, 26 Nov 2020 09:46:48 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:470:7a58:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id A5243FCAC; Thu, 26 Nov 2020 09:46:48 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::ec74:5d3a:9570:54b5] (unknown [IPv6:2001:470:7a58:0:ec74:5d3a:9570:54b5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9924843345; Thu, 26 Nov 2020 10:46:46 +0100 (CET) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_43784985-B155-4E1E-89DC-97D72CD098C5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: possible usb3-connected hard drive spin down causing lag Date: Thu, 26 Nov 2020 10:46:36 +0100 In-Reply-To: Cc: freebsd-current@freebsd.org To: tech-lists References: X-Mailer: Apple Mail (2.3445.104.17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 09:46:48 -0000 --Apple-Mail=_43784985-B155-4E1E-89DC-97D72CD098C5 Content-Type: multipart/mixed; boundary="Apple-Mail=_06AAB545-0BBB-49DD-B7E8-ECA0CB147400" --Apple-Mail=_06AAB545-0BBB-49DD-B7E8-ECA0CB147400 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 26 Nov 2020, at 01:10, tech-lists wrote: >=20 > I have a usb3-connected harddrive. dmesg shows this: > [...] > da0: Fixed Direct Access SPC-4 SCSI device > [...] >=20 > running current-r367806-arm64 >=20 > I think it might be auto-spinning-down or auto-sleeping. It's > making initial interaction lag of 2-3 seconds. Is there a sysctl or = something somewhere where I can tell it to never sleep? Or is that = something I'd need to contact the manufacturer about? Or is there an = alternative strategy like tmpfs. It's not a "green" drive but I guess it = might > be "green" in that it's usb3 powered. >=20 > I have vfs.read_max=3D128 in /etc/sysctl.conf > zdb has ashift=3D12 >=20 > In case it's relevant, the filesystem on the disk is zfs. Once > "woken up", inferaction is quick, as expected. > thanks, I have been using the attached rc.d script for a long time now, which uses camcontrol(8)'s "apm" and "aam" commands to set drives to 'maximum performance' (aka don't try to save power by shutting down all the time). Just drop this into /usr/local/etc/rc.d, and add something like the following to your rc.conf: camperf_devices=3D"da0 da1" camperf_enable=3D"YES" You can also manually start the rc.d script by running: sudo service camperf start -Dimitry --Apple-Mail=_06AAB545-0BBB-49DD-B7E8-ECA0CB147400 Content-Disposition: attachment; filename=camperf Content-Type: application/octet-stream; x-unix-mode=0755; name="camperf" Content-Transfer-Encoding: 7bit #!/bin/sh # PROVIDE: camperf # BEFORE: LOGIN # # Add the following lines to /etc/rc.conf to enable camperf: # # camperf_enable (bool): set to NO by default. # Set to YES to enable camperf. # camperf_devices: list of devices on which to run camperf # Example: # Set the disks da0 and da1 to max APM and AAM performance: # # camperf_devices="da0 da1" # . /etc/rc.subr name="camperf" rcvar=camperf_enable command=/sbin/camcontrol start_cmd=camperf_start load_rc_config $name : ${camperf_enable="NO"} camperf_start() { if [ -n "${camperf_devices}" ]; then for i in ${camperf_devices}; do echo "camperf: configuring device /dev/${i}" ${command} apm /dev/${i} -l 254 ${command} aam /dev/${i} -l 254 done fi } run_rc_command "$1" --Apple-Mail=_06AAB545-0BBB-49DD-B7E8-ECA0CB147400-- --Apple-Mail=_43784985-B155-4E1E-89DC-97D72CD098C5 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCX795fAAKCRCwXqMKLiCW o3mlAKC41pQgVpoxPhCCHpFLjj7YjiqbPQCfUP1tY1RcnqEeLwmU7XFAMw1cvTg= =pBI5 -----END PGP SIGNATURE----- --Apple-Mail=_43784985-B155-4E1E-89DC-97D72CD098C5-- From owner-freebsd-current@freebsd.org Thu Nov 26 10:08:07 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 43DCD4A7B65 for ; Thu, 26 Nov 2020 10:08:07 +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 4ChYNk72MFz3m2M for ; Thu, 26 Nov 2020 10:08:06 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1kiEBu-0005CG-R7; Thu, 26 Nov 2020 11:07:54 +0100 Date: Thu, 26 Nov 2020 11:07:54 +0100 From: Kurt Jaeger To: Graham Perrin Cc: freebsd-current@freebsd.org Subject: Re: zpool export: umount failed, device inexplicably busy (lsof found nothing) Message-ID: <20201126100754.GB74574@home.opsec.eu> References: <4125dad7-b1ea-bf20-4996-6a138ff202eb@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4ChYNk72MFz3m2M X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; local_wl_from(0.00)[freebsd.org] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 10:08:07 -0000 Hi! > If the problem recurs: is it _ever_ sane to get nothing listed by lsof > for a volume that can not be unmounted? Use fstat -- this is part of the base system. Maybe lsof does not catch every corner case ? -- pi@opsec.eu +49 171 3101372 Now what ? From owner-freebsd-current@freebsd.org Thu Nov 26 11:16:55 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D89614A922D for ; Thu, 26 Nov 2020 11:16:55 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (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 "mail.evolve.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ChZw572jXz3qwX for ; Thu, 26 Nov 2020 11:16:53 +0000 (UTC) (envelope-from freebsd@grem.de) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 286652bb; Thu, 26 Nov 2020 11:16:44 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 05498dae (TLSv1.3:AEAD-CHACHA20-POLY1305-SHA256:256:NO); Thu, 26 Nov 2020 11:16:43 +0000 (UTC) Date: Thu, 26 Nov 2020 12:16:23 +0100 From: Michael Gmelin To: Gary Jennejohn Cc: Warner Losh , tech-lists , FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201126121623.31ea2cd3@bsd64.grem.de> In-Reply-To: <20201126091206.0dcd5b33@ernst.home> References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4ChZw572jXz3qwX X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.44 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[grem.de:s=20180501]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:213.239.217.29/32]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grem.de]; SPAMHAUS_ZRD(0.00)[213.239.217.29:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[grem.de:+]; NEURAL_HAM_SHORT(-0.94)[-0.942]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[213.239.217.29:from]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 11:16:55 -0000 On Thu, 26 Nov 2020 10:12:06 +0100 Gary Jennejohn wrote: > On Thu, 26 Nov 2020 01:14:02 -0700 > Warner Losh wrote: > > > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn > > wrote: > > > On Thu, 26 Nov 2020 00:10:40 +0000 > > > tech-lists wrote: > > > > > > > Hi, > > > > > > > > I have a usb3-connected harddrive. dmesg shows this: > > > > [...] > > > > da0: Fixed Direct Access SPC-4 SCSI device > > > > [...] > > > > > > > > running current-r367806-arm64 > > > > > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > > > making initial interaction lag of 2-3 seconds. Is there a > > > > sysctl or something somewhere where I can tell it to never > > > > sleep? Or is that something I'd need to contact the > > > > manufacturer about? Or is there an alternative strategy like > > > > tmpfs. It's not a "green" drive but I guess it might be > > > > "green" in that it's usb3 powered. > > > > > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > > > zdb has ashift=12 > > > > > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > > > "woken up", inferaction is quick, as expected. > > > > thanks, > > > > > > > > > > I'd be interested in an answer to this question myself. I have > > > several USB-attached UFS2 disks which spin down after a few > > > minutes. > > > > > > But, based on some quick searches, this behavior is either a > > > "feature" of the disk itself - seems common with so-called green > > > disks - or of the controller in the external enclosure or docking > > > station. > > > > > > This behavior makes sense for drives used with laptops, but for > > > desktop computers not so useful. > > > > > > There are some sysctl's relevant to spindown, but they appear to > > > only come into play during suspend or shutdown. The ones > > > relevant to USB which I found are: > > > > > > kern.cam.ada.spindown_suspend: Spin down upon suspend > > > kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > > > > > There may be commands which a user can send the disk/controller to > > > disable this behavior, but I didn't find any with my simple > > > searches. > > > > For SAS drives, there's a mode page that controls this behavior. > > > > You might see if the sysutil/ataidle port/package does what you > > want. > > Thanks, Warner, but that port is not in my HEAD ports tree. It's > also not in the HEAD pkg repository. Many the name has changed? > > My disks are all SATA in various USB3 enclosures/docking stations. > I also used ataidle in the past, but it was removed from the ports tree in 2018 (see MOVED). Since then, I'm using camcontrol to set standby timeout values on my SATA drives, I never tried it on USB devices though. Example: /sbin/camcontrol standby /dev/da2 -v -t 1800 Best, Michael -- Michael Gmelin From owner-freebsd-current@freebsd.org Thu Nov 26 16:55:50 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9DFBA468A7E for ; Thu, 26 Nov 2020 16:55:50 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 4ChkR96GZ4z4kW2 for ; Thu, 26 Nov 2020 16:55:49 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x429.google.com with SMTP id k14so2867361wrn.1 for ; Thu, 26 Nov 2020 08:55:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7q+cGBIoGI2QztrddXoLO9ShRIePA1HuuoJqw7zpfEk=; b=SEGGATErbpEOw+7CDqUuYTNr+zOQmbOo2OQWWmOwGBt+WBpEywTkNaJEMQhQ7BgScw GLNuRPrIFMkoYLgUxJqx0izn6qSZa/Zt+Vkl5xT0lBm3ZSnNYHKtJcz8FkeMLTmgIxpQ pifwjQagJ77+F0DXSlAu2YZjjmcm2Gd534Yb4LI0GDYNLTy1g8FoOvTGhxfae0hZL6PC fVKksd3cj6bhO7GNxVEz6Gmg1ZGPwpS+3PBl2xXGxb5T3OJX3w4/+BqbKltAU1eJuiNk JTXPjidJJqAPmcYjB0NCFFdneALaS3XrGdS4lIZHIig5Mxlf3qaDhMFGYMv9Wj1+rSTS GbtA== X-Gm-Message-State: AOAM532KYHC+AFA/vOF6aA+QItporZDdt+5WYTRJbbT7qNcolL7B0Dzk ZZvl31i5IVUik6zOrWLDKh6uycILQwU= X-Google-Smtp-Source: ABdhPJx70zHPfYlhZo+DbyvCbbghk64Zy4s2Lv1M81E0B2+EwkwQrMXHoseEVlt2qHHri9AtVAdovA== X-Received: by 2002:a5d:65ca:: with SMTP id e10mr4976319wrw.42.1606409747799; Thu, 26 Nov 2020 08:55:47 -0800 (PST) Received: from [192.168.1.11] (79-66-147-78.dynamic.dsl.as9105.com. [79.66.147.78]) by smtp.gmail.com with ESMTPSA id e4sm9755840wrr.32.2020.11.26.08.55.46 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Nov 2020 08:55:47 -0800 (PST) Subject: zpool export: umount fails, device inexplicably busy (lsof finds nothing) From: Graham Perrin To: freebsd-current@freebsd.org References: <4125dad7-b1ea-bf20-4996-6a138ff202eb@gmail.com> Message-ID: <1b4bf881-7689-95ac-6bb5-984d063bda73@gmail.com> Date: Thu, 26 Nov 2020 16:55:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4ChkR96GZ4z4kW2 X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; 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(-1.00)[-0.999]; RECEIVED_SPAMHAUS_PBL(0.00)[79.66.147.78:received]; FROM_EQ_ENVFROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::429:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; 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]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::429:from:127.0.2.255]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::429:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 16:55:50 -0000 On 25/11/2020 17:35, Graham Perrin wrote: > … >> root@momh167-gjp4-8570p:~ # zpool export Transcend >> cannot unmount '/Volumes/t500': umount failed >> root@momh167-gjp4-8570p:~ # umount /Volumes/t500 >> umount: unmount of /Volumes/t500 failed: Device busy >> root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/ >> root@momh167-gjp4-8570p:~ # >> >> ---- >> >> When this last occurred, I could export the pool after signing out >> from KDE. >> > The problem seemed to be consistently reproducible but (fingers > crossed) no problem yesterday or today. > > Previously: most often using OpenZFS in base. > > Now using OpenZFS from ports, with r367936. > > If the problem recurs: is it _ever_ sane to get nothing listed by lsof > for a volume that can not be unmounted? I spoke too soon, the problem recurred this afternoon: root@mowa219-gjp4-8570p:~ # zpool export Transcend cannot unmount '/Volumes/t500/VirtualBox': umount failed root@mowa219-gjp4-8570p:~ # lsof /Volumes/t500/VirtualBox lsof: WARNING: device cache mismatch: /dev/drm/121 lsof: WARNING: /root/.lsof_mowa219-gjp4-8570p was updated. root@mowa219-gjp4-8570p:~ # lsof /Volumes/t500/VirtualBox root@mowa219-gjp4-8570p:~ # zpool export Transcend cannot unmount '/Volumes/t500/VirtualBox': umount failed root@mowa219-gjp4-8570p:~ # uname -v FreeBSD 13.0-CURRENT #72 r367936: Sun Nov 22 21:46:00 GMT 2020 root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG root@mowa219-gjp4-8570p:~ # zfs --version zfs-0.8.0-1 zfs-kmod-v2020110200-zfs_8583540c6 root@mowa219-gjp4-8570p:~ # From owner-freebsd-current@freebsd.org Thu Nov 26 17:34:30 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28BB446A023 for ; Thu, 26 Nov 2020 17:34:30 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 4ChlHn5sXsz4msm for ; Thu, 26 Nov 2020 17:34:29 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1kiL9y-0004J7-FJ; Thu, 26 Nov 2020 17:34:22 +0000 Date: Thu, 26 Nov 2020 17:34:22 +0000 From: Gary Palmer To: Graham Perrin Cc: freebsd-current@freebsd.org Subject: Re: zpool export: umount fails, device inexplicably busy (lsof finds nothing) Message-ID: <20201126173422.GB46155@in-addr.com> References: <4125dad7-b1ea-bf20-4996-6a138ff202eb@gmail.com> <1b4bf881-7689-95ac-6bb5-984d063bda73@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1b4bf881-7689-95ac-6bb5-984d063bda73@gmail.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4ChlHn5sXsz4msm X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 17:34:30 -0000 On Thu, Nov 26, 2020 at 04:55:46PM +0000, Graham Perrin wrote: > On 25/11/2020 17:35, Graham Perrin wrote: > > ??? > > > root@momh167-gjp4-8570p:~ # zpool export Transcend > > > cannot unmount '/Volumes/t500': umount failed > > > root@momh167-gjp4-8570p:~ # umount /Volumes/t500 > > > umount: unmount of /Volumes/t500 failed: Device busy > > > root@momh167-gjp4-8570p:~ # lsof /Volumes/t500/ > > > root@momh167-gjp4-8570p:~ # > > > > > > ---- > > > > > > When this last occurred, I could export the pool after signing out > > > from KDE. > > > > > The problem seemed to be consistently reproducible but (fingers crossed) > > no problem yesterday or today. > > > > Previously: most often using OpenZFS in base. > > > > Now using OpenZFS from ports, with r367936. > > > > If the problem recurs: is it _ever_ sane to get nothing listed by lsof > > for a volume that can not be unmounted? > > I spoke too soon, the problem recurred this afternoon: > > root@mowa219-gjp4-8570p:~ # zpool export Transcend > cannot unmount '/Volumes/t500/VirtualBox': umount failed > root@mowa219-gjp4-8570p:~ # lsof /Volumes/t500/VirtualBox > lsof: WARNING: device cache mismatch: /dev/drm/121 > lsof: WARNING: /root/.lsof_mowa219-gjp4-8570p was updated. > root@mowa219-gjp4-8570p:~ # lsof /Volumes/t500/VirtualBox > root@mowa219-gjp4-8570p:~ # zpool export Transcend > cannot unmount '/Volumes/t500/VirtualBox': umount failed > root@mowa219-gjp4-8570p:~ # uname -v > FreeBSD 13.0-CURRENT #72 r367936: Sun Nov 22 21:46:00 GMT 2020 > root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > root@mowa219-gjp4-8570p:~ # zfs --version > zfs-0.8.0-1 > zfs-kmod-v2020110200-zfs_8583540c6 > root@mowa219-gjp4-8570p:~ # does "fuser -c" show anything? the -m option may also be interesting (Search through mmapped files too) Regards, Gary From owner-freebsd-current@freebsd.org Thu Nov 26 17:44:32 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4F55346A802 for ; Thu, 26 Nov 2020 17:44:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 4ChlWM38YGz4nm3 for ; Thu, 26 Nov 2020 17:44:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x734.google.com with SMTP id q5so2167572qkc.12 for ; Thu, 26 Nov 2020 09:44:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=88lviB9SPkaj1uWryEqZHVu9AaJdMHS4nRIY6WSvqiY=; b=oKRLenhfuX85bHmlket/37B/38SHbSQIKpMt8ksQ5N9pqC3voc8in3V6g00ZA65/uP zjoVRxJD6QvH2m67OBbSRSrXyo8zk4vh1HQlwKyAS1MS0NYQSu1YjKmWcFP036BeYPc0 DT1dpfqlNUHHKHx2mxG56WpgBKu49PChFTVAcbKMypAOBZrJ3Qken1J259KO+Z+evPzD f99UGGFPmxzQnOwg6UAMXQ3YHJmzsBR7nvDqxWdpt5duxczInOMIzQCbHPNqUdK+kIVx vOcP2xnUnW1BHXdFQnDGzaffda/+YzC2oH+Z3H0k4eeyHvPs19TlyHRQ5fJdAU/zaoxL qmkg== X-Gm-Message-State: AOAM5321H4TyeHJwknLeJufspkFsBBJmsDX4kGHfTB0+LZHk9RGldvvJ RNPzxavC/x17iXbR2V+Dl4sC2HFxIvM3g1WI3X8Apw== X-Google-Smtp-Source: ABdhPJwZidFOJr6/XwnziSNmlhRy4zEkd+0KBnWTH9pmLdglW4B3LOaLm/3mk4Y5umYE42N5fdrCxnN0jZMeKBlDksM= X-Received: by 2002:a37:9b01:: with SMTP id d1mr4108506qke.89.1606412670500; Thu, 26 Nov 2020 09:44:30 -0800 (PST) MIME-Version: 1.0 References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> <20201126121623.31ea2cd3@bsd64.grem.de> In-Reply-To: <20201126121623.31ea2cd3@bsd64.grem.de> From: Warner Losh Date: Thu, 26 Nov 2020 10:44:19 -0700 Message-ID: Subject: Re: possible usb3-connected hard drive spin down causing lag To: Michael Gmelin Cc: Gary Jennejohn , tech-lists , FreeBSD Current X-Rspamd-Queue-Id: 4ChlWM38YGz4nm3 X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; 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)[bsdimp.com]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::734:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::734:from]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::734:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; FREEMAIL_CC(0.00)[gmail.com,zyxst.net,freebsd.org] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 17:44:32 -0000 On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote: > > > On Thu, 26 Nov 2020 10:12:06 +0100 > Gary Jennejohn wrote: > > > On Thu, 26 Nov 2020 01:14:02 -0700 > > Warner Losh wrote: > > > > > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn > > > wrote: > > > > On Thu, 26 Nov 2020 00:10:40 +0000 > > > > tech-lists wrote: > > > > > > > > > Hi, > > > > > > > > > > I have a usb3-connected harddrive. dmesg shows this: > > > > > [...] > > > > > da0: Fixed Direct Access SPC-4 SCSI device > > > > > [...] > > > > > > > > > > running current-r367806-arm64 > > > > > > > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > > > > making initial interaction lag of 2-3 seconds. Is there a > > > > > sysctl or something somewhere where I can tell it to never > > > > > sleep? Or is that something I'd need to contact the > > > > > manufacturer about? Or is there an alternative strategy like > > > > > tmpfs. It's not a "green" drive but I guess it might be > > > > > "green" in that it's usb3 powered. > > > > > > > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > > > > zdb has ashift=12 > > > > > > > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > > > > "woken up", inferaction is quick, as expected. > > > > > thanks, > > > > > > > > > > > > > I'd be interested in an answer to this question myself. I have > > > > several USB-attached UFS2 disks which spin down after a few > > > > minutes. > > > > > > > > But, based on some quick searches, this behavior is either a > > > > "feature" of the disk itself - seems common with so-called green > > > > disks - or of the controller in the external enclosure or docking > > > > station. > > > > > > > > This behavior makes sense for drives used with laptops, but for > > > > desktop computers not so useful. > > > > > > > > There are some sysctl's relevant to spindown, but they appear to > > > > only come into play during suspend or shutdown. The ones > > > > relevant to USB which I found are: > > > > > > > > kern.cam.ada.spindown_suspend: Spin down upon suspend > > > > kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > > > > > > > There may be commands which a user can send the disk/controller to > > > > disable this behavior, but I didn't find any with my simple > > > > searches. > > > > > > For SAS drives, there's a mode page that controls this behavior. > > > > > > You might see if the sysutil/ataidle port/package does what you > > > want. > > > > Thanks, Warner, but that port is not in my HEAD ports tree. It's > > also not in the HEAD pkg repository. Many the name has changed? > > > > My disks are all SATA in various USB3 enclosures/docking stations. > > > > I also used ataidle in the past, but it was removed from the ports tree > in 2018 (see MOVED). > > Since then, I'm using camcontrol to set standby timeout values on my > SATA drives, I never tried it on USB devices though. > > Example: > > /sbin/camcontrol standby /dev/da2 -v -t 1800 Perfect! I've not had to deal with sata disks that did this since the ataidle days. I looked in camcontrol before suggesting it, but somehow missed this... Glad I posted a bogus answer (sorry about that), since I learned something new. Warner From owner-freebsd-current@freebsd.org Thu Nov 26 17:46:07 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D796746A3FB for ; Thu, 26 Nov 2020 17:46:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 4ChlYC5cqxz4pFg for ; Thu, 26 Nov 2020 17:46:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x82b.google.com with SMTP id f27so1608806qtv.6 for ; Thu, 26 Nov 2020 09:46:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q71My08xmhDAKML5Ct6IV7iC4isJFx3OWCkSekPR9ww=; b=X1e1nUh6V3Awu21NJaZUbYSstRXBry7n1vrmJ6Y0fqXCXkg2TGwHt4InYZ7YgpLASQ Rh/wTf27xEhakGLHNmesApjYkw+38/ZVvX5jxzU2Xi/IYVz3EjRSuuZ162m/9hJ3W+B+ f578MurFS1bBv0sWbP1g4+vY/WxEePnAeTkrN2WJsUoIFzNPacbuUEfdSc2tEgxxKl1l l078+t3CAwmMHxYL1RT2+kYF1Rmzk0juAooDGqfhmHd8Juy2uT35RLeIFgwncwr4t4uO 1O8yKCE4LZNdxPO2tAGIQLMKBKBzO1Wnkdvt1QCyIbvF222rOYSzVuW9CqGShmFUiHWg +LjQ== X-Gm-Message-State: AOAM532Q030LoC/+VNg2N2VeTMv7teDu5dVaQwCHlbukgDfK2F/0Y1uO BUjBgWCD9CIcsMX7bPHyy5quMB6KBhyK6nD4ov5kqw== X-Google-Smtp-Source: ABdhPJxuer7XybofsNHKzuF0WHKGvh95qM3imtLXRePI+y/VDronFDs4ATqBQHvyi2MsWIyZy+ZnwBv4C13MkZILzVY= X-Received: by 2002:ac8:7619:: with SMTP id t25mr4171293qtq.244.1606412766996; Thu, 26 Nov 2020 09:46:06 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 26 Nov 2020 10:45:55 -0700 Message-ID: Subject: Re: possible usb3-connected hard drive spin down causing lag To: Dimitry Andric Cc: tech-lists , FreeBSD Current X-Rspamd-Queue-Id: 4ChlYC5cqxz4pFg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 17:46:07 -0000 On Thu, Nov 26, 2020 at 2:47 AM Dimitry Andric wrote: > On 26 Nov 2020, at 01:10, tech-lists wrote: > > > > I have a usb3-connected harddrive. dmesg shows this: > > [...] > > da0: Fixed Direct Access SPC-4 SCSI device > > [...] > > > > running current-r367806-arm64 > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > making initial interaction lag of 2-3 seconds. Is there a sysctl or > something somewhere where I can tell it to never sleep? Or is that > something I'd need to contact the manufacturer about? Or is there an > alternative strategy like tmpfs. It's not a "green" drive but I guess it > might > > be "green" in that it's usb3 powered. > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > zdb has ashift=12 > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > "woken up", inferaction is quick, as expected. > > thanks, > > I have been using the attached rc.d script for a long time now, which > uses camcontrol(8)'s "apm" and "aam" commands to set drives to 'maximum > performance' (aka don't try to save power by shutting down all the > time). > > Just drop this into /usr/local/etc/rc.d, and add something like the > following to your rc.conf: > > camperf_devices="da0 da1" > camperf_enable="YES" > > You can also manually start the rc.d script by running: > > sudo service camperf start > Should we have this, or a similar 'standby' setting as well in base? this question comes up a lot... Warner From owner-freebsd-current@freebsd.org Thu Nov 26 18:21:13 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF38946BD0A for ; Thu, 26 Nov 2020 18:21:13 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 4ChmKh6ntHz4rXP for ; Thu, 26 Nov 2020 18:21:12 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id u12so3139163wrt.0 for ; Thu, 26 Nov 2020 10:21:12 -0800 (PST) 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:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=HBTa2nibAXha+fnEKe/Im1MHPsg12Fc38aznAru3Auc=; b=JllxTX0wfrHJchcjJJODLd2UGykZJx64uHWvPo2oIb2jxrUkuSddbpljDuBt6buizz zgzgNP065jufyHDFKcXoCaNb4ad1/ZlLN8s50X49OVA1A4fO94ssUWbjq0Ix3tUXMt8j XIulR7vMjkEZW5Bhk8FWItJYgeK9QmYGva/A5lgMGgCuyPYJKENYNEHOuzMO1O96v4bE mc797pfGHXYMlD0aYoYZoKD7fBYijFBwv6G+3hUUHa/xgYG0hDo9bRwTDBnVEbFWvLwn GcvrwLk6VmeIlQpOZaDBJIU4ApzgWGvA9A4Es6KdgWaMc9rFrO2BZdjr1GMQQjrifX3o 7J/g== X-Gm-Message-State: AOAM53055DW9vwHP/QNHxSUCs+oZpAZFFpepXVRRtV7xFL7CPRZcxQp5 ay8ceoufz5XOl/vXP9Kgut6ZvYMs354= X-Google-Smtp-Source: ABdhPJzsBbrCgms95XD/0SeogTfi0yBFIoTqDjpIvSqfJie8DDXxLtgUEOvC1XtP3jO04Z+UCJYKIQ== X-Received: by 2002:adf:ec8a:: with SMTP id z10mr5545385wrn.113.1606414870540; Thu, 26 Nov 2020 10:21:10 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id g138sm9394114wme.39.2020.11.26.10.21.09 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 10:21:09 -0800 (PST) Date: Thu, 26 Nov 2020 19:21:08 +0100 From: Gary Jennejohn To: FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201126182108.4314a0aa@ernst.home> In-Reply-To: References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> <20201126121623.31ea2cd3@bsd64.grem.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4ChmKh6ntHz4rXP X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.32 / 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:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::431:from]; 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=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.14:received]; 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]; FREEMAIL_REPLYTO(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::431:from:127.0.2.255]; NEURAL_SPAM_SHORT(0.68)[0.677]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::431:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 18:21:13 -0000 On Thu, 26 Nov 2020 10:44:19 -0700 Warner Losh wrote: > On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote: > > > > > > > On Thu, 26 Nov 2020 10:12:06 +0100 > > Gary Jennejohn wrote: > > > > > On Thu, 26 Nov 2020 01:14:02 -0700 > > > Warner Losh wrote: > > > > > > > On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn > > > > wrote: > > > > > On Thu, 26 Nov 2020 00:10:40 +0000 > > > > > tech-lists wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I have a usb3-connected harddrive. dmesg shows this: > > > > > > [...] > > > > > > da0: Fixed Direct Access SPC-4 SCSI device > > > > > > [...] > > > > > > > > > > > > running current-r367806-arm64 > > > > > > > > > > > > I think it might be auto-spinning-down or auto-sleeping. It's > > > > > > making initial interaction lag of 2-3 seconds. Is there a > > > > > > sysctl or something somewhere where I can tell it to never > > > > > > sleep? Or is that something I'd need to contact the > > > > > > manufacturer about? Or is there an alternative strategy like > > > > > > tmpfs. It's not a "green" drive but I guess it might be > > > > > > "green" in that it's usb3 powered. > > > > > > > > > > > > I have vfs.read_max=128 in /etc/sysctl.conf > > > > > > zdb has ashift=12 > > > > > > > > > > > > In case it's relevant, the filesystem on the disk is zfs. Once > > > > > > "woken up", inferaction is quick, as expected. > > > > > > thanks, > > > > > > > > > > > > > > > > I'd be interested in an answer to this question myself. I have > > > > > several USB-attached UFS2 disks which spin down after a few > > > > > minutes. > > > > > > > > > > But, based on some quick searches, this behavior is either a > > > > > "feature" of the disk itself - seems common with so-called green > > > > > disks - or of the controller in the external enclosure or docking > > > > > station. > > > > > > > > > > This behavior makes sense for drives used with laptops, but for > > > > > desktop computers not so useful. > > > > > > > > > > There are some sysctl's relevant to spindown, but they appear to > > > > > only come into play during suspend or shutdown. The ones > > > > > relevant to USB which I found are: > > > > > > > > > > kern.cam.ada.spindown_suspend: Spin down upon suspend > > > > > kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > > > > > > > > > There may be commands which a user can send the disk/controller to > > > > > disable this behavior, but I didn't find any with my simple > > > > > searches. > > > > > > > > For SAS drives, there's a mode page that controls this behavior. > > > > > > > > You might see if the sysutil/ataidle port/package does what you > > > > want. > > > > > > Thanks, Warner, but that port is not in my HEAD ports tree. It's > > > also not in the HEAD pkg repository. Many the name has changed? > > > > > > My disks are all SATA in various USB3 enclosures/docking stations. > > > > > > > I also used ataidle in the past, but it was removed from the ports tree > > in 2018 (see MOVED). > > > > Since then, I'm using camcontrol to set standby timeout values on my > > SATA drives, I never tried it on USB devices though. > > > > Example: > > > > /sbin/camcontrol standby /dev/da2 -v -t 1800 > > > Perfect! I've not had to deal with sata disks that did this since the > ataidle days. I looked in camcontrol before suggesting it, but somehow > missed this... Glad I posted a bogus answer (sorry about that), since I > learned something new. > camcontrol unfortuantely doesn't work with my USB3 enclosures. I suspect that the USB3-to-SATA bridge controller is doing its own thing and camcontrol has no effect on its behavior. Not tragic for me since I use these disks primarily for backups. But for someone using a USB attached disk as a primary file system this behavior will definitely be a PITA. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Nov 26 18:37:57 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4341E46C700 for ; Thu, 26 Nov 2020 18:37:57 +0000 (UTC) (envelope-from dim@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Chmj11PmSz4swn; Thu, 26 Nov 2020 18:37:57 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 0AFA12467D; Thu, 26 Nov 2020 18:37:57 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::ec74:5d3a:9570:54b5] (unknown [IPv6:2001:470:7a58:0:ec74:5d3a:9570:54b5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id E5C8443C15; Thu, 26 Nov 2020 19:37:54 +0100 (CET) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_FC6D5932-8C69-48B3-B0D4-26A69E83FB2C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Re: possible usb3-connected hard drive spin down causing lag Date: Thu, 26 Nov 2020 19:37:47 +0100 In-Reply-To: <20201126182108.4314a0aa@ernst.home> Cc: FreeBSD Current To: Gary Jennejohn References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> <20201126121623.31ea2cd3@bsd64.grem.de> <20201126182108.4314a0aa@ernst.home> X-Mailer: Apple Mail (2.3445.104.17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 18:37:57 -0000 --Apple-Mail=_FC6D5932-8C69-48B3-B0D4-26A69E83FB2C Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 26 Nov 2020, at 19:21, Gary Jennejohn wrote: > > On Thu, 26 Nov 2020 10:44:19 -0700 > Warner Losh wrote: ... >>> Example: >>> >>> /sbin/camcontrol standby /dev/da2 -v -t 1800 >> >> >> Perfect! I've not had to deal with sata disks that did this since the >> ataidle days. I looked in camcontrol before suggesting it, but somehow >> missed this... Glad I posted a bogus answer (sorry about that), since I >> learned something new. >> > > camcontrol unfortuantely doesn't work with my USB3 enclosures. I > suspect that the USB3-to-SATA bridge controller is doing its own thing > and camcontrol has no effect on its behavior. Not tragic for me since > I use these disks primarily for backups. But for someone using a USB > attached disk as a primary file system this behavior will definitely be > a PITA. In this case it's about ATA commands being passed though the USB bridge. Does "camcontrol identify daX" fail in your case too? I have used quite a bunch of different USB disks, mostly from WD or Seagate, and these come with varying qualities of USB-SATA bridges in them. But all of them work with "camcontrol identify". -Dimitry --Apple-Mail=_FC6D5932-8C69-48B3-B0D4-26A69E83FB2C 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCX7/1+wAKCRCwXqMKLiCW o9RXAKCsEOwoEKZMwpR2zU0NjEnGlJEDVgCg38hOaNkpigZt2GSZOPlJceaLUP4= =MGlp -----END PGP SIGNATURE----- --Apple-Mail=_FC6D5932-8C69-48B3-B0D4-26A69E83FB2C-- From owner-freebsd-current@freebsd.org Thu Nov 26 19:09:50 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5441746D270 for ; Thu, 26 Nov 2020 19:09:50 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (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 "mail.evolve.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ChnPn0bp6z4vJK; Thu, 26 Nov 2020 19:09:48 +0000 (UTC) (envelope-from freebsd@grem.de) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 2af3f24d; Thu, 26 Nov 2020 19:09:45 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id b3101c52 (TLSv1.3:AEAD-CHACHA20-POLY1305-SHA256:256:NO); Thu, 26 Nov 2020 19:09:42 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: possible usb3-connected hard drive spin down causing lag From: Michael Gmelin In-Reply-To: <20201126182108.4314a0aa@ernst.home> Date: Thu, 26 Nov 2020 20:09:41 +0100 Cc: FreeBSD Current Message-Id: <6D7FEFE1-FF63-4920-9BA8-C8DCBE3D4019@grem.de> References: <20201126182108.4314a0aa@ernst.home> To: gljennjohn@gmail.com X-Mailer: iPhone Mail (18B92) X-Rspamd-Queue-Id: 4ChnPn0bp6z4vJK X-Spamd-Bar: / X-Spamd-Result: default: False [-1.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:213.239.217.29/32]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[grem.de:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[213.239.217.29:from]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; FORGED_RECIPIENTS(2.00)[m:gljennjohn@gmail.com,s:grembo@freebsd.org]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[grem.de:s=20180501]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grem.de]; SPAMHAUS_ZRD(0.00)[213.239.217.29:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 19:09:50 -0000 > On 26. Nov 2020, at 19:21, Gary Jennejohn wrote: >=20 > =EF=BB=BFOn Thu, 26 Nov 2020 10:44:19 -0700 > Warner Losh wrote: >=20 >>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote: >>>=20 >>>=20 >>>=20 >>> On Thu, 26 Nov 2020 10:12:06 +0100 >>> Gary Jennejohn wrote: >>>=20 >>>> On Thu, 26 Nov 2020 01:14:02 -0700 >>>> Warner Losh wrote: >>>>=20 >>>>> On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn >>>>> wrote: =20 >>>>>> On Thu, 26 Nov 2020 00:10:40 +0000 >>>>>> tech-lists wrote: >>>>>>=20 >>>>>>> Hi, >>>>>>>=20 >>>>>>> I have a usb3-connected harddrive. dmesg shows this: >>>>>>> [...] >>>>>>> da0: Fixed Direct Access SPC-4 SCSI device >>>>>>> [...] >>>>>>>=20 >>>>>>> running current-r367806-arm64 >>>>>>>=20 >>>>>>> I think it might be auto-spinning-down or auto-sleeping. It's >>>>>>> making initial interaction lag of 2-3 seconds. Is there a >>>>>>> sysctl or something somewhere where I can tell it to never >>>>>>> sleep? Or is that something I'd need to contact the >>>>>>> manufacturer about? Or is there an alternative strategy like >>>>>>> tmpfs. It's not a "green" drive but I guess it might be >>>>>>> "green" in that it's usb3 powered. >>>>>>>=20 >>>>>>> I have vfs.read_max=3D128 in /etc/sysctl.conf >>>>>>> zdb has ashift=3D12 >>>>>>>=20 >>>>>>> In case it's relevant, the filesystem on the disk is zfs. Once >>>>>>> "woken up", inferaction is quick, as expected. >>>>>>> thanks, >>>>>>>=20 >>>>>>=20 >>>>>> I'd be interested in an answer to this question myself. I have >>>>>> several USB-attached UFS2 disks which spin down after a few >>>>>> minutes. >>>>>>=20 >>>>>> But, based on some quick searches, this behavior is either a >>>>>> "feature" of the disk itself - seems common with so-called green >>>>>> disks - or of the controller in the external enclosure or docking >>>>>> station. >>>>>>=20 >>>>>> This behavior makes sense for drives used with laptops, but for >>>>>> desktop computers not so useful. >>>>>>=20 >>>>>> There are some sysctl's relevant to spindown, but they appear to >>>>>> only come into play during suspend or shutdown. The ones >>>>>> relevant to USB which I found are: >>>>>>=20 >>>>>> kern.cam.ada.spindown_suspend: Spin down upon suspend >>>>>> kern.cam.ada.spindown_shutdown: Spin down upon shutdown >>>>>>=20 >>>>>> There may be commands which a user can send the disk/controller to >>>>>> disable this behavior, but I didn't find any with my simple >>>>>> searches. =20 >>>>>=20 >>>>> For SAS drives, there's a mode page that controls this behavior. >>>>>=20 >>>>> You might see if the sysutil/ataidle port/package does what you >>>>> want. =20 >>>>=20 >>>> Thanks, Warner, but that port is not in my HEAD ports tree. It's >>>> also not in the HEAD pkg repository. Many the name has changed? >>>>=20 >>>> My disks are all SATA in various USB3 enclosures/docking stations. >>>>=20 >>>=20 >>> I also used ataidle in the past, but it was removed from the ports tree >>> in 2018 (see MOVED). >>>=20 >>> Since then, I'm using camcontrol to set standby timeout values on my >>> SATA drives, I never tried it on USB devices though. >>>=20 >>> Example: >>>=20 >>> /sbin/camcontrol standby /dev/da2 -v -t 1800 =20 >>=20 >>=20 >> Perfect! I've not had to deal with sata disks that did this since the >> ataidle days. I looked in camcontrol before suggesting it, but somehow >> missed this... Glad I posted a bogus answer (sorry about that), since I >> learned something new. >>=20 >=20 > camcontrol unfortuantely doesn't work with my USB3 enclosures. I > suspect that the USB3-to-SATA bridge controller is doing its own thing > and camcontrol has no effect on its behavior. Not tragic for me since > I use these disks primarily for backups. But for someone using a USB > attached disk as a primary file system this behavior will definitely be=20= > a PITA. Does using /dev/passX instead of /dev/daX make a difference? (I remember I h= ad to do something like this when using smartctl on usb drives). -m >=20 > --=20 > Gary Jennejohn > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@freebsd.org Thu Nov 26 23:07:48 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 34FAC474398 for ; Thu, 26 Nov 2020 23:07:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 4ChthM14PYz3mKH for ; Thu, 26 Nov 2020 23:07:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E6B78139B for ; Thu, 26 Nov 2020 18:07:44 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 26 Nov 2020 18:07:45 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehfedgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurddutddu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtg hhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 0FB4F3064AA6 for ; Thu, 26 Nov 2020 18:07:43 -0500 (EST) Date: Thu, 26 Nov 2020 23:07:42 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> <20201126121623.31ea2cd3@bsd64.grem.de> <20201126182108.4314a0aa@ernst.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="P0dqQ1dDnsLpa5V6" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4ChthM14PYz3mKH X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.20:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.20:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.20:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 23:07:48 -0000 --P0dqQ1dDnsLpa5V6 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 26, 2020 at 07:37:47PM +0100, Dimitry Andric wrote: >In this case it's about ATA commands being passed though the USB bridge. >Does "camcontrol identify daX" fail in your case too? > >I have used quite a bunch of different USB disks, mostly from WD or >Seagate, and these come with varying qualities of USB-SATA bridges in >them. But all of them work with "camcontrol identify". With my usb3 powered disk, camdontrol identify da0 works some features: support enabled value advanced power management yes yes 254/0xFE power management yes yes microcode download yes yes loads of others thanks for posting that script btw --=20 J. --P0dqQ1dDnsLpa5V6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/ANTUACgkQs8o7QhFz NAW2wQ//df+kjRCxSX8nAhHruww74DyewQj4jvhN5lzC9GD0W5d/EUxR7Tw25UT0 SxJZihlhcLiz6lLWBP1jh0ATXjm8gC73QctrNaHStYTzWZDSHk6pVse8+Xp0AOG+ u1TrA4puj7MEzTLb9OtLB6E4eYBYbqUvefb9hxcAKN7Ph7AIplabKWkKzceMkkgY fbiBX6Iq6YKwFbkwAGCe3oiLnsMJbvnOU5rdvwtWXvN1f41UvX/VmIQtHLgcmrjN f3hA0QxnxbT9snsWIT/lB0+gOUeHEfaGTUcaOC6WJChdx0AKvcZ+rS6wpL59K/R1 CKf7btg2kp1gja87fusvN/LfZso9Z9e4dRv14MqhgDlsNe96F8bV6dy4QexdBjGA 90afx46czZuQpXaRGFUnxCIzuvMReYPGU05YmxVOO1gB/ZsAz5435r4oktiJDNBD 7CVqxgROeJmgXmvOy0ryh4Tb3z4BBH98HX8sXDJ5WVnApg5yJmrHpYulDHNZj8gy 0SHVtCPbQqZrXkw0YA6azoWAHn6ygrC7pip+FyDYlyCFTm+0UxzXmF2xm0keLqgi p6pq4aCmic9TJtRyRm3ToIhsrW/6dxvti2/uhJhLaZ1DB4aCoKsZrPWlgHGun/sb zBhRsqBovMqQVbgwjalc9tlGdfJx6x3U2fl3ZMLrfLsP0LBk0G4= =nFMA -----END PGP SIGNATURE----- --P0dqQ1dDnsLpa5V6-- From owner-freebsd-current@freebsd.org Fri Nov 27 03:24:45 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 99CAC47A9B5 for ; Fri, 27 Nov 2020 03:24:45 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 4Cj0Nr50rNz4Vxv for ; Fri, 27 Nov 2020 03:24:44 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id AF444938 for ; Thu, 26 Nov 2020 22:24:42 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 26 Nov 2020 22:24:42 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehfedgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurddutddu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtg hhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id CFDE93064AA7 for ; Thu, 26 Nov 2020 22:24:41 -0500 (EST) Date: Fri, 27 Nov 2020 03:24:39 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="F2VguJWxUxeN+bpt" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Cj0Nr50rNz4Vxv X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.21:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.21:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.21:from:127.0.2.255]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.21:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 03:24:45 -0000 --F2VguJWxUxeN+bpt Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, It seems the issue wasn't with the hardware or the connection. I use mutt and it's the program that was slowing everything down, and that was down to me using new mutt with my old config. The whole pause for 5 seconds thing was due to it scanning gigabytes of email each=20 time it woke up. The fix was to review the config and change a couple of=20 settings. Now there's no delay (well there is a bit but only because it's= =20 scanning the folders it's told to for new mail). But looking at a hardware cause wasn't in vain. On the way to the solution,= =20 found a few tips through here that sped up the system generally, and learne= d=20 a bit. So now I have a *really quick* raspberry pi4 which is rock-solid=20 stable, so thanks :D --=20 J. --F2VguJWxUxeN+bpt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/AcW8ACgkQs8o7QhFz NAUtfA//WpCPWjcjM9Pp53H1LSZOGoQOccABxqwhTxBnPM8kifvKOn6HNG7kbUKU NXU56mkMGFJ2m3Trocjs9KW2qgkfDtuVGD33gsT6cTAkBXK1Sf1A1Sr0MGNBPakE C9Vvd/s7Xmll43ow2wxyvRSyiYnxmG7GMWQg3LfTWrJoYthpe3s44g6RoKjBTmAs FXdP5n1/exFb+Tan3rPXUv/jt1XStdTwOEW0UZx8WS7WMsViH5pW8Zc+K1mrN4R8 Z63QTPhsVZ2WYK0XHB/tW36ceSvpGUpTxzCh/vD0F+xHSkaBS+nrukdQNPqIsmOG Pm7S5KuAiu6mJhKXzJnANs+ayz7sIt6P7IqIB3Y/MyLqXfdM65FXPHOK7H+AraJQ gNz/EczMwWfQkQCCVzTV6Ew2zOe0x0qzwAvkwJkAv5MLF4wCiu8nYKzU1DQ+GOoO yvORSDxN4yG1wDB5cW54by3IbvjQYWCyJ9cijRB/YWPMtVVRvJFu19opB2CELZ4v PtlDJFhHcriic1LzM7/8BIHIMqSfXS7QR9+Bx6j4LwdvBUhW/6zVsK+dWP0q94wM hhJVl5qhnT4GDUkqHrJAPuaerSQHSTFZzuZELGSY1imVPbkk9nNhsIMzUXCREg6z S5Twgedn2wC10kkbjkT6/9iBF7Uxak2WPIUTAxPNMaHXYWblq8U= =EtOL -----END PGP SIGNATURE----- --F2VguJWxUxeN+bpt-- From owner-freebsd-current@freebsd.org Fri Nov 27 05:09:30 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C3CCD47CF1E for ; Fri, 27 Nov 2020 05:09:30 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from out03.mta.xmission.com (out03.mta.xmission.com [166.70.13.233]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cj2jj44mwz4bLB; Fri, 27 Nov 2020 05:09:29 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from in02.mta.xmission.com ([166.70.13.52]) by out03.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kiW0c-00GqiQ-Oe; Thu, 26 Nov 2020 22:09:26 -0700 Received: from mta5.zcs.xmission.com ([166.70.13.69]) by in02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kiW0b-00CgXw-P3; Thu, 26 Nov 2020 22:09:26 -0700 Received: from localhost (localhost [127.0.0.1]) by mta5.zcs.xmission.com (Postfix) with ESMTP id 8993F12806BE; Thu, 26 Nov 2020 22:09:25 -0700 (MST) X-Amavis-Modified: Mail body modified (using disclaimer) - mta5.zcs.xmission.com Received: from mta5.zcs.xmission.com ([127.0.0.1]) by localhost (mta5.zcs.xmission.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jz8AZr5VcbdF; Thu, 26 Nov 2020 22:09:25 -0700 (MST) Received: from [10.0.10.142] (c-174-52-16-57.hsd1.ut.comcast.net [174.52.16.57]) by mta5.zcs.xmission.com (Postfix) with ESMTPSA id 4E018128066C; Thu, 26 Nov 2020 22:09:25 -0700 (MST) To: freebsd-current@freebsd.org Cc: kib@freebsd.org From: Rebecca Cran Message-ID: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> Date: Thu, 26 Nov 2020 22:09:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 Content-Language: en-US X-XM-SPF: eid=1kiW0b-00CgXw-P3; ; ; mid=<2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com>; ; ; hst=in02.mta.xmission.com; ; ; ip=166.70.13.69; ; ; frm=rebecca@bsdio.com; ; ; spf=none X-SA-Exim-Connect-IP: 166.70.13.69 X-SA-Exim-Mail-From: rebecca@bsdio.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa08.xmission.com X-Spam-Level: *** X-Spam-Status: No, score=3.5 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,HTML_MESSAGE,LotsOfNums_01,TO_NO_BRKTS_PCNT, XM_B_Unicode autolearn=disabled version=3.4.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * 0.0 XM_B_Unicode BODY: Testing for specific types of unicode * 1.2 LotsOfNums_01 BODY: Lots of long strings of numbers * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa08 1397; IP=ok Body=1 Fuz1=1] [Fuz2=1] * 2.5 TO_NO_BRKTS_PCNT To: lacks brackets + percentage X-Spam-DCC: XMission; sa08 1397; IP=ok Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ***;freebsd-current@freebsd.org X-Spam-Relay-Country: X-Spam-Timing: total 443 ms - load_scoreonly_sql: 0.04 (0.0%), signal_user_changed: 12 (2.8%), b_tie_ro: 10 (2.3%), parse: 1.47 (0.3%), extract_message_metadata: 22 (4.9%), get_uri_detail_list: 3.1 (0.7%), tests_pri_-1000: 4.7 (1.1%), tests_pri_-950: 1.43 (0.3%), tests_pri_-900: 1.22 (0.3%), tests_pri_-90: 79 (17.9%), check_bayes: 77 (17.4%), b_tokenize: 10 (2.3%), b_tok_get_all: 8 (1.7%), b_comp_prob: 2.3 (0.5%), b_tok_touch_all: 53 (11.9%), b_finish: 1.42 (0.3%), tests_pri_0: 307 (69.3%), check_dkim_signature: 0.56 (0.1%), check_dkim_adsp: 37 (8.3%), poll_dns_idle: 35 (7.8%), tests_pri_10: 2.2 (0.5%), tests_pri_500: 9 (1.9%), rewrite_mail: 0.00 (0.0%) Subject: panic shortly after boot when amdgpu.ko is loaded (fpu?) X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) X-Rspamd-Queue-Id: 4Cj2jj44mwz4bLB X-Spamd-Bar: - X-Spamd-Result: default: False [-1.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[bsdio.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_LOW(-0.10)[166.70.13.233:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RECEIVED_SPAMHAUS_PBL(0.00)[174.52.16.57:received]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:6315, ipnet:166.70.0.0/16, country:US]; ARC_NA(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; R_DKIM_ALLOW(-0.20)[bsdio.com:s=xmission]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[166.70.13.233:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[bsdio.com]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[166.70.13.233:from:127.0.2.255]; R_SPF_NA(0.00)[no SPF record]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 05:09:30 -0000 I have a Threadripper 2990WX system that I recently installed an AMD Radeon Pro W5700 into. It runs fine unless I load the amdgpu driver, at which point it panics several seconds after boot: I have enough time to login and run a few commands, but even if I just leave it it'll panic.  I'm running: FreeBSD photon.int.bluestop.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 6db1a3e8098-c273171(master): Thu Nov 26 01:26:17 MST 2020 bcran@photon.int.bluestop.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 I rebuilt the drm-current-kmod-5.4.62.g20201109_1 port today. The panic is: Fatal trap 9: general protection fault while in kernel mode cpuid = 24; apic id = 18 instruction pointer = 0x20:0xffffffff81002dcf stack pointer = 0x0:0xfffffe016e6ffaa0 frame pointer = 0x0:0xfffffe016e6ffaa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4372 (hald) trap number = 9 panic: general protection fault cpuid = 24 time = 1606450595 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe016e6ff7b0 vpanic() at vpanic+0x181/frame 0xfffffe016e6ff800 panic() at panic+0x43/frame 0xfffffe016e6ff860 trap_fatal() at trap_fatal+0x387/frame 0xfffffe016e6ff8c0 trap() at trap+0x8e/frame 0xfffffe016e6ff9d0 calltrap() at calltrap+0x8/frame 0xfffffe016e6ff9d0 --- trap 0x9, rip = 0xffffffff81002dcf, rsp = 0xfffffe016e6ffaa0, rbp = 0xfffffe016e6ffaa0 --- fpurestore_xrstor3264() at fpurestore_xrstor3264+0x2f/frame 0xfffffe016e6ffaa0 restore_fpu_curthread() at restore_fpu_curthread+0x85/frame 0xfffffe016e6ffac0 fpudna() at fpudna+0x3a/frame 0xfffffe016e6ffae0 trap() at trap+0x246/frame 0xfffffe016e6ffbf0 calltrap() at calltrap+0x8/frame 0xfffffe016e6ffbf0 --- trap 0x16, rip = 0x80067137f, rsp = 0x7fffffffd8b0, rbp = 0x7fffffffd8f0 --- Uptime: 1m4s Dumping 4193 out of 130894 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% I've uploaded details (core.txt, dmesg.txt etc.) to https://bsdio.com/freebsd/crashes/2020-11-26-amdgpu/ and the vmcore file is available on request. -- Rebecca Cran From owner-freebsd-current@freebsd.org Fri Nov 27 06:09:31 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A3A9F47E511 for ; Fri, 27 Nov 2020 06:09:31 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 4Cj42z40J7z4dN8; Fri, 27 Nov 2020 06:09:31 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x331.google.com with SMTP id d3so1027363wmb.4; Thu, 26 Nov 2020 22:09:31 -0800 (PST) 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=jlt45sx1D0+H323/Ma3CbsmEALmH8VFfuMglRl5QhiI=; b=a5j4spxuNunWZZyMsipxI9FhTfy/4d5sXkI02+IppM3LuzYXU1YJCbSwb/13nUu+O8 kYoSzrHr0i9rNcEs70irypt008KMC8fjdlWtcuxsbzAHphRTS4GY7znxzjsJanzi1Uf1 Bwa8tfjEZE0wJeF6GdaeuSNGIFTQzAaSMN7XnP6tFQeXj+WVu7kuhaYtEY+ntOVuMH5G fG8QVGEZcq96Up5TQsTWv4Ie2dwYls8uKzpNoHkrKNhem2/kXeDhIBbHEflWcufTHE2l dqasW9Ey4a1P+SB+r9oR+r8QKPXw+plBqwHIhLdyO50/euJ2CIA+PRBZuH/bWKPHviLb CRLQ== X-Gm-Message-State: AOAM533nyb0eqBmF/GRfKMoWSksuxguYj+l37o5kdBsOjeQtg6eK5x0L NQLE47EmukiJ6GgGrGpK8gcGpEkPno0= X-Google-Smtp-Source: ABdhPJytHh8XytjdT9t34psuaQ64ZE0Ce0UgcID21ObIEAUzET/S54ZD0Qc7gQxB8K2mR6CrtmEFNw== X-Received: by 2002:a7b:c101:: with SMTP id w1mr7120237wmi.170.1606457368534; Thu, 26 Nov 2020 22:09:28 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id j13sm5880328wrp.70.2020.11.26.22.09.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 22:09:27 -0800 (PST) Date: Fri, 27 Nov 2020 07:09:25 +0100 From: Gary Jennejohn To: Dimitry Andric Cc: FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201127060925.402ab542@ernst.home> In-Reply-To: References: <20201126080724.1cb3a8af@ernst.home> <20201126091206.0dcd5b33@ernst.home> <20201126121623.31ea2cd3@bsd64.grem.de> <20201126182108.4314a0aa@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Cj42z40J7z4dN8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 06:09:31 -0000 On Thu, 26 Nov 2020 19:37:47 +0100 Dimitry Andric wrote: > On 26 Nov 2020, at 19:21, Gary Jennejohn wrote: > > > > On Thu, 26 Nov 2020 10:44:19 -0700 > > Warner Losh wrote: > ... > >>> Example: > >>> > >>> /sbin/camcontrol standby /dev/da2 -v -t 1800 > >> > >> > >> Perfect! I've not had to deal with sata disks that did this since the > >> ataidle days. I looked in camcontrol before suggesting it, but somehow > >> missed this... Glad I posted a bogus answer (sorry about that), since I > >> learned something new. > >> > > > > camcontrol unfortuantely doesn't work with my USB3 enclosures. I > > suspect that the USB3-to-SATA bridge controller is doing its own thing > > and camcontrol has no effect on its behavior. Not tragic for me since > > I use these disks primarily for backups. But for someone using a USB > > attached disk as a primary file system this behavior will definitely be > > a PITA. > > In this case it's about ATA commands being passed though the USB bridge. > Does "camcontrol identify daX" fail in your case too? > > I have used quite a bunch of different USB disks, mostly from WD or > Seagate, and these come with varying qualities of USB-SATA bridges in > them. But all of them work with "camcontrol identify". > camcontrol identify does work. The enclosure I tested has an ASMedia asm1153e bridge in it. This one idles the disk after a few minutes. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Nov 27 06:34:36 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 762B747E9D7 for ; Fri, 27 Nov 2020 06:34:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) 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 4Cj4bw2g2Wz4fq4 for ; Fri, 27 Nov 2020 06:34:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x32a.google.com with SMTP id x22so4152545wmc.5 for ; Thu, 26 Nov 2020 22:34:36 -0800 (PST) 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=PpGwWcxyaaontsgcbscALBWH1Ss329VjyWev2FFQe24=; b=iznqpsSWb/UpowqIhRK9Gx1xsVYa8Dfbl+UMJ3UvhWFNvtjLMZ707c3rrzgEn0zc8M DNefbbiEVM1v+JpA5sEgU7X8dZ+0pG1gjHq/GLTsR8nURvh2xP0majmFEnUduNFdEH1z 8V8JapZyPxgTzv6jQA23FkGQ5Al2D7qQsB0l4Myzy6p8pvANq3lvABdS7FDJd/OOPQSL 2G0kdw7ZxdqrBu4ZTav2TDghWUCUpCvLd0iFiJgqk/G/LdjSiZl4kBxu608H+Yp1YkFK Lk8IIBWUU9mMEHCNMAAn3dcswdKFr5Um0FxdVvg4ZVzuEN6AKQnto+sPt8ZPOSPA7kds OG5w== X-Gm-Message-State: AOAM530tRo1XquLtiB+SYA8gR4c0j51zN9WWvpGr/zwj6RS7kH3Odom8 J+NSi9o8wktOnKV/tNmFHhk= X-Google-Smtp-Source: ABdhPJzx6KcNfywNxgna28nvhv3oZxJiGPOBhk+WrGhwqY7qR0mIs7YBlAQiYRQtxBMfy41fXQPI2w== X-Received: by 2002:a05:600c:229a:: with SMTP id 26mr7267589wmf.100.1606458874827; Thu, 26 Nov 2020 22:34:34 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id j8sm12897083wrx.11.2020.11.26.22.34.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 22:34:34 -0800 (PST) Date: Fri, 27 Nov 2020 07:34:32 +0100 From: Gary Jennejohn To: Michael Gmelin Cc: FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201127063432.590c387f@ernst.home> In-Reply-To: <6D7FEFE1-FF63-4920-9BA8-C8DCBE3D4019@grem.de> References: <20201126182108.4314a0aa@ernst.home> <6D7FEFE1-FF63-4920-9BA8-C8DCBE3D4019@grem.de> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Cj4bw2g2Wz4fq4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 06:34:36 -0000 On Thu, 26 Nov 2020 20:09:41 +0100 Michael Gmelin wrote: > > On 26. Nov 2020, at 19:21, Gary Jennejohn wrote: > > > > ___On Thu, 26 Nov 2020 10:44:19 -0700 > > Warner Losh wrote: > > > >>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote: > >>> > >>> > >>> > >>> On Thu, 26 Nov 2020 10:12:06 +0100 > >>> Gary Jennejohn wrote: > >>> > >>>> On Thu, 26 Nov 2020 01:14:02 -0700 > >>>> Warner Losh wrote: > >>>> > >>>>> On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn > >>>>> wrote: > >>>>>> On Thu, 26 Nov 2020 00:10:40 +0000 > >>>>>> tech-lists wrote: > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> I have a usb3-connected harddrive. dmesg shows this: > >>>>>>> [...] > >>>>>>> da0: Fixed Direct Access SPC-4 SCSI device > >>>>>>> [...] > >>>>>>> > >>>>>>> running current-r367806-arm64 > >>>>>>> > >>>>>>> I think it might be auto-spinning-down or auto-sleeping. It's > >>>>>>> making initial interaction lag of 2-3 seconds. Is there a > >>>>>>> sysctl or something somewhere where I can tell it to never > >>>>>>> sleep? Or is that something I'd need to contact the > >>>>>>> manufacturer about? Or is there an alternative strategy like > >>>>>>> tmpfs. It's not a "green" drive but I guess it might be > >>>>>>> "green" in that it's usb3 powered. > >>>>>>> > >>>>>>> I have vfs.read_max=128 in /etc/sysctl.conf > >>>>>>> zdb has ashift=12 > >>>>>>> > >>>>>>> In case it's relevant, the filesystem on the disk is zfs. Once > >>>>>>> "woken up", inferaction is quick, as expected. > >>>>>>> thanks, > >>>>>>> > >>>>>> > >>>>>> I'd be interested in an answer to this question myself. I have > >>>>>> several USB-attached UFS2 disks which spin down after a few > >>>>>> minutes. > >>>>>> > >>>>>> But, based on some quick searches, this behavior is either a > >>>>>> "feature" of the disk itself - seems common with so-called green > >>>>>> disks - or of the controller in the external enclosure or docking > >>>>>> station. > >>>>>> > >>>>>> This behavior makes sense for drives used with laptops, but for > >>>>>> desktop computers not so useful. > >>>>>> > >>>>>> There are some sysctl's relevant to spindown, but they appear to > >>>>>> only come into play during suspend or shutdown. The ones > >>>>>> relevant to USB which I found are: > >>>>>> > >>>>>> kern.cam.ada.spindown_suspend: Spin down upon suspend > >>>>>> kern.cam.ada.spindown_shutdown: Spin down upon shutdown > >>>>>> > >>>>>> There may be commands which a user can send the disk/controller to > >>>>>> disable this behavior, but I didn't find any with my simple > >>>>>> searches. > >>>>> > >>>>> For SAS drives, there's a mode page that controls this behavior. > >>>>> > >>>>> You might see if the sysutil/ataidle port/package does what you > >>>>> want. > >>>> > >>>> Thanks, Warner, but that port is not in my HEAD ports tree. It's > >>>> also not in the HEAD pkg repository. Many the name has changed? > >>>> > >>>> My disks are all SATA in various USB3 enclosures/docking stations. > >>>> > >>> > >>> I also used ataidle in the past, but it was removed from the ports tree > >>> in 2018 (see MOVED). > >>> > >>> Since then, I'm using camcontrol to set standby timeout values on my > >>> SATA drives, I never tried it on USB devices though. > >>> > >>> Example: > >>> > >>> /sbin/camcontrol standby /dev/da2 -v -t 1800 > >> > >> > >> Perfect! I've not had to deal with sata disks that did this since the > >> ataidle days. I looked in camcontrol before suggesting it, but somehow > >> missed this... Glad I posted a bogus answer (sorry about that), since I > >> learned something new. > >> > > > > camcontrol unfortuantely doesn't work with my USB3 enclosures. I > > suspect that the USB3-to-SATA bridge controller is doing its own thing > > and camcontrol has no effect on its behavior. Not tragic for me since > > I use these disks primarily for backups. But for someone using a USB > > attached disk as a primary file system this behavior will definitely be > > a PITA. > > Does using /dev/passX instead of /dev/daX make a difference? (I > remember I had to do something like this when using smartctl on usb > drives). > No, the bridge controller still idles the disk after a few minutes. But I tried it with camcontrol idle rather than standby. Trying standby does send a ATA STANDBY command to pass0. Maybe that will work. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Nov 27 06:52:17 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E4F7847EFAF for ; Fri, 27 Nov 2020 06:52:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 4Cj50K1qcpz4gcw for ; Fri, 27 Nov 2020 06:52:17 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id w24so5521059wmi.0 for ; Thu, 26 Nov 2020 22:52:17 -0800 (PST) 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:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=ZCTp4f+SscCf3bV0nd13hhE299/L8eSf5n7outJCGkw=; b=Xgmge/p8b0LrRkD3u+peVcEULXhsQaKXSH/TNf2siPcNLCEvqdWK0p2+Q8/qxt+2GV qN4adrp9kP16AzeG5oEobWrVPmLWc+CMEUrJQ1ZXSdS56sGWmKSPrQgjOwvFTjh+sj55 +q3vwXkA3MXHstaHXfZ/B2wD0x1XjSPbzAJJ1BRtJwTwyISdTKzOxhpy+/dM1GUHIWaf mGDNOQ87Xl39pm6fFOhLYiNw0Yq8u5htvsxGIjyy9pw1yHPj3F5uPrbASqzidQ3EvRdS rCtmWfLVzPaqBY4wYhsX2YrvtqLgpggnC8JfZb9hOtNm3a1gW54RdLejwWFS+5nAOlzk lcSg== X-Gm-Message-State: AOAM531fKG3g2jRU2xXZ9X19XJTgptZTdjYNfoF5MMcqClDS4pgs9oYY z7a+V1F9Y0zyt2oDo7S6pSyuxm6tKAo= X-Google-Smtp-Source: ABdhPJwnOdPoGFfTdEi2c9IFHzgqg+SLEbheI9khr14E+FTrn/6xKC9pqwSW7qik4vyeIIGo3QsLpQ== X-Received: by 2002:a05:600c:2110:: with SMTP id u16mr7316654wml.4.1606459935588; Thu, 26 Nov 2020 22:52:15 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id l13sm12584196wrm.24.2020.11.26.22.52.14 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Nov 2020 22:52:14 -0800 (PST) Date: Fri, 27 Nov 2020 07:52:13 +0100 From: Gary Jennejohn To: FreeBSD Current Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: <20201127065213.449920b2@ernst.home> In-Reply-To: <20201127063432.590c387f@ernst.home> References: <20201126182108.4314a0aa@ernst.home> <6D7FEFE1-FF63-4920-9BA8-C8DCBE3D4019@grem.de> <20201127063432.590c387f@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Cj50K1qcpz4gcw X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 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:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; 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]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32c:from]; 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=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.14:received]; 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]; FREEMAIL_REPLYTO(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32c:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32c:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 06:52:18 -0000 On Fri, 27 Nov 2020 07:34:32 +0100 Gary Jennejohn wrote: > On Thu, 26 Nov 2020 20:09:41 +0100 > Michael Gmelin wrote: > > > > On 26. Nov 2020, at 19:21, Gary Jennejohn wrote: > > > > > > ___On Thu, 26 Nov 2020 10:44:19 -0700 > > > Warner Losh wrote: > > > > > >>> On Thu, Nov 26, 2020 at 4:16 AM Michael Gmelin wrote: > > >>> > > >>> > > >>> > > >>> On Thu, 26 Nov 2020 10:12:06 +0100 > > >>> Gary Jennejohn wrote: > > >>> > > >>>> On Thu, 26 Nov 2020 01:14:02 -0700 > > >>>> Warner Losh wrote: > > >>>> > > >>>>> On Thu, Nov 26, 2020 at 1:07 AM Gary Jennejohn > > >>>>> wrote: > > >>>>>> On Thu, 26 Nov 2020 00:10:40 +0000 > > >>>>>> tech-lists wrote: > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I have a usb3-connected harddrive. dmesg shows this: > > >>>>>>> [...] > > >>>>>>> da0: Fixed Direct Access SPC-4 SCSI device > > >>>>>>> [...] > > >>>>>>> > > >>>>>>> running current-r367806-arm64 > > >>>>>>> > > >>>>>>> I think it might be auto-spinning-down or auto-sleeping. It's > > >>>>>>> making initial interaction lag of 2-3 seconds. Is there a > > >>>>>>> sysctl or something somewhere where I can tell it to never > > >>>>>>> sleep? Or is that something I'd need to contact the > > >>>>>>> manufacturer about? Or is there an alternative strategy like > > >>>>>>> tmpfs. It's not a "green" drive but I guess it might be > > >>>>>>> "green" in that it's usb3 powered. > > >>>>>>> > > >>>>>>> I have vfs.read_max=128 in /etc/sysctl.conf > > >>>>>>> zdb has ashift=12 > > >>>>>>> > > >>>>>>> In case it's relevant, the filesystem on the disk is zfs. Once > > >>>>>>> "woken up", inferaction is quick, as expected. > > >>>>>>> thanks, > > >>>>>>> > > >>>>>> > > >>>>>> I'd be interested in an answer to this question myself. I have > > >>>>>> several USB-attached UFS2 disks which spin down after a few > > >>>>>> minutes. > > >>>>>> > > >>>>>> But, based on some quick searches, this behavior is either a > > >>>>>> "feature" of the disk itself - seems common with so-called green > > >>>>>> disks - or of the controller in the external enclosure or docking > > >>>>>> station. > > >>>>>> > > >>>>>> This behavior makes sense for drives used with laptops, but for > > >>>>>> desktop computers not so useful. > > >>>>>> > > >>>>>> There are some sysctl's relevant to spindown, but they appear to > > >>>>>> only come into play during suspend or shutdown. The ones > > >>>>>> relevant to USB which I found are: > > >>>>>> > > >>>>>> kern.cam.ada.spindown_suspend: Spin down upon suspend > > >>>>>> kern.cam.ada.spindown_shutdown: Spin down upon shutdown > > >>>>>> > > >>>>>> There may be commands which a user can send the disk/controller to > > >>>>>> disable this behavior, but I didn't find any with my simple > > >>>>>> searches. > > >>>>> > > >>>>> For SAS drives, there's a mode page that controls this behavior. > > >>>>> > > >>>>> You might see if the sysutil/ataidle port/package does what you > > >>>>> want. > > >>>> > > >>>> Thanks, Warner, but that port is not in my HEAD ports tree. It's > > >>>> also not in the HEAD pkg repository. Many the name has changed? > > >>>> > > >>>> My disks are all SATA in various USB3 enclosures/docking stations. > > >>>> > > >>> > > >>> I also used ataidle in the past, but it was removed from the ports tree > > >>> in 2018 (see MOVED). > > >>> > > >>> Since then, I'm using camcontrol to set standby timeout values on my > > >>> SATA drives, I never tried it on USB devices though. > > >>> > > >>> Example: > > >>> > > >>> /sbin/camcontrol standby /dev/da2 -v -t 1800 > > >> > > >> > > >> Perfect! I've not had to deal with sata disks that did this since the > > >> ataidle days. I looked in camcontrol before suggesting it, but somehow > > >> missed this... Glad I posted a bogus answer (sorry about that), since I > > >> learned something new. > > >> > > > > > > camcontrol unfortuantely doesn't work with my USB3 enclosures. I > > > suspect that the USB3-to-SATA bridge controller is doing its own thing > > > and camcontrol has no effect on its behavior. Not tragic for me since > > > I use these disks primarily for backups. But for someone using a USB > > > attached disk as a primary file system this behavior will definitely be > > > a PITA. > > > > Does using /dev/passX instead of /dev/daX make a difference? (I > > remember I had to do something like this when using smartctl on usb > > drives). > > > > No, the bridge controller still idles the disk after a few minutes. > > But I tried it with camcontrol idle rather than standby. Trying > standby does send a ATA STANDBY command to pass0. Maybe that will > work. > Now I see that I misunderstood the meaning of the -t flag. Using the -v flag I noticed that using -t 0 actually sets the timeout to only 30 seconds. I've now tried the idle and standby commands with -t 600 (10 minutes). So, I'll have to wait and see whether that works. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Nov 27 08:29:20 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9565D4A1C85 for ; Fri, 27 Nov 2020 08:29:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 4Cj78H4Cdrz4kyj for ; Fri, 27 Nov 2020 08:29:19 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D44FC5C0049 for ; Fri, 27 Nov 2020 03:29:18 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Nov 2020 03:29:18 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehfedguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehgtderre dttddvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshesiiih gihsthdrnhgvtheqnecuggftrfgrthhtvghrnhepvefghffftdefkeelleehtdejledvhf dvgeeijeevfffguddvhfetgeejueejueeinecukfhppeekvddrjedtrdeluddruddtuden ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthh dqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 370F93280063 for ; Fri, 27 Nov 2020 03:29:18 -0500 (EST) Date: Fri, 27 Nov 2020 08:29:16 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: firewall choice Message-ID: Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cmc/6UCdWruhTTy3" Content-Disposition: inline X-Rspamd-Queue-Id: 4Cj78H4Cdrz4kyj X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.29:from]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.111.4.29:from]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[66.111.4.29:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 08:29:20 -0000 --cmc/6UCdWruhTTy3 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, What's the "best" [1] choice for firewalling these days, in the list's opin= ion? There's pf, ipf and ipfw. Which is the one being most recently developed/up= dated? I'm used to using pf, have done for over a decade. But OpenBSD's pf has div= erged=20 a lot more from when it first came across. There seems to be a lot more opt= ions. Is FreeBSD's pf being actively developed still? ipfw seems a lot more syntatically complex than pf. Is it more capable also? I know nothing about ipf yet. [1] up-to-date, versatile, low overhead, high throughput, IPv6-able, traffic shaping/queueing thanks, --=20 J. --cmc/6UCdWruhTTy3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/AuNEACgkQs8o7QhFz NAW97hAAl6rawxMigO9Dx4EaB1iMqogdUazHVOD9fpHLqlM3b+TAqFt7dhehrs/u iOdC8uZomZ1HdVNDlP4GqAtMYYatxuNJxSKFS/jQPKzbWHWNaAhzcmcs1sVMOtpB +zGu3zGsxYw0onN6oR/hwlhWCH3wBKNgcfujoJ/CR45bF5GFFr/zuYM1vjAkA0vK DdkXkrt7NkjwHPfo7eMuEzbHjZj7LleQNXNEVT11IcKuFZQyNS35SnUY6enaW/4E P0iD9I+Kp1YMOiTETHZabPdndNLEISFJkqEnz8F1xzbTrvsmlr0ZF/WVyfgp1ZEY FCOIp9At9ikxLxRttt8mQXX5M12ffLXPCc4l0FWK92WIaa++rlvvoyqiPmyaPhbJ e0xoegottiRF/vBRcRjeTkNowsz6h0cWBSdC7PPysITDSFiQ38LbsM6qQ764T+6k JF91xs7w89oCO1i8ftZG51eTZyi0sRrwK2ZdNuyXXCGZCsiR3cNAaSCB+lskEacW AXnaZZhnh/5Mlv90DIrsyruBQFgOLCvwPtFLlBwaMGm3kx+g6feIwyM39nKqPR/N 62MauGgpPmsO3Rlj1bS549zBBbyQSRgJ0n1QCucOgCVMvpfAQ6nROXH0n/Ye7GqM RpK499l92nnl6vbgCnTXewL89/1UVYWddzGHElRqdljgg3bq+zg= =bQKL -----END PGP SIGNATURE----- --cmc/6UCdWruhTTy3-- From owner-freebsd-current@freebsd.org Fri Nov 27 08:57:05 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B1E5E4A24D9 for ; Fri, 27 Nov 2020 08:57:05 +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 4Cj7mK30yHz4nKb for ; Fri, 27 Nov 2020 08:57:05 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1kiZYp-000EeE-Ld for freebsd-current@freebsd.org; Fri, 27 Nov 2020 09:56:59 +0100 Date: Fri, 27 Nov 2020 09:56:59 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: Re: firewall choice Message-ID: <20201127085659.GC74574@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Cj7mK30yHz4nKb X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 08:57:05 -0000 Hi! > What's the "best" [1] choice for firewalling these days, in the list's opinion? At work, we use pf for complex setups, editing the rules using fwbuilder, and ipfw for the simple setups and the quick blocks... -- pi@opsec.eu +49 171 3101372 Now what ? From owner-freebsd-current@freebsd.org Fri Nov 27 09:16:39 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9FE294A3059 for ; Fri, 27 Nov 2020 09:16:39 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cj8Bv1Lqqz4pTH for ; Fri, 27 Nov 2020 09:16:38 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 0AR9Gbrs040390 for ; Fri, 27 Nov 2020 01:16:43 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Fri, 27 Nov 2020 01:16:37 -0800 From: Chris To: freebsd-current@freebsd.org Subject: Re: firewall choice In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: <2653d213518332070e63e2c8e6ec7a4f@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Cj8Bv1Lqqz4pTH X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 09:16:39 -0000 On 2020-11-27 00:29, tech-lists wrote: > Hi, > > What's the "best" [1] choice for firewalling these days, in the list's > opinion? I can't speak for the whole list. ;-) But in my opinion with tables totaling over 150 million IPs. I'm casting a vote for pf(4). It's wildly easy on resources and as fast and flexible as I could ever hope to want. Started using it years ago, and never looked back. :-) > > There's pf, ipf and ipfw. Which is the one being most recently > developed/updated? > I'm used to using pf, have done for over a decade. But OpenBSD's pf has > diverged a > lot more from when it first came across. There seems to be a lot more > options. > Is FreeBSD's pf being actively developed still? Yes. It is actively developed. > > ipfw seems a lot more syntatically complex than pf. Is it more capable also? > I know nothing about ipf yet. > > [1] up-to-date, versatile, low overhead, high throughput, IPv6-able, > traffic shaping/queueing > > thanks, --Chris From owner-freebsd-current@freebsd.org Fri Nov 27 11:17:56 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 782E74A530B for ; Fri, 27 Nov 2020 11:17:56 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) (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 4CjBtq3Kzqz4vwt for ; Fri, 27 Nov 2020 11:17:55 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-ed1-x543.google.com with SMTP id d18so5303362edt.7 for ; Fri, 27 Nov 2020 03:17:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=zZg4jBoN0kaW1w3zyWpUlzvxrio6DvYwssF6C7DDMP0=; b=fLW9xxJVBGjmPQmaK0EsJc5tP2g9uTa4El7EEAGhWVjiTzwFTSpqrMyP7+i57zWONZ Oh7G4YmbF9C87zYW7e1UgT7Cy/Qcvzu9UirmxeZWLlXASiBRwye2rN1PRAnHl56nXW+o Y9OZ1nPf/9Pbb3DnkWarbYaLM/ps+w6RQ6hHX9m2PPE1YHgbrS+YquOeS/pq8VP4OHkV xYnusU1unFL1Fsw5Y9zsBHGYdIIvgks7dsaYCSglbwws6eW+LwAP0gH5BtEDvXn3LTeZ iH7mbeWq02d897BUXjHmNRM4igiFdBOrjt0co4H3/bXoWoJfXgfuxNGmR7g/QGkdZiKj sRmw== X-Gm-Message-State: AOAM533NnEtbmm0T1oIiJ62DvGzucPHO6/KsmgLoWoo/rWd2OhrhFazn kZ67YDPqntgRmngJGUnNabTkmavGB0JaZo5GaEK0ALwEIo85gQ== X-Google-Smtp-Source: ABdhPJzykh3idwfl7PokMQsN1qhtg8dwiLdSr0hvzsr3VoAiBng1gArpDfGaFjqzxFCLCWmyXgp0o63HG7qSEZHeHtY= X-Received: by 2002:aa7:d703:: with SMTP id t3mr6896216edq.375.1606475873750; Fri, 27 Nov 2020 03:17:53 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a50:344f:0:0:0:0:0 with HTTP; Fri, 27 Nov 2020 03:17:53 -0800 (PST) In-Reply-To: References: From: grarpamp Date: Fri, 27 Nov 2020 06:17:53 -0500 Message-ID: Subject: Re: firewall choice To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4CjBtq3Kzqz4vwt X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.995]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::543:from]; 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=20161025]; 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]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::543:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::543:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 11:17:56 -0000 > What's the "best" [1] choice for firewalling these days, in the list's opinion? > There's pf, ipf and ipfw. This question comes up over years. Consider starting and joining with people to create a comparison page on the FreeBSD Wiki, both a feature / capability comparison table, and contextual paragraphs. A mini project like that can help many users and add their researches to it. > [1] up-to-date, versatile, low overhead, high throughput, IPv6-able, > traffic shaping/queueing From owner-freebsd-current@freebsd.org Fri Nov 27 11:22:59 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28BFE4A53B5 for ; Fri, 27 Nov 2020 11:22:59 +0000 (UTC) (envelope-from kp@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjC0g0jvGz3CMc; Fri, 27 Nov 2020 11:22:59 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [5.9.86.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.codepro.be", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id E62E82BC48; Fri, 27 Nov 2020 11:22:58 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id A96E71E64B; Fri, 27 Nov 2020 12:22:57 +0100 (CET) From: "Kristof Provost" To: tech-lists Cc: freebsd-current@freebsd.org Subject: Re: firewall choice Date: Fri, 27 Nov 2020 12:22:56 +0100 X-Mailer: MailMate (1.13.2r5673) Message-ID: <5CEA59B9-7D14-42E6-B2B4-DFCF656F02A9@FreeBSD.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 11:22:59 -0000 On 27 Nov 2020, at 9:29, tech-lists wrote: > What's the "best" [1] choice for firewalling these days, in the list's > opinion? > > There's pf, ipf and ipfw. Which is the one being most recently > developed/updated? > I'm used to using pf, have done for over a decade. But OpenBSD's pf > has diverged a lot more from when it first came across. There seems to > be a lot more options. > Is FreeBSD's pf being actively developed still? > All three are actively maintained and grow new features from time to time. > [1] up-to-date See above. All three are actively maintained. > low overhead, high throughput I believe ipfw currently performs best. I can’t rank ipf and pf, because I’ve not seen benchmarks for ipf. > IPv6-able, All three. > traffic shaping/queueing Mostly ipfw, because dummynet. pf has ALTQ, but that has more limitations than dummynet. I think ipf doesn’t do shaping, but I may be mistaken about that. Best regards, Kristof From owner-freebsd-current@freebsd.org Fri Nov 27 11:29:15 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7A844A58A0 for ; Fri, 27 Nov 2020 11:29:15 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) 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 4CjC7v5jhhz3CqC; Fri, 27 Nov 2020 11:29:15 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id CB5B6260206; Fri, 27 Nov 2020 12:29:13 +0100 (CET) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) To: Rebecca Cran , freebsd-current@freebsd.org Cc: kib@freebsd.org References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> From: Hans Petter Selasky Message-ID: Date: Fri, 27 Nov 2020 12:29:06 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4CjC7v5jhhz3CqC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 11:29:16 -0000 On 11/27/20 6:09 AM, Rebecca Cran wrote: > I have a Threadripper 2990WX system that I recently installed an AMD > Radeon Pro W5700 into. It runs fine unless I load the amdgpu driver, at > which point it panics several seconds after boot: I have enough time to > login and run a few commands, but even if I just leave it it'll panic. > I'm running: > > > FreeBSD photon.int.bluestop.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 > 6db1a3e8098-c273171(master): Thu Nov 26 01:26:17 MST 2020 > bcran@photon.int.bluestop.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > amd64 > > > I rebuilt the drm-current-kmod-5.4.62.g20201109_1 port today. > > > The panic is: > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 24; apic id = 18 > instruction pointer    = 0x20:0xffffffff81002dcf > stack pointer            = 0x0:0xfffffe016e6ffaa0 > frame pointer            = 0x0:0xfffffe016e6ffaa0 > code segment        = base 0x0, limit 0xfffff, type 0x1b >             = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags    = interrupt enabled, resume, IOPL = 0 > current process        = 4372 (hald) > trap number        = 9 > panic: general protection fault > cpuid = 24 > time = 1606450595 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe016e6ff7b0 > vpanic() at vpanic+0x181/frame 0xfffffe016e6ff800 > panic() at panic+0x43/frame 0xfffffe016e6ff860 > trap_fatal() at trap_fatal+0x387/frame 0xfffffe016e6ff8c0 > trap() at trap+0x8e/frame 0xfffffe016e6ff9d0 > calltrap() at calltrap+0x8/frame 0xfffffe016e6ff9d0 > --- trap 0x9, rip = 0xffffffff81002dcf, rsp = 0xfffffe016e6ffaa0, rbp = > 0xfffffe016e6ffaa0 --- > fpurestore_xrstor3264() at fpurestore_xrstor3264+0x2f/frame > 0xfffffe016e6ffaa0 > restore_fpu_curthread() at restore_fpu_curthread+0x85/frame > 0xfffffe016e6ffac0 > fpudna() at fpudna+0x3a/frame 0xfffffe016e6ffae0 > trap() at trap+0x246/frame 0xfffffe016e6ffbf0 > calltrap() at calltrap+0x8/frame 0xfffffe016e6ffbf0 > --- trap 0x16, rip = 0x80067137f, rsp = 0x7fffffffd8b0, rbp = > 0x7fffffffd8f0 --- > Uptime: 1m4s > Dumping 4193 out of 130894 > MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > > I've uploaded details (core.txt, dmesg.txt etc.) to > https://bsdio.com/freebsd/crashes/2020-11-26-amdgpu/ and the vmcore file > is available on request. > Hi, Is the problem always triggered by hald? If you disable hald in rc.conf, does the system run for a longer period of time? --HPS From owner-freebsd-current@freebsd.org Fri Nov 27 14:58:04 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F24224A9604 for ; Fri, 27 Nov 2020 14:58:04 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 4CjHmq6tDQz3NhX for ; Fri, 27 Nov 2020 14:58:03 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E3747E20 for ; Fri, 27 Nov 2020 09:58:01 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 27 Nov 2020 09:58:02 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehgedgjeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurddutddu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtg hhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 1DEEA3064AB0 for ; Fri, 27 Nov 2020 09:58:01 -0500 (EST) Date: Fri, 27 Nov 2020 14:57:59 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: firewall choice Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PYCCYOZtYvv1w6NF" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4CjHmq6tDQz3NhX X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.20:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.20:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.20:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 14:58:05 -0000 --PYCCYOZtYvv1w6NF Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 27, 2020 at 06:17:53AM -0500, grarpamp wrote: >> What's the "best" [1] choice for firewalling these days, in the list's o= pinion? >> There's pf, ipf and ipfw. > >This question comes up over years. > >Consider starting and joining with people to create >a comparison page on the FreeBSD Wiki, >both a feature / capability comparison table, >and contextual paragraphs. >A mini project like that can help many users >and add their researches to it. I'd be happy to if I knew where to start/how to start/is there a guide. --=20 J. --PYCCYOZtYvv1w6NF Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/BE+4ACgkQs8o7QhFz NAUrBA/9HlSFFYO3YK+LrC9+MdqP1jt+yxb6fNeR3U0g49uD9fhOE65GaJMP9cGN kM9SJCe/mLWZq/R0yYDny4IVqgb4ejATukQWyC8RIOIi4UIcU10Z5wP7Do7gN0iT eRXhsXUvYCdcOeotLRHV2HUQKOklRqkCg3zLyarHDdb60aMDubn4fIQPvay7al1v 2jzT7p9mCt+6AG9ufpXbf6fH+up3Quudczy45N1Fs7HU8h146JzbjmsJKes14FIi IBxWknKop/F/BFzhZBFb518Y1DX3G2u740MVe4cx8ibuXJzAocPA/p4aNH+O2FxM Dm7H2wuUHbAFkFtx1Z31WUCGNGCgzHLi9TUQRuSuAezh3gPWXW74IYGCLgQPss4k kyhoAJ1qvUiF6WTfE8rxFMD3MQQjc/ZpHVTUcZsExotqf8+NnTZeqVyIXFyfVQ5/ Ma8Bjl+irkunq3ZRu6uyp2mSdJMT6bM9w0EFGvV8G3Hu0VrlmY2Xh1kPYcdPW38R 6cvULZ983FOVVvEkWy9BPVVZ7j6bXfXhbe9lmXFAT2nsYWiCZm8cGc13oqSlCkSA YuITc0Klk+ybkTZTFg+mDnjSda/7KaA7wQmKwd3UNyw6ss1Iyp72CCGf+HSU/NKa SePz4pmip39AJvdoa/Ie8FvJm9dICM5+yYcojFtXk9seT82480M= =rKgy -----END PGP SIGNATURE----- --PYCCYOZtYvv1w6NF-- From owner-freebsd-current@freebsd.org Fri Nov 27 15:34:30 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 15CF74AAA24 for ; Fri, 27 Nov 2020 15:34:30 +0000 (UTC) (envelope-from ronald-lists@klop.ws) 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 4CjJZr5lYhz3R2H for ; Fri, 27 Nov 2020 15:34:28 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Fri, 27 Nov 2020 16:34:24 +0100 (CET) From: Ronald Klop To: freebsd-current@freebsd.org Message-ID: <1299467375.48.1606491264664@localhost> In-Reply-To: References: Subject: Re: possible usb3-connected hard drive spin down causing lag MIME-Version: 1.0 X-Mailer: Realworks (536.12.97891edf0a6) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4CjJZr5lYhz3R2H X-Spamd-Bar: - X-Spamd-Result: default: False [-1.50 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[194.109.157.24:from]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(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]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(1.00)[1.000]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[194.109.157.24:from]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; 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]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 15:34:30 -0000 Van: tech-lists Datum: vrijdag, 27 november 2020 04:24 Aan: freebsd-current@freebsd.org Onderwerp: Re: possible usb3-connected hard drive spin down causing lag > > Hi, > > It seems the issue wasn't with the hardware or the connection. > I use mutt and it's the program that was slowing everything down, > and that was down to me using new mutt with my old config. The whole > pause for 5 seconds thing was due to it scanning gigabytes of email each time it woke up. The fix was to review the config and change a couple of settings. Now there's no delay (well there is a bit but only because it's scanning the folders it's told to for new mail). > > But looking at a hardware cause wasn't in vain. On the way to the solution, found a few tips through here that sped up the system generally, and learned a bit. So now I have a *really quick* raspberry pi4 which is rock-solid stable, so thanks :D > > -- > J. > Mind to share these tips, so I can use them on my RPI4? ;-) From owner-freebsd-current@freebsd.org Fri Nov 27 17:09:32 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F4F64ACB16 for ; Fri, 27 Nov 2020 17:09:32 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from out02.mta.xmission.com (out02.mta.xmission.com [166.70.13.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjLhX22Cxz3mCs; Fri, 27 Nov 2020 17:09:32 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from in01.mta.xmission.com ([166.70.13.51]) by out02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1kihFR-00EAAX-S0; Fri, 27 Nov 2020 10:09:29 -0700 Received: from mta4.zcs.xmission.com ([166.70.13.68]) by in01.mta.xmission.com with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.87) (envelope-from ) id 1kihFR-0001Gi-Cq; Fri, 27 Nov 2020 10:09:29 -0700 Received: from localhost (localhost [127.0.0.1]) by mta4.zcs.xmission.com (Postfix) with ESMTP id 34A6E50030C; Fri, 27 Nov 2020 10:09:29 -0700 (MST) X-Amavis-Modified: Mail body modified (using disclaimer) - mta4.zcs.xmission.com Received: from mta4.zcs.xmission.com ([127.0.0.1]) by localhost (mta4.zcs.xmission.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 04fujQjnuS4v; Fri, 27 Nov 2020 10:09:29 -0700 (MST) Received: from [10.0.10.142] (c-174-52-16-57.hsd1.ut.comcast.net [174.52.16.57]) by mta4.zcs.xmission.com (Postfix) with ESMTPSA id 007915006B2; Fri, 27 Nov 2020 10:09:28 -0700 (MST) To: Hans Petter Selasky , freebsd-current@freebsd.org Cc: kib@freebsd.org References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> From: Rebecca Cran Message-ID: <40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com> Date: Fri, 27 Nov 2020 10:09:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-XM-SPF: eid=1kihFR-0001Gi-Cq; ; ; mid=<40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com>; ; ; hst=in01.mta.xmission.com; ; ; ip=166.70.13.68; ; ; frm=rebecca@bsdio.com; ; ; spf=none X-SA-Exim-Connect-IP: 166.70.13.68 X-SA-Exim-Mail-From: rebecca@bsdio.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa08.xmission.com X-Spam-Level: ** X-Spam-Status: No, score=2.0 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,LotsOfNums_01,NICE_REPLY_A,T_TM2_M_HEADER_IN_MSG, TooManyTo_001,XMSubLong,XM_B_Unicode autolearn=disabled version=3.4.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5011] * 0.7 XMSubLong Long Subject * 0.3 TooManyTo_001 Multiple "To" Header Recipients 2x (uncommon) * 0.0 XM_B_Unicode BODY: Testing for specific types of unicode * 1.2 LotsOfNums_01 BODY: Lots of long strings of numbers * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa08 1397; IP=ok Body=1 Fuz1=1] [Fuz2=1] * -0.0 NICE_REPLY_A Looks like a legit reply (A) X-Spam-DCC: XMission; sa08 1397; IP=ok Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: **;Hans Petter Selasky , freebsd-current@freebsd.org X-Spam-Relay-Country: X-Spam-Timing: total 297 ms - load_scoreonly_sql: 0.06 (0.0%), signal_user_changed: 15 (5.0%), b_tie_ro: 12 (4.1%), parse: 1.39 (0.5%), extract_message_metadata: 6 (1.9%), get_uri_detail_list: 0.79 (0.3%), tests_pri_-1000: 3.9 (1.3%), tests_pri_-950: 2.2 (0.7%), tests_pri_-900: 1.83 (0.6%), tests_pri_-90: 98 (32.9%), check_bayes: 96 (32.2%), b_tokenize: 7 (2.4%), b_tok_get_all: 7 (2.2%), b_comp_prob: 2.2 (0.8%), b_tok_touch_all: 75 (25.2%), b_finish: 1.22 (0.4%), tests_pri_0: 156 (52.7%), check_dkim_signature: 0.49 (0.2%), check_dkim_adsp: 40 (13.5%), poll_dns_idle: 34 (11.4%), tests_pri_10: 2.1 (0.7%), tests_pri_500: 7 (2.4%), rewrite_mail: 0.00 (0.0%) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) X-Rspamd-Queue-Id: 4CjLhX22Cxz3mCs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 17:09:32 -0000 On 11/27/20 4:29 AM, Hans Petter Selasky wrote: > > Is the problem always triggered by hald? If you disable hald in > rc.conf, does the system run for a longer period of time? It turns out that disabling ntpd let the system run for a longer period of time - until I ran "sysctl sys" at which point I got a panic. And this time the panic actually implicates amdgpu.ko, which is an improvement: #9  0x0000000000000000 in ?? () #10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count ()    from /boot/modules/amdgpu.ko #11 0xffffffff82a14b80 in sysctl_handle_attr () from /boot/modules/amdgpu.ko #12 0xffffffff80c06cc1 in sysctl_root_handler_locked (oid=0xfffffe02133ff000,     arg1=0xfffffe016e360980, arg2=-8724518803888, req=0xfffffe016e360980,     tracker=0xfffff81099af6280) at /usr/src/sys/kern/kern_sysctl.c:184 #13 0xffffffff80c0610c in sysctl_root (oidp=,     arg1=0xfffff810aa27e650, arg2=-2100190360, req=0xfffffe016e360980)     at /usr/src/sys/kern/kern_sysctl.c:2211 Since it _is_ a problem in amdgpu, I'll stop this thread and re-post on freebsd-x11. -- Rebecca Cran From owner-freebsd-current@freebsd.org Fri Nov 27 18:04:27 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B6EAE4AD90C for ; Fri, 27 Nov 2020 18:04:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 4CjMvt4S0Vz3pTs for ; Fri, 27 Nov 2020 18:04:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D7D39953 for ; Fri, 27 Nov 2020 13:04:24 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Nov 2020 13:04:24 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehgedguddtlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehgtd erredttddvnecuhfhrohhmpehtvggthhdqlhhishhtshcuoehtvggthhdqlhhishhtshes iiihgihsthdrnhgvtheqnecuggftrfgrthhtvghrnheptdehiefgvddufeekkedvtdefvd ettddtkeduvdegveelffdtkeffudejvdfhudetnecukfhppeekvddrjedtrdeluddruddt udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvg gthhdqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 975AC3280066 for ; Fri, 27 Nov 2020 13:04:23 -0500 (EST) Date: Fri, 27 Nov 2020 18:04:21 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: possible usb3-connected hard drive spin down causing lag Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <1299467375.48.1606491264664@localhost> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oI8tY4uKrx8tBVEm" Content-Disposition: inline In-Reply-To: <1299467375.48.1606491264664@localhost> X-Rspamd-Queue-Id: 4CjMvt4S0Vz3pTs X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.998]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.21:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.21:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.21:from:127.0.2.255]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.21:from]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 18:04:27 -0000 --oI8tY4uKrx8tBVEm Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 27, 2020 at 04:34:24PM +0100, Ronald Klop wrote: > >Mind to share these tips, so I can use them on my RPI4? ;-) sure! I'll write up a simple site later, but in summary this is what=20 I've done subsequent to the initial setup. E&OE, if it breaks you=20 get to keep both bits, no guarantees etc etc. In no particular order: 1. in /boot/msdos/config.txt there's this: over_voltage=3D6 arm_freq=3D2000 sdram_freq_min=3D3200 [I use a FLIRC case to keep it cool. you *must* use cooling for this. Max temps I'm seeing under very heavy compiling (it runs poudriere) is 72 degC in 25 degC ambient] 2. /usr/src /usr/ports /usr/local /usr/obj /home /var/cache/ccache are all on the usb3 disk, seperate datasets. 3. swap is 16GB and is the first partition on the usb3 disk 4. for compiling, ccache is a must. 5. set tmp to tmpfs in /etc/fstab. I use 1GB like this: tmpfs /tmp tmpfs rw,mode=3D1777,size=3D1024m 0 0 6. make things like mutt use this /tmp 7. enable powerd and on bootup. Make it almost always use the overclocked speed like this in /etc/rc.conf powerd_enable=3D"YES" powerd_flags=3D"-r 1" This makes it run @ 2GHz always without needing to set something like boost= _turbo. 8. in /etc/sysctl.conf: vfs.read_max=3D128 # default 64 9. compile mutt with kyotocabinet which uses (I think) memory mapping for c= ache lookups things like that. Faster than on-disk. 10. Look up the spec of yr usb3 connected device. Does it have 4k sectors? If it does, if you're using zfs make sure vfs.zfs.min_auto_ashift=3D12 in /etc/sysctl.conf 11. if you do compile stuff it'd be worth using -j3 if you want reasonably = responsive interactive use from the pi while it's compiling. Like I've said, this isn't even guaranteed to work. All I can say is it's whats working on my rpi4/8GB now and I'm very happy with it. --=20 J. --oI8tY4uKrx8tBVEm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/BP50ACgkQs8o7QhFz NAWYhhAAgWr7mCKfra+MkR98XtpvezwvjvMxrSfWCY+F10EvidjWEK3P+T2hWf40 JntTn1o1eWVZ75hDJFv5ITMXcmdVzjx2+SYGMxNlFAsWvD7TZs8pbPX2Ijya3TKK D8vaKkSulf+XLPHDDgV/cSjB0ZgADDCe38oanDNus3CDklHH0srNpUvp8F43o5BV +4hurQy2HCMm+Bgc6hBPLQdt8861CHbS/HPhyTjBxvuG/2zHmrgMzmLQEDBfheG5 4C6jsGWYShaMHYO+PabZPt+3A85OYSJUSN/75A1bYdxVEqaH+mo7hDel4uHSPoIs Lv0qygAsqHBVTp+k25N+koTG8TljC0HfOhj9QxxrVjKTnMSbwo5HeaSdsrLJP6jj bHkPN/cP446/EXVSwhYBEo61GRFWc4XI+NsTx2xxi/dOaOSPekihzteA2w/aiiF8 bYN0xvyT0pI1WH7gNe3jYNda9+pjVCN/kppZ9NELk2Q/WYKe1DmjH3M1L9lh+T/v FHHsel34VXl5YIH8brWztlY3xzApfGLNGxqJovptFfEiOuD3WURX4CVEjDUzNeqb 8v9OhfwSkUSrNzEonI1C0PueDDZOTPfptj2noj2DPzHzvcu8gRbg8HgE9gNPpH3w Av7KEL1YfygmJI+rS6HWhUPzCyrycvaSbvV+YtyPFWg8IA7ZohQ= =maqm -----END PGP SIGNATURE----- --oI8tY4uKrx8tBVEm-- From owner-freebsd-current@freebsd.org Fri Nov 27 18:10:36 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 161804ADBB3 for ; Fri, 27 Nov 2020 18:10:36 +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 4CjN2z3tPyz3ptK for ; Fri, 27 Nov 2020 18:10:35 +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 0ARIA1JS095365 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 27 Nov 2020 20:10:04 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 0ARIA1JS095365 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 0ARIA1B8095363; Fri, 27 Nov 2020 20:10:01 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 27 Nov 2020 20:10:01 +0200 From: Konstantin Belousov To: Rebecca Cran Cc: freebsd-current@freebsd.org Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) Message-ID: References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> 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.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4CjN2z3tPyz3ptK X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 18:10:36 -0000 On Thu, Nov 26, 2020 at 10:09:24PM -0700, Rebecca Cran wrote: > I have a Threadripper 2990WX system that I recently installed an AMD Radeon > Pro W5700 into. It runs fine unless I load the amdgpu driver, at which point > it panics several seconds after boot: I have enough time to login and run a > few commands, but even if I just leave it it'll panic.  I'm running: > > > FreeBSD photon.int.bluestop.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 > 6db1a3e8098-c273171(master): Thu Nov 26 01:26:17 MST 2020 bcran@photon.int.bluestop.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > amd64 > > > I rebuilt the drm-current-kmod-5.4.62.g20201109_1 port today. > > > The panic is: > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 24; apic id = 18 > instruction pointer = 0x20:0xffffffff81002dcf > stack pointer = 0x0:0xfffffe016e6ffaa0 > frame pointer = 0x0:0xfffffe016e6ffaa0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 4372 (hald) > trap number = 9 > panic: general protection fault > cpuid = 24 > time = 1606450595 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe016e6ff7b0 > vpanic() at vpanic+0x181/frame 0xfffffe016e6ff800 > panic() at panic+0x43/frame 0xfffffe016e6ff860 > trap_fatal() at trap_fatal+0x387/frame 0xfffffe016e6ff8c0 > trap() at trap+0x8e/frame 0xfffffe016e6ff9d0 > calltrap() at calltrap+0x8/frame 0xfffffe016e6ff9d0 > --- trap 0x9, rip = 0xffffffff81002dcf, rsp = 0xfffffe016e6ffaa0, rbp = 0xfffffe016e6ffaa0 --- > fpurestore_xrstor3264() at fpurestore_xrstor3264+0x2f/frame 0xfffffe016e6ffaa0 > restore_fpu_curthread() at restore_fpu_curthread+0x85/frame 0xfffffe016e6ffac0 > fpudna() at fpudna+0x3a/frame 0xfffffe016e6ffae0 > trap() at trap+0x246/frame 0xfffffe016e6ffbf0 > calltrap() at calltrap+0x8/frame 0xfffffe016e6ffbf0 > --- trap 0x16, rip = 0x80067137f, rsp = 0x7fffffffd8b0, rbp = 0x7fffffffd8f0 --- > Uptime: 1m4s > Dumping 4193 out of 130894 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > > I've uploaded details (core.txt, dmesg.txt etc.) to > https://bsdio.com/freebsd/crashes/2020-11-26-amdgpu/ and the vmcore file is > available on request. And what is the instruction at 0xffffffff81002dcf ? From owner-freebsd-current@freebsd.org Fri Nov 27 18:19:49 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B41694ADEAE for ; Fri, 27 Nov 2020 18:19:49 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) 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 4CjNFc6w7pz3qnT; Fri, 27 Nov 2020 18:19:48 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32f.google.com with SMTP id 10so5854407wml.2; Fri, 27 Nov 2020 10:19:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=/0tsIRa22Jxk4ATMRJfHxhgTiOIf6JPbBSXs+qSIqyg=; b=nac1dP6RM4xjQt1O/l/87pgG+jFlTwtZIIz8Ii4rgD3Gr2J4R/ugoRU6/tumhm+eis VQvMZci+4lGf3nTBeh95ZacsZ+vuJSpI8jtyZdMQdqLKamV1l4cMatur3oxA1hQUE29+ pU6H/pZfRA+nalfnbWC5X9P/Sgk4RGra130msAcDodS8pFXwSfq208cNgJDvtabDvin7 dHVtc97CX+ZgsBJX2Qy/RDt9dKE5Qb/GWoArEHhknxao+UJr3uqIAN5h+xrVnY0SbHrN LvgryboRi4V8OKqmbGKUdTghlbpsgjwRe+gblUYSAWX0WY403qogKcMPxg5JlU7hE7K/ WOIQ== X-Gm-Message-State: AOAM530a7Fl6uUSCbbXYM+v74aV93RCmmfqz/do2RMsloqdDUCI8d3Rr HZe58J2HTnlmq11ncvKAuslebpMras3C/Q== X-Google-Smtp-Source: ABdhPJxJEK60jZ7RrBaqjRg5t2vDgXzZ3Or01GY23Q3DdRccMnOm4e6C7eBwjfBS8I2YoGWmlZCKJw== X-Received: by 2002:a1c:2e48:: with SMTP id u69mr10551508wmu.30.1606501187205; Fri, 27 Nov 2020 10:19:47 -0800 (PST) Received: from [192.168.1.11] (79-66-147-78.dynamic.dsl.as9105.com. [79.66.147.78]) by smtp.gmail.com with ESMTPSA id l11sm13350680wmh.46.2020.11.27.10.19.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Nov 2020 10:19:46 -0800 (PST) Subject: Re: suspend/resume versus OpenZFS on USB From: Graham Perrin To: FreeBSD Current , Matthew Macy , Ryan Moeller Cc: Hans Petter Selasky References: <6824e9f5-0496-a9ba-9cf2-01a6c8b34a4e@selasky.org> <24c4f60d-d937-7763-9cea-697de75109a6@gmail.com> <7cd8c682-0c4b-c332-c6de-d17dccbd9672@selasky.org> Message-ID: Date: Fri, 27 Nov 2020 18:19:45 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4CjNFc6w7pz3qnT X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RECEIVED_SPAMHAUS_PBL(0.00)[79.66.147.78:received]; FROM_EQ_ENVFROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::32f:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::32f:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32f:from]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 18:19:49 -0000 On 05/09/2020 18:18, Graham Perrin wrote: > On 05/09/2020 10:26, Hans Petter Selasky wrote: >> On 2020-09-05 11:00, Graham Perrin wrote: >>> On 04/09/2020 09:01, Hans Petter Selasky wrote: >>>> On 2020-09-04 01:42, Graham Perrin wrote: >>>>> This week for the first time I toyed with OpenZFS on a USB device: >>>>> a mobile hard disk drive connected to the dock of an HP EliteBook >>>>> 8570p. >>>>> >>>>> A light test, with the pool imported but not writing to the >>>>> dataset at suspend time. >>>>> >>>>> At resume time (22:31), the device was still physically connected >>>>> but the pool suffered an I/O failure (and the keyboard and >>>>> trackball on USB were unusable). >>> … >>>> We need output from "procstat -akk" to see where ZFS/USB is hanging. >>>> >>>> --HPS >>> >>> For test purposes I reproduced the behaviour with a different >>> device, a USB flash drive (connected to the same dock). >>> >>> Attached: >>> >>> 2020-09-05 09:27:55 procstat -akk.txt >>> >>> – output from procstat -akk >>> >>> 2020-09-05 09:17:59 suspend 09:26:49 resume.txt >>> >>> – the output in context. >>> >>> Thank you >>> >>> Graham >>> >>> >> >> Hi, >> >> USB is not hanging. >> >> It looks like a problem with USB resume, that no devices are >> recognized, until you re-plug them ... >> >> --HPS > > Hi > > If I export the pool before suspend, no problem at resume time. > > … Please Is there any way to avoid the need to export before suspending the computer? Might there be a future improvement to support for USB? Thanks From owner-freebsd-current@freebsd.org Fri Nov 27 18:40:27 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 377374AE803 for ; Fri, 27 Nov 2020 18:40:27 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from out02.mta.xmission.com (out02.mta.xmission.com [166.70.13.232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjNjQ0VYdz3rXg for ; Fri, 27 Nov 2020 18:40:25 +0000 (UTC) (envelope-from rebecca@bsdio.com) Received: from in02.mta.xmission.com ([166.70.13.52]) by out02.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kiifP-00EHRu-SB; Fri, 27 Nov 2020 11:40:23 -0700 Received: from mta5.zcs.xmission.com ([166.70.13.69]) by in02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kiifP-00DtMk-1Z; Fri, 27 Nov 2020 11:40:23 -0700 Received: from localhost (localhost [127.0.0.1]) by mta5.zcs.xmission.com (Postfix) with ESMTP id D443A1280588; Fri, 27 Nov 2020 11:40:22 -0700 (MST) X-Amavis-Modified: Mail body modified (using disclaimer) - mta5.zcs.xmission.com Received: from mta5.zcs.xmission.com ([127.0.0.1]) by localhost (mta5.zcs.xmission.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id s673PwK3qubY; Fri, 27 Nov 2020 11:40:22 -0700 (MST) Received: from [10.0.10.142] (c-174-52-16-57.hsd1.ut.comcast.net [174.52.16.57]) by mta5.zcs.xmission.com (Postfix) with ESMTPSA id A746B1280486; Fri, 27 Nov 2020 11:40:22 -0700 (MST) To: Konstantin Belousov Cc: freebsd-current@freebsd.org References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> From: Rebecca Cran Message-ID: <99435773-d1e0-562b-52e1-df9c392c61c3@bsdio.com> Date: Fri, 27 Nov 2020 11:40:21 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-XM-SPF: eid=1kiifP-00DtMk-1Z; ; ; mid=<99435773-d1e0-562b-52e1-df9c392c61c3@bsdio.com>; ; ; hst=in02.mta.xmission.com; ; ; ip=166.70.13.69; ; ; frm=rebecca@bsdio.com; ; ; spf=none X-SA-Exim-Connect-IP: 166.70.13.69 X-SA-Exim-Mail-From: rebecca@bsdio.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa07.xmission.com X-Spam-Level: * X-Spam-Status: No, score=1.9 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,LotsOfNums_01,NICE_REPLY_A,T_TM2_M_HEADER_IN_MSG, XMSubLong,XM_B_SpammyWords,XM_B_Unicode autolearn=disabled version=3.4.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * 0.7 XMSubLong Long Subject * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * 1.2 LotsOfNums_01 BODY: Lots of long strings of numbers * 0.0 XM_B_Unicode BODY: Testing for specific types of unicode * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa07 1397; IP=ok Body=1 Fuz1=1] [Fuz2=1] * 0.2 XM_B_SpammyWords One or more commonly used spammy words * -0.0 NICE_REPLY_A Looks like a legit reply (A) X-Spam-DCC: XMission; sa07 1397; IP=ok Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: *;Konstantin Belousov X-Spam-Relay-Country: X-Spam-Timing: total 415 ms - load_scoreonly_sql: 0.04 (0.0%), signal_user_changed: 11 (2.5%), b_tie_ro: 9 (2.2%), parse: 0.95 (0.2%), extract_message_metadata: 4.1 (1.0%), get_uri_detail_list: 0.96 (0.2%), tests_pri_-1000: 2.5 (0.6%), tests_pri_-950: 1.28 (0.3%), tests_pri_-900: 1.03 (0.2%), tests_pri_-90: 94 (22.6%), check_bayes: 92 (22.2%), b_tokenize: 7 (1.6%), b_tok_get_all: 6 (1.5%), b_comp_prob: 1.93 (0.5%), b_tok_touch_all: 74 (17.8%), b_finish: 0.94 (0.2%), tests_pri_0: 283 (68.2%), check_dkim_signature: 0.89 (0.2%), check_dkim_adsp: 43 (10.4%), poll_dns_idle: 32 (7.8%), tests_pri_10: 3.0 (0.7%), tests_pri_500: 12 (2.9%), rewrite_mail: 0.00 (0.0%) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) X-Rspamd-Queue-Id: 4CjNjQ0VYdz3rXg X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[166.70.13.232:from]; DKIM_TRACE(0.00)[bsdio.com:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[166.70.13.232:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[166.70.13.232:from]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:6315, ipnet:166.70.0.0/16, country:US]; ARC_NA(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; RCVD_COUNT_FIVE(0.00)[6]; R_DKIM_ALLOW(-0.20)[bsdio.com:s=xmission]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bsdio.com]; SPAMHAUS_ZRD(0.00)[166.70.13.232:from:127.0.2.255]; RECEIVED_SPAMHAUS_PBL(0.00)[174.52.16.57:received]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 18:40:27 -0000 On 11/27/20 11:10 AM, Konstantin Belousov wrote: > And what is the instruction at 0xffffffff81002dcf ? I got a much clearer panic by running "sysctl sys" which shows it's more likely a problem for the amdgpu folks and not an underlying FreeBSD problem. #7  0xffffffff810295cd in trap (frame=0xfffffe016e360760)     at /usr/src/sys/amd64/amd64/trap.c:398 #8  #9  0x0000000000000000 in ?? () #10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count ()    from /boot/modules/amdgpu.ko #11 0xffffffff82a14b80 in sysctl_handle_attr () from /boot/modules/amdgpu.ko #12 0xffffffff80c06cc1 in sysctl_root_handler_locked (oid=0xfffffe02133ff000,     arg1=0xfffffe016e360980, arg2=-8724518803888, req=0xfffffe016e360980,     tracker=0xfffff81099af6280) at /usr/src/sys/kern/kern_sysctl.c:184 #13 0xffffffff80c0610c in sysctl_root (oidp=,     arg1=0xfffff810aa27e650, arg2=-2100190360, req=0xfffffe016e360980)     at /usr/src/sys/kern/kern_sysctl.c:2211 #14 0xffffffff80c06783 in userland_sysctl (td=0xfffffe00f00b6100,     name=0xfffffe016e360a40, namelen=4, old=,     oldlenp=, inkernel=, new=0x0, newlen=0,     retval=0xfffffe016e360aa8, flags=0)     at /usr/src/sys/kern/kern_sysctl.c:2368 #15 0xffffffff80c065cf in sys___sysctl (td=0xfffffe00f00b6100,     uap=0xfffffe00f00b64e8) at /usr/src/sys/kern/kern_sysctl.c:2241 #16 0xffffffff8102a81c in syscallenter (td=0xfffffe00f00b6100)     at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:189 #17 amd64_syscall (td=0xfffffe00f00b6100, traced=0)     at /usr/src/sys/amd64/amd64/trap.c:1156 #18 #19 0x00000008003819ca in ?? () Backtrace stopped: Cannot access memory at address 0x7fffffffb618 (kgdb) From owner-freebsd-current@freebsd.org Fri Nov 27 21:16:46 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0AADC468FDB for ; Fri, 27 Nov 2020 21:16:46 +0000 (UTC) (envelope-from lwhsu@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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjS9n6tSxz4SvT for ; Fri, 27 Nov 2020 21:16:45 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: lwhsu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id D848D5BC for ; Fri, 27 Nov 2020 21:16:45 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by mail-yb1-f169.google.com with SMTP id x17so5621396ybr.8 for ; Fri, 27 Nov 2020 13:16:45 -0800 (PST) X-Gm-Message-State: AOAM530G7uzCTmMmrmROWXbvbQFhFe0rGP3GDp8vzgyh/Q+ev7GTMSmm cfwTll2uy7FlPINZCgDFV8zm+X0v75LaCHC4dWU= X-Google-Smtp-Source: ABdhPJzPGjTtzDGfTDJTn3l/AgD9YJ39VzEJ/+sl06khzk9bWMoM/OUiTHzCXGWIqd/EA1p7kBNCpShW0HJijJq3wcI= X-Received: by 2002:a25:209:: with SMTP id 9mr15992417ybc.127.1606511805145; Fri, 27 Nov 2020 13:16:45 -0800 (PST) MIME-Version: 1.0 References: <0b2f0f19-490b-4bb5-52b3-201e24ebeaee@anduin.net> <39ceba1e-3e9e-a861-ab71-d376969990c4@FreeBSD.org> <2162563.mfXeX5GmMH@carbon8.weirdr.net> In-Reply-To: <2162563.mfXeX5GmMH@carbon8.weirdr.net> From: Li-Wen Hsu Date: Sat, 28 Nov 2020 05:16:33 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Wake from sleep kinda broken-ish? (ThinkPad Carbon X1 6th gen) To: =?UTF-8?Q?Eirik_=C3=98verby?= Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 21:16:46 -0000 On Mon, Oct 12, 2020 at 5:22 PM Eirik =C3=98verby wrote= : > > On Wednesday, September 16, 2020 9:05:43 AM CEST Warner Losh wrote: > > I too can report this for my Lenovo Yoga running code as of September 1= 3, > > but with manu's latest drm... It used to work fine, but my last build = on > > the system was from May. Most likely a new panic in that code path, but > > I've not chased down further... > > So I got a gen8 to play with, and the list of grievances is long - but I = have > one observation that may be of interest: > The gen8 would be usable (at least seemingly so) with a 13-kernel from la= t > 2019 or very early 2020. Then around the end of January - I've bisected i= t > down to around Jan 24, give or take, it would start wedging _hard_ after = a > minute or two of heavy load (compiling, cat /dev/random, that sort of thi= ng). > It was a problem prior to that too but it was _much_ harder to trigger, a= t > least based on my tests this weekend. > > The "solution" is to add > hint.hwpstate_intel.0.disabled=3D"1" > to /boot/loader.conf. This obviously has disastrous impact on battery lif= e. > The emt module takes over, so power management is a lot more rudimentary > (powerd now does nearly nothing, while powerd++ kills interactivity). Bat= tery > life is much shorter than on my gen6, and it gets hotter. > > BUT: This thing - gen8 - would get stuck in the acpi_beep before adding t= his > to loader.conf. After adding the hint, I have not had a single failure wh= en > resuming. It's behaving much better than my gen6. Recently I got an interesting observation: if I suspend with `zzz`, (which is basically doing `acpiconf -s S3`), and resuming by pushing the power button, there is 95% chance of resuming failure. However, if I use close/open the lid to suspend/resume, I haven't hit any failure since last week. I suppose that these 2 suspend/resume methods are basically doing the same thing? My hw.acpi.lid_switch_state sysctl is S3. I have tried suspending with `zzz` then closing the lid, there is about 50% failure rate, but the sample number is very small. Is there any idea about what makes the difference between these 2 suspend/resume methods? I'm running 13.0-CURRENT r367582, with drm-devel-kmod-5.4.62.g20201109 and gpu-firmware-kmod-g20200920. My /boot/loader.conf has hw.i915kms.enable_psr=3D0 but no hint.hwpstate_intel.0.disabled=3D1 Best, Li-Wen From owner-freebsd-current@freebsd.org Fri Nov 27 21:47:54 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 95E81469EAB for ; Fri, 27 Nov 2020 21:47:54 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 4CjSsk3Vrpz4VpQ for ; Fri, 27 Nov 2020 21:47:53 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: by mail-pf1-x42d.google.com with SMTP id n137so5606852pfd.3 for ; Fri, 27 Nov 2020 13:47:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ReA/ZcIFJKzo/tfZ21Z8ZOlJu5CpmgivRFHxgxcCXcw=; b=jCPUAbKdDWpXPx7bm2GN1Vw8arEBGr/Yk7pIZNTuzJjxxljBMK63G3fFHOMoiCP7nS Mn/5EA9FTMihr7lz6ifbQ2mNP686TlK+YOJK4uw4Q3UG7INWCOHH7hnlGzGx7JT7Ggcx uuQRrYCUt+gZZhAPzGyRJwn3LJJldk4VTyS1T5dCJZMnkUyC971q2g5e6lP6fqfj44ZN 3oe3wb6DpIrYji2pjV0+rbaVB8GYeizLnAow2djMoIvT+l6rVA75cTHnhFEBWfRQ+d8D k7Q1++se7NWm0TqP/4QUhPLaNHnthFrv5e2HB74OfnIzPvI+yjJMUpXeZ1UsF8gswL19 zavQ== X-Gm-Message-State: AOAM5335MqbvCN63a7tIXvVlbP74xlbxa5k0t5FWJIvdlWBeyFe4dfzh hAbVYHWXPWUcTh6mKkinGilorxaa1go8VA== X-Google-Smtp-Source: ABdhPJwSjehIASrUkXS87y8+1FRrZ5/jUpUjQC3CGDcdLJtVJsMqPq9v9MrcfqGUTaHJsimo0u5SQg== X-Received: by 2002:a63:1902:: with SMTP id z2mr8414434pgl.308.1606513672745; Fri, 27 Nov 2020 13:47:52 -0800 (PST) Received: from [192.168.1.113] (172-125-77-130.lightspeed.sntcca.sbcglobal.net. [172.125.77.130]) by smtp.gmail.com with ESMTPSA id w18sm8721309pfi.216.2020.11.27.13.47.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Nov 2020 13:47:51 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\)) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) From: Bakul Shah In-Reply-To: <40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com> Date: Fri, 27 Nov 2020 13:47:49 -0800 Cc: Hans Petter Selasky , freebsd-current@freebsd.org, kib@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0075A3F0-C106-4970-B840-0DFAEA29DBC9@iitbombay.org> References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> <40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com> To: Rebecca Cran X-Mailer: Apple Mail (2.3654.20.0.2.21) X-Rspamd-Queue-Id: 4CjSsk3Vrpz4VpQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 21:47:54 -0000 > On Nov 27, 2020, at 9:09 AM, Rebecca Cran wrote: >=20 > On 11/27/20 4:29 AM, Hans Petter Selasky wrote: >>=20 >> Is the problem always triggered by hald? If you disable hald in = rc.conf, does the system run for a longer period of time? >=20 > It turns out that disabling ntpd let the system run for a longer = period of time - until I ran "sysctl sys" at which point I got a panic. >=20 > And this time the panic actually implicates amdgpu.ko, which is an = improvement: >=20 >=20 > #9 0x0000000000000000 in ?? () > #10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count () > from /boot/modules/amdgpu.ko > #11 0xffffffff82a14b80 in sysctl_handle_attr () from = /boot/modules/amdgpu.ko >=20 > #12 0xffffffff80c06cc1 in sysctl_root_handler_locked = (oid=3D0xfffffe02133ff000, > arg1=3D0xfffffe016e360980, arg2=3D-8724518803888, = req=3D0xfffffe016e360980, > tracker=3D0xfffff81099af6280) at = /usr/src/sys/kern/kern_sysctl.c:184 > #13 0xffffffff80c0610c in sysctl_root (oidp=3D, > arg1=3D0xfffff810aa27e650, arg2=3D-2100190360, = req=3D0xfffffe016e360980) > at /usr/src/sys/kern/kern_sysctl.c:2211 >=20 >=20 > Since it _is_ a problem in amdgpu, I'll stop this thread and re-post = on freebsd-x11. FWIW, I am using amdgpu on a Ryzen 5 3500U system on a couple days old -current (r368025). "sysctl sys" complains about "unknown oid 'sys'". I am runing hald & ntpd. I had a few amdgpu related panics initially but they vanished once I added PORTS_MODULES=3Dgraphics/drm-devel-kmod to /etc/src.conf to compile it along with the kernel. I am running GENERIC-NODEBUG. The machine gets rebooted when I install a new kernel (usually once a week). My guess is some weird interaction rather than something in amdgpu. From owner-freebsd-current@freebsd.org Fri Nov 27 23:07:15 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ECC1146B855 for ; Fri, 27 Nov 2020 23:07:15 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 4CjVdG5xxNz4ZQJ for ; Fri, 27 Nov 2020 23:07:14 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: by mail-pf1-x433.google.com with SMTP id b6so5716475pfp.7 for ; Fri, 27 Nov 2020 15:07:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g5HYv8IfJGwABUWxnFGPqN9b/T6trSSsCPV7aNy1I2U=; b=cGqmLNLWtZz4M52oMJNkbsRPNtVUV+M4+8fQ97u6M9zmVMA26Qien7f2hUfua8CbtB mMh7nDdsqEKq3wLdsWbqrTOexIIZYP6QfyFtr+kbzD5PN0RN2gv3sotQ4YOEDFb6KYfI HcLncqur2FAH2ueHn58pqoQYNTo78ncJbrz9FhnO5qug5KLn22AO4rvMXdn9+LES9LMW uD83FM9fZOduLKgjG/i0KP2sTPqV7bSuy4hgGF7mkgx7+7f3W57EJNWjUmk/cO0Nz4UI RnJjO6ZE9V2gwBLqSa3E03pxXqn2jEb76/hhDPeTB7WS86pLeVezyFiYKVwxhbCD12gd X6Lg== X-Gm-Message-State: AOAM533CohlDGE4D9ejUurolJbco9UNtwtTKvHv25src6mDqHjBWNQON ngklNe6wF2k3RBe+yK+PxeeHdg== X-Google-Smtp-Source: ABdhPJyHcB+O2lK7poPG2yIgFkl/wrz1XFoeUse15/e1Kt0HYi1p4vj1VKK4hAaVatuMWOwpcATaHQ== X-Received: by 2002:a17:90a:b114:: with SMTP id z20mr12568136pjq.14.1606518433272; Fri, 27 Nov 2020 15:07:13 -0800 (PST) Received: from [192.168.1.113] (172-125-77-130.lightspeed.sntcca.sbcglobal.net. [172.125.77.130]) by smtp.gmail.com with ESMTPSA id x28sm8872349pfr.186.2020.11.27.15.07.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Nov 2020 15:07:12 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\)) Subject: Re: panic shortly after boot when amdgpu.ko is loaded (fpu?) From: Bakul Shah In-Reply-To: <0075A3F0-C106-4970-B840-0DFAEA29DBC9@iitbombay.org> Date: Fri, 27 Nov 2020 15:07:10 -0800 Cc: Hans Petter Selasky , freebsd-current@freebsd.org, kib@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <916B4D57-6C8A-4510-AE29-5E289717CBCA@iitbombay.org> References: <2a0f9031-a96d-2989-4d6c-a7691c451b74@bsdio.com> <40ac5686-aa96-f9e4-7c9c-5dbe628af49a@bsdio.com> <0075A3F0-C106-4970-B840-0DFAEA29DBC9@iitbombay.org> To: Rebecca Cran X-Mailer: Apple Mail (2.3654.20.0.2.21) X-Rspamd-Queue-Id: 4CjVdG5xxNz4ZQJ X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[iitbombay-org.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::433:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[iitbombay-org.20150623.gappssmtp.com:s=20150623]; FREEFALL_USER(0.00)[bakul]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[iitbombay.org]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::433:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::433:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 23:07:16 -0000 > On Nov 27, 2020, at 1:47 PM, Bakul Shah wrote: >=20 >=20 >=20 >> On Nov 27, 2020, at 9:09 AM, Rebecca Cran wrote: >>=20 >> On 11/27/20 4:29 AM, Hans Petter Selasky wrote: >>>=20 >>> Is the problem always triggered by hald? If you disable hald in = rc.conf, does the system run for a longer period of time? >>=20 >> It turns out that disabling ntpd let the system run for a longer = period of time - until I ran "sysctl sys" at which point I got a panic. >>=20 >> And this time the panic actually implicates amdgpu.ko, which is an = improvement: >>=20 >>=20 >> #9 0x0000000000000000 in ?? () >> #10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count () >> from /boot/modules/amdgpu.ko >> #11 0xffffffff82a14b80 in sysctl_handle_attr () from = /boot/modules/amdgpu.ko >>=20 >> #12 0xffffffff80c06cc1 in sysctl_root_handler_locked = (oid=3D0xfffffe02133ff000, >> arg1=3D0xfffffe016e360980, arg2=3D-8724518803888, = req=3D0xfffffe016e360980, >> tracker=3D0xfffff81099af6280) at = /usr/src/sys/kern/kern_sysctl.c:184 >> #13 0xffffffff80c0610c in sysctl_root (oidp=3D, >> arg1=3D0xfffff810aa27e650, arg2=3D-2100190360, = req=3D0xfffffe016e360980) >> at /usr/src/sys/kern/kern_sysctl.c:2211 >>=20 >>=20 >> Since it _is_ a problem in amdgpu, I'll stop this thread and re-post = on freebsd-x11. >=20 > FWIW, I am using amdgpu on a Ryzen 5 3500U system on a couple days old > -current (r368025). "sysctl sys" complains about "unknown oid 'sys'". > I am runing hald & ntpd. I had a few amdgpu related panics initially > but they vanished once I added > PORTS_MODULES=3Dgraphics/drm-devel-kmod > to /etc/src.conf to compile it along with the kernel. I am running > GENERIC-NODEBUG. The machine gets rebooted when I install a new kernel > (usually once a week). >=20 > My guess is some weird interaction rather than something in amdgpu. To get sysctl sys working I compiled a GENERIC kernel from today's 368108 revision and so far there are no problems. $ sysctl sys.device.drmn0.pcie_replay_count sys.device.drmn0.pcie_replay_count: 0 sysctl -a also works. Last commit log on drm-devel-kmod (the last tiem may be what you're running into): Author: manu Date: Mon Nov 9 13:37:12 2020 +0000 drm-current-kmod/drm-devel-kmod: Update to latest version - Use acpi code from base (thanks to wulf@) - Add radeon/i386 patches (thanks to tilj@) - Translate O_ flags for linuxulator (thanks to Greg V) - Lot of linuxkpi cleanup - Hack for amdgpu when the IP isn't init properly, this happens on one of my laptop with a dGPU. We still don't support it but we don't panic when we load amdgpu From owner-freebsd-current@freebsd.org Fri Nov 27 23:11:46 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ED25746B8FD for ; Fri, 27 Nov 2020 23:11:46 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ej1-x642.google.com (mail-ej1-x642.google.com [IPv6:2a00:1450:4864:20::642]) (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 4CjVkV1GpRz4bD3 for ; Fri, 27 Nov 2020 23:11:45 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-ej1-x642.google.com with SMTP id d17so7764722ejy.9 for ; Fri, 27 Nov 2020 15:11:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=k/4DfvFHbNKYyTM9Z+IWFXFpmqZGHLJSnP92td4MjvE=; b=p55CPEdIfIE8ON8vlIZAOzWrW6SDWQk1aGoje7TDpGSBp/LNi2V4ZLlqSXjC3XQdpV SkGlbNUeD3Bh1deRHSeQlKa+1Q5KOaIZdVtbcbjHqKgXyc56QUcA53seol7ermzHo55/ GhDwT2DYDe6zMf1uwHTQg66RYDWngtlgjuqiqYVL/w3eg5eov/Qz3n4iyKDWw1RZcS8w fAdEEIa8G0JtKSBnm0BqhbE3IjkHQIuj1vXjvJlVF8Xsoa8sGAFr8wcAtF3gLYdJHZHu WSVL7p2fxWOImIULz9KU9sm8eagtcRnAbMsni4s1OmPCPXftPIWt+noznxcdIrke+XBG PN+Q== X-Gm-Message-State: AOAM531XB1JbXBXrAIpBbaDEA3Vp7gnGO9m+uQijycLtdts3FKzgY0yZ It++XdxLkEabPG29IDdTlH4ckis/xhYhsgQHv2P9ZMkhtDpOcQ== X-Google-Smtp-Source: ABdhPJxU9R+L/CQ0G2a1rELGlhb9hhzXTzDyuSvexCEjkUObvltiaVEzoNlLTGj0+v36SXeRYTwQjP2IUZAhiJayEqE= X-Received: by 2002:a17:906:14d:: with SMTP id 13mr2610628ejh.516.1606518704427; Fri, 27 Nov 2020 15:11:44 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a50:344f:0:0:0:0:0 with HTTP; Fri, 27 Nov 2020 15:11:43 -0800 (PST) In-Reply-To: References: From: grarpamp Date: Fri, 27 Nov 2020 18:11:43 -0500 Message-ID: Subject: Re: firewall choice To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4CjVkV1GpRz4bD3 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.97 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.97)[-0.971]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::642:from]; 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=20161025]; 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]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::642:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::642:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 23:11:47 -0000 >>> What's the "best" [1] choice for firewalling these days >>> There's pf, ipf and ipfw. >> >>This question comes up over years. >> >>Consider starting and joining with people to create >>a comparison page on the FreeBSD Wiki, >>both a feature / capability comparison table, >>and contextual paragraphs. >>A mini project like that can help many users >>and add their researches to it. > > I'd be happy to if I knew where to start/how to start/is there a guide. Starting a wiki is here... https://wiki.freebsd.org/ https://wiki.freebsd.org/AboutWiki Which falls under larger handbook doc area... https://lists.freebsd.org/mailman/listinfo/freebsd-doc Much of comparison would pull from man pages. Could also come from posting a call for input / announce to questions, hackers, forum, etc. Wiki should not duplicate admin info from here... https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html But would cover this handbook bullet item that is not actually covered in the handbook (which could link out to the wiki page for that)... "- The differences between the firewalls built into FreeBSD." A full comparison would also want to note and point to upstream sources, and have a table of which filter systems are supported going forward in each unix OS (the *BSD flavors including DragonFly ipfw3 pf, Linux netfilter+nftables, Illumos). And cover layer2 capabilities, switching, bridging, ipv6, nat, rate limits / shape / queue, proxy, arbitrary rewriting and routing hooks, etc. NetBSD where ipf was last released has deprecated both ipf and pf in favor of npf. While upstream devel and maintenance on ipf has died, pf still lives on at OpenBSD. Anyone can start. Have fun. From owner-freebsd-current@freebsd.org Fri Nov 27 23:43:31 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 12F2346CA1A for ; Fri, 27 Nov 2020 23:43:31 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 4CjWR574Jjz4cK6 for ; Fri, 27 Nov 2020 23:43:29 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A04BF2BD for ; Fri, 27 Nov 2020 18:43:27 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Nov 2020 18:43:27 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehhedgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucfkphepkedvrdejtddrledurddutddu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthgvtg hhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: from rpi4.local (fws.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id C32D43280060 for ; Fri, 27 Nov 2020 18:43:26 -0500 (EST) Date: Fri, 27 Nov 2020 23:43:24 +0000 From: tech-lists To: freebsd-current@freebsd.org Subject: Re: firewall choice Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HTET7FAZEg1m4Ux1" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4CjWR574Jjz4cK6 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.25:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.25:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.25:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm1,messagingengine.com:s=fm1]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.25:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 23:43:31 -0000 --HTET7FAZEg1m4Ux1 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 27, 2020 at 06:11:43PM -0500, grarpamp wrote: [...lots...] OK thanks for that looks like I've got some reading to do --=20 J. --HTET7FAZEg1m4Ux1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAl/BjxMACgkQs8o7QhFz NAX7mA/+OSn7cQh3xXozIdzeeNYXmUCW1W/B6qqZ0UKDuXs7aDnSbnXO9O35uV/I ZvTnikZv3aCC1RpV/Nw3JfPbZbzFM+6X1EKUJuAvzIb2sDWmY+yXXZix4iZ6xLZH mcnnsTXVITCzv24B0Pm4O6D9KH1XUjjDrgYTQr9u/uEBAxlid7cFtRrEzsrBSGiV LzhTac0mB60W/qqW9lRg16JyP5/jtOVHOiib6kYAVVSma9FIoZcjtBjduU+t3C26 sCWjd4I447NS6ObcxdBCm1q/ULcuwqOS1IEbxTmwWO+99l3yzL7okWhiil+FeRZE FgXFwvKQ9e2g0+G9MlsJgp23q/0LCpIWMBoAom6YqP5hKPJLSgc0tioo6V3GvU+k HMYxaG1yFJ9imSbVnj8vUeoIxVC70urXpCH34rUMKBWR83p2TIaJfN5S5nZ2tDlY tUj5DlI111dHTg2ryQP1fDXfGeEINx1OIYRQNKtZF/CjXGlKvLiEf3XQlLa8pSXp fMuQvVCiB2mnaBze8qwQmkI2iGjdJMUtezb2JkNDEhhuFbpiOopSRzSYD9tD4azo lgOp8ZmKDKvzJ5NSHeE7svKOj8rqUWO9N20p5G7iJAV22+EHT13WthJgAGrkTwY5 hTdtRI2xp2QEd7Z9EfYBssEvgiiv2I32u9WGTsC8Sdbh/RaJMeA= =1z9p -----END PGP SIGNATURE----- --HTET7FAZEg1m4Ux1-- From owner-freebsd-current@freebsd.org Sat Nov 28 06:26:17 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F1A84774EA for ; Sat, 28 Nov 2020 06:26:17 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjhMq6NQlz3Fr2 for ; Sat, 28 Nov 2020 06:26:15 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.229.168]) by shaw.ca with ESMTPA id itgSk9xTJbYg3itgTkgt59; Fri, 27 Nov 2020 23:26:13 -0700 X-Authority-Analysis: v=2.4 cv=Q4RsX66a c=1 sm=1 tr=0 ts=5fc1ed85 a=7AlCcx2GqMg+lh9P3BclKA==:117 a=7AlCcx2GqMg+lh9P3BclKA==:17 a=xqWC_Br6kY4A:10 a=kj9zAlcOel0A:10 a=nNwsprhYR40A:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=EkcXrb_YAAAA:8 a=i3EhSejfWCEPKW0IYRMA:9 a=CjuIK1q_8ugA:10 a=VssJInpMtHUA:10 a=3-a-VZz4A_wA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [IPv6:fc00:1:1:1::5b]) by spqr.komquats.com (Postfix) with ESMTPS id F3B5A1CAD; Fri, 27 Nov 2020 22:26:10 -0800 (PST) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 0AS6QAbC032721; Fri, 27 Nov 2020 22:26:10 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202011280626.0AS6QAbC032721@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: grarpamp cc: freebsd-current@freebsd.org Subject: Re: firewall choice In-reply-to: References: Comments: In-reply-to grarpamp message dated "Fri, 27 Nov 2020 18:11:43 -0500." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 2020 22:26:10 -0800 X-CMAE-Envelope: MS4xfL/7ID90yfp8yRZ5CkpA8wZO/wXFeaDWVMsMQMgKRi/9sDC8+H743Gjmmt53KvCE/mLPnXYe7aNjPWwGljoFT7AheeL95nqIHffX4OfllPl/GrUnwiAe Ftt/mGjOCOy5psWeKKyzRsmOXezIgwsVzuZDE1k91Bmi7Z4A9dfSMzWZTElHaGt/HzRHdYWFpro+GsPPW8Ho7zGgJqc2Aw7W+AevWDemE9E9sOU3dVBhNeP3 KPcjioF2h+7qg9UUtMQodA== X-Rspamd-Queue-Id: 4CjhMq6NQlz3Fr2 X-Spamd-Bar: / X-Spamd-Result: default: False [0.30 / 15.00]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; RWL_MAILSPIKE_GOOD(0.00)[64.59.136.137:from]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[70.67.229.168:received]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.59.136.137:from]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cschubert.com: no valid DMARC record]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[64.59.136.137:from:127.0.2.255]; RCVD_IN_DNSWL_LOW(-0.10)[64.59.136.137:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Nov 2020 06:26:17 -0000 In message , grarpamp writes: > >>> What's the "best" [1] choice for firewalling these days > >>> There's pf, ipf and ipfw. > >> > >>This question comes up over years. > >> > >>Consider starting and joining with people to create > >>a comparison page on the FreeBSD Wiki, > >>both a feature / capability comparison table, > >>and contextual paragraphs. > >>A mini project like that can help many users > >>and add their researches to it. > > > > I'd be happy to if I knew where to start/how to start/is there a guide. > > Starting a wiki is here... > https://wiki.freebsd.org/ > https://wiki.freebsd.org/AboutWiki > > Which falls under larger handbook doc area... > https://lists.freebsd.org/mailman/listinfo/freebsd-doc > > Much of comparison would pull from man pages. > > Could also come from posting a call for input / announce > to questions, hackers, forum, etc. > > Wiki should not duplicate admin info from here... > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html > But would cover this handbook bullet item that is > not actually covered in the handbook (which > could link out to the wiki page for that)... > "- The differences between the firewalls built into FreeBSD." > > A full comparison would also want to note and point to > upstream sources, and have a table of which filter systems > are supported going forward in each unix OS (the *BSD > flavors including DragonFly ipfw3 pf, Linux netfilter+nftables, > Illumos). pf was originally written when Darren Reed took a job at Sun. He changed the license at the time. FreeBSD moved it (and other softwre to contrib), as did NetBSD (in their own way). OpenBSD wrote pf in the space of a week in reaction to the license change. > > And cover layer2 capabilities, switching, bridging, ipv6, > nat, rate limits / shape / queue, proxy, arbitrary rewriting > and routing hooks, etc. > > NetBSD where ipf was last released has deprecated > both ipf and pf in favor of npf. While upstream devel and > maintenance on ipf has died, pf still lives on at OpenBSD. It's hardly deprecated in NetBSD. Christos Zoulas and I have exchanged a fair bit of code. Darren Reed released and maintained IPF through the Australian National University. NetBSD imported it, like we do here at FreeBSD, into their src tree. > > Anyone can start. Have fun. My ipf work is documented at https://wiki.freebsd.org/IPFilter. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- 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 owner-freebsd-current@freebsd.org Sat Nov 28 13:50:33 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5AD914A1CF3 for ; Sat, 28 Nov 2020 13:50:33 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4CjtDT1HJQz3r8w for ; Sat, 28 Nov 2020 13:50:33 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2BFD54A1AA4; Sat, 28 Nov 2020 13:50:33 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2BB764A1A7D for ; Sat, 28 Nov 2020 13:50:33 +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 4CjtDR3yPHz3r6J for ; Sat, 28 Nov 2020 13:50:31 +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 0ASDoN05075420 for ; Sat, 28 Nov 2020 13:50:23 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.16.1/8.16.1/Submit) id 0ASDoNka075419 for current@freebsd.org; Sat, 28 Nov 2020 05:50:23 -0800 (PST) (envelope-from david) Date: Sat, 28 Nov 2020 05:50:23 -0800 From: David Wolfskill To: current@freebsd.org Subject: Laptop exhibits erratic responsiveness Message-ID: Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="48sZbCI1Kx/r2ZzT" Content-Disposition: inline X-Rspamd-Queue-Id: 4CjtDR3yPHz3r6J X-Spamd-Bar: + X-Spamd-Result: default: False [1.60 / 15.00]; HAS_REPLYTO(0.00)[current@freebsd.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[107.204.234.170:from]; FREEFALL_USER(0.00)[david]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[107.204.234.170:from:127.0.2.255]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_SHORT(1.00)[0.999]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_NA(0.00)[catwhisker.org]; ARC_NA(0.00)[]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; REPLYTO_EQ_TO_ADDR(5.00)[]; MAILMAN_DEST(0.00)[current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Nov 2020 13:50:33 -0000 --48sZbCI1Kx/r2ZzT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've delayed trying to send this, as I wasn't clear on how to express it -- and I had hoped that the problem would "go away" before I figured that part out: I first observed it around 09 Nov, which is when I updated the laptop (via in-place source upgrade, as usual) from r367484 to r367517. One of the issues I faced with respect to expressing the nature of the problem was "how to quantify" it. And as I was trying to get some work done on another machine, it ocurred to me that perhaps pinging that other machine might illustrate things adequately, so: g1-48(13.0-C)[17] ping albert PING albert.catwhisker.org (172.16.8.13): 56 data bytes 64 bytes from 172.16.8.13: icmp_seq=3D0 ttl=3D63 time=3D0.511 ms 64 bytes from 172.16.8.13: icmp_seq=3D1 ttl=3D63 time=3D0.667 ms 64 bytes from 172.16.8.13: icmp_seq=3D2 ttl=3D63 time=3D0.537 ms 64 bytes from 172.16.8.13: icmp_seq=3D3 ttl=3D63 time=3D0.618 ms 64 bytes from 172.16.8.13: icmp_seq=3D4 ttl=3D63 time=3D0.647 ms 64 bytes from 172.16.8.13: icmp_seq=3D5 ttl=3D63 time=3D0.538 ms 64 bytes from 172.16.8.13: icmp_seq=3D6 ttl=3D63 time=3D0.538 ms 64 bytes from 172.16.8.13: icmp_seq=3D7 ttl=3D63 time=3D0.543 ms 64 bytes from 172.16.8.13: icmp_seq=3D8 ttl=3D63 time=3D0.571 ms 64 bytes from 172.16.8.13: icmp_seq=3D9 ttl=3D63 time=3D0.500 ms 64 bytes from 172.16.8.13: icmp_seq=3D10 ttl=3D63 time=3D0.618 ms 64 bytes from 172.16.8.13: icmp_seq=3D11 ttl=3D63 time=3D0.548 ms 64 bytes from 172.16.8.13: icmp_seq=3D12 ttl=3D63 time=3D0.532 ms 64 bytes from 172.16.8.13: icmp_seq=3D13 ttl=3D63 time=3D0.532 ms 64 bytes from 172.16.8.13: icmp_seq=3D14 ttl=3D63 time=3D0.613 ms 64 bytes from 172.16.8.13: icmp_seq=3D15 ttl=3D63 time=3D0.593 ms 64 bytes from 172.16.8.13: icmp_seq=3D16 ttl=3D63 time=3D0.501 ms 64 bytes from 172.16.8.13: icmp_seq=3D17 ttl=3D63 time=3D0.630 ms 64 bytes from 172.16.8.13: icmp_seq=3D18 ttl=3D63 time=3D0.556 ms 64 bytes from 172.16.8.13: icmp_seq=3D19 ttl=3D63 time=3D0.566 ms 64 bytes from 172.16.8.13: icmp_seq=3D20 ttl=3D63 time=3D0.642 ms 64 bytes from 172.16.8.13: icmp_seq=3D21 ttl=3D63 time=3D0.611 ms 64 bytes from 172.16.8.13: icmp_seq=3D22 ttl=3D63 time=3D0.628 ms 64 bytes from 172.16.8.13: icmp_seq=3D23 ttl=3D63 time=3D92.473 ms 64 bytes from 172.16.8.13: icmp_seq=3D24 ttl=3D63 time=3D0.647 ms 64 bytes from 172.16.8.13: icmp_seq=3D25 ttl=3D63 time=3D0.483 ms 64 bytes from 172.16.8.13: icmp_seq=3D26 ttl=3D63 time=3D0.476 ms 64 bytes from 172.16.8.13: icmp_seq=3D27 ttl=3D63 time=3D0.561 ms 64 bytes from 172.16.8.13: icmp_seq=3D28 ttl=3D63 time=3D0.560 ms 64 bytes from 172.16.8.13: icmp_seq=3D29 ttl=3D63 time=3D0.599 ms 64 bytes from 172.16.8.13: icmp_seq=3D30 ttl=3D63 time=3D0.677 ms 64 bytes from 172.16.8.13: icmp_seq=3D31 ttl=3D63 time=3D0.563 ms 64 bytes from 172.16.8.13: icmp_seq=3D32 ttl=3D63 time=3D0.609 ms 64 bytes from 172.16.8.13: icmp_seq=3D33 ttl=3D63 time=3D0.558 ms 64 bytes from 172.16.8.13: icmp_seq=3D34 ttl=3D63 time=3D0.527 ms 64 bytes from 172.16.8.13: icmp_seq=3D35 ttl=3D63 time=3D0.610 ms 64 bytes from 172.16.8.13: icmp_seq=3D36 ttl=3D63 time=3D0.621 ms 64 bytes from 172.16.8.13: icmp_seq=3D37 ttl=3D63 time=3D0.501 ms 64 bytes from 172.16.8.13: icmp_seq=3D38 ttl=3D63 time=3D68482.244 ms 64 bytes from 172.16.8.13: icmp_seq=3D39 ttl=3D63 time=3D0.672 ms 64 bytes from 172.16.8.13: icmp_seq=3D40 ttl=3D63 time=3D0.635 ms 64 bytes from 172.16.8.13: icmp_seq=3D41 ttl=3D63 time=3D0.585 ms 64 bytes from 172.16.8.13: icmp_seq=3D42 ttl=3D63 time=3D0.629 ms 64 bytes from 172.16.8.13: icmp_seq=3D43 ttl=3D63 time=3D0.566 ms 64 bytes from 172.16.8.13: icmp_seq=3D44 ttl=3D63 time=3D0.641 ms 64 bytes from 172.16.8.13: icmp_seq=3D45 ttl=3D63 time=3D0.638 ms 64 bytes from 172.16.8.13: icmp_seq=3D46 ttl=3D63 time=3D0.645 ms 64 bytes from 172.16.8.13: icmp_seq=3D47 ttl=3D63 time=3D0.540 ms 64 bytes from 172.16.8.13: icmp_seq=3D48 ttl=3D63 time=3D0.487 ms 64 bytes from 172.16.8.13: icmp_seq=3D49 ttl=3D63 time=3D13.063 ms 64 bytes from 172.16.8.13: icmp_seq=3D50 ttl=3D63 time=3D0.567 ms 64 bytes from 172.16.8.13: icmp_seq=3D51 ttl=3D63 time=3D0.487 ms 64 bytes from 172.16.8.13: icmp_seq=3D52 ttl=3D63 time=3D0.428 ms 64 bytes from 172.16.8.13: icmp_seq=3D53 ttl=3D63 time=3D0.692 ms 64 bytes from 172.16.8.13: icmp_seq=3D54 ttl=3D63 time=3D0.605 ms 64 bytes from 172.16.8.13: icmp_seq=3D55 ttl=3D63 time=3D0.630 ms 64 bytes from 172.16.8.13: icmp_seq=3D56 ttl=3D63 time=3D0.561 ms 64 bytes from 172.16.8.13: icmp_seq=3D57 ttl=3D63 time=3D0.634 ms 64 bytes from 172.16.8.13: icmp_seq=3D58 ttl=3D63 time=3D0.571 ms 64 bytes from 172.16.8.13: icmp_seq=3D59 ttl=3D63 time=3D0.577 ms 64 bytes from 172.16.8.13: icmp_seq=3D60 ttl=3D63 time=3D0.592 ms 64 bytes from 172.16.8.13: icmp_seq=3D61 ttl=3D63 time=3D0.455 ms 64 bytes from 172.16.8.13: icmp_seq=3D62 ttl=3D63 time=3D0.585 ms 64 bytes from 172.16.8.13: icmp_seq=3D63 ttl=3D63 time=3D0.548 ms 64 bytes from 172.16.8.13: icmp_seq=3D64 ttl=3D63 time=3D0.443 ms 64 bytes from 172.16.8.13: icmp_seq=3D65 ttl=3D63 time=3D0.584 ms 64 bytes from 172.16.8.13: icmp_seq=3D66 ttl=3D63 time=3D0.592 ms ^C --- albert.catwhisker.org ping statistics --- 67 packets transmitted, 67 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 0.428/1024.248/68482.244/8303.513 ms g1-48(13.0-C)[18]=20 Please note that no packets are dropped, and that most exhibit an RTT of around 0.6 ms, and that no packets are dropped -- which is ... good, as far as that goes. (The laptop is presently using a wired Ethernet (em0) link, as "wireless" doesn't play well with significant lags in response time, or so it appears to me.) But packet 23 shows a hint of something gone awry, and packet 38 ... something's gone walkabout, and is in no hurry to return. While the above "ping" was done during the upgrade from r368097 to r368119, I have observed similar effects when the machine was idle (but running head). I do NOT observe these effects when the machine is running stable/12 (also tracked/updated daily), nor have I seen the behavior on other machines (my build machine, which also tracks head and stable/12 daily; various machines at work, which generally track head about every 4 - 5 weeks). Any ideas for tracking this down? I have documented various aspects of what process I use to track/uodate the machines, the environment, and the history of the tracking: * http://www.catwhisker.org/~david/FreeBSD/upgrade.html * http://www.catwhisker.org/~david/FreeBSD/history/ Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org "Make America Great Again," he said -- and THIS is what he did??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --48sZbCI1Kx/r2ZzT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl/CVZ9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PclHHQgAugzyOA5sdTF+R/1SLXOmsWNFwRvjATU6eYdQEzLq3xRqmpe8/kluXiiY XrI7zK1gJWVWfrfG31m1kEc7bHY7Z5Pv31/DKxFcIAZUYnnZXi5lk3csyVzgl/+S qoITjV0ZKx1uJeBNXmtoU2GMhm8FmckHF41Vlc+GPGPpWpbfIhhOMg/BUVm8Tk0B wDJR8etcJ6EKA6FWROog3Xkd1gBLjHgOebkEiMOTOIWOOkpt3Ao3GJc5T+Zn4dBe yqMXvjRJYxZLzFT0WzywtTxapS7Ggnb4LYLF0M/SZMRmFDSPtDFT0R5EKeeHvNLl tU+5FUv3NJ4+0Eu9/X+14MlLGqJWzg== =tEk3 -----END PGP SIGNATURE----- --48sZbCI1Kx/r2ZzT--