From owner-freebsd-current@freebsd.org Sun Apr 12 04:41:10 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 BA78A2B107B; Sun, 12 Apr 2020 04:41:10 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 490Jwj6h5Nz4bDK; Sun, 12 Apr 2020 04:41:09 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 03C4fXj7013328 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 11 Apr 2020 21:41:40 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: freebsd-stable From: Chris Reply-To: bsd-lists@BSDforge.com To: freebsd-current Subject: Why is the console a graphic/bitmapped console, and not text/character by default Date: Sat, 11 Apr 2020 21:41:40 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 490Jwj6h5Nz4bDK X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.60 / 15.00]; NEURAL_HAM_MEDIUM(-0.78)[-0.784,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81]; NEURAL_HAM_LONG(-0.82)[-0.821,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 04:41:10 -0000 Sorry for the ling title=2E But wasn't sure how make my question more concise=2E Why did we begin making an initial console "graphics mode" by default=2E My understanding has always been that (Free)BSD has been a "Server by default", and a Desktop after an initial install if that's one chosen target=2E It's near impossible to perform initial configuration in graphics mode, using a mouse to cut/copy/paste does *not* work as intended=2E Which requires one to make the necessary changes "breaking to the new system" after install completes to change initiation to test-mode before bouncing the box=2E While this "works" for long-time users=2E It's an *extra*, and seemingly *unnecessary* step=2E It is also likely to behoove first-time/new users -- except those already targeting a Desktop=2E Thanks for any insight into this! :) --Chris From owner-freebsd-current@freebsd.org Sun Apr 12 05:04: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 EE1CE2B211B for ; Sun, 12 Apr 2020 05:04:49 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-hyfv06011301.me.com (mr85p00im-hyfv06011301.me.com [17.58.23.184]) (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 490KS06dyZz4cVH for ; Sun, 12 Apr 2020 05:04:48 +0000 (UTC) (envelope-from tsoome@me.com) Received: from [192.168.150.159] (148-52-235-80.sta.estpak.ee [80.235.52.148]) by mr85p00im-hyfv06011301.me.com (Postfix) with ESMTPSA id 88EA0580217; Sun, 12 Apr 2020 05:04:46 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Toomas Soome Mime-Version: 1.0 (1.0) Subject: Re: Why is the console a graphic/bitmapped console, and not text/character by default Date: Sun, 12 Apr 2020 08:04:43 +0300 Message-Id: <2751595C-BBB8-46DF-ABC2-5CAD7B82176B@me.com> References: Cc: freebsd-current , freebsd-stable In-Reply-To: To: bsd-lists@bsdforge.com X-Mailer: iPhone Mail (17E255) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-11_06:2020-04-11, 2020-04-11 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0 mlxlogscore=843 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2004120045 X-Rspamd-Queue-Id: 490KS06dyZz4cVH X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.00)[ip: (-2.14), ipnet: 17.58.16.0/20(-1.54), asn: 714(-2.45), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[184.23.58.17.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[184.23.58.17.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 05:04:50 -0000 You have UEFI setup? With UEFI, there is no text mode. If mouse copy/paste is working is not a property of screen mode but it if th= e console driver does implement it or not. Sent from my iPhone > On 12. Apr 2020, at 07:41, Chris wrote: >=20 > =EF=BB=BFSorry for the ling title. But wasn't sure how make my > question more concise. > Why did we begin making an initial console "graphics mode" > by default. My understanding has always been that (Free)BSD > has been a "Server by default", and a Desktop after an initial > install if that's one chosen target. > It's near impossible to perform initial configuration > in graphics mode, using a mouse to cut/copy/paste does *not* > work as intended. Which requires one to make the necessary > changes "breaking to the new system" after install completes > to change initiation to test-mode before bouncing the box. > While this "works" for long-time users. It's an *extra*, and > seemingly *unnecessary* step. It is also likely to behoove > first-time/new users -- except those already targeting a > Desktop. >=20 > Thanks for any insight into this! :) >=20 > --Chris >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@freebsd.org Sun Apr 12 05:34: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 70D522B2AE5 for ; Sun, 12 Apr 2020 05:34:13 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 490L5x1cj6z4dr7 for ; Sun, 12 Apr 2020 05:34:12 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 03C5YaM6054258 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 11 Apr 2020 22:34:43 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: freebsd-current In-Reply-To: <2751595C-BBB8-46DF-ABC2-5CAD7B82176B@me.com> From: Chris Reply-To: bsd-lists@BSDforge.com To: Toomas Soome Subject: Re: Why is the console a graphic/bitmapped console, and not text/character by default Date: Sat, 11 Apr 2020 22:34:43 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 490L5x1cj6z4dr7 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.67 / 15.00]; NEURAL_HAM_MEDIUM(-0.76)[-0.760,0]; NEURAL_HAM_LONG(-0.91)[-0.912,0]; 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.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 05:34:13 -0000 On Sun, 12 Apr 2020 08:04:43 +0300 Toomas Soome tsoome@me=2Ecom said > You have UEFI setup? With UEFI, there is no text mode=2E >=20 > If mouse copy/paste is working is not a property of screen mode but it if= the > console driver does implement it or not=2E >=20 > Sent from my iPhone >=20 > > On 12=2E Apr 2020, at 07:41, Chris wrote: > >=20 > > =EF=BB=BFSorry for the ling title=2E But wasn't sure how make my > > question more concise=2E > > Why did we begin making an initial console "graphics mode" > > by default=2E My understanding has always been that (Free)BSD > > has been a "Server by default", and a Desktop after an initial > > install if that's one chosen target=2E > > It's near impossible to perform initial configuration > > in graphics mode, using a mouse to cut/copy/paste does *not* > > work as intended=2E Which requires one to make the necessary > > changes "breaking to the new system" after install completes > > to change initiation to test-mode before bouncing the box=2E > > While this "works" for long-time users=2E It's an *extra*, and > > seemingly *unnecessary* step=2E It is also likely to behoove > > first-time/new users -- except those already targeting a > > Desktop=2E > >=20 > > Thanks for any insight into this! :) > >=20 > > --Chris > >=20 > >=20 With (U)EFI firmware, you're in graphics until the kernel takes over=2E Where you can switch/change/obtain text/character mode=2E I'm not we're talking about the same thing here=2E --Chris From owner-freebsd-current@freebsd.org Sun Apr 12 06:32:24 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 783832B3F8B for ; Sun, 12 Apr 2020 06:32:24 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 490MP32fPcz3Csf for ; Sun, 12 Apr 2020 06:32:23 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-lj1-x229.google.com with SMTP id r24so5786665ljd.4 for ; Sat, 11 Apr 2020 23:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T33vd+ca9UaB8Ht7AtpufNXi7mx4S1sUjMxSFZHn+wk=; b=AzcT15/HLrcIxOLB1Px1Afm9SIJvsto5n5L50+HJ1zTJH76InDga43jRDv6X2f8I8D MjQtqlQQ4jwwKtgQwlVDJyr42g525idDqm37AaQPfwRFesYHpWN64XIsrzSfXyqV0tyg 574X/9lM2toKW+IQMSpU3oPSUH76BygIjn01KhIGtU3beEIbgtwBlMOe9mN78LgjVW1T pYgk2chOTleCPrCFZG3wLi0yZOUMRdeZAmDWMGkpB2fGOBcd5IpMlGpsPi6TR+csWp9O gGISIMQaRqhwpA234aPrzl8e0wytfeYqRF3A1aNvYNg9Zg1vDNxDnXdU7HenYrtT7tpG ktDg== 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=T33vd+ca9UaB8Ht7AtpufNXi7mx4S1sUjMxSFZHn+wk=; b=TYwpjzFBmFU4sb5vmfgbKqGBNSLZR1+yS0bfNOj2JWIpiuB8Dm05Q3YbdYrBhd2lM3 iXzGQLIxvwfz/m+UxLndp6u+tmEvbUI5b838wd4+PqIkeN7t5uXUz1kypikUFcf8TgGl IQCw8yuZzKJHOA7RP52xXqHTaW53ovUEBU3tdAC3BaYjShFnUN5V8EbMPk3eiTQu679j 3KPP/vT//pP5bk346TkeTGbBBvnfe8w+8r6VoExseX1O6mfmXPK4wd+dTD0nKAcbbaoq v4kemQqGhdZuSwrIucOwu3cS8klm0/5LCWkZWTWnid59Gr46KkmShKNJPH5QrDM3xUCq Qx/Q== X-Gm-Message-State: AGi0PuZHk0y9ZDrkmKyqmGFAxOgT1KOf4ggP0qCi1wMipzmvYPjlxP2S rRMLQt5KufyH4laHNnNhqBmfGkkaFcd2VTr2Vf/l+/WoIQ== X-Google-Smtp-Source: APiQypJ3dqqR+37Nu2nD/UG3MLOcuVRqqG487RTyEG26C3ae+Duapm1TSQdoct5zCYAVCco8n+20J7/yfH3RuArzpUo= X-Received: by 2002:a2e:88d9:: with SMTP id a25mr7479950ljk.70.1586673140880; Sat, 11 Apr 2020 23:32:20 -0700 (PDT) MIME-Version: 1.0 References: <4fe5f234-a185-89f6-97ca-fd2bc6524205@daemonic.se> In-Reply-To: <4fe5f234-a185-89f6-97ca-fd2bc6524205@daemonic.se> From: Clay Daniels Date: Sun, 12 Apr 2020 01:32:09 -0500 Message-ID: Subject: Re: FreeBSD-13.0-CURRENT-amd64-20200409-r359731: drm-kmod failure? To: Niclas Zeising Cc: "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 490MP32fPcz3Csf X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=AzcT15/H; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of claydanielsjr@gmail.com designates 2a00:1450:4864:20::229 as permitted sender) smtp.mailfrom=claydanielsjr@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.14), ipnet: 2a00:1450::/32(-2.36), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 06:32:24 -0000 On Sat, Apr 11, 2020 at 2:06 AM Niclas Zeising wrote: > > How did you install the driver? > When using the drm drivers on current, you usually have to build them > from ports rather than use the packages, this way the driver matches the > kernel you are using. > Regards > -- > Niclas > Thanks, Niclas. I guess I'm mostly too lazy and drm-kmod has been working well just using pkg install drm-kmod to bother with making the ports. But I reloaded r359731 and went to /usr/ports/graphics and installed drm-current-kmod which brought in gpu-firmware-kmod and everything worked fine. I then installed xorg (via pkg), rebooted, ran startx, and used the xterm window in twm to install firefox, and write this reply. Clay From owner-freebsd-current@freebsd.org Sun Apr 12 07:23: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 DB9942B530C for ; Sun, 12 Apr 2020 07:23:59 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztbu10021601.me.com (pv50p00im-ztbu10021601.me.com [17.58.6.57]) (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 490NXZ6hfxz3GPV for ; Sun, 12 Apr 2020 07:23:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from [10.247.0.202] (unknown [91.209.240.229]) by pv50p00im-ztbu10021601.me.com (Postfix) with ESMTPSA id 5500F6E03EC; Sun, 12 Apr 2020 07:23:56 +0000 (UTC) From: Toomas Soome Message-Id: <6BDCC642-4CE1-4F61-988B-EE81B311732B@me.com> Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Why is the console a graphic/bitmapped console, and not text/character by default Date: Sun, 12 Apr 2020 10:23:53 +0300 In-Reply-To: Cc: freebsd-current To: "bsd-lists@bsdforge.com" References: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-12_02:2020-04-11, 2020-04-12 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2004120068 X-Rspamd-Queue-Id: 490NXZ6hfxz3GPV X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.00)[ip: (-5.68), ipnet: 17.58.0.0/20(-2.08), asn: 714(-2.45), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[57.6.58.17.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 07:23:59 -0000 > On 12. Apr 2020, at 08:34, Chris wrote: >=20 > On Sun, 12 Apr 2020 08:04:43 +0300 Toomas Soome tsoome@me.com = said >=20 >> You have UEFI setup? With UEFI, there is no text mode. >> If mouse copy/paste is working is not a property of screen mode but = it if the >> console driver does implement it or not. >> Sent from my iPhone >> > On 12. Apr 2020, at 07:41, Chris wrote: >> > > =EF=BB=BFSorry for the ling title. But wasn't sure how make my >> > question more concise. >> > Why did we begin making an initial console "graphics mode" >> > by default. My understanding has always been that (Free)BSD >> > has been a "Server by default", and a Desktop after an initial >> > install if that's one chosen target. >> > It's near impossible to perform initial configuration >> > in graphics mode, using a mouse to cut/copy/paste does *not* >> > work as intended. Which requires one to make the necessary >> > changes "breaking to the new system" after install completes >> > to change initiation to test-mode before bouncing the box. >> > While this "works" for long-time users. It's an *extra*, and >> > seemingly *unnecessary* step. It is also likely to behoove >> > first-time/new users -- except those already targeting a >> > Desktop. >> > > Thanks for any insight into this! :) >> > > --Chris >> > >=20 > With (U)EFI firmware, you're in graphics until the kernel takes over. > Where you can switch/change/obtain text/character mode. >=20 > I'm not we're talking about the same thing here. >=20 UEFI systems *may* provide VGA bios for gfx, but thats not granted, and = if not you have no =E2=80=9Ctext=E2=80=9D mde at all. In virtual = environment it is possible you do not get even framebuffer mapped = memory. rgds, toomas= From owner-freebsd-current@freebsd.org Sun Apr 12 19:26: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 5367E2C68CB; Sun, 12 Apr 2020 19:26:54 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 490hZj3xxcz4XmM; Sun, 12 Apr 2020 19:26:53 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 7D94560EB; Sun, 12 Apr 2020 19:26:52 +0000 (UTC) To: FreeBSD Hackers , freebsd-current From: Eric McCorkle Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXonLJBYJKwYBBAHaRw8BAQdA4oHU11A8qtqD0EtRofyORHbGX1ZIT/mnk9eceKQx56q0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiZBBMWCABBAhsDBQkB4TOA BQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAFiEEPfuJobsx0Me4pIwLPOOjZtwQVqwFAl6JzIAC GQEACgkQPOOjZtwQVqy2DgD+IRCNNfb7C16fjEHazDMBwmBIMz+CTJUdhoz73P9iy0cA/ixK 83qOW46q1fpCpaZtPvv0FRpcZ5EppnNQ0Yuh40YLuDgEXonLJBIKKwYBBAGXVQEFAQEHQCxw rRXlvDoXgDGv2WMrLy9UaJ4fNWXIdlaiiKZIH7lBAwEIB4h+BBgWCAAmFiEEPfuJobsx0Me4 pIwLPOOjZtwQVqwFAl6JyyQCGwwFCQHhM4AACgkQPOOjZtwQVqxS7wD+JgzZC4995EL9j2iB qhPUZTIgs61IypLoDx+o1zsSfvkBALs+/jvkQL4plT0hGtfFaa0iMnLeIXKd/1FSNGSD9hQI Subject: Working on Zoom port Message-ID: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> Date: Sun, 12 Apr 2020 15:26:46 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="K3uT4CXQrOW8G37aQEBs32ZvrYUz2y2O2" X-Rspamd-Queue-Id: 490hZj3xxcz4XmM X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of eric@metricspace.net has no SPF policy when checking 2001:470:1f11:617::107) smtp.mailfrom=eric@metricspace.net X-Spamd-Result: default: False [-5.18 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; IP_SCORE(-2.08)[ip: (-2.10), ipnet: 2001:470::/32(-4.66), asn: 6939(-3.60), country: US(-0.05)]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; SIGNED_PGP(-2.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 19:26:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --K3uT4CXQrOW8G37aQEBs32ZvrYUz2y2O2 Content-Type: multipart/mixed; boundary="dsgNSRM51C8kbUY3Lz4XL9V7rmjlvHciP"; protected-headers="v1" From: Eric McCorkle To: FreeBSD Hackers , freebsd-current Message-ID: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> Subject: Working on Zoom port --dsgNSRM51C8kbUY3Lz4XL9V7rmjlvHciP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable All, Given how Zoom is getting used a lot more these days, I've started working on a port that installs the Zoom linux client. Here is a link to my github if anyone wants to help: https://github.com/emc2/freebsd-ports/tree/zoom I'm not done yet. The zoom linux client installs a bunch of Qt libraries in its own directory. These either need to be installed with a port, or else the right configs need to be set to search for libraries there. I'm going to take a break, but I'm going to circle back to this. --dsgNSRM51C8kbUY3Lz4XL9V7rmjlvHciP-- --K3uT4CXQrOW8G37aQEBs32ZvrYUz2y2O2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXpNrdgAKCRA846Nm3BBW rMWkAP4q9dXFJK2R95nEHxyqP9whJFm0elMaoURyJmNCBJY3BAEA+2ynHcI3hlAG qgp58iaD0544QxX8GIJyWKVztjE0Hgg= =1nTb -----END PGP SIGNATURE----- --K3uT4CXQrOW8G37aQEBs32ZvrYUz2y2O2-- From owner-freebsd-current@freebsd.org Sun Apr 12 22:05: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 916A12AB11B; Sun, 12 Apr 2020 22:05:48 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 490m6437Lgz3GD4; Sun, 12 Apr 2020 22:05:48 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1472) id 61957D411; Sun, 12 Apr 2020 22:05:48 +0000 (UTC) To: freebsd-hackers@FreeBSD.org Subject: FreeBSD Quarterly Status Report - First Quarter 2020 Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Message-Id: <20200412220548.61957D411@freefall.freebsd.org> Date: Sun, 12 Apr 2020 22:05:48 +0000 (UTC) From: Lorenzo Salvadore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2020 22:05:48 -0000 FreeBSD Project Quarterly Status Report - First Quarter 2020 Introduction Welcome, to the quarterly reports, of the future! Well, at least the first quarterly report from 2020. The new timeline, mentioned in the last few reports, still holds, which brings us to this report, which covers the period of January 2020 - March 2020. As you will see from this report, we've had quite an active quarter with big changes to both kernel, userland, documentation, ports, and third-party projects in the form of everything from bug and security fixes over new features to speed improvements and optimizations. As this report also covers the start of the epidemic, it's also interesting to note that a quick glance at the svn logs reveal that there has been no overall drop in number of source commits, that docs commits have also stayed constant, and that ports have seen an upwards trend. We hope that all of you are and yours are as safe as can be managed, and that we get through this together by working together. -- Daniel Ebdrup Jensen, debdrup@freebsd.org __________________________________________________________________ FreeBSD Team Reports * FreeBSD Foundation * FreeBSD Core Team * FreeBSD Release Engineering Team * Cluster Administration Team * Continuous Integration * Ports Collection * FreeBSD Graphics Team status report Projects * NFS over TLS implementation * Import of the Kyua test framework * Linux compatibility layer update * syzkaller on FreeBSD Kernel * if_bridge * sigfastblock(2) * arm64 LSE atomic instructions * FreeBSD on Microsoft HyperV and Azure * FreeBSD on the ARM Morello platform * NXP ARM64 SoC support * ENA FreeBSD Driver Update Architectures * FreeBSD/powerpc Project * FreeBSD/RISC-V Project Userland Programs * GCC 4.2.1 Retirement * elfctl utility * ELF Tool Chain Ports * KDE on FreeBSD * XFCE * Wine on FreeBSD * Go on freebsd/arm64 * sysctlmibinfo2 API Documentation * FreeBSD Translations on Weblate * FreeBSD Manpages overhaul Third-Party Projects * pot and the nomad pot driver * NomadBSD __________________________________________________________________ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Foundation Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Funding comes from individual and corporate donations and is used to fund and manage software development projects, conferences and developer summits, and provide travel grants to FreeBSD contributors. The Foundation purchases and supports hardware to improve and maintain FreeBSD infrastructure and provides resources to improve security, quality assurance, and release engineering efforts; publishes marketing material to promote, educate, and advocate for the FreeBSD Project; facilitates collaboration between commercial vendors and FreeBSD developers; and finally, represents the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. Here are some highlights of what we did to help FreeBSD last quarter: General We moved! Our new address is: The FreeBSD Foundation 3980 Broadway St. STE #103-107 Boulder, CO 80304 USA In February, the board of directors had an all-day board meeting in Berkely, CA, where FreeBSD began! We put together our strategic plans for the next 2 years, which includes software developments projects we want to support and some educational initiatives. COVID-19 impacts the Foundation. We put policies in place for all of our staff members to work from home. We also put a temporary ban on travel for staff members. We are continuing our work supporting the community and Project, but some of our work and responses are delayed because of changes in some of our priorities and the impact of limited childcare for a few of our staff members. Partnerships and Commercial User Support We help facilitate collaboration between commercial users and FreeBSD developers. We also meet with companies to discuss their needs and bring that information back to the Project. In Q1, Deb Goodkin met with commercial users at LinuxConfAu in Australia, FOSDEM in Belgium, and SCALE18x in the US. These venues provide an excellent opportunity to meet with commercial and individual users and contributors to FreeBSD. It's not only beneficial for the above, but it also helps us understand some of the applications where FreeBSD is used. In addition to meeting with commercial users at conferences, we continued discussions over email or on calls over the quarter. Fundraising Efforts Last quarter we raised $57,000! Thank you to everyone who came through, especially in this economic crisis we have found ourselves in. It heartens us deeply that individuals and organizations have supported our efforts, when there are so many people, animals, and businesses in need right now. We also want to extend a big thank you to Tarsnap, VMWare, and Stormshield for leading the way with Silver level donations. We hope other organizations will follow their lead and give back to help us continue supporting FreeBSD. We are 100% funded by donations, and those funds go towards software development work to improve FreeBSD, FreeBSD advocacy around the world, keeping FreeBSD secure, continuous integration improvements, sponsoring BSD-related and computing conferences, legal support for the Project, and many other areas. Please consider making a donation to help us continue and increase our support for FreeBSD: https://www.FreeBSDfoundation.org/donate/. We also have the Partnership Program, to provide more benefits for our larger commercial donors. Find out more information at https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ and share with your companies! OS Improvements The Foundation supports software development projects to improve the FreeBSD operating system through our full time technical staff, contractors, and project grant recipients. They maintain and improve critical kernel subsystems, add new features and functionality, and fix problems. Over the last quarter there were 273 commits to the FreeBSD base system source repository tagged with FreeBSD Foundation sponsorship, about 12% of base system commits over the quarter. Many of these are part of sponsored or staff projects that have their own entries in this FreeBSD Quarterly Report, but Foundation staff and contractors (Ed Maste, Konstantin Belousov, Mark Johnston, Li-Wen Hsu) also support the project with an ongoing series of bug fixes, build fixes, and miscellaneous improvements that don't warrant a separate entry. Ed committed miscellaneous improvements to various parts of FreeBSD's build infrastructure, largely prompted by the work to retire the obsolete GCC 4.2.1. This included removal of the LLVM_LIBUNWIND option (now always set), and the removal of unused gperf, gcov, and the GPL devicetree compiler (dtc). Ed committed sendfile support for the Linuxulator, submitted by previous intern Bora Özarslan, and tested and committed a number of submitted bug fixes for the Microchip USB-Ethernet controller if_muge driver. Ed also updated the copy of OpenSSH in the base system to 7.9p1, with additional updates in progress, and worked on a number of security advisories released during the quarter. Konstantin Belousov and Mark Johnston both performed a large number of code reviews during the quarter under Foundation sponsorship. This work helps developers in the FreeBSD community and those working at companies using FreeBSD to integrate their work into FreeBSD. In addition to work described elsewhere in this report Konstantin also continued his usual series of bug fixes and improvements. This quarter this included low-level x86 support, fixing sendfile bugs, file system and vfs bug fixes, and dozens of other miscellaneous improvements. Additional work included a variety of commits to support Hygon x86 CPUs and improvements to the runtime linker (rtld)'s direct execution mode. Mark Johnston continued his work on the Syzkaller system-call fuzzer, and committed fixes for many issues reported by Syzkaller. Mark triaged a large number of submitted bug reports and in many cases committed attached patches or developed fixes. Mark also addressed dozens of Coverity Scan reports. Mark's other changes included arm64 Large System Extensions (LSE) atomic operations, low-level arm64 and x86 work, virtual memory (VM) work, and bug fixes or other improvements to syslog, the lagg(4) link aggregation driver, and build reproducibility. Li-Wen Hsu committed many changes to tests in the base system, such as turning off known failing tests tracked by PRs, test-related pkgbase fixes, and other improvements. Continuous Integration and Quality Assurance The Foundation provides a full-time staff member who is working on improving our automated testing, continuous integration, and overall quality assurance efforts. During the first quarter of 2020, Foundation staff continued to improve the Project's CI infrastructure, worked with contributors to fix the failing build and test cases. The building of a CI staging environment is in progress on the new machine purchased by the Foundation. We are also working with other teams in the Project for their testing needs. For example, we added a new job for running LTP (Linux Testing Project) on the Linuxulator, to validate improvements in the Foundation's sponsored Linux emulation work. We are also working with many external projects and companies to improve their support of FreeBSD. See the FreeBSD CI section of this report for completed work items and detailed information. Supporting FreeBSD Infrastructure The Foundation provides hardware and support to improve the FreeBSD infrastructure. Last quarter, we continued supporting FreeBSD hardware located around the world. We purchased one server for a mirror in Malaysia, and signed the MOU for the new NYI colocation facility in Illinois. NYI generously provides this as an in-kind donation to the Project. FreeBSD Advocacy and Education A large part of our efforts are dedicated to advocating for the Project. This includes promoting work being done by others with FreeBSD; producing advocacy literature to teach people about FreeBSD and help make the path to starting using FreeBSD or contributing to the Project easier; and attending and getting other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD tables, and give FreeBSD presentations. The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, to work together on projects, and to facilitate collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. Check out some of the advocacy and education work we did last quarter: * Organized and presented at the first ever FreeBSD Mini-Conf LinuxConfAu 2020, in Gold Coast, Australia in addition to sponsoring the conference itself. The recap can be found here. * Presented BSD Dev Room at FOSDEM '20, in Brussels, Belgium and represented FreeBSD at a stand along with other members of the community. Find out more here: https://www.freebsdfoundation.org/blog/fosdem-2020-conference-recap/ * Represented FreeBSD at Apricot 2020 in Melbourne, Australia and sponsored the event. * Industry Partner Sponsor for USENIX FAST '20 in Santa Clara, CA * Sponsored FOSSASIA 2020, in Singapore * Committed to hold FreeBSD Day at SCALE 18x, in Pasadena, CA * Held a "Getting Started with FreeBSD Workshop" at SCALE 18x in addition to giving a talk, representing FreeBSD at the Expo and holding a "Why FreeBSD is Me" BoF. Check out the conference recap. We continued producing FreeBSD advocacy material to help people promote FreeBSD. Learn more about our efforts in 2019 to advocate for FreeBSD. In addition to the information found in the Development Projects update section of this report, take a minute to check out the latest update blogs: * POWER to the People: Making FreeBSD a First Class Citizen on POWER. * Development Project Update: Toolchain Modernization. Read more about our conference adventures in the conference recaps and trip reports in our monthly newsletters. We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues. You can find out more about events we attended and upcoming events here. As is the case for most of us in this industry, SCALE was the last event we will be attending for a few months. However, we're already working on how we can make more on-line tutorials and how-to guides available to facilitate getting more folks to try out FreeBSD. In the meantime, please check out the how-to guides we already have available! We have continued our work with a new website developer to help us improve our website. Work has begun to make it easier for community members to find information more easily and to make the site more efficient. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to http://www.FreeBSDfoundation.org/ to find out how we support FreeBSD and how we can help you! __________________________________________________________________ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. * Core approved a source commit bit for Alfredo Dal'Ava Júnior. Alfredo has been working on powerpc64 support. Justin Hibbits (jhibbits) will mentor Alfredo. * Core approved a source commit bit for Ryan Moeller. Ryan has been working on porting ZoL to FreeBSD. Alexander Motin (mav) and Matt Macy (mmacy) will mentor Ryan. * Core approved a source commit bit for Nick O'Brien. Nick has been working on RISC-V at Axiado. Kristof Provost (kp) and Philip Paeps (philip) will mentor Nick. * Core approved a source commit bit for Richard Scheffenegger. Richard has been contributing TCP work. Michael Tuexen (tuexen) will mentor Richard and Rodney Grimes (rgrimes) will act as co-mentor. * Core approved a source commit bit for Aleksandr Fedorov. Aleksandr has been testing and reviewing bhyve networking code. Vincenzo Maffione (vmaffione) will mentor Aleksandr and John Baldwin (jhb) will act as co-mentor. * Core requested that the freebsd-mobile@ list be retired as it was almost exclusively receiving spam. postmaster@ completed core's request. * Core approved third party authentication for some project services with certain conditions. For example, for authentication with Google, users must be using a FreeBSD.org account with two-factor authentication enabled. For GitHub, we will enable and force multi-factor authentication for our organization. * The Core-initiated Git Transition Working Group continued to meet over the first quarter of 2020. Their report is still forthcoming. __________________________________________________________________ FreeBSD Release Engineering Team Links FreeBSD 11.4-RELEASE schedule URL: https://www.freebsd.org/releases/11.4R/schedule.html FreeBSD 12.2-RELEASE schedule URL: https://www.freebsd.org/releases/12.2R/schedule.html FreeBSD development snapshots URL: https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. The FreeBSD Release Engineering Team published the schedules for the upcoming 11.4-RELEASE and 12.2-RELEASE cycles. Much time was spent by Glen Barber working on updates to the various build tools adding support for builds from both Subversion and Git. This is very much a work in progress, as there are a number of inter-connected moving parts. Additionally throughout the quarter, several development snapshots builds were released for the head, stable/12, and stable/11 branches. Much of this work was sponsored by Rubicon Communications, LLC (netgate.com) and the FreeBSD Foundation. __________________________________________________________________ Cluster Administration Team Links Cluster Administration Team members URL: https://www.freebsd.org/administration.html#t-clusteradm Contact: Cluster Administration Team The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following: * Upgrade all ref- and universe- machines * South Africa mirror (JINX) is online * Package service of Seattle, USA mirror (TUK) is online * Ongoing systems administration work: + Creating accounts for new committers. + Backups of critical infrastructure. + Keeping up with security updates in 3rd party software. Work in progress: * Setup Malaysia (KUL) mirror * Setup Brazil (BRA) mirror * Setup Amsterdam (PKT) mirror * Review the service jails and service administrators operation. * Infrastructure of building aarch64 and powerpc64 packages + NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder. + Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation. + Boot issues with Aarch64 reference machines. * New NYI.net sponsored colocation space in Chicago-land area. * Prepare resource for git working group * Searching for more mirror providers + https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout + https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror __________________________________________________________________ Continuous Integration Links FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD Hardware Testing Lab URL: https://ci.FreeBSD.org/hwlab FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org FreeBSD CI weekly report URL: https://hackmd.io/@FreeBSD-CI FreeBSD Jenkins wiki URL: https://wiki.freebsd.org/Jenkins Hosted CI wiki URL: https://wiki.freebsd.org/HostedCI 3rd Party Software CI URL: https://wiki.freebsd.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://preview.tinyurl.com/y9maauwg FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet The FreeBSD CI team maintains the continuous integration system and related tasks for the FreeBSD project. The CI system regularly checks the committed changes can be successfully built, then performs various tests and analysis of the results. The artifacts from the build jobs are archived in the artifact server for further testing and debugging needs. The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the codes or adjust test infrastructure. The details of these efforts are available in the weekly CI reports. During the first quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD. Important changes: * All the -head jobs are using clang/lld toolchain * All the -head test are using kyua in the base * RISC-V jobs now generate full disk image and run tests in QEMU with OpenSBI * freebsd-doc job also checks building of www.freebsd.org New jobs added: * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/ * https://ci.freebsd.org/job/FreeBSD-head-powerpc64-images/ * https://ci.freebsd.org/job/FreeBSD-head-powerpc64-testvm/ Work in progress: * Collecting and sorting CI tasks and ideas here * Setup the CI stage environment and put the experimental jobs on it * Implementing automatic tests on bare metal hardware * Adding drm ports building test against -CURRENT * Testing and merging pull requests in the FreeBSD-ci repo * Planning for running ztest and network stack tests * Helping more 3rd software get CI on FreeBSD through a hosted CI solution * Adding non-x86 test jobs. * Adding external toolchain related jobs. * Adding more hardware to the hardware lab Please see freebsd-testing@ related tickets for more WIP information, and join the efforts Sponsor: The FreeBSD Foundation __________________________________________________________________ Ports Collection Links About FreeBSD Ports URL: https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/index.html Ports Management Team URL: https://www.freebsd.org/portmgr/index.html Contact: René Ladan Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter. During the last quarter the number of ports settled in at 39,000. There are currently just over 2,400 open PRs of which 640 are unassigned. The last quarter saw 8146 commits by 173 committers to the HEAD branch and 357 commits by 52 committers to the 2020Q1 branch. This means the number of PRs grew although the committer activity remained more or less constant. As always, people come and go. This time we welcomed Loïc Bartoletti (lbartoletti@), Mikael Urankar (mikael@), Kyle Evans (kevans@, who is already a src committer), and Lorenzo Salvadore (salvadore@, who we already know for compiling these reports you are reading right now). We said goodbye to dbn@ and theraven@, who we hope to see back in the future. On the infrastructure side, USES=qca was added and USES=zope was removed. The latter was also due to it was incompatible with Python 3, and portmgr is in the process of removing Python 2.7 from the Ports Tree. This means that all ports that currently rely on Python 2.7 need to be updated to work with Python 3 or be removed. After a long period of work by multiple people, Xorg got updated from the 1.18 to the 1.20 release series. Also, the web browsers were updated: Firefox to version 75.0, Firefox ESR to 68.7.0, and Chromium to 80.0.3987.149. The package manager itself got updated to version 1.13.2. antoine@ ran 29 exp-runs during the last quarter for various updates to KDE, poppler, pkg and build tools; and test compatibility with src changes: removing procfs-based debugging, fixing TLS alignment, and only including libssp_nonshared.a in libc for the i386 and Power architectures. __________________________________________________________________ FreeBSD Graphics Team status report Links Project GitHub page URL: https://github.com/FreeBSDDesktop Contact: FreeBSD Graphics Team Contact: Niclas Zeising The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics stack. This includes graphics drivers, graphics libraries such as the MESA OpenGL implementation, the X.org xserver with related libraries and applications, and Wayland with related libraries and applications. The biggest highlight by far during the previous quarter was the long awaited update of xorg-server to version 1.20. After years of work by many people, this update finally landed in the form of xorg-server 1.20.7. With this update came a couple of new things, most notably, FreeBSD 12 and later was switched to use the udev/evdev backend by default for handling input devices, such as mice and keyboards. Together with this release, the OpenGL library implementation mesa was switched to use DRI3 by default, instead of the older DRI2. These updates caused some fallout when they first were comitted, most notably issues with keyboards. But with help from Michael Gmelin and others on the mailing lists, most issues were sorted fast. Unfortunately version 304 of the nVidia graphics driver is no longer supported as of this release. Since this update, xorg-server has also been bumped to 1.20.8, which is the latest upstream release. Apart from this update, there has also been ongoing work to keep the various drm-kmod ports and packages up to date, mostly in response to changes in FreeBSD CURRENT and to security issues found in the Intel i915 driver. We have also done updates as needed to keep the graphics and input stack up to date and working, and deprecated and removed several old and no longer used drivers, applications and libraries. We have also continued our regularly scheduled bi-weekly meetings. People who are interested in helping out can find us on the x11@FreeBSD.org mailing list, or on our gitter chat: (https://gitter.im/FreeBSDDesktop/Lobby). We are also available in #freebsd-xorg on EFNet. We also have a team area on GitHub where our work repositories can be found: https://github.com/FreeBSDDesktop __________________________________________________________________ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. NFS over TLS implementation Contact: Rick Macklem In an effort to improve NFS security, an internet draft which I expect will become and RFC soon specifies the use of TLS 1.3 to encrypt all data traffic on a Sun RPC connection used for NFS. Although NFS has been able to use sec=krb5p to encrypt data on the wire, this requires a Kerberos environment and, as such, has not been widely adopted. It also required that encryption/decryption be done in software, since only the RPC message NFS arguments are encrypted. Since Kernel TLS is capable of using hardware assist to improve performance and does not require Kerberos, NFS over TLS may be more widely adopted, once implementations are available. Since FreeBSD's kernel TLS requires that data be in ext_pgs mbufs for transmission, most of the work so far has been modifying the NFS code that builds the protocol arguments to optionally use ext_pgs mbufs. Coding changes to handle received ext_pgs mbufs has also been done, although this may not be required by the receive kernel TLS. The kernel RPC has also been modified to do the STARTTLS Null RPC and to do upcalls to userland daemons that perform the SSL_connect()/SSL_accept(), since the kernel TLS does not do this initial handshake. So far only a self signed certificate on the server, with no requirement for the client to have a certificate has been implemented. Work is still needed to be done for the case where the NFS client is expected to have a signed certificate. In particular, it is not obvious to me what the correct solution is for clients that do not have a fixed IP address/DNS name. The code now is about ready for testing, but requires that the kernel TLS be able to support receive as well as transmit. Patches to the kernel TLS for receive are being worked on by jhb@freebsd.org. Once receive side kernel TLS becomes available, the code in subversion under base/projects/nfs-over-tls will need third party testing and a security evaluation by someone familiar with TLS. __________________________________________________________________ Import of the Kyua test framework Links The FreeBSD Test Suite URL: https://wiki.freebsd.org/TestSuite Contact: Brooks Davis The FreeBSD test suite uses the Kyua test framework to run tests. Historically Kyua has been installed from the ports collection (devel/kyua). While this is fine for mainstream architectures, it can pose bootstrapping issues on new architectures and package installation is quite slow under emulation or on FPGA based systems. By including it in the FreeBSD base system we can avoid these issues. We hope that this inclusion will spur testing of embedded platforms and simplify the process of testing within continuous integration systems. We currently plan to retain the devel/kyua port to serve FreeBSD versions without and to serve as a development version. Sponsor: DARPA __________________________________________________________________ Linux compatibility layer update Contact: Edward Tomasz Napierala Work during this quarter focused on source code cleanup and making it easier to debug missing functionality. There were, however, some user-visible changes: added support for TCP_CORK as required by Nginx, added support MAP_32BIT flag, which fixes Mono binaries from Ubuntu Bionic, and a fix for DNS resolution with glibc newer than 2.30, which affected CentOS 8. The Linux Test Project tests that are being run as part of the the FreeBSD Continuous Integration infrastructure now include the Open POSIX test suite. There's still a lot to do: * There are pending reviews for patches that add extended attributes support, and fexecve(2) syscall, and they require wrapping up and committing * There are over 400 failing LTP tests. Some of them are false positives, some are easy to fix bugs, and some require adding new system calls. Any help is welcome. Sponsor: The FreeBSD Foundation __________________________________________________________________ syzkaller on FreeBSD Contact: Mark Johnston Contact: Michael Tuexen See the syzkaller entry in the 2019q1 quarterly report for an introduction to syzkaller. A number of kernel bugs have been found by syzkaller and fixed this quarter, mostly in the network stack and file descriptor table code. Bug investigations have led to improvements in debugging facilities and assertions, for example in the SCTP stack. Syzkaller reproducers have been added to Peter Holm's stress2 suite, helping ensure that regressions are found quickly. The syzkaller instance hosted by backtrace.io (see the 2019q3 report) has been very useful in testing syzkaller improvements and finding bugs. Though Google runs a dedicated syzkaller instance targeting FreeBSD, it has proved fruitful to run multiple instances since they end up building different corpuses and thus discover different, though overlapping, sets of bugs. Support for fuzzing a number of new system calls has been added, including the new copy_file_range() and __realpathat() system calls, and the Capsicum system calls. Some work was also done to audit existing system call definitions to ensure that FreeBSD-specific extensions of POSIX system calls are covered. Work is ongoing to target the Linux emulation layer, and to collect kernel dumps so that one-off crashes with no reproducer have a chance at being diagnosed and fixed. Sponsor: backtrace.io Sponsor: The FreeBSD Foundation __________________________________________________________________ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. if_bridge Contact: Kristof Provost The current implementation of if_bridge uses a single mutex to protect its internal data structures. As a result it's nowhere near as fast as it could be. This is relevant for users who want to run many vnet jails or virtual machines bridged together, for example. As part of this project several new tests have already been added for if_bridge. These are generally very useful for validating any locking changes, and will also help to prevent regressions for other future changes. These tests live in /usr/tests/sys/net/if_bridge_test. The current work is concentrating on investigating if it's possible to leverage the ConcurrencyKit epoch code for the datapath (i.e. bridge_input(), bridge_output(), bridge_forward(), ...). Sponsor: The FreeBSD Foundation __________________________________________________________________ sigfastblock(2) Contact: Konstantin Belousov Rtld services need to be async signal safe. This is needed, for instance, to provide working symbol bindings in signal handlers. For threaded processes, libthr interposes all user-installed signal handlers and saves the signals and related context if signal is delivered while rtld or libthr are in protected section of code. In non-threaded processes, the async safety is provided by changing signal mask for the thread. It is actually better than the interposing done by libthr, since signals are delivered in the right context, instead of libthr attempt of recreate it later. But the unfortunate side-effect is that each rtld entry requires two syscalls, one to set mask, and one to restore it. Typically this adds around 40 or more syscalls on each process startup. Worse, rtld services used by typical language runtime exception handling systems also have the cost of signal mask manipulation. The new sigfastblock(2) syscall was added that allows thread to designate a memory location as fast signal block. If this word contains non-zero value, kernel interprets the thread state same as if all blockable signals are blocked. The facility drastically improves exception handling speed on FreeBSD. Since signals might abort interruptible sleeps, initial implementation read the blocking word on each syscall entry. This is needed to ensure that userspace does not see spurious EINTR/ERESTART if the signals are blocked by the word. Since if kernel cached outdated value for the block word, it would abort sleep, but then ast sees the correct mask and does not deliver the pending signal. There were concerns that this read of the word causes slowdown in syscalls microbenchmarks, esp. on machines with SMAP. The reason is that SMAP requires all userspace access bracketed by STAC/CLAC pair of instructions, which are de-facto serializing (this is not architectural, but all current microarchitectures do it). The decision was made to eliminate the word read, at the cost of possibly returning spurious EINTR. The impact should be minimal, since sigfastblock(2) is not supposed to be the service available to users, it is only assumed for rtld and libthr implementations. Sponsor: The FreeBSD Foundation __________________________________________________________________ arm64 LSE atomic instructions Contact: Mark Johnston An investigation of some performance oddities on EC2 Graviton 2 instances resulted in support for the use of Large System Extension (LSE) atomic instructions in the FreeBSD kernel. LSE is an mandatory ISA extension specified in ARMv8.1. It consists of a number of new atomic instructions, superseding the Load-Linked/Store-Conditional (LL/SC) instruction pairs use when LSE is not implemented. The extension is present in a number of ARMv8 server platforms, including the Cavium ThunderX2 and AWS Graviton 2. The new instructions provide significantly better scalability. A recent set of patches modified the FreeBSD kernel to detect support for LSE and dynamically select an atomic(9) implementation based on the new instructions when all CPUs implement the extension. The initial atomic(9) implementations were provided by Ali Saidi. Some benchmarking on a 64-vCPU Graviton 2 instance shows a ~4% reduction in wall clock time for a kernel build, and a ~15% reduction in system CPU time. Some ARMv8 multi-processor systems implement a heterogenous CPU architecture, referred to as big.LITTLE, in which multiple processor types are used. Surprisingly, such systems may implement the LSE on only a subset of its CPUs, in which case LSE instructions cannot be used by the kernel. As a result, FreeBSD currently waits until all processors are online before selecting the atomic(9) implementation, which precludes the use of ifuncs to provide dynamic selection. Currently atomic(9)'s use of LSE is limited to the kernel. A future project would extend this to userspace, so that FreeBSD system libraries can leverage the LSE instructions when they are available. Sponsor: The FreeBSD Foundation Sponsor: Amazon __________________________________________________________________ FreeBSD on Microsoft HyperV and Azure Links FreeBSD on MicrosoftAzure wiki URL: https://wiki.freebsd.org/MicrosoftAzure FreeBSD on Microsoft HyperV URL: https://wiki.freebsd.org/HyperV Contact: FreeBSD Integration Services Team Contact: Wei Hu Contact: Li-Wen Hsu Wei is working on HyperV Socket support for FreeBSD. HyperV Socket provides a way for the HyperV host and guest to communicate using a common socket interface without networking required. Some features in Azure require HyperV Socket support in the guest. Details of HyperV Socket is available here. The work-in-progress is available here This project is sponsored by Microsoft. Li-Wen is working on the FreeBSD release code related to Azure for the -CURRENT and 12-STABLE branches. The release of 12.1-RELEASE on Azure is also in progress. The work-in-progress is available here This project is sponsored by The FreeBSD Foundation. __________________________________________________________________ FreeBSD on the ARM Morello platform Links The Arm Morello Board URL: https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html The CHERI Project URL: https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ Contact: Andrew Turner Contact: Ruslan Bukin Contact: Brooks Davis Contact: John Baldwin Contact: Robert Watson CHERI (Capability Hardware Enhanced RISC Instructions) extends conventional hardware Instruction-Set Architectures (ISAs) with new architectural features to enable fine-grained memory protection and highly scalable software compartmentalization. The CHERI memory-protection features allow historically memory-unsafe programming languages such as C and C++ to be adapted to provide strong, compatible, and efficient protection against many currently widely exploited vulnerabilities. The CHERI scalable compartmentalization features enable the fine-grained decomposition of operating-system (OS) and application code, to limit the effects of security vulnerabilities in ways that are not supported by current architectures. CHERI is a hybrid capability architecture in that it is able to blend architectural capabilities with conventional MMU-based architectures and microarchitectures, and with conventional software stacks based on virtual memory and C/C++. This approach allows incremental deployment within existing ecosystems, which we have demonstrated through hardware and software prototyping. On 18 October 2019, Arm announced Morello, an experimental CHERI-extended, multicore, superscalar ARMv8-A processor, System-on-Chip (SoC), and prototype board to be available from late 2021. Morello is a part of the UKRI £187M Digital Security by Design Challenge (DSbD) supported by the UK Industrial Strategy Challenge Fund, including a commitment of over £50M commitment by Arm. The aim is to test and validate CHERI extensions to the Arm ISA at scale with the idea that "successful concepts are expected to be carried forward into the architecture." The Morello board is scheduled to ship in the third quarter of 2021. Over the past decade we have developed CheriBSD, a version of FreeBSD supporting CHERI. Our public facing work has been performed on MIPS64 and more recently on RISC-V. Andrew has also developed a port to an earlier version of the Morello ISA which we will be merging into our public repository as simulators and compilers become available. The Morello board is based on the Arm Neoverse N1 platform and derived from the N1SDP development platform. (The AWS Graviton2 systems are also based on the N1 core.) Ruslan and Andrew are currently working to enable all relevant features of the N1 and the N1SDP to give us a solid baseline for work on Morello. These features include the PCI root complex, system memory management unit (SMMU), and CoreSight. To the extent practical we are upstreaming these features to FreeBSD. Sponsor: DARPA, UKRI __________________________________________________________________ NXP ARM64 SoC support Contact: Marcin Wojtas Contact: Artur Rojek Contact: Dawid Gorecki The Semihalf team initiated working on FreeBSD support for the NXP LS1046A SoC LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with integrated packet processing acceleration and high speed peripherals including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide range of networking, storage, security and industrial applications. Completed since the last update: * Clean-up and rebase support on top of FreeBSD-HEAD. Prepare features for the upstream submission: + QorIQ platform clockgen driver + LS1046A clockgen driver + GPIO support for QorIQ boards + QorIQ LS10xx AHCI driver + VF610 I2C controller support + TCA6416 GPIO expander + Epson RX-8803 RTC + QorIQ LS10xx SDHCI driver Todo: * Upstreaming of developed features. This work is expected to be submitted/merged to HEAD in the Q2 of 2020. Sponsor: Alstom Group __________________________________________________________________ ENA FreeBSD Driver Update Links ENA README URL: https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README Contact: Michal Krawczyk Contact: Maciej Bielski Contact: Marcin Wojtas ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. Completed since the last update: * Upstream of the driver to v2.1.1, introducing: + Bug fix for LLQ mode which was causing race when multiple IO queues were used Work in progress: * Last touches for ENA v2.2.0 release, introducing: + Add driver support for the upcoming HW features (like Rx offsets, reporting Tx drops) + Add sysctl tuneables for IO queue number + Create IO queues with optional size backoff + Rework the way of configration of drbr and Rx ring size to be more robust and stable + New HAL version + Other minor fixes and improvements Sponsor: Amazon.com Inc __________________________________________________________________ Architectures Updating platform-specific features and bringing in support for new hardware platforms. FreeBSD/powerpc Project Contact: Mark Linimon Contact: Justin Hibbits Contact: Piotr Kubaj The FreeBSD/powerpc project continues to mature. In addition to the above listed people, we want to acknowledge contributions from adalava, bdragon, luporl, and mikael, among others. Key points: * On -CURRENT, all platforms have been switched to the LLVM 10.0 compiler and lld10. Thus, ld.bfd has been removed from base. * On powerpc64, -CURRENT has been switched to the ELFv2 ABI. Older versions of -CURRENT that either used GCC, or LLVM with the ELFv1 ABI, are no longer supported. * On powerpc64 FreeBSD-STABLE (11 and 12), the platforms still remain on the antique gcc4.2.1 in base. Note: that version of GCC has been removed from the -CURRENT src tree. Support for this configuration is now a "best-effort" status. * On powerpc (32-bit), the ABI did not change as with powerpc64, so upgrading should be easier than with powerpc64. Hardware status: * The aacraid(4) driver has been been fixed for big-endian, thanks to luporl. This means that Talos customers who got the SAS option can now use the onboard SAS. * The ixl(4) driver has also been fixed for big-endian, also thanks to luporl. Software status: * As a result of -CURRENT switching to LLVM/ELFv2, ifuncs became available, meaning that we now have optimized memcpy/bcopy and strncpy functions when running on processors that supports VSX instructions. * powerpc64 is now able to run on QEMU without the need of Huge Pages support. * The virtio drivers have been fixed. * kernel minidump has been fixed. Package status: * A FreeBSD.org package set is available for powerpc64/12 (quarterly). The -quarterly build has just been rebased from 12.0 to 12.1, per the desupport of the older 12.0. The first rebased build has been completed, with 29776 packages being available. * We are currently working on the upgrade of the package builder to a recent -CURRENT. Therefore, the available packages for -CURRENT are still ELFv1, which are not useful. Please contact Mark Linimon for more information. * mesa has been switched to llvm90, which fixes certain problems. * Work continues on firefox and related ports. * More ports fixes are being committed every day. The team would like to thank IBM for the loan of two POWER8 and one POWER9 machines, and Oregon State University (OSU) for providing the hosting. As well, we would like to thank the clusteradm team for keeping the Tyan POWER8 machines online that are hosted at NYI. Also, Piotr would like to thank the FreeBSD Foundation for funding his personal Talos, and Raptor (via its IntegriCloud subsidiary) for loaning a server on which talos.anongoth.pl runs. __________________________________________________________________ FreeBSD/RISC-V Project Links Wiki URL: https://wiki.freebsd.org/riscv Contact: Ruslan Bukin Contact: Mitchell Horne Contact: John Baldwin Contact: Kristof Provost Contact: Philip Paeps Contact: freebsd-riscv Mailing List Contact: IRC #freebsd-riscv channel on freenode It has been a year since the RISC-V project's last status report. In that time, the RISC-V port has benefited from increased attention, and received improvements of all kinds. The RISC-V project has brought in two new src committers. We'd like to welcome Jessica Clarke (jrtc27@), who is a member of CheriBSD, and Nick O'Brien (nick@) of Axiado to the team. Some highlights from last year: * Bring-up on SiFive's Hifive Unleashed board * Support for the OpenSBI firmware and version 0.2 of the SBI specification * Addition of the UART, SPI, and PRCI device drivers for the HiFive Unleashed Last quarter, the default compiler and linker was switched to clang/lld. This required a small number of integration changes on our side, but was mainly enabled by the upstream improvements to the RISC-V LLVM back-end. LLVM's RISC-V support became "official" with LLVM 9, and LLVM 10 has brought further improvements. The LLVM back-end is expected to continue to mature, as there are now many parties actively involved in its development. GCC remains supported as an external toolchain for RISC-V. The CI job for HEAD has been updated to use the clang/lld toolchain, and a GCC job will be added in the future. The RISC-V disk image built in the CI system now contains the full base system and is available on the CI artifact server for further testing. The CI test job was updated to use OpenSBI in qemu. Work on running the FreeBSD test suite for RISC-V in the CI system is in progress. Some progress has been made on supporting the ports framework on RISC-V, which was mostly untested until recently. First, emulators/qemu-user-static-devel received an update adding support for the RISC-V 64-bit ABI, allowing ports to be cross-compiled via poudiere(8). Second, improvements were made to the detection of the soft-float ABI, riscv64sf. Systems running either of the hard-float or soft-float ABIs can now compile and run ports natively. At the moment a small subset of ports can be built successfully, and in the coming months we will look to improve that to include a base set of crucial ports (e.g. python or perl). The CheriBSD project saw an initial port to RISC-V this quarter. Preliminary support for the CHERI ISA has been added to the Spike and QEMU emulators, as well as the necessary changes on the CheriBSD side. Currently, the CheriBSD RISC-V kernel boots, and most statically compiled CHERI binaries run without issue. Although real RISC-V hardware is still scarce, any users with an interest trying out or contributing to the RISC-V port are encouraged to do so. Please visit the recently updated wiki page for information on getting set up, or check out "Getting Started with FreeBSD/RISC-V" in the January/February edition of The FreeBSD Journal. Sponsor: DARPA, AFRL, Axiado, the FreeBSD Foundation __________________________________________________________________ Userland Programs Changes affecting the base system and programs in it. GCC 4.2.1 Retirement Contact: Ed Maste Contact: Warner Losh In 2007 the GNU Compiler Collection (GCC) migrated to GPLv3, which prompted discussions about the future of the FreeBSD tool chain. We held a Tool Chain Summit at BSDCan 2010. Roman Divacky gave an update on the ClangBSD project, building FreeBSD using the new and rapidly improving Clang compiler. Since that time Clang was imported into the FreeBSD base system and was used more and more widely - first being installed but not the default cc, then used by default on i386 and amd64, and later used on more and more targets. In the years since Dimitry Andric has been keeping our copy of Clang up-to-date. GCC 4.2.1 was kept in the tree for a few FreeBSD targets that hadn't migrated to Clang, such as MIPS and Sparc64. By early this year all remaning targets had migrated to external toolchain (contemporary GCC from ports or packages), or had been deprecated. With no in-tree consumers remaining, GCC 4.2.1 was removed from FreeBSD in r358454 on February 29, 2020. Sponsor: The FreeBSD Foundation __________________________________________________________________ elfctl utility Contact: Ed Maste In r340076 Ed added the NT_FREEBSD_FEATURE_CTL ELF note, used to allow binaries to opt out of, or in to, vulnerability mitigation and other features. FreeBSD Foundation intern Bora Özarslan later added a tool to decode and modify the ELF note, but it had yet to be installed by default. In the previous quarter Ed renamed the tool to elfctl, and installed it in /usr/bin. Ed also committed a number of minor bug fixes, code style improvements, etc. Usage examples - list known feature flags: $ elfctl -l Known features are: aslr Disable ASLR protmax Disable implicit PROT_MAX stackgap Disable stack gap wxneeded Requires W+X mappings List feature tags set on a binary: $ elfctl /bin/ls File '/bin/ls' features: aslr 'Disable ASLR' is unset. protmax 'Disable implicit PROT_MAX' is unset. stackgap 'Disable stack gap' is unset. wxneeded 'Requires W+X mappings' is unset. Indicate that a binary requests to opt-out of address randomization: $ elfctl -e +aslr binary Sponsor: The FreeBSD Foundation __________________________________________________________________ ELF Tool Chain Contact: Ed Maste A number of performance and functional improvements were committed to ELF Tool Chain tools over the last quarter. FreeBSD Foundation intern Tiger Gao added DWARF Debug Information Entry (DIE) caching to addr2line which provided a substantial improvement when translating many entries (even surpassing GNU addr2line with a large list). Tiger also rebased and updated an upstream ELF Tool Chain submission to handle DW_AT_ranges and addressed two elfcopy/objcopy bugs: setting the OS/ABI field correctly when converting a binary file to ELF, and correctly adding new sections when there is no .shstrtab section. Ed committed several readelf improvements, including decoding the PROTMAX_DISABLE, STKGAP_DISABLE, and WXNEEDED ELF feature control flags, decoding Xen and GNU Build-ID ELF notes, and improved input validation. Mark Johnston addressed many memory and file descriptor leaks and similar issues reported by Coverity Scan. Sponsor: The FreeBSD Foundation __________________________________________________________________ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. KDE on FreeBSD Links KDE FreeBSD URL: https://freebsd.kde.org/ KDE Community FreeBSD URL: https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages the software produced by the KDE Community for FreeBSD. The software includes a full desktop environment KDE Plasma, the art application Krita, video editor Kdenlive and hundreds of other applications that can be used on any FreeBSD desktop machine. The quarter opened with a new kstars (amateur astronomy application) release landing in ports, and then had the usual regular updates: * three KDE Frameworks releases (on a monthly schedule), * three bugfix releases to the collection of KDE software from the KDE release service (formerly KDE Applications, but it was always more that only-applications), * three bugfix releases to the KDE Plasma desktop. There were no substantial Qt updates but four bugfix releases for devel/cmake, and regular work all over the ports tree. The SDDM login manager was updated to a much newer -- by over a year -- release and patched to support more FreeBSD features. One update to devel/qca dropped compatibility with FreeBSD 11 because upstream no longer supports older OpenSSL versions. There is infrastructure in the ports tree now that adds a USES=qca for Qt applications needing crypto support. The open bugs list remains stable around 28 open issues, with some interesting xkb issues as a highlight. We welcome detailed bug reports and patches. KDE packaging updates are prepared in a copy of the ports repository on GitHub and then merged in SVN. We welcome pull requests there as well. __________________________________________________________________ XFCE Contact: Guido Falsi After the XFCE update to 4.14 a regression was observed in the XFCE window manager xfwm4. It caused window decorations to be drawn wrong or missing with certain graphic hardware setups. It has been reported that the recent update to Xorg server in the ports tree fixes this issue. The updated Xorg server will be available in the next qurterly branch. __________________________________________________________________ Wine on FreeBSD Links Wine homepage URL: https://www.winehq.org Contact: Gerald Pfeifer Contact: Lorenzo Salvadore The standard Wine port has moved from Wine 4.0.3 to Wine 5.0 which represents over 7,400 individual changes including built-in modules in PE format, multi-monitor support, Vulkan 1.1 support, and an XAudio2 re-implementation. After our request for help in the last quarterly report the i386 wine ports have been adopted by salvadore who immediately started resolving existing bugs and improving the ports. Most of this work is ready and we began committing first pieces in March. Since it takes more time than initially expected, we will also update the i386-wine-devel port during this process so that users needing a more recent version can easily get it from the ports tree (or binary packages). On the other hand, we plan on backporting these improvements to i386-wine after i386-wine-devel is done and only then update that port, so that we always guarantee a stable version of i386-wine. __________________________________________________________________ Go on freebsd/arm64 Links Go 1.14 Release Notes URL: https://golang.org/doc/go1.14#freebsd Contact: Mikaël Urankar Contact: Dmitri Goutnik Starting from the recently released version 1.14, Go now officially supports 64-bit ARM architecture on FreeBSD 12.0 or later. This porting effort was initially started by Greg V (aka myfreeweb) and resumed by Shigeru Yamamoto, Dmitri Goutnik and Mikaël Urankar. Dmitry has set up a CI builder to catch regression on FreeBSD aarch64 (it's required by the golang policy for adding a new port to the main Go repository) Work in progress: * a lot of ports use an old version of golang.org/x/sys or golang.org/x/net (to name a few) that doesn't contain the FreeBSD aarch64 bits, work is being done to fix these ports (details are in the bug tracker entry __________________________________________________________________ sysctlmibinfo2 API Links sysctlmibinfo2 URL: https://gitlab.com/alfix/sysctlmibinfo2 Contact: Alfonso Sabato Siciliano In the previous third and fouth quarterly status reports 2019, the sysctlinfo interface and an extension to improve the sysctlbyname() syscall were described, they can access to the sysctl MIB and pass the properties of an object to the userland, but both are quite low level and kernel related. The sysctlmibinfo2 library provides an API to explore the sysctl MIB, to convert an object name in its corresponding Object Identifier and to find an object to get its properties, therefore it is useful to handle an object correctly and to build a sysctl-like utility. Primarily sysctlmibinfo2 wraps the low level interface to provide an easy API, some example: sysctlmif_desc() retrieves the description of an object, sysctlmif_kind() gets the type (string, integer, etc) and sysctlmif_fmt() specifies the format (an integer could represent a deciKelvin, milliKelvin, etc), then it is possible to print properly an object value. Moreover sysctlmibinfo2 provides a high level API: a struct sysctlmif_object definition and functions to build data structures of objects. Example, let's say we want to manage the sound system, sysctlmif_grouplistbyname("hw.snd") returns the list of the Sound Driver objects and sysctlmif_treebyname("dev.pcm") returns a tree where "dev.pcm" is the root node and each subtree represents an audio device. Obviously sysctlmibinfo2 benefits of the features of sysctlinfo: handles OIDs up to CTL_MAXNAME levels, supports capability mode, can seek an object by its name (avoiding to explore the MIB just to find the corresponding OID), gets all info about an object in a time, manages a name with a NULL level or expanded with an input for the sysctl handler. The library can be installed via the devel/libsysctlmibinfo2 port, a manual page and examples in the Public Domain are available for getting started your projects. __________________________________________________________________ Documentation Noteworthy changes in the documentation tree, in manpages, or in external books/documents. FreeBSD Translations on Weblate Links Translate FreeBSD on Weblate wiki URL: https://wiki.freebsd.org/DocTranslationOnWeblate FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/ Contact: Danilo G. Baio Contact: Edson Brandi As announced on January, The FreeBSD Project is adopting Weblate as its web-based continuous localization platform. We are getting new volunteers to the effort and so far these are the numbers: Q1 2020 Status * 10 languages * 47 registered users Languages * Chinese (Simplified) (zh_CN) * Chinese (Traditional) (zh_TW) - Added * French (fr_FR) - Added * German (de_DE) - Added * Italian (it_IT) - Added * Norwegian Bokmål - Added - New language on FreeBSD * Persian (fa_IR) - Added - New language on FreeBSD * Portuguese (Brazil) * Spanish * Turkish (tr-TR) [1] - Added - New language on FreeBSD 1 - Already had an effort in the past. We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. __________________________________________________________________ FreeBSD Manpages overhaul Contact: Gordon Bergling I am currently working on an overhaul for the FreeBSD manpages by updating the HISTORY and STANDARDS sections and while here creating new manpages for parts of the system that missing documentation. FreeBSD has already one of the best documentation available for an UNIX-like operation system, but there are parts that could be improved. For the parts that have been already improved you can have a look at my Phabricator account. If you would like to help on improving the documentation effort, please contact Benedict Reuschling bcr@freebsd.org or me at gbergling@gmail.com. __________________________________________________________________ Third-Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. pot and the nomad pot driver Links pot project URL: https://pot.pizzamig.dev pot on github URL: https://github.com/pizzamig/pot Nomad pot driver URL: https://github.com/trivago/nomad-pot-driver minipot URL: https://github.com/pizzamig/minipot Contact: Luca Pizzamiglio Contact: Esteban Barrios An initial effort to write proper documentation and guides for the pot project has started. The documentation, even if incomplete, is available at here. A F.A.Q. page is available and waiting for users to submit their questions. During the last quarter, some bugs were reported on pot and on the nomad-pot-driver. Both projects released a new bug fix version. Many thanks to 'grembo' and 'Crest' that reported issues, tested and tried our solutions. Thanks also to Mateusz (0mp) for his Pull Requests! pot will have a new release soon (0.11.0), focused on network: * network stack support: ipv4 only, ipv6 only, dual stack. * flexible network setup for alias: adding the ability to use an arbitrary network setup for alias network type Contributions are welcome! Label "good first issue" has been added to issues to invite newcomers to contribute to the project! __________________________________________________________________ NomadBSD Links NomadBSD Website URL: https://www.nomadbsd.org/ NomadBSD Github URL: https://www.github.com/NomadBSD/NomadBSD NomadBSD Forum URL: https://forum.NomadBSD.org/ Contact: NomadBSD Team NomadBSD is a persistent live system for USB flash drives, based on FreeBSD. Together with automatic hardware detection and setup, it is configured to be used as a desktop system that works out of the box, but can also be used for data recovery, for educational purposes, or testing FreeBSD's hardware compatibility. In March we released a new minor version 1.3.1 which improves the configuration of the network interfaces, fixed some bugs and added nomadbsd-chusr and nomadbsd-sysinfo. Further some new features found their way into the release. Some days later the channel explainingcomputers on YouTube released a review video of NomadBSD. The explainingcomputers has almost 600,000 followers and the review was positive so we saw the highest peak in downloads ever! Along with it came a lot of people looking for help on our mailing list and on Twitter so we decided to set up a new support forum. We are looking for people to help the project. Help is much appreciated in all areas: * Translation of program interfaces * Design artwork * Programming new tools, extend existing ones * Tests and Bug reports / UX and feature suggestions * Mirrors outside of Europe Open tasks: * Support installation on disk partitions and add a partition editor GUI. * Complete disk encryption * Add a user-friendly network manager From owner-freebsd-current@freebsd.org Mon Apr 13 01:58: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 2E9B32AF94F; Mon, 13 Apr 2020 01:58:49 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 490sGw096Yz3xFB; Mon, 13 Apr 2020 01:58:47 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 03D1wiGG029673; Sun, 12 Apr 2020 18:58:44 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 03D1wiN4029672; Sun, 12 Apr 2020 18:58:44 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> Subject: Re: Working on Zoom port In-Reply-To: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> To: Eric McCorkle Date: Sun, 12 Apr 2020 18:58:44 -0700 (PDT) CC: FreeBSD Hackers , freebsd-current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 490sGw096Yz3xFB X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [1.28 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.12)[-0.120,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.47)[0.470,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 01:58:49 -0000 > All, > > Given how Zoom is getting used a lot more these days, I've started > working on a port that installs the Zoom linux client. > > Here is a link to my github if anyone wants to help: > > https://github.com/emc2/freebsd-ports/tree/zoom > > > I'm not done yet. The zoom linux client installs a bunch of Qt > libraries in its own directory. These either need to be installed with > a port, or else the right configs need to be set to search for libraries > there. > > I'm going to take a break, but I'm going to circle back to this. > You are aware of the rather large pile of recent security issues surronding zoom I hope. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Apr 13 06:06:22 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 200A02B3C18 for ; Mon, 13 Apr 2020 06:06:22 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 490ymX4lqvz4874 for ; Mon, 13 Apr 2020 06:06:20 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from [46.98.36.103] (helo=thinkpad.flex-it.com.ua) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1jNsEW-000NdY-8Z for freebsd-current@freebsd.org; Mon, 13 Apr 2020 09:06:12 +0300 Subject: Re: Working on Zoom port To: freebsd-current@freebsd.org References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> From: Alexandr Krivulya Message-ID: Date: Mon, 13 Apr 2020 09:06:06 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 490ymX4lqvz4874 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua X-Spamd-Result: default: False [-5.76 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-3.46)[ip: (-9.15), ipnet: 193.239.72.0/22(-4.58), asn: 35297(-3.66), country: UA(0.07)]; RECEIVED_SPAMHAUS_PBL(0.00)[103.36.98.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 06:06:22 -0000 13.04.20 04:58, Rodney W. Grimes пишет: >> All, >> >> Given how Zoom is getting used a lot more these days, I've started >> working on a port that installs the Zoom linux client. >> >> Here is a link to my github if anyone wants to help: >> >> https://github.com/emc2/freebsd-ports/tree/zoom >> >> >> I'm not done yet. The zoom linux client installs a bunch of Qt >> libraries in its own directory. These either need to be installed with >> a port, or else the right configs need to be set to search for libraries >> there. >> >> I'm going to take a break, but I'm going to circle back to this. >> > You are aware of the rather large pile of recent security issues > surronding zoom I hope. Yes, you right. But a lot of people (as me) use it for non-confidential or educational purposes. So working zoom client is very important for me for example. I'm not a developer, but can test your port, Eric. Thank you! From owner-freebsd-current@freebsd.org Mon Apr 13 10:14: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 2D0412B9402; Mon, 13 Apr 2020 10:14:05 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 4914GN2w4Cz4PBK; Mon, 13 Apr 2020 10:14:04 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 9245161B8; Mon, 13 Apr 2020 10:14:03 +0000 (UTC) Subject: Re: Working on Zoom port To: "Rodney W. Grimes" Cc: FreeBSD Hackers , freebsd-current References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> From: Eric McCorkle Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXonLJBYJKwYBBAHaRw8BAQdA4oHU11A8qtqD0EtRofyORHbGX1ZIT/mnk9eceKQx56q0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiZBBMWCABBAhsDBQkB4TOA BQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAFiEEPfuJobsx0Me4pIwLPOOjZtwQVqwFAl6JzIAC GQEACgkQPOOjZtwQVqy2DgD+IRCNNfb7C16fjEHazDMBwmBIMz+CTJUdhoz73P9iy0cA/ixK 83qOW46q1fpCpaZtPvv0FRpcZ5EppnNQ0Yuh40YLuDgEXonLJBIKKwYBBAGXVQEFAQEHQCxw rRXlvDoXgDGv2WMrLy9UaJ4fNWXIdlaiiKZIH7lBAwEIB4h+BBgWCAAmFiEEPfuJobsx0Me4 pIwLPOOjZtwQVqwFAl6JyyQCGwwFCQHhM4AACgkQPOOjZtwQVqxS7wD+JgzZC4995EL9j2iB qhPUZTIgs61IypLoDx+o1zsSfvkBALs+/jvkQL4plT0hGtfFaa0iMnLeIXKd/1FSNGSD9hQI Message-ID: <0e6e47f5-331d-fc95-85f1-9f42e3c0dbbf@metricspace.net> Date: Mon, 13 Apr 2020 06:13:58 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AtspJfqq2sjysCLrhNbEzZUUcyDTCQBwy" X-Rspamd-Queue-Id: 4914GN2w4Cz4PBK X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of eric@metricspace.net has no SPF policy when checking 2001:470:1f11:617::107) smtp.mailfrom=eric@metricspace.net X-Spamd-Result: default: False [-5.41 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_NA(0.00)[]; SIGNED_PGP(-2.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.31)[ip: (-3.25), ipnet: 2001:470::/32(-4.66), asn: 6939(-3.60), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 10:14:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --AtspJfqq2sjysCLrhNbEzZUUcyDTCQBwy Content-Type: multipart/mixed; boundary="ZoWvA77N76ADK7MHi1G4a2YgBu3HXKCXl"; protected-headers="v1" From: Eric McCorkle To: "Rodney W. Grimes" Cc: FreeBSD Hackers , freebsd-current Message-ID: <0e6e47f5-331d-fc95-85f1-9f42e3c0dbbf@metricspace.net> Subject: Re: Working on Zoom port References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> In-Reply-To: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> --ZoWvA77N76ADK7MHi1G4a2YgBu3HXKCXl Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 4/12/20 9:58 PM, Rodney W. Grimes wrote: > You are aware of the rather large pile of recent security issues > surronding zoom I hope. >=20 I am. All the same, some of us have to use it for work... --ZoWvA77N76ADK7MHi1G4a2YgBu3HXKCXl-- --AtspJfqq2sjysCLrhNbEzZUUcyDTCQBwy Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXpQ7ZgAKCRA846Nm3BBW rAi/AQCNkp4P9LbMTejdq6If9qKrXI0hr9uKFSJP6ik4eAjyLAD/c9GohXXDAFpx s/xuvdbpYu0SSOdRWgJwtji+cyqHGQQ= =x7+d -----END PGP SIGNATURE----- --AtspJfqq2sjysCLrhNbEzZUUcyDTCQBwy-- From owner-freebsd-current@freebsd.org Mon Apr 13 15:17: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 81A812C0D47 for ; Mon, 13 Apr 2020 15:17:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491C0X4WG9z3FDX for ; Mon, 13 Apr 2020 15:17:32 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [188.174.63.186] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1jO0EP-00051Z-La for freebsd-current@freebsd.org; Mon, 13 Apr 2020 16:38:37 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id 03DEcaws005497 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 13 Apr 2020 16:38:36 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id 03DEcaKS005496 for freebsd-current@freebsd.org; Mon, 13 Apr 2020 16:38:36 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 13 Apr 2020 16:38:36 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: Re: Working on Zoom port Message-ID: <20200413143836.GB5387@c720-r342378> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 13.0-CURRENT r342378 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.11.1 (2018-12-01) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 188.174.63.186 X-Rspamd-Queue-Id: 491C0X4WG9z3FDX X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of guru@unixarea.de has no SPF policy when checking 178.254.4.101) smtp.mailfrom=guru@unixarea.de X-Spamd-Result: default: False [3.68 / 15.00]; HAS_REPLYTO(0.00)[guru@unixarea.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XOIP(0.00)[]; GREYLIST(0.00)[pass,body]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RECEIVED_SPAMHAUS_PBL(0.00)[186.63.174.188.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_LOW(-0.10)[101.4.254.178.list.dnswl.org : 127.0.5.1]; RSPAMD_URIBL(4.50)[zooom.us]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.50)[-0.495,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[unixarea.de]; NEURAL_HAM_MEDIUM(-0.38)[-0.385,0]; R_SPF_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-1.24)[ip: (-8.02), ipnet: 178.254.0.0/19(0.93), asn: 42730(0.89), country: DE(-0.02)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 15:17:33 -0000 El día lunes, abril 13, 2020 a las 09:06:06a. m. +0300, Alexandr Krivulya escribió: > 13.04.20 04:58, Rodney W. Grimes пишет: > >> All, > >> > >> Given how Zoom is getting used a lot more these days, I've started > >> working on a port that installs the Zoom linux client. > >> > >> Here is a link to my github if anyone wants to help: > >> > >> https://github.com/emc2/freebsd-ports/tree/zoom > >> > >> > >> I'm not done yet. The zoom linux client installs a bunch of Qt > >> libraries in its own directory. These either need to be installed with > >> a port, or else the right configs need to be set to search for libraries > >> there. > >> > >> I'm going to take a break, but I'm going to circle back to this. > >> > > You are aware of the rather large pile of recent security issues > > surronding zoom I hope. > > Yes, you right. But a lot of people (as me) use it for non-confidential > or educational purposes. So working zoom client is very important for me > for example. > I'm not a developer, but can test your port, Eric. Thank you! Hello, Please, can some kind soul enlighten me a bit how this (zooom.us) works from a technical point of view. The background of my question, and I've never used zoom before, is that my son receives via mail MS OutLook invitations (due to the closing of his misuc shool for Corona virus) and if I open them on my Windows business laptop, it downloads for every new session some piece(s) of software, which is then executed and establishes an audio/video session with his teacher. How this works exactly a how this is supposed to work on FreeBSD? Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Mon Apr 13 16:32:41 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 A1D772C323D for ; Mon, 13 Apr 2020 16:32:41 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491DgD3cb0z3NTT for ; Mon, 13 Apr 2020 16:32:40 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from [46.98.36.103] (helo=thinkpad.flex-it.com.ua) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1jO20j-000P5M-4g for freebsd-current@freebsd.org; Mon, 13 Apr 2020 19:32:37 +0300 Subject: Re: Working on Zoom port To: freebsd-current@freebsd.org References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> From: Alexandr Krivulya Message-ID: Date: Mon, 13 Apr 2020 19:32:31 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200413143836.GB5387@c720-r342378> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 491DgD3cb0z3NTT X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua X-Spamd-Result: default: False [-0.69 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RSPAMD_URIBL(4.50)[zooom.us]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(0.00)[+mx:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; RCPT_COUNT_ONE(0.00)[1]; BAD_REP_POLICIES(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[103.36.98.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; IP_SCORE(-3.42)[ip: (-9.03), ipnet: 193.239.72.0/22(-4.51), asn: 35297(-3.61), country: UA(0.07)]; NEURAL_HAM_LONG(-0.90)[-0.896,0]; NEURAL_HAM_MEDIUM(-0.88)[-0.878,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 16:32:41 -0000 13.04.20 17:38, Matthias Apitz пишет: > El día lunes, abril 13, 2020 a las 09:06:06a. m. +0300, Alexandr Krivulya escribió: > >> 13.04.20 04:58, Rodney W. Grimes пишет: >>>> All, >>>> >>>> Given how Zoom is getting used a lot more these days, I've started >>>> working on a port that installs the Zoom linux client. >>>> >>>> Here is a link to my github if anyone wants to help: >>>> >>>> https://github.com/emc2/freebsd-ports/tree/zoom >>>> >>>> >>>> I'm not done yet. The zoom linux client installs a bunch of Qt >>>> libraries in its own directory. These either need to be installed with >>>> a port, or else the right configs need to be set to search for libraries >>>> there. >>>> >>>> I'm going to take a break, but I'm going to circle back to this. >>>> >>> You are aware of the rather large pile of recent security issues >>> surronding zoom I hope. >> Yes, you right. But a lot of people (as me) use it for non-confidential >> or educational purposes. So working zoom client is very important for me >> for example. >> I'm not a developer, but can test your port, Eric. Thank you! > Hello, > > Please, can some kind soul enlighten me a bit how this (zooom.us) works > from a technical point of view. The background of my question, and I've > never used zoom before, is that my son receives via mail MS OutLook > invitations (due to the closing of his misuc shool for Corona virus) and > if I open them on my Windows business laptop, it downloads > for every new session some piece(s) of software, which is then executed > and establishes an audio/video session with his teacher. > > How this works exactly a how this is supposed to work on FreeBSD? > > Thanks > > matthias Hello! All of you need - a conference ID and probably password. Now you can participate in conference by pressing Join button in zoom client and providing this ID and/or password. Conference ID is part of your url after '/j/' - for example conference url is https://zoom.us/j/111222333?pwd=ejhxhshyocdyaszT9 and conference ID is 111222333. BTW, you can join conference via web-client from browser by url https://zoom.us/wc/join/YOUR-CONFERENCE-ID, but with firefox prior version 77 (nightly) without audio and with chromium without webcam (FreeBSD only, also audio and screen sharing works). From owner-freebsd-current@freebsd.org Mon Apr 13 17:36: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 CF0AF2C465B for ; Mon, 13 Apr 2020 17:36:15 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491G4Z4lz7z3xZh for ; Mon, 13 Apr 2020 17:36:14 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [188.174.63.186] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1jO30G-0002Js-7k for freebsd-current@freebsd.org; Mon, 13 Apr 2020 19:36:12 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id 03DHaBv3008325 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 13 Apr 2020 19:36:11 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id 03DHaBAK008324 for freebsd-current@freebsd.org; Mon, 13 Apr 2020 19:36:11 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 13 Apr 2020 19:36:11 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: Re: Working on Zoom port Message-ID: <20200413173611.GA8043@c720-r342378> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 13.0-CURRENT r342378 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.11.1 (2018-12-01) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 188.174.63.186 X-Rspamd-Queue-Id: 491G4Z4lz7z3xZh X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of guru@unixarea.de has no SPF policy when checking 178.254.4.101) smtp.mailfrom=guru@unixarea.de X-Spamd-Result: default: False [-1.94 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[guru@unixarea.de]; HAS_XOIP(0.00)[]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RECEIVED_SPAMHAUS_PBL(0.00)[186.63.174.188.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; IP_SCORE(-1.24)[ip: (-7.98), ipnet: 178.254.0.0/19(0.93), asn: 42730(0.88), country: DE(-0.02)]; R_DKIM_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[101.4.254.178.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[unixarea.de]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 17:36:15 -0000 El día lunes, abril 13, 2020 a las 07:32:31p. m. +0300, Alexandr Krivulya escribió: > Hello! > All of you need - a conference ID and probably password. Now you can > participate in conference by pressing Join button in zoom client and > providing this ID and/or password. Conference ID is part of your url > after '/j/' - for example conference url is > https://zoom.us/j/111222333?pwd=ejhxhshyocdyaszT9 and conference ID is > 111222333. BTW, you can join conference via web-client from browser by > url https://zoom.us/wc/join/YOUR-CONFERENCE-ID, but with firefox prior > version 77 (nightly) without audio and with chromium without webcam > (FreeBSD only, also audio and screen sharing works). Hello Alexandr, Thanks for the kind explanation. With this I understand now the invitation data: Bernhard S. invites you to a scheduled Zoom-meeting. Zoom-Meeting join https://us04web.zoom.us/j/454819xxx?pwd=OUtlOHB4xxxxxxxxxxxxxxxxRTk2dz09 Meeting-ID: 454 819 xxx Passwort: 8xWxxx And, your port will make the Linux client running on FreeBSD? Wouldn't it be an option to make video working in chromium on FreeBSD? Thanks again matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub From owner-freebsd-current@freebsd.org Mon Apr 13 17:47: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 05B182C4B1F for ; Mon, 13 Apr 2020 17:47:26 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 491GKT064Qz3yQT for ; Mon, 13 Apr 2020 17:47:24 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi1-f169.google.com with SMTP id j16so8049759oih.10 for ; Mon, 13 Apr 2020 10:47:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:content-transfer-encoding; bh=7Ziq+NvT9aU7yhkCpICfdK7g9esPE0aWR+kpr42t0Pw=; b=WjK1kKfCEXGVe54uz6Hnf6HnHI/hmEAug81RmP+2WkgDWUFKnha/DEyWKgVRTGGhIQ 65p537EcFsCcIO5CrO+4pyEJdq8QTcpw+LDyrFFzE4NqSdiVgtxRsxwv7hVRO0ETgBtw aGrQnvruy0zy62OGwF7rLUf6tFD5qM29EYSElpZcvUDlC6hQn7dH1aum+PMXR8vZe802 nI04aaDI2nSa/J7RaBaC28mrMAQXVRo3L27x9xwEklqL/Ah0Zdf5NbZNDHrFBSb6wdfZ OBYytzvMp9vWv0UTJ8ww2YmyGgnxJynmGDrNTLfmM9gYr+k5BF9rt+bTcov1ymuMte4C 6l9A== X-Gm-Message-State: AGi0PuY/DS+OV4zuP7cmBK7HLa8lZujCVlZvbMaUqOkYdLCbeZC+zCaL BV2/Fecz8My/ACM0Vs3RLYYv7WLC X-Google-Smtp-Source: APiQypLNnxQNAmlJdXb1NMMBhPuePkKP1M50naYbYys3sPR6spl6VYxgIP00R7DPaLTw75TNJISBaw== X-Received: by 2002:aca:4b94:: with SMTP id y142mr1587619oia.170.1586800043375; Mon, 13 Apr 2020 10:47:23 -0700 (PDT) Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com. [209.85.167.180]) by smtp.gmail.com with ESMTPSA id v2sm2536990oiv.56.2020.04.13.10.47.22 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Apr 2020 10:47:23 -0700 (PDT) Received: by mail-oi1-f180.google.com with SMTP id k9so8043017oia.8 for ; Mon, 13 Apr 2020 10:47:22 -0700 (PDT) X-Received: by 2002:a05:6808:2d3:: with SMTP id a19mr4052760oid.135.1586800042508; Mon, 13 Apr 2020 10:47:22 -0700 (PDT) MIME-Version: 1.0 References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> <20200413173611.GA8043@c720-r342378> In-Reply-To: <20200413173611.GA8043@c720-r342378> Reply-To: cem@freebsd.org From: Conrad Meyer Date: Mon, 13 Apr 2020 10:47:11 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Working on Zoom port To: Matthias Apitz , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 491GKT064Qz3yQT X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.167.169 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-2.25 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[169.167.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.25)[ip: (-0.38), ipnet: 209.85.128.0/17(-0.40), asn: 15169(-0.43), country: US(-0.05)]; RWL_MAILSPIKE_POSSIBLE(0.00)[169.167.85.209.rep.mailspike.net : 127.0.0.17]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 17:47:26 -0000 Hi Matthias, >From personal experience, receiving Zoom video in conferences with native www/chromium and the web interface works perfectly fine and has for some time (at least the last year). I think, but don't recall if I personally tried it, that mic support is fine as well. Audio playback is fine. Unfortunately, until recently, the webcam support in our chromium port was disabled; it is restored in the '80.mumble.163_1' version of the port. There have been mixed reports of success (or not) with webcams in chromium after 163_1; it works ok for some people and there are flickering issues for others. I don't have a supported webcam easily available to test, but would appreciate more data (either "it works for me," or "it doesn't, in this way") in PR 245505 ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245505 ). So, it may work well; it may only work half-duplex for video. Try it out! Firefox support may be better; I'm not familiar with the status of our Firefox port. Best regards, Conrad P.S., the web interface only offers a subset of the full functionality, so I believe the efforts to port the linux binary client are valuable. Still, the web interface works well enough that it might be an option. It's what I use at my day job. On Mon, Apr 13, 2020 at 10:36 AM Matthias Apitz wrote: > > El d=C3=ADa lunes, abril 13, 2020 a las 07:32:31p. m. +0300, Alexandr Kri= vulya escribi=C3=B3: > > > Hello! > > All of you need - a conference ID and probably password. Now you can > > participate in conference by pressing Join button in zoom client and > > providing this ID and/or password. Conference ID is part of your url > > after '/j/' - for example conference url is > > https://zoom.us/j/111222333?pwd=3DejhxhshyocdyaszT9 and conference ID i= s > > 111222333. BTW, you can join conference via web-client from browser by > > url https://zoom.us/wc/join/YOUR-CONFERENCE-ID, but with firefox prior > > version 77 (nightly) without audio and with chromium without webcam > > (FreeBSD only, also audio and screen sharing works). > > Hello Alexandr, > Thanks for the kind explanation. With this I understand now the > invitation data: > > Bernhard S. invites you to a scheduled Zoom-meeting. > Zoom-Meeting join > > https://us04web.zoom.us/j/454819xxx?pwd=3DOUtlOHB4xxxxxxxxxxxxxxxxRTk= 2dz09 > > Meeting-ID: 454 819 xxx > Passwort: 8xWxxx > > And, your port will make the Linux client running on FreeBSD? > > Wouldn't it be an option to make video working in chromium on FreeBSD? > > Thanks again > > matthias > > -- > Matthias Apitz, =E2=9C=89 guru@unixarea.de, http://www.unixarea.de/ +49-1= 76-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > _______________________________________________ > 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 Mon Apr 13 18:59:37 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 948E32C62C4; Mon, 13 Apr 2020 18:59:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 491Hwm1NWFz438Z; Mon, 13 Apr 2020 18:59:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.206] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id be881b08 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 13 Apr 2020 18:59:29 +0000 (UTC) Subject: Re: Working on Zoom port To: Eric McCorkle , FreeBSD Hackers , freebsd-current References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> From: Pete Wright Message-ID: Date: Mon, 13 Apr 2020 11:59:28 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 491Hwm1NWFz438Z X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(-2.77)[ip: (-9.26), ipnet: 174.136.96.0/20(-4.12), asn: 25795(-0.41), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 18:59:37 -0000 On 4/12/20 12:26 PM, Eric McCorkle wrote: > All, > > Given how Zoom is getting used a lot more these days, I've started > working on a port that installs the Zoom linux client. > > Here is a link to my github if anyone wants to help: > > https://github.com/emc2/freebsd-ports/tree/zoom > > > I'm not done yet. The zoom linux client installs a bunch of Qt > libraries in its own directory. These either need to be installed with > a port, or else the right configs need to be set to search for libraries > there. > > I'm going to take a break, but I'm going to circle back to this. > Thanks Eric, I remember trying to get this working several months ago via the linux compatibility layer and got stuck.  i hope to take another wack at it based on your repository.  in my ideal world i'd be able to get this working in a jail via, but i think just getting the bits to work is probably the most important task. i've had working solutions based on jitsi and riot.im with acceptable performance, so i suspect our webcamd bits are in good enough shape to support this.  interested to see how how this effort progresses :) -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Mon Apr 13 19:09:52 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 64F372C66A5; Mon, 13 Apr 2020 19:09:52 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mx6-out7.antispamcloud.com (mx6-out7.antispamcloud.com [95.211.2.198]) (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 491J8Y5CWXz43db; Mon, 13 Apr 2020 19:09:48 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from yo.nortado.com ([178.128.145.22]) by mx105.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1jO4Sk-0009OF-7H; Mon, 13 Apr 2020 21:09:45 +0200 Received: from nortado.com (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by yo.nortado.com (Postfix) with ESMTPSA id 3F29C260B5B; Mon, 13 Apr 2020 19:09:35 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 13 Apr 2020 15:09:35 -0400 From: Waitman Gobble To: Pete Wright Cc: Eric McCorkle , FreeBSD Hackers , freebsd-current Subject: Re: Working on Zoom port Reply-To: waitman@waitman.net In-Reply-To: References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> User-Agent: Roundcube Webmail/1.4.2 Message-ID: X-Sender: waitman@waitman.net Organization: Waitman Gobble X-Originating-IP: 178.128.145.22 X-EuropeanMX-Domain: waitman.net X-EuropeanMX-Username: wago X-EuropeanMX-Outgoing-Class: unsure X-EuropeanMX-Outgoing-Evidence: Combined (0.14) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0VxB0mWeGZk2wSOLROvd+japSDasLI4SayDByyq9LIhVpn3iyN0OhS2z Mzt63xyM60TNWdUk1Ol2OGx3IfrIJKyP9eGNFz9TW9u+Jt8z2T3Kt4FCDfTrob8nSjJ07tRP4ULb F8CC0LnhgQQLIg1Y5+UPGvDuFh7QVNM7ktBErHxEAGNLO5xjHiGDHbmUI8Haq78QxW4/uvY7TqKY ZF11oE/LSYayC+7SkfekM+pEYsng37pzJn/4aesV+4FIdAMh9B5e973vehgRRMJdd1x498QWMjET lJm10LPC4weQTXkIGZLIHyBgucWCg+Uk0L+ZsaGiCLNBP5EaFuQqo7XeLyWjmYVQnec0JEgL7iPG Zspc6SoHsJyHSpfPjnGsVqdfLBtCheh5C7lovH0u37yux7EfgMf4XRgCk/48zRqgqXKNkBShG6Tp I4KXCxH5Seuhs86GsVpKkOR92RIEPrzbiL92GXVwzwcXfB350+n4irIOm4aVlBObnVhI6K7gAuPO 4330hhMlTIZgxlSmau//kM+ez1OLpXUS8pu2Pqft5x+tZ6NDi09Sehf7j1ee0+xFN4xtNBxr6Qte Skko+H6Sty2Ht9p5migV+wKZZMMHDParyA8R+6RgjrI6aI+8RofqAZ3r7oAH2YSlFfm/LrtbAON6 EipRzMVZ5LqwTx7Vvn9SQGDjK8yfkwEB3Am5tquL+DlwRHGlZ3mQyaEJ2TxT9jvKLaRJNHm7F49+ QMHnFjdUSiKpjX8Diqj7bGgmXqZT03nMP5ellsEj6vAssSbsJLHVMYsio+isNbHDrclyZ/CtbjUa TeA10p5YqL3vgxqrmlvxDejqc1gSvA2YxCROcMJJzShZr3VYdGZWFROFaQdNeHkNjfXxRRqyRbYy SsHpHBPhNYIpjFfrge5A/rkxuFAccBIk1Sag4dKiqCrF8eZZOVFQFoLeBNwFM8uQL+1vA/w6i4ia OyhOjNAfo7IbI5ifinkO4WSMINISaUxfMFKCWli9r39cNUyFa3D67wXM2VtIDpT88TEiAnXgl0Wd 2i1lFawbDxpzYifNwA/+CbHAB5rbFPDebgnpvxKy52VmbPfu5doKQn08ga6eUI4mmMJAKzJilPq0 IsaNzChiAYty X-Report-Abuse-To: spam@quarantine12.antispamcloud.com X-Rspamd-Queue-Id: 491J8Y5CWXz43db X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.49 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[waitman@waitman.net]; HAS_XOIP(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[waitman.net:+]; DMARC_POLICY_ALLOW(0.00)[waitman.net,reject]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.37)[ipnet: 95.211.0.0/16(0.94), asn: 60781(0.87), country: NL(0.03)]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_LOW(-0.10)[198.2.211.95.list.dnswl.org : 127.0.3.1]; ASN(0.00)[asn:60781, ipnet:95.211.0.0/16, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_SPF_FAIL(0.00)[-all]; R_DKIM_ALLOW(-0.20)[waitman.net:s=eueu]; NEURAL_HAM_MEDIUM(-0.98)[-0.978,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-0.98)[-0.979,0]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 19:09:52 -0000 On 2020-04-13 14:59, Pete Wright wrote: > On 4/12/20 12:26 PM, Eric McCorkle wrote: >> All, >> >> Given how Zoom is getting used a lot more these days, I've started >> working on a port that installs the Zoom linux client. >> >> Here is a link to my github if anyone wants to help: >> >> https://github.com/emc2/freebsd-ports/tree/zoom >> >> >> I'm not done yet. The zoom linux client installs a bunch of Qt >> libraries in its own directory. These either need to be installed >> with >> a port, or else the right configs need to be set to search for >> libraries >> there. >> >> I'm going to take a break, but I'm going to circle back to this. >> > > Thanks Eric, I remember trying to get this working several months ago > via the linux compatibility layer and got stuck.  i hope to take > another wack at it based on your repository.  in my ideal world i'd be > able to get this working in a jail via, but i think just getting the > bits to work is probably the most important task. > > i've had working solutions based on jitsi and riot.im with acceptable > performance, so i suspect our webcamd bits are in good enough shape to > support this.  interested to see how how this effort progresses :) > > -pete A few things - using "latest" for the distfile isn't going to work, as soon as they update the file it will break the port. Also they ship a whole bunch of libraries without any licenses. For sure there is Apache and BSD code in there. I guess somebody could write Boston to the the GPL licenses, but the other libraries are totally a no-go without licenses. Are they using the "commerical" version of Qt? Or maybe they just got liberal with it like they did the other stuff? I think the commercial version is different than normal people have, if not now then soon. -- Waitman Gobble From owner-freebsd-current@freebsd.org Mon Apr 13 22:23: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 6E8A82AB0A8; Mon, 13 Apr 2020 22:23:31 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (static-108-31-38-18.washdc.fios.verizon.net [108.31.38.18]) by mx1.freebsd.org (Postfix) with ESMTP id 491NS21kbvz4JB1; Mon, 13 Apr 2020 22:23:29 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f] (unknown [IPv6:2001:470:1f11:617:3210:b3ff:fe77:ca3f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id D55F96341; Mon, 13 Apr 2020 22:23:22 +0000 (UTC) Subject: Re: Working on Zoom port To: Pete Wright , FreeBSD Hackers , freebsd-current References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> From: Eric McCorkle Autocrypt: addr=eric@metricspace.net; prefer-encrypt=mutual; keydata= mDMEXonLJBYJKwYBBAHaRw8BAQdA4oHU11A8qtqD0EtRofyORHbGX1ZIT/mnk9eceKQx56q0 JEVyaWMgTWNDb3JrbGUgPGVyaWNAbWV0cmljc3BhY2UubmV0PoiZBBMWCABBAhsDBQkB4TOA BQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAFiEEPfuJobsx0Me4pIwLPOOjZtwQVqwFAl6JzIAC GQEACgkQPOOjZtwQVqy2DgD+IRCNNfb7C16fjEHazDMBwmBIMz+CTJUdhoz73P9iy0cA/ixK 83qOW46q1fpCpaZtPvv0FRpcZ5EppnNQ0Yuh40YLuDgEXonLJBIKKwYBBAGXVQEFAQEHQCxw rRXlvDoXgDGv2WMrLy9UaJ4fNWXIdlaiiKZIH7lBAwEIB4h+BBgWCAAmFiEEPfuJobsx0Me4 pIwLPOOjZtwQVqwFAl6JyyQCGwwFCQHhM4AACgkQPOOjZtwQVqxS7wD+JgzZC4995EL9j2iB qhPUZTIgs61IypLoDx+o1zsSfvkBALs+/jvkQL4plT0hGtfFaa0iMnLeIXKd/1FSNGSD9hQI Message-ID: Date: Mon, 13 Apr 2020 18:23:18 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5LzCOuGHJvq91mNUSjw4aFHZrIzCcbcbG" X-Rspamd-Queue-Id: 491NS21kbvz4JB1 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of eric@metricspace.net has no SPF policy when checking 108.31.38.18) smtp.mailfrom=eric@metricspace.net X-Spamd-Result: default: False [-3.57 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; DMARC_NA(0.00)[metricspace.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_NA(0.00)[]; SIGNED_PGP(-2.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:701, ipnet:108.31.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.47)[ip: (-1.91), ipnet: 108.31.0.0/16(-0.95), asn: 701(0.57), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 22:23:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5LzCOuGHJvq91mNUSjw4aFHZrIzCcbcbG Content-Type: multipart/mixed; boundary="IBO1bw3Np3kIFqfSDUdXJBmHs1ndG5stJ"; protected-headers="v1" From: Eric McCorkle To: Pete Wright , FreeBSD Hackers , freebsd-current Message-ID: Subject: Re: Working on Zoom port References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> In-Reply-To: --IBO1bw3Np3kIFqfSDUdXJBmHs1ndG5stJ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 4/13/20 2:59 PM, Pete Wright wrote: > Thanks Eric, I remember trying to get this working several months ago > via the linux compatibility layer and got stuck.=C2=A0 i hope to take a= nother > wack at it based on your repository.=C2=A0 in my ideal world i'd be abl= e to > get this working in a jail via, but i think just getting the bits to > work is probably the most important task. >=20 > i've had working solutions based on jitsi and riot.im with acceptable > performance, so i suspect our webcamd bits are in good enough shape to > support this.=C2=A0 interested to see how how this effort progresses :)= FWIW, I got the webcam working on the librem laptops. Only weird part is that it creates two video devices that represent the same hardware. --IBO1bw3Np3kIFqfSDUdXJBmHs1ndG5stJ-- --5LzCOuGHJvq91mNUSjw4aFHZrIzCcbcbG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXpTmVgAKCRA846Nm3BBW rHHJAQC9KjwfpEWifjt/BJzLbH0nY7cMxaFXvCfLu7vQu9+J9wEA01nWNVxHQoJL TM1g5vzKr6Pwve7xt/c8/cZpi1wVkwA= =8kd1 -----END PGP SIGNATURE----- --5LzCOuGHJvq91mNUSjw4aFHZrIzCcbcbG-- From owner-freebsd-current@freebsd.org Mon Apr 13 23:28: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 D0CB52AC61E; Mon, 13 Apr 2020 23:28:26 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 491Ptx6L96z4MB6; Mon, 13 Apr 2020 23:28:25 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52C7DA.dip0.t-ipconnect.de [46.82.199.218]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id 03DNSJMY074444 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Apr 2020 01:28:23 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id 03DNSI4C000364; Tue, 14 Apr 2020 01:28:18 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id 03DNS6T4062727; Tue, 14 Apr 2020 01:28:18 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <202004132328.03DNS6T4062727@fire.js.berklix.net> cc: FreeBSD Hackers , freebsd-current Subject: Re: Working on Zoom port From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Sun, 12 Apr 2020 18:58:44 -0700." <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> Date: Tue, 14 Apr 2020 01:28:06 +0200 X-Rspamd-Queue-Id: 491Ptx6L96z4MB6 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jhs@berklix.com has no SPF policy when checking 94.185.90.68) smtp.mailfrom=jhs@berklix.com X-Spamd-Result: default: False [4.88 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.984,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.00)[ip: (0.02), ipnet: 94.185.88.0/22(0.01), asn: 33824(-0.00), country: DE(-0.02)]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; MISSING_TO(2.00)[]; NEURAL_SPAM_LONG(1.00)[0.997,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[218.199.82.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2020 23:28:26 -0000 "Rodney W. Grimes" wrote: > > All, > > > > Given how Zoom is getting used a lot more these days, I've started > > working on a port that installs the Zoom linux client. > > > > Here is a link to my github if anyone wants to help: > > > > https://github.com/emc2/freebsd-ports/tree/zoom > > > > > > I'm not done yet. The zoom linux client installs a bunch of Qt > > libraries in its own directory. These either need to be installed with > > a port, or else the right configs need to be set to search for libraries > > there. > > > > I'm going to take a break, but I'm going to circle back to this. > > > > You are aware of the rather large pile of recent security issues > surronding zoom I hope. https://www.theregister.co.uk/2020/04/08/zoom_security_stamos/ 8 Apr 2020 "As Zoom bans spread over privacy concerns, vid-conf biz taps up Stamos as firefighter in totally-not-a-PR-stunt move" https://www.theregister.co.uk/2020/03/27/doc_searls_zoom_privacy/ 27 Mar 2020 Yeah, that Zoom app you're trusting with work chatter? It lives with 'vampires feeding on the blood of human data' Cheers -- Julian Stacey, Consultant Systems Engineer, BSD Linux http://berklix.com/jhs/ http://berklix.org/corona/ Real Brexit 31 Dec 2020 will further damage UK & EU From owner-freebsd-current@freebsd.org Tue Apr 14 06:49: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 5D6232B627A for ; Tue, 14 Apr 2020 06:49:44 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 491bh66vLtz3FYY for ; Tue, 14 Apr 2020 06:49:42 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from [91.243.202.199] (helo=thinkpad.flex-it.com.ua) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1jOFO1-0004sn-5n; Tue, 14 Apr 2020 09:49:33 +0300 From: Alexandr Krivulya Subject: Re: Working on Zoom port To: =?UTF-8?B?0JbQuNC70LjQvSwg0JzQuNGF0LDQuNC7INCh0LXRgNCz0LXQtdCy0LjRhw==?= Cc: freebsd-current@freebsd.org References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> Message-ID: Date: Tue, 14 Apr 2020 09:49:27 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.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: 491bh66vLtz3FYY X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua X-Spamd-Result: default: False [-5.73 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[shurik.kiev.ua]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.43)[ip: (-9.05), ipnet: 193.239.72.0/22(-4.53), asn: 35297(-3.62), country: UA(0.07)]; RECEIVED_SPAMHAUS_PBL(0.00)[199.202.243.91.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 06:49:44 -0000 13.04.20 19:59, Жилин, Михаил Сергеевич пишет: > Hi, > > Does the latest Firefox support audio in Zoom? It's really the only > pain point of Firefox + Zoom on FreeBSD. > I'm forced to use it every day, so Web client is cool except for audio > issue on Firefox. > According to [1] latest firefox nightly builds now support audio in zoom. This nightly builds are not available for FreeBSD but you can try to build it from sources. [1] https://www.reddit.com/r/firefox/comments/fsz3rk/implementation_of_the_audioworklets_makes_firefox/ From owner-freebsd-current@freebsd.org Tue Apr 14 08:31:38 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 7862C2B945C for ; Tue, 14 Apr 2020 08:31:38 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 491dxk1pktz3MTW; Tue, 14 Apr 2020 08:31:38 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 31C336DDE; Tue, 14 Apr 2020 08:31:38 +0000 (UTC) From: Jan Beich To: Alexandr Krivulya Cc: =?utf-8?B?0JbQuNC70LjQvSwg0JzQuNGF0LDQuNC7INCh0LXRgNCz0LXQtdCy0LjRhw==?= , freebsd-current@freebsd.org Subject: Re: Working on Zoom port References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> Date: Tue, 14 Apr 2020 10:31:36 +0200 In-Reply-To: (Alexandr Krivulya's message of "Tue, 14 Apr 2020 09:49:27 +0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 08:31:38 -0000 Alexandr Krivulya writes: > 13.04.20 19:59, =D0=96=D0=B8=D0=BB=D0=B8=D0=BD, =D0=9C=D0=B8=D1=85=D0=B0= =D0=B8=D0=BB =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B5=D0=B2=D0=B8=D1=87 =D0=BF= =D0=B8=D1=88=D0=B5=D1=82: > >> Hi, >> >> Does the latest Firefox support audio in Zoom? It's really the only >> pain point of Firefox=C2=A0+ Zoom on FreeBSD. >> I'm forced to use it every day, so Web client is cool except for >> audio issue on Firefox. >> > > According to [1] latest firefox nightly builds now support audio in > zoom. This nightly builds are not available for FreeBSD but you can > try to build it from sources. > > [1] > https://www.reddit.com/r/firefox/comments/fsz3rk/implementation_of_the_au= dioworklets_makes_firefox/ If that Nightly means 76 then see bug 245422 for downstream version. Unfortunately, it doesn't build yet due to a bug in Clang or Rust. From owner-freebsd-current@freebsd.org Tue Apr 14 09:51: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 CDB312BAF7B; Tue, 14 Apr 2020 09:51:20 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 491gjh4jdTz3wkC; Tue, 14 Apr 2020 09:51:20 +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 82F417D71; Tue, 14 Apr 2020 09:51:20 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 1C11ECD8C; Tue, 14 Apr 2020 11:51:19 +0200 (CEST) From: "Kristof Provost" To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: CFT: if_bridge performance improvements Date: Tue, 14 Apr 2020 11:51:15 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: <5377E42E-4C01-4BCC-B934-011AC3448B54@FreeBSD.org> 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.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 09:51:20 -0000 Hi, Thanks to support from The FreeBSD Foundation I’ve been able to work on improving the throughput of if_bridge. It changes the (data path) locking to use the NET_EPOCH infrastructure. Benchmarking shows substantial improvements (x5 in test setups). This work is ready for wider testing now. It’s under review here: https://reviews.freebsd.org/D24250 Patch for CURRENT: https://reviews.freebsd.org/D24250?download=true Patches for stable/12: https://people.freebsd.org/~kp/if_bridge/stable_12/ I’m not currently aware of any panics or issues resulting from these patches. Do note that if you run a Bhyve + tap on bridges setup the tap code suffers from a similar bottleneck and you will likely not see major improvements in single VM to host throughput. I would expect, but have not tested, improvements in overall throughput (i.e. when multiple VMs send traffic at the same time). Best regards, Kristof From owner-freebsd-current@freebsd.org Tue Apr 14 22:35: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 DD5492CB305; Tue, 14 Apr 2020 22:35:19 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4920gC5Vj1z3NMG; Tue, 14 Apr 2020 22:35:19 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1129) id 96ADF16895; Tue, 14 Apr 2020 22:35:19 +0000 (UTC) Date: Tue, 14 Apr 2020 22:35:19 +0000 From: Li-Wen Hsu To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD CI Weekly Report 2020-04-05 Message-ID: <20200414223519.GA33328@freefall.freebsd.org> Reply-To: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 22:35:19 -0000 (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2020-04-05 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2020-03-30 to 2020-04-05. During this period, we have: * 1715 builds (93.6% (+0.1) passed, 6.4% (-0.1) failed) of buildworld and buildkernel (GENERIC and LINT) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 274 test runs (49.7% (-4.6) passed, 19.3% (-24.4) unstable, 31.0% (+29.0) exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 26 doc and www builds (84.6 (-10.6) passed, 15.4% (+10.6) failed) Test case status (on 2020-04-05 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | ------------------- | --------- | --------- | ------- | -------- | | head/amd64 | 7740 (+4) | 7619 (-6) | 9 (+4) | 112 (+6) | | head/i386 | 7738 (+4) | 7613 (-4) | 11 (+6) | 114 (+2) | | 12-STABLE/amd64 | 7508 (+2) | 7452 (+2) | 0 (0) | 56 (0) | | 12-STABLE/i386 | 7506 (+2) | 7442 (-1) | 0 (0) | 64 (+3) | | 11-STABLE/amd64 | 6882 (+2) | 6835 (+5) | 0 (0) | 47 (-3) | | 11-STABLE/i386 | 6880 (+2) | 6831 (+5) | 0 (0) | 49 (-3) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20200405 and archive is available at https://hackmd.io/@FreeBSD-CI/ , any help is welcome. ## News * New armv6 job is added: * FreeBSD-head-armv6-testvm The images are available at https://artifact.ci.freebsd.org ## Failing jobs * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ * See console log for the error details. ## Failing tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ Some test cases not correctly skipped because test env loads the wrong kyua.conf after kyua imported to the base. * lib.libproc.proc_test.symbol_lookup * lib.msun.ctrig_test.test_inf_inputs * local.kyua.integration.cmd_about_test.topic__authors__installed * sys.kern.ptrace_test.ptrace__parent_wait_after_attach * sys.netipsec.tunnel.empty.v4 * sys.netipsec.tunnel.empty.v6 * sys.opencrypto.blake2_test.blake2b_vectors_x86 * sys.opencrypto.blake2_test.blake2s_vectors_x86 * usr.bin.calendar.legacy_test.main * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ All amd64 failures and: * sys.kern.ptrace_test.ptrace__parent_exits_before_child * sys.net.if_lagg_test.witness ## Regressions * 3 tests start failing after llvm10 import * lib.libproc.proc_test.symbol_lookup * lib.msun.ctrig_test.test_inf_inputs https://bugs.freebsd.org/244732 * (DTrace) common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d https://bugs.freebsd.org/244823 * fusefs tests fail when mac_bsdextended.ko is loaded https://bugs.freebsd.org/244229 * `dtrace -c` causes program dumps core after somewhere between (r357694, r357701] https://bugs.freebsd.org/244053 * Lock-order reversals triggered by tests under sys.net.if_lagg_test.* on i386 https://bugs.freebsd.org/244163 Discovered by newly endabled sys.net.* tests. ([r357857](https://svnweb.freebsd.org/changeset/base/357857)) * sys.net.if_lagg_test.lacp_linkstate_destroy_stress panics i386 kernel https://bugs.freebsd.org/244168 Discovered by newly endabled sys.net.* tests. ([r357857](https://svnweb.freebsd.org/changeset/base/357857)) * (test case) sys.geom.class.multipath.misc.fail_on_error (on 12-STABLE) https://bugs.freebsd.org/244158 ## Failing and Flaky tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * cddl.usr.sbin.dtrace.common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d * https://bugs.freebsd.org/244823 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~13 failing and ~109 skipped cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details * Work for cleaning these failing cass are in progress * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/ * Total 3670 tests (0), 2285 success (-5), 579 failures (+5), 806 skipped (0) ## Disabled Tests * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 * lib.libc.sys.stat_test.stat_socket https://bugs.freebsd.org/240621 * lib.libarchive.functional_test.test_write_filter_zstd https://bugs.freebsd.org/240683 * lib.libcasper.services.cap_dns.dns_test.main https://bugs.freebsd.org/241435 * local.kyua.* (31 cases) & local.lutok.* (3 cases) on 11-i386 https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/2278/testReport/ * sys.geom.class.multipath.failloop.failloop https://bugs.freebsd.org/242689 * sys.kern.ptrace_test.ptrace__procdesc_reparent_wait_child https://bugs.freebsd.org/243605 * skip sys.geom.class.multipath.failloop.failloop https://bugs.freebsd.org/244053 * sys.kern.ptrace_test.ptrace__parent_wait_after_attach https://bugs.freebsd.org/244055 * sys.kern.ptrace_test.ptrace__parent_exits_before_child https://bugs.freebsd.org/244056 * sys.geom.class.multipath.misc.fail_on_error (12-STABLE) https://bugs.freebsd.org/244158 * sys.net.if_lagg_test.witness (i386) https://bugs.freebsd.org/244163 * PipePdfork.WildcardWait in sys.capsicum.capsicum-test.main https://bugs.freebsd.org/244165 * sys.net.if_lagg_test.lacp_linkstate_destroy_stress (i386) https://bugs.freebsd.org/244168 * sys.netinet6.frag6.frag6_07.frag6_07 https://bugs.freebsd.org/244170 * sys.netinet.fibs_test.udp_dontroute6 https://bugs.freebsd.org/244172 * sys.netpfil.pf.nat.exhaust https://bugs.freebsd.org/244703 * sys.geom.class.gate.ggate_test.ggated https://bugs.freebsd.org/244737 ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded * https://bugs.freebsd.org/239292 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger * https://bugs.freebsd.org/239397 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger * https://bugs.freebsd.org/239399 Flakey test case: sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger * https://bugs.freebsd.org/239425 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger * https://bugs.freebsd.org/241662 Flakey test case: lib.libarchive.functional_test.test_fuzz_iso9660 ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-current@freebsd.org Tue Apr 14 22:37:10 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 D1D772CB631; Tue, 14 Apr 2020 22:37:10 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4920jL5CmXz3Nhv; Tue, 14 Apr 2020 22:37:10 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1129) id A440116A26; Tue, 14 Apr 2020 22:37:10 +0000 (UTC) Date: Tue, 14 Apr 2020 22:37:10 +0000 From: Li-Wen Hsu To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD CI Weekly Report 2020-04-12 Message-ID: <20200414223710.GB33328@freefall.freebsd.org> Reply-To: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 22:37:10 -0000 (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2020-04-12 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2020-04-06 to 2020-04-12. During this period, we have: * 1801 builds (94.0% (+0.4) passed, 6.0% (-0.4) failed) of buildworld and buildkernel (GENERIC and LINT) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 288 test runs (25.1% (-24.6) passed, 29.9% (+10.6) unstable, 45.1% (+14.1) exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 30 doc and www builds (83.3% (-1.3) passed, 16.7% (+1.3) failed) Test case status (on 2020-04-12 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | ------------------- | --------- | ---------- | -------- | -------- | | head/amd64 | 7744 (+4) | 7638 (+19) | 14 (+5) | 92 (-20) | | head/i386 | 7742 (+4) | 7628 (+15) | 16 (+5) | 98 (-16) | | 12-STABLE/amd64 | 7508 (0) | 7449 (-3) | 1 (+1) | 58 (+2) | | 12-STABLE/i386 | 7506 (0) | 7425 (-17) | 2 (+2) | 79 (+15) | | 11-STABLE/amd64 | 6882 (0) | 6829 (-6) | 1 (+1) | 52 (+5) | | 11-STABLE/i386 | 6880 (0) | 6749 (-82) | 80 (+80) | 51 (+2) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20200412 and archive is available at https://hackmd.io/@FreeBSD-CI/ , any help is welcome. ## News * The test env now loads the required module for firewall tests. * New armv7 job is added (to replace armv6 one): * FreeBSD-head-armv7-testvm The images are available at https://artifact.ci.freebsd.org FreeBSD-head-armv7-test is ready but needs test env update. ## Failing jobs * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ * See console log for the error details. ## Failing tests * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ * local.kyua.integration.cmd_about_test.topic__authors__installed * sys.netipsec.tunnel.empty.v4 * sys.netipsec.tunnel.empty.v6 * sys.netpfil.common.forward.ipf_v4 * sys.netpfil.common.forward.ipfw_v4 * sys.netpfil.common.forward.pf_v4 * sys.netpfil.common.tos.ipfw_tos * sys.netpfil.common.tos.pf_tos * sys.netpfil.pf.forward.v4 * sys.netpfil.pf.set_tos.v4 * sys.opencrypto.blake2_test.blake2b_vectors_x86 * sys.opencrypto.blake2_test.blake2s_vectors_x86 * sbin.nvmecontrol.basic.__test_cases_list__ Fixed in r359903 * usr.bin.calendar.legacy_test.main Fixed in r359862 * https://ci.freebsd.org/job/FreeBSD-head-i386-test/ All amd64 failures and: * sys.netinet.divert.ipdivert_ip_input_local_success * sys.netinet.divert.ipdivert_ip_output_remote_success * https://ci.freebsd.org/job/FreeBSD-stable-12-amd64-test/ * usr.bin.calendar.legacy_test.main Fixed in r359863 * sbin.nvmecontrol.basic.__test_cases_list__ Fixed in r359904 * https://ci.freebsd.org/job/FreeBSD-stable-12-i386-test/ * usr.bin.calendar.legacy_test.main Fixed in r359863 * https://ci.freebsd.org/job/FreeBSD-stable-11-amd64-test/ * usr.bin.calendar.legacy_test.main Fixed in r359864 * https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/ Many failure all due to kyua.conf issue. Already fixed on 2020-04-13. ## Regressions * 3 tests start failing after llvm10 import * lib.libproc.proc_test.symbol_lookup * lib.msun.ctrig_test.test_inf_inputs https://bugs.freebsd.org/244732 * (DTrace) common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d https://bugs.freebsd.org/244823 * fusefs tests fail when mac_bsdextended.ko is loaded https://bugs.freebsd.org/244229 * `dtrace -c` causes program dumps core after somewhere between (r357694, r357701] https://bugs.freebsd.org/244053 * Lock-order reversals triggered by tests under sys.net.if_lagg_test.* on i386 https://bugs.freebsd.org/244163 Discovered by newly endabled sys.net.* tests. ([r357857](https://svnweb.freebsd.org/changeset/base/357857)) * sys.net.if_lagg_test.lacp_linkstate_destroy_stress panics i386 kernel https://bugs.freebsd.org/244168 Discovered by newly endabled sys.net.* tests. ([r357857](https://svnweb.freebsd.org/changeset/base/357857)) * (test case) sys.geom.class.multipath.misc.fail_on_error (on 12-STABLE) https://bugs.freebsd.org/244158 ## Failing and Flaky tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * cddl.usr.sbin.dtrace.common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d * https://bugs.freebsd.org/244823 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~13 failing and ~109 skipped cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details * Work for cleaning these failing cass are in progress * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/ * Total 3670 tests (0), 2285 success (-5), 579 failures (+5), 806 skipped (0) ## Disabled Tests * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 * lib.libc.sys.stat_test.stat_socket https://bugs.freebsd.org/240621 * lib.libarchive.functional_test.test_write_filter_zstd https://bugs.freebsd.org/240683 * lib.libcasper.services.cap_dns.dns_test.main https://bugs.freebsd.org/241435 * local.kyua.* (31 cases) & local.lutok.* (3 cases) on 11-i386 https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/2278/testReport/ * sys.geom.class.multipath.failloop.failloop https://bugs.freebsd.org/242689 * sys.kern.ptrace_test.ptrace__procdesc_reparent_wait_child https://bugs.freebsd.org/243605 * skip sys.geom.class.multipath.failloop.failloop https://bugs.freebsd.org/244053 * sys.kern.ptrace_test.ptrace__parent_wait_after_attach https://bugs.freebsd.org/244055 * sys.kern.ptrace_test.ptrace__parent_exits_before_child https://bugs.freebsd.org/244056 * sys.geom.class.multipath.misc.fail_on_error (12-STABLE) https://bugs.freebsd.org/244158 * sys.net.if_lagg_test.witness (i386) https://bugs.freebsd.org/244163 * PipePdfork.WildcardWait in sys.capsicum.capsicum-test.main https://bugs.freebsd.org/244165 * sys.net.if_lagg_test.lacp_linkstate_destroy_stress (i386) https://bugs.freebsd.org/244168 * sys.netinet6.frag6.frag6_07.frag6_07 https://bugs.freebsd.org/244170 * sys.netinet.fibs_test.udp_dontroute6 https://bugs.freebsd.org/244172 * sys.netpfil.pf.nat.exhaust https://bugs.freebsd.org/244703 * sys.geom.class.gate.ggate_test.ggated https://bugs.freebsd.org/244737 ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded * https://bugs.freebsd.org/239292 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger * https://bugs.freebsd.org/239397 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger * https://bugs.freebsd.org/239399 Flakey test case: sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger * https://bugs.freebsd.org/239425 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger * https://bugs.freebsd.org/241662 Flakey test case: lib.libarchive.functional_test.test_fuzz_iso9660 ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-current@freebsd.org Tue Apr 14 23:18:00 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 E2FE62CC7B4 for ; Tue, 14 Apr 2020 23:18:00 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4921cS5hjLz3wvQ; Tue, 14 Apr 2020 23:18:00 +0000 (UTC) (envelope-from clay.daniels.jr@gmail.com) Received: by mail-lj1-x22d.google.com with SMTP id u15so1676884ljd.3; Tue, 14 Apr 2020 16:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MOTmSPMb/p/faLut4cB0mJs4Q5MzDTc3R6I7zkqY8ZU=; b=KXfq2lk0S2RK3vUN5NH8yeNl2wCQt/bBj9SxlZoRMM77rQSnCH1urUHt6LoKGwjCMP n+zIBh1nQIbSk5gIUNltE5efr2Qt5rB/NYbw6DcXQMSVDBaVb6Vte/XCKKz635WnIvqL zN9rNGnrhCOocCHMu2d6iyOoRJun9I42MeDjPRA5xnOZazZhrAeg43juyjSoQsHtjAdn 1AvVJFnG9cE+CR1RlvilZL9COx9u7qE2/2zG0eYCOnm0CD9RzGBnw/+VrRsk5Ayrfcxi /C6T+e/zDlu8Ogi/BUWy5qmnd4nA5rFIUiVyrhQWB0LoYyRIlrf2sw9irnK6sLRnRrhY 5AHw== 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=MOTmSPMb/p/faLut4cB0mJs4Q5MzDTc3R6I7zkqY8ZU=; b=L9YvLqfF8BXlbJODEihpQZJfMbBny1j32odV+b3osr3fS6WdtS1Y6B9s+g9MkzWv8b oYmFxFm3eUVzQJ9tHapmLSFJ13z4G9ycN5zQlD+wvw3qQ0JlpekCB9X0ZOYDfHc82c2X iISxKLyOTpwqi9T3hyNSWekx8j5n93helXVEMUFI3R09cMBt8XfOqWYbF+ojncR33XaK E80t9R4cFbjVTdq1XjyYCpltDSgH9SaHJ92kgMfCVLkseeIcZHJtxcJp6A15BxCzFhj1 5DvhWAOvNqHHUcCgq4k9sep5Tq1q5zz62qWJ3SbMpZATEm/itB6Mqi58ybofSSQHs9h2 oBdw== X-Gm-Message-State: AGi0PuY+t0xDLoyVeIK5E/tAIMXz6VGF1wMJyR9LPcaK8RXr2Kp/J1xw kSWsxn6e2Sx0lwMiHTWSpxy9dhs/0FWNl0Sc83B84sQ= X-Google-Smtp-Source: APiQypLi28DP5nihsj2JCzEQHI0QYcTzGbNKsuHyN44ltWWbKqw7+Gud2b8UyVlvQYVgufmztdxq2eL7BgSU1QK+qmA= X-Received: by 2002:a2e:b8c7:: with SMTP id s7mr1504889ljp.212.1586906278326; Tue, 14 Apr 2020 16:17:58 -0700 (PDT) MIME-Version: 1.0 References: <202004130158.03D1wiN4029672@gndrsh.dnsmgr.net> <20200413143836.GB5387@c720-r342378> In-Reply-To: From: Clay Daniels Date: Tue, 14 Apr 2020 18:17:47 -0500 Message-ID: Subject: Re: Working on Zoom port To: Jan Beich Cc: Alexandr Krivulya , =?UTF-8?B?0JbQuNC70LjQvSwg0JzQuNGF0LDQuNC7INCh0LXRgNCz0LXQtdCy0LjRhw==?= , "freebsd-current@freebsd.org" X-Rspamd-Queue-Id: 4921cS5hjLz3wvQ X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 23:18:00 -0000 On Tue, Apr 14, 2020 at 3:31 AM Jan Beich wrote:> According to [1] latest firefox nightly builds now support audio in> zoom. This nightly builds are not available for FreeBSD but you can try to build it from sources. > > [1] > > > https://www.reddit.com/r/firefox/comments/fsz3rk/implementation_of_the_audioworklets_makes_firefox/ > > If that Nightly means 76 then see bug 245422 for downstream version. > Unfortunately, it doesn't build yet due to a bug in Clang or Rust. _______________________________________________ > > I use Nightly on an older machine running NetBSD 9.0 and it uses Nightly 71.0 (64-bit). It's audio is fine, & I'm currently listening to the Uncle John's Band by the Grateful Dead ;-) Clay From owner-freebsd-current@freebsd.org Wed Apr 15 13:34: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 D46692B65FB; Wed, 15 Apr 2020 13:34:17 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492NcT4tFSz3M1b; Wed, 15 Apr 2020 13:34:17 +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 74F9514BAF; Wed, 15 Apr 2020 13:34:17 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id BF7DBEA1B; Wed, 15 Apr 2020 15:34:15 +0200 (CEST) From: "Kristof Provost" To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD CI Weekly Report 2020-04-12 Date: Wed, 15 Apr 2020 15:34:12 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: In-Reply-To: <20200414223710.GB33328@freefall.freebsd.org> References: <20200414223710.GB33328@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 13:34:17 -0000 On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: > (Please send the followup to freebsd-testing@ and note Reply-To is > set.) > > FreeBSD CI Weekly Report 2020-04-12 > =================================== > > Here is a summary of the FreeBSD Continuous Integration results for > the period > from 2020-04-06 to 2020-04-12. > > During this period, we have: > > * 1801 builds (94.0% (+0.4) passed, 6.0% (-0.4) failed) of buildworld > and > buildkernel (GENERIC and LINT) were executed on aarch64, amd64, > armv6, > armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, > sparc64 architectures for head, stable/12, stable/11 branches. > * 288 test runs (25.1% (-24.6) passed, 29.9% (+10.6) unstable, 45.1% > (+14.1) > exception) were executed on amd64, i386, riscv64 architectures for > head, > stable/12, stable/11 branches. > * 30 doc and www builds (83.3% (-1.3) passed, 16.7% (+1.3) failed) > > Test case status (on 2020-04-12 23:59): > | Branch/Architecture | Total | Pass | Fail | Skipped | > | ------------------- | --------- | ---------- | -------- | -------- | > | head/amd64 | 7744 (+4) | 7638 (+19) | 14 (+5) | 92 (-20) | > | head/i386 | 7742 (+4) | 7628 (+15) | 16 (+5) | 98 (-16) | > | 12-STABLE/amd64 | 7508 (0) | 7449 (-3) | 1 (+1) | 58 (+2) | > | 12-STABLE/i386 | 7506 (0) | 7425 (-17) | 2 (+2) | 79 (+15) | > | 11-STABLE/amd64 | 6882 (0) | 6829 (-6) | 1 (+1) | 52 (+5) | > | 11-STABLE/i386 | 6880 (0) | 6749 (-82) | 80 (+80) | 51 (+2) | > > (The statistics from experimental jobs are omitted) > > If any of the issues found by CI are in your area of interest or > expertise > please investigate the PRs listed below. > > The latest web version of this report is available at > https://hackmd.io/@FreeBSD-CI/report-20200412 and archive is available > at > https://hackmd.io/@FreeBSD-CI/ , any help is welcome. > > ## News > > * The test env now loads the required module for firewall tests. > > * New armv7 job is added (to replace armv6 one): > * FreeBSD-head-armv7-testvm > The images are available at https://artifact.ci.freebsd.org > FreeBSD-head-armv7-test is ready but needs test env update. > > ## Failing jobs > > * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ > * See console log for the error details. > > ## Failing tests > > * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ > * local.kyua.integration.cmd_about_test.topic__authors__installed > * sys.netipsec.tunnel.empty.v4 > * sys.netipsec.tunnel.empty.v6 > * sys.netpfil.common.forward.ipf_v4 > * sys.netpfil.common.forward.ipfw_v4 > * sys.netpfil.common.forward.pf_v4 > * sys.netpfil.common.tos.ipfw_tos > * sys.netpfil.common.tos.pf_tos > * sys.netpfil.pf.forward.v4 I can’t actually reproduce this failure in my test VM, but with the ci test VM I can reproduce the problem. It’s not related to pf, because the sanity check ping we do before we set up pf already fails. Or rather pft_ping.py sends an incorrect packet, because `ping` does get the packet to go where it’s supposed to go. Scapy seems to fail to find the source IP address, so we get this: 12:12:22.152652 IP 0.0.0.0 > 198.51.100.3: ICMP echo request, id 0, seq 0, length 12 I have a vague recollection that we’ve seem this problem before, but I can’t remember what we did about it. In all likelihood most of the other netpfil tests fail for exactly the same reason. Best regards, Kristof From owner-freebsd-current@freebsd.org Wed Apr 15 14:09: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 BFF8B2B7FD3; Wed, 15 Apr 2020 14:09:57 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492PPd53FVz3PW8; Wed, 15 Apr 2020 14:09:57 +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 7A9EE14F66; Wed, 15 Apr 2020 14:09:57 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 20857EAAA; Wed, 15 Apr 2020 16:09:56 +0200 (CEST) From: "Kristof Provost" To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, bofh@freebsd.org, "Alexander V. Chernikov" Subject: Re: FreeBSD CI Weekly Report 2020-04-12 Date: Wed, 15 Apr 2020 16:09:55 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: In-Reply-To: References: <20200414223710.GB33328@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 14:09:57 -0000 On 15 Apr 2020, at 15:34, Kristof Provost wrote: > On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: >> (Please send the followup to freebsd-testing@ and note Reply-To is >> set.) >> >> FreeBSD CI Weekly Report 2020-04-12 >> =================================== >> >> Here is a summary of the FreeBSD Continuous Integration results for >> the period >> from 2020-04-06 to 2020-04-12. >> >> During this period, we have: >> >> * 1801 builds (94.0% (+0.4) passed, 6.0% (-0.4) failed) of buildworld >> and >> buildkernel (GENERIC and LINT) were executed on aarch64, amd64, >> armv6, >> armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, >> sparc64 architectures for head, stable/12, stable/11 branches. >> * 288 test runs (25.1% (-24.6) passed, 29.9% (+10.6) unstable, 45.1% >> (+14.1) >> exception) were executed on amd64, i386, riscv64 architectures for >> head, >> stable/12, stable/11 branches. >> * 30 doc and www builds (83.3% (-1.3) passed, 16.7% (+1.3) failed) >> >> Test case status (on 2020-04-12 23:59): >> | Branch/Architecture | Total | Pass | Fail | Skipped >> | >> | ------------------- | --------- | ---------- | -------- | -------- >> | >> | head/amd64 | 7744 (+4) | 7638 (+19) | 14 (+5) | 92 (-20) >> | >> | head/i386 | 7742 (+4) | 7628 (+15) | 16 (+5) | 98 (-16) >> | >> | 12-STABLE/amd64 | 7508 (0) | 7449 (-3) | 1 (+1) | 58 (+2) >> | >> | 12-STABLE/i386 | 7506 (0) | 7425 (-17) | 2 (+2) | 79 (+15) >> | >> | 11-STABLE/amd64 | 6882 (0) | 6829 (-6) | 1 (+1) | 52 (+5) >> | >> | 11-STABLE/i386 | 6880 (0) | 6749 (-82) | 80 (+80) | 51 (+2) >> | >> >> (The statistics from experimental jobs are omitted) >> >> If any of the issues found by CI are in your area of interest or >> expertise >> please investigate the PRs listed below. >> >> The latest web version of this report is available at >> https://hackmd.io/@FreeBSD-CI/report-20200412 and archive is >> available at >> https://hackmd.io/@FreeBSD-CI/ , any help is welcome. >> >> ## News >> >> * The test env now loads the required module for firewall tests. >> >> * New armv7 job is added (to replace armv6 one): >> * FreeBSD-head-armv7-testvm >> The images are available at https://artifact.ci.freebsd.org >> FreeBSD-head-armv7-test is ready but needs test env update. >> >> ## Failing jobs >> >> * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ >> * See console log for the error details. >> >> ## Failing tests >> >> * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ >> * local.kyua.integration.cmd_about_test.topic__authors__installed >> * sys.netipsec.tunnel.empty.v4 >> * sys.netipsec.tunnel.empty.v6 >> * sys.netpfil.common.forward.ipf_v4 >> * sys.netpfil.common.forward.ipfw_v4 >> * sys.netpfil.common.forward.pf_v4 >> * sys.netpfil.common.tos.ipfw_tos >> * sys.netpfil.common.tos.pf_tos >> * sys.netpfil.pf.forward.v4 > I can’t actually reproduce this failure in my test VM, but with the > ci test VM I can reproduce the problem. > It’s not related to pf, because the sanity check ping we do before > we set up pf already fails. > Or rather pft_ping.py sends an incorrect packet, because `ping` does > get the packet to go where it’s supposed to go. > > Scapy seems to fail to find the source IP address, so we get this: > > 12:12:22.152652 IP 0.0.0.0 > 198.51.100.3: ICMP echo request, id 0, > seq 0, length 12 > > I have a vague recollection that we’ve seem this problem before, but > I can’t remember what we did about it. > > In all likelihood most of the other netpfil tests fail for exactly the > same reason. The problem appears to be that /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing the `netstat -rnW` output. For reference, this is the output in the test VM: Routing tables Internet: Destination Gateway Flags Nhop# Mtu Netif Expire 127.0.0.1 link#2 UH 1 16384 lo0 192.0.2.0/24 link#4 U 2 1500 epair0a 192.0.2.1 link#4 UHS 1 16384 lo0 198.51.100.0/24 192.0.2.2 UGS 3 1500 epair0a Internet6: Destination Gateway Flags Nhop# Mtu Netif Expire ::/96 ::1 UGRS 4 16384 lo0 ::1 link#2 UH 1 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRS 4 16384 lo0 fe80::/10 ::1 UGRS 4 16384 lo0 fe80::%lo0/64 link#2 U 3 16384 lo0 fe80::1%lo0 link#2 UHS 2 16384 lo0 fe80::%epair0a/64 link#4 U 5 1500 epair0a fe80::3d:9dff:fe7c:d70a%epair0a link#4 UHS 1 16384 lo0 fe80::%epair1a/64 link#6 U 6 1500 epair1a fe80::37:9eff:fe03:250a%epair1a link#6 UHS 1 16384 lo0 ff02::/16 ::1 UGRS 4 16384 lo0 The parsing code seems to think that the netif for the 198.51.100.0/24 route is 1500 rather than epair0a. This may be related to the difference in netstat output, because on my VM it looks like this: Routing tables Internet: Destination Gateway Flags Use Mtu Netif Expire default 172.16.2.1 UGS 319 1500 vtnet0 127.0.0.1 link#2 UH 0 16384 lo0 172.16.2.0/24 link#1 U 14 1500 vtnet0 172.16.2.2 link#1 UHS 0 16384 lo0 Internet6: Destination Gateway Flags Use Mtu Netif Expire ::/96 ::1 UGRS 0 16384 lo0 ::1 link#2 UH 0 16384 lo0 ::ffff:0.0.0.0/96 ::1 UGRS 0 16384 lo0 fe80::/10 ::1 UGRS 0 16384 lo0 fe80::%vtnet0/64 link#1 U 0 1500 vtnet0 fe80::5a9c:fcff:fe02:a95e%vtnet0 link#1 UHS 0 16384 lo0 fe80::%lo0/64 link#2 U 0 16384 lo0 fe80::1%lo0 link#2 UHS 0 16384 lo0 ff02::/16 ::1 UGRS 0 16384 lo0 I suspect that this change was introduced in r359823 (Introduce nexthop objects and new routing KPI). Best regards, Kristof From owner-freebsd-current@freebsd.org Wed Apr 15 14:49: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 4048E2B8F3B; Wed, 15 Apr 2020 14:49:44 +0000 (UTC) (envelope-from olivier@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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492QHX0xqyz3wt2; Wed, 15 Apr 2020 14:49:44 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) (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: olivier/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id E6B86170E7; Wed, 15 Apr 2020 14:49:43 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: by mail-pg1-f179.google.com with SMTP id r4so17093pgg.4; Wed, 15 Apr 2020 07:49:43 -0700 (PDT) X-Gm-Message-State: AGi0PuYCsN/5awg9udJTfwL7GvOf1DjTBmnISu7CpUvEVvY6WRFj07ag imRgxkdYAlQg+6ygtL28GIdD2tOMvK/So9jB1CM= X-Google-Smtp-Source: APiQypKecHW77MF5DIXi8FXRktWsuQds0xTOB4APspMaWMrkHF4euHjE8RZvfkDfLkoNh/Z3pJhQk8izB38QA7UpQLQ= X-Received: by 2002:a62:4e0c:: with SMTP id c12mr27056707pfb.87.1586962182720; Wed, 15 Apr 2020 07:49:42 -0700 (PDT) MIME-Version: 1.0 References: <20200414223710.GB33328@freefall.freebsd.org> In-Reply-To: From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Wed, 15 Apr 2020 16:49:31 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD CI Weekly Report 2020-04-12 To: Kristof Provost Cc: freebsd-testing@freebsd.org, freebsd-current , "freebsd-stable@freebsd.org Stable" , bofh@freebsd.org, "Alexander V. Chernikov" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 14:49:44 -0000 On Wed, Apr 15, 2020 at 4:10 PM Kristof Provost wrote: > > The problem appears to be that > /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing > the `netstat -rnW` output. > Shouldn't scapy use the libxo output of netstat to mitigate this regression ? From owner-freebsd-current@freebsd.org Wed Apr 15 15:28:18 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 D5E5D2BA023; Wed, 15 Apr 2020 15:28:18 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492R825Nhvz40DN; Wed, 15 Apr 2020 15:28:18 +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 9A0EA175E8; Wed, 15 Apr 2020 15:28:18 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 35C53ED27; Wed, 15 Apr 2020 17:28:17 +0200 (CEST) From: "Kristof Provost" To: "Olivier =?utf-8?q?Cochard-Labb=C3=A9?=" Cc: freebsd-testing@freebsd.org, freebsd-current , Stable , bofh@freebsd.org, "Alexander V. Chernikov" Subject: Re: FreeBSD CI Weekly Report 2020-04-12 Date: Wed, 15 Apr 2020 17:28:13 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: In-Reply-To: References: <20200414223710.GB33328@freefall.freebsd.org> MIME-Version: 1.0 Embedded-HTML: [{"HTML":[362, 854], "plain":[58, 303], "uuid":"C83DB664-8363-477B-9B11-992FD4A5E8E1"}] Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 15:28:18 -0000 On 15 Apr 2020, at 16:49, Olivier Cochard-Labbé wrote: > On Wed, Apr 15, 2020 at 4:10 PM Kristof Provost > wrote: > >> >> The problem appears to be that >> /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is >> misparsing >> the `netstat -rnW` output. >> > > Shouldn't scapy use the libxo output of netstat to mitigate this > regression > ? That would likely help, yes. I’m going to leave that decision up to the maintainer, because I’m not going to do the work :) I’m also not sure how “stable” we want the netstat output to be. Best regards, Kristof From owner-freebsd-current@freebsd.org Wed Apr 15 16:33:23 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 5AD452BB831; Wed, 15 Apr 2020 16:33:23 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 492Sb60plyz447w; Wed, 15 Apr 2020 16:33:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id 03FGXElW047294 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 15 Apr 2020 09:33:14 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id 03FGXEJ0047293; Wed, 15 Apr 2020 09:33:14 -0700 (PDT) (envelope-from sgk) Date: Wed, 15 Apr 2020 09:33:14 -0700 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: panic: sleeping thread. Possibly related to drm and swapping. Message-ID: <20200415163314.GA47279@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 492Sb60plyz447w X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.21 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; IP_SCORE(-0.22)[ip: (0.02), ipnet: 128.95.0.0/16(-0.26), asn: 73(-0.82), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 16:33:23 -0000 Just recieved this panic. I am using drm-legacy-kmod-g20200306 on a Dell Latitude D530 laptop. The panic occurred as I was starting libreoffice. Suggestions? mobile dumped core - see /var/crash/vmcore.2 Wed Apr 15 09:22:07 PDT 2020 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r359179M: Sat Mar 21 13:46:12 PDT 2020 root@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE i386 panic: sleeping thread Reading symbols from /boot/kernel/kernel... Reading symbols from /usr/lib/debug//boot/kernel/kernel.debug... Unread portion of the kernel message buffer: Sleeping thread (tid 100154, pid 1072) owns a non-sleepable lock KDB: stack backtrace of thread 100154: sched_switch(22209e00,104) at sched_switch+0x173/frame 0x220e04c8 mi_switch(104) at mi_switch+0x13e/frame 0x220e0500 sleepq_switch(2239ecac,ffffe8e0,2239ecac,2239ec2c,220e0574,...) at sleepq_switch+0xe3/frame 0x220e0518 sleepq_timedwait(2239ecac,50) at sleepq_timedwait+0x2a/frame 0x220e0540 _sleep(2239ecac,2239ec2c,50,fcc13e,ffffe8e0,13,0,0,100) at _sleep+0x176/frame 0x220e0574 swap_pager_getpages_locked(1,0,0) at swap_pager_getpages_locked+0x6b5/frame 0x220e05dc swap_pager_getpages(2239ec2c,220e0640,1,0,0) at swap_pager_getpages+0x40/frame 0x220e05fc vm_pager_get_pages(2239ec2c,220e0640,1,0,0,...) at vm_pager_get_pages+0x26/frame 0x220e0624 i915_gem_wire_page(0,220e0677,2239ec2c,0,2239ec3c,...) at i915_gem_wire_page+0x6b/frame 0x220e0650 i915_gem_object_get_pages_gtt(8af4700,2189a000,102,22569800,1000,...) at i915_gem_object_get_pages_gtt+0xb0/frame 0x220e0684 i915_gem_object_pin(8af4700,0,0,0,22779000,...) at i915_gem_object_pin+0x3ca/frame 0x220e06c0 i915_gem_execbuffer_reserve_object(5f,4f2a700,8af2b5c,18e59a5c,22779110,...) at i915_gem_execbuffer_reserve_object+0x64/frame 0x220e06e8 i915_gem_execbuffer_reserve(22209e00,22779110,20,24da9600,0,...) at i915_gem_execbuffer_reserve+0x1e8/frame 0x220e0720 i915_gem_do_execbuffer(220e0b70,28f2a000,11,fffffff3,22569800,...) at i915_gem_do_execbuffer+0x845/frame 0x220e09a8 i915_gem_execbuffer2(22569800,220e0b70,22505200,69,21ca3410,...) at i915_gem_execbuffer2+0xf6/frame 0x220e09c8 drm_ioctl(1847fa00,c0406469,220e0b70,7,22209e00) at drm_ioctl+0x31b/frame 0x220e09f4 devfs_ioctl(220e0a60) at devfs_ioctl+0x99/frame 0x220e0a2c VOP_IOCTL_APV(10c0614,220e0a60) at VOP_IOCTL_APV+0x18/frame 0x220e0a40 vn_ioctl(218a3070,c0406469,220e0b70,22291d00,22209e00) at vn_ioctl+0x13a/frame 0x220e0af0 devfs_ioctl_f(218a3070,c0406469,220e0b70,22291d00,22209e00) at devfs_ioctl_f+0x2c/frame 0x220e0b18 kern_ioctl(22209e00,a,c0406469,220e0b70) at kern_ioctl+0x1ea/frame 0x220e0b50 sys_ioctl(22209e00,2220a090,220e0cdc,22209e00,3206,...) at sys_ioctl+0xd4/frame 0x220e0c08 syscall(220e0ce8,3b,3b,3b,ffbfeb90,...) at syscall+0x1fd/frame 0x220e0cdc Xint0x80_syscall() at 0xffc033f9/frame 0x220e0cdc --- syscall (54, FreeBSD ELF32, sys_ioctl), eip = 0xffc05f6c, esp = 0xffc07fe8, ebp = 0xffbfeb54 --- panic: sleeping thread cpuid = 0 time = 1586967582 KDB: stack backtrace: db_trace_self_wrapper(aee2f1,1,21935470,1828d8e4,a0f170,...) at db_trace_self_wrapper+0x2a/frame 0x1828d8b8 kdb_backtrace(2,80,22209e00,8a5fa00,c,...) at kdb_backtrace+0x2e/frame 0x1828d918 vpanic(1002aba,1828d954,1828d954,1828d968,c7a399,...) at vpanic+0x11f/frame 0x1828d934 panic(1002aba,c,8a5fa00,17ffe000,8a5fa00,...) at panic+0x14/frame 0x1828d948 propagate_priority(0,246,0,0,22209e00,...) at propagate_priority+0x239/frame 0x1828d968 turnstile_wait(8a5fa00,22209e00,0) at turnstile_wait+0x285/frame 0x1828d984 __rw_wlock_hard(2239ec3c,22209e00) at __rw_wlock_hard+0x40d/frame 0x1828da00 swp_pager_async_iodone(18ef1000,0,157000,ffffffff,18eec000,...) at swp_pager_async_iodone+0x294/frame 0x1828da24 bufdone(18ef1000) at bufdone+0x60/frame 0x1828da64 swapgeom_done(18eec000) at swapgeom_done+0x44/frame 0x1828da7c g_io_deliver(18eec000,0) at g_io_deliver+0x1e7/frame 0x1828dab8 g_std_done(2eae4b58) at g_std_done+0x78/frame 0x1828dacc g_io_deliver(2eae4b58,0) at g_io_deliver+0x1e7/frame 0x1828db08 g_std_done(246ee108) at g_std_done+0x78/frame 0x1828db1c g_io_deliver(246ee108,0) at g_io_deliver+0x1e7/frame 0x1828db58 g_disk_done(2ce1fd68,28,18f5e000,0,0,...) at g_disk_done+0x10a/frame 0x1828db8c adadone(8bfd880,2cddc800) at adadone+0x86e/frame 0x1828dbcc xpt_done_process(25a51,8ad8e68e,e7c6bed,18058000,0,...) at xpt_done_process+0x3fd/frame 0x1828dbf8 xpt_done_direct(2cddc800) at xpt_done_direct+0x39/frame 0x1828dc1c ahci_ch_intr_direct(18058000) at ahci_ch_intr_direct+0xe6/frame 0x1828dc48 ahci_intr_one(17fab454) at ahci_intr_one+0x23/frame 0x1828dc5c ithread_loop(8e23ea0,1828dce8) at ithread_loop+0x1a0/frame 0x1828dcb8 fork_exit(be4b10,8e23ea0,1828dce8,0,0,...) at fork_exit+0x66/frame 0x1828dcd4 fork_trampoline() at 0xffc0340e/frame 0x1828dcd4 --- kthread start KDB: enter: panic 0x00c1e379 in doadump (textdump=0) at /usr/src/sys/kern/kern_shutdown.c:393 393 savectx(&dumppcb); (kgdb) #0 0x00c1e379 in doadump (textdump=0) at /usr/src/sys/kern/kern_shutdown.c:393 #1 0x009c0a89 in db_fncall_generic (addr=, nargs=0, args=, rv=) at /usr/src/sys/ddb/db_command.c:610 #2 db_fncall (dummy1=405329652, dummy2=false, dummy3=145217792, dummy4=0x1828d6f0 "pT\223!\f\327(\030", ) at /usr/src/sys/ddb/db_command.c:658 #3 0x009c05c8 in db_command (last_cmdp=, cmd_table=, dopager=1) at /usr/src/sys/ddb/db_command.c:482 #4 0x009c032c in db_command_loop () at /usr/src/sys/ddb/db_command.c:535 #5 0x009c3426 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:253 #6 0x00c64c39 in kdb_trap (type=3, code=0, tf=0x1828d8cc) at /usr/src/sys/kern/subr_kdb.c:699 #7 0x00f9324a in trap (frame=0x1828d8cc) at /usr/src/sys/i386/i386/trap.c:668 #8 0xffc0319f in ?? () #9 0x1828d8cc in ?? () #10 0x00000028 in ?? () #11 0x00000028 in ?? () #12 0x00000100 in ?? () #13 0x0101ae42 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (kgdb) -- Steve From owner-freebsd-current@freebsd.org Wed Apr 15 20:21: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 4467A2C1022; Wed, 15 Apr 2020 20:21:32 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward103o.mail.yandex.net (forward103o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::606]) (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 492YfK5H1Wz4Lyl; Wed, 15 Apr 2020 20:21:29 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward501o.mail.yandex.net (forward501o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::611]) by forward103o.mail.yandex.net (Yandex) with ESMTP id 4208D5F8320A; Wed, 15 Apr 2020 23:21:11 +0300 (MSK) Received: from mxback24o.mail.yandex.net (mxback24o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::75]) by forward501o.mail.yandex.net (Yandex) with ESMTP id 3EACF1E80002; Wed, 15 Apr 2020 23:21:11 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback24o.mail.yandex.net (mxback/Yandex) with ESMTP id DIwk9NYhfE-LA2S1Nra; Wed, 15 Apr 2020 23:21:10 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1586982070; bh=pcnmyfi5q3HAMA53d7VJPHEH6EjFCQiuew2bY/lFFC8=; h=Message-Id:Cc:Subject:In-Reply-To:Date:References:To:From; b=cKmyl/jtOeyU7W0titJHlwzJpZoXtxvNdNC+PcrsWiw84mXhxbY4PhcnXFas3sUM0 hdfN1pj4ZFMHWU/2I4LZ9B/pWwFiwMbeRj0CIeN9vYSOumPm5e8S5X86FnqzQ2aWYc GA0fNVnuk6de2MIPE3itCUSd7V3zGnPVvUDvANEc= Received: by myt2-c3952fd46804.qloud-c.yandex.net with HTTP; Wed, 15 Apr 2020 23:21:10 +0300 From: Alexander V. Chernikov To: Kristof Provost , "freebsd-testing@freebsd.org" Cc: "freebsd-current@freebsd.org" , "freebsd-stable@freebsd.org" , "bofh@freebsd.org" , =?utf-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= In-Reply-To: References: <20200414223710.GB33328@freefall.freebsd.org> Subject: Re: FreeBSD CI Weekly Report 2020-04-12 MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 15 Apr 2020 21:21:10 +0100 Message-Id: <885331586982061@myt5-bc0f9d8e5f27.qloud-c.yandex.net> Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-Rspamd-Queue-Id: 492YfK5H1Wz4Lyl X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ipfw.ru header.s=mail header.b=cKmyl/jt; dmarc=none; spf=pass (mx1.freebsd.org: domain of melifaro@ipfw.ru designates 2a02:6b8:0:1a2d::606 as permitted sender) smtp.mailfrom=melifaro@ipfw.ru X-Spamd-Result: default: False [-6.16 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[ipfw.ru:s=mail]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ipfw.ru]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_FIVE(0.00)[6]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DKIM_TRACE(0.00)[ipfw.ru:+]; RCVD_IN_DNSWL_NONE(0.00)[6.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.d.2.a.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; IP_SCORE(-3.66)[ip: (-9.72), ipnet: 2a02:6b8::/32(-4.76), asn: 13238(-3.85), country: RU(0.01)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 20:21:32 -0000 15.04.2020, 15:10, "Kristof Provost" : > On 15 Apr 2020, at 15:34, Kristof Provost wrote: >>  On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: >>>  (Please send the followup to freebsd-testing@ and note Reply-To is >>>  set.) >>> >>>  FreeBSD CI Weekly Report 2020-04-12 >>>  =================================== >>> >>>  Here is a summary of the FreeBSD Continuous Integration results for >>>  the period >>>  from 2020-04-06 to 2020-04-12. >>> >>>  During this period, we have: >>> >>>  * 1801 builds (94.0% (+0.4) passed, 6.0% (-0.4) failed) of buildworld >>>  and >>>    buildkernel (GENERIC and LINT) were executed on aarch64, amd64, >>>  armv6, >>>    armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, >>>    sparc64 architectures for head, stable/12, stable/11 branches. >>>  * 288 test runs (25.1% (-24.6) passed, 29.9% (+10.6) unstable, 45.1% >>>  (+14.1) >>>    exception) were executed on amd64, i386, riscv64 architectures for >>>  head, >>>    stable/12, stable/11 branches. >>>  * 30 doc and www builds (83.3% (-1.3) passed, 16.7% (+1.3) failed) >>> >>>  Test case status (on 2020-04-12 23:59): >>>  | Branch/Architecture | Total | Pass | Fail | Skipped >>>  | >>>  | ------------------- | --------- | ---------- | -------- | -------- >>>  | >>>  | head/amd64 | 7744 (+4) | 7638 (+19) | 14 (+5) | 92 (-20) >>>  | >>>  | head/i386 | 7742 (+4) | 7628 (+15) | 16 (+5) | 98 (-16) >>>  | >>>  | 12-STABLE/amd64 | 7508 (0) | 7449 (-3) | 1 (+1) | 58 (+2) >>>  | >>>  | 12-STABLE/i386 | 7506 (0) | 7425 (-17) | 2 (+2) | 79 (+15) >>>  | >>>  | 11-STABLE/amd64 | 6882 (0) | 6829 (-6) | 1 (+1) | 52 (+5) >>>  | >>>  | 11-STABLE/i386 | 6880 (0) | 6749 (-82) | 80 (+80) | 51 (+2) >>>  | >>> >>>  (The statistics from experimental jobs are omitted) >>> >>>  If any of the issues found by CI are in your area of interest or >>>  expertise >>>  please investigate the PRs listed below. >>> >>>  The latest web version of this report is available at >>>  https://hackmd.io/@FreeBSD-CI/report-20200412 and archive is >>>  available at >>>  https://hackmd.io/@FreeBSD-CI/ , any help is welcome. >>> >>>  ## News >>> >>>  * The test env now loads the required module for firewall tests. >>> >>>  * New armv7 job is added (to replace armv6 one): >>>    * FreeBSD-head-armv7-testvm >>>    The images are available at https://artifact.ci.freebsd.org >>>    FreeBSD-head-armv7-test is ready but needs test env update. >>> >>>  ## Failing jobs >>> >>>  * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ >>>    * See console log for the error details. >>> >>>  ## Failing tests >>> >>>  * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ >>>    * local.kyua.integration.cmd_about_test.topic__authors__installed >>>    * sys.netipsec.tunnel.empty.v4 >>>    * sys.netipsec.tunnel.empty.v6 >>>    * sys.netpfil.common.forward.ipf_v4 >>>    * sys.netpfil.common.forward.ipfw_v4 >>>    * sys.netpfil.common.forward.pf_v4 >>>    * sys.netpfil.common.tos.ipfw_tos >>>    * sys.netpfil.common.tos.pf_tos >>>    * sys.netpfil.pf.forward.v4 >>  I can’t actually reproduce this failure in my test VM, but with the >>  ci test VM I can reproduce the problem. >>  It’s not related to pf, because the sanity check ping we do before >>  we set up pf already fails. >>  Or rather pft_ping.py sends an incorrect packet, because `ping` does >>  get the packet to go where it’s supposed to go. >> >>  Scapy seems to fail to find the source IP address, so we get this: >> >>          12:12:22.152652 IP 0.0.0.0 > 198.51.100.3: ICMP echo request, id 0, >>  seq 0, length 12 >> >>  I have a vague recollection that we’ve seem this problem before, but >>  I can’t remember what we did about it. >> >>  In all likelihood most of the other netpfil tests fail for exactly the >>  same reason. > > The problem appears to be that > /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing > the `netstat -rnW` output. Thanks for the analysis! Sorry for breaking the tests. I should have run tests with userland changes installed. I'll revert the netstat output changes shortly to unbreak the tests. Re longer-term: parsing textual output for the routes does not seem to be a good habit, especially in these days. Structural (libxo) approach looks better, however I guess this will make scapy unusable on the routers with full-view. So far light-weight sysctl-route reader looks like the best option. What do you folks think? > > For reference, this is the output in the test VM: > >         Routing tables > >         Internet: >         Destination Gateway Flags Nhop# Mtu Netif > Expire >         127.0.0.1 link#2 UH 1 16384 lo0 >         192.0.2.0/24 link#4 U 2 1500 epair0a >         192.0.2.1 link#4 UHS 1 16384 lo0 >         198.51.100.0/24 192.0.2.2 UGS 3 1500 epair0a > >         Internet6: >         Destination Gateway Flags > Nhop# Mtu Netif Expire >         ::/96 ::1 UGRS >      4 16384 lo0 >         ::1 link#2 UH >      1 16384 lo0 >         ::ffff:0.0.0.0/96 ::1 UGRS >      4 16384 lo0 >         fe80::/10 ::1 UGRS >      4 16384 lo0 >         fe80::%lo0/64 link#2 U >      3 16384 lo0 >         fe80::1%lo0 link#2 UHS >      2 16384 lo0 >         fe80::%epair0a/64 link#4 U >      5 1500 epair0a >         fe80::3d:9dff:fe7c:d70a%epair0a link#4 UHS >      1 16384 lo0 >         fe80::%epair1a/64 link#6 U >      6 1500 epair1a >         fe80::37:9eff:fe03:250a%epair1a link#6 UHS >      1 16384 lo0 >         ff02::/16 ::1 UGRS >      4 16384 lo0 > > The parsing code seems to think that the netif for the 198.51.100.0/24 > route is 1500 rather than epair0a. > This may be related to the difference in netstat output, because on my > VM it looks like this: > >         Routing tables > >         Internet: >         Destination Gateway Flags Use Mtu Netif > Expire >         default 172.16.2.1 UGS 319 1500 vtnet0 >         127.0.0.1 link#2 UH 0 16384 lo0 >         172.16.2.0/24 link#1 U 14 1500 vtnet0 >         172.16.2.2 link#1 UHS 0 16384 lo0 > >         Internet6: >         Destination Gateway Flags >      Use Mtu Netif Expire >         ::/96 ::1 UGRS >        0 16384 lo0 >         ::1 link#2 UH >        0 16384 lo0 >         ::ffff:0.0.0.0/96 ::1 UGRS >        0 16384 lo0 >         fe80::/10 ::1 UGRS >        0 16384 lo0 >         fe80::%vtnet0/64 link#1 U >        0 1500 vtnet0 >         fe80::5a9c:fcff:fe02:a95e%vtnet0 link#1 UHS >        0 16384 lo0 >         fe80::%lo0/64 link#2 U >        0 16384 lo0 >         fe80::1%lo0 link#2 UHS >        0 16384 lo0 >         ff02::/16 ::1 UGRS >        0 16384 lo0 > > I suspect that this change was introduced in r359823 (Introduce nexthop > objects and new routing KPI). > > Best regards, > Kristof > _______________________________________________ > 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 Apr 15 20:27: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 02D362C15DF; Wed, 15 Apr 2020 20:27:45 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492YnX6F3Cz4N2q; Wed, 15 Apr 2020 20:27:44 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from mx.bofh.network (mx.bofh.network [IPv6:2001:19f0:5001:2b77:5400:2ff:fe7b:aa2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.bofh.network", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: bofh/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 3461619AC0; Wed, 15 Apr 2020 20:27:44 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from [IPv6:2402:54c0:ffff:ffff:9188:3af7:1bd8:3b5d] ( [2402:54c0:ffff:ffff:9188:3af7:1bd8:3b5d]) by mx.bofh.network (OpenSMTPD) with ESMTPSA id 74b240b3 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Wed, 15 Apr 2020 20:27:41 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Subject: Re: FreeBSD CI Weekly Report 2020-04-12 From: Muhammad Moinur Rahman In-Reply-To: <885331586982061@myt5-bc0f9d8e5f27.qloud-c.yandex.net> Date: Thu, 16 Apr 2020 02:27:36 +0600 Cc: Kristof Provost , "freebsd-testing@freebsd.org" , "freebsd-current@freebsd.org" , "freebsd-stable@freebsd.org" , =?utf-8?Q?Olivier_Cochard-Labb=C3=A9?= Content-Transfer-Encoding: quoted-printable Message-Id: References: <20200414223710.GB33328@freefall.freebsd.org> <885331586982061@myt5-bc0f9d8e5f27.qloud-c.yandex.net> To: "Alexander V. Chernikov" X-Mailer: Apple Mail (2.3608.60.0.2.5) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 20:27:45 -0000 Hi Alexandar, I have changed net/scapy to apply a simple patch as a workaround for the = time being. ports@r531789 should do the trick for now. So no need to = revert. Kind Regards, Moin > On 16 Apr, 2020, at 02:21, Alexander V. Chernikov = wrote: >=20 >=20 >=20 > 15.04.2020, 15:10, "Kristof Provost" : >> On 15 Apr 2020, at 15:34, Kristof Provost wrote: >>> On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: >>>> (Please send the followup to freebsd-testing@ and note Reply-To is >>>> set.) >>>>=20 >>>> FreeBSD CI Weekly Report 2020-04-12 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>=20 >>>> Here is a summary of the FreeBSD Continuous Integration results = for >>>> the period >>>> from 2020-04-06 to 2020-04-12. >>>>=20 >>>> During this period, we have: >>>>=20 >>>> * 1801 builds (94.0% (+0.4) passed, 6.0% (-0.4) failed) of = buildworld >>>> and >>>> buildkernel (GENERIC and LINT) were executed on aarch64, amd64, >>>> armv6, >>>> armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, = riscv64, >>>> sparc64 architectures for head, stable/12, stable/11 branches. >>>> * 288 test runs (25.1% (-24.6) passed, 29.9% (+10.6) unstable, = 45.1% >>>> (+14.1) >>>> exception) were executed on amd64, i386, riscv64 architectures = for >>>> head, >>>> stable/12, stable/11 branches. >>>> * 30 doc and www builds (83.3% (-1.3) passed, 16.7% (+1.3) failed) >>>>=20 >>>> Test case status (on 2020-04-12 23:59): >>>> | Branch/Architecture | Total | Pass | Fail | Skipped >>>> | >>>> | ------------------- | --------- | ---------- | -------- | = -------- >>>> | >>>> | head/amd64 | 7744 (+4) | 7638 (+19) | 14 (+5) | 92 (-20) >>>> | >>>> | head/i386 | 7742 (+4) | 7628 (+15) | 16 (+5) | 98 (-16) >>>> | >>>> | 12-STABLE/amd64 | 7508 (0) | 7449 (-3) | 1 (+1) | 58 (+2) >>>> | >>>> | 12-STABLE/i386 | 7506 (0) | 7425 (-17) | 2 (+2) | 79 (+15) >>>> | >>>> | 11-STABLE/amd64 | 6882 (0) | 6829 (-6) | 1 (+1) | 52 (+5) >>>> | >>>> | 11-STABLE/i386 | 6880 (0) | 6749 (-82) | 80 (+80) | 51 (+2) >>>> | >>>>=20 >>>> (The statistics from experimental jobs are omitted) >>>>=20 >>>> If any of the issues found by CI are in your area of interest or >>>> expertise >>>> please investigate the PRs listed below. >>>>=20 >>>> The latest web version of this report is available at >>>> https://hackmd.io/@FreeBSD-CI/report-20200412 and archive is >>>> available at >>>> https://hackmd.io/@FreeBSD-CI/ , any help is welcome. >>>>=20 >>>> ## News >>>>=20 >>>> * The test env now loads the required module for firewall tests. >>>>=20 >>>> * New armv7 job is added (to replace armv6 one): >>>> * FreeBSD-head-armv7-testvm >>>> The images are available at https://artifact.ci.freebsd.org >>>> FreeBSD-head-armv7-test is ready but needs test env update. >>>>=20 >>>> ## Failing jobs >>>>=20 >>>> * https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc6_build/ >>>> * See console log for the error details. >>>>=20 >>>> ## Failing tests >>>>=20 >>>> * https://ci.freebsd.org/job/FreeBSD-head-amd64-test/ >>>> * = local.kyua.integration.cmd_about_test.topic__authors__installed >>>> * sys.netipsec.tunnel.empty.v4 >>>> * sys.netipsec.tunnel.empty.v6 >>>> * sys.netpfil.common.forward.ipf_v4 >>>> * sys.netpfil.common.forward.ipfw_v4 >>>> * sys.netpfil.common.forward.pf_v4 >>>> * sys.netpfil.common.tos.ipfw_tos >>>> * sys.netpfil.common.tos.pf_tos >>>> * sys.netpfil.pf.forward.v4 >>> I can=E2=80=99t actually reproduce this failure in my test VM, but = with the >>> ci test VM I can reproduce the problem. >>> It=E2=80=99s not related to pf, because the sanity check ping we do = before >>> we set up pf already fails. >>> Or rather pft_ping.py sends an incorrect packet, because `ping` = does >>> get the packet to go where it=E2=80=99s supposed to go. >>>=20 >>> Scapy seems to fail to find the source IP address, so we get this: >>>=20 >>> 12:12:22.152652 IP 0.0.0.0 > 198.51.100.3: ICMP echo = request, id 0, >>> seq 0, length 12 >>>=20 >>> I have a vague recollection that we=E2=80=99ve seem this problem = before, but >>> I can=E2=80=99t remember what we did about it. >>>=20 >>> In all likelihood most of the other netpfil tests fail for exactly = the >>> same reason. >>=20 >> The problem appears to be that >> /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is = misparsing >> the `netstat -rnW` output. > Thanks for the analysis! >=20 > Sorry for breaking the tests. > I should have run tests with userland changes installed. >=20 > I'll revert the netstat output changes shortly to unbreak the tests. > Re longer-term: parsing textual output for the routes does not seem to = be a good habit, especially in these days. > Structural (libxo) approach looks better, however I guess this will = make scapy unusable on the routers with full-view. >=20 > So far light-weight sysctl-route reader looks like the best option. > What do you folks think? >=20 >>=20 >> For reference, this is the output in the test VM: >>=20 >> Routing tables >>=20 >> Internet: >> Destination Gateway Flags Nhop# Mtu Netif >> Expire >> 127.0.0.1 link#2 UH 1 16384 lo0 >> 192.0.2.0/24 link#4 U 2 1500 epair0a >> 192.0.2.1 link#4 UHS 1 16384 lo0 >> 198.51.100.0/24 192.0.2.2 UGS 3 1500 epair0a >>=20 >> Internet6: >> Destination Gateway Flags >> Nhop# Mtu Netif Expire >> ::/96 ::1 UGRS >> 4 16384 lo0 >> ::1 link#2 UH >> 1 16384 lo0 >> ::ffff:0.0.0.0/96 ::1 UGRS >> 4 16384 lo0 >> fe80::/10 ::1 UGRS >> 4 16384 lo0 >> fe80::%lo0/64 link#2 U >> 3 16384 lo0 >> fe80::1%lo0 link#2 UHS >> 2 16384 lo0 >> fe80::%epair0a/64 link#4 U >> 5 1500 epair0a >> fe80::3d:9dff:fe7c:d70a%epair0a link#4 UHS >> 1 16384 lo0 >> fe80::%epair1a/64 link#6 U >> 6 1500 epair1a >> fe80::37:9eff:fe03:250a%epair1a link#6 UHS >> 1 16384 lo0 >> ff02::/16 ::1 UGRS >> 4 16384 lo0 >>=20 >> The parsing code seems to think that the netif for the = 198.51.100.0/24 >> route is 1500 rather than epair0a. >> This may be related to the difference in netstat output, because on = my >> VM it looks like this: >>=20 >> Routing tables >>=20 >> Internet: >> Destination Gateway Flags Use Mtu Netif >> Expire >> default 172.16.2.1 UGS 319 1500 vtnet0 >> 127.0.0.1 link#2 UH 0 16384 lo0 >> 172.16.2.0/24 link#1 U 14 1500 vtnet0 >> 172.16.2.2 link#1 UHS 0 16384 lo0 >>=20 >> Internet6: >> Destination Gateway Flags >> Use Mtu Netif Expire >> ::/96 ::1 UGRS >> 0 16384 lo0 >> ::1 link#2 UH >> 0 16384 lo0 >> ::ffff:0.0.0.0/96 ::1 UGRS >> 0 16384 lo0 >> fe80::/10 ::1 UGRS >> 0 16384 lo0 >> fe80::%vtnet0/64 link#1 U >> 0 1500 vtnet0 >> fe80::5a9c:fcff:fe02:a95e%vtnet0 link#1 UHS >> 0 16384 lo0 >> fe80::%lo0/64 link#2 U >> 0 16384 lo0 >> fe80::1%lo0 link#2 UHS >> 0 16384 lo0 >> ff02::/16 ::1 UGRS >> 0 16384 lo0 >>=20 >> I suspect that this change was introduced in r359823 (Introduce = nexthop >> objects and new routing KPI). >>=20 >> Best regards, >> Kristof >> _______________________________________________ >> 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 Apr 15 23:19: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 C50A92C4B1B for ; Wed, 15 Apr 2020 23:19:54 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 492dc84nywz4Y6M for ; Wed, 15 Apr 2020 23:19:52 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (unknown [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 382E4639E for ; Wed, 15 Apr 2020 19:19:49 -0400 (EDT) To: freebsd-current From: Michael Butler Subject: anyone else seeing bind fail on recent -current? Message-ID: Date: Wed, 15 Apr 2020 19:19:48 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-NZ Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 492dc84nywz4Y6M X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-3.71)[ip: (-9.78), ipnet: 202.12.127.0/24(-4.89), asn: 5716(-3.85), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[protected-networks.net:+]; DMARC_POLICY_ALLOW(-0.50)[protected-networks.net,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2020 23:19:54 -0000 This instance is/was running in a jail but now fails sometime after SVN r359823 .. I'm trying to bisect but any hints appreciated .. named[98746]: ---------------------------------------------------- named[98746]: BIND 9 is maintained by Internet Systems Consortium, named[98746]: Inc. (ISC), a non-profit 501(c)(3) public-benefit named[98746]: corporation. Support and training for BIND 9 are named[98746]: available at https://www.isc.org/support named[98746]: ---------------------------------------------------- named[98746]: command channel listening on 127.0.0.1#953 named[98746]: command channel listening on ::1#953 named[98746]: netmgr.c:1000: REQUIRE(worker->recvbuf_inuse) failed, back trace named[98746]: #0 0x2cbb35 in ?? named[98746]: #1 0x4a7b4a in ?? named[98746]: #2 0x4bd297 in ?? named[98746]: #3 0x4c12a1 in ?? named[98746]: #4 0x8009f67f4 in ?? named[98746]: #5 0x8009f87b8 in ?? named[98746]: #6 0x8009e7e81 in ?? named[98746]: #7 0x4bb6e9 in ?? named[98746]: #8 0x800a15f39 in ?? named[98746]: exiting (due to assertion failure) root[98760]: /usr/local/etc/rc.d/named: WARNING: failed to start named imb From owner-freebsd-current@freebsd.org Thu Apr 16 00:24:51 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 7CFC82C6260 for ; Thu, 16 Apr 2020 00:24:51 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 492g366WJ9z4cYF; Thu, 16 Apr 2020 00:24:50 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 8EB76466E; Wed, 15 Apr 2020 20:24:48 -0400 (EDT) Subject: Re: anyone else seeing bind fail on recent -current? To: freebsd-current@freebsd.org References: Cc: thierry@freebsd.org From: Michael Butler Message-ID: Date: Wed, 15 Apr 2020 20:24:48 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-NZ Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 492g366WJ9z4cYF X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.70 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-3.70)[ip: (-9.75), ipnet: 202.12.127.0/24(-4.87), asn: 5716(-3.83), country: US(-0.05)]; DKIM_TRACE(0.00)[protected-networks.net:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protected-networks.net,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 00:24:51 -0000 On 4/15/20 7:19 PM, Michael Butler wrote: > This instance is/was running in a jail but now fails sometime after SVN > r359823 .. I'm trying to bisect but any hints appreciated .. > > named[98746]: ---------------------------------------------------- > named[98746]: BIND 9 is maintained by Internet Systems Consortium, > named[98746]: Inc. (ISC), a non-profit 501(c)(3) public-benefit > named[98746]: corporation. Support and training for BIND 9 are > named[98746]: available at https://www.isc.org/support > named[98746]: ---------------------------------------------------- > named[98746]: command channel listening on 127.0.0.1#953 > named[98746]: command channel listening on ::1#953 > named[98746]: netmgr.c:1000: REQUIRE(worker->recvbuf_inuse) failed, back > trace > named[98746]: #0 0x2cbb35 in ?? > named[98746]: #1 0x4a7b4a in ?? > named[98746]: #2 0x4bd297 in ?? > named[98746]: #3 0x4c12a1 in ?? > named[98746]: #4 0x8009f67f4 in ?? > named[98746]: #5 0x8009f87b8 in ?? > named[98746]: #6 0x8009e7e81 in ?? > named[98746]: #7 0x4bb6e9 in ?? > named[98746]: #8 0x800a15f39 in ?? > named[98746]: exiting (due to assertion failure) > root[98760]: /usr/local/etc/rc.d/named: WARNING: failed to start named As it turns out, the update to devel/libuv on SVN r531786 causes this failure .. :-( imb From owner-freebsd-current@freebsd.org Thu Apr 16 01:12:06 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 F3F262C7FFE for ; Thu, 16 Apr 2020 01:12:05 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492h5d1l5Zz3Cj1 for ; Thu, 16 Apr 2020 01:12:05 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pl1-x644.google.com with SMTP id ay1so737453plb.0 for ; Wed, 15 Apr 2020 18:12:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zckfh4O+Fl8JasIFemsKHptRnfAGUUvT8zUH4JtyCRs=; b=b5mOuSqtpxG7z/+dzSTr1Ejdrpfk2MitutIeotP4Hbwef8yuUPi7YBbF09ZjV2E4ZZ nS8Cc8qQUIyeM6XMI8t7s5m7siBLSsSuHQNRO57OeusK6SDkY2oLFVLcwmOa28iVIkDH MVwJY65F5b97v2PRj5XYJa1m+Vpo2/eL4SxR79JVvKEk6kyMP+/L6hHTM7DP1aeoxkZY /okki5LTz5t4DoPwTfbc8uLmWP4jKEl+a2FenbL3zF/R2DFH9XBV/3TWvtOVBhFR9dB9 XZ+5WF9S4/mRKQ6UnwCWY+SvbDzv8Z5LiRPoYtD5KUgBiny4dddWfxAoED8eM/DyOKeI 79cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=zckfh4O+Fl8JasIFemsKHptRnfAGUUvT8zUH4JtyCRs=; b=ISfGTFi6wLVaj/S5h6zGmGIRQFbAu3ZHDhRTNXBs0+1ncMSX5nWpCGFz08HXncRZ2t xenCRvdmqJnFujK/JABMip4wmbV0SXo9Wg/3z5Pc50uazb+c8zZ1FoZeYNR7gOF81XNS exOxezA3oPNekvm/G/TlklOWokadzFl7NVf9HfCPhCq/5mzlimLBMovyl3GtjJqomL9N QrhLh9PsnPxxCFkTD4pNoRvDdM1iv8je+UW0LoyFHcBrTI7jSNMUZWE9ELaVjkwVdk2W 1SXV/WZKKKFJr6564sf3EkupMOXDH0kmiAUPokfDaodcGc9kh1f/o7/2BEZTvXig0sgC OkOQ== X-Gm-Message-State: AGi0PuZBxtOLxF21z7Tg7X3Rbl3Bw+Ug4sa+iIc3CO8U1XbFC/5nbRPC 0ij94fXrNH5+O+ZcLmWmlG2rhCKt X-Google-Smtp-Source: APiQypINBzXz0gZMIeMxquufY2PuH2CpmJ6d9+6EHFoOW31huwNFZtCfNjttlr76GLivhFUuKF7sjw== X-Received: by 2002:a17:90a:252f:: with SMTP id j44mr2120453pje.9.1586999523635; Wed, 15 Apr 2020 18:12:03 -0700 (PDT) Received: from [192.168.1.103] (180-150-68-130.b49644.syd.nbn.aussiebb.net. [180.150.68.130]) by smtp.gmail.com with ESMTPSA id r13sm14231170pgj.9.2020.04.15.18.12.01 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Apr 2020 18:12:03 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: anyone else seeing bind fail on recent -current? To: freebsd-current@freebsd.org References: From: Kubilay Kocak Message-ID: Date: Thu, 16 Apr 2020 11:11:58 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Thunderbird/76.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 492h5d1l5Zz3Cj1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=b5mOuSqt; dmarc=none; spf=pass (mx1.freebsd.org: domain of koobsfreebsd@gmail.com designates 2607:f8b0:4864:20::644 as permitted sender) smtp.mailfrom=koobsfreebsd@gmail.com X-Spamd-Result: default: False [-1.35 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[koobs@FreeBSD.org]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; FORGED_SENDER(0.30)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_NEQ_ENVFROM(0.00)[koobs@FreeBSD.org,koobsfreebsd@gmail.com]; FROM_HAS_DN(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.16)[ip: (-0.02), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[4.4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 01:12:06 -0000 On 16/04/2020 10:24 am, Michael Butler wrote: > On 4/15/20 7:19 PM, Michael Butler wrote: >> This instance is/was running in a jail but now fails sometime after SVN >> r359823 .. I'm trying to bisect but any hints appreciated .. >> >> named[98746]: ---------------------------------------------------- >> named[98746]: BIND 9 is maintained by Internet Systems Consortium, >> named[98746]: Inc. (ISC), a non-profit 501(c)(3) public-benefit >> named[98746]: corporation. Support and training for BIND 9 are >> named[98746]: available at https://www.isc.org/support >> named[98746]: ---------------------------------------------------- >> named[98746]: command channel listening on 127.0.0.1#953 >> named[98746]: command channel listening on ::1#953 >> named[98746]: netmgr.c:1000: REQUIRE(worker->recvbuf_inuse) failed, back >> trace >> named[98746]: #0 0x2cbb35 in ?? >> named[98746]: #1 0x4a7b4a in ?? >> named[98746]: #2 0x4bd297 in ?? >> named[98746]: #3 0x4c12a1 in ?? >> named[98746]: #4 0x8009f67f4 in ?? >> named[98746]: #5 0x8009f87b8 in ?? >> named[98746]: #6 0x8009e7e81 in ?? >> named[98746]: #7 0x4bb6e9 in ?? >> named[98746]: #8 0x800a15f39 in ?? >> named[98746]: exiting (due to assertion failure) >> root[98760]: /usr/local/etc/rc.d/named: WARNING: failed to start named > > As it turns out, the update to devel/libuv on SVN r531786 causes this > failure .. :-( > Tracked at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245653 From owner-freebsd-current@freebsd.org Thu Apr 16 06:34: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 047AE2B24DC; Thu, 16 Apr 2020 06:34:54 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492qG46pXPz432X; Thu, 16 Apr 2020 06:34:52 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-wr1-x42c.google.com with SMTP id d27so3481431wra.1; Wed, 15 Apr 2020 23:34:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LPfmQUu0UfMQ1rR7YSThHDfoUkMef4LciOt0qUf53q0=; b=IGMb66aKbgpm5FADjd4DGNZX2t/fMKOXlSKQimI7jfve9Zx2NUeP96bnfm4eqsicLn L0ZoYANppc6Yagu6oHE1jvF3IX8EBNfpoQ4JFjs32KX5eXQR07ezuirVP63xaXapLijw 4fCT92PRh1lCcWtzOP3GRV4j4OaJe5WeNc/qLPMaIKhkM5q8ppTXMGLNkg53so9w8aCJ +YLsqBWGCCbYYJNoZF/G3z1WYpaNTpN6vAUk3Nix8FzU61kDks9oVGXuWKrYS9HXILAZ jOjOIUcDRHAjkvPO44cCS4jseowSq8MbiNwW0UCehgpyABL9RSeyOvI30U+gemI3uQsU nKWA== 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=LPfmQUu0UfMQ1rR7YSThHDfoUkMef4LciOt0qUf53q0=; b=GQEo/fV6jld56hvzViDnHOlU2L6mzp8NRopFEqJTs3EuR9kgC+RDmkAAEeTiKn9WCY OvSQr6g/4jwL5rHVsi8jutj1QOZ/IA/Q9S/k3CrBf7T++XtHVPlv3bioplfFoud1nIC6 mzpNJJvosRto03g7ugnMQjtGK7rdWmngdAS6+s2FHUsF8f/FV3djKQ83HV9Jxob3AupZ oNycaMBa0d7pBTwLrOM2zIOgLqcUBYe4jg9EmGkgp894kOTQE+4VfwsMqhbzYekkhSr+ 5wUOIlrCgGbZZTelXwu3sEmENOsOCceI84TP+ButRYknaS5z8CmRXd32jPmi64f/RkXw XB/g== X-Gm-Message-State: AGi0PuZx3IPGxSErdcc0zdIWuUbLCRLHBJwQ3MpuXj4UOh0kNs2gVtXI kOcgAs7JPuwP6E19SqLPzRWhXaNy2B1JP9Rp9Jfh9Q== X-Google-Smtp-Source: APiQypLCld7jAqOuX7lAP2nkn/81Spqa1jocBofXLPrTldVfhoS5zWO1HdPch1P1oLP21Jw658g7cAYrnY0t/SWKNJk= X-Received: by 2002:a5d:474b:: with SMTP id o11mr25202855wrs.391.1587018890418; Wed, 15 Apr 2020 23:34:50 -0700 (PDT) MIME-Version: 1.0 References: <5377E42E-4C01-4BCC-B934-011AC3448B54@FreeBSD.org> In-Reply-To: <5377E42E-4C01-4BCC-B934-011AC3448B54@FreeBSD.org> From: Pavel Timofeev Date: Thu, 16 Apr 2020 09:34:41 +0300 Message-ID: Subject: Re: CFT: if_bridge performance improvements To: Kristof Provost Cc: freebsd-current , freebsd-stable stable X-Rspamd-Queue-Id: 492qG46pXPz432X X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=IGMb66aK; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of timp87@gmail.com designates 2a00:1450:4864:20::42c as permitted sender) smtp.mailfrom=timp87@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; URI_COUNT_ODD(1.00)[9]; IP_SCORE(0.00)[ip: (-9.12), ipnet: 2a00:1450::/32(-2.35), asn: 15169(-0.43), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[c.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 06:34:54 -0000 =D0=B2=D1=82, 14 =D0=B0=D0=BF=D1=80. 2020 =D0=B3., 12:51 Kristof Provost : > Hi, > > Thanks to support from The FreeBSD Foundation I=E2=80=99ve been able to w= ork > on improving the throughput of if_bridge. > It changes the (data path) locking to use the NET_EPOCH infrastructure. > Benchmarking shows substantial improvements (x5 in test setups). > > This work is ready for wider testing now. > > It=E2=80=99s under review here: https://reviews.freebsd.org/D24250 > > Patch for CURRENT: https://reviews.freebsd.org/D24250?download=3Dtrue > Patches for stable/12: > https://people.freebsd.org/~kp/if_bridge/stable_12/ > > I=E2=80=99m not currently aware of any panics or issues resulting from th= ese > patches. > > Do note that if you run a Bhyve + tap on bridges setup the tap code > suffers from a similar bottleneck and you will likely not see major > improvements in single VM to host throughput. I would expect, but have > not tested, improvements in overall throughput (i.e. when multiple VMs > send traffic at the same time). > > Best regards, > Kristof > Hi! Thank you for your work! Do you know if epair suffers from the same issue as tap? > From owner-freebsd-current@freebsd.org Thu Apr 16 07:41:52 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 288002B4365; Thu, 16 Apr 2020 07:41:52 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 492rlN0LQpz478X; Thu, 16 Apr 2020 07:41:52 +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 E65781F43F; Thu, 16 Apr 2020 07:41:51 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 7331FF9F9; Thu, 16 Apr 2020 09:41:49 +0200 (CEST) From: "Kristof Provost" To: "Pavel Timofeev" Cc: freebsd-current , "freebsd-stable stable" Subject: Re: CFT: if_bridge performance improvements Date: Thu, 16 Apr 2020 09:41:48 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: <5D021E5B-8B7C-4DF2-ABC7-415A1D0F0B62@FreeBSD.org> In-Reply-To: References: <5377E42E-4C01-4BCC-B934-011AC3448B54@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 07:41:52 -0000 On 16 Apr 2020, at 8:34, Pavel Timofeev wrote: > Hi! > Thank you for your work! > Do you know if epair suffers from the same issue as tap? > I’ve not tested it, but I believe that epair scales significantly better than tap. It has a per-cpu mutex (or more accurately, a mutex in each of its per-cpu structures), so I’d expect much better throughput from epair than you’d see from tap. Best regards, Kristof From owner-freebsd-current@freebsd.org Thu Apr 16 15:41: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 7C9FD2BF8A6 for ; Thu, 16 Apr 2020 15:41:17 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4933NY128Gz4dTc for ; Thu, 16 Apr 2020 15:41:17 +0000 (UTC) (envelope-from scottl@samsco.org) Received: by mailman.nyi.freebsd.org (Postfix) id 214942BF8A5; Thu, 16 Apr 2020 15:41:17 +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 210B82BF8A4 for ; Thu, 16 Apr 2020 15:41:17 +0000 (UTC) (envelope-from scottl@samsco.org) 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 4933NX0dqKz4dTX for ; Thu, 16 Apr 2020 15:41:15 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 2BED3686; Thu, 16 Apr 2020 11:41:14 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 16 Apr 2020 11:41:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=P zn3N9gp+jf00HHeQipZ9eVgiNoJx7LFOv6pG7nVots=; b=gac7fWW/FkoWRlS0w ZVwydisLQOsMOMeWI0TtFIq4rflpK3kdiynHP/L/zjG+CIM3L4f/RYGzTuoulORr yRqekveXKNGOd1zNmT0hs+fx3JAdw+5mV6PxE7oYtdsOR1XVet3DMnVCSULqmJen M8PGrvxSAKoGkgVwbvzvLxwG8POL5vMURpalHX4rsTpiwD2nYj9TxqOnfM4TSObi +Eq4VYfWnJ+iUE2SkNuEFRF7iNyrlDACx16mSH2Um9Gbg5HAWyXPo2fFof5quEaE azdw1P889eUBYrR8oFqVgufiR9qVempXd1Y0HhggKqYjZtovb0DBUq2LRn43Rhg5 9JBjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Pzn3N9gp+jf00HHeQipZ9eVgiNoJx7LFOv6pG7nVo ts=; b=13lGTrOf224CCW6vPN0GfQir91w/MzOj7UeE9E145c0uK1tmFYpCKrTQ2 KdR6deDHz/DNY44yd0Kgsc7zp4AsSXgAlJ+TwqeaIV73MdI/tcHV5zGTOI/D5zP4 FD7zPDQj4LE6Xzc35r4RdZcnxvDcMPJJFaB8eSS8oEFXiaGs2NqyBpp+k7YwupRF k5Eu0sFMllyuV9Qc8i1ccNjPrzeuHpRnlOpcEB0vWHFOFWakTsJoJBNJ1+h5VDDf 00sgGLhWx4PIE3PSqhm+s8WW8/TQf75+WyeVl2Zx8O98iOdNg0GWWd36nYWvga+6 PT0sOavDjocv60HDVQrCcgjpxFt5Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeehgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpefutghothht ucfnohhnghcuoehstghothhtlhesshgrmhhstghordhorhhgqeenucfkphepkedrgeeird ekledrvddufeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehstghothhtlhesshgrmhhstghordhorhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F7C6306006C; Thu, 16 Apr 2020 11:41:12 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: buildkernel failure because ctfconvert not installed From: Scott Long In-Reply-To: <89524.1586501879@critter.freebsd.dk> Date: Thu, 16 Apr 2020 09:41:11 -0600 Cc: Yuri Pankov , =?utf-8?Q?Trond_Endrest=C3=B8l?= , Gary Jennejohn , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20200408083204.4a2d6dbc@ernst.home> <814e8e7d-68e6-bead-481b-21c5552583c4@FreeBSD.org> <20200409093346.1aec1bba@ernst.home> <20200409105626.386b0ba5@ernst.home> <9f03fb79-a0ad-3c11-9a50-bc7731882da9@fastmail.com> <89524.1586501879@critter.freebsd.dk> To: Poul-Henning Kamp , freebsd-rwg@gndrsh.dnsmgr.net X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 4933NX0dqKz4dTX X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=gac7fWW/; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=13lGTrOf; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.25 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[samsco.org]; RCPT_COUNT_FIVE(0.00)[6]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.84), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[25.123.147.64.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; FREEMAIL_CC(0.00)[fastmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 15:41:17 -0000 > On Apr 10, 2020, at 12:57 AM, Poul-Henning Kamp = wrote: >=20 > -------- > In message <9f03fb79-a0ad-3c11-9a50-bc7731882da9@fastmail.com>, Yuri = Pankov writes: >> Trond Endrest=C3=B8l wrote: >>> On Thu, 9 Apr 2020 10:56+0200, Gary Jennejohn wrote: >>>=20 >>>> OK, I figured it out. >>>>=20 >>>> I used to have MK_CTF=3Dno in src.conf, but I recently changed it = to >>>> WITH_CTF=3Dno. >>>=20 >>> It's either WITH_xxx=3Dyes or WITHOUT_xxx=3Dyes. >>=20 >> Or even WITH_xxx=3D or WITHOUT_xxx=3D, src.conf(5) explicitly states = that=20 >> value is NOT checked: >>=20 >> The values of variables are ignored regardless of their setting; even = if=20 >> they would be set to "FALSE" or "NO". The presence of an option=20 >> causes it to be honored by make(1). >=20 > That is not even close to POLA-compliance... >=20 > Obviously negative values ("false", "no") should either be reported as > errors or preferably be respected. >=20 > PS: [This is not the bikeshed you are looking for] >=20 I remember being slightly astonished by the current behavior in the = early/mid 2000=E2=80=99s. Then I learned, adapted, and got over it. Change happens, often for the = best. Being stuck in the past doesn=E2=80=99t help, and neither does Rodney=E2=80=99s action of = berating, belittling, and gaslighting people who don't agree with him. POLA is a good mental check to help guide decisions, but it=E2=80=99s = not set in stone. Nothing should be set in stone, we should all be willing and able to evaluate = circumstances and make new decisions. Being robotic and set in stone is an excuse for = being lazy and/or egotistical. Scott From owner-freebsd-current@freebsd.org Thu Apr 16 18:48: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 B59212C4E00 for ; Thu, 16 Apr 2020 18:48:50 +0000 (UTC) (envelope-from joh.hendriks@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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4937Xx4ggtz3RHB for ; Thu, 16 Apr 2020 18:48:49 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wr1-x435.google.com with SMTP id b11so6071768wrs.6 for ; Thu, 16 Apr 2020 11:48:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=Dm+SS+2Q4v6iQQKYCBVN7ER+xprTsA0v79pc/yM4aXg=; b=bcgm646Avc8Ib8tZy+SD8V8dlnTp33UoDPYPdyY+0wNTckbl5bljQ4on/NqmaysR4k 0JfxA86NHtvtHgOc3quSIOXEjI/8wC7FifRNdzFQrM3tcNW1HJlr9bSeWhMUv6uR11nP PTmM2JVckoW09XN66iPwxIsjHqJxOcK9ZqmLJ9VFv3TZSQtrv2G3wVywzxV88cC6/RTt ylSacCnm/EWKMbqCKWEhcM2G6CbtY8X8mvyki0E4xRWQAgeDCvsKtnZsT08aDkyKpU0c shMrJwPxGQ0rprfdR20Q/84D6od8ZTATaH7gso+qsoFEh1lADQAlkX4vv7EMaogHdCso 8uhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=Dm+SS+2Q4v6iQQKYCBVN7ER+xprTsA0v79pc/yM4aXg=; b=WRbCvTD45ipq9q8jQVKJeMxK9VZGDczyLJqHB0HxSSixhwyIhf3J2SCL4/kRgfAoKl KKYCgq5vaa6bvKf/UjpnXtJZ9Wn43Ol4iP5nW3una7Ip8m9Rc+VrQ4nkAfc42tf1OatV SCut2sbFz8QFuKsbL+Wukpwfe+P2L/knIH1TkJkhQK3ITWlhWqacADC2LEXRrU69rqFz wjVNb4YNzWnqPm0CbLWyDNbICjSCmTN6H4nbHY8Xm7AP1taqe19Y5QYdDmACkyLnD4by 07JyT7r8xdbkPkKRA8A/33SxQPAoYSHknhGhzRec6UnKhqQ9eE6gCTMe+D+DpU6979Z+ vabg== X-Gm-Message-State: AGi0PuZTxwzcOWSwFJTZoKk1cWniLthOOd9+p1Nu0gR66brBU37q27SX PccJ+ABBXazCw5rnzsaeU/0OkDvJoa0= X-Google-Smtp-Source: APiQypLUkk9V9tQKFhWN4G8oQQijg7Qxi1P06xcKNYfuIb8ihViLcjq9cHON+6MaOeJV9wqCodRUvw== X-Received: by 2002:adf:d845:: with SMTP id k5mr10228805wrl.214.1587062911058; Thu, 16 Apr 2020 11:48:31 -0700 (PDT) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id k184sm4611648wmf.9.2020.04.16.11.48.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Apr 2020 11:48:30 -0700 (PDT) To: freebsd-current@freebsd.org From: Johan Hendriks Subject: sort.core error doing installworld on Current. Message-ID: <3f8a4c5f-d1fb-9e31-d9d5-5bbbe311c265@gmail.com> Date: Thu, 16 Apr 2020 20:48:29 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: nl X-Rspamd-Queue-Id: 4937Xx4ggtz3RHB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=bcgm646A; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johhendriks@gmail.com designates 2a00:1450:4864:20::435 as permitted sender) smtp.mailfrom=johhendriks@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.36), ipnet: 2a00:1450::/32(-2.35), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[5.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 18:48:50 -0000 I have a machine running FreeBSD head. rev 13.0-CURRENT #11 r360008 This is a quite powerful machine, so i thought it was a good idea to let that server do the build and for my virtualbox machine i can use the powerful machine to do a installword over NFS. But when i did the make installworld step the client so to say gives an error. install   -o root -g wheel -m 444 /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu /usr/share/zoneinfo/Zulu install   -o root -g wheel -m 444 /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules /usr/share/zoneinfo/posixrules install   -o root -g wheel -m 444 /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core /usr/share/zoneinfo/sort.core install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: Permission denied *** Error code 71 Stop. bmake[5]: stopped in /usr/src/share/zoneinfo *** Error code 1 Stop. bmake[4]: stopped in /usr/src/share *** Error code 1 Stop. bmake[3]: stopped in /usr/src *** Error code 1 Stop. bmake[2]: stopped in /usr/src *** Error code 1 Stop. bmake[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src .ERROR_TARGET='installworld' .ERROR_META_FILE='' .MAKE.LEVEL='0' MAKEFILE='' .MAKE.MODE='normal' _ERROR_CMD='.PHONY' .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64' .TARGETS='installworld' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='/usr/obj' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20181221' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64' It looks likes sort coredumps in the usr/share/zoneinfo part of the base. As it has no permission on the NFS share it errors out. On the server itself, the installworld goes well, but it leaves a sort.core file behind in /usr/share/zoneinfo cd /usr/share/zoneinfo ls -al -r--r--r--   1 root  wheel          118 Apr 16 20:25 Zulu -r--r--r--   1 root  wheel        3519 Apr 16 20:25 posixrules -r--r--r--   1 root  wheel  8982528 Apr 16 20:25 sort.core -r--r--r--   1 root  wheel      19424 Apr 16 20:25 zone.tab -r--r--r--   1 root  wheel      17955 Apr 16 20:25 zone1970.tab my src.conf file looks like this WITHOUT_BLUETOOTH=yes WITHOUT_CALENDAR=yes WITHOUT_DICT=yes WITHOUT_GAMES=yes WITHOUT_I4B=yes WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_LPR=yes WITHOUT_PROFILE=yes WITHOUT_SENDMAIL=yes WITHOUT_SHAREDOCS=yes WITHOUT_WIRELESS=yes WITHOUT_HAST=yes WITHOUT_LLVM_TARGET_{MIPS,POWERPC,SPARC,RISCV}= YES WITHOUT_LIB32=yes in /etc/make.conf i have the following MALLOC_PRODUCTION=yes BATCH_DELETE_OLD_FILES= yes CUPS_OVERWRITE_BASE=yes What can i do about this? Thank you for your time. From owner-freebsd-current@freebsd.org Thu Apr 16 19:40:00 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 CD21B2C6012 for ; Thu, 16 Apr 2020 19:40:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi1-x241.google.com (mail-oi1-x241.google.com [IPv6:2607:f8b0:4864:20::241]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4938h00RQmz40t6 for ; Thu, 16 Apr 2020 19:39:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi1-x241.google.com with SMTP id t199so544oif.7 for ; Thu, 16 Apr 2020 12:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=p6UIIkPmetfzTdXMrIB6LpUmA/Xm/HvkF3xoylHIvF4=; b=W3Ex1iWoTXIfmmo17rZawsKC6WtlmBsPJYwGNDQp51aKRhN5D0Qzw6gNOXjS3QA/nE hIG726VCygTR1zV7Zxm5rLVDycMS02QtG+S+/xbA26nfaU6t+Dez5ep1dT5Dq2Sn1lmk Qy7fohLwk4x4TrzRo8seNNEARhHFkdlo7gJK22JlrUgXIRTL7hrGkpZ5eb9vqrHo8aQr 4HZ8YymXlbPDHOVgVebGjzsXTftQm8s/iAKmkOgT5Q7N/UWh/Y223Kbld+Lc/gekUGYV A/ZYLHh/WN9HvmNzXoXuQxucwhwD2oip2bKqqgGWhhJ1TNnJxWm7jo0SobtliRlZxn7j lAvg== 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=p6UIIkPmetfzTdXMrIB6LpUmA/Xm/HvkF3xoylHIvF4=; b=frFjW1PZx8MIj3akJ6ygYspwnI85sA3cRGNq3rDyV33umYSavzZdB65xQI0QBSxgjE SRs38kbeHqA1RcU/avZ5+060xns2uu1Q8Hjxs1f3Nro2Xc1CSZmitMDJmCxIqc5gS7NH gZ2c0AcIzGdGr+henzgzsoW2d/NOtN2IEDkdxaEDi9hR3DwrViIrPYFhzjsVbslGla98 s001tP8nFkn7A1JzM1Ww5jJyL1PB8floR/lQN3fpiN273WrAGKy87U6k5hq3UnszNrOm e8NOBnBKqQkirvFvEVNZc9QsIsYezZbWq+XrbVugGeJUVIhA1FgcCCJWZ+O65lyeqhJN t9kA== X-Gm-Message-State: AGi0Pub6vQFqKfG0ogZ+97PaayXWyFKAcZARNy6SvEbzBRy9x4o+/BbK ga6jMVdOFIN/oKRRmT8G4NZVpfYtQta8pXv78UT5Haps87A= X-Google-Smtp-Source: APiQypJAocQzJkB+sVFlOlpoc4cvgWU6YgYhs2VxZLyqlqqQ6ougbYW5VgiQpDSrWoHV34JLaA0jyyYZbmmgv8+9d9Q= X-Received: by 2002:aca:4588:: with SMTP id s130mr4107139oia.133.1587065998922; Thu, 16 Apr 2020 12:39:58 -0700 (PDT) MIME-Version: 1.0 References: <3f8a4c5f-d1fb-9e31-d9d5-5bbbe311c265@gmail.com> In-Reply-To: <3f8a4c5f-d1fb-9e31-d9d5-5bbbe311c265@gmail.com> From: Kevin Oberman Date: Thu, 16 Apr 2020 12:39:42 -0700 Message-ID: Subject: Re: sort.core error doing installworld on Current. To: Johan Hendriks Cc: FreeBSD Current X-Rspamd-Queue-Id: 4938h00RQmz40t6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=W3Ex1iWo; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::241 as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-1.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[5]; 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]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; IP_SCORE(0.00)[ip: (0.10), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 19:40:00 -0000 ai you some how had a sort core dump sitting in /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how did get there? I'd take a look at the date on the file and, it it is older than the buildworld, just assume that it was left-over garbage. In either case, you can delete it and do another installworld. That should most likely fix things, but, if the buildworld or installworld had a crash of sort(1) that left the file, further investigation might be needed. Re-making the zoneinfo would help track it down should this be a rel bug, but it's my uneducated guess that it's not. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks wrote: > I have a machine running FreeBSD head. > rev 13.0-CURRENT #11 r360008 > > This is a quite powerful machine, so i thought it was a good idea to let > that server do the build and for my virtualbox machine i can use the > powerful machine to do a installword over NFS. > > But when i did the make installworld step the client so to say gives an > error. > > install -o root -g wheel -m 444 > /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu > /usr/share/zoneinfo/Zulu > install -o root -g wheel -m 444 > /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules > /usr/share/zoneinfo/posixrules > install -o root -g wheel -m 444 > /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core > /usr/share/zoneinfo/sort.core > install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: > Permission denied > *** Error code 71 > > Stop. > bmake[5]: stopped in /usr/src/share/zoneinfo > *** Error code 1 > > Stop. > bmake[4]: stopped in /usr/src/share > *** Error code 1 > > Stop. > bmake[3]: stopped in /usr/src > *** Error code 1 > > Stop. > bmake[2]: stopped in /usr/src > *** Error code 1 > > Stop. > bmake[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > .ERROR_TARGET='installworld' > .ERROR_META_FILE='' > .MAKE.LEVEL='0' > MAKEFILE='' > .MAKE.MODE='normal' > _ERROR_CMD='.PHONY' > .CURDIR='/usr/src' > .MAKE='make' > .OBJDIR='/usr/obj/usr/src/amd64.amd64' > .TARGETS='installworld' > DESTDIR='' > LD_LIBRARY_PATH='' > MACHINE='amd64' > MACHINE_ARCH='amd64' > MAKEOBJDIRPREFIX='/usr/obj' > MAKESYSPATH='/usr/src/share/mk' > MAKE_VERSION='20181221' > PATH='/sbin:/bin:/usr/sbin:/usr/bin' > SRCTOP='/usr/src' > OBJTOP='/usr/obj/usr/src/amd64.amd64' > > It looks likes sort coredumps in the usr/share/zoneinfo part of the base. > As it has no permission on the NFS share it errors out. > On the server itself, the installworld goes well, but it leaves a > sort.core file behind in /usr/share/zoneinfo > > cd /usr/share/zoneinfo > ls -al > -r--r--r-- 1 root wheel 118 Apr 16 20:25 Zulu > -r--r--r-- 1 root wheel 3519 Apr 16 20:25 posixrules > -r--r--r-- 1 root wheel 8982528 Apr 16 20:25 sort.core > -r--r--r-- 1 root wheel 19424 Apr 16 20:25 zone.tab > -r--r--r-- 1 root wheel 17955 Apr 16 20:25 zone1970.tab > > my src.conf file looks like this > WITHOUT_BLUETOOTH=yes > WITHOUT_CALENDAR=yes > WITHOUT_DICT=yes > WITHOUT_GAMES=yes > WITHOUT_I4B=yes > WITHOUT_IPFILTER=yes > WITHOUT_IPX=yes > WITHOUT_LPR=yes > WITHOUT_PROFILE=yes > WITHOUT_SENDMAIL=yes > WITHOUT_SHAREDOCS=yes > WITHOUT_WIRELESS=yes > WITHOUT_HAST=yes > WITHOUT_LLVM_TARGET_{MIPS,POWERPC,SPARC,RISCV}= YES > WITHOUT_LIB32=yes > > in /etc/make.conf i have the following > MALLOC_PRODUCTION=yes > BATCH_DELETE_OLD_FILES= yes > CUPS_OVERWRITE_BASE=yes > > > What can i do about this? > > Thank you for your time. > > > _______________________________________________ > 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 Apr 16 19:51: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 0FFFA2C6597 for ; Thu, 16 Apr 2020 19:51:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4938wk0KQxz41lc for ; Thu, 16 Apr 2020 19:51:01 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x332.google.com with SMTP id g14so4093308otg.10 for ; Thu, 16 Apr 2020 12:51:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6s5MjSxCfmOL+ovrmId2f46S9IeXmZU0I2FgaWXp+6Q=; b=ox9rHMokjsZUUOTyAnN/uHssyviD74K3G+QZGy1a2BoZvhm81ZuLEf1975ZGpLy9Uy woUIh/1WC3n35USVVhUoLwUolL4FTtB7OSV151+icGa6yB+miSHz7LgKMmQZPwkqfVAY d4h3785i191xcPKVCk95x9aiG2bS9VWmyKvQ6PfNoAaJicCb9b4bWrrEj8SYYN7D5UQF rDh9zZ7/zz4zmq375iwYJGq8qssDf144KaCo1okzMOKAuhWisXMbbr00EQtZxu1ICEny LrxUFOXhv/bhQqxL1H30qZBtItaBDNfmXWq2pm+5bgNIkAoHJH2P3m9R2UIxmQelTumd wtVQ== 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=6s5MjSxCfmOL+ovrmId2f46S9IeXmZU0I2FgaWXp+6Q=; b=JbaFPTZXDqdZi3py9FbxOnlwSpFJU1RiqaydS/+ipy25a9QCnXlnCSCTjSC6bDP2bC 6hi/casfBFvmgmxKk2+sZUyF877bpt0pM2dv67gizl2JaJVS/E5nSm2BjE3GcZ6GFfwQ XtXd8GQgeCIav7ubPyTCpzCVLi+vlvS2+lJm4e14WSWpLr3dlf2O+z7Pe1Xw1tYFd1gR /pP1yrcBj9F2+3TAjZ6h/L5qZ6zzJsriKrZanoI9W3GXd/tkPDSaV6IC3ktZoQ1F+GSg 5WRIEM1G0ARuXHQO4nIifjg6VPtEEZk2cv/iyZQsp/eU7arshRCveKJREjfpcbIZLCEr dU9w== X-Gm-Message-State: AGi0Puan5Sztty9aZgk/11sKUNQrS1EAHp43U2M4NHFMSA1U6+QGY6le sqbM588sxmkSeeLlcWa7eUo/cXYSIFd9+nyjSl7Hox/4QwQ= X-Google-Smtp-Source: APiQypLy3LugJgU2q9/Z9fdyFth0Ci6RIhJDjJtwKOK9xN916wonhPaKaT7yQnrhbd3+SGFaP/0SL2KdckfAuPR5ab0= X-Received: by 2002:a05:6830:157:: with SMTP id j23mr8111555otp.93.1587066660718; Thu, 16 Apr 2020 12:51:00 -0700 (PDT) MIME-Version: 1.0 References: <3f8a4c5f-d1fb-9e31-d9d5-5bbbe311c265@gmail.com> In-Reply-To: From: Kevin Oberman Date: Thu, 16 Apr 2020 12:50:44 -0700 Message-ID: Subject: Re: sort.core error doing installworld on Current. To: Johan Hendriks Cc: FreeBSD Current X-Rspamd-Queue-Id: 4938wk0KQxz41lc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ox9rHMok; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::332 as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-2.70 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; 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]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; IP_SCORE(0.00)[ip: (-8.49), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.3.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2020 19:51:03 -0000 On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: > So you some how had a sort core dump sitting in > /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how > did get there? I'd take a look at the date on the file and, it it is older > than the buildworld, just assume that it was left-over garbage. In either > case, you can delete it and do another installworld. > > That should most likely fix things, but, if the buildworld or installworld > had a crash of sort(1) that left the file, further investigation might be > needed. Re-making the zoneinfo would help track it down should this be a re > al bug, but it's my uneducated guess that it's not. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > Please forgive that awful post! I missed a part of your message by laziness. It's odd that the error of sort(1) crashing was not caught by the script. Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch something. Looking at the core might tell you which "sort" was involved... the one you just built or the one in the base system. This could be just a FOTU, but I would not bet on it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks > wrote: > >> I have a machine running FreeBSD head. >> rev 13.0-CURRENT #11 r360008 >> >> This is a quite powerful machine, so i thought it was a good idea to let >> that server do the build and for my virtualbox machine i can use the >> powerful machine to do a installword over NFS. >> >> But when i did the make installworld step the client so to say gives an >> error. >> >> install -o root -g wheel -m 444 >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu >> /usr/share/zoneinfo/Zulu >> install -o root -g wheel -m 444 >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules >> /usr/share/zoneinfo/posixrules >> install -o root -g wheel -m 444 >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core >> /usr/share/zoneinfo/sort.core >> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: >> Permission denied >> *** Error code 71 >> >> Stop. >> bmake[5]: stopped in /usr/src/share/zoneinfo >> *** Error code 1 >> >> Stop. >> bmake[4]: stopped in /usr/src/share >> *** Error code 1 >> >> Stop. >> bmake[3]: stopped in /usr/src >> *** Error code 1 >> >> Stop. >> bmake[2]: stopped in /usr/src >> *** Error code 1 >> >> Stop. >> bmake[1]: stopped in /usr/src >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/src >> .ERROR_TARGET='installworld' >> .ERROR_META_FILE='' >> .MAKE.LEVEL='0' >> MAKEFILE='' >> .MAKE.MODE='normal' >> _ERROR_CMD='.PHONY' >> .CURDIR='/usr/src' >> .MAKE='make' >> .OBJDIR='/usr/obj/usr/src/amd64.amd64' >> .TARGETS='installworld' >> DESTDIR='' >> LD_LIBRARY_PATH='' >> MACHINE='amd64' >> MACHINE_ARCH='amd64' >> MAKEOBJDIRPREFIX='/usr/obj' >> MAKESYSPATH='/usr/src/share/mk' >> MAKE_VERSION='20181221' >> PATH='/sbin:/bin:/usr/sbin:/usr/bin' >> SRCTOP='/usr/src' >> OBJTOP='/usr/obj/usr/src/amd64.amd64' >> >> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. >> As it has no permission on the NFS share it errors out. >> On the server itself, the installworld goes well, but it leaves a >> sort.core file behind in /usr/share/zoneinfo >> >> cd /usr/share/zoneinfo >> ls -al >> >> From owner-freebsd-current@freebsd.org Fri Apr 17 01:32:01 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 65E5E2CD484 for ; Fri, 17 Apr 2020 01:32:01 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493JV83BDjz4MnH for ; Fri, 17 Apr 2020 01:32:00 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 03H1Vv4D048301; Thu, 16 Apr 2020 18:31:57 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 03H1VvSX048300; Thu, 16 Apr 2020 18:31:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202004170131.03H1VvSX048300@gndrsh.dnsmgr.net> Subject: Re: sort.core error doing installworld on Current. In-Reply-To: To: Kevin Oberman Date: Thu, 16 Apr 2020 18:31:57 -0700 (PDT) CC: Johan Hendriks , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 493JV83BDjz4MnH X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [1.85 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.21)[0.214,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.05)]; NEURAL_SPAM_LONG(0.70)[0.702,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 01:32:01 -0000 > On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: > > > So you some how had a sort core dump sitting in > > /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how > > did get there? I'd take a look at the date on the file and, it it is older > > than the buildworld, just assume that it was left-over garbage. In either > > case, you can delete it and do another installworld. > > > > That should most likely fix things, but, if the buildworld or installworld > > had a crash of sort(1) that left the file, further investigation might be > > needed. Re-making the zoneinfo would help track it down should this be a re > > al bug, but it's my uneducated guess that it's not. > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkoberman@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > Please forgive that awful post! I missed a part of your message by laziness. > > It's odd that the error of sort(1) crashing was not caught by the script. Yes, that is a Makefile flaw someplace. Further there must be a wildcard being used to decide which files to install, that is a further Makefile flaw. Wildcards should NOT be used in the source of an install list, exactly because of this type of cruft that can be dropped in an obj dir. > Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch > something. Looking at the core might tell you which "sort" was involved... > the one you just built or the one in the base system. This could be just a > FOTU, but I would not bet on it. I suspect a recent zoneinfo commit as the root cause. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > > > > > > On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks > > wrote: > > > >> I have a machine running FreeBSD head. > >> rev 13.0-CURRENT #11 r360008 > >> > >> This is a quite powerful machine, so i thought it was a good idea to let > >> that server do the build and for my virtualbox machine i can use the > >> powerful machine to do a installword over NFS. > >> > >> But when i did the make installworld step the client so to say gives an > >> error. > >> > >> install -o root -g wheel -m 444 > >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu > >> /usr/share/zoneinfo/Zulu > >> install -o root -g wheel -m 444 > >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules > >> /usr/share/zoneinfo/posixrules > >> install -o root -g wheel -m 444 > >> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core > >> /usr/share/zoneinfo/sort.core > >> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: > >> Permission denied > >> *** Error code 71 > >> > >> Stop. > >> bmake[5]: stopped in /usr/src/share/zoneinfo > >> *** Error code 1 > >> > >> Stop. > >> bmake[4]: stopped in /usr/src/share > >> *** Error code 1 > >> > >> Stop. > >> bmake[3]: stopped in /usr/src > >> *** Error code 1 > >> > >> Stop. > >> bmake[2]: stopped in /usr/src > >> *** Error code 1 > >> > >> Stop. > >> bmake[1]: stopped in /usr/src > >> *** Error code 1 > >> > >> Stop. > >> make: stopped in /usr/src > >> .ERROR_TARGET='installworld' > >> .ERROR_META_FILE='' > >> .MAKE.LEVEL='0' > >> MAKEFILE='' > >> .MAKE.MODE='normal' > >> _ERROR_CMD='.PHONY' > >> .CURDIR='/usr/src' > >> .MAKE='make' > >> .OBJDIR='/usr/obj/usr/src/amd64.amd64' > >> .TARGETS='installworld' > >> DESTDIR='' > >> LD_LIBRARY_PATH='' > >> MACHINE='amd64' > >> MACHINE_ARCH='amd64' > >> MAKEOBJDIRPREFIX='/usr/obj' > >> MAKESYSPATH='/usr/src/share/mk' > >> MAKE_VERSION='20181221' > >> PATH='/sbin:/bin:/usr/sbin:/usr/bin' > >> SRCTOP='/usr/src' > >> OBJTOP='/usr/obj/usr/src/amd64.amd64' > >> > >> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. > >> As it has no permission on the NFS share it errors out. > >> On the server itself, the installworld goes well, but it leaves a > >> sort.core file behind in /usr/share/zoneinfo > >> > >> cd /usr/share/zoneinfo > >> ls -al > >> > >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Fri Apr 17 10:24: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 ABF102B264B for ; Fri, 17 Apr 2020 10:24:46 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493XJs30vqz4tcJ for ; Fri, 17 Apr 2020 10:24:45 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wm1-x32d.google.com with SMTP id y24so2416583wma.4 for ; Fri, 17 Apr 2020 03:24:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Spvb0e4CEMW7CQ4rHn5evpvSIGifKj4EQNlmFSiSkMY=; b=ed1+ZM+OaDhJgQbSKm0TCoIlbZE7OsFGL6V7MpIs4+7SWvnZwngPnrvXo1qlVP+zPX y88OTkkmcgvyqt4FYcJ4Doi6Mu7z0w1Y0AG2qIFl1nGw+Ej/xdzWtGVbNcRmXOz/kLgB BhRuNTGuVknYD4CQnqij2NgSoxPr9y4iwPCye/uGu/TUstlheK1LEtMQHfuWee9Dw3Kk UBS7KX5hPtZkX0nuffbkRo9Prose8KT+qLbGtHSDKnltkKLkhkL52V7fk+5NiQWqC8SM l/+vzypS02RWZRNxgVq5I3wq5h+MUhUFAEvJpiVCT7mOIPPJpsggtpym1QHn6ib68fmZ 5Dlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Spvb0e4CEMW7CQ4rHn5evpvSIGifKj4EQNlmFSiSkMY=; b=mdiVpTp6TRyL8ZSK9HFlB8nmUKSO4W1hgMUaKk7JYtDPokDXNRaGSE+a6SucQAzi5e Qc5VGGA2pMfUSLKka7KVrgjqUN5iKKuj047oulaYpwUZXf+9TSBAEVlYnJYsnm/Rm/cD kR5DRB34RnCThOFj3DLdHac7mCSPFSEqepZ+gmlL3d+WKBKWSoa2W92Qbo+ySPmfF1wi bCdXuBA2rR+Mg1ORusHNqxQoRcj0Dpm1HHNiDALCcl8aDFIxZrOYu2vgERPC7TaJ3HnK d03tdtVR1mzhI2thAOCZ0aJXVnAt72DcZcYiD0xwU9EcGyPGrrYNMWez5L2hthmeEk9A zKpw== X-Gm-Message-State: AGi0PuY6rGBvD0v2bg1ykf98tEHI1zT6agPu9EspoL0TT0ReNxmtdGyr Cy3CNodoLXLAuzNlYf8vGkEWhiV9GiE= X-Google-Smtp-Source: APiQypIZ655NjFwwOOJft4/sXwJgXfTm3DN2JpsZzenB4Jmi4e4ao3S1bCDNNbZnj3mJgAtekL1TSw== X-Received: by 2002:a1c:492:: with SMTP id 140mr2807410wme.9.1587119083338; Fri, 17 Apr 2020 03:24:43 -0700 (PDT) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id t2sm7226119wmt.15.2020.04.17.03.24.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Apr 2020 03:24:42 -0700 (PDT) Subject: Re: sort.core error doing installworld on Current. To: freebsd-current@freebsd.org References: <202004170131.03H1VvSX048300@gndrsh.dnsmgr.net> From: Johan Hendriks Message-ID: <6a8ef2da-de41-446a-2a85-abf632b72ecd@gmail.com> Date: Fri, 17 Apr 2020 12:24:41 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <202004170131.03H1VvSX048300@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl X-Rspamd-Queue-Id: 493XJs30vqz4tcJ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ed1+ZM+O; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johhendriks@gmail.com designates 2a00:1450:4864:20::32d as permitted sender) smtp.mailfrom=johhendriks@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.10), ipnet: 2a00:1450::/32(-2.35), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[d.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 10:24:46 -0000 Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: >> On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: >> >>> So you some how had a sort core dump sitting in >>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how >>> did get there? I'd take a look at the date on the file and, it it is older >>> than the buildworld, just assume that it was left-over garbage. In either >>> case, you can delete it and do another installworld. >>> >>> That should most likely fix things, but, if the buildworld or installworld >>> had a crash of sort(1) that left the file, further investigation might be >>> needed. Re-making the zoneinfo would help track it down should this be a re >>> al bug, but it's my uneducated guess that it's not. >>> -- >>> Kevin Oberman, Part time kid herder and retired Network Engineer >>> E-mail: rkoberman@gmail.com >>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>> >> Please forgive that awful post! I missed a part of your message by laziness. >> >> It's odd that the error of sort(1) crashing was not caught by the script. > Yes, that is a Makefile flaw someplace. > Further there must be a wildcard being used to decide which files to > install, that is a further Makefile flaw. Wildcards should NOT be used > in the source of an install list, exactly because of this type of cruft > that can be dropped in an obj dir. > >> Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch >> something. Looking at the core might tell you which "sort" was involved... >> the one you just built or the one in the base system. This could be just a >> FOTU, but I would not bet on it. > I suspect a recent zoneinfo commit as the root cause. > I have no idea how to bypass this issue. I have used sort from the latest snapshot and placed that file on the system and in the build dir, but i keep getting the core How can i test an build and install part for zoneinfo If i go into the dir /usr/src/share/zoneinfo and do make install it does not work, do i need to add something? Thank you both for your time >> -- >> Kevin Oberman, Part time kid herder and retired Network Engineer >> E-mail: rkoberman@gmail.com >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >> >> >>> >>> On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks >>> wrote: >>> >>>> I have a machine running FreeBSD head. >>>> rev 13.0-CURRENT #11 r360008 >>>> >>>> This is a quite powerful machine, so i thought it was a good idea to let >>>> that server do the build and for my virtualbox machine i can use the >>>> powerful machine to do a installword over NFS. >>>> >>>> But when i did the make installworld step the client so to say gives an >>>> error. >>>> >>>> install -o root -g wheel -m 444 >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu >>>> /usr/share/zoneinfo/Zulu >>>> install -o root -g wheel -m 444 >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules >>>> /usr/share/zoneinfo/posixrules >>>> install -o root -g wheel -m 444 >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core >>>> /usr/share/zoneinfo/sort.core >>>> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: >>>> Permission denied >>>> *** Error code 71 >>>> >>>> Stop. >>>> bmake[5]: stopped in /usr/src/share/zoneinfo >>>> *** Error code 1 >>>> >>>> Stop. >>>> bmake[4]: stopped in /usr/src/share >>>> *** Error code 1 >>>> >>>> Stop. >>>> bmake[3]: stopped in /usr/src >>>> *** Error code 1 >>>> >>>> Stop. >>>> bmake[2]: stopped in /usr/src >>>> *** Error code 1 >>>> >>>> Stop. >>>> bmake[1]: stopped in /usr/src >>>> *** Error code 1 >>>> >>>> Stop. >>>> make: stopped in /usr/src >>>> .ERROR_TARGET='installworld' >>>> .ERROR_META_FILE='' >>>> .MAKE.LEVEL='0' >>>> MAKEFILE='' >>>> .MAKE.MODE='normal' >>>> _ERROR_CMD='.PHONY' >>>> .CURDIR='/usr/src' >>>> .MAKE='make' >>>> .OBJDIR='/usr/obj/usr/src/amd64.amd64' >>>> .TARGETS='installworld' >>>> DESTDIR='' >>>> LD_LIBRARY_PATH='' >>>> MACHINE='amd64' >>>> MACHINE_ARCH='amd64' >>>> MAKEOBJDIRPREFIX='/usr/obj' >>>> MAKESYSPATH='/usr/src/share/mk' >>>> MAKE_VERSION='20181221' >>>> PATH='/sbin:/bin:/usr/sbin:/usr/bin' >>>> SRCTOP='/usr/src' >>>> OBJTOP='/usr/obj/usr/src/amd64.amd64' >>>> >>>> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. >>>> As it has no permission on the NFS share it errors out. >>>> On the server itself, the installworld goes well, but it leaves a >>>> sort.core file behind in /usr/share/zoneinfo >>>> >>>> cd /usr/share/zoneinfo >>>> ls -al >>>> >>>> >> _______________________________________________ >> 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 Fri Apr 17 10:36:22 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 734C92B2D80 for ; Fri, 17 Apr 2020 10:36:22 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 493XZG0DNQz4vJ8 for ; Fri, 17 Apr 2020 10:36:22 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.nyi.freebsd.org (Postfix) id 07C0A2B2D7F; Fri, 17 Apr 2020 10:36:22 +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 078492B2D7E for ; Fri, 17 Apr 2020 10:36:22 +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) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493XZD2jFxz4vJ7 for ; Fri, 17 Apr 2020 10:36:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id 03HAaIZu060398; Fri, 17 Apr 2020 10:36:18 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id 03HAaITQ060397; Fri, 17 Apr 2020 03:36:18 -0700 (PDT) (envelope-from david) Date: Fri, 17 Apr 2020 03:36:17 -0700 From: David Wolfskill To: Johan Hendriks Cc: current@freebsd.org Subject: Re: sort.core error doing installworld on Current. Message-ID: <20200417103617.GI1253@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Johan Hendriks References: <202004170131.03H1VvSX048300@gndrsh.dnsmgr.net> <6a8ef2da-de41-446a-2a85-abf632b72ecd@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="+p4NvxO1ICbi3VNc" Content-Disposition: inline In-Reply-To: <6a8ef2da-de41-446a-2a85-abf632b72ecd@gmail.com> X-Rspamd-Queue-Id: 493XZD2jFxz4vJ7 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 107.204.234.170 as permitted sender) smtp.mailfrom=david@catwhisker.org X-Spamd-Result: default: False [-7.08 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[current@freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170]; IP_SCORE(-2.68)[ip: (-9.73), ipnet: 107.192.0.0/12(-4.86), asn: 7018(1.24), country: US(-0.05)]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[catwhisker.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; 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]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 10:36:22 -0000 --+p4NvxO1ICbi3VNc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 17, 2020 at 12:24:41PM +0200, Johan Hendriks wrote: >=20 > Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: > .... > I have no idea how to bypass this issue. > .... Sorry; I was busy with work stuff when your original post came by. IIRC, you had several system components excluded from building (on your build machine); do you also have them excluded on the target machine(s)? That is, /etc/src.conf on each target machines needs to specify (the installation of) no more than what was built on the build machine. I have been doing this (bild on a more pawerful machine; mount on less-powerful machine via NFS; install) routinely (every Sunday) for the last several years; it's when I have managed to neglect to ensure the above property that I have encountered such "weirdness." Ref. http://www.catwhisker.org/~david/FreeBSD/upgrade.html Peace and good health, david --=20 David H. Wolfskill david@catwhisker.org Please read https://www.speaker.gov/newsroom/41420-0 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --+p4NvxO1ICbi3VNc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl6ZhqFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 Pck3Pgf/TDGjFN9HMQXjlWPr47W8TWyNaaCR98b4vsJtqeeIyLSWwWspL0gOtd+u JYgRUVMup1nBhvb3JK13lkpj8CQJa+fMt05iz/uivBYHJphUxOSVb6tw1xdQ5Csx TvTmN1i1Na2i2GAW8DJR7fcXZfH09bB85WNSQla9F9aqQUSQjrObRDpaKTwZkKe6 VPnAtmXgHeEaKQprdjfKTtAgUuOKDV4yQGuHhcyRoE+CQqbUNeoc9VQMf3EPSVVG +gR6XyyvrlPdwwH8ECrt9ffBEdoYWP6FUDOwE8+81fnQPBf/zjU0oSUN+96qCid5 A6wKyPRaSXv1GzJTbFq48RoXFsR+zg== =NeHr -----END PGP SIGNATURE----- --+p4NvxO1ICbi3VNc-- From owner-freebsd-current@freebsd.org Fri Apr 17 10:38:00 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 A54F32B3088 for ; Fri, 17 Apr 2020 10:38:00 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493Xc73tjVz4vb9 for ; Fri, 17 Apr 2020 10:37:59 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 03HAbuFU050130; Fri, 17 Apr 2020 03:37:56 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 03HAbuYw050129; Fri, 17 Apr 2020 03:37:56 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202004171037.03HAbuYw050129@gndrsh.dnsmgr.net> Subject: Re: sort.core error doing installworld on Current. In-Reply-To: <6a8ef2da-de41-446a-2a85-abf632b72ecd@gmail.com> To: Johan Hendriks Date: Fri, 17 Apr 2020 03:37:56 -0700 (PDT) CC: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 493Xc73tjVz4vb9 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [2.01 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.05)]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.32)[0.320,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.76)[0.756,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 10:38:00 -0000 > > Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: > >> On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: > >> > >>> So you some how had a sort core dump sitting in > >>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how > >>> did get there? I'd take a look at the date on the file and, it it is older > >>> than the buildworld, just assume that it was left-over garbage. In either > >>> case, you can delete it and do another installworld. > >>> > >>> That should most likely fix things, but, if the buildworld or installworld > >>> had a crash of sort(1) that left the file, further investigation might be > >>> needed. Re-making the zoneinfo would help track it down should this be a re > >>> al bug, but it's my uneducated guess that it's not. > >>> -- > >>> Kevin Oberman, Part time kid herder and retired Network Engineer > >>> E-mail: rkoberman@gmail.com > >>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > >>> > >> Please forgive that awful post! I missed a part of your message by laziness. > >> > >> It's odd that the error of sort(1) crashing was not caught by the script. > > Yes, that is a Makefile flaw someplace. > > Further there must be a wildcard being used to decide which files to > > install, that is a further Makefile flaw. Wildcards should NOT be used > > in the source of an install list, exactly because of this type of cruft > > that can be dropped in an obj dir. > > > >> Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch > >> something. Looking at the core might tell you which "sort" was involved... > >> the one you just built or the one in the base system. This could be just a > >> FOTU, but I would not bet on it. > > I suspect a recent zoneinfo commit as the root cause. > > > I have no idea how to bypass this issue. > I have used sort from the latest snapshot and placed that file on the > system and in the build dir, but i keep getting the core > > How can i test an build and install part for zoneinfo > > If i go into the dir /usr/src/share/zoneinfo and do make install it does > not work, do i need to add something? Can you show us the output from cd /usr/src/share/zoneinfo make clean && make depend && make all && make install Someplace in that we should get to see sort crashing... > > Thank you both for your time > > >> -- > >> Kevin Oberman, Part time kid herder and retired Network Engineer > >> E-mail: rkoberman@gmail.com > >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > >> > >> > >>> > >>> On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks > >>> wrote: > >>> > >>>> I have a machine running FreeBSD head. > >>>> rev 13.0-CURRENT #11 r360008 > >>>> > >>>> This is a quite powerful machine, so i thought it was a good idea to let > >>>> that server do the build and for my virtualbox machine i can use the > >>>> powerful machine to do a installword over NFS. > >>>> > >>>> But when i did the make installworld step the client so to say gives an > >>>> error. > >>>> > >>>> install -o root -g wheel -m 444 > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu > >>>> /usr/share/zoneinfo/Zulu > >>>> install -o root -g wheel -m 444 > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules > >>>> /usr/share/zoneinfo/posixrules > >>>> install -o root -g wheel -m 444 > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core > >>>> /usr/share/zoneinfo/sort.core > >>>> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: > >>>> Permission denied > >>>> *** Error code 71 > >>>> > >>>> Stop. > >>>> bmake[5]: stopped in /usr/src/share/zoneinfo > >>>> *** Error code 1 > >>>> > >>>> Stop. > >>>> bmake[4]: stopped in /usr/src/share > >>>> *** Error code 1 > >>>> > >>>> Stop. > >>>> bmake[3]: stopped in /usr/src > >>>> *** Error code 1 > >>>> > >>>> Stop. > >>>> bmake[2]: stopped in /usr/src > >>>> *** Error code 1 > >>>> > >>>> Stop. > >>>> bmake[1]: stopped in /usr/src > >>>> *** Error code 1 > >>>> > >>>> Stop. > >>>> make: stopped in /usr/src > >>>> .ERROR_TARGET='installworld' > >>>> .ERROR_META_FILE='' > >>>> .MAKE.LEVEL='0' > >>>> MAKEFILE='' > >>>> .MAKE.MODE='normal' > >>>> _ERROR_CMD='.PHONY' > >>>> .CURDIR='/usr/src' > >>>> .MAKE='make' > >>>> .OBJDIR='/usr/obj/usr/src/amd64.amd64' > >>>> .TARGETS='installworld' > >>>> DESTDIR='' > >>>> LD_LIBRARY_PATH='' > >>>> MACHINE='amd64' > >>>> MACHINE_ARCH='amd64' > >>>> MAKEOBJDIRPREFIX='/usr/obj' > >>>> MAKESYSPATH='/usr/src/share/mk' > >>>> MAKE_VERSION='20181221' > >>>> PATH='/sbin:/bin:/usr/sbin:/usr/bin' > >>>> SRCTOP='/usr/src' > >>>> OBJTOP='/usr/obj/usr/src/amd64.amd64' > >>>> > >>>> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. > >>>> As it has no permission on the NFS share it errors out. > >>>> On the server itself, the installworld goes well, but it leaves a > >>>> sort.core file behind in /usr/share/zoneinfo > >>>> > >>>> cd /usr/share/zoneinfo > >>>> ls -al > >>>> > >>>> > >> _______________________________________________ > >> 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" > >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Fri Apr 17 10:47: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 6A9752B358F for ; Fri, 17 Apr 2020 10:47:19 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493Xpt1hX5z3C4D for ; Fri, 17 Apr 2020 10:47:17 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 03HAlFCD050162; Fri, 17 Apr 2020 03:47:15 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 03HAlFk6050161; Fri, 17 Apr 2020 03:47:15 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202004171047.03HAlFk6050161@gndrsh.dnsmgr.net> Subject: Re: sort.core error doing installworld on Current. In-Reply-To: <202004171037.03HAbuYw050129@gndrsh.dnsmgr.net> To: "Rodney W. Grimes" Date: Fri, 17 Apr 2020 03:47:15 -0700 (PDT) CC: Johan Hendriks , freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 493Xpt1hX5z3C4D X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [1.84 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.21)[0.212,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.05)]; NEURAL_SPAM_LONG(0.70)[0.698,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 10:47:19 -0000 > > > > Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: > > >> On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: > > >> > > >>> So you some how had a sort core dump sitting in > > >>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how > > >>> did get there? I'd take a look at the date on the file and, it it is older > > >>> than the buildworld, just assume that it was left-over garbage. In either > > >>> case, you can delete it and do another installworld. > > >>> > > >>> That should most likely fix things, but, if the buildworld or installworld > > >>> had a crash of sort(1) that left the file, further investigation might be > > >>> needed. Re-making the zoneinfo would help track it down should this be a re > > >>> al bug, but it's my uneducated guess that it's not. > > >>> -- > > >>> Kevin Oberman, Part time kid herder and retired Network Engineer > > >>> E-mail: rkoberman@gmail.com > > >>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > >>> > > >> Please forgive that awful post! I missed a part of your message by laziness. > > >> > > >> It's odd that the error of sort(1) crashing was not caught by the script. > > > Yes, that is a Makefile flaw someplace. > > > Further there must be a wildcard being used to decide which files to > > > install, that is a further Makefile flaw. Wildcards should NOT be used > > > in the source of an install list, exactly because of this type of cruft > > > that can be dropped in an obj dir. >From src/share/zoneinfo/Makefile at about line 93: 92 if make(*install*) 93 TZS!= cd ${TZBUILDDIR} && find * -type f | LC_ALL=C sort ^^^^ this is a very bad thing to do in a Makefile. 94 .endif Now I still don't know why sort cored, but I am sure this is the line that did it. > > > > > >> Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch > > >> something. Looking at the core might tell you which "sort" was involved... > > >> the one you just built or the one in the base system. This could be just a > > >> FOTU, but I would not bet on it. > > > I suspect a recent zoneinfo commit as the root cause. > > > > > I have no idea how to bypass this issue. > > I have used sort from the latest snapshot and placed that file on the > > system and in the build dir, but i keep getting the core > > > > How can i test an build and install part for zoneinfo > > > > If i go into the dir /usr/src/share/zoneinfo and do make install it does > > not work, do i need to add something? > > Can you show us the output from > cd /usr/src/share/zoneinfo > make clean && make depend && make all && make install > Someplace in that we should get to see sort crashing... > > > > > Thank you both for your time > > > > >> -- > > >> Kevin Oberman, Part time kid herder and retired Network Engineer > > >> E-mail: rkoberman@gmail.com > > >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > >> > > >> > > >>> > > >>> On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks > > >>> wrote: > > >>> > > >>>> I have a machine running FreeBSD head. > > >>>> rev 13.0-CURRENT #11 r360008 > > >>>> > > >>>> This is a quite powerful machine, so i thought it was a good idea to let > > >>>> that server do the build and for my virtualbox machine i can use the > > >>>> powerful machine to do a installword over NFS. > > >>>> > > >>>> But when i did the make installworld step the client so to say gives an > > >>>> error. > > >>>> > > >>>> install -o root -g wheel -m 444 > > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu > > >>>> /usr/share/zoneinfo/Zulu > > >>>> install -o root -g wheel -m 444 > > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules > > >>>> /usr/share/zoneinfo/posixrules > > >>>> install -o root -g wheel -m 444 > > >>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core > > >>>> /usr/share/zoneinfo/sort.core > > >>>> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: > > >>>> Permission denied > > >>>> *** Error code 71 > > >>>> > > >>>> Stop. > > >>>> bmake[5]: stopped in /usr/src/share/zoneinfo > > >>>> *** Error code 1 > > >>>> > > >>>> Stop. > > >>>> bmake[4]: stopped in /usr/src/share > > >>>> *** Error code 1 > > >>>> > > >>>> Stop. > > >>>> bmake[3]: stopped in /usr/src > > >>>> *** Error code 1 > > >>>> > > >>>> Stop. > > >>>> bmake[2]: stopped in /usr/src > > >>>> *** Error code 1 > > >>>> > > >>>> Stop. > > >>>> bmake[1]: stopped in /usr/src > > >>>> *** Error code 1 > > >>>> > > >>>> Stop. > > >>>> make: stopped in /usr/src > > >>>> .ERROR_TARGET='installworld' > > >>>> .ERROR_META_FILE='' > > >>>> .MAKE.LEVEL='0' > > >>>> MAKEFILE='' > > >>>> .MAKE.MODE='normal' > > >>>> _ERROR_CMD='.PHONY' > > >>>> .CURDIR='/usr/src' > > >>>> .MAKE='make' > > >>>> .OBJDIR='/usr/obj/usr/src/amd64.amd64' > > >>>> .TARGETS='installworld' > > >>>> DESTDIR='' > > >>>> LD_LIBRARY_PATH='' > > >>>> MACHINE='amd64' > > >>>> MACHINE_ARCH='amd64' > > >>>> MAKEOBJDIRPREFIX='/usr/obj' > > >>>> MAKESYSPATH='/usr/src/share/mk' > > >>>> MAKE_VERSION='20181221' > > >>>> PATH='/sbin:/bin:/usr/sbin:/usr/bin' > > >>>> SRCTOP='/usr/src' > > >>>> OBJTOP='/usr/obj/usr/src/amd64.amd64' > > >>>> > > >>>> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. > > >>>> As it has no permission on the NFS share it errors out. > > >>>> On the server itself, the installworld goes well, but it leaves a > > >>>> sort.core file behind in /usr/share/zoneinfo > > >>>> > > >>>> cd /usr/share/zoneinfo > > >>>> ls -al > > >>>> > > >>>> > > >> _______________________________________________ > > >> 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" > > >> > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Fri Apr 17 11:23:09 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 9160F2B537F for ; Fri, 17 Apr 2020 11:23:09 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493YcD4gmsz3GcJ for ; Fri, 17 Apr 2020 11:23:08 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id BA3C128432 for ; Fri, 17 Apr 2020 13:23:06 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2BD8C28434 for ; Fri, 17 Apr 2020 13:23:05 +0200 (CEST) From: Miroslav Lachman <000.fbsd@quip.cz> Subject: PCIe NVME drives not detected on Dell R6515 To: FreeBSD-Current Message-ID: Date: Fri, 17 Apr 2020 13:23:04 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 493YcD4gmsz3GcJ X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.82)[ip: (0.27), ipnet: 94.124.104.0/21(0.14), asn: 42000(3.59), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.987,0]; NEURAL_SPAM_LONG(1.00)[1.000,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 11:23:09 -0000 I already asked on stable@ but as I tried it on 13-CURRENT with the same result I am trying to ask for help here. I have rented dedicated server Dell PowerEdge R6515 with iDRAC access only. There are 2 NVME drives which I wanted to use as ZFS root pool. They are shown in iDRAC Device Description: PCIe SSD in Slot 1 in Bay 1 Device Protocol: NVMe-MI1.0 Model: Dell Express Flash NVMe P4510 1TB SFF Bus: 130 Manufacturer: INTEL Product ID: a54 Revision: VDV1DP23 Enclosure: PCIe SSD Backplane 1 pciconf -l show many things, some of them are named "noneN@pci..." but none "nvme" The is printscreen (12.1 but 13-CURRENT is the same) https://ibb.co/tPnymL7 But I booted Linux SystemRescueCd and nvme devices are there visible in /dev/ https://ibb.co/sj22Nwg There is verbose output of Linux lspci https://ibb.co/dPZTwV1 Linux dmesg contains: nvme nvme0: pci function 0000:81:00.0 nvme nvme1: pci function 0000:82:00.0 nvme nvme0: 32/0/0 default/read/poll queues nvme nvme1: 32/0/0 default/read/poll queues The machine is Dell PowerEdge R6515 with AMD EPYC 7302P More details extracted from iDRAC web interface I found this informations PCIe SSD in Slot 1 in Bay 1 Bus: 82 BusProtocol: PCIE Device: 0 DeviceDescription: PCIe SSD in Slot 1 in Bay 1 DeviceProtocol: NVMe-MI1.0 DeviceType: PCIeSSD DriveFormFactor: 2.5 inch FailurePredicted: NO FQDD: Disk.Bay.1:Enclosure.Internal.0-1 FreeSizeInBytes: Information Not Available Function: 0 HotSpareStatus: Information Not Available InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 Manufacturer: INTEL MaximumCapableSpeed: 8 GT/s MediaType: Solid State Drive Model: Dell Express Flash NVMe P4510 1TB SFF NegotiatedSpeed: 8 GT/s PCIeCapableLinkWidth: x4 PCIeNegotiatedLinkWidth: x4 PrimaryStatus: Ok ProductID: a54 RaidStatus: Information Not Available RAIDType: Unknown RemainingRatedWriteEndurance: 100 % Revision: VDV1DP23 SerialNumber: PHLJxxxxxxWF1PxxxxN SizeInBytes: 1000204886016 Slot: 1 State: Ready SystemEraseCapability: CryptographicErasePD PCIe SSD in Slot 1 in Bay 1 - PCI Device BusNumber: 130 DataBusWidth: 4x or x4 Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) DeviceDescription: PCIe SSD in Slot 1 in Bay 1 DeviceNumber: 0 DeviceType: PCIDevice FQDD: Disk.Bay.1:Enclosure.Internal.0-1 FunctionNumber: 0 InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 LastSystemInventoryTime: 2020-04-17T03:21:39 LastUpdateTime: 2020-03-31T13:55:06 Manufacturer: Intel Corporation PCIDeviceID: 0A54 PCISubDeviceID: 2003 PCISubVendorID: 1028 PCIVendorID: 8086 SlotLength: 2.5 Inch Drive Form Factor SlotType: PCI Express Gen 3 SFF-8639 Can anybody shed some light what the real problem is? Is the hardware not properly detected or is the driver completely missing? NVME PCIe architecture is out of my knowledge. I really appreciate any help. Kind regards Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 11:30: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 613412B5692 for ; Fri, 17 Apr 2020 11:30:55 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493YnB1fBSz3Gvj for ; Fri, 17 Apr 2020 11:30:54 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wr1-x42a.google.com with SMTP id k1so2657561wrx.4 for ; Fri, 17 Apr 2020 04:30:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=8Qon0bjt5vNoxSEsszHNbwNEOCNLitfka6FsEqq7rgM=; b=V7WdtxgVQKwlw/aPF4BfOPyrwrMnkH4RdLQc/bA3Y1OJfpNgixXDwqadrOJIBnTkSg Ny8Ak2p4qxzobp3u5Wwk3eP4JtOOmu2Z/BDYSG37eSJ7EcK/CxafcTNfLCoZMyrMpcH1 EGy7T72es3LXl9owALs2zLjh4m9YXCAIVmr/d1HMvgtqGcAR0w+94OvaFTr92jbUPFEJ 4dn/f7Zg+wZKMmZh9aqSsHIrDN58DiGMOOjFoWg4Cy/wWwejn8hjac2y9T5sobPUQwSZ M3JPx+Te3rGPY9Jp6LMg2YfYx6M+d/7LOgo5KXCO+7WPYwK9vKDdSEGeZ0fH3YZDtW/3 VMyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=8Qon0bjt5vNoxSEsszHNbwNEOCNLitfka6FsEqq7rgM=; b=H0WW7BR5YgsGarjmzQX1yEnTkh7O7Z9xFnCiew624vpPgaUiI7pstQ75OqM5hroEUo x2Y79mbY/4opuSffPDKRUWvcV0ELjnJu/l0XXLAQvdlrEArfSJCHQ6S7ij/jyxzpQYGW VgM/2CphWZNhx25Yw0mvxQ7SgJ33mzX1PlWBFrOtiFvDg3Kp7+2NHaRKcekBe7g2iinK ndAKpl1C1Z3xx3DVBcoYX0ZR+IeKhHhFy7Awto+1fBtmICdh8CzaD1sHLz3ZQgZWMXN+ gGu1veGX6JlxOosvPHXrFTkYjM7g0gCV4jjYyL1Nu08FmB/hZwm6kc6xx2V9kwPi2ENq eKjg== X-Gm-Message-State: AGi0Pua6ZgnTZV8yxHAonklx2RW9WWNYBqqOqrzIqbAO09ejy5S3yMTP aikJJnTWtmrNYQocuheeUK0uUlizMnU= X-Google-Smtp-Source: APiQypKpY48oJmr2eG1LmNb/jPN/PPAcCR8k5ASB83AgCuSw3vjIXJRQMge16FqgV6fvcefm9zUZYg== X-Received: by 2002:a5d:4b90:: with SMTP id b16mr3699041wrt.16.1587123052365; Fri, 17 Apr 2020 04:30:52 -0700 (PDT) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id r2sm7602872wmg.2.2020.04.17.04.30.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Apr 2020 04:30:51 -0700 (PDT) Subject: Re: sort.core error doing installworld on Current. To: freebsd-current@freebsd.org References: <202004171047.03HAlFk6050161@gndrsh.dnsmgr.net> From: Johan Hendriks Message-ID: Date: Fri, 17 Apr 2020 13:30:49 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <202004171047.03HAlFk6050161@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl X-Rspamd-Queue-Id: 493YnB1fBSz3Gvj X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=V7WdtxgV; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johhendriks@gmail.com designates 2a00:1450:4864:20::42a as permitted sender) smtp.mailfrom=johhendriks@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.31), ipnet: 2a00:1450::/32(-2.35), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[a.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 11:30:55 -0000 Op 17-04-2020 om 12:47 schreef Rodney W. Grimes: >>> Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: >>>>> On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman wrote: >>>>> >>>>>> So you some how had a sort core dump sitting in >>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The questions, how >>>>>> did get there? I'd take a look at the date on the file and, it it is older >>>>>> than the buildworld, just assume that it was left-over garbage. In either >>>>>> case, you can delete it and do another installworld. >>>>>> >>>>>> That should most likely fix things, but, if the buildworld or installworld >>>>>> had a crash of sort(1) that left the file, further investigation might be >>>>>> needed. Re-making the zoneinfo would help track it down should this be a re >>>>>> al bug, but it's my uneducated guess that it's not. >>>>>> -- >>>>>> Kevin Oberman, Part time kid herder and retired Network Engineer >>>>>> E-mail: rkoberman@gmail.com >>>>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>>>>> >>>>> Please forgive that awful post! I missed a part of your message by laziness. >>>>> >>>>> It's odd that the error of sort(1) crashing was not caught by the script. >>>> Yes, that is a Makefile flaw someplace. >>>> Further there must be a wildcard being used to decide which files to >>>> install, that is a further Makefile flaw. Wildcards should NOT be used >>>> in the source of an install list, exactly because of this type of cruft >>>> that can be dropped in an obj dir. > From src/share/zoneinfo/Makefile at about line 93: > 92 if make(*install*) > 93 TZS!= cd ${TZBUILDDIR} && find * -type f | LC_ALL=C sort > ^^^^ this is a very bad thing to do in a Makefile. > > 94 .endif > > Now I still don't know why sort cored, but I am sure this is the line that did it. > >>>>> Clearly, sort should NOT crash! Again, a re-build of zoneinfo might catch >>>>> something. Looking at the core might tell you which "sort" was involved... >>>>> the one you just built or the one in the base system. This could be just a >>>>> FOTU, but I would not bet on it. >>>> I suspect a recent zoneinfo commit as the root cause. >>>> >>> I have no idea how to bypass this issue. >>> I have used sort from the latest snapshot and placed that file on the >>> system and in the build dir, but i keep getting the core >>> >>> How can i test an build and install part for zoneinfo >>> >>> If i go into the dir /usr/src/share/zoneinfo and do make install it does >>> not work, do i need to add something? >> Can you show us the output from >> cd /usr/src/share/zoneinfo >> make clean && make depend && make all && make install >> Someplace in that we should get to see sort crashing... >> On both machines my src.conf file is the same. I will start over from a clean world by doing a make cleanworld and see if it then still gives the errors Maybe some old artifacts are hanging around. >> >>> Thank you both for your time >>> >>>>> -- >>>>> Kevin Oberman, Part time kid herder and retired Network Engineer >>>>> E-mail: rkoberman@gmail.com >>>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>>>> >>>>> >>>>>> On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks >>>>>> wrote: >>>>>> >>>>>>> I have a machine running FreeBSD head. >>>>>>> rev 13.0-CURRENT #11 r360008 >>>>>>> >>>>>>> This is a quite powerful machine, so i thought it was a good idea to let >>>>>>> that server do the build and for my virtualbox machine i can use the >>>>>>> powerful machine to do a installword over NFS. >>>>>>> >>>>>>> But when i did the make installworld step the client so to say gives an >>>>>>> error. >>>>>>> >>>>>>> install -o root -g wheel -m 444 >>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu >>>>>>> /usr/share/zoneinfo/Zulu >>>>>>> install -o root -g wheel -m 444 >>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules >>>>>>> /usr/share/zoneinfo/posixrules >>>>>>> install -o root -g wheel -m 444 >>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core >>>>>>> /usr/share/zoneinfo/sort.core >>>>>>> install: /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: >>>>>>> Permission denied >>>>>>> *** Error code 71 >>>>>>> >>>>>>> Stop. >>>>>>> bmake[5]: stopped in /usr/src/share/zoneinfo >>>>>>> *** Error code 1 >>>>>>> >>>>>>> Stop. >>>>>>> bmake[4]: stopped in /usr/src/share >>>>>>> *** Error code 1 >>>>>>> >>>>>>> Stop. >>>>>>> bmake[3]: stopped in /usr/src >>>>>>> *** Error code 1 >>>>>>> >>>>>>> Stop. >>>>>>> bmake[2]: stopped in /usr/src >>>>>>> *** Error code 1 >>>>>>> >>>>>>> Stop. >>>>>>> bmake[1]: stopped in /usr/src >>>>>>> *** Error code 1 >>>>>>> >>>>>>> Stop. >>>>>>> make: stopped in /usr/src >>>>>>> .ERROR_TARGET='installworld' >>>>>>> .ERROR_META_FILE='' >>>>>>> .MAKE.LEVEL='0' >>>>>>> MAKEFILE='' >>>>>>> .MAKE.MODE='normal' >>>>>>> _ERROR_CMD='.PHONY' >>>>>>> .CURDIR='/usr/src' >>>>>>> .MAKE='make' >>>>>>> .OBJDIR='/usr/obj/usr/src/amd64.amd64' >>>>>>> .TARGETS='installworld' >>>>>>> DESTDIR='' >>>>>>> LD_LIBRARY_PATH='' >>>>>>> MACHINE='amd64' >>>>>>> MACHINE_ARCH='amd64' >>>>>>> MAKEOBJDIRPREFIX='/usr/obj' >>>>>>> MAKESYSPATH='/usr/src/share/mk' >>>>>>> MAKE_VERSION='20181221' >>>>>>> PATH='/sbin:/bin:/usr/sbin:/usr/bin' >>>>>>> SRCTOP='/usr/src' >>>>>>> OBJTOP='/usr/obj/usr/src/amd64.amd64' >>>>>>> >>>>>>> It looks likes sort coredumps in the usr/share/zoneinfo part of the base. >>>>>>> As it has no permission on the NFS share it errors out. >>>>>>> On the server itself, the installworld goes well, but it leaves a >>>>>>> sort.core file behind in /usr/share/zoneinfo >>>>>>> >>>>>>> cd /usr/share/zoneinfo >>>>>>> ls -al >>>>>>> >>>>>>> >>>>> _______________________________________________ >>>>> 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" >>>>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> >> -- >> Rod Grimes rgrimes@freebsd.org >> _______________________________________________ >> 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 Fri Apr 17 14:28:12 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 4F20A2BB3C0 for ; Fri, 17 Apr 2020 14:28:12 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493djk1BBpz40cr for ; Fri, 17 Apr 2020 14:28:09 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id f13so3235736wrm.13 for ; Fri, 17 Apr 2020 07:28:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=h/nKZwSJ0zw5JMxtWleKgcpIZ5lBkiAuEYQS6g5/73A=; b=ML1Q7S4gZI9jhqU29j863/IwGnD8PpK7itxiNCYms8dPaHeq9CRACT2sQZ2JmdiIMy SviEaK2/GENJIYkmGgVmv1I+90V2dIUgpTac1L8amWOPzTV4NykHUwaX3k0b25QNZpGJ P7cgp2WenXnwItaezfXryxp7+ROrR3ofgtKvU80oCFR7yx18+xJia6GEHf82yeT5wL3E ObtptughOQaPpL/SY6yNM6dHKkz7oU577uLOM9zqSzeWT4ya38m99W9MShG1cCpt4OyA +CcpTKGEDlBOdSrlSji3MNwg3u0LPEY4TC+yGBERit+zc69uqUMaRn/htwycRKkCbygK Z5Jg== 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=h/nKZwSJ0zw5JMxtWleKgcpIZ5lBkiAuEYQS6g5/73A=; b=BbQjTtMqKmWD/2pwjev4GbeW6I4NCtjbku3w01LWAqZIk5FwWUAwXxB2qJBl66uh79 3bFLTf3HFWL5Z8tM+q5h1pGOh/L52+U+FKGDR3PY+ybILQM7DSXWI3KIZ2E764fnC8Sm 3oBtcXlwqA41If7CrqfUtN7G7ys30/EQkLJ/IUd8cMs2ExcLhKxSMENCyrL43WvQUXAr +iifzarwu2JOJw1DKGoo4F0NCtxxeEoanCk+Go5+IYpcMooV1g7EY0fZlHI5t5bPrNof DdtgOtgEkUMLwWvTNgbhgKdHAGwskGlZXDtseBK0/MqzX8tjNR7T2GaRObwMJe6XGLAs vfrQ== X-Gm-Message-State: AGi0PuYIhgO0NIQ2ROY2WUln/u+BgnYRPfhLltuKMR8zZvJyTVvIKhEL eWS8Ks50P31KFI0X6dyzk+IzOZB1gdk= X-Google-Smtp-Source: APiQypLikpRZwRyHmWgGUKO5WxiRd14Y2Bpl9SA5P9KsHUHN89MaeEFJBcu3dS07q1d5ftHHGCGWrw== X-Received: by 2002:adf:cc8d:: with SMTP id p13mr4448204wrj.114.1587133687746; Fri, 17 Apr 2020 07:28:07 -0700 (PDT) Received: from MacBook-Pro-van-Johan.local (85-147-130-226.cable.dynamic.v4.ziggo.nl. [85.147.130.226]) by smtp.gmail.com with ESMTPSA id t2sm7994262wmt.15.2020.04.17.07.28.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Apr 2020 07:28:07 -0700 (PDT) Subject: Re: sort.core error doing installworld on Current. From: Johan Hendriks To: freebsd-current@freebsd.org References: <202004171047.03HAlFk6050161@gndrsh.dnsmgr.net> Message-ID: Date: Fri, 17 Apr 2020 16:28:06 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: nl X-Rspamd-Queue-Id: 493djk1BBpz40cr X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ML1Q7S4g; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of johhendriks@gmail.com designates 2a00:1450:4864:20::433 as permitted sender) smtp.mailfrom=johhendriks@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.14), ipnet: 2a00:1450::/32(-2.35), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[3.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 14:28:12 -0000 Op 17-04-2020 om 13:30 schreef Johan Hendriks: > > Op 17-04-2020 om 12:47 schreef Rodney W. Grimes: >>>> Op 17-04-2020 om 03:31 schreef Rodney W. Grimes: >>>>>> On Thu, Apr 16, 2020 at 12:39 PM Kevin Oberman >>>>>> wrote: >>>>>> >>>>>>> So you some how had a sort core dump sitting in >>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir. The >>>>>>> questions, how >>>>>>> did get there? I'd take a look at the date on the file and, it >>>>>>> it is older >>>>>>> than the buildworld, just assume that it was left-over garbage. >>>>>>> In either >>>>>>> case, you can delete it and do another installworld. >>>>>>> >>>>>>> That should most likely fix things, but, if the buildworld or >>>>>>> installworld >>>>>>> had a crash of sort(1) that left the file, further investigation >>>>>>> might be >>>>>>> needed. Re-making the zoneinfo would help track it down should >>>>>>> this be a re >>>>>>> al bug, but it's my uneducated guess that it's not. >>>>>>> -- >>>>>>> Kevin Oberman, Part time kid herder and retired Network Engineer >>>>>>> E-mail: rkoberman@gmail.com >>>>>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>>>>>> >>>>>> Please forgive that awful post! I missed a part of your message >>>>>> by laziness. >>>>>> >>>>>> It's odd that the error of sort(1) crashing was not caught by the >>>>>> script. >>>>> Yes, that is a Makefile flaw someplace. >>>>> Further there must be a wildcard being used to decide which files to >>>>> install, that is a further Makefile flaw.  Wildcards should NOT be >>>>> used >>>>> in the source of an install list, exactly because of this type of >>>>> cruft >>>>> that can be dropped in an obj dir. >>  From src/share/zoneinfo/Makefile at about line 93: >> 92  if make(*install*) >> 93  TZS!= cd ${TZBUILDDIR} && find * -type f | LC_ALL=C sort >>                                   ^^^^ this is a very bad thing to do >> in a Makefile. >> >> 94  .endif >> >> Now I still don't know why sort cored, but I am sure this is the line >> that did it. >> >>>>>> Clearly, sort should NOT crash! Again, a re-build of zoneinfo >>>>>> might catch >>>>>> something. Looking at the core might tell you which "sort" was >>>>>> involved... >>>>>> the one you just built or the one in the base system. This could >>>>>> be just a >>>>>> FOTU, but I would not bet on it. >>>>> I suspect a recent zoneinfo commit as the root cause. >>>>> >>>> I have no idea how to bypass this issue. >>>> I have used sort from the latest snapshot and placed that file on the >>>> system and in the build dir, but i keep getting the core >>>> >>>> How can i test an build and install part for zoneinfo >>>> >>>> If i go into the dir /usr/src/share/zoneinfo and do make install it >>>> does >>>> not work, do i need to add something? >>> Can you show us the output from >>> cd /usr/src/share/zoneinfo >>> make clean && make depend && make all && make install >>> Someplace in that we should get to see sort crashing... >>> > On both machines my src.conf file is the same. > > I will start over from a clean world by doing a make cleanworld and > see if it then still gives the errors > Maybe some old artifacts are hanging around. > > > >>> >>>> Thank you both for your time >>>> >>>>>> -- >>>>>> Kevin Oberman, Part time kid herder and retired Network Engineer >>>>>> E-mail: rkoberman@gmail.com >>>>>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >>>>>> >>>>>> >>>>>>> On Thu, Apr 16, 2020 at 11:49 AM Johan Hendriks >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> I have a machine running FreeBSD head. >>>>>>>> rev 13.0-CURRENT #11 r360008 >>>>>>>> >>>>>>>> This is a quite powerful machine, so i thought it was a good >>>>>>>> idea to let >>>>>>>> that server do the build and for my virtualbox machine i can >>>>>>>> use the >>>>>>>> powerful machine to do a installword over NFS. >>>>>>>> >>>>>>>> But when i did the make installworld step the client so to say >>>>>>>> gives an >>>>>>>> error. >>>>>>>> >>>>>>>> install   -o root -g wheel -m 444 >>>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Zulu >>>>>>>> /usr/share/zoneinfo/Zulu >>>>>>>> install   -o root -g wheel -m 444 >>>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/posixrules >>>>>>>> /usr/share/zoneinfo/posixrules >>>>>>>> install   -o root -g wheel -m 444 >>>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core >>>>>>>> /usr/share/zoneinfo/sort.core >>>>>>>> install: >>>>>>>> /usr/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/sort.core: >>>>>>>> Permission denied >>>>>>>> *** Error code 71 >>>>>>>> >>>>>>>> Stop. >>>>>>>> bmake[5]: stopped in /usr/src/share/zoneinfo >>>>>>>> *** Error code 1 >>>>>>>> >>>>>>>> Stop. >>>>>>>> bmake[4]: stopped in /usr/src/share >>>>>>>> *** Error code 1 >>>>>>>> >>>>>>>> Stop. >>>>>>>> bmake[3]: stopped in /usr/src >>>>>>>> *** Error code 1 >>>>>>>> >>>>>>>> Stop. >>>>>>>> bmake[2]: stopped in /usr/src >>>>>>>> *** Error code 1 >>>>>>>> >>>>>>>> Stop. >>>>>>>> bmake[1]: stopped in /usr/src >>>>>>>> *** Error code 1 >>>>>>>> >>>>>>>> Stop. >>>>>>>> make: stopped in /usr/src >>>>>>>> .ERROR_TARGET='installworld' >>>>>>>> .ERROR_META_FILE='' >>>>>>>> .MAKE.LEVEL='0' >>>>>>>> MAKEFILE='' >>>>>>>> .MAKE.MODE='normal' >>>>>>>> _ERROR_CMD='.PHONY' >>>>>>>> .CURDIR='/usr/src' >>>>>>>> .MAKE='make' >>>>>>>> .OBJDIR='/usr/obj/usr/src/amd64.amd64' >>>>>>>> .TARGETS='installworld' >>>>>>>> DESTDIR='' >>>>>>>> LD_LIBRARY_PATH='' >>>>>>>> MACHINE='amd64' >>>>>>>> MACHINE_ARCH='amd64' >>>>>>>> MAKEOBJDIRPREFIX='/usr/obj' >>>>>>>> MAKESYSPATH='/usr/src/share/mk' >>>>>>>> MAKE_VERSION='20181221' >>>>>>>> PATH='/sbin:/bin:/usr/sbin:/usr/bin' >>>>>>>> SRCTOP='/usr/src' >>>>>>>> OBJTOP='/usr/obj/usr/src/amd64.amd64' >>>>>>>> >>>>>>>> It looks likes sort coredumps in the usr/share/zoneinfo part of >>>>>>>> the base. >>>>>>>> As it has no permission on the NFS share it errors out. >>>>>>>> On the server itself, the installworld goes well, but it leaves a >>>>>>>> sort.core file behind in /usr/share/zoneinfo >>>>>>>> >>>>>>>> cd /usr/share/zoneinfo >>>>>>>> ls -al >>>>>>>> >>>>>>>> >>>>>> _______________________________________________ >>>>>> 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" >>>>>> >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>>> >>> -- >>> Rod Grimes rgrimes@freebsd.org >>> _______________________________________________ >>> 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" >>> I have rebuild everything on the host and did a make cleanworld. Al is fine now. I should have done that before i asked here. Sorry to have wasted your time. But we did find a Makefile that should be doing things differently. regards Johan From owner-freebsd-current@freebsd.org Fri Apr 17 15:38: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 7BE8F2BDACA for ; Fri, 17 Apr 2020 15:38:54 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493gHK4Qljz46Xr for ; Fri, 17 Apr 2020 15:38:53 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8851D5C0074; Fri, 17 Apr 2020 11:38:52 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 11:38:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=M El5mweO17XTsOtVs4nilPdNRbGoYriT/ZeJeiEX1L0=; b=fygoSqYCeWG68K4Eo PEJd27+K/Z+MEshSRc4fXyLxiDRyJunfWVcsWL3EgcqbzoS7oVaDFqL9IFKs8mXg bjYLc/ruCJzxmk6g9nYNDBfR2U+nUnRmNB5mfo8LvwSMKFqALgs/K9DGI3/LrjY0 l9Tfzzk5GnhOI129INutSe1Ckct6F/L76HbWJrDQTATyFvedNQAHDIb00BQixUaX Jold3ZQO6R+tTfoAXP9qu+ZSmUy0owgLsWCvxkqCR+8ccHVRtx30PdVoi9c6ZNqf F5PrW3+WyYdDueZu8bbfzow7DJWXHjKFB4rvIxBbQ1C9+naIn+RvY5ftKSIbWVuJ 764lQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=MEl5mweO17XTsOtVs4nilPdNRbGoYriT/ZeJeiEX1 L0=; b=ZpQ+pot8QfGfQcrRzqUgcKkjthagYfsoEU71FAmW4cLg1Grt4GxMRCsk6 C1/v1tse+v4cZBfCbuUnj1X8uEF80oJ+PZz6T915QA90c3ePcEiKX0oWAeWmx5/Z v5pTR4UxMFkqLk6ldRGXItUuJRRurVVEZUP0Mel4IAUkrhbqajPdn3jTX1oKGwek PTQsumOqUoiFEbo+XF6lBs1qcjpL0jO2XfHGQ0VJT6Ww9P+i3J9d7xJGeGjUD7ce 5vwZIFzbvxwObZQbt2dqAcG9bvD4IsbeiFzuz+QdaVDQiJ0ZvyXU8JAATQBVf9GU FFDzYzEbx+206I1cQloAoH9N9VE4A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecuogfuuhhsphgvtghtffhomhgrihhnucdlgeelmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpefutghothht ucfnohhnghcuoehstghothhtlhesshgrmhhstghordhorhhgqeenucffohhmrghinhepih gssgdrtghopdhfrhgvvggsshgurdhorhhgnecukfhppeekrdegiedrkeelrddvudefnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshgtohhtth hlsehsrghmshgtohdrohhrgh X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id EF2AD3060067; Fri, 17 Apr 2020 11:38:51 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: Date: Fri, 17 Apr 2020 09:38:51 -0600 Cc: FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> References: To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493gHK4Qljz46Xr X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=fygoSqYC; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=ZpQ+pot8; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 66.111.4.29 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-3.49)[ip: (-9.84), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[29.4.111.66.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 15:38:54 -0000 Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either in = 12-STABLE or 13-CURRENT? Also, can you send me the output of = =E2=80=98dmesg=E2=80=99? Thanks, Scott > On Apr 17, 2020, at 5:23 AM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > I already asked on stable@ but as I tried it on 13-CURRENT with the = same result I am trying to ask for help here. >=20 > I have rented dedicated server Dell PowerEdge R6515 with iDRAC access = only. > There are 2 NVME drives which I wanted to use as ZFS root pool. >=20 > They are shown in iDRAC >=20 > Device Description: PCIe SSD in Slot 1 in Bay 1 > Device Protocol: NVMe-MI1.0 > Model: Dell Express Flash NVMe P4510 1TB SFF > Bus: 130 > Manufacturer: INTEL > Product ID: a54 > Revision: VDV1DP23 > Enclosure: PCIe SSD Backplane 1 >=20 >=20 > pciconf -l show many things, some of them are named "noneN@pci..." but = none "nvme" >=20 > The is printscreen (12.1 but 13-CURRENT is the same) >=20 > https://ibb.co/tPnymL7 >=20 > But I booted Linux SystemRescueCd and nvme devices are there visible = in /dev/ > https://ibb.co/sj22Nwg >=20 > There is verbose output of Linux lspci https://ibb.co/dPZTwV1 >=20 > Linux dmesg contains: > nvme nvme0: pci function 0000:81:00.0 > nvme nvme1: pci function 0000:82:00.0 > nvme nvme0: 32/0/0 default/read/poll queues > nvme nvme1: 32/0/0 default/read/poll queues >=20 >=20 > The machine is Dell PowerEdge R6515 with AMD EPYC 7302P >=20 >=20 > More details extracted from iDRAC web interface >=20 > I found this informations >=20 > PCIe SSD in Slot 1 in Bay 1 > Bus: 82 > BusProtocol: PCIE > Device: 0 > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > DeviceProtocol: NVMe-MI1.0 > DeviceType: PCIeSSD > DriveFormFactor: 2.5 inch > FailurePredicted: NO > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > FreeSizeInBytes: Information Not Available > Function: 0 > HotSpareStatus: Information Not Available > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > Manufacturer: INTEL > MaximumCapableSpeed: 8 GT/s > MediaType: Solid State Drive > Model: Dell Express Flash NVMe P4510 1TB SFF > NegotiatedSpeed: 8 GT/s > PCIeCapableLinkWidth: x4 > PCIeNegotiatedLinkWidth: x4 > PrimaryStatus: Ok > ProductID: a54 > RaidStatus: Information Not Available > RAIDType: Unknown > RemainingRatedWriteEndurance: 100 % > Revision: VDV1DP23 > SerialNumber: PHLJxxxxxxWF1PxxxxN > SizeInBytes: 1000204886016 > Slot: 1 > State: Ready > SystemEraseCapability: CryptographicErasePD >=20 > PCIe SSD in Slot 1 in Bay 1 - PCI Device > BusNumber: 130 > DataBusWidth: 4x or x4 > Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > DeviceNumber: 0 > DeviceType: PCIDevice > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > FunctionNumber: 0 > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > LastSystemInventoryTime: 2020-04-17T03:21:39 > LastUpdateTime: 2020-03-31T13:55:06 > Manufacturer: Intel Corporation > PCIDeviceID: 0A54 > PCISubDeviceID: 2003 > PCISubVendorID: 1028 > PCIVendorID: 8086 > SlotLength: 2.5 Inch Drive Form Factor > SlotType: PCI Express Gen 3 SFF-8639 >=20 >=20 > Can anybody shed some light what the real problem is? >=20 > Is the hardware not properly detected or is the driver completely = missing? >=20 > NVME PCIe architecture is out of my knowledge. >=20 > I really appreciate any help. >=20 > Kind regards > Miroslav Lachman > _______________________________________________ > 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 Fri Apr 17 15:41:00 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 406B82BDD11 for ; Fri, 17 Apr 2020 15:41:00 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493gKk6cDpz46wV for ; Fri, 17 Apr 2020 15:40:58 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8663228436; Fri, 17 Apr 2020 17:40:56 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id CF9EF28437; Fri, 17 Apr 2020 17:40:55 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <0ab05eb9-ce7f-a500-ca9f-70b97002946e@quip.cz> Date: Fri, 17 Apr 2020 17:40:55 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493gKk6cDpz46wV X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [3.97 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; IP_SCORE(0.82)[ip: (0.27), ipnet: 94.124.104.0/21(0.14), asn: 42000(3.59), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.96)[0.959,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(1.00)[0.998,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 15:41:00 -0000 Scott Long wrote on 04/17/2020 17:38: > Can you send me the output of ‘pciconf -llv’, either in 12-STABLE or 13-CURRENT? Also, can you send me the output of ‘dmesg’? I have only iDRAC access to this machine, I cannot copy or export text. Can I send you printscreen images? Thank you! Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 15:50: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 433802BE0FC for ; Fri, 17 Apr 2020 15:50:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493gY05twXz47gJ for ; Fri, 17 Apr 2020 15:50:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf30.google.com with SMTP id y19so1109379qvv.4 for ; Fri, 17 Apr 2020 08:50:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/MMwh1UzCMHg0/I0PmQMWxjxkT5QKpBTMEdJ/8lXZzw=; b=0fuGb8YW66Wg1uraBaTImWvAQFww6Es3Pz/ljc1IWGuAcfviFx8M37RycDVPn0j85J RrM4YT1QiqZRffVeouP0Virkfojcov4aXoBNzU6R0EYvkFHmdVN2lF8GQ/sXbx5wiXAV +YtPYRVZ3Jq9AlR7ZapMge9FbNWtw8MX961Ue6KK2u5dargrZQU4rn78ptfD71wE+DC7 xzSpLp3nHRK8qMkXLpt2S2EQ8UP1udP4m4bBTx73gHkWk3d8ySeefmqWpuLeqx55Mvzj jbLLHuMU7VGSa+mxGGC3M8/EKIZXHUfIWvx6L2kj8x1k/op9533jnYtFlyszbZRnijBK sI7w== 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=/MMwh1UzCMHg0/I0PmQMWxjxkT5QKpBTMEdJ/8lXZzw=; b=fbQUXiIO7HjN4ad1I9ITuSnUCBHAntmb+EPEBjkVxh1dNAQYaH6QCkphpb1RyVgP2/ oOf/rLL1PYAQE5EbUAlLME7qKlnEd6G44cXFl5k/hpF31yi3sFqBPJOEOgYwjcIopDi3 GrZrsTe37lxWHCKPmY4vtzTmdnO2eH95F0FRHD6K11EvtWmFOSZjyg0tOAkwV6n+nljf Xb/iC9mCtDAhKb5+Uikx/LZ7/KNmBLaIsFbJT7nch/M4QMl0V7TR6wy22RvUv0q7z+fW zvNuCfqKK53Mtz7UTSlEaotE1Fa/p9PziXEZz1z5zECFRQklKGZ951WbtzfQBjuFsH34 /Sig== X-Gm-Message-State: AGi0PubZNGnshP7IRLfAO/FPh6MLr4rvSsjd5/XnYmWGSjVnEn/USrcX 0yAEo6gMI1e6WE4NGsWwG+9b+rWb/4XyD9NX4Frdi3jK X-Google-Smtp-Source: APiQypJOWjwfEgk43qCZJN+AJz+XO8V+xgqRDeBdeCXugsnDk/CEfWcVJtRbyIrcirXwjmkexJ/99WhxYTdBCAOM/LA= X-Received: by 2002:a0c:e105:: with SMTP id w5mr3467898qvk.118.1587138643355; Fri, 17 Apr 2020 08:50:43 -0700 (PDT) MIME-Version: 1.0 References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> In-Reply-To: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> From: Warner Losh Date: Fri, 17 Apr 2020 09:50:31 -0600 Message-ID: Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current X-Rspamd-Queue-Id: 493gY05twXz47gJ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=0fuGb8YW; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::f30) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-2.36 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[15]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[0.3.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-1.36)[ip: (-6.01), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 15:50:46 -0000 On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: > Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either in 1= 2-STABLE or > 13-CURRENT? Also, can you send me the output of =E2=80=98dmesg=E2=80=99? > There was another thread that said there was a raid card in the way... It would be cool to find a way to get it out of the way... :) Warner > Thanks, > Scott > > > > On Apr 17, 2020, at 5:23 AM, Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > I already asked on stable@ but as I tried it on 13-CURRENT with the > same result I am trying to ask for help here. > > > > I have rented dedicated server Dell PowerEdge R6515 with iDRAC access > only. > > There are 2 NVME drives which I wanted to use as ZFS root pool. > > > > They are shown in iDRAC > > > > Device Description: PCIe SSD in Slot 1 in Bay 1 > > Device Protocol: NVMe-MI1.0 > > Model: Dell Express Flash NVMe P4510 1TB SFF > > Bus: 130 > > Manufacturer: INTEL > > Product ID: a54 > > Revision: VDV1DP23 > > Enclosure: PCIe SSD Backplane 1 > > > > > > pciconf -l show many things, some of them are named "noneN@pci..." but > none "nvme" > > > > The is printscreen (12.1 but 13-CURRENT is the same) > > > > https://ibb.co/tPnymL7 > > > > But I booted Linux SystemRescueCd and nvme devices are there visible in > /dev/ > > https://ibb.co/sj22Nwg > > > > There is verbose output of Linux lspci https://ibb.co/dPZTwV1 > > > > Linux dmesg contains: > > nvme nvme0: pci function 0000:81:00.0 > > nvme nvme1: pci function 0000:82:00.0 > > nvme nvme0: 32/0/0 default/read/poll queues > > nvme nvme1: 32/0/0 default/read/poll queues > > > > > > The machine is Dell PowerEdge R6515 with AMD EPYC 7302P > > > > > > More details extracted from iDRAC web interface > > > > I found this informations > > > > PCIe SSD in Slot 1 in Bay 1 > > Bus: 82 > > BusProtocol: PCIE > > Device: 0 > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > DeviceProtocol: NVMe-MI1.0 > > DeviceType: PCIeSSD > > DriveFormFactor: 2.5 inch > > FailurePredicted: NO > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > FreeSizeInBytes: Information Not Available > > Function: 0 > > HotSpareStatus: Information Not Available > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > Manufacturer: INTEL > > MaximumCapableSpeed: 8 GT/s > > MediaType: Solid State Drive > > Model: Dell Express Flash NVMe P4510 1TB SFF > > NegotiatedSpeed: 8 GT/s > > PCIeCapableLinkWidth: x4 > > PCIeNegotiatedLinkWidth: x4 > > PrimaryStatus: Ok > > ProductID: a54 > > RaidStatus: Information Not Available > > RAIDType: Unknown > > RemainingRatedWriteEndurance: 100 % > > Revision: VDV1DP23 > > SerialNumber: PHLJxxxxxxWF1PxxxxN > > SizeInBytes: 1000204886016 > > Slot: 1 > > State: Ready > > SystemEraseCapability: CryptographicErasePD > > > > PCIe SSD in Slot 1 in Bay 1 - PCI Device > > BusNumber: 130 > > DataBusWidth: 4x or x4 > > Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > DeviceNumber: 0 > > DeviceType: PCIDevice > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > FunctionNumber: 0 > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > LastSystemInventoryTime: 2020-04-17T03:21:39 > > LastUpdateTime: 2020-03-31T13:55:06 > > Manufacturer: Intel Corporation > > PCIDeviceID: 0A54 > > PCISubDeviceID: 2003 > > PCISubVendorID: 1028 > > PCIVendorID: 8086 > > SlotLength: 2.5 Inch Drive Form Factor > > SlotType: PCI Express Gen 3 SFF-8639 > > > > > > Can anybody shed some light what the real problem is? > > > > Is the hardware not properly detected or is the driver completely > missing? > > > > NVME PCIe architecture is out of my knowledge. > > > > I really appreciate any help. > > > > Kind regards > > Miroslav Lachman > > _______________________________________________ > > 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" > > _______________________________________________ > 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 Fri Apr 17 15:54: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 DEDF82BE90B for ; Fri, 17 Apr 2020 15:54:59 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493gdt6p44z48gS for ; Fri, 17 Apr 2020 15:54:58 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 82DB15C02BD; Fri, 17 Apr 2020 11:54:58 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 11:54:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=h leXxx/YjL9a7SZru3yF4kZBAta7ZYWzvw6IejuS3lo=; b=rFJVk/SNmV2MBDDTI fWdzoLQwOvjJjhMcR6pLM2BXNFDBEkhvdFPh7ZrdKvHXYbFMGnlZJuGPaZH6xHUa IxGAJupl9vaqreAt+AvSjrSPZ0Sh2I/kGTB8E+Wc8AiEAMj1w8DCO6xe/niKjku6 UesdMWfMNVvhKhmYdyg0DIsj3pnhaNTQ3sH3wKp8uI6xQQhMDl4fIJ+2zs1cvZlY znYYmBIe4bXFcjye4E6OLCsBEZZc3f+rQU4N92vwbU00oFrLuf9sR2OGYCLykmNa US1xT/BQZFEeYlApKFFR6t0DAfaP102C9M1sJdn/qdxWiUzZnYojApK7MEFp8zwI pfaaw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=hleXxx/YjL9a7SZru3yF4kZBAta7ZYWzvw6IejuS3 lo=; b=b947QVwqmNFOVEkE3oqydlsjNoyHoBCqr9EolQHKz8vGu0UMbA3qXx1pN my72nzYgqmYOdTi3lL0V0aOVXXYD+KJF1lN5yi18apt/srlc0BQq/qOH1NVF57NN fCaUIZwhl2kFH1wNtKHFHyKTIqp+RPMDUeC5H6agUYKDimO+F7eE+3iv/LBzNtTc 5+dPptJNeTx3Qi8P9yBZSou6GxZ4yJgX3ywr37BOqx4vpCKIIXbDFCwivgAmD7P0 9fWEyY3kiD1bTY7hn1i+DEAwaoOAZOhBPvyQUaultBQ40wUS/6wG7zB3jYLbsGQk 0RDcnCrL5UichD8TXpxIcuhwNfx4w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdelhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecuogfuuhhsphgvtghtffhomhgrihhnucdlgeelmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpefutghothht ucfnohhnghcuoehstghothhtlhesshgrmhhstghordhorhhgqeenucffohhmrghinhepih gssgdrtghopdhfrhgvvggsshgurdhorhhgnecukfhppeekrdegiedrkeelrddvudefnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshgtohhtth hlsehsrghmshgtohdrohhrgh X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id 5CB733060069; Fri, 17 Apr 2020 11:54:57 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: Date: Fri, 17 Apr 2020 09:54:56 -0600 Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> To: Warner Losh X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493gdt6p44z48gS X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=rFJVk/SN; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=b947QVwq; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 66.111.4.29 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.49)[ip: (-9.84), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[29.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 15:54:59 -0000 Would that be the Intel VMD/VROC stuff? If so, there=E2=80=99s a driver = for FreeBSD, but it=E2=80=99s not well tested yet. Will have to dig in = further. Scott > On Apr 17, 2020, at 9:50 AM, Warner Losh wrote: >=20 >=20 >=20 > On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: > Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either = in 12-STABLE or 13-CURRENT? Also, can you send me the output of = =E2=80=98dmesg=E2=80=99? >=20 > There was another thread that said there was a raid card in the way... = It would be cool to find a way to get it out of the way... :) >=20 > Warner > =20 > Thanks, > Scott >=20 >=20 > > On Apr 17, 2020, at 5:23 AM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: > >=20 > > I already asked on stable@ but as I tried it on 13-CURRENT with the = same result I am trying to ask for help here. > >=20 > > I have rented dedicated server Dell PowerEdge R6515 with iDRAC = access only. > > There are 2 NVME drives which I wanted to use as ZFS root pool. > >=20 > > They are shown in iDRAC > >=20 > > Device Description: PCIe SSD in Slot 1 in Bay 1 > > Device Protocol: NVMe-MI1.0 > > Model: Dell Express Flash NVMe P4510 1TB SFF > > Bus: 130 > > Manufacturer: INTEL > > Product ID: a54 > > Revision: VDV1DP23 > > Enclosure: PCIe SSD Backplane 1 > >=20 > >=20 > > pciconf -l show many things, some of them are named "noneN@pci..." = but none "nvme" > >=20 > > The is printscreen (12.1 but 13-CURRENT is the same) > >=20 > > https://ibb.co/tPnymL7 > >=20 > > But I booted Linux SystemRescueCd and nvme devices are there visible = in /dev/ > > https://ibb.co/sj22Nwg > >=20 > > There is verbose output of Linux lspci https://ibb.co/dPZTwV1 > >=20 > > Linux dmesg contains: > > nvme nvme0: pci function 0000:81:00.0 > > nvme nvme1: pci function 0000:82:00.0 > > nvme nvme0: 32/0/0 default/read/poll queues > > nvme nvme1: 32/0/0 default/read/poll queues > >=20 > >=20 > > The machine is Dell PowerEdge R6515 with AMD EPYC 7302P > >=20 > >=20 > > More details extracted from iDRAC web interface > >=20 > > I found this informations > >=20 > > PCIe SSD in Slot 1 in Bay 1 > > Bus: 82 > > BusProtocol: PCIE > > Device: 0 > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > DeviceProtocol: NVMe-MI1.0 > > DeviceType: PCIeSSD > > DriveFormFactor: 2.5 inch > > FailurePredicted: NO > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > FreeSizeInBytes: Information Not Available > > Function: 0 > > HotSpareStatus: Information Not Available > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > Manufacturer: INTEL > > MaximumCapableSpeed: 8 GT/s > > MediaType: Solid State Drive > > Model: Dell Express Flash NVMe P4510 1TB SFF > > NegotiatedSpeed: 8 GT/s > > PCIeCapableLinkWidth: x4 > > PCIeNegotiatedLinkWidth: x4 > > PrimaryStatus: Ok > > ProductID: a54 > > RaidStatus: Information Not Available > > RAIDType: Unknown > > RemainingRatedWriteEndurance: 100 % > > Revision: VDV1DP23 > > SerialNumber: PHLJxxxxxxWF1PxxxxN > > SizeInBytes: 1000204886016 > > Slot: 1 > > State: Ready > > SystemEraseCapability: CryptographicErasePD > >=20 > > PCIe SSD in Slot 1 in Bay 1 - PCI Device > > BusNumber: 130 > > DataBusWidth: 4x or x4 > > Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > DeviceNumber: 0 > > DeviceType: PCIDevice > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > FunctionNumber: 0 > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > LastSystemInventoryTime: 2020-04-17T03:21:39 > > LastUpdateTime: 2020-03-31T13:55:06 > > Manufacturer: Intel Corporation > > PCIDeviceID: 0A54 > > PCISubDeviceID: 2003 > > PCISubVendorID: 1028 > > PCIVendorID: 8086 > > SlotLength: 2.5 Inch Drive Form Factor > > SlotType: PCI Express Gen 3 SFF-8639 > >=20 > >=20 > > Can anybody shed some light what the real problem is? > >=20 > > Is the hardware not properly detected or is the driver completely = missing? > >=20 > > NVME PCIe architecture is out of my knowledge. > >=20 > > I really appreciate any help. > >=20 > > Kind regards > > Miroslav Lachman > > _______________________________________________ > > 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" >=20 > _______________________________________________ > 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 Fri Apr 17 16:10: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 348332BF0E0 for ; Fri, 17 Apr 2020 16:10:35 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493gzt1lY8z4B97 for ; Fri, 17 Apr 2020 16:10:33 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0A99228433; Fri, 17 Apr 2020 18:10:32 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 3FD4328416; Fri, 17 Apr 2020 18:10:31 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long , Warner Losh Cc: FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <295b7714-ed88-8ffa-fb5c-1033d63dd552@quip.cz> Date: Fri, 17 Apr 2020 18:10:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493gzt1lY8z4B97 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [3.97 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; IP_SCORE(0.82)[ip: (0.27), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.58), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.95)[0.953,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.998,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 16:10:35 -0000 Scott Long wrote on 04/17/2020 17:54: > Would that be the Intel VMD/VROC stuff? If so, there’s a driver for FreeBSD, but it’s not well tested yet. Will have to dig in further. This is AMD EPYC machine. Isn't VROC Intel only thing? >> On Apr 17, 2020, at 9:50 AM, Warner Losh wrote: >> On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: >> Can you send me the output of ‘pciconf -llv’, either in 12-STABLE or 13-CURRENT? Also, can you send me the output of ‘dmesg’? >> >> There was another thread that said there was a raid card in the way... It would be cool to find a way to get it out of the way... :) I didn't find any evidence of RAID card but maybe I cannot look for it. Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 16: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 EC77C2BF659 for ; Fri, 17 Apr 2020 16:16:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493h6C0vgLz4BsQ for ; Fri, 17 Apr 2020 16:16:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x733.google.com with SMTP id l25so2988696qkk.3 for ; Fri, 17 Apr 2020 09:16:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VqMT/IvR3O/9fZUr2HrVRpfhKCPV00wrPCJrNiQio1A=; b=kszmCuyh3WY1zxGcal+FswMbzIMhz8hocLCMRVbnsu425x0Ha7vwW6syGO+k1t3xIM I0SSOpCaJFvuEdgYXESewOzBq2dxX66gVhkq4P1ywUC2v+XmxZ/+49/2D4Df8x/xwTLx iRsKNreD3ao/zOa5y8TP7FbGFan3/aVannw9Z0cIniUONpWmWwUhZY6Sxb5LBXt06xJ0 bM2xxo9xbheCsJSdXANLGwE5SzPDmv2NUQZ0YtsJUX7Mutumpqk+ifnQqN+pphKNahow SbI5PZ6O8r/UfB0vp6LiMRXOnxC6BU0yPnOuffk4vtXlhTRbkpT2qXJ4pJbUFDDYOpit FQfQ== 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=VqMT/IvR3O/9fZUr2HrVRpfhKCPV00wrPCJrNiQio1A=; b=FvYg7dNJHftaoDeFOMhp4YcYGHyRvid7PHXLkuuHYRDykReEgAMEVZPlUW4Nku6gHw J6RqCLojBwcLxNyE5Sw6CZ5lnO7ELXpvFynfRQOU2dHSqAkZZ8YaxHdskJWQgCNlVWNb i0U04yfoAcyYxgglBX9e9eY60dFi3qRNUJ/L+Iwl4AlAP+TOHf8ndiWWQ0dvk5IImmlH FXUEwf+yGKrhIKL8OFHzQ2+Nt1BpSy70Arqr1tlRAQGlbVyd9fsF3WscV2ygwMUu8D8U A8VbLecCHjbmxnfqgOT3BfIDJ252jnsoH3zzS6kUTSl0yjjyppTz32jEdREJ70zb8kk0 MH9A== X-Gm-Message-State: AGi0PuZ7WfCZo2yO71hZVDFm3YVA6OWsiyyPDCLicYLEr9Ou46N223OH jry+RoOu0P3SudKnLge4Go0GmH7wL1rjILZJBaX4+uEvcHc= X-Google-Smtp-Source: APiQypK+RET8k2+flxvOfqufy2gdhdkZO+Mw7/h/zvc0PGTopsZ0voEzDfjWsp8qajP4ToWm1BXLhk8jtmyfV7oGdpo= X-Received: by 2002:a37:6ce:: with SMTP id 197mr3861424qkg.495.1587140161975; Fri, 17 Apr 2020 09:16:01 -0700 (PDT) MIME-Version: 1.0 References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> In-Reply-To: <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> From: Warner Losh Date: Fri, 17 Apr 2020 10:15:50 -0600 Message-ID: Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current X-Rspamd-Queue-Id: 493h6C0vgLz4BsQ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=kszmCuyh; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::733) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.98 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[3.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-1.98)[ip: (-9.09), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 16:16:04 -0000 No. It was some kind of extra card (Perteq?) managing things in a Dell server. It may be the VMD/VROC stuff, and that driver may be worth a shot, but I'm thinking not. It looks like Doug's code for that is in the tree, though https://reviews.freebsd.org/rS353380. Or are other changes needed? I've been blessed with either being able to turn this off, or not having to deal... Warner On Fri, Apr 17, 2020 at 9:54 AM Scott Long wrote: > Would that be the Intel VMD/VROC stuff? If so, there=E2=80=99s a driver = for > FreeBSD, but it=E2=80=99s not well tested yet. Will have to dig in furth= er. > > Scott > > > > On Apr 17, 2020, at 9:50 AM, Warner Losh wrote: > > > > > > > > On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: > > Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either in= 12-STABLE or > 13-CURRENT? Also, can you send me the output of =E2=80=98dmesg=E2=80=99? > > > > There was another thread that said there was a raid card in the way... > It would be cool to find a way to get it out of the way... :) > > > > Warner > > > > Thanks, > > Scott > > > > > > > On Apr 17, 2020, at 5:23 AM, Miroslav Lachman <000.fbsd@quip.cz> > wrote: > > > > > > I already asked on stable@ but as I tried it on 13-CURRENT with the > same result I am trying to ask for help here. > > > > > > I have rented dedicated server Dell PowerEdge R6515 with iDRAC access > only. > > > There are 2 NVME drives which I wanted to use as ZFS root pool. > > > > > > They are shown in iDRAC > > > > > > Device Description: PCIe SSD in Slot 1 in Bay 1 > > > Device Protocol: NVMe-MI1.0 > > > Model: Dell Express Flash NVMe P4510 1TB SFF > > > Bus: 130 > > > Manufacturer: INTEL > > > Product ID: a54 > > > Revision: VDV1DP23 > > > Enclosure: PCIe SSD Backplane 1 > > > > > > > > > pciconf -l show many things, some of them are named "noneN@pci..." > but none "nvme" > > > > > > The is printscreen (12.1 but 13-CURRENT is the same) > > > > > > https://ibb.co/tPnymL7 > > > > > > But I booted Linux SystemRescueCd and nvme devices are there visible > in /dev/ > > > https://ibb.co/sj22Nwg > > > > > > There is verbose output of Linux lspci https://ibb.co/dPZTwV1 > > > > > > Linux dmesg contains: > > > nvme nvme0: pci function 0000:81:00.0 > > > nvme nvme1: pci function 0000:82:00.0 > > > nvme nvme0: 32/0/0 default/read/poll queues > > > nvme nvme1: 32/0/0 default/read/poll queues > > > > > > > > > The machine is Dell PowerEdge R6515 with AMD EPYC 7302P > > > > > > > > > More details extracted from iDRAC web interface > > > > > > I found this informations > > > > > > PCIe SSD in Slot 1 in Bay 1 > > > Bus: 82 > > > BusProtocol: PCIE > > > Device: 0 > > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > > DeviceProtocol: NVMe-MI1.0 > > > DeviceType: PCIeSSD > > > DriveFormFactor: 2.5 inch > > > FailurePredicted: NO > > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > > FreeSizeInBytes: Information Not Available > > > Function: 0 > > > HotSpareStatus: Information Not Available > > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > > Manufacturer: INTEL > > > MaximumCapableSpeed: 8 GT/s > > > MediaType: Solid State Drive > > > Model: Dell Express Flash NVMe P4510 1TB SFF > > > NegotiatedSpeed: 8 GT/s > > > PCIeCapableLinkWidth: x4 > > > PCIeNegotiatedLinkWidth: x4 > > > PrimaryStatus: Ok > > > ProductID: a54 > > > RaidStatus: Information Not Available > > > RAIDType: Unknown > > > RemainingRatedWriteEndurance: 100 % > > > Revision: VDV1DP23 > > > SerialNumber: PHLJxxxxxxWF1PxxxxN > > > SizeInBytes: 1000204886016 > > > Slot: 1 > > > State: Ready > > > SystemEraseCapability: CryptographicErasePD > > > > > > PCIe SSD in Slot 1 in Bay 1 - PCI Device > > > BusNumber: 130 > > > DataBusWidth: 4x or x4 > > > Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) > > > DeviceDescription: PCIe SSD in Slot 1 in Bay 1 > > > DeviceNumber: 0 > > > DeviceType: PCIDevice > > > FQDD: Disk.Bay.1:Enclosure.Internal.0-1 > > > FunctionNumber: 0 > > > InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 > > > LastSystemInventoryTime: 2020-04-17T03:21:39 > > > LastUpdateTime: 2020-03-31T13:55:06 > > > Manufacturer: Intel Corporation > > > PCIDeviceID: 0A54 > > > PCISubDeviceID: 2003 > > > PCISubVendorID: 1028 > > > PCIVendorID: 8086 > > > SlotLength: 2.5 Inch Drive Form Factor > > > SlotType: PCI Express Gen 3 SFF-8639 > > > > > > > > > Can anybody shed some light what the real problem is? > > > > > > Is the hardware not properly detected or is the driver completely > missing? > > > > > > NVME PCIe architecture is out of my knowledge. > > > > > > I really appreciate any help. > > > > > > Kind regards > > > Miroslav Lachman > > > _______________________________________________ > > > 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" > > > > _______________________________________________ > > 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 Fri Apr 17 16:17:02 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 993472BF7E8 for ; Fri, 17 Apr 2020 16:17:02 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493h7K6h9zz4C3x for ; Fri, 17 Apr 2020 16:17:01 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6E48A5C006F; Fri, 17 Apr 2020 12:17:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 12:17:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=c gID2niiq5h/bVrRgohploj9zJAkKwFX/M3wJcicFWI=; b=AGpEUchIKek4+1vPF LS0hnGPQ3h+V2bjTcz9IXZLE5J9kJ1RZZrVXHpCtFsbw03iSTzuJVdWn8b/UieD7 LdTHlszZxlgC40NhUCEFKkaKVZprP59TrslBAjaBXOpYCKFUPjCXyzmXhLb8yUcq MC0UmMOjwEpRL3TOWhJEMm/QDXS5+HC7sjFIAlbcv+HnoQE1hUHisGXpDyoQGBvO 1A7dOMgEr7AEQFF/wvz8N1svhL9ZjhFIXyPzaJcZA0Iw+iXqqoSdFqBJcjDV8gfD 9eUk/PW1CcXbeWR370KRPR4aZF9QYiDn/QJWqBx89s35QxkAulRZTQIJb4seQBml g157w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=cgID2niiq5h/bVrRgohploj9zJAkKwFX/M3wJcicF WI=; b=29vX9a7CKDukYQTEa1qqRJB4UBoydlu4bGXboceklV+Y1K6BS+rrT8tFr JvqXjt6ED4exsTdOAatWfluzcjWK14cUjW0hOSGqQgJovWZvypO0dOAdNsdoNp8D +b0I6NbTfCZymNZTjbFU6hrpjNQxrqZFj8Bx4CPOko2X9pp9jeZOMcp6RnHstJZX sAu8cHwZrk7sZd8E4iy4LFfWaHqUH8hQHZYVVMljXMSS1CaFIxk7YbYaR/SMV1Ay HnqFClB6IgBEWMkHvBB41NxvRCsICXBuRfm2+Mi/3n3kP6fg0rUkFV+XFzVyQ1bx efaNs4PaYsVz7EZHLJdeT+7/QV48g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecuogfuuhhsphgvtghtffhomhgrihhnucdlgeelmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpefutghothht ucfnohhnghcuoehstghothhtlhesshgrmhhstghordhorhhgqeenucffohhmrghinhepih gssgdrtghopdhfrhgvvggsshgurdhorhhgnecukfhppeekrdegiedrkeelrddvudefnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshgtohhtth hlsehsrghmshgtohdrohhrgh X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id BADCD3060057; Fri, 17 Apr 2020 12:17:00 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> Date: Fri, 17 Apr 2020 10:17:00 -0600 Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> To: Warner Losh X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493h7K6h9zz4C3x X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=AGpEUchI; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=29vX9a7C; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 66.111.4.29 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.49)[ip: (-9.84), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[29.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 16:17:02 -0000 You are correct about Intel vs AMD. Comparing the full output of = pciconf from FreeBSD with the fragment of lspci from Linux suggests that = there=E2=80=99s at least one set of a PCIe switch and child devices that = is not being enumerated by FreeBSD. Can you send the full output of = `lspci -tvv` from linux? Thanks, Scott > On Apr 17, 2020, at 9:54 AM, Scott Long wrote: >=20 > Would that be the Intel VMD/VROC stuff? If so, there=E2=80=99s a = driver for FreeBSD, but it=E2=80=99s not well tested yet. Will have to = dig in further. >=20 > Scott >=20 >=20 >> On Apr 17, 2020, at 9:50 AM, Warner Losh wrote: >>=20 >>=20 >>=20 >> On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: >> Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either = in 12-STABLE or 13-CURRENT? Also, can you send me the output of = =E2=80=98dmesg=E2=80=99? >>=20 >> There was another thread that said there was a raid card in the = way... It would be cool to find a way to get it out of the way... :) >>=20 >> Warner >>=20 >> Thanks, >> Scott >>=20 >>=20 >>> On Apr 17, 2020, at 5:23 AM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >>>=20 >>> I already asked on stable@ but as I tried it on 13-CURRENT with the = same result I am trying to ask for help here. >>>=20 >>> I have rented dedicated server Dell PowerEdge R6515 with iDRAC = access only. >>> There are 2 NVME drives which I wanted to use as ZFS root pool. >>>=20 >>> They are shown in iDRAC >>>=20 >>> Device Description: PCIe SSD in Slot 1 in Bay 1 >>> Device Protocol: NVMe-MI1.0 >>> Model: Dell Express Flash NVMe P4510 1TB SFF >>> Bus: 130 >>> Manufacturer: INTEL >>> Product ID: a54 >>> Revision: VDV1DP23 >>> Enclosure: PCIe SSD Backplane 1 >>>=20 >>>=20 >>> pciconf -l show many things, some of them are named "noneN@pci..." = but none "nvme" >>>=20 >>> The is printscreen (12.1 but 13-CURRENT is the same) >>>=20 >>> https://ibb.co/tPnymL7 >>>=20 >>> But I booted Linux SystemRescueCd and nvme devices are there visible = in /dev/ >>> https://ibb.co/sj22Nwg >>>=20 >>> There is verbose output of Linux lspci https://ibb.co/dPZTwV1 >>>=20 >>> Linux dmesg contains: >>> nvme nvme0: pci function 0000:81:00.0 >>> nvme nvme1: pci function 0000:82:00.0 >>> nvme nvme0: 32/0/0 default/read/poll queues >>> nvme nvme1: 32/0/0 default/read/poll queues >>>=20 >>>=20 >>> The machine is Dell PowerEdge R6515 with AMD EPYC 7302P >>>=20 >>>=20 >>> More details extracted from iDRAC web interface >>>=20 >>> I found this informations >>>=20 >>> PCIe SSD in Slot 1 in Bay 1 >>> Bus: 82 >>> BusProtocol: PCIE >>> Device: 0 >>> DeviceDescription: PCIe SSD in Slot 1 in Bay 1 >>> DeviceProtocol: NVMe-MI1.0 >>> DeviceType: PCIeSSD >>> DriveFormFactor: 2.5 inch >>> FailurePredicted: NO >>> FQDD: Disk.Bay.1:Enclosure.Internal.0-1 >>> FreeSizeInBytes: Information Not Available >>> Function: 0 >>> HotSpareStatus: Information Not Available >>> InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 >>> Manufacturer: INTEL >>> MaximumCapableSpeed: 8 GT/s >>> MediaType: Solid State Drive >>> Model: Dell Express Flash NVMe P4510 1TB SFF >>> NegotiatedSpeed: 8 GT/s >>> PCIeCapableLinkWidth: x4 >>> PCIeNegotiatedLinkWidth: x4 >>> PrimaryStatus: Ok >>> ProductID: a54 >>> RaidStatus: Information Not Available >>> RAIDType: Unknown >>> RemainingRatedWriteEndurance: 100 % >>> Revision: VDV1DP23 >>> SerialNumber: PHLJxxxxxxWF1PxxxxN >>> SizeInBytes: 1000204886016 >>> Slot: 1 >>> State: Ready >>> SystemEraseCapability: CryptographicErasePD >>>=20 >>> PCIe SSD in Slot 1 in Bay 1 - PCI Device >>> BusNumber: 130 >>> DataBusWidth: 4x or x4 >>> Description: Express Flash NVMe 1.0 TB 2.5" U.2 (P4510) >>> DeviceDescription: PCIe SSD in Slot 1 in Bay 1 >>> DeviceNumber: 0 >>> DeviceType: PCIDevice >>> FQDD: Disk.Bay.1:Enclosure.Internal.0-1 >>> FunctionNumber: 0 >>> InstanceID: Disk.Bay.1:Enclosure.Internal.0-1 >>> LastSystemInventoryTime: 2020-04-17T03:21:39 >>> LastUpdateTime: 2020-03-31T13:55:06 >>> Manufacturer: Intel Corporation >>> PCIDeviceID: 0A54 >>> PCISubDeviceID: 2003 >>> PCISubVendorID: 1028 >>> PCIVendorID: 8086 >>> SlotLength: 2.5 Inch Drive Form Factor >>> SlotType: PCI Express Gen 3 SFF-8639 >>>=20 >>>=20 >>> Can anybody shed some light what the real problem is? >>>=20 >>> Is the hardware not properly detected or is the driver completely = missing? >>>=20 >>> NVME PCIe architecture is out of my knowledge. >>>=20 >>> I really appreciate any help. >>>=20 >>> Kind regards >>> Miroslav Lachman >>> _______________________________________________ >>> 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" >>=20 >> _______________________________________________ >> 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" >=20 > _______________________________________________ > 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 Fri Apr 17 16:31: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 1C4FE2C0189 for ; Fri, 17 Apr 2020 16:31:04 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493hRW3H7Nz4DKf for ; Fri, 17 Apr 2020 16:31:03 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 10BA928434; Fri, 17 Apr 2020 18:31:01 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id EFA1128432; Fri, 17 Apr 2020 18:30:59 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Warner Losh , Scott Long Cc: FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Fri, 17 Apr 2020 18:30:59 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 493hRW3H7Nz4DKf X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [3.99 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; IP_SCORE(0.81)[ip: (0.27), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.58), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.974,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 16:31:04 -0000 Warner Losh wrote on 04/17/2020 18:15: > No. It was some kind of extra card (Perteq?) managing things in a Dell > server. It may be the VMD/VROC stuff, and that driver may be worth a shot, > but I'm thinking not. It looks like Doug's code for that is in the tree, > though https://reviews.freebsd.org/rS353380. Or are other changes needed? > I've been blessed with either being able to turn this off, or not having > to deal... vmd is in the kernel of 13-CURRENT installer I tried but I don't see any vmd device. Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 16:46: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 37FF02C09C2 for ; Fri, 17 Apr 2020 16:46:50 +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) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493hnj4MTyz4Fp4 for ; Fri, 17 Apr 2020 16:46:49 +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 1jPU8X-000PyN-70; Fri, 17 Apr 2020 17:46:41 +0100 Date: Fri, 17 Apr 2020 17:46:41 +0100 From: Gary Palmer To: Miroslav Lachman <000.fbsd@quip.cz> Cc: FreeBSD-Current Subject: Re: PCIe NVME drives not detected on Dell R6515 Message-ID: <20200417164641.GB96264@in-addr.com> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <0ab05eb9-ce7f-a500-ca9f-70b97002946e@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0ab05eb9-ce7f-a500-ca9f-70b97002946e@quip.cz> 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: 493hnj4MTyz4Fp4 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.90 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.93)[-0.930,0]; NEURAL_HAM_LONG(-0.96)[-0.965,0]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 16:46:50 -0000 On Fri, Apr 17, 2020 at 05:40:55PM +0200, Miroslav Lachman wrote: > Scott Long wrote on 04/17/2020 17:38: > > Can you send me the output of ???pciconf -llv???, either in 12-STABLE or 13-CURRENT? Also, can you send me the output of ???dmesg???? > > I have only iDRAC access to this machine, I cannot copy or export text. Can > I send you printscreen images? You used to be able to ssh to the iDRAC IP and there was a magic command that let you get to the serial console via SSH. I don't have access to Dell hardware any more to dig out the magic command, sorry Regards, Gary From owner-freebsd-current@freebsd.org Fri Apr 17 18:35:42 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 486B82C4549; Fri, 17 Apr 2020 18:35:42 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493lCL1Fwdz4QnB; Fri, 17 Apr 2020 18:35:42 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) Received: from [IPv6:2600:1700:358a:c660:305b:9aa6:7c2d:c818] (unknown [IPv6:2600:1700:358a:c660:305b:9aa6:7c2d:c818]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: freqlabs/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 0A026FBFF; Fri, 17 Apr 2020 18:35:42 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) From: Ryan Moeller Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: OpenZFS port updated Message-Id: Date: Fri, 17 Apr 2020 14:35:41 -0400 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3608.80.23.2.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 18:35:42 -0000 FreeBSD support has been merged into the master branch of the = openzfs/zfs repository, and the FreeBSD ports have been switched to this = branch. OpenZFS brings many exciting features to FreeBSD, including: * native encryption * improved TRIM implementation * most recently, persistent L2ARC Of course, avoid upgrading your pools if you want to keep the option to = go back to the base ZFS. OpenZFS can be installed alongside the base ZFS. Change your loader.conf = entry to openzfs_load=3D=E2=80=9CYES=E2=80=9D to load the OpenZFS module = at boot, and set PATH to find the tools in /usr/local/sbin before /sbin. = The base zfs tools are still basically functional with the OpenZFS = module, so changing PATH in rc is not strictly necessary. The FreeBSD loader can boot from pools with the encryption feature = enabled, but the root/bootenv datasets must not be encrypted themselves. The FreeBSD platform support in OpenZFS does not yet include all = features present in FreeBSD=E2=80=99s ZFS. Some notable changes/missing = features include: * many sysctl names have changed (legacy compat sysctls should be added = at some point)=20 * zfs send progress reporting in process title via setproctitle * extended 'zfs holds -r' = (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D290015) * vdev ashift optimizations = (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D254591) * pre-mountroot zpool.cache loading (for automatic pool imports) To the last point, this mainly effects the case where / is on ZFS and = /boot is not or is on a different pool. OpenZFS cannot handle this case = yet, but work is in progress to cover that use case. Booting directly = from ZFS does work. If there are pools that need to be imported at boot other than the boot = pool, OpenZFS does not automatically import yet, and it uses = /etc/zfs/zpool.cache rather than /boot/zfs/zpool.cache to keep track of = imported pools. To ensure all pool imports occur automatically, a = simple edit to /etc/rc.d/zfs will suffice: diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs index 2d35f9b5464..8e4aef0b1b3 100755 --- a/libexec/rc/rc.d/zfs +++ b/libexec/rc/rc.d/zfs @@ -25,6 +25,13 @@ zfs_start_jail() =20 zfs_start_main() { + local cachefile + + for cachefile in /boot/zfs/zpool.cache /etc/zfs/zpool.cache; do + if [ -f $cachefile ]; then + zpool import -c $cachefile -a + fi + done zfs mount -va zfs share -a if [ ! -r /etc/zfs/exports ]; then This will probably not be needed long-term. It is not necessary if the = boot pool is the only pool. Happy testing :) - Ryan= From owner-freebsd-current@freebsd.org Fri Apr 17 19:18:24 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 B6B5F2C5B97 for ; Fri, 17 Apr 2020 19:18:24 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493m8b5Jz7z4W0T for ; Fri, 17 Apr 2020 19:18:23 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E2A5A456; Fri, 17 Apr 2020 15:18:21 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 15:18:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=4 Rk9dRwCcn4dnx52iPzntreiSeKmEcZ2Pq9HsPQbVKo=; b=Qk2XyCG8ewFg1uTKR Y1usF9VYn9kaR+czGtMjVqGKA+ScxtHoIkjTHr/lHU5elsI0h5bRq4CCdQQiY+6N 9FERjTFAFj3KG6RRdXIAiiQF4rUOL90o73kLKjHd6Gg5BrZbl236kcScjz1qbF0w JgyStL1i2wBkK3LXx2+l7hWrZi3h325rOc25cTcEsStV8IPjSAeeX2L1aRKK64Md Gxt6aikjCWL4w7y1s2hoyMS5xVni2xqu59dpNQYdGEEErHgwsNvE8xvBqdnwlNuv W1wXg33SvXW3GIlw5key6qZTQgf+bF3sogJQT//n0XjPqPV1dhOdyjXoujE94D1H gElhw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=4Rk9dRwCcn4dnx52iPzntreiSeKmEcZ2Pq9HsPQbV Ko=; b=B8loiBkJnKtTG2uvOS1KfnY2cJMB4aPvz4Ugj8ER1q4V+YG3BTYbkxBwI V8biirYOZKhmvXKdN0U7K0XAswHRuC02vk4bZQdkKHP9NBBkzOnUhmpBuNmNCblc gHdn5MmPlMIDzhLjdIdbdtdsG3aqssJaY4QJaVfjI8pjt75qEJ41UT3ifm7jUK2L TRMxlR0dadf/0G7NUJYlSjM4oigvqYaDjJpdAOFMlcZQw+vrY6nBCuLbHk35FwDR anqilXU2FUOHhuTU0Rw/Lhtgv529MpfjgC2VpTd89o998Q4/p7oWwq08n/jVoXdi x5czSf9wyX9wDSTSXnw0j4Zzy4p4g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgddufeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpefutghothhtucfnohhnghcuoehstghothhtlhesshgrmhhs tghordhorhhgqeenucfkphepkedrgeeirdekledrvddufeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehstghothhtlhesshgrmhhstghordho rhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id B2170306005C; Fri, 17 Apr 2020 15:18:20 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> Date: Fri, 17 Apr 2020 13:18:20 -0600 Cc: Warner Losh , FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493m8b5Jz7z4W0T X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=Qk2XyCG8; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=B8loiBkJ; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.87), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 19:18:24 -0000 > On Apr 17, 2020, at 11:46 AM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Scott Long wrote on 04/17/2020 18:17: >> You are correct about Intel vs AMD. Comparing the full output of = pciconf from FreeBSD with the fragment of lspci from Linux suggests that = there=E2=80=99s at least one set of a PCIe switch and child devices that = is not being enumerated by FreeBSD. Can you send the full output of = `lspci -tvv` from linux? >=20 > Sorry for my late reply. Booting the Linux SystemRescueCd is too slow. >=20 > lspci -tvv output is attached >=20 > I tried to connect to SOL by SSH but it shows black screen only. >=20 > lspci shows drives: >=20 > Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] >=20 > Kind regards > Miroslav Lachman >=20 It looks like pcib12 and pcib13 in FreeBSD should be the bridges that = have the NVMe devices behind them, but those devices aren=E2=80=99t = showing up. I don=E2=80=99t see any obvious code in linux to handle = those bridges, so there must be something subtle that we=E2=80=99re = missing in FreeBSD. Maybe we=E2=80=99re having trouble enumerating = above PCI bus 128? I think that was a problem a few years ago but I = also thought it was fixed. Can you do the following in FreeBSD: pciconf -lBc pcib12 pciconf -lBc pcib13 Thanks, Scott From owner-freebsd-current@freebsd.org Fri Apr 17 19:42:00 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 232632C6B37 for ; Fri, 17 Apr 2020 19:42:00 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493mgq0Jvnz4YS1 for ; Fri, 17 Apr 2020 19:41:58 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7660828433; Fri, 17 Apr 2020 21:41:56 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 7510B28434; Fri, 17 Apr 2020 21:41:55 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: Warner Losh , FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Fri, 17 Apr 2020 21:41:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> X-Rspamd-Queue-Id: 493mgq0Jvnz4YS1 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.01 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.996,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(0.81)[ip: (0.27), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.58), country: CZ(0.09)]; NEURAL_SPAM_LONG(1.00)[1.000,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 19:42:00 -0000 Scott Long wrote on 04/17/2020 21:18: > > >> On Apr 17, 2020, at 11:46 AM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> Scott Long wrote on 04/17/2020 18:17: >>> You are correct about Intel vs AMD. Comparing the full output of pciconf from FreeBSD with the fragment of lspci from Linux suggests that there’s at least one set of a PCIe switch and child devices that is not being enumerated by FreeBSD. Can you send the full output of `lspci -tvv` from linux? >> >> Sorry for my late reply. Booting the Linux SystemRescueCd is too slow. >> >> lspci -tvv output is attached >> >> I tried to connect to SOL by SSH but it shows black screen only. >> >> lspci shows drives: >> >> Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] >> >> Kind regards >> Miroslav Lachman >> > > It looks like pcib12 and pcib13 in FreeBSD should be the bridges that have the NVMe devices behind them, but those devices aren’t showing up. I don’t see any obvious code in linux to handle those bridges, so there must be something subtle that we’re missing in FreeBSD. Maybe we’re having trouble enumerating above PCI bus 128? I think that was a problem a few years ago but I also thought it was fixed. Can you do the following in FreeBSD: > > pciconf -lBc pcib12 > pciconf -lBc pcib13 Printscreen attached. Anything else I can provide? Thank you Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 19:44: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 D37872C6D3A for ; Fri, 17 Apr 2020 19:44:44 +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) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493ml037WTz4Yly for ; Fri, 17 Apr 2020 19:44:44 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD)) (envelope-from ) id 1jPWud-0004SE-1V; Fri, 17 Apr 2020 21:44:31 +0200 Date: Fri, 17 Apr 2020 21:44:31 +0200 From: Kurt Jaeger To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Scott Long , Warner Losh , FreeBSD-Current Subject: Re: PCIe NVME drives not detected on Dell R6515 Message-ID: <20200417194431.GD39563@home.opsec.eu> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 493ml037WTz4Yly X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.88 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.90)[-0.904,0]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; NEURAL_HAM_LONG(-0.97)[-0.972,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 19:44:44 -0000 Hi! > > pciconf -lBc pcib12 > > pciconf -lBc pcib13 > > Printscreen attached. Attachments are stripped from the list -- can you put them somewhere online ? -- pi@opsec.eu +49 171 3101372 Now what ? From owner-freebsd-current@freebsd.org Fri Apr 17 19:47: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 9C9202C6F5A for ; Fri, 17 Apr 2020 19:47:59 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493mpk5FBZz4Z3S; Fri, 17 Apr 2020 19:47:58 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 63E0A28416; Fri, 17 Apr 2020 21:47:57 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 4CB3128434; Fri, 17 Apr 2020 21:47:56 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Kurt Jaeger Cc: Scott Long , Warner Losh , FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> Date: Fri, 17 Apr 2020 21:47:55 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <20200417194431.GD39563@home.opsec.eu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 493mpk5FBZz4Z3S X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; IP_SCORE(0.81)[ip: (0.26), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.57), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.991,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 19:47:59 -0000 Kurt Jaeger wrote on 04/17/2020 21:44: > Hi! > >>> pciconf -lBc pcib12 >>> pciconf -lBc pcib13 >> >> Printscreen attached. > > Attachments are stripped from the list -- can you put them somewhere > online ? Here it is https://ibb.co/c1dZrTf Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 20:14: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 01C812C7AD6; Fri, 17 Apr 2020 20:14:45 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493nPc1sGXz4cJM; Fri, 17 Apr 2020 20:14:44 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (unknown [IPv6:2602:41:642b:600::6]) (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 "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id 9C6BC38D28; Fri, 17 Apr 2020 20:14:37 +0000 (UTC) Received: from [IPv6:2602:41:642b:630:6c16:8993:6207:3a64] (unknown [IPv6:2602:41:642b:630:6c16:8993:6207:3a64]) by chombo.houseloki.net (Postfix) with ESMTPSA id B9C9F17B7; Fri, 17 Apr 2020 13:14:36 -0700 (PDT) Subject: Re: OpenZFS port updated To: Ryan Moeller , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: From: Mel Pilgrim Message-ID: Date: Fri, 17 Apr 2020 13:14:36 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493nPc1sGXz4cJM X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 2607:f740:c::4ae as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-5.64 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bluerosetech.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-3.34)[ip: (-8.60), ipnet: 2607:f740:c::/48(-4.22), asn: 36236(-3.81), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:c::/48, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:14:45 -0000 On 2020-04-17 11:35, Ryan Moeller wrote: > The FreeBSD platform support in OpenZFS does not yet include all > features present in FreeBSD’s ZFS. Some notable changes/missing > features include: [...] > * pre-mountroot zpool.cache loading (for automatic pool imports) > > To the last point, this mainly effects the case where / is on ZFS and > /boot is not or is on a different pool. OpenZFS cannot handle this > case yet, but work is in progress to cover that use case. Booting > directly from ZFS does work. To be clear, this means OpenZFS currently does not support / on GELI-encrypted disks, correct? From owner-freebsd-current@freebsd.org Fri Apr 17 20:15: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 676712C7D36; Fri, 17 Apr 2020 20:15:48 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493nQq4Sfyz4cd5; Fri, 17 Apr 2020 20:15:47 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 1493475A; Fri, 17 Apr 2020 16:15:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 16:15:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=I 5DOPajtPdJLr1Ijxwf3nO45bOWxaNJ6kZwdUHpMZrs=; b=ldBChjFnzttkQ4Xra xIfqV6sM3hvXVY/Tttjgncj0R3Nbgf8fQxyni3baZ+9rz72x8tHEWlxyfBCyyyoE IilEtXwwLL3LEmuaLqFzScIN+Gd1O3tgpF7abIowqiGxkOe7XX7KY8RqAjlJLBro EzdK/KQy5W9D28sJhzQyRzXJqBEKLln5EhnuXRCyWFfdpnGWhnyzxfYf49b2pAE5 HfOP8uAlOLQlOpeDh4xZJkX0pgAJ1wRKjytiZZdoub7wE8/sIcdbmpix+JdKsthG +OyEr5CDGTF2OV+2BqB7f7WpA1hHaTGJY99lW3wHBK57T6eRQOXSsllhtd9XTjJJ bqJEg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=I5DOPajtPdJLr1Ijxwf3nO45bOWxaNJ6kZwdUHpMZ rs=; b=GQhwX/fYHVD16GtJ0i+5QaKUOQatwfToeaN5I/jmFumj+LZGIVKyPeo7d RiteIs5wXm166bfjzVDdswFVDZXnxMtcoRMEU0cKUDTEWW92dYkhYUP+ggVzaUku UxgeqVTLEkInipKs20aJ/wHemNSg/ursjq1oKBOXdjE7fNOV6RGSCu0y05zNqf5+ 53YZh5yBl5mIeV3ois1LXx0zTmXsrqUUpCW6tSA0i1UL2n5XzuD2VC+Bb+5y9UTp ONVjK8WrDQimg/0kCNQtNwxNdCLCg2a99n1Os7XjqLAfl44YDQq/TJhP67Ad4pEE hUUDjZxRlsFVSOekTPAFo9ILZmAcg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgddugeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpefutghothhtucfnohhnghcuoehstghothhtlhesshgrmhhs tghordhorhhgqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucfkphepkedrge eirdekledrvddufeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehstghothhtlhesshgrmhhstghordhorhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id 3D8A13280069; Fri, 17 Apr 2020 16:15:45 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: OpenZFS port updated From: Scott Long In-Reply-To: Date: Fri, 17 Apr 2020 14:15:44 -0600 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6333818E-63DA-4851-8496-9B0CE82145A3@samsco.org> References: To: Ryan Moeller X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493nQq4Sfyz4cd5 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=ldBChjFn; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=GQhwX/fY; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; DMARC_NA(0.00)[samsco.org]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(-3.50)[ip: (-9.86), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:15:48 -0000 Is the intention to eventually replace the zfs code in src/ ? What will = be the long-term relationship between src/ and ports/ for this? Scott > On Apr 17, 2020, at 12:35 PM, Ryan Moeller = wrote: >=20 > FreeBSD support has been merged into the master branch of the = openzfs/zfs repository, and the FreeBSD ports have been switched to this = branch. >=20 > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption > * improved TRIM implementation > * most recently, persistent L2ARC >=20 > Of course, avoid upgrading your pools if you want to keep the option = to go back to the base ZFS. >=20 > OpenZFS can be installed alongside the base ZFS. Change your = loader.conf entry to openzfs_load=3D=E2=80=9CYES=E2=80=9D to load the = OpenZFS module at boot, and set PATH to find the tools in = /usr/local/sbin before /sbin. The base zfs tools are still basically = functional with the OpenZFS module, so changing PATH in rc is not = strictly necessary. >=20 > The FreeBSD loader can boot from pools with the encryption feature = enabled, but the root/bootenv datasets must not be encrypted themselves. >=20 > The FreeBSD platform support in OpenZFS does not yet include all = features present in FreeBSD=E2=80=99s ZFS. Some notable changes/missing = features include: > * many sysctl names have changed (legacy compat sysctls should be = added at some point)=20 > * zfs send progress reporting in process title via setproctitle > * extended 'zfs holds -r' = (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D290015) > * vdev ashift optimizations = (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D254591) > * pre-mountroot zpool.cache loading (for automatic pool imports) >=20 > To the last point, this mainly effects the case where / is on ZFS and = /boot is not or is on a different pool. OpenZFS cannot handle this case = yet, but work is in progress to cover that use case. Booting directly = from ZFS does work. >=20 > If there are pools that need to be imported at boot other than the = boot pool, OpenZFS does not automatically import yet, and it uses = /etc/zfs/zpool.cache rather than /boot/zfs/zpool.cache to keep track of = imported pools. To ensure all pool imports occur automatically, a = simple edit to /etc/rc.d/zfs will suffice: >=20 > diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs > index 2d35f9b5464..8e4aef0b1b3 100755 > --- a/libexec/rc/rc.d/zfs > +++ b/libexec/rc/rc.d/zfs > @@ -25,6 +25,13 @@ zfs_start_jail() >=20 > zfs_start_main() > { > + local cachefile > + > + for cachefile in /boot/zfs/zpool.cache /etc/zfs/zpool.cache; do > + if [ -f $cachefile ]; then > + zpool import -c $cachefile -a > + fi > + done > zfs mount -va > zfs share -a > if [ ! -r /etc/zfs/exports ]; then >=20 > This will probably not be needed long-term. It is not necessary if the = boot pool is the only pool. >=20 > Happy testing :) >=20 > - Ryan > _______________________________________________ > 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 Fri Apr 17 20:17: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 140EE2A8177 for ; Fri, 17 Apr 2020 20:17:36 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493nSv0kDbz4d4G; Fri, 17 Apr 2020 20:17:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id BC6CD6C6; Fri, 17 Apr 2020 16:17:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 16:17:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=/ yAUsNeAgPNNyoLi0erlSqpoa3rNk0J17cthr6SHOg8=; b=lWQfYX8Grf+LzcYwb i010mwk+dRjQL8U8kNBrlduN0/t52vHGUsPIKfIVo06HqliyPZsQG2uJAXwYjB6K Pifsn0V1w3soghVks/l/VM/mOXeTBVaVuDpNooYXhJ+k0ZAfjxmDQNwivVXeXJZq zZSuo7i0yNhZa8IoBltOLeQ2xUCj+rYjlZ8U24L0jT2+qJr7TEBUR0kGI/DZ717a Qj04kH57bpD5mMRI4zspQSrwRpaljr08eojshEKUh/xWtcM8Idz4kCLecKyI8YMJ 9cVIOSKlzWZdjTvngb3IK6iXMWl/F2YNGUh0l/b9xwun1ZuLgO/eBzQoxi9E/gw6 7mzng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=/yAUsNeAgPNNyoLi0erlSqpoa3rNk0J17cthr6SHO g8=; b=Oa1iH2pTal4lErJ6RzOkScUyZPmXAemrrqxLAb7rwNyIHECV/p88QPuEi s7DhEC2EfoUTgCVjPRkByEhJ6PZnYEuNG718yhNmpCbDwL2XgBziWKuxmlSnT6WN +9nTscX2QQ4va9byj/vmpuRT1Ef8TtgJu7G3WVKQB9XvWHVM+kP2csqe8Ky3HlYt qazGjnXZU0AirQuzRYGRMF37S8fh6IjYWCVInALxc8PwU8evYeccbrKNz4pdwB2P zkNg2psxsIWNtSdn9A4+yxf4YmxAWOgwZqT+XQCoQ4/xHquJgrxUcrsZ5SMMSHVh S3mUD8u6wYJyoMoyKouT8WROzEyiQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgddugeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffohhmrghinhculdegledmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepufgtohht thcunfhonhhguceoshgtohhtthhlsehsrghmshgtohdrohhrgheqnecuffhomhgrihhnpe hisggsrdgtohenucfkphepkedrgeeirdekledrvddufeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehstghothhtlhesshgrmhhstghordhorh hg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id 84F6E3280064; Fri, 17 Apr 2020 16:17:32 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> Date: Fri, 17 Apr 2020 14:17:32 -0600 Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493nSv0kDbz4d4G X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=lWQfYX8G; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=Oa1iH2pT; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.86), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:17:36 -0000 > On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Kurt Jaeger wrote on 04/17/2020 21:44: >> Hi! >>>> pciconf -lBc pcib12 >>>> pciconf -lBc pcib13 >>>=20 >>> Printscreen attached. >> Attachments are stripped from the list -- can you put them somewhere >> online ? >=20 > Here it is https://ibb.co/c1dZrTf >=20 > Miroslav Lachman >=20 Ok, the bridges know about their downstream bus numbers, but I see = nothing that suggests that they=E2=80=99re being probed. The next step = would be bootverbose, but that=E2=80=99s going to be a lot of output to = collect in screen captures. Scott From owner-freebsd-current@freebsd.org Fri Apr 17 20:31:24 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 CF23D2A8B5D; Fri, 17 Apr 2020 20:31:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493nmr5CxTz4fY0; Fri, 17 Apr 2020 20:31:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) (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 A65A810ABA; Fri, 17 Apr 2020 20:31:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f181.google.com with SMTP id c16so3167079qtv.1; Fri, 17 Apr 2020 13:31:24 -0700 (PDT) X-Gm-Message-State: AGi0PuYIQMdkyALY4uIyTlX70FwpdSjRzBYfYLVsiXUXW2swYT9Y+uaN am+P2SZrLafuyLTzbSZsWbokT+HVRl45AvNewpQ= X-Google-Smtp-Source: APiQypImNWurV+3om2JQHeW4BQLPqd6ythV5w88KW8URIuD3X/v16/MWlyk3a480GvbCSeGEbF2aFl8tVm6P2+aurns= X-Received: by 2002:ac8:4254:: with SMTP id r20mr4711204qtm.211.1587155484292; Fri, 17 Apr 2020 13:31:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Fri, 17 Apr 2020 15:31:10 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: OpenZFS port updated To: Mel Pilgrim Cc: Ryan Moeller , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:31:24 -0000 On Fri, Apr 17, 2020 at 3:14 PM Mel Pilgrim wrote: > > On 2020-04-17 11:35, Ryan Moeller wrote: > > The FreeBSD platform support in OpenZFS does not yet include all > > features present in FreeBSD=E2=80=99s ZFS. Some notable changes/missing > > features include: > [...] > > * pre-mountroot zpool.cache loading (for automatic pool imports) > > > > To the last point, this mainly effects the case where / is on ZFS and > > /boot is not or is on a different pool. OpenZFS cannot handle this > > case yet, but work is in progress to cover that use case. Booting > > directly from ZFS does work. > > To be clear, this means OpenZFS currently does not support / on > GELI-encrypted disks, correct? If you have a legacy setup with a bootpool, that is correct. Since 12.0+ the bootpool is almost completely redundant except for some odd setup that I can never remember. For legacy setups, the bootpool can/should be merged into your root pool if it's feasible. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Fri Apr 17 20:34:52 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 2986B2A921B; Fri, 17 Apr 2020 20:34:52 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id 493nrq1TGtz4gKm; Fri, 17 Apr 2020 20:34:50 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.30] ([194.32.164.30]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 03HKYnkC014447; Fri, 17 Apr 2020 21:34:49 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: OpenZFS port updated From: Bob Bishop In-Reply-To: Date: Fri, 17 Apr 2020 21:34:49 +0100 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Ryan Moeller X-Mailer: Apple Mail (2.3273) X-Rspamd-Queue-Id: 493nrq1TGtz4gKm X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rb@gid.co.uk designates 194.32.164.250 as permitted sender) smtp.mailfrom=rb@gid.co.uk X-Spamd-Result: default: False [-2.21 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; DMARC_NA(0.00)[gid.co.uk]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.51)[ip: (-1.85), ipnet: 194.32.164.0/24(-0.93), asn: 42831(0.29), country: GB(-0.07)]; RCVD_IN_DNSWL_NONE(0.00)[250.164.32.194.list.dnswl.org : 127.0.10.0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42831, ipnet:194.32.164.0/24, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:34:52 -0000 Hi, > On 17 Apr 2020, at 19:35, Ryan Moeller wrote: >=20 > FreeBSD support has been merged into the master branch of the = openzfs/zfs repository, and the FreeBSD ports have been switched to this = branch. >=20 > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption > * improved TRIM implementation [etc] Note that unlike native ZFS, OpenZFS doesn=E2=80=99t (last time I = looked) support autotrim by default - you have to enable it explicitly. -- Bob Bishop rb@gid.co.uk From owner-freebsd-current@freebsd.org Fri Apr 17 20:45: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 EFE062A9BAA for ; Fri, 17 Apr 2020 20:45:15 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493p4q0sqnz3Crp; Fri, 17 Apr 2020 20:45:14 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5B9A228433; Fri, 17 Apr 2020 22:45:12 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 95FB728416; Fri, 17 Apr 2020 22:45:10 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Fri, 17 Apr 2020 22:45:09 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493p4q0sqnz3Crp X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; IP_SCORE(0.81)[ip: (0.26), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.57), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.989,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:45:16 -0000 Scott Long wrote on 04/17/2020 22:17: > > >> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> Kurt Jaeger wrote on 04/17/2020 21:44: >>> Hi! >>>>> pciconf -lBc pcib12 >>>>> pciconf -lBc pcib13 >>>> >>>> Printscreen attached. >>> Attachments are stripped from the list -- can you put them somewhere >>> online ? >> >> Here it is https://ibb.co/c1dZrTf >> >> Miroslav Lachman >> > > Ok, the bridges know about their downstream bus numbers, but I see nothing that suggests that they’re being probed. The next step would be bootverbose, but that’s going to be a lot of output to collect in screen captures. Over 3000 lines long but I finally managed to make SOL work so I have it as text! https://pastebin.pl/view/90fdaafb Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 20:56: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 382442AA1A1; Fri, 17 Apr 2020 20:56:45 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493pL34DY3z3DhS; Fri, 17 Apr 2020 20:56:43 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.206] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 8cf77812 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 17 Apr 2020 20:56:36 +0000 (UTC) Subject: Re: OpenZFS port updated To: Ryan Moeller , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: From: Pete Wright Message-ID: <6b25375d-0945-f01e-264e-ee410195fa97@nomadlogic.org> Date: Fri, 17 Apr 2020 13:56:31 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.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: 493pL34DY3z3DhS X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.07 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; IP_SCORE(-2.77)[ip: (-9.24), ipnet: 174.136.96.0/20(-4.15), asn: 25795(-0.42), country: US(-0.05)]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 20:56:45 -0000 On 4/17/20 11:35 AM, Ryan Moeller wrote: > FreeBSD support has been merged into the master branch of the openzfs/zfs repository, and the FreeBSD ports have been switched to this branch. Congratulations on this effort - big milestone! > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption Is there a good doc reference on available for using this?  I believe this is zfs filesystem level encryption and not a replacement for our existing full-disk-encryption scheme that currently works? thanks again! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Fri Apr 17 21:07:42 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 2A9EB2AA846 for ; Fri, 17 Apr 2020 21:07:42 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493pZj3gl2z3FfY; Fri, 17 Apr 2020 21:07:41 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E4C8828434; Fri, 17 Apr 2020 23:07:39 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A0C3128433; Fri, 17 Apr 2020 23:07:38 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> Date: Fri, 17 Apr 2020 23:07:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493pZj3gl2z3FfY X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; IP_SCORE(0.81)[ip: (0.26), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.57), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.990,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:07:42 -0000 Scott Long wrote on 04/17/2020 23:04: > > >> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> Scott Long wrote on 04/17/2020 22:17: >>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >>>> >>>> Kurt Jaeger wrote on 04/17/2020 21:44: >>>>> Hi! >>>>>>> pciconf -lBc pcib12 >>>>>>> pciconf -lBc pcib13 >>>>>> >>>>>> Printscreen attached. >>>>> Attachments are stripped from the list -- can you put them somewhere >>>>> online ? >>>> >>>> Here it is https://ibb.co/c1dZrTf >>>> >>>> Miroslav Lachman >>>> >>> Ok, the bridges know about their downstream bus numbers, but I see nothing that suggests that they’re being probed. The next step would be bootverbose, but that’s going to be a lot of output to collect in screen captures. >> >> Over 3000 lines long but I finally managed to make SOL work so I have it as text! >> >> https://pastebin.pl/view/90fdaafb >> > > This helped a lot, thanks. It looks like these PCIe buses are marked as being hotplug, and for some reason we’re not probing them. At this point, I’d need to feed you some kernel patches that will dump out more info, but you’d have to compile them and get them onto your boot media. Is that a possibility? Currently I have all machines on 11.3 (where I can rebuild kernel without problem) If CURRENT is required I would need to setup some CURRENT VM in VirtualBox. Can you send me some link to documentation who should I create new ISO after rebuild? Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 21:13:09 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 E94932AACA8 for ; Fri, 17 Apr 2020 21:13:09 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493pj06TMfz3GQw; Fri, 17 Apr 2020 21:13:08 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 241833C1; Fri, 17 Apr 2020 17:04:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 17:04:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=d eBdkAZ83po+XNviAHcBkF3W5s08QpD9T8Fdll65hHg=; b=R0jOgvKz1ApJ9A//Z 9J6XgnvlpkLOIzF1BH36Mww/2gXYBLLvaCXJheXzU7v96BVzh/k9AFqCo4CTRbjx djWorryIvoSOT86nImzSH42QoUhY9eafjnXd7v5eZyg0VkTVlxLpwVXvRsTdgjiQ A5M2MYMrBHaYIC3z2sNZ8OnqPgNY65HAQh/b1DXZosObievgKyTOW3ui+f0dUDmc QioSZQBJLHykFvoqdtZbAEGii23P/rJTIyPEWhf6s1BsIKU2L0qqQjYMOoHNuKHq CgmK0qxRLKO8UWui5sC7R9QWddkgkJFpCDvnRQKPmbljOqoKK7w7EkF92gahinNz 73qiw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=deBdkAZ83po+XNviAHcBkF3W5s08QpD9T8Fdll65h Hg=; b=S9E8Tq45Of/gMVvT+tGQxyNgp7U5pHe6awiZV40C+qLWbOnBkB5t29Szs TNCWybH6KzXmgY3XuZW1ddtNhvBqoIm7MKVJ1ttfgvCRU1oWHeLHz5Rk64dW8J/H BR9XjjT0zYa+fSh0htQmTU0HbIzJyhdFaV1MWpMEZ7CWc9pQvijnaQlL17PIP0Th U2brL7Co4RtVrhaGjnlQrSk7eTA5y9CwaVC4wl4RjcYuisY+ASC9lrXIlhiTbF4g voL0M7orXRH5zF+ZSseo6XYv4YrwsoFSVbqHPT6hI0IZo16pb96/17x+7QVTbki4 VsfvD/YnjtEacUbvKFjmeNH595Gfw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdduheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffohhmrghinhculdegledmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepufgtohht thcunfhonhhguceoshgtohhtthhlsehsrghmshgtohdrohhrgheqnecuffhomhgrihhnpe hisggsrdgtohdpphgrshhtvggsihhnrdhplhenucfkphepkedrgeeirdekledrvddufeen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehstghoth htlhesshgrmhhstghordhorhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id C8DA13280059; Fri, 17 Apr 2020 17:04:09 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: Date: Fri, 17 Apr 2020 15:04:09 -0600 Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493pj06TMfz3GQw X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=R0jOgvKz; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=S9E8Tq45; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.86), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:13:10 -0000 > On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Scott Long wrote on 04/17/2020 22:17: >>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >>>=20 >>> Kurt Jaeger wrote on 04/17/2020 21:44: >>>> Hi! >>>>>> pciconf -lBc pcib12 >>>>>> pciconf -lBc pcib13 >>>>>=20 >>>>> Printscreen attached. >>>> Attachments are stripped from the list -- can you put them = somewhere >>>> online ? >>>=20 >>> Here it is https://ibb.co/c1dZrTf >>>=20 >>> Miroslav Lachman >>>=20 >> Ok, the bridges know about their downstream bus numbers, but I see = nothing that suggests that they=E2=80=99re being probed. The next step = would be bootverbose, but that=E2=80=99s going to be a lot of output to = collect in screen captures. >=20 > Over 3000 lines long but I finally managed to make SOL work so I have = it as text! >=20 > https://pastebin.pl/view/90fdaafb >=20 This helped a lot, thanks. It looks like these PCIe buses are marked as = being hotplug, and for some reason we=E2=80=99re not probing them. At = this point, I=E2=80=99d need to feed you some kernel patches that will = dump out more info, but you=E2=80=99d have to compile them and get them = onto your boot media. Is that a possibility? Thanks, Scott From owner-freebsd-current@freebsd.org Fri Apr 17 21:13: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 078A82AAD31 for ; Fri, 17 Apr 2020 21:13:33 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [208.111.40.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493pjS1xfQz3GXT for ; Fri, 17 Apr 2020 21:13:32 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (65-100-43-2.dia.static.qwest.net [65.100.43.2]) (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 "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id 5F36C38D21; Fri, 17 Apr 2020 21:13:25 +0000 (UTC) Received: from [IPv6:2602:41:642b:630:6c16:8993:6207:3a64] (unknown [IPv6:2602:41:642b:630:6c16:8993:6207:3a64]) by chombo.houseloki.net (Postfix) with ESMTPSA id 9CEC417DB; Fri, 17 Apr 2020 14:13:24 -0700 (PDT) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Warner Losh , Scott Long Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> From: Mel Pilgrim Message-ID: <75286053-5501-8da5-976e-aad50405b864@bluerosetech.com> Date: Fri, 17 Apr 2020 14:13:24 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493pjS1xfQz3GXT X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 208.111.40.118 as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-5.45 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bluerosetech.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(-3.15)[ip: (-7.94), ipnet: 208.111.40.0/24(-3.97), asn: 36236(-3.81), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:208.111.40.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:13:33 -0000 On 2020-04-17 8:50, Warner Losh wrote: > On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: > >> Can you send me the output of ‘pciconf -llv’, either in 12-STABLE or >> 13-CURRENT? Also, can you send me the output of ‘dmesg’? >> > > There was another thread that said there was a raid card in the way... It > would be cool to find a way to get it out of the way... :) On the R6515, NVME drives are supported through a PERC S150 mini card. There's no m.2 slots or U.2 ports on the mainboard itself. The S150 supports non-RAID mode, but that still leaves supporting a software-based PERC card as a PCIe switch for the 8 or 10 NVME bays behind it. From owner-freebsd-current@freebsd.org Fri Apr 17 21:15: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 58C2E2AB083 for ; Fri, 17 Apr 2020 21:15:44 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493plz3KlYz3Gv7 for ; Fri, 17 Apr 2020 21:15:43 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id F13D371F; Fri, 17 Apr 2020 17:15:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 17:15:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=S GlXyQxy+9HXlYyL219dqYdkKQcPfbNJauvZZ1ncPEA=; b=jjKV6q/mWeYdiqiYD VGjokBxDbOUKGt5hsceKhbAiAvOM7P7KoN7FWAQT2L0YYDD2CTWNtmgNVeP1C6kr xtNJaANCk2f9mE44AlG7VBxswpaHPPjdy45sCSihOii3J5nBEBhLJ0OuoqiDLzYc 5v0nqxWEBd6+OHMPN9HtsTwVERHS4z4vYoKyaTCFANo0Rj+jnccOg2QmdH2nyVGl RGj2gq1zKgX92kqq55r/hAeKLOqqNyiMVkrZhFVAW+KM1zTyHoC77n8JRjSI4bXT YLGXk/y/LgIJuE24c9bwo6FMj33V8ss08PHE8gMru+ED9Pj92Ck1H4VK/ojwCuRN /Ksdg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=SGlXyQxy+9HXlYyL219dqYdkKQcPfbNJauvZZ1ncP EA=; b=wZHatNCvAJ/f1rxw+84EyNZ+ZCea8weyg/V7ciB5th3YKdHjPM5EWS/Mj HADqXRgYKI4dDfdVB85qJkj3iQypaMD3zfH/hBjHaOaCcXYpXzjtU2s9t5mmM6wh FfPhPDG1FkI/7BjrnQsaeJ/9xpeUWS4t5wgH4Uu5/FFjKo7i7U4OVYEnEnX+YYwo wz5kdSaIQuFql0kQHWxAaBLIBEB8g9JvFe3nEqVzkUIJ5Gp2LDAcFi1MDpyja87z PHcFEiqeZTICoE5xXh+1kZMuisOKUR8nPj3b0bJPGwonXcn2PJgEZlpioyEOsPZw Tsc6osf9jM8zJ0SMpiG3HG/JSsBig== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdduheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpefutghothhtucfnohhnghcuoehstghothhtlhesshgrmhhs tghordhorhhgqeenucfkphepkedrgeeirdekledrvddufeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehstghothhtlhesshgrmhhstghordho rhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id A79A3306005C; Fri, 17 Apr 2020 17:15:40 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: <75286053-5501-8da5-976e-aad50405b864@bluerosetech.com> Date: Fri, 17 Apr 2020 15:15:40 -0600 Cc: Warner Losh , Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <75286053-5501-8da5-976e-aad50405b864@bluerosetech.com> To: Mel Pilgrim X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493plz3KlYz3Gv7 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=jjKV6q/m; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=wZHatNCv; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.86), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:15:44 -0000 > On Apr 17, 2020, at 3:13 PM, Mel Pilgrim = wrote: >=20 > On 2020-04-17 8:50, Warner Losh wrote: >> On Fri, Apr 17, 2020 at 9:39 AM Scott Long wrote: >>> Can you send me the output of =E2=80=98pciconf -llv=E2=80=99, either = in 12-STABLE or >>> 13-CURRENT? Also, can you send me the output of =E2=80=98dmesg=E2=80=99= ? >>>=20 >> There was another thread that said there was a raid card in the = way... It >> would be cool to find a way to get it out of the way... :) > On the R6515, NVME drives are supported through a PERC S150 mini card. = There's no m.2 slots or U.2 ports on the mainboard itself. The S150 = supports non-RAID mode, but that still leaves supporting a = software-based PERC card as a PCIe switch for the 8 or 10 NVME bays = behind it. This doesn=E2=80=99t seem to be the case for Miroslav=E2=80=99s system. = There=E2=80=99s no special handling of the PCIe bridge/switch in linux = where it does work, and there=E2=80=99s growing evidence that this is a = case of FreeBSD not handling hotplug ports correctly. Scott From owner-freebsd-current@freebsd.org Fri Apr 17 21:30:41 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 463C82AB73F for ; Fri, 17 Apr 2020 21:30:41 +0000 (UTC) (envelope-from scottl@samsco.org) 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 493q5D22wQz3J3g; Fri, 17 Apr 2020 21:30:40 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id BAA2D514; Fri, 17 Apr 2020 17:30:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 17:30:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=T sF400PcsiqQ6OL/lqm7nqYiuvvrB3E2wnDRMNnPA40=; b=Wgs/JrG0WZvHFCyfw RxRb7EliIiyiUaPqE0twDUXKLGbJZrYPAMX3R7NVEOWv0hTXGHYidomhS3EqMHnW B1u5ZBnDKguZSiILwYb/hfUF+1IsPv8TTqQuAaqIFx2nwB/sKApEGcl93N2ZZGhP ozBsYOpqLIsQTNcI0ADf0cfFxR/kb/OtEIKM4yGtPaqJ7eo2iPRNll/pacznsbWR 3qzcMVCbOIhxZONhth1y7XaXcfzk+rbdrY7R7QVMOVe8D2V9YKaI0+P4N/OSYj4o zYDs20Ufcql91jU1O8ys7NNRpjOLm7RoeAHjeTuFO2+lLT231eIp2cxRPaXcsHt8 WnA0A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=TsF400PcsiqQ6OL/lqm7nqYiuvvrB3E2wnDRMNnPA 40=; b=qFwUYewzT1JCXJoP3HzUGvNT5ROMF1d2gLHS5x2X+OzmjKpCkB4OwVXPq TwIDS+k5t/fgAJrykhgHTwOJTxp471Dw5PrvWQrwpyXsarsFZPhP2JP7BoKooTLh Hoe/f54GEAumPdVSJMh+q40+JC5acUYPMJacg28/3F0slyRr5+tdmKfjp6i8YXF8 mgXX5kRffBgtauO745oSkpSmxrfLzxEbooaEysxkaSO0eSPM5pBAM8lCzlelVqPA 9Xz8Qh+GoLpzSJtTsTnNx7/+z/fer901C3V8dNlHMpXwJ5f8pQ3u3V+fhUJ8LLgZ qgb7IAWS/A1LVrb7anRXVwyZTD7bQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdduiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffohhmrghinhculdegledmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepufgtohht thcunfhonhhguceoshgtohhtthhlsehsrghmshgtohdrohhrgheqnecuffhomhgrihhnpe hisggsrdgtohdpphgrshhtvggsihhnrdhplhenucfkphepkedrgeeirdekledrvddufeen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehstghoth htlhesshgrmhhstghordhorhhg X-ME-Proxy: Received: from [192.168.0.114] (unknown [8.46.89.213]) by mail.messagingengine.com (Postfix) with ESMTPA id 914BF3280064; Fri, 17 Apr 2020 17:30:37 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: PCIe NVME drives not detected on Dell R6515 From: Scott Long In-Reply-To: <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> Date: Fri, 17 Apr 2020 15:30:37 -0600 Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current Content-Transfer-Encoding: quoted-printable Message-Id: <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org> References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 493q5D22wQz3J3g X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=Wgs/JrG0; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=qFwUYewz; dmarc=none; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; IP_SCORE(-3.50)[ip: (-9.86), ipnet: 64.147.123.0/24(-4.92), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[21.123.147.64.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:30:41 -0000 > On Apr 17, 2020, at 3:07 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Scott Long wrote on 04/17/2020 23:04: >>> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >>>=20 >>> Scott Long wrote on 04/17/2020 22:17: >>>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >>>>>=20 >>>>> Kurt Jaeger wrote on 04/17/2020 21:44: >>>>>> Hi! >>>>>>>> pciconf -lBc pcib12 >>>>>>>> pciconf -lBc pcib13 >>>>>>>=20 >>>>>>> Printscreen attached. >>>>>> Attachments are stripped from the list -- can you put them = somewhere >>>>>> online ? >>>>>=20 >>>>> Here it is https://ibb.co/c1dZrTf >>>>>=20 >>>>> Miroslav Lachman >>>>>=20 >>>> Ok, the bridges know about their downstream bus numbers, but I see = nothing that suggests that they=E2=80=99re being probed. The next step = would be bootverbose, but that=E2=80=99s going to be a lot of output to = collect in screen captures. >>>=20 >>> Over 3000 lines long but I finally managed to make SOL work so I = have it as text! >>>=20 >>> https://pastebin.pl/view/90fdaafb >>>=20 >> This helped a lot, thanks. It looks like these PCIe buses are marked = as being hotplug, and for some reason we=E2=80=99re not probing them. = At this point, I=E2=80=99d need to feed you some kernel patches that = will dump out more info, but you=E2=80=99d have to compile them and get = them onto your boot media. Is that a possibility? >=20 > Currently I have all machines on 11.3 (where I can rebuild kernel = without problem) > If CURRENT is required I would need to setup some CURRENT VM in = VirtualBox. >=20 > Can you send me some link to documentation who should I create new ISO = after rebuild? >=20 I don=E2=80=99t know of any docs for doing custom releases, and it looks = like it=E2=80=99s harder than it used to be to insert custom patches. = That said, I recommend doing the following on your 11.x build system: 1. Do a clean `make buildworld` with an up-to-date tree 2. change into the `release` directory that you just did the buildworld = from 3. `sudo make release NOPORTS=3D NODOC=3D CHROOTDIR=3D/usr/tmp/release = SRCBRANCH=3D"base/stable/11@rHEAD=E2=80=9D` You can set CHROOTDIR to whatever you want that has a few GB of space, = but remember where you=E2=80=99ve set it for later steps. This will = build a release with stock sources. Let it complete, both to prepare = for the next step and to ensure that it works. It=E2=80=99ll take an = hour or two depending on your machine speed 4. Take the patch that I=E2=80=99ll send you shortly and apply it to = $CHROOTDIR/usr/src 5. `sudo make memstick NOPORTS=3D NODOC=3D SRC_UPDATE_SKIP=3D = CHROOTDIR=3D/usr/tmp/release` Scott From owner-freebsd-current@freebsd.org Fri Apr 17 21:39:12 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 7C4012ABE1B for ; Fri, 17 Apr 2020 21:39:12 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 493qH30ygbz3K1w; Fri, 17 Apr 2020 21:39:10 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 42E515C01D1; Fri, 17 Apr 2020 17:39:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 17 Apr 2020 17:39:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=p BQ/vpdX3DNBjoLDzovYUi50DaHLqDJeWORqTcABKvE=; b=hpL8tLD59uK5eo7g6 K86hYlXLIW/P+O5AHd5UDmTJEiEViQZq8HlFRqTdSBiNcTsv9+SyQC4bQo/5j7tb t0JmPl/ORX7ljZIHhSIvivnDNNHb0R/da+10qxYTL/rJFTL45rB93asuHSty1mvZ p1WPk5MKHvNDCg4g7rAbyYeb2/V4MHWzD7X1nsN0eL8UzAKPEXd8ECT/RTdk5tIG yU0Wbbnd2Ck6Cz9XiVIXZJHT1ORezICBp6jxLrJ9vcWQRnWFhigUfLWerrim/TxW 1NH2sLU99e7A4Mqy9p/YZ0msmqs3BuNsfok6YIpTb2jKMoAqAAAh9Aw1ODtqX+CD SJM/w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=pBQ/vpdX3DNBjoLDzovYUi50DaHLqDJeWORqTcABK vE=; b=fE2troxDTD+Cc52Bwtlph98phvEYVSXYgT5RpHxuJbKt1TAIA5xlWJTpI S2h4+EUVsgqKlQXySz97GnkRPBSrWAzmR/CSUmG1tM08qpeBEIzkYP91Mtf6uRgI lW6TBZB722HrC5NOI573yreFKQYF8Rau0e9z6v7/PViUW2Fvj+NQySBiumsK5jgL l0BgmCb5jGglgHHf0x7r8CHvPDVXn6rB2b6I/WmmuZST0gHPeV9AFqyYxUmWDV0a eFoO5z/16+qkiBnI20imVeapUwF0fLjL4RhO3ko1kh5c+oHko3EwO3tPOzBVGYQf xXMv2zPfeiu3n+cvqDrYOF/n/2KxA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeejgdduieefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne goufhushhpvggtthffohhmrghinhculdegledmnecujfgurhepuffvfhfhkffffgggjggt gfesthekredttdefjeenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihphgrnhhkoh hvsehfrghsthhmrghilhdrtghomheqnecuffhomhgrihhnpehisggsrdgtohdpphgrshht vggsihhnrdhplhenucfkphepkeehrddujeehrddufeelrddvhedunecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihprghnkhhovhesfhgrshht mhgrihhlrdgtohhm X-ME-Proxy: Received: from [192.168.1.6] (unknown [85.175.139.251]) by mail.messagingengine.com (Postfix) with ESMTPA id EAA24328005E; Fri, 17 Apr 2020 17:39:06 -0400 (EDT) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long , Miroslav Lachman <000.fbsd@quip.cz> Cc: Kurt Jaeger , Warner Losh , FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org> From: Yuri Pankov Message-ID: Date: Sat, 18 Apr 2020 00:39:06 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493qH30ygbz3K1w X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fastmail.com header.s=fm2 header.b=hpL8tLD5; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=fE2troxD; dmarc=pass (policy=none) header.from=fastmail.com; spf=pass (mx1.freebsd.org: domain of ypankov@fastmail.com designates 66.111.4.27 as permitted sender) smtp.mailfrom=ypankov@fastmail.com X-Spamd-Result: default: False [-3.10 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[fastmail.com:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; FREEMAIL_FROM(0.00)[fastmail.com]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[fastmail.com:+,messagingengine.com:+]; DMARC_POLICY_ALLOW(-0.50)[fastmail.com,none]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[27.4.111.66.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[fastmail.com]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.83), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)]; RECEIVED_SPAMHAUS_PBL(0.00)[251.139.175.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:39:12 -0000 Scott Long wrote: > > >> On Apr 17, 2020, at 3:07 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> Scott Long wrote on 04/17/2020 23:04: >>>> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >>>> >>>> Scott Long wrote on 04/17/2020 22:17: >>>>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >>>>>> >>>>>> Kurt Jaeger wrote on 04/17/2020 21:44: >>>>>>> Hi! >>>>>>>>> pciconf -lBc pcib12 >>>>>>>>> pciconf -lBc pcib13 >>>>>>>> >>>>>>>> Printscreen attached. >>>>>>> Attachments are stripped from the list -- can you put them somewhere >>>>>>> online ? >>>>>> >>>>>> Here it is https://ibb.co/c1dZrTf >>>>>> >>>>>> Miroslav Lachman >>>>>> >>>>> Ok, the bridges know about their downstream bus numbers, but I see nothing that suggests that they’re being probed. The next step would be bootverbose, but that’s going to be a lot of output to collect in screen captures. >>>> >>>> Over 3000 lines long but I finally managed to make SOL work so I have it as text! >>>> >>>> https://pastebin.pl/view/90fdaafb >>>> >>> This helped a lot, thanks. It looks like these PCIe buses are marked as being hotplug, and for some reason we’re not probing them. At this point, I’d need to feed you some kernel patches that will dump out more info, but you’d have to compile them and get them onto your boot media. Is that a possibility? >> >> Currently I have all machines on 11.3 (where I can rebuild kernel without problem) >> If CURRENT is required I would need to setup some CURRENT VM in VirtualBox. >> >> Can you send me some link to documentation who should I create new ISO after rebuild? >> > > I don’t know of any docs for doing custom releases, and it looks like it’s harder than it used to be to insert custom patches. That said, I recommend doing the following on your 11.x build system: > > 1. Do a clean `make buildworld` with an up-to-date tree > 2. change into the `release` directory that you just did the buildworld from > 3. `sudo make release NOPORTS= NODOC= CHROOTDIR=/usr/tmp/release SRCBRANCH="base/stable/11@rHEAD”` > > You can set CHROOTDIR to whatever you want that has a few GB of space, but remember where you’ve set it for later steps. This will build a release with stock sources. Let it complete, both to prepare for the next step and to ensure that it works. It’ll take an hour or two depending on your machine speed > > 4. Take the patch that I’ll send you shortly and apply it to $CHROOTDIR/usr/src > 5. `sudo make memstick NOPORTS= NODOC= SRC_UPDATE_SKIP= CHROOTDIR=/usr/tmp/release` Just a thought - it could possibly be easier to build just the patched kernel and try booting it (11.3 userland should work with CURRENT kernel, right?), doing the kernel-toolchaing target first, and using INSTKERNNAME with the installkernel target to temporary select it from loader menu. From owner-freebsd-current@freebsd.org Fri Apr 17 21:40: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 4A5342ABFE5; Fri, 17 Apr 2020 21:40:26 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493qJT1Lbjz3KF0; Fri, 17 Apr 2020 21:40:25 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (65-100-43-2.dia.static.qwest.net [65.100.43.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id AA49638D28; Fri, 17 Apr 2020 21:40:23 +0000 (UTC) Received: from [IPv6:2602:41:642b:630:6c16:8993:6207:3a64] (unknown [IPv6:2602:41:642b:630:6c16:8993:6207:3a64]) by chombo.houseloki.net (Postfix) with ESMTPSA id 2AF9017F4; Fri, 17 Apr 2020 14:40:23 -0700 (PDT) Subject: Re: OpenZFS port updated To: Kyle Evans Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , Ryan Moeller References: From: Mel Pilgrim Message-ID: <8abb14b2-7426-559d-af7e-c339fa130515@bluerosetech.com> Date: Fri, 17 Apr 2020 14:40:23 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 493qJT1Lbjz3KF0 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 2607:f740:c::4ae as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-5.65 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx:relay3.brtsvcs.net]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bluerosetech.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-3.35)[ip: (-8.66), ipnet: 2607:f740:c::/48(-4.25), asn: 36236(-3.81), country: US(-0.05)]; TO_DN_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:c::/48, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:40:26 -0000 On 2020-04-17 13:31, Kyle Evans wrote: > On Fri, Apr 17, 2020 at 3:14 PM Mel Pilgrim > wrote: >> >> On 2020-04-17 11:35, Ryan Moeller wrote: >>> The FreeBSD platform support in OpenZFS does not yet include all >>> features present in FreeBSD’s ZFS. Some notable changes/missing >>> features include: >> [...] >>> * pre-mountroot zpool.cache loading (for automatic pool imports) >>> >>> To the last point, this mainly effects the case where / is on ZFS and >>> /boot is not or is on a different pool. OpenZFS cannot handle this >>> case yet, but work is in progress to cover that use case. Booting >>> directly from ZFS does work. >> >> To be clear, this means OpenZFS currently does not support / on >> GELI-encrypted disks, correct? > > If you have a legacy setup with a bootpool, that is correct. Since > 12.0+ the bootpool is almost completely redundant except for some odd > setup that I can never remember. For legacy setups, the bootpool > can/should be merged into your root pool if it's feasible. Yes, these are the "legacy" configuration with a small, unecrypted pool containing /boot and the keys to attach the encrypted root pool. Could the case you're thinking of be avoiding manual entry of a password at boot? From owner-freebsd-current@freebsd.org Fri Apr 17 21:54: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 016422ACEFE; Fri, 17 Apr 2020 21:54:15 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493qcQ5yKmz3Lk6; Fri, 17 Apr 2020 21:54:14 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) Received: from [IPv6:2600:1700:358a:c660:305b:9aa6:7c2d:c818] (unknown [IPv6:2600:1700:358a:c660:305b:9aa6:7c2d:c818]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: freqlabs/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id A4B87114B0; Fri, 17 Apr 2020 21:54:14 +0000 (UTC) (envelope-from freqlabs@FreeBSD.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: OpenZFS port updated From: Ryan Moeller In-Reply-To: <6b25375d-0945-f01e-264e-ee410195fa97@nomadlogic.org> Date: Fri, 17 Apr 2020 17:54:14 -0400 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0ED41E6B-9C57-405B-84BE-1161F012A974@FreeBSD.org> References: <6b25375d-0945-f01e-264e-ee410195fa97@nomadlogic.org> To: Pete Wright X-Mailer: Apple Mail (2.3608.80.23.2.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 21:54:15 -0000 > On Apr 17, 2020, at 4:56 PM, Pete Wright wrote: >=20 > On 4/17/20 11:35 AM, Ryan Moeller wrote: >> FreeBSD support has been merged into the master branch of the = openzfs/zfs repository, and the FreeBSD ports have been switched to this = branch. > Congratulations on this effort - big milestone! >> OpenZFS brings many exciting features to FreeBSD, including: >> * native encryption > Is there a good doc reference on available for using this? I believe = this is zfs filesystem level encryption and not a replacement for our = existing full-disk-encryption scheme that currently works? I=E2=80=99m not aware of a good current doc for this. If anyone = finds/writes something, please post it! There are some old resources you can find with a quick search that do a = pretty good job of covering the basic ideas, but I think the exact = syntax of commands may be slightly changed in the final implementation. The encryption is performed at a filesystem level (per-dataset). > thanks again! > -pete >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Fri Apr 17 22:12: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 B22962AD7C5; Fri, 17 Apr 2020 22:12:07 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493r134MhGz3N96; Fri, 17 Apr 2020 22:12:07 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (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: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 5A7F81171B; Fri, 17 Apr 2020 22:12:07 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-lf1-f42.google.com with SMTP id w145so3054736lff.3; Fri, 17 Apr 2020 15:12:07 -0700 (PDT) X-Gm-Message-State: AGi0PubQFsc0rTSk1oHuxbshJiwDEEt5Xg7vuQzCqlghmKi+y7xvcdAk DBHrOKKDrxI+05pNkiQrCysOfZbWvXUdieOQZ1w= X-Google-Smtp-Source: APiQypLnNI/LTN5vPsgpaQ8E77N++Wun83bLgFb5pPilrKLNPrBEmTJ7d9CAzUMoJUwJqt7LkyHIvehohYZYhdQdxgI= X-Received: by 2002:a19:c602:: with SMTP id w2mr211775lff.74.1587161525910; Fri, 17 Apr 2020 15:12:05 -0700 (PDT) MIME-Version: 1.0 References: <6333818E-63DA-4851-8496-9B0CE82145A3@samsco.org> In-Reply-To: <6333818E-63DA-4851-8496-9B0CE82145A3@samsco.org> From: Matthew Macy Date: Fri, 17 Apr 2020 15:11:54 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: OpenZFS port updated To: Scott Long Cc: Ryan Moeller , freebsd-current , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 22:12:07 -0000 On Fri, Apr 17, 2020 at 1:16 PM Scott Long wrote: > > Is the intention to eventually replace the zfs code in src/ ? Yes. Once the feature gap is filled in and most of the potential POLA violations are fixed. > What will be the long-term relationship between src/ and ports/ for this? OpenZFS users on 12 will use the port indefinitely. HEAD will presumably be updated whenever a point release is created upstream. Ultimately I can see two versions of the port, one that tracks master for HEAD and 12 and one that tracks only the latest release for 12 users. -M > > Scott > > > > On Apr 17, 2020, at 12:35 PM, Ryan Moeller wrote= : > > > > FreeBSD support has been merged into the master branch of the openzfs/z= fs repository, and the FreeBSD ports have been switched to this branch. > > > > OpenZFS brings many exciting features to FreeBSD, including: > > * native encryption > > * improved TRIM implementation > > * most recently, persistent L2ARC > > > > Of course, avoid upgrading your pools if you want to keep the option to= go back to the base ZFS. > > > > OpenZFS can be installed alongside the base ZFS. Change your loader.con= f entry to openzfs_load=3D=E2=80=9CYES=E2=80=9D to load the OpenZFS module = at boot, and set PATH to find the tools in /usr/local/sbin before /sbin. Th= e base zfs tools are still basically functional with the OpenZFS module, so= changing PATH in rc is not strictly necessary. > > > > The FreeBSD loader can boot from pools with the encryption feature enab= led, but the root/bootenv datasets must not be encrypted themselves. > > > > The FreeBSD platform support in OpenZFS does not yet include all featur= es present in FreeBSD=E2=80=99s ZFS. Some notable changes/missing features = include: > > * many sysctl names have changed (legacy compat sysctls should be added= at some point) > > * zfs send progress reporting in process title via setproctitle > > * extended 'zfs holds -r' (https://svnweb.freebsd.org/base?view=3Drevis= ion&revision=3D290015) > > * vdev ashift optimizations (https://svnweb.freebsd.org/base?view=3Drev= ision&revision=3D254591) > > * pre-mountroot zpool.cache loading (for automatic pool imports) > > > > To the last point, this mainly effects the case where / is on ZFS and /= boot is not or is on a different pool. OpenZFS cannot handle this case yet,= but work is in progress to cover that use case. Booting directly from ZFS = does work. > > > > If there are pools that need to be imported at boot other than the boot= pool, OpenZFS does not automatically import yet, and it uses /etc/zfs/zpoo= l.cache rather than /boot/zfs/zpool.cache to keep track of imported pools. = To ensure all pool imports occur automatically, a simple edit to /etc/rc.d= /zfs will suffice: > > > > diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs > > index 2d35f9b5464..8e4aef0b1b3 100755 > > --- a/libexec/rc/rc.d/zfs > > +++ b/libexec/rc/rc.d/zfs > > @@ -25,6 +25,13 @@ zfs_start_jail() > > > > zfs_start_main() > > { > > + local cachefile > > + > > + for cachefile in /boot/zfs/zpool.cache /etc/zfs/zpool.cache; do > > + if [ -f $cachefile ]; then > > + zpool import -c $cachefile -a > > + fi > > + done > > zfs mount -va > > zfs share -a > > if [ ! -r /etc/zfs/exports ]; then > > > > This will probably not be needed long-term. It is not necessary if the = boot pool is the only pool. > > > > Happy testing :) > > > > - Ryan > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > > _______________________________________________ > 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 Sat Apr 18 04:01: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 BF5622B88ED; Sat, 18 Apr 2020 04:01:04 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 493zlh2td0z4NR3; Sat, 18 Apr 2020 04:01:04 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.216] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id f8384a92 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 18 Apr 2020 04:01:03 +0000 (UTC) Subject: Re: OpenZFS port updated To: Ryan Moeller Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <6b25375d-0945-f01e-264e-ee410195fa97@nomadlogic.org> <0ED41E6B-9C57-405B-84BE-1161F012A974@FreeBSD.org> From: Pete Wright Message-ID: <679853e2-6113-1daa-3353-d9c5a1123a0f@nomadlogic.org> Date: Fri, 17 Apr 2020 21:01:03 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <0ED41E6B-9C57-405B-84BE-1161F012A974@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 493zlh2td0z4NR3 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 04:01:04 -0000 On 4/17/20 2:54 PM, Ryan Moeller wrote: >> On Apr 17, 2020, at 4:56 PM, Pete Wright wrote: >> >> On 4/17/20 11:35 AM, Ryan Moeller wrote: >>> FreeBSD support has been merged into the master branch of the openzfs/zfs repository, and the FreeBSD ports have been switched to this branch. >> Congratulations on this effort - big milestone! >>> OpenZFS brings many exciting features to FreeBSD, including: >>> * native encryption >> Is there a good doc reference on available for using this? I believe this is zfs filesystem level encryption and not a replacement for our existing full-disk-encryption scheme that currently works? > I’m not aware of a good current doc for this. If anyone finds/writes something, please post it! > There are some old resources you can find with a quick search that do a pretty good job of covering the basic ideas, but I think the exact syntax of commands may be slightly changed in the final implementation. > > The encryption is performed at a filesystem level (per-dataset). thanks for the clarification Ryan.  I may try to test this out in the near future and will try to record my findings in a wiki or somewhere.  being able to do filesystem level encryption is something i have several immediate use cases for. thanks! -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sat Apr 18 04:27: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 579EF2BA3F1 for ; Sat, 18 Apr 2020 04:27:50 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4940LZ0V4Mz4RZ8 for ; Sat, 18 Apr 2020 04:27:49 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 03I4STA8095570 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 17 Apr 2020 21:28:36 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: freebsd-current In-Reply-To: <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> From: Chris Reply-To: bsd-lists@BSDforge.com To: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: PCIe NVME drives not detected on Dell R6515 Date: Fri, 17 Apr 2020 21:28:35 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4940LZ0V4Mz4RZ8 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; NEURAL_HAM_MEDIUM(-0.93)[-0.935,0]; NEURAL_HAM_LONG(-0.99)[-0.989,0]; 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.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 04:27:50 -0000 On Fri, 17 Apr 2020 23:07:38 +0200 Miroslav Lachman 000=2Efbsd@quip=2Ecz said > Scott Long wrote on 04/17/2020 23:04: > >=20 > >=20 > >> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000=2Efbsd@quip=2Ecz> wrote= : > >> > >> Scott Long wrote on 04/17/2020 22:17: > >>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000=2Efbsd@quip=2Ecz> wro= te: > >>>> > >>>> Kurt Jaeger wrote on 04/17/2020 21:44: > >>>>> Hi! > >>>>>>> pciconf -lBc pcib12 > >>>>>>> pciconf -lBc pcib13 > >>>>>> > >>>>>> Printscreen attached=2E > >>>>> Attachments are stripped from the list -- can you put them somewher= e > >>>>> online ? > >>>> > >>>> Here it is https://ibb=2Eco/c1dZrTf > >>>> > >>>> Miroslav Lachman > >>>> > >>> Ok, the bridges know about their downstream bus numbers, but I see no= thing > > that suggests that they=E2=80=99re being probed=2E The next step would b= e bootverbose, > > but that=E2=80=99s going to be a lot of output to collect in screen cap= tures=2E > >> > >> Over 3000 lines long but I finally managed to make SOL work so I have = it as > > text! > >> > >> https://pastebin=2Epl/view/90fdaafb > >> > >=20 > > This helped a lot, thanks=2E It looks like these PCIe buses are marked a= s > > being hotplug, and for some reason we=E2=80=99re not probing them=2E At = this point, > > I=E2=80=99d need to feed you some kernel patches that will dump out mor= e info, but > > you=E2=80=99d have to compile them and get them onto your boot media=2E = Is that a > > possibility? >=20 > Currently I have all machines on 11=2E3 (where I can rebuild kernel=20 > without problem) > If CURRENT is required I would need to setup some CURRENT VM in VirtualBo= x=2E >=20 > Can you send me some link to documentation who should I create new ISO=20 > after rebuild? Here's what I do After building world && kernel: # cd /usr/src/ # make installworld DESTDIR=3D/to/path/with-2Gig-space # make distribution DESTDIR=3D/to/path/with-2Gig-space (you need a slice with ~2G space available) Then: # mkisofs -b boot/cdboot -no-emul-boot -r -J -V "FreeBSD__Install"= -publisher "" -o /path/to/put/NEW_INSTALL=2Eiso /to/path/with-2Gi= g-space Hope it makes sense to you=2E :) --Chris >=20 > Miroslav Lachman > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= " From owner-freebsd-current@freebsd.org Sat Apr 18 05:45:23 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 BE2622BCCDC for ; Sat, 18 Apr 2020 05:45:23 +0000 (UTC) (envelope-from marc@bumblingdork.com) Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49423z11gbz4Xgj for ; Sat, 18 Apr 2020 05:45:18 +0000 (UTC) (envelope-from marc@bumblingdork.com) Received: by mail-ua1-x92c.google.com with SMTP id g10so1530961uae.5 for ; Fri, 17 Apr 2020 22:45:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bumblingdork.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=hbrHmFpPD3flJOXhpIb09KS09sceTsERUSjEO979+Lk=; b=J7SNfu8VGEreflGBy+jvaDqr4Y+r0taS4ulDxOshRQuan1zZV7/SKLe7lmHz/qsJyL o16kk6DwhYQ5QA9tZFD5z/lzN2OA8yRkbKc6AfAaFfbCQdOKssdkaRSEyCtUdAhYvjvW Jl1dIHFIWAJPkOV5QvUUuA71gOje9NPjd093wZmqxurBm+zGu3/5e3rvCWNpz2qR1ttH sVHZbX9GH1W9aw7rOfG0e9Wtj5bk+8vKkRTus0OS1KtMycAtE/AgYtEciz6TwbDlxa+U P5pBG6FdmTts6Z0o1cCzuld449S/WOXtvA9M8grsg3r9I4LLkmA/Th2UlNQa2+doDdnP fQbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hbrHmFpPD3flJOXhpIb09KS09sceTsERUSjEO979+Lk=; b=Bg7Mt9Knphad3wvAYy57/oBJEIthCjh6+6wudoRQhKx2/h5aj3fOyieD5UgJSChqUA MzoQON+oKGSqm/PrBO42WDvlySIRhcBgwQ1ah6R19NdKzVQHDLnCMjG0p9vEPlOBIpU8 mlQNFQYHO8PRiFig4gA5KF1tmQtiUpoHJlVVY3NO0FnnRE8ui1KbUrVR+fyccypcZ4DP h7znRRyB17hyvtb0Ayzn9H6tCNIakIlGjFN+sTzzHrve9BKXhveGLexmxMwVt1OM0ZuL vUdcmOiya2lsn6BCmbSgTJl/FeSZW1UvwQjiTgv8hi6zI/ffQ/T5vfDha6v6x2EmzQo4 Xktg== X-Gm-Message-State: AGi0PuaRJheAIpWbG7JuVV5lbAZYIuC2wxQ7YLkwHsTXsRahovR+gEbY zqwkZCV7WKXCZSIgPi/c4+iapKfCKcNqsAyZRLlYHhPcD7s= X-Google-Smtp-Source: APiQypLciT6CXt30y76HUJPzRhdTgQASvDj5HrOXPsgfEozKMC49Xsd86XY7zW+6GRBry0Q0jd+tD55ziP3rYfS+fQ0= X-Received: by 2002:ab0:202:: with SMTP id 2mr1637498uas.42.1587188717488; Fri, 17 Apr 2020 22:45:17 -0700 (PDT) MIME-Version: 1.0 From: Marc Veldman Date: Sat, 18 Apr 2020 07:45:06 +0200 Message-ID: Subject: Patch to add recent bluetooth features to hccontrol To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 49423z11gbz4Xgj X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=temperror (DNS error when getting key) header.d=bumblingdork.com header.s=google header.b=J7SNfu8V; dmarc=pass (policy=none) header.from=bumblingdork.com; spf=pass (mx1.freebsd.org: domain of marc@bumblingdork.com designates 2607:f8b0:4864:20::92c as permitted sender) smtp.mailfrom=marc@bumblingdork.com X-Spamd-Result: default: False [-4.74 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-1.94)[ip: (-8.88), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.43), country: US(-0.05)]; DKIM_TRACE(0.00)[bumblingdork.com:?]; DMARC_POLICY_ALLOW(-0.50)[bumblingdork.com,none]; RCVD_IN_DNSWL_NONE(0.00)[c.2.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_DKIM_TEMPFAIL(0.00)[bumblingdork.com:s=google]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 05:45:23 -0000 apologies if this is the wrong list. I have created a patch to add more recent bluetooth features to hccontrol. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245354 Is this a reasonable approach? Best regards, Marc Veldman From owner-freebsd-current@freebsd.org Sat Apr 18 06:27: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 4111F2BE1EF; Sat, 18 Apr 2020 06:27:33 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49430h6nssz4bT9; Sat, 18 Apr 2020 06:27:32 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 03I6RUjk053805; Fri, 17 Apr 2020 23:27:30 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 03I6RUbc053804; Fri, 17 Apr 2020 23:27:30 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202004180627.03I6RUbc053804@gndrsh.dnsmgr.net> Subject: Re: OpenZFS port updated In-Reply-To: To: Ryan Moeller Date: Fri, 17 Apr 2020 23:27:30 -0700 (PDT) CC: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 49430h6nssz4bT9 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 06:27:33 -0000 > FreeBSD support has been merged into the master branch of the openzfs/zfs repository, and the FreeBSD ports have been switched to this branch. > > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption > * improved TRIM implementation > * most recently, persistent L2ARC > > Of course, avoid upgrading your pools if you want to keep the option to go back to the base ZFS. Has anyone published a set of pool options vs *ZFS implementations so one can figure out least common denomitator set of options when creating cross system pools, as the trial and error method is a royal pain. > > OpenZFS can be installed alongside the base ZFS. Change your loader.conf entry to openzfs_load=?YES? to load the OpenZFS module at boot, and set PATH to find the tools in /usr/local/sbin before /sbin. The base zfs tools are still basically functional with the OpenZFS module, so changing PATH in rc is not strictly necessary. > > The FreeBSD loader can boot from pools with the encryption feature enabled, but the root/bootenv datasets must not be encrypted themselves. > > The FreeBSD platform support in OpenZFS does not yet include all features present in FreeBSD?s ZFS. Some notable changes/missing features include: > * many sysctl names have changed (legacy compat sysctls should be added at some point) > * zfs send progress reporting in process title via setproctitle > * extended 'zfs holds -r' (https://svnweb.freebsd.org/base?view=revision&revision=290015) > * vdev ashift optimizations (https://svnweb.freebsd.org/base?view=revision&revision=254591) > * pre-mountroot zpool.cache loading (for automatic pool imports) > > To the last point, this mainly effects the case where / is on ZFS and /boot is not or is on a different pool. OpenZFS cannot handle this case yet, but work is in progress to cover that use case. Booting directly from ZFS does work. > > If there are pools that need to be imported at boot other than the boot pool, OpenZFS does not automatically import yet, and it uses /etc/zfs/zpool.cache rather than /boot/zfs/zpool.cache to keep track of imported pools. To ensure all pool imports occur automatically, a simple edit to /etc/rc.d/zfs will suffice: I am not so keen on the idea of "cache" data living in /boot, but I suppose /boot is already tainted with per machine data that should of lived someplace else. > diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs > index 2d35f9b5464..8e4aef0b1b3 100755 > --- a/libexec/rc/rc.d/zfs > +++ b/libexec/rc/rc.d/zfs > @@ -25,6 +25,13 @@ zfs_start_jail() > > zfs_start_main() > { > + local cachefile > + > + for cachefile in /boot/zfs/zpool.cache /etc/zfs/zpool.cache; do > + if [ -f $cachefile ]; then > + zpool import -c $cachefile -a > + fi > + done > zfs mount -va > zfs share -a > if [ ! -r /etc/zfs/exports ]; then > > This will probably not be needed long-term. It is not necessary if the boot pool is the only pool. > > Happy testing :) > > - Ryan > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Sat Apr 18 06:58: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 AAC842BEFD2 for ; Sat, 18 Apr 2020 06:58:59 +0000 (UTC) (envelope-from SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4943hx4zGYz4dYc for ; Sat, 18 Apr 2020 06:58:57 +0000 (UTC) (envelope-from SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E6D0628433; Sat, 18 Apr 2020 08:58:53 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A949528432; Sat, 18 Apr 2020 08:58:52 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long Cc: FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz> <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <6c2f9946-6e3e-e71a-0ef2-ee706d57085d@quip.cz> Date: Sat, 18 Apr 2020 08:58:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4943hx4zGYz4dYc X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [3.99 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; IP_SCORE(0.81)[ip: (0.26), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.56), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.984,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(1.00)[0.999,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=FWDs=6C=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 06:58:59 -0000 Scott Long wrote on 04/17/2020 23:30: >> Can you send me some link to documentation who should I create new ISO after rebuild? >> > > I don’t know of any docs for doing custom releases, and it looks like it’s harder than it used to be to insert custom patches. That said, I recommend doing the following on your 11.x build system: > > 1. Do a clean `make buildworld` with an up-to-date tree > 2. change into the `release` directory that you just did the buildworld from > 3. `sudo make release NOPORTS= NODOC= CHROOTDIR=/usr/tmp/release SRCBRANCH="base/stable/11@rHEAD”` > > You can set CHROOTDIR to whatever you want that has a few GB of space, but remember where you’ve set it for later steps. This will build a release with stock sources. Let it complete, both to prepare for the next step and to ensure that it works. It’ll take an hour or two depending on your machine speed > > 4. Take the patch that I’ll send you shortly and apply it to $CHROOTDIR/usr/src > 5. `sudo make memstick NOPORTS= NODOC= SRC_UPDATE_SKIP= CHROOTDIR=/usr/tmp/release` I did frech checkout of 11 stable in to /usr/src113/ setenv MAKEOBJDIRPREFIX /usr/obj113 cd /usr/src113 make buildworld make buildkernel KERNCONF=GENERIC cd release/ mkdir /vol0/release make release NOPORTS= NODOC= CHROOTDIR=/vol0/release SRCBRANCH="base/stable/11@rHEAD" /vol0/release is empty, it was created in /usr/obj113/usr/src113/release # ll /usr/obj113/usr/src113/release/ total 1696255 -rw-r--r-- 1 root wheel 1051 Apr 18 08:28 MANIFEST -rw-r--r-- 1 root wheel 56066772 Apr 18 07:51 base-dbg.txz -rw-r--r-- 1 root wheel 118984236 Apr 18 07:51 base.txz drwxr-xr-x 18 root wheel 22 Apr 18 08:32 bootonly -rw-r--r-- 1 root wheel 333000704 Apr 18 08:33 bootonly.iso drwxr-xr-x 18 root wheel 22 Apr 18 08:30 disc1 -rw-r--r-- 1 root wheel 692711424 Apr 18 08:31 disc1.iso drwxr-xr-x 8 root wheel 8 Apr 18 08:25 dist -rw-r--r-- 1 root wheel 1428564 Apr 18 07:51 doc.txz drwxr-xr-x 2 root wheel 12 Apr 18 08:28 ftp -rw-r--r-- 1 root wheel 116 Apr 18 08:25 kernel-dbg.txz -rw-r--r-- 1 root wheel 40103140 Apr 18 08:25 kernel.txz -rw-r--r-- 1 root wheel 14682736 Apr 18 07:51 lib32-dbg.txz -rw-r--r-- 1 root wheel 24179800 Apr 18 07:51 lib32.txz -rw-r--r-- 1 root wheel 762520064 Apr 18 08:33 memstick.img -rw-r--r-- 1 root wheel 373301760 Apr 18 08:34 mini-memstick.img -rw-r--r-- 1 root wheel 0 Apr 18 08:28 packagesystem -rw-r--r-- 1 root wheel 0 Apr 18 08:51 release -rw-r--r-- 1 root wheel 159327100 Apr 18 08:27 src.txz -rw-r--r-- 1 root wheel 4941816 Apr 18 07:51 tests.txz What I did wrong? Anyway I am waiting for your patches. Kind regards Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Apr 17 17:46: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 8EDC32C2BF2 for ; Fri, 17 Apr 2020 17:46:17 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 493k6H37H5z4LB1 for ; Fri, 17 Apr 2020 17:46:15 +0000 (UTC) (envelope-from SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5167028434; Fri, 17 Apr 2020 19:46:13 +0200 (CEST) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D072A28432; Fri, 17 Apr 2020 19:46:10 +0200 (CEST) Subject: Re: PCIe NVME drives not detected on Dell R6515 To: Scott Long , Warner Losh Cc: FreeBSD-Current References: <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> Date: Fri, 17 Apr 2020 19:46:07 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> X-Rspamd-Queue-Id: 493k6H37H5z4LB1 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.01 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.997,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(0.81)[ip: (0.27), ipnet: 94.124.104.0/21(0.13), asn: 42000(3.58), country: CZ(0.09)]; NEURAL_SPAM_LONG(1.00)[1.000,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~,3:~]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=00MP=6B=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-Mailman-Approved-At: Sat, 18 Apr 2020 08:17:26 +0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 17:46:17 -0000 Scott Long wrote on 04/17/2020 18:17: > You are correct about Intel vs AMD. Comparing the full output of pciconf from FreeBSD with the fragment of lspci from Linux suggests that there’s at least one set of a PCIe switch and child devices that is not being enumerated by FreeBSD. Can you send the full output of `lspci -tvv` from linux? Sorry for my late reply. Booting the Linux SystemRescueCd is too slow. lspci -tvv output is attached I tried to connect to SOL by SSH but it shows black screen only. lspci shows drives: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] Kind regards Miroslav Lachman >> On Apr 17, 2020, at 9:54 AM, Scott Long wrote: >> >> Would that be the Intel VMD/VROC stuff? If so, there’s a driver for FreeBSD, but it’s not well tested yet. Will have to dig in further. >> >> Scott >> From owner-freebsd-current@freebsd.org Sat Apr 18 09:16: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 9AC5B2C3050 for ; Sat, 18 Apr 2020 09:16:58 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4946mB3XdSz3N2J; Sat, 18 Apr 2020 09:16:58 +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 5A4BD1854D; Sat, 18 Apr 2020 09:16:58 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id D2B9012A68; Sat, 18 Apr 2020 11:16:56 +0200 (CEST) From: "Kristof Provost" To: FreeBSD-Current Cc: status-updates@freebsdfoundation.org Subject: Bridge project update (Week of April 14th) Date: Sat, 18 Apr 2020 11:16:53 +0200 X-Mailer: MailMate (1.13.1r5671) Message-ID: 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.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 09:16:58 -0000 Hi, Again, relatively little to report on. The review on the main patch is ongoing. It will likely be committed next week. I launched a call for testing, and a number of people have done so. Only one major issue was reported, on the stable/12 version of the patch. That’s since been resolved. Best regards, Kristof Provost From owner-freebsd-current@freebsd.org Sat Apr 18 12:05: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 02BA92C71D9 for ; Sat, 18 Apr 2020 12:05:35 +0000 (UTC) (envelope-from nonameless@ukr.net) Received: from frv198.fwdcdn.com (frv198.fwdcdn.com [212.42.77.198]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.ukr.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 494BVk0Q3rz46kg for ; Sat, 18 Apr 2020 12:05:33 +0000 (UTC) (envelope-from nonameless@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:Cc:To :Subject:From:Date:Sender:Reply-To:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=90YCYLxfXeXRPh0tPn904ELwf/YEfb+mHwDjZbVcWEg=; b=s t+lHYTWTLy5zUrTAkNoSqL/CfTnMrsVPX7OGZbDh5NTu61f5+gVtKVXIcV0fBeMdf13v+mSanwBSD aM7OuVBpE6F0dm/LHcwSK7BO7O3IcrOIs77t53YrM0uFenU3xoGB4NgTMQRFe0ZoVofPsNGSEvrgn ZATK6shbf4xezihk=; Received: from [10.10.80.25] (helo=frv55.fwdcdn.com) by frv198.fwdcdn.com with smtp ID 1jPmDt-000Orj-CB for freebsd-current@freebsd.org; Sat, 18 Apr 2020 15:05:25 +0300 Date: Sat, 18 Apr 2020 15:05:25 +0300 From: nonameless@ukr.net Subject: Outdated jemalloc in CURRENT To: freebsd-current@freebsd.org Cc: Received: from nonameless@ukr.net by frv55.fwdcdn.com; Sat, 18 Apr 2020 15:05:25 +0300 Message-Id: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> X-Mailer: mail.ukr.net 5.0 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-Rspamd-Queue-Id: 494BVk0Q3rz46kg X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ukr.net header.s=ffe header.b=s t+lHYT; dmarc=pass (policy=none) header.from=ukr.net; spf=pass (mx1.freebsd.org: domain of nonameless@ukr.net designates 212.42.77.198 as permitted sender) smtp.mailfrom=nonameless@ukr.net X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ukr.net:s=ffe]; IP_SCORE(0.00)[ipnet: 212.42.77.0/24(-4.87), asn: 8856(-3.90), country: UA(0.07)]; R_SPF_ALLOW(-0.20)[+ip4:212.42.77.0/24]; FREEMAIL_FROM(0.00)[ukr.net]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[ukr.net.dwl.dnswl.org : 127.0.5.1]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ukr.net:+]; DMARC_POLICY_ALLOW(-0.50)[ukr.net,none]; FROM_NO_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[ukr.net]; ASN(0.00)[asn:8856, ipnet:212.42.77.0/24, country:UA]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 12:05:35 -0000 Hi everyone! As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance regressions that was fixed in 5.2.1. Are there some issues that blocking update jemalloc to recent version? Thanks. From owner-freebsd-current@freebsd.org Sat Apr 18 14:20:14 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 75E2B2CAB00 for ; Sat, 18 Apr 2020 14:20:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 494FV42jYYz4Jds for ; Sat, 18 Apr 2020 14:20:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id 03IEK3oE064105 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 18 Apr 2020 07:20:03 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id 03IEK34R064104; Sat, 18 Apr 2020 07:20:03 -0700 (PDT) (envelope-from sgk) Date: Sat, 18 Apr 2020 07:20:03 -0700 From: Steve Kargl To: nonameless@ukr.net Cc: freebsd-current@freebsd.org Subject: Re: Outdated jemalloc in CURRENT Message-ID: <20200418142003.GA64067@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> X-Rspamd-Queue-Id: 494FV42jYYz4Jds X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.22 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FROM_HAS_DN(0.00)[]; IP_SCORE(-0.22)[ip: (0.02), ipnet: 128.95.0.0/16(-0.26), asn: 73(-0.82), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[ukr.net]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 14:20:14 -0000 On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: > Hi everyone! > > As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance regressions that was fixed in 5.2.1. > > Are there some issues that blocking update jemalloc to recent version? > ------------------------------------------------------------------------ r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines Revert r354605: Update jemalloc to version 5.2.1. Compilation fails for non-llvm-based platforms. ------------------------------------------------------------------------ r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines Update jemalloc to version 5.2.1. -- Steve From owner-freebsd-current@freebsd.org Sat Apr 18 15:01: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 6276E2CC103 for ; Sat, 18 Apr 2020 15:01:13 +0000 (UTC) (envelope-from gbergling@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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 494GPN4dc3z4N2W for ; Sat, 18 Apr 2020 15:01:12 +0000 (UTC) (envelope-from gbergling@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id u13so6438300wrp.3 for ; Sat, 18 Apr 2020 08:01:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=G34yETb4ALxsf7rzIEYragaF7OFjP1n4p9rhZNkAbIQ=; b=PU9bJ8RHZ+eAO4GhN+msXQwOFP0yJljhKFmad3YNlJB06cZXb/r+R0sq4QyvxNsTS+ 2L5JzayJdoFU1dtl5nvij2Yhu/K38TQkfvzc3r49oLHsw7RHwHcSHWoY1JmTfg9SUR5V ClHkBWqVOx+o+f8wYOm330fpYnie7VAw+RXEZd5RblF1x4muEXNagSmN0SmXHZyP18sP 605EVY5u9NyL+37K9ITkeeo6a1/ADdBiqOnBrEYWpWDgbniL72zb3msAdGQcQyjtBkQE pXx/mv557t2qOHtslytk3Jsu0Yk9EXTINOebUQgm2CPN5T2tHs5MHff9sBKTcu95MIin B+Og== X-Gm-Message-State: AGi0PuboS2OWm2h8S0GaoLzlLiZykSEgrOGlMCeozZrg6F2+JgECYHwD So1qBU92Qc/48VrP50FSwmZYOvOW X-Google-Smtp-Source: APiQypLlXPuSSY1ws3cBHLAoAKzKhxQe1ybNBIWCDW3273HlBwGB5rRtr/D4y4cVZo9S5z11V9bcOA== X-Received: by 2002:a05:6000:1008:: with SMTP id a8mr9685348wrx.189.1587222070712; Sat, 18 Apr 2020 08:01:10 -0700 (PDT) Received: from lion.0xfce3.net (p4FD3AF72.dip0.t-ipconnect.de. [79.211.175.114]) by smtp.gmail.com with ESMTPSA id k5sm23167071wrg.48.2020.04.18.08.01.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 18 Apr 2020 08:01:10 -0700 (PDT) Sender: Gordon Bergling Date: Sat, 18 Apr 2020 17:01:08 +0200 From: Gordon Bergling To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: Outdated jemalloc in CURRENT Message-ID: <20200418150108.GA14089@lion.0xfce3.net> References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> <20200418142003.GA64067@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200418142003.GA64067@troutmask.apl.washington.edu> X-Url: X-Operating-System: FreeBSD 12.1-STABLE amd64 X-Host-Uptime: 4:59PM up 1 day, 22:48, 3 users, load averages: 0.36, 0.32, 1.14 X-Rspamd-Queue-Id: 494GPN4dc3z4N2W X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[googlemail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[gbergling@googlemail.com,gbergling@gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[114.175.211.79.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; IP_SCORE(0.00)[ip: (-9.06), ipnet: 2a00:1450::/32(-2.34), asn: 15169(-0.43), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[gbergling@googlemail.com,gbergling@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DMARC_POLICY_QUARANTINE(1.50)[googlemail.com : SPF not aligned (relaxed), DKIM not aligned (relaxed),quarantine]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 15:01:13 -0000 I am not sure, that this info is correct. As far as I remember the update for jemalloc was reverted due to build problems, on some architecture. An updated revision has still to be commited to -CURRENT. Gordon On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: > On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: > > Hi everyone! > > > > As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance regressions that was fixed in 5.2.1. > > > > Are there some issues that blocking update jemalloc to recent version? > > > > ------------------------------------------------------------------------ > r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines > > Revert r354605: Update jemalloc to version 5.2.1. > > Compilation fails for non-llvm-based platforms. > > ------------------------------------------------------------------------ > r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines > > Update jemalloc to version 5.2.1. > > -- > Steve > _______________________________________________ > 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" -- Gordon Bergling Mobile: +49 170 23 10 948 Web: https://www.gordons-perspective.com/ Mail: gbergling@gmail.com Think before you print! From owner-freebsd-current@freebsd.org Sat Apr 18 15:10: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 EBF922CC567 for ; Sat, 18 Apr 2020 15:10:53 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 494GcY05h4z4NyP for ; Sat, 18 Apr 2020 15:10:52 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 184565C011C; Sat, 18 Apr 2020 11:10:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 18 Apr 2020 11:10:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=N 8Kxkof61kUMkvHEeICm56Lk/dA9OMsXKE5OJAYKfL4=; b=fFRrA6+21Xj1IRTG0 ux3PCt0dVkQJkhYVBca1VyVKQFDqNVTg0TDjIY4xLUJxnaGe6HDro3aiEhfCSci5 koOap87+QPAwftmTUTRGVyzfOxvW2prncBKMNrDOdEffQ1RTWahaah6RSJLu9tGh B7jw3yrobmHrK2ychtd60JPBiaIHnDEedbwNmq1SN+m4gfE/pU4EEFnFCf01QVHA 6JDvkhlTDs/vN/W6ZEBxFMtfXqdyAETHQV4ifw9HaRlLT1VtoHYMHw0mrP9fgNi5 CEAw+AQlRSuvExSLgTKIgGgxfOU9EdN343n/qZs5IxaCFn3hIE2dXe6OxB1kEDgJ COahA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=N8Kxkof61kUMkvHEeICm56Lk/dA9OMsXKE5OJAYKf L4=; b=a6SnRxFsK5Zt8Ng8UoSE0/8RXr5SIIrRYsLGiE71F5g/bicePMdxtjG// q22scqTH2rI6Tco4UO46pszfiRqJKxVkL0IQ6NXLiFKOkcRhJFSnct7ubvNZ9y5G W4eAVIrF8VllNraaUG6ZIBZ2syxqRCJG8+FKfFDQJ4NFjm8YORQpNXiR32RT1RHP 9dHJZFDvjBs1XYAg3RVMaetawaeSeqe7SDLeZ2k0akMXLxncThIPE2C0u8Q9W7CD QAK6b0Um80vfxEW/EGbtshfagmp78urMYJsehIUC7xb4tlWaxMorXzUFY7a473Bs EeHHnshCPPdCn3bvfS57miDcsafBg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeelgdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpegjuhhrihcu rfgrnhhkohhvuceohihprghnkhhovhesfhgrshhtmhgrihhlrdgtohhmqeenucfkphepke ehrddujeehrddufeelrddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhephihprghnkhhovhesfhgrshhtmhgrihhlrdgtohhm X-ME-Proxy: Received: from [192.168.1.6] (unknown [85.175.139.251]) by mail.messagingengine.com (Postfix) with ESMTPA id F2B5C3280066; Sat, 18 Apr 2020 11:10:49 -0400 (EDT) Subject: Re: Outdated jemalloc in CURRENT To: Gordon Bergling , Steve Kargl Cc: freebsd-current@freebsd.org References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> <20200418142003.GA64067@troutmask.apl.washington.edu> <20200418150108.GA14089@lion.0xfce3.net> From: Yuri Pankov Message-ID: <1f4e0642-8dff-612c-526a-2bfcbc0e5085@fastmail.com> Date: Sat, 18 Apr 2020 18:10:50 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200418150108.GA14089@lion.0xfce3.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 494GcY05h4z4NyP X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fastmail.com header.s=fm2 header.b=fFRrA6+2; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=a6SnRxFs; dmarc=pass (policy=none) header.from=fastmail.com; spf=pass (mx1.freebsd.org: domain of ypankov@fastmail.com designates 66.111.4.28 as permitted sender) smtp.mailfrom=ypankov@fastmail.com X-Spamd-Result: default: False [-3.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[28.4.111.66.rep.mailspike.net : 127.0.0.18]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.28]; FREEMAIL_FROM(0.00)[fastmail.com]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[fastmail.com:+,messagingengine.com:+]; DMARC_POLICY_ALLOW(-0.50)[fastmail.com,none]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.00)[ip: (-9.82), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)]; RCVD_IN_DNSWL_LOW(-0.10)[28.4.111.66.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[251.139.175.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[fastmail.com]; R_DKIM_ALLOW(-0.20)[fastmail.com:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 15:10:54 -0000 Gordon Bergling wrote: > I am not sure, that this info is correct. As far as I remember the update for jemalloc was reverted due to build problems, on some architecture. An updated revision has still to be commited to -CURRENT. That's exactly what the commit log says, yes? > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: >>> Hi everyone! >>> >>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance regressions that was fixed in 5.2.1. >>> >>> Are there some issues that blocking update jemalloc to recent version? >>> >> >> ------------------------------------------------------------------------ >> r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines >> >> Revert r354605: Update jemalloc to version 5.2.1. >> >> Compilation fails for non-llvm-based platforms. >> >> ------------------------------------------------------------------------ >> r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines >> >> Update jemalloc to version 5.2.1. From owner-freebsd-current@freebsd.org Sat Apr 18 15:15:34 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 D4B592CC8A5 for ; Sat, 18 Apr 2020 15:15:34 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (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 494Gjw6g3fz4PNv for ; Sat, 18 Apr 2020 15:15:32 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1jPpBp-0001F5-Vj for freebsd-current@freebsd.org; Sat, 18 Apr 2020 17:15:30 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "FreeBSD Current" Date: Sat, 18 Apr 2020 17:15:28 +0200 Subject: xtoolchain-llvm10 missing? MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.2 X-Scan-Signature: 7194f67edb0fd0030ea28d62f3968513 X-Rspamd-Queue-Id: 494Gjw6g3fz4PNv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-1.52 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[klop.ws]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.72)[ip: (-0.62), ipnet: 195.190.28.0/24(-0.25), asn: 47172(-2.76), country: NL(0.03)]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[88.28.190.195.list.dnswl.org : 127.0.10.0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 15:15:34 -0000 Hi, Building CURRENT on my laptop takes very very long because every little change in llvm/clang makes it recompile a complete compiler. So I want to build with CROSS_TOOLCHAIN=xtoolchain-llvm10 (10.0) and WITHOUT_TOOLCHAIN=yes. In ports/pkgs the most recent versions I see are xtoolchain-llvm90 or xtoolchain-llvm-devel (11.0?). Is xtoolchain-llvm10 missing on purpose? Regards, Ronald. From owner-freebsd-current@freebsd.org Sat Apr 18 15:21: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 7F3282CCD6E for ; Sat, 18 Apr 2020 15:21:55 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 494GsG384Mz4Q5K for ; Sat, 18 Apr 2020 15:21:54 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id 03IFLq5U064466 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 18 Apr 2020 08:21:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id 03IFLq53064465; Sat, 18 Apr 2020 08:21:52 -0700 (PDT) (envelope-from sgk) Date: Sat, 18 Apr 2020 08:21:52 -0700 From: Steve Kargl To: Gordon Bergling Cc: freebsd-current@freebsd.org Subject: Re: Outdated jemalloc in CURRENT Message-ID: <20200418152152.GA64335@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> <20200418142003.GA64067@troutmask.apl.washington.edu> <20200418150108.GA14089@lion.0xfce3.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200418150108.GA14089@lion.0xfce3.net> X-Rspamd-Queue-Id: 494GsG384Mz4Q5K X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.21 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-0.22)[ip: (0.02), ipnet: 128.95.0.0/16(-0.26), asn: 73(-0.82), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Apr 2020 15:21:55 -0000 On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote: > > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: >>> Hi everyone! >>> >>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some >>> performance regressions that was fixed in 5.2.1. >>> >>> Are there some issues that blocking update jemalloc to recent version? >>> >> >> ------------------------------------------------------------------------ >> r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines >> >> Revert r354605: Update jemalloc to version 5.2.1. >> >> Compilation fails for non-llvm-based platforms. >> >> ------------------------------------------------------------------------ >> r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines >> >> Update jemalloc to version 5.2.1. >> > > I am not sure, that this info is correct. As far as I remember the > update for jemalloc was reverted due to build problems, on some > architecture. An updated revision has still to be commited to -CURRENT. > Those two commits confirm your memory. 5.2.1 was committed in r354605. 5.2.1 was reverted with r354606 where the reason for reverting is stated. As 5.2.1 has not been re-committed and there is nothing in reviews.freebsd.org for review, one may expect the reason in r354606 still stands. PS: Please, do not top-post. PPS: Please, wrap your messages to something less than 80 characters. -- Steve