From owner-freebsd-current@freebsd.org Sun May 28 07:49:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49B64D85120 for ; Sun, 28 May 2017 07:49:04 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 053D7E8F; Sun, 28 May 2017 07:49:02 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA12086; Sun, 28 May 2017 10:49:00 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dEswe-000LB8-IW; Sun, 28 May 2017 10:49:00 +0300 Subject: Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) To: Rick Macklem , "freebsd-current@freebsd.org" Cc: "cem@freebsd.org" , "jeff@freebsd.org" , Ryan Stone References: From: Andriy Gapon Message-ID: Date: Sun, 28 May 2017 10:48:00 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 07:49:04 -0000 On 28/05/2017 01:20, Rick Macklem wrote: > After poking at this some more, it appears that r312426 is the main cause of > this degradation. Rick, thank you for the investigation! A quick question before a longer reply: what network driver do you use in your test setup? Is it ixl by a chance? -- Andriy Gapon From owner-freebsd-current@freebsd.org Sun May 28 15:54:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BC55D85786 for ; Sun, 28 May 2017 15:54:38 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16D441307 for ; Sun, 28 May 2017 15:54:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.197] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 330d5f05 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Sun, 28 May 2017 08:54:36 -0700 (PDT) To: freebsd-current@freebsd.org From: Pete Wright Subject: INO64 Effecting Firefox Message-ID: Date: Sun, 28 May 2017 08:54:35 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 15:54:38 -0000 Hi all, I can't imagine that this is related to INO64, but since upgrading my world and kernel on drm-next (which merged upstream CURRENT as of May 27 which should include the ino64 work) I am having segfaults running firefox. Previous to this firefox was very stable for work/personal daily use. The error I'm seeing is: Full message: TypeError: malformed UTF-8 character sequence at offset 0 Firefox does start and I can load a page or two before it sefaults. The full console output is here: https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f Posting this here in the off chance that it's either related to ino64, or some other recent change has caused this problem. Cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun May 28 16:09:37 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 356DDD85D55 for ; Sun, 28 May 2017 16:09:37 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A369F19E2 for ; Sun, 28 May 2017 16:09:36 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.164.222]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0ML7NR-1dFHs72NiD-000L20; Sun, 28 May 2017 18:09:26 +0200 Date: Sun, 28 May 2017 18:09:19 +0200 From: "O. Hartmann" To: Pete Wright Cc: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox Message-ID: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/u=TtxToWBmbcUfvfDUO5Iii"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:JomtQV0DrQo3QKIQC+khS1+kZCmV3rdzcd3YJKZVZ2tnzf1LnFh Y0YM1yhZro/5FbTEmfrFI8UPdAC9yURBKDO+cBh7jlVbqMDLdYqtlT8sKnEJXjCKAAI+KKW V5I1jQK1MpxemMuZ0EqBAf+44k8aywMABdZDeWJG42E6NEEtd/KaFkpZS9uP9EFxOW2fpRb fEflfZnCJ0zkrs9OHGDrg== X-UI-Out-Filterresults: notjunk:1;V01:K0:CQf2b/BuS+I=:186JxC0xMAZO6nJNYwMi0o ZgxCetnUI4RfElDOAHxHq/qjDAV5a13QgFpRJ/bWw1r+t+G8Utt/jV6TYYYFlrHi8jSVHGFWr pXSsCZYOQBWZRJrAEfDnC9qvMNKoEkbGHH8+0htjdRId8VHE3AN1/gq0xu2riYGA3avc43fRn 3WSQIZZNmDM4V0UmtCzL+tX4ACMhj2F2LqArxLkB3FWg8eDyvaTsahKvssbRkuhQMhAdSXv71 qfZlRW3KE3DY8t31Rzp8AhPqMxAd/F1fjatymCQ3GM2nIPiYZtKBMz4tXKoELFCpJ6CnnQJtF Rl+nrR6K/oBlIErxiUz9+cHKKRN7P7UyJcJ+BQr21ql0AkMn+gwfxpDRBryTw/oi8GvAWTVL3 lXmje20a8k/FlainjOPibgv/GdfdCd8soN32mndE4aC/0VEVSzbJD4fI2vRonye0ew3kiNb6A FOLf9ozsFgrJE/E+TZ4vQHEkPcbj+LbfANSVD/QDRDJmVida5EyCQncaQe/NmScQLT3lbhkV8 ddul3oo18kcjCNhZqwY5Vp+MN0savZ3RFLhNpfZw89JuEjlw9ZRqzDpPNC+4bf/yyVWafy+Jk Ssm8gPExpdH5aJTISc688tYF3yhl5X/ZVM4zxau9TJDLh01ZBcGsFrfdEy+UZk7T84143CkOc KiBMuA6qIEUXWNVmGYChOu6jfUpAIJ7TyaNJ11TDGvfuSp0MPo4pR0b7gnFBZIUtTOtihVSwb cdb2u2Q0K1vS9M23PFUjYCVZdmPa1HUpf7DkLEiwM1c7dRJdIB17CNffP+I= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 16:09:37 -0000 --Sig_/u=TtxToWBmbcUfvfDUO5Iii Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 28 May 2017 08:54:35 -0700 Pete Wright schrieb: > Hi all, >=20 > I can't imagine that this is related to INO64, but since upgrading my=20 > world and kernel on drm-next (which merged upstream CURRENT as of May 27= =20 > which should include the ino64 work) I am having segfaults running=20 > firefox. Previous to this firefox was very stable for work/personal=20 > daily use. >=20 > The error I'm seeing is: > Full message: TypeError: malformed UTF-8 character sequence at offset 0 >=20 > Firefox does start and I can load a page or two before it sefaults. >=20 > The full console output is here: >=20 > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f >=20 >=20 > Posting this here in the off chance that it's either related to ino64,=20 > or some other recent change has caused this problem. >=20 > Cheers! >=20 > -pete >=20 >=20 I see similar problems. Out of the blue, firefox crashes. But in my case, firefox is "old", since it doesn't compile with WITH_LLD_IS= _LD due to a very strange error (Bug 218808). The binary I run und CURRENT (FreeBSD 12.0-CURRENT #8 r319001: Sun May 28 0= 0:21:16 CEST 2017 amd64, WITH_LLD_IS_LD=3Dyes) if as of firefox-53.0_2,1 Name : firefox Version : 53.0_2,1 Installed on : Sun Apr 16 10:17:14 2017 CEST Origin : www/firefox Architecture : FreeBSD:12:amd64 I got a kind of relief (means: the frequence of crashes is reduced) when st= arting to rebuild all ports again (I'm staying with make and portmaster) to meet ABI = requirements after ino64 has been introduced. Another strange behaviour is: firefox crashes very likely very often when s= tarted. Once it has run a while, I can consider it "stable". It doen not crash then.=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/u=TtxToWBmbcUfvfDUO5Iii Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWSr2LwAKCRDS528fyFhY lPDCAgCGWbOHEg7EDbSO6VYY8yblr3LscX0mlQtLjo46PxXsXCpFLf8M4kuR99rR /6rc7N1pJF70tW4z1YtzoIpl4c1wAf9+6Qg2GJ3A2vxNtvtiSJ94kjYCEII/1cUe u68llw8vSMaqQjjQFrLMn5dzIL1r6u2qD2S1FivtYgIF1V5i3Dga =T2Kw -----END PGP SIGNATURE----- --Sig_/u=TtxToWBmbcUfvfDUO5Iii-- From owner-freebsd-current@freebsd.org Sun May 28 16:45:03 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56BB4D85871 for ; Sun, 28 May 2017 16:45:03 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B85161E28 for ; Sun, 28 May 2017 16:45:02 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v4SGpQHC098967 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sun, 28 May 2017 19:51:29 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v4SGii1h077112 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 28 May 2017 19:44:44 +0300 (EEST) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v4SGiiMr077111 for freebsd-current@freebsd.org; Sun, 28 May 2017 19:44:44 +0300 (EEST) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox Date: Sun, 28 May 2017 19:44:43 +0300 Message-ID: <5493690.zc92PMVLEF@asus.theweb.org.ua> Organization: Private person User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.30; amd64; ; ) In-Reply-To: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> References: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Mailman-Approved-At: Sun, 28 May 2017 17:15:50 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 16:45:03 -0000 On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 > > Pete Wright schrieb: > > Hi all, > > > > I can't imagine that this is related to INO64, but since upgrading my > > world and kernel on drm-next (which merged upstream CURRENT as of May 27 > > which should include the ino64 work) I am having segfaults running > > firefox. Previous to this firefox was very stable for work/personal > > daily use. > > > > The error I'm seeing is: > > Full message: TypeError: malformed UTF-8 character sequence at offset 0 > > > > Firefox does start and I can load a page or two before it sefaults. > > > > The full console output is here: > > > > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f > > > > > > Posting this here in the off chance that it's either related to ino64, > > or some other recent change has caused this problem. > > > > Cheers! > > > > -pete > > I see similar problems. Out of the blue, firefox crashes. > But in my case, firefox is "old", since it doesn't compile with > WITH_LLD_IS_LD due to a very strange error (Bug 218808). > > The binary I run und CURRENT (FreeBSD 12.0-CURRENT #8 r319001: Sun May 28 > 00:21:16 CEST 2017 amd64, WITH_LLD_IS_LD=yes) if as of > > firefox-53.0_2,1 > Name : firefox > Version : 53.0_2,1 > Installed on : Sun Apr 16 10:17:14 2017 CEST > Origin : www/firefox > Architecture : FreeBSD:12:amd64 > > I got a kind of relief (means: the frequence of crashes is reduced) when > starting to rebuild all ports again (I'm staying with make and portmaster) > to meet ABI requirements after ino64 has been introduced. > > Another strange behaviour is: firefox crashes very likely very often when > started. Once it has run a while, I can consider it "stable". It doen not > crash then. Please try to rebuild firefox. It helps me today with firefox-esr segfaulting on my desktop running 12.0-CURRENT r318856 From my limited understanding of stacktraces it was related to libthr changes. From owner-freebsd-current@freebsd.org Sun May 28 17:21:48 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A8DDD85829 for ; Sun, 28 May 2017 17:21:48 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EAE115F0 for ; Sun, 28 May 2017 17:21:48 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-pg0-x232.google.com with SMTP id x64so13158453pgd.3 for ; Sun, 28 May 2017 10:21:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ERDM6vkjGICe3xKHAamfJG9QfwN+0kUcvNe+8J9niek=; b=k08HdhOzCcdSRDc5+MhHUhnv7b033L++3G2bBoaajUs11SFzTjeiSwPa2xdVThKCly 8t6dxFzw4AxkIv4dIuBRVLoq/LP+zsz5/FU3P9MVa48EKcKhCZELDYq/Ze1K1qptOqcL LOYnbcPhfICMYnc5HwGFCePhnjbvSC8oOm/0S5BF8mlygjetniU2WlYvDzBiH3sd2v// aAO/X3WueJ+rvcMWrttPF8yjVzIKTd3uqNxIgf7CNBI0E//ydsBOgMmYe0tfHO52w/40 2xqUIEDR9j3/aWdd1pa84wI+UeTwf3OkfPieTpFzGjq1FZOR0kSvyCTEajulzyc8AXCi EIHg== 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=ERDM6vkjGICe3xKHAamfJG9QfwN+0kUcvNe+8J9niek=; b=fYViFzh70ARmDq3euj2e+hQMk028AK1hJs/j3kZf//qzsXSrIwqR4tRH6X2sgGxzVI mKT5M1CYrnUyH+bbwifmwhuQjJwpSZjVFA10EQjSO50hPAGXGP/qVsjyjYCx6z1RH8cV l7sSQiuw/hWCyBw+EDL5TqVj6h3qeRGhAxPfGMGo7zDZc2hSzEFKE6TQmd/6yT/mlDFr mTv0xk/avc26Q1Xvp2r1ul1v8oAZZ9GRmL31PgWYJewwfVZIv+9iM2aNl0Yxq9ZfintZ R1S3pcDkiG491rPwR76P9KSMSiQapDj8yXb8eeVfh7N6nNVbxTMkeaBxhM2o/Lp+PZLL a9Og== X-Gm-Message-State: AODbwcBykwH36t+sHVU+5oKoiPlT+EcruyT/80eYO3qUHwSgJeGNtMK7 aXys6z/0OeC48HQ4XoyAkAc5Xr663F8c X-Received: by 10.98.217.5 with SMTP id s5mr13295901pfg.42.1495992107409; Sun, 28 May 2017 10:21:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.168.79 with HTTP; Sun, 28 May 2017 10:21:47 -0700 (PDT) From: blubee blubeeme Date: Mon, 29 May 2017 01:21:47 +0800 Message-ID: Subject: firefox/ rust failed to install on FreeBSD 12-CURRENT To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 17:21:48 -0000 I'm trying to install firefox on FreeBSD FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318998: Sun May 28 04:38:22 CST 2017 /usr/obj/usr/src/sys/GENERIC amd64 ===> firefox-i18n-53.0.3 depends on file: /usr/local/lib/firefox/firefox - not found ===> firefox-53.0.3_1,1 depends on package: nspr>=4.13.1 - found ===> firefox-53.0.3_1,1 depends on package: nss>=3.29.5 - found ===> firefox-53.0.3_1,1 depends on package: libevent>=2.0.21_2 - found ===> firefox-53.0.3_1,1 depends on package: harfbuzz>=1.4.1 - found ===> firefox-53.0.3_1,1 depends on package: graphite2>=1.3.8 - found ===> firefox-53.0.3_1,1 depends on package: png>=1.6.28 - found ===> firefox-53.0.3_1,1 depends on package: libvorbis>=1.3.5,3 - found ===> firefox-53.0.3_1,1 depends on package: libvpx>=1.5.0 - found ===> firefox-53.0.3_1,1 depends on package: sqlite3>=3.17.0 - found ===> firefox-53.0.3_1,1 depends on package: py27-sqlite3>0 - found ===> firefox-53.0.3_1,1 depends on package: v4l_compat>0 - found ===> firefox-53.0.3_1,1 depends on executable: autoconf-2.13 - found ===> firefox-53.0.3_1,1 depends on executable: yasm - found ===> firefox-53.0.3_1,1 depends on executable: zip - found ===> firefox-53.0.3_1,1 depends on package: gtk3>=3.14.6 - found ===> firefox-53.0.3_1,1 depends on package: libnotify>0 - found ===> firefox-53.0.3_1,1 depends on executable: rustc - not found ===> Building for rust-1.17.0 gmake[7]: Entering directory '/usr/ports/lang/rust/work/rustc-1.17.0-src' "/usr/local/bin/python2.7" /usr/ports/lang/rust/work/rustc-1.17.0-src/src/bootstrap/bootstrap.py build -v info: looks like you are running this command under `sudo` and so in order to preserve your $HOME this will now use vendored sources by default. Note that if this does not work you should run a normal build first before running a command like `sudo make install` extracting /usr/ports/lang/rust/work/rustc-1.17.0-src/build/cache/2017-03-11/rust-std-1.16.0-x86_64-unknown-freebsd.tar.gz extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/ manifest.in extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd/lib extracting rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib/rustlib/x86_64-unknown-freebsd/lib/GNUSparseFile.0/librustc_llvm-74a1be1110b5d4d0.so gmake[7]: Leaving directory '/usr/ports/lang/rust/work/rustc-1.17.0-src' *** Error code 1 Stop. make[6]: stopped in /usr/ports/lang/rust *** Error code 1 Stop. make[5]: stopped in /usr/ports/lang/rust *** Error code 1 Stop. make[4]: stopped in /usr/ports/www/firefox *** Error code 1 Stop. make[3]: stopped in /usr/ports/www/firefox *** Error code 1 Stop. make[2]: stopped in /usr/ports/www/firefox-i18n *** Error code 1 Stop. make[1]: stopped in /usr/ports/www/firefox-i18n *** Error code 1 Stop. make: stopped in /usr/ports/www/firefox-i18n I am getting build failures with or without make_build_unsafe flags. I am building from source and ports tree is updated to revision 441919. Best, Owen From owner-freebsd-current@freebsd.org Sun May 28 20:16:57 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11E3BD86348 for ; Sun, 28 May 2017 20:16:57 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660072.outbound.protection.outlook.com [40.107.66.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B214D1553; Sun, 28 May 2017 20:16:56 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0191.CANPRD01.PROD.OUTLOOK.COM (10.165.218.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1124.9; Sun, 28 May 2017 20:16:54 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1124.015; Sun, 28 May 2017 20:16:54 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" CC: Andriy Gapon , "cem@freebsd.org" , "jeff@freebsd.org" , Ryan Stone , "Colin Percival" Subject: Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) Thread-Topic: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) Thread-Index: AQHS1mmgxqkdxhAY5U2DZ8FjIm51zqIIvdIkgAFvXYY= Date: Sun, 28 May 2017 20:16:53 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: FreeBSD.org; dkim=none (message not signed) header.d=none;FreeBSD.org; dmarc=none action=none header.from=uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0191; 7:O2ZEQIZ+AVS1CCuMktupu/2jqPa7aGpnYGW51c+WtdsEwfrU7wk5hBpDv6Cq2bzTsj5/GCFrcx92CTBej1KuU7HR6J6s5a8rn5tqk9a3Rq92ZFiJOjT1atAxFm8RiajWmwAaMOQDPCvhwpmpUo6zOqksgVQiOPg161se2Pp8552MzhHffvRPPjH0Aez+A5W/EazC1HP5ez/6ybDgKon9MYWi8aifsisUP2YSA63rIPacB/ZW/vzfjFwH5Qu3O8c32nbYv0weyZnqnSMHw1c5T4qpjagE86Io/mMyWjq2NSd9aqdfRJ7Trbh9RGV/LA3IwFZil7YNKMVEKTmePt6oSA== x-ms-traffictypediagnostic: YTXPR01MB0191: x-ms-office365-filtering-correlation-id: 32923207-d713-460e-f07a-08d4a6067ba2 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:YTXPR01MB0191; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123558100)(20161123560025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123555025)(6072148); SRVR:YTXPR01MB0191; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0191; x-forefront-prvs: 03218BFD9F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39850400002)(39400400002)(39410400002)(39840400002)(39450400003)(24454002)(229853002)(86362001)(6916009)(3660700001)(2950100002)(3280700002)(7696004)(76176999)(54356999)(50986999)(8936002)(25786009)(4326008)(450100002)(2900100001)(81166006)(8676002)(189998001)(305945005)(102836003)(33656002)(74316002)(5660300001)(2906002)(74482002)(122556002)(2351001)(54906002)(77096006)(53936002)(55016002)(478600001)(9686003)(110136004)(38730400002)(6246003)(6436002)(6506006)(2501003)(5640700003)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0191; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2017 20:16:53.9748 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0191 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 20:16:57 -0000 I wrote: [stuff snipped] > So, I'd say either reverting the patch or replacing it with the "obvious = change" mentioned > in the commit message will at least mostly fix the problem. "mostly fix" was probably a bit optimistic. Here's my current #s. (All cases are the same single threaded kernel build, same hardware, etc. T= he only changes are recent vs 1yr old head kernel and what is noted.) - 1yr old kernel, SMP, SCHED_ULE 94minutes - 1yr old kernel, no SMP, SCHED_ULE 111minutes - recent kernel, SMP, SCHED_4BSD 104minutes - recent kernel, no SMP, SCHED_ULE 113minutes - recent kernel, SMP, SCHED_ULE, r312426 reverted 122minutes - recent kernel, SMP, SCHED_ULE 148minutes So, reverting r312426 only gets rid of about 1/2 of the degradation. One more thing I will note is that the system CPU is higher for the cases t= hat run with lower/better elapsed times: - 1yr old kernel, SMP, SCHED_ULE 545s - 1yr old kernel, no SMP, SCHED_ULE 293s - recent kernel, no SMP, SCHED_ULE 292s - recent kernel, SMP, SCHED_ULE 466s cperciva@ is running a highly parallelized buuildworld and he sees better slightly better elapsed times and much lower system CPU for SCHED_ULE. As such, I suspect it is the single threaded, processes mostly sleeping wai= ting for I/O case that is broken. I suspect this is how many people use NFS, since a highly parallelized make= would not be a typical NFS client task, I think? There are other changes to sched_ule.c in the last year, but I'm not sure w= hich would be easy to revert and might make a difference in this case? rick ps: I've cc'd cperiva@ and he might wish to report his results. I am hoping= he does try a make without "-j" at some point. From owner-freebsd-current@freebsd.org Sun May 28 20:43:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54FC6D86BD1 for ; Sun, 28 May 2017 20:43:43 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2428B10F0 for ; Sun, 28 May 2017 20:43:43 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-pg0-x234.google.com with SMTP id x64so14047401pgd.3 for ; Sun, 28 May 2017 13:43:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=932y6fVEjMCffWLgpBJHJF6PcFve/VsNCDEkZTsCgS0=; b=GXv/jTc3HnXa4dGKIjksupyrJLtaK09HANinhsqewNhtv06yW2dSLR+7I7Q+Ky7+ri 5qOXUF956f963R3LB7k3EB3bJ7dZGw8LDDa3FLGO/HD/QuKlEm9MyBBVT1Le/K6aBhzG ODbuIs3LyzV515LkcBNcg7TRYiG8DonNpHxvXctcgmLrK4cdBh4AEAdZE8B8tH51z/Ku 0mphhvGNwIXYOCgCijeE+R7bYwN/mQWbcfKPW7d4uTKMFDwZO5iY5BmAUkzsO0pEUCCX KhxJWWN/thsR6FNOrd6UyqqxTqSS31plBN7rm3VvANSiydDsKuKzc6hBlhLZ/T+/vzhq /LMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=932y6fVEjMCffWLgpBJHJF6PcFve/VsNCDEkZTsCgS0=; b=S4BZahweION447kwTtt1DCkStlKBItAAP7nW20E/k52w1/8OXYbR5z6ExVoG68ZMiH E6mpjUHj9VVByR75+TJQ6tC58t6Je68P8pHIN08OwRf+W+XSwtwp4zKpUoUX/WA6tJSb YXrM62xPkHr8i8lENkVRzx5p2wx6QoyAxQ4DJGnah/eEClUcF/U0R0y0OZxNyP/2yCkx b0PUm/72zzYwGu17jURcaCmfLAuRg8vyx9dOG0y9UXwR3K+aQD3ByCeqjkMCLTsz/Wpy tZLN41Ih0nb6iNo9KNV643sG9vId+NjZH45jbCVkP9IpoFbRh3SQTOGtxTmRJeLihiLk eKXg== X-Gm-Message-State: AODbwcCRgeid1kTwnO81Ybj/mpwVToMho37uohFdxTmhlm0rz1nlk7l2 HPPTqgEaVjSgS89SJ0FDGO2HRjJNpQ== X-Received: by 10.99.112.3 with SMTP id l3mr14820712pgc.13.1496004222702; Sun, 28 May 2017 13:43:42 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.100.176.201 with HTTP; Sun, 28 May 2017 13:43:42 -0700 (PDT) In-Reply-To: References: <20170528192420.GC82323@kib.kiev.ua> From: Kevin Oberman Date: Sun, 28 May 2017 13:43:42 -0700 X-Google-Sender-Auth: nNgTdQf0qfPPEgcn7tXuX5WN3TA Message-ID: Subject: Re: firefox/ rust failed to install on FreeBSD 12-CURRENT To: blubee blubeeme , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 28 May 2017 20:43:43 -0000 On Sun, May 28, 2017 at 1:12 PM, blubee blubeeme wrote: > I am using the default tcsh shell and sudo -c isn't a valid sudo command. > > > On Mon, May 29, 2017 at 3:49 AM, Kevin Oberman > wrote: > >> On Sun, May 28, 2017 at 12:24 PM, Konstantin Belousov < >> kostikbel@gmail.com> wrote: >> [...] >> More exactly, don't build rust with 'sudo buildcommand' where >> 'buildcommand' could be make, portmaster, or any other command that will >> build rust. >> >> You can, however, 'sudo -c' and then run the build with no problem. I do >> this regularly. 'sudo -c' really makes your environment into root with a >> new shell and you must 'exit' to get back to being yourself. >> -- >> Kevin Oberman, Part time kid herder and retired Network Engineer >> E-mail: rkoberman@gmail.com >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >> > > Brain, meet fingers. Fingers, meet brain. It's 'sudo -s'. Don't know why I typed 'c'. And did it twice! Sorry! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-current@freebsd.org Mon May 29 01:36:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEE16D86445 for ; Mon, 29 May 2017 01:36:22 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0122.outbound.protection.outlook.com [104.47.36.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5352C179A for ; Mon, 29 May 2017 01:36:22 +0000 (UTC) (envelope-from sjg@juniper.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CPhA1Fawx/7SLPxv5BuJhEkhyjpJ0VayWuLONfhEkkg=; b=K7SL+CBxYbt73ro8uhr90N0vy+OssiyCFTzSJBj9XvNJa0akiFlSVTajJfGFhN/9kf+zNdnZDOFPW+/b6N31AXgtwNlP3VgBZtvP0r7BYRS+uSpajidOkocB+VMqUSP31kdUyEt25Fhh2vaSwZO5zgaDFWCPF4bx3gVnTYwu6z0= Received: from BL2PR05CA0022.namprd05.prod.outlook.com (10.255.226.22) by BLUPR05MB1970.namprd05.prod.outlook.com (10.162.224.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.1; Mon, 29 May 2017 01:36:20 +0000 Received: from DM3NAM05FT009.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::207) by BL2PR05CA0022.outlook.office365.com (2a01:111:e400:c04::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6 via Frontend Transport; Mon, 29 May 2017 01:36:20 +0000 Authentication-Results: spf=softfail (sender IP is 66.129.239.12) smtp.mailfrom=juniper.net; freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=fail action=none header.from=juniper.net; Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from p-emfe01a-sac.jnpr.net (66.129.239.12) by DM3NAM05FT009.mail.protection.outlook.com (10.152.98.115) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1075.12 via Frontend Transport; Mon, 29 May 2017 01:36:20 +0000 Received: from p-mailhub01.juniper.net (10.160.2.17) by p-emfe01a-sac.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sun, 28 May 2017 18:36:16 -0700 Received: from kaos.jnpr.net (kaos.jnpr.net [172.21.30.60]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id v4T1aFX0013819; Sun, 28 May 2017 18:36:15 -0700 (envelope-from sjg@juniper.net) Received: from kaos.jnpr.net (localhost [127.0.0.1]) by kaos.jnpr.net (Postfix) with ESMTP id D77FF38551F; Sun, 28 May 2017 18:36:15 -0700 (PDT) To: Thomas Mueller CC: , Ngie Cooper , Subject: Re: Bug in make setting wrong MAKESYSPATH In-Reply-To: References: <4E.66.25473.9D551295@dnvrco-omsmta03> <81057.1495500066@kaos.jnpr.net> <95058.1495555282@kaos.jnpr.net> <24672.1495645494@kaos.jnpr.net> <68.62.09002.EB636295@dnvrco-omsmta01> <38541.1495688881@kaos.jnpr.net> Comments: In-reply-to: Thomas Mueller message dated "Sat, 27 May 2017 07:42:23 -0000." From: "Simon J. Gerraty" X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7054.1496021775.1@kaos.jnpr.net> Date: Sun, 28 May 2017 18:36:15 -0700 Message-ID: <7055.1496021775@kaos.jnpr.net> X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39850400002)(39860400002)(39450400003)(39410400002)(39840400002)(2980300002)(24454002)(199003)(189002)(9170700003)(93886004)(6916009)(39060400002)(6266002)(106466001)(356003)(105596002)(53416004)(76506005)(77096006)(50226002)(47776003)(229853002)(81166006)(4326008)(55016002)(6246003)(8936002)(53936002)(8676002)(8656002)(9686003)(54906002)(2950100002)(46406003)(189998001)(86362001)(7126002)(7696004)(478600001)(97756001)(50986999)(50466002)(76176999)(2810700001)(305945005)(117636001)(2906002)(23726003)(5660300001)(107886003)(110136004)(38730400002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB1970; H:p-emfe01a-sac.jnpr.net; FPR:; SPF:SoftFail; MLV:ovrnspm; A:1; MX:1; PTR:InfoDomainNonexistent; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT009; 1:DK1RZnCSKiiQ5xgAsXdgChTCxw4wyGSbi4HZ03gfkrJ1T6CPai9f4i4HyYAfsTm4lZuRTbPhsuZb2S5gtYuQ2Sgwkf1AbEdvN6ZDElBxJ3siNoFaYR3qA/3id/ygIud0bDS441JAw9tGl/l9+CupMEyRF5CYePpwwpuw1t+8r9fZ7SKvm/jT9nht2rEtqap3hWiFymnJvBJGfSmK2W8uWEXg1dEnaa+TBbrIREM97FHTDjoXN0tZCbqp//X+Np6JONQfwpvPNLblK1HhLgU2Hmb6vRMhA4QxfWheFier/2yyS8Uo0SIYYXb7m2o7ITkbjiN6mncflHIue1JDXG2/0kTQYytydYI9Cyn2U6Oim4/PFMI92t6nR9fgP8EIr3ocCLwHb4ulToUkp1qQINQKrcIey1iWXrZSgxeSNvS7Vrz5lVXNNXVr48C0LAsIsfmSYo1itpjuY+0p+hOtCDitwawPJ4ijY4k7oXtle9/Wgiz2QxcQ7ZpTK7EF39KEz1z1LvGJmNU9Po3Sl7Bghq6n7wyNmRU/Gx7pGzz8mlFP6pv6SDjp72RO/NUSU2bicIOe X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: BLUPR05MB1970: X-MS-Office365-Filtering-Correlation-Id: b4d73d12-839a-46be-2db2-08d4a6331bbc X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BLUPR05MB1970; X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 3:lhJuCuyDIqhwj6sUzXVbv3csm6oF5zw16t3mRKVjoEhThi0T2TrYi7saO28ILUYdxUUp4xHtHXs9y1ER5lWuu1ofMy8OF1DIJhzI6+1DajLNU2kWg7uz6usTP1T8ZJr6H1IiFmB7v9jq8gjxrJTIKKtj8KRZ3p/S3NNHEh5QVPoP6YfoxJkcVqKoq3luCbObHjvTJZ73pM1kCXkLbi1nejj+YUN8rpqZYpWLn8EznQf4HT+LQM9qCKoIZO1MSxWg8ClxHxImwGuUBwaWYhHHgLjEZoEDfrMvx40UQcvpdEE9YcXARpl1bJwU25TidzJds+G6g10/TkC9grFVfQeodAuY0pb0FSV7pDvHn2YzSoWVPrXQRc29mfDORSuWyXV5e15s4GItFtnip+4rJ9cXhvFJ8tGpaRTiZKdasfQzCi5gxZ2mZP6Hk7kXixBBwuYhdHrjghMMTlICs04wMdf7OlRnMIrHEmX64flj8oCtVNbeRISgyYm8Zwp3tldfnGLb X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 25:E7ea8v2o+V4k9K/PswbL+MjbwAY3CfrPOqMK4DU15RgNsyB/oXFM5K1d/mubMxdHJe9XNy0AikEK/tUbx7Hhwx8CEJI+NSMR2F2aZr1PW7/igfSVPri4JcPZJwBnacsmw+aXwysQ4KsSn1VB9gE4zCK9K1Fd5j4H4YqXaCbxlbQ8r7QM0sTAHN417vqBBfM0DCK8Lt1j9znrbq9gkVBw2NC4PxUFFiKDePLS/j/2agpQM5/TZjlDOkmGnsA9QNHApWGaf7kt/Lx6/eAtakB8l1aDAj5hLu//7/MN1TGBhdz3wwvtyzhbhp0C5QwaFdkdHWjnAVubV5m2+ubPUEKGbC7xhMBdxI04SdfaskgyR9RZLsjG3gcRHKmzLNVtCcJ4vb5tUOxOQf07bm0wnVrVR6M+fytUjFKQfOEepHhpsgd8vfwisb6wz+PN1/x3NpgrFA2GjtZ3Fv0+6LFG0Q45B990pGe4nOR94Nh6uYWPS/M=; 31:JGZfmmUuL+9xnhhcla3bPuFQJplABZms/gdiWQuKRzGEq9KEauvaz7J6C7R1sao0jZsRz+gvm8xRPVMW8hmbXKcqVsBuWXjxbvdMxUm3PqjI08JdtiLFlG20jYts1Rz/wlQB/y8MitmtsYTNYBW3RVMMtWrqiys7Rwjju4ngJAdSVbnbwSJ+AJQACJeraoW7eKsicB/yRQ0YYbFtLceTANqLDfkWrHzt5/eNfV2koFJy7caihBRqCL789Mt1AaIw1qImhKXLyNmweF+YpUJ5fg== X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 20:0yHHCNTZAn7Gq9p9ibFBn+ausWfuAJi8Ffq2ISKFmRJPDM9X2Kl1l9bdODCyQsJb7QQ19Cbe6ODxnSTfmoLFI5udswRkIsAKVPkJaoxmhFlGgNc+Gl7KH0l9bNdxZpOaVmZHteh5ZP/rbWQvrEqgDsDtPZBp0jdfUThEhcDVS9jJB6AujNrVLHndNpknafdzaOgDVsQ4MVr2rZPVIiRIqYsCSbA+BkXSwzvHdfUuQE+0A/v9GAO2wYKA0rWJ7Ys4bhOKjEuYwfz84K7+weZM7rNPyfvnhIcLG3ic+5DArfPYJ0SLslPEqPkEI65g+fBu+0GHpsXfcDb8EeXXIyRe7wjE3kxUOw6wGGOQjtJUBpt66yfW3r31SGe60UHZAxrq3VetGerHDT9UlOyedkbXByxcXjGJ+8qi1vJYbT1Qlfj+HGuo9VdWlI2rTPWmfmtAa3NBq7P7MYsUnaCChQ8ufZo1Gz1CuwVy292vmHc8/rkw7CQGDbL4ItsbscctYmSA X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(71323512122534); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700073)(100105000095)(100000701073)(100105300095)(100000702073)(100105100095)(6040450)(601004)(2401047)(13018025)(13016025)(8121501046)(5005006)(10201501046)(93006095)(93003095)(3002001)(100000703073)(100105400095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123555025)(20161123558100)(20161123560025)(6072148)(100000704073)(100105200095)(100000705073)(100105500095); SRVR:BLUPR05MB1970; BCL:0; PCL:0; RULEID:(100000800073)(100110000095)(100000801073)(100110300095)(100000802073)(100110100095)(100000803073)(100110400095)(100000804073)(100110200095)(100000805073)(100110500095); SRVR:BLUPR05MB1970; X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR05MB1970; 4:M08NaOYbjEk5Pm10IETH6GBDCBp3630xKm7hUw7ie2?= =?us-ascii?Q?oBDHWnDfbi+312vRi16J4f+RfcQjygC8uE/jL99O4aZh8ADfbGrVWJyD/VWY?= =?us-ascii?Q?j05b5EogoEhA3A1B/KDNwXSRJSw6yzCtz+yrgfHM1zE5PZ+L7wvDlDAV/62N?= =?us-ascii?Q?em1tSBHczPmULzxZ11xh+yVOiZ21My02ivV+gNs9zfdDa9muZ4hvM48xa8rI?= =?us-ascii?Q?xchfwbqxmZGSD5C14IRA5qugmX/Q5sVe/fULeQDAQsbkswn3QfhP4WzSjw6O?= =?us-ascii?Q?TDlZrU8GB/+ajDm0xhiTsXfjsRopUQBImGIBA6cxcOCTfht2U8GGK4SGRwkP?= =?us-ascii?Q?a0Lx/dApm0/FNOVhXi1tO019ah1evFvpJPb10f45j8N2arZDbn8Y8nspbgsM?= =?us-ascii?Q?cnSkv/OnoE/HPAifADrCURf4zM4NA0SJ765L9+DKg0lXcMUHnu4rTiEiKOw4?= =?us-ascii?Q?XQsYtSZLRwVO3jhWkd/GQTFmM1ISQ905QDwIcVtTFaLr43MvePm8WlvwewC9?= =?us-ascii?Q?uy3IE+yinuwMN4nwdmeIeOxkSq0jYdxjRWmeoVwOg9v6dmJnaB+q5arDzWaT?= =?us-ascii?Q?Ha/hkSiV10RWwlTxk2uSc/4wRehh8UgsBOgcbx6yEYwVMPqOgM3L1XLStNH8?= =?us-ascii?Q?SSEJeJXWoB8lrx+Seposhk9Dik1bIgAvyHk8Rou2mVkpTEA8NJzxvIvHiRev?= =?us-ascii?Q?5d3z/NeakuS9j5RS1XAEOhe5TVtposkNxp9VGWseOMHwSHF/B8gCC1ebVy5H?= =?us-ascii?Q?SaSWs8n36qMgbPcY5K4GpP/Ej0RV8A4jhc+V3ltpuVklaXIdMGAdU8QEumYq?= =?us-ascii?Q?sbKznk2fU5Z05vLXeZpRK3iWFEiU1qj8hnlLwuF/AQsltJwIF9t3erCTCUk7?= =?us-ascii?Q?JQUuFmUuZoFPbDraE86LR4ideUXkEx1FO/tNZbhmZR1IpViCJG81MqmPTgAb?= =?us-ascii?Q?+V9KF+0STk9Vpr8kQz1ICUdq+G+YdDVUxMN0s9rOs8o24X0cYmf7VeIkDA0d?= =?us-ascii?Q?9F9CokQ6keAmSZ/PKU9rffMcA1yDPrgB7JLrRMgnHIfnyZeKuEqEBWH6F1XM?= =?us-ascii?Q?Y+hKHdyz1zxPNFgA0JQaf4P/GkK8Jx0BkYtU1l1iEOSIrlyfSksfOsk8Q6FP?= =?us-ascii?Q?aAZl7PVDPwG/kksX0Xlnsj6241p46B3pk7+4uX0dZ0HDah2nJ2ywmekl+9mb?= =?us-ascii?Q?0DBpRhkqHFyNQAUiPliHOGHwMm4/MwauerQCN8WGHF0dHBzMFfcb5Yt1nLUl?= =?us-ascii?Q?FE72Xsn9f6cpwC2N4=3D?= X-Forefront-PRVS: 0322B4EDE1 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR05MB1970; 23:YSlFxxja5flsWIfqeos9sTUpf98CDE3PrwQcI+qU2?= =?us-ascii?Q?FX27lZRuH7IICeXbOz5pj48UeqeoD3eCHwoP/Tu4J+mL1JYNYb/bbWbJwcPP?= =?us-ascii?Q?0SzJI2xthbk0lf/Nvrx8YV2E0pwkFNXHzwqoQEXIwVTazeCX7kYuk978ZVhL?= =?us-ascii?Q?WYMe6rmMI1asf5iOGv22JICcC5QQq8/YaHSFetR+tH0CdO2jBqraFSXIo0/2?= =?us-ascii?Q?uawt81xeXJIFwtAXkOeL+jYYa9BTNd7zYBtcKpfbbkL9GwLl5mCdMJ37ritN?= =?us-ascii?Q?jo9PlYlj2k9e2VG3I+8rwJUMFX7gE2CTdqTltTOfqiliLFrrl/ASeL4CoLxQ?= =?us-ascii?Q?v4W16TxS+cgBA/DRisBUsQdxZeDGAlamhkA0bhCCURw6VKIxy7SQeVarnR97?= =?us-ascii?Q?k/OPnIQjqw62APa2tsUYhOCrNPTvv5lHZkMnthVRkFM3Va9O5gXLnM0ROwNe?= =?us-ascii?Q?uF6iKip9BdWJ9+xLiTfFk6pqJ389DbEymouMfwGW2+9br8uAlrL6aBfqtkxr?= =?us-ascii?Q?6uqewmpncsziHADOzjDz1P6aeLWs6oBZiTcofx5NSW4b5d3oBevpJTmyn+Eg?= =?us-ascii?Q?26FD/GEGCqnYkWJYuLLKd+g0Ts2Sfp8Rxg76s7cG/memp3rD/VM/vv/BPBrl?= =?us-ascii?Q?8O9RI4vUJzLw47B9SslNBJk7nuC/mwQCNbDHNaT97Oz/EIVzNPlv5sCzlxVY?= =?us-ascii?Q?sdccR1RubuW7+CFg+weibnTJeZ3BftqAUftT9Yxgn7/cGTD4C/7e2X7U29/8?= =?us-ascii?Q?ttsPl2oZobbaN6XSwRFhE0bRrFOycU1PR3YLPv4Dr6zDCXABTANEpfe1+8PT?= =?us-ascii?Q?TYw3dRfWX1DOKTTkanPj2o0KAwZdNpU7PRA20KEd4rmi6HxZb8NmAt2LGH8d?= =?us-ascii?Q?iRsVUKkqI9GIMXl9DbdP13SlQYfFU37SJtK9kfVO2f7m8vd2ABdYTiQ8HgQE?= =?us-ascii?Q?HrX3s9lCP+Xsxkt6ylFxuv9LUmFsmljJJNJlOcIqd8qAfqfFjnzNMnOV0bJZ?= =?us-ascii?Q?uom8c4GjXdFmUhl0jINcNcalSUpF/odhlIbPWE+CiYdPrmYn9kR4Y9nSlKfc?= =?us-ascii?Q?jyiuEjZOBZGi4gBOR34+a2ifzMqC6ufRZeeIO5JGUtsy4UkPu+U8qMlJk/n5?= =?us-ascii?Q?GW8j0vb6cgxOOmVjivEfnHc0ASTAFJHyOQ7XbBXn0vp0sauhByxFxU20WYQf?= =?us-ascii?Q?5Y0DIgsdZrGc74PZjdajCApcARvkgN/u72yivtWxDSiUwuw+q6bC8r/FkXPP?= =?us-ascii?Q?G7MfaQ7Mhd4lKanw/Jr9NyBd+Ehz8TJxDu/B5+m7c0P0kdwZd9HmnsO4OhCc?= =?us-ascii?Q?FtZlgvwGWziKEB8NaD2EorsKg5L5b81Vm9zUkTU6bk0UqieW7i2b0P/T2JSk?= =?us-ascii?Q?DZIGw=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 6:+5Xj5C/mX8sRcgBbpyZNpali8xxhydGJ41FW8offOfy98TsrWF/5Y5iOyKbjNqlrSDU9XATYxBC2v5TVVGfBz/QakbdvlcSa+zBvm1J/73z9l5FDo+msMfUpCnb5XWMaFvLmL4gKrHeISViaixNrQ4zMVgMihgPB/n8I8QRlpHWuo2Dr/xVOfgwUymf5Po0ATlyly1Tm6PQyZnMQzM0ibP9UAAy5JkYbKIiqr1NbzAL0qVYQL0MNGgq0Nn2aYotv1vZ3pyfowtPxFNPF0v2SwYlEojCXGWSd/FA0DYdTdpIzCchtohWzzaX5pDopFdKo5eqYXqFOogBE+la5aBwsn7/4qocD5setOLfNsKH9ZB1fnZ3aMCZ60FYeafg0aWWyY2ZC4YC9SMOjic4N0v4t64QI5b0l33rBn+nDVj0xGZdDEdcbussc4CHY+4G9efL9eI2tsGFQET9dVba+0Nqc9aCX0WydzrtjPUPEwJWTIgMFesCdiLWFtePaA4sRmjPymWBPrFWbpa1Q+tiHtRG44qQ8eY9lD2gzeG51wjp8Ml8= X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 5:mLX7x016W5tOTR12eT3fq4ze0GzKpLP+t8xTxtm23ptdu8j2UqkGsBRgn9NGrqiOLqAf2hPrSC4C1If/xM5I4QC16MDOYd0HLReqKZpM+JME5U/Itxx8QbEB9+9PLOrQCPhhVwQ/QbFMpvchyNBgykrapu0AZGE6Sh7J9DLro5uMFarrfhG1dFpEjcr+x42eGKw2WzQNSqlkN77eem+Bwf4goaPfOsBNsO9RRsVTU40wlw1ULyFUinGlhH44+FtDZ+s8pA7TDccaUIJFTKES8F3ADeUbadacykXllPAdn67nyv1ozQafnOvkQLM/osZz2BzLoI23ENmWRqMfahXssPx5GxjNrWl7JO29cfngaxgTNwqIuq67dcRGe++UuH6IN1UUH3ABZkHTeWwDio2/3kLBWNt6C3w2e7yclufINvuuAy8bS+0NkPalVwqyHKZM+onUowI0lzDB3SdNMeGHyiZB9b8ifDPfQLj4RGsqJ3QdOITG+U5+CtAJ1QHdQiIY; 24:5e7zOojHCjGaQb0K52XdSzkT7AT1Sauik8ywlzaa802Mx/Mxx9UJN3EI6W1XEaXmzSXstoe7K5OOGfJCU6l6l+VGZtpLXxf0LbI4zVrQJlk= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; BLUPR05MB1970; 7:EeeAm1vLlq8Nyhjw7YyXJISm3ypcokCWqP1Xj0hgCw01zsR5uy1h8/OnXDZKaKrIoAw8PVeGTF5bFr/9cYBRbCiBuoL31IYPR022zzJ02GrsXoUQL7KAWv2/lHeqU/Yv7sNNmi7TcnnkjV7mbt3ejyR1CmY3Q3pYpxcfsjV8pTOYiDhRMn6ayWTQQomulrl+e39WZOCSGUhCgF+iz1/9EoAq50bVkEGh8N+CbkngFcEWti0sPJQDmnDaZtiDagrlVR3I9RpNQSeWP5N42Sbi/lTZuC3sV2GK8JH4a9L+WC0TkcuxpS/7Eb0YSIpVtS6YD9/nkeMWhilec//8A1c2CQ== X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 May 2017 01:36:20.1674 (UTC) X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[p-emfe01a-sac.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB1970 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 01:36:22 -0000 Thomas Mueller wrote: > Just because I found a workaround does not mean it is not a bug. Sorry I don't know what else to tell you. make is behaving as it should, based on the way it is configured. That setup was deemed the most useful by those working on src/, so is not likely to be changed. I guess we should add a note to the man page... From owner-freebsd-current@freebsd.org Mon May 29 06:56:19 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED116CC25DD for ; Mon, 29 May 2017 06:56:19 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 841A91DF4 for ; Mon, 29 May 2017 06:56:18 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from MSEXCH13.mands.hu (192.168.4.5) by MSEXCH13.mands.hu (192.168.4.5) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 29 May 2017 08:41:03 +0200 Received: from MSEXCH13.mands.hu ([::1]) by MSEXCH13.mands.hu ([::1]) with mapi id 15.00.1263.000; Mon, 29 May 2017 08:41:03 +0200 From: =?iso-8859-1?Q?M=26S_-_Krasznai_Andr=E1s?= To: "Oleg V. Nauman" , "freebsd-current@freebsd.org" Subject: RE: INO64 Effecting Firefox Thread-Topic: INO64 Effecting Firefox Thread-Index: AQHS18rCIbddq//sD02c3HwU1KwpIKIJyGmAgAAJ5ICAAQT6UA== Date: Mon, 29 May 2017 06:41:03 +0000 Message-ID: References: <20170528180919.7821e484@thor.intern.walstatt.dynvpn.de> <5493690.zc92PMVLEF@asus.theweb.org.ua> In-Reply-To: <5493690.zc92PMVLEF@asus.theweb.org.ua> Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.4.90] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 06:56:20 -0000 Hi, Since last Thursday's update of Freebsd-12-current kernel, world (and preco= mpiled packeges with pkg update/upgrade) I experience rather large number o= f Firefox crashes. Sometimes it crashes without opening any pages (I just s= tarted and left firefox for a few minutes, it crashes with the same error:= =20 A coding exception was thrown and uncaught in a Task. Full message: TypeError: malformed UTF-8 charachter sequence at offset 0 etc. )=20 Version numbers: FreeBSD-12-0-CURRENT #318917; firefox-53.0.3,1 best regards Andr=E1s Krasznai -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of Oleg V. Nauman Sent: Sunday, May 28, 2017 6:45 PM To: freebsd-current@freebsd.org Subject: Re: INO64 Effecting Firefox On Sunday 28 May 2017 18:09:19 O. Hartmann wrote: > Am Sun, 28 May 2017 08:54:35 -0700 >=20 > Pete Wright schrieb: > > Hi all, > >=20 > > I can't imagine that this is related to INO64, but since upgrading=20 > > my world and kernel on drm-next (which merged upstream CURRENT as of=20 > > May 27 which should include the ino64 work) I am having segfaults=20 > > running firefox. Previous to this firefox was very stable for=20 > > work/personal daily use. > >=20 > > The error I'm seeing is: > > Full message: TypeError: malformed UTF-8 character sequence at=20 > > offset 0 > >=20 > > Firefox does start and I can load a page or two before it sefaults. > >=20 > > The full console output is here: > >=20 > > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f > >=20 > >=20 > > Posting this here in the off chance that it's either related to=20 > > ino64, or some other recent change has caused this problem. > >=20 > > Cheers! > >=20 > > -pete >=20 > I see similar problems. Out of the blue, firefox crashes. > But in my case, firefox is "old", since it doesn't compile with=20 > WITH_LLD_IS_LD due to a very strange error (Bug 218808). >=20 > The binary I run und CURRENT (FreeBSD 12.0-CURRENT #8 r319001: Sun May=20 > 28 > 00:21:16 CEST 2017 amd64, WITH_LLD_IS_LD=3Dyes) if as of >=20 > firefox-53.0_2,1 > Name : firefox > Version : 53.0_2,1 > Installed on : Sun Apr 16 10:17:14 2017 CEST > Origin : www/firefox > Architecture : FreeBSD:12:amd64 >=20 > I got a kind of relief (means: the frequence of crashes is reduced)=20 > when starting to rebuild all ports again (I'm staying with make and=20 > portmaster) to meet ABI requirements after ino64 has been introduced. >=20 > Another strange behaviour is: firefox crashes very likely very often=20 > when started. Once it has run a while, I can consider it "stable". It=20 > doen not crash then. Please try to rebuild firefox. It helps me today with firefox-esr segfault= ing on my desktop running 12.0-CURRENT r318856 From my limited understandi= ng of stacktraces it was related to libthr changes. _______________________________________________ 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 May 29 09:00:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD886CF4F84 for ; Mon, 29 May 2017 09:00:05 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B35C716AB for ; Mon, 29 May 2017 09:00:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LaJWs-1ddqyr3pnS-00m36Z for ; Mon, 29 May 2017 10:59:56 +0200 Date: Mon, 29 May 2017 10:59:49 +0200 From: "O. Hartmann" To: freebsd-current Subject: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined Message-ID: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:5PbTvq3Y9hsdtCvqtUGRTkPpHRmozhRaYOxQcPvsWocy9NQqP3G 3YioyEuVLeYb5OzqQSoaZPHOTbSDin/KcWLNZ05xQG3aW99EzEqzTilhmjWEo6LEHsFdOGi MdV5Lb8eGCQSAJIQ4cWZ4rNqRR8UQPJ993zo2hdVdrTiNGHm5QhrITZqTnGmcvUPDMn6Udm sIId4gdW5z9XrVSUeaD1w== X-UI-Out-Filterresults: notjunk:1;V01:K0:IQRzkODXTzg=:2X07sKBHmQB+38klTerXJu +EbX23H7KOQcimz9GKoemEfNwLfR4IoNpzPf3EA/HTphtKUbTU2u4eP0XVYprcA73Ufi4MtZj JjxtiUd5kv/BW0LFfGRb+jgcej3uv/+P96gtlON2Lsy1vsl09Y57f9Hrwm63SGiQYzhqJxQfg 7TO/kJfAh3lMRTarNThpPpOXQsOJKM9k58a74FepA9OgbeOSfvL8GNq9qXXCQPoN/Y2mNp7/Q L72K1XmPVSloqa8j4pQAGouxBz+teWkwssO8dYf9Qb4Y+nqnd/y4ZbTyYRduBmoL1NNYfwG/V xwmBRO4WYedUdQdG1BsRkB+SyYmFcW80jqsCzifyIh3JVIp/frIeaKY6wBqximF7vd7bBDqSC Aq6QHhRv8A0RT5u9SQfTpJ/eebGUeMbwOBNa9WhKaH2kn2XyzjAtdNitMyHCIuc4KWDja2Jyf NPXIcmGIXBzmw3wMTL35yKRaiy6nUVmRZ8IJLSCvY3M5SR1/F6ydBlKaE1nYfIimUXc58uInd 7m6wNt2oYj2ubrcoQ6MR2unqpU0xkR+QdBcEzY2VItPKKYp2IB2eEtqPaiZOP0keYfpJOc1ge J6fXs4WYxI/6zBwK9zADNdIG3rXKrFjIjTlxu32Qe6cEkk80a9xKBGx84ADN5yUcNyBd09f1e Yi97X9fVnkqHD85LVPVTU9XO4y8pR3dmvXmpl3iHAqqL6MIY1W7qZJWH7HhnmdB0jN9wqXhrP rBe9SRWMDB7tsG3MtrMZ9rfE4p30Uv71PJa/Zs/7agvJuDorbMQgtp4QtwWLp8X2p/lBGXrwD xUf4dzy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 09:00:05 -0000 After updating several boxes running CURRENT after introduction of ino64, I have one box which persitently rejects compiling and installing devel/libunwind, as you can finde below. The box in question is running FreeBSD 12.0-CURRENT #22 r319083: Sun May 28 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD=yes set. Another system, which has also been update to meet ino64, but hasn't completely switch over all ports to the new ABI by recompiling, seems to work. The OS version in question is FreeBSD 12.0-CURRENT #1 r319088: Mon May 29 06:56:45 CEST 2017 amd64, also WITH_LLD_IS_LD=yes set. I tried to recompile again all required ports for devel/libunwind via portmaster -f, even some addtional ports on a hunch like gmake, gperf etc., but without any success. The difference on both hosts is the CPU: the failing is IvyBridge XEON, the working one is a Haswell XEON. I'm out of ideas :-( If someone has some ideas, please send me an email. thanks, Oliver [...] libtool: link: cc -O2 -pipe -O3 -fstack-protector -fno-strict-aliasing -fexceptions -Wall -Wsign-compare -fstack-protector -o .libs/Gperf-trace Gperf-trace.o ../src/.libs/libunwind-x86_64.so /usr/ports/devel/libunwind/work/libunwind-1.2/src/.libs/libunwind.so ../src/.libs/libunwind.so -lgcc_s -llzma -Wl,-rpath -Wl,/usr/local/lib --- Gperf-simple --- /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_init_local' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_init_local' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function measure_unwind): cannot preempt symbol '_Ux86_64_init_local' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-simple.c:(function measure_unwind): cannot preempt symbol '_Ux86_64_step' defined in ../src/.libs/libunwind-x86_64.so --- Gperf-trace --- /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_init_local' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_init_local' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_local_addr_space' defined in ../src/.libs/libunwind-x86_64.so /usr/bin/ld: error: Gperf-trace.c:(function main): cannot preempt symbol '_Ux86_64_set_caching_policy' defined in ../src/.libs/libunwind-x86_64.so --- Gperf-simple --- cc: error: linker command failed with exit code 1 (use -v to see invocation) --- Gperf-trace --- cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [Gperf-trace] Error code 1 From owner-freebsd-current@freebsd.org Mon May 29 12:20:03 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31B32CFDC09 for ; Mon, 29 May 2017 12:20:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DE67077209; Mon, 29 May 2017 12:20:01 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA14950; Mon, 29 May 2017 15:19:59 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dFJeQ-000MT6-TK; Mon, 29 May 2017 15:19:58 +0300 Subject: Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) To: Rick Macklem Cc: "cem@freebsd.org" , "jeff@freebsd.org" , Ryan Stone , FreeBSD Current References: From: Andriy Gapon Message-ID: Date: Mon, 29 May 2017 15:19:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 12:20:03 -0000 On 28/05/2017 01:20, Rick Macklem wrote: > - with the "obvious change" mentioned in r312426's commit message, using > (flags & SW_TYPE_MASK) == SWT_RELINQUISH instead of (flag & SWT_RELINQUISH) > 121minutes Rick, can I see how exactly your variant of the obvious change looks in your version? I am asking, because I meant applying that change to the original code while it can be also interpreted as applying it to the code after r312426. That is, does it looks like this: preempted = !((td->td_flags & TDF_SLICEEND) || ((flags & SW_TYPE_MASK) == SWT_RELINQUISH)); or like this: preempted = !(td->td_flags & TDF_SLICEEND) && ((flags & SW_TYPE_MASK) == SWT_RELINQUISH); > I also tested: > ((flags & SW_PREEMPT) != 0 || (flags & SW_TYPE_MASK) == SWT_IDLE || > (flags & SW_TYPE_MASK) == SWT_IWAIT) > and it also resulted in 121minutes So, this sets the preempted flag for SWT_IDLE and SWT_IWAIT cases. The flag makes any difference only if the current thread is calling mi_switch() but remains running (of which typical cases are preemption and yielding). As far as I can tell, mi_switch(SWT_IWAIT) is only called when the thread is already inhibited via TD_SET_IWAIT, so that should not make any difference. SWT_IDLE is set only when the current thread is an idle thread, so that should not make any difference either. Thus, I am puzzled as to why this change could make any difference. Could you please post full code snippets for each local change that you tried? Also, could you please capture KTR sched trace while running the test on the kernel with no local modifications and on the 1yr old kernel? Ideally, I would like to see the trace with KTR_SCHED | KTR_RUNQ compiled into the kernel via KTR_COMPILE and then enabled at the run time via debug.ktr.mask=0x20400000. Thank you. -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon May 29 14:50:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08147D4E041; Mon, 29 May 2017 14:50:06 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7C167C5BA; Mon, 29 May 2017 14:50:05 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x235.google.com with SMTP id c15so28031480ith.0; Mon, 29 May 2017 07:50:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=Sncpeh8gUE3B2jqtJ65n+Q9rU5tyuHxplZ871zGSZDM=; b=dEUZPFAKCXoMYNr6kugy7jj3DpEHbyQqjB6uADCM3oCn1ffqxtgaSmQsQHvrJ3W/By i4XAqWv1CPTlha9l9PNYXg5p0o4Fi8VfBPxzfm23KkhSDA2PflaWUcUD5PGiLuXULVFb GoWofAvfWsapzrIpUpOfbTYdQwa9gtlJO4Po6HiNMXnuqMEb7S9dilDqXERouoqOibkB 6Ue4N0t9fqaX4mLVGEjm8pmfHRQlaoVS9WCVMXg/BroOpabu5hTuaQ7pXKI8IEqDeeJT LmQZ0v/nWOecVQVyqrnD65A3fTFQfoc7+HOFV/t/Vfwhq/emqB8hr2MJ7YX9C/7GCOjA HKgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Sncpeh8gUE3B2jqtJ65n+Q9rU5tyuHxplZ871zGSZDM=; b=J+JbxXgdXw8/y1Ismd0vBI4Fme4Z7XTssTQi2bmedr014UkdoRiqXOcOhDpHDFAUfc WJwMSnUTk9oWkjjcsvDghAKmTG8mYtxRfGzvryeb5gvhlNQoep1coMPmE7oP2Iw70XMI dsTcWbpqPnOd/J4ysm5CwgZ8PT2FyNnczuuagj1KxAn1auSPojxrEed0FitQn4Fl0MJy nTKIEKQs2v2lfwJ+S6KmxxaELvQTz7ElRyuHzrVunRpU0BF2CPbVnWIkuHyro+7FNLus p8UTUiOtUCrkK9mN++rx3aM2D0TX3rj4pPRd1Ecxwx8tFlnY8hTgaZpXkNOSg8ltkZLM 7RVw== X-Gm-Message-State: AODbwcCqhyDYfYoGz2X308I0q6VKPbIzi1AlzSJzGm8xouaXru0dcmMR 38nv+I8uG9s1XNNAnumNX4cbnjyPQcxYhak= X-Received: by 10.36.91.212 with SMTP id g203mr14195572itb.7.1496069405046; Mon, 29 May 2017 07:50:05 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Mon, 29 May 2017 07:49:44 -0700 (PDT) From: Ed Maste Date: Mon, 29 May 2017 10:49:44 -0400 X-Google-Sender-Auth: IRScAaswV6cyiU-1CUWAczCYeMc Message-ID: Subject: ino64 status update and upgrade caution To: FreeBSD Current , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 14:50:06 -0000 The ino64 project was committed to src last week[1][2] with UPDATING notes added shortly thereafter [3][4][5]. As some people have been tripped up by the ino64 change I want to emphasize again that the upgrade procedure described in UPDATING should be followed exactly. The reboot after installing the new ino64 kernel, and the addition of COMPAT_FREEBSD11 to custom kernel configurations, are crucial steps. Note that this upgrade is just the usual standard, documented procedure and is required whenever new syscalls or other forwards-incompatible changes are introduced. Prior to ino64 we have had a period without any significant Application Binary Interface (ABI) or Kernel Binary Interface (KBI) changes and it was possible to take shortcuts with the upgrade procedure. The ino64 change is backwards-compatible but not forwards-compatible and shortcuts must not be taken. (As a general rule, it is safest to always use the full procedure unless you follow the commit mailing list and are aware of which changes are not foward-compatible.) In addition, some users have created a libarchive.so.6 symlink to libarchive.so.7, in an attempt to run older binaries on a fresh post- ino64 install. Do not do this: libarchive.so.6 and libarchive.so.7 have an incompatible ABI and this will result in incorrect and unpredictable behaviour. The most recent -CURRENT package set was built prior to the ino64 commit, and thus will not work on a fresh ino64 install or snapshot image. Until the next package set is available please build from ports, or use Poudriere to build your own package set. Most ports with a dependency on ino64 have now been patched. The remaining ports which still need a change for ino64 are: Port Responsible for # Skipped -------------------------- ---------------------------- lang/gcc6-aux 54 sysutils/py-psutil 13 (fix in review D10801) devel/llvm38 6 sysutils/py-psutil121 3 devel/radare2 0 emulators/qemu-user-static 0 lang/ccl 0 lang/dmd2 0 lang/gcc5-aux 0 lang/modula3 0 lang/rust-nightly 0 lang/twelf 0 lang/urweb 0 net-mgmt/netdata 0 [1] https://svnweb.freebsd.org/changeset/base/318736 [2] https://svnweb.freebsd.org/changeset/base/318737 [3] https://svnweb.freebsd.org/changeset/base/318757 [4] https://svnweb.freebsd.org/changeset/base/318758 [5] https://svnweb.freebsd.org/changeset/base/318792 From owner-freebsd-current@freebsd.org Mon May 29 18:45:37 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB874D7D75D for ; Mon, 29 May 2017 18:45:37 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B42D4857E7 for ; Mon, 29 May 2017 18:45:37 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id k91so45073856ioi.1 for ; Mon, 29 May 2017 11:45:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Fjuoqec/zozOi7q3X5QTeFhYJP0wylWh57NCfg0CG/4=; b=TzhTQTZyJwg2bdToBs2ZfJi9pD1m5OPxVFoza0SZZC2jAPSUEVj1agOZi3H09BfLOb 6oPoe8X2Q3DA5XPjoU/c41wDNFG+sYvOC0vNHtxQ9yc7kWq9yAvjrfIHnthU5EpUxViW MTWR75cwxGEOISJKFXrE6DwX0AGQ/+h2FNADh/Qe4fKWTDPh7gWaRPAQt9QSOrRm1eum Wi6nDNuE1X+TRCxZEXZC9I53dnaXSWH418wZPtez/2UmCvF5qn/2t942sTY3KG0z/Awg /CcYaE2xMmucH+zcJF13mzaKqsE96aT+wefIZ9AADMZ3//MjiEu3+PWGRaGoAJuuQ/IW CipQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Fjuoqec/zozOi7q3X5QTeFhYJP0wylWh57NCfg0CG/4=; b=Zb/cAzXbxb368ucK/pmUF54VAIOSQD736tNOXkRgMfGw3tXuCRXknRvHYMiF1mu9rZ rmLY1KTnti9IrItLz/NVw39YkoOv4kRZhUeygPL2Mb1se3eSKsq6TPULd+Av1Ii8uwMS BQ4gm3ClxyHrmDaWacGYupvp0vwJ0cLdr17TzRsAEUBq9lqrRc3tK7+DS+E/8hAndBWu V2vFiyQKIT1OcB+AKOgQT5V0i7c/n2r0XqwBiZcTPExudcTBy6vxG6ciIgadHGnfn5dy 8Lg77m1t+TmCjtDAbeElGYxSwIyDj4I5Y4CABrbB5yKe5LS9AnVeKSz4NLhqwYNFcv0R 989g== X-Gm-Message-State: AODbwcC55DBmTXtNJ4/1/FvLwuJcJdpw28AljHvs4eH/Uuz/GGJLgpnu xNv4cULDV4fQMHiMoBruPCJpwjNcosxlajg= X-Received: by 10.107.170.16 with SMTP id t16mr14099222ioe.113.1496083537018; Mon, 29 May 2017 11:45:37 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Mon, 29 May 2017 11:45:16 -0700 (PDT) In-Reply-To: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> From: Ed Maste Date: Mon, 29 May 2017 14:45:16 -0400 X-Google-Sender-Auth: OHk5jxg4mewKp2Mq8S3KXCNWLEw Message-ID: Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 18:45:38 -0000 On 29 May 2017 at 04:59, O. Hartmann wrote: > After updating several boxes running CURRENT after introduction of ino64, I > have one box which persitently rejects compiling and installing > devel/libunwind, as you can finde below. > > The box in question is running FreeBSD 12.0-CURRENT #22 r319083: Sun May 28 > 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD=yes set. What's the difference between this and the report in PR 219524? AFAICT this is just a known issue with the libunwind port and LLD, and will need a change in libunwind to fix. From owner-freebsd-current@freebsd.org Mon May 29 18:03:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE363D7C725 for ; Mon, 29 May 2017 18:03:33 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from sonic321-48.consmr.mail.ne1.yahoo.com (sonic321-48.consmr.mail.ne1.yahoo.com [66.163.185.229]) by mx1.freebsd.org (Postfix) with ESMTP id B127583D56 for ; Mon, 29 May 2017 18:03:33 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1496081005; bh=/rTf32qdc3fq/TVgsWSNgllUMGNyvkM1uTWQFy1ycp8=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=umPnWvYT0g3Bp7PZvkXhmMndqAgMQ6CyypBEGONDLafzr7FV7yc0rJicLC2TvbaDvDofXsbCGmdeICFs/Q1tUHZg0b3MhcjNG5fbtyF9p5N1TcSXhjK59biCAYsHwG5/i3kHaBVo6h+vAp67QuSVPqT8J1YRWOL2p7+cQuBL0SECYSu0+AlLfmP6brBrm/tjrj/pWnnSvDzpJoUFwVXZJqXMiayaamtH8nlCd+lUJjH9U2ju4W18QM+xOU/4ZBDKJrFIjktPd1xsSKu5ia9fn4/1smHImxnOs4KYODJReKYX0gOCNkF8xZXY8XsIcvir3THC/XHZGbT6p3COnmePnA== X-YMail-OSG: XnX1sXsVM1lsWZIE9.JQf2_DhWvQPXcVPMEVZJ0iOCyOR8yfTA5XLbPnukmV3Rc v4qIseiGUaqUfSFvRMssEIi.tlxEIbQvZt9EZ_k0fqO5RSX8FiDQ8HH_FOichttBlL8yFCSVjCsW xvFlWRs4VD_o.1ma7u69AXX1HUJuroXk8OeUB1aIE6lcm8IqeBQlkcl5koIFO9UMgt9urGjeo0ZS lfHc6j2GSVoswR_rLQQuNdiUJ0aS3er3fhGInrj4tEoIha8gdUbyJi6XBlrmWQt9ffJCMTeEJrXM yDRwx1.2KvN1BmZeuvXLXD9cBkHfJhzuxitqmWqXd42b7V_I4b2pGJIDtJzJV5hBKTJVkjO5hQd8 4hzC4RVStzwA8fk5m0nVPdLl.s5wA6rqm8Qy11SRkDYihQkYzFnbVf.W9jfdd9y2YrldsH0zrnHm sPyGdWhejEUul3LUxweWFn7niKyGrALuAWeJYMopsd6edECU2UUFcfFrXoer2hfHXmEfMEajkr4t 4neHbzgFQQAhukidGWs3QKBCIoSPxrarS Received: from sonic.gate.mail.ne1.yahoo.com by sonic321.consmr.mail.ne1.yahoo.com with HTTP; Mon, 29 May 2017 18:03:25 +0000 Date: Mon, 29 May 2017 17:59:24 +0000 (UTC) From: Jeffrey Bouquet Reply-To: Jeffrey Bouquet To: Cc: Message-ID: <1116168837.2488786.1496080764980@mail.yahoo.com> Subject: Xorg error 'alphasort' MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit References: <1116168837.2488786.1496080764980.ref@mail.yahoo.com> X-Mailer: WebService/1.1.9726 YahooMailBasic Mozilla/5.0 (X11; FreeBSD i386; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Lightning/5.1 X-Mailman-Approved-At: Mon, 29 May 2017 20:24:36 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 29 May 2017 18:03:34 -0000 First try, did not build, to try to fix, Xorg, took the easy way out and restored the /usr/local/bin/Xorg that was working two days ago from backup. ............................ Xorg.log.0 says it is devd??? ........................... error in Subject is only from memory. ........................... Fixed, temporarily, in under 15 minutes here. No time to investigate further, just wondering... ............................. 1.18.4,1 >> 1.18.4_1,1 xorg-server was done within the last 12 hours from pkg 12.0-CURRENT ino64? not upto speed... on that either. Not tested: xorg-vfbserver xorg-nestserver From owner-freebsd-current@freebsd.org Tue May 30 00:32:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85642D8642A; Tue, 30 May 2017 00:32:50 +0000 (UTC) (envelope-from kcaseysw@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45BD068DB7; Tue, 30 May 2017 00:32:50 +0000 (UTC) (envelope-from kcaseysw@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id b204so93484245oii.1; Mon, 29 May 2017 17:32:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Ntl4tOxW754GWvFAgjEM64kKAdzsPCq/9WX7ZcOw4qE=; b=PxD4KtxP+bX2xpR6ReDcT7IQfsYyyqOGypKWn5ftBQsHo5rznUw7NYYNllRjNoFneb TE8h14RDmbic8n38WYoYkNctuzrf+v0TZ3It3McZ0YjkklKbVSPBY+E251xrU2IJ7mna mK5jVvaQlREiz+Jh5MdmlsVTaNO56FZ+V82vCzrVS/MCTj1tqI2O167GPZXeL4OobSMg BgII6jWufQXelqJbsnSLSjv8DZv5t04/RIfRxI+9flE9Kn0bvkPux5JLvWV868AInjQP jzOmORD+fU4UbAFx9UXa6vMtMKqR3C52IypwMduy/gyy66Ji7xNFSHJ75H7GNRiRQgYr GDzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Ntl4tOxW754GWvFAgjEM64kKAdzsPCq/9WX7ZcOw4qE=; b=g+ZJbZf+ljfzD1zfFPyu58NyRFCE7xv+q5oETYockQSO3YhOAbwZAiQFc1LsahKYR5 25ED3DUFYEqhrlG+JYIhyKML37VtGkSVn9YEkseK6vWiADPINnlt1zZvHID245+tjYXc YZrpXYsrk1zGcWefviL7g1dqhOnlC0SfXV8UeFpNH0K2q6WlNS10QBwMZqERmr+NnTSd kMOLzBZrsX7h023WrXcdYGS9PgelFMw2ssI5znWzSfbekSlBqYBnO0ZF2yPAVHY/ZpRx 62+sV0F/WJVVVf9rfPHWiY3ijDPc7N+5E4C6DFZOgSrP4it04he10uoOWQzhi9/yseOA 9q5A== X-Gm-Message-State: AODbwcAxoPkNdFEVcdwcCLLaRocyKcwZMXA6YkDikggzdXfO1LJjJK2f r6rjUZJQ2VK8xF48Beo= X-Received: by 10.157.61.101 with SMTP id a92mr7441728otc.259.1496104369121; Mon, 29 May 2017 17:32:49 -0700 (PDT) Received: from [192.168.2.92] (99-21-194-223.lightspeed.sndgca.sbcglobal.net. [99.21.194.223]) by smtp.gmail.com with ESMTPSA id q35sm5063139otg.7.2017.05.29.17.32.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 May 2017 17:32:47 -0700 (PDT) From: Kevin Casey X-Google-Original-From: Kevin Casey Subject: side-effects from mesa-libs and ino64 updates ...? To: FreeBSD Current , FreeBSD Ports References: Message-ID: Date: Mon, 29 May 2017 17:28:16 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 00:32:50 -0000 I would appreciate observations about two difficulties that have surfaced for me since the mesa-libs and ino64 updates. Likely these are pilot errors but I've not been able to identify the causes. Here's the environment ... FreeBSD silver 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318232: Fri May 12 00:21:37 PDT 2017 root@silver:/usr/src/sys/amd64/compile/silver amd64 /usr/src revision: 319159 /etc/src-env.conf WITH_META_MODE=yes NO_SILENT=yes rm -r /usr/obj 1. buildworld runs now fail: Building /usr/obj/usr/src/share/colldef/es_MX.UTF-8.LC_COLLATE --- all_subdir_lib --- /usr/obj/usr/src/tmp/usr/lib/libgcc_s.so: undefined reference to `__gxx_personality_v0' cc: error: linker command failed with exit code 1 (use -v to see invocation) 2. with ports as of: Fetching snapshot metadata... done. Updating from Sat May 27 09:42:54 PDT 2017 to Sun May 28 16:37:47 PDT 2017. echo $QT_SELECT qt5 attempting to re-install devel/py-qt5-core with portmaster -d py27-qt5-core yields Error: Failed to determine the detail of your Qt installation. Thanks for your thoughts. Kevin Casey From owner-freebsd-current@freebsd.org Tue May 30 12:28:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DA90B7BCE6 for ; Tue, 30 May 2017 12:28:50 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660078.outbound.protection.outlook.com [40.107.66.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CB0684040 for ; Tue, 30 May 2017 12:28:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1124.9; Tue, 30 May 2017 12:28:47 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1124.016; Tue, 30 May 2017 12:28:47 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" Subject: patch that makes max buffer cache block size tunable for review Thread-Topic: patch that makes max buffer cache block size tunable for review Thread-Index: AQHS2UAIoDTGzgNSjUW2F1Ji7nd3zA== Date: Tue, 30 May 2017 12:28:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0189; 7:CNsUomLXFZxONW/oiJ1zsKomOrlOW9DYkIcnj683JDP7rjopcvOvePnTZqGwsQ3HBEWqsSBj5f4sJjmws3COG2FWn61X1UgGfGU+8ov81k7mWF6yNe/Y+X5wUwJRxuC5q51pzdzLPFwDKXQr2OrhVWlePPGCSWjPCr25SjJGLxzOf1IGHlGFhshEwGznsIChXz6107hRu5woe+zI8V+ojPPOs2rH8U/H1U1AupTKau9IX/WDgE+A6zj+K6/p90YvfqXNVVK/qrcV/KgD/WzPP9wfID14PIMiocIyWIq64ZG2MnhZP8L3x+8bjty9TUm79LzCtoCbEeFRM2D3kG2fRg== x-ms-traffictypediagnostic: YTXPR01MB0189: x-ms-office365-filtering-correlation-id: fac6dea3-3960-49d2-c746-08d4a7576b7e x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:YTXPR01MB0189; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123562025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123564025)(20161123558100)(6072148); SRVR:YTXPR01MB0189; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0189; x-forefront-prvs: 032334F434 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39400400002)(39450400003)(39850400002)(39840400002)(39410400002)(52254002)(54356999)(8676002)(81166006)(38730400002)(50986999)(6306002)(9686003)(6506006)(74316002)(8936002)(6436002)(5660300001)(74482002)(5640700003)(25786009)(6916009)(7696004)(53936002)(77096006)(55016002)(122556002)(33656002)(14454004)(110136004)(86362001)(2906002)(189998001)(966005)(3660700001)(2351001)(2900100001)(478600001)(3280700002)(102836003)(305945005); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0189; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 30 May 2017 12:28:47.2765 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0189 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 12:28:50 -0000 Hi, I just put a patch here: https://reviews.freebsd.org/D10991 that makes the maximum size of a buffer cache block a tunable. This allows the NFS client to use larger I/O sized RPCs. By default, the NFS client will use the largest I/O size possible. What is actually in use can be checked via "nfsstat -m". Anyone interested in reviewing and/or testing this, please do so, rick= From owner-freebsd-current@freebsd.org Tue May 30 16:00:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94611B82667 for ; Tue, 30 May 2017 16:00:50 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D06068B6C for ; Tue, 30 May 2017 16:00:50 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x231.google.com with SMTP id k91so59189854ioi.1 for ; Tue, 30 May 2017 09:00:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=CrLsNK115cWlhuj6xvFFrF+MWrfQu+JzQtNrOgvFIUQ=; b=l/I5KB51rI0QdGWVgAwS+adpIjZ6c0bm4olsv7k4zPr0C+ys4074031qbH95vJRQj0 vjUAsAUSd4TTuvrfwua/mQVPuVeLxgTHBEHiZmvob8kYDK/yt4ipGuDqMRKn3sq2LT3y +x5luHSWTlHj3ib9u/zNJIArMuaIyMAGUQIVif8sI7n60x/ceD1tY7nni3DPdNMFKbT7 Bf/v4/knE8fL2Ojn3Pf28suTcuNPE1nE7RfOS709eLFlsFmYRO7TzyflhFtmkRn8NwO2 41+GdLMUvSk41o895+rHByRGghSu83ljUlNfieVWpUOKH5Hj8GMpQHadgn35NDqq7MVF QkTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=CrLsNK115cWlhuj6xvFFrF+MWrfQu+JzQtNrOgvFIUQ=; b=bUO/kEvD53hFu+lE6j4Qsl/CMJJtNIi8n6MUGCq4/2lzUDZVkqwqMnjvC/F+BsI8KT qdZKDCAF7v93oh3k2qNsYRuW/WDpZPVsrk9ykQAgA1md+fkbHv+fuWuQYpwYmEn6CepV L/vlz6fUuEGMZc8myJdwkWMd1gCQyxtd8HDBNr75rxS9MBV3qvMtnAVyF6IEhWzmuLbO WWUzaxeBvbYN4YNa15rWVeyIRg21a0K6l18Q8vfRxXKCQgC4+LSM4MI51BMEgKDKDwNV UHYjncto7q4UsYeziOCkKKI8mOp2kz3Cpv+dAYrXUx/b9QCJimZhgtvpnC4msKqIksa4 5d6g== X-Gm-Message-State: AODbwcCXSSh4i4Alw6TCfqSyI5j1PtkU2HN6e6pZQIAoX+pDi3+D43h3 HoswEkL41472c7HXT5P3sckkl9ml9rQ6 X-Received: by 10.107.1.70 with SMTP id 67mr17848059iob.159.1496160047226; Tue, 30 May 2017 09:00:47 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Tue, 30 May 2017 09:00:26 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Tue, 30 May 2017 12:00:26 -0400 X-Google-Sender-Auth: keHnoaQyt5nPItA0cVnOwxgKzAM Message-ID: Subject: Re: ino64 status update and upgrade caution To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 16:00:50 -0000 On 29 May 2017 at 10:49, Ed Maste wrote: > The ino64 project was committed to src last week[1][2] with > UPDATING notes added shortly thereafter [3][4][5]. I've now added an anti-foot-shooting test[6] which invokes the new rescue binary prior to proceeding with installworld. This should cause the installation to abort if make installworld is attempted prior to the reboot into the new kernel. [6] https://svnweb.freebsd.org/changeset/base/319219 From owner-freebsd-current@freebsd.org Tue May 30 16:49:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8B8FB87DA1 for ; Tue, 30 May 2017 16:49:28 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AF246F03E; Tue, 30 May 2017 16:49:27 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.137.20]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LoEPJ-1dql2k2bP7-00gFPC; Tue, 30 May 2017 18:49:19 +0200 Date: Tue, 30 May 2017 18:49:13 +0200 From: "O. Hartmann" To: Ed Maste Cc: "O. Hartmann" , freebsd-current Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined Message-ID: <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/E8KD/6iqO/w/O1UozYGFrRv"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:+7W5fuF6np/7LeGjSPKLcISmVwmWVepDnzXNTFhPHRxqEVJAnXG E6BzIf6hGKboYGluKYMgoJ8caLicH2h3rwPHmouAolhKZntjLLiE7I2C4UpgX868uN7ZQx4 lsVKL50hhz+0IelWdKhV/2Ln2npHxfZsCSMbPiczPrfIC/78atnOTB6GVTZmMkfVYD6cXTr WD5kwsyl6AZkTesrCQSfg== X-UI-Out-Filterresults: notjunk:1;V01:K0:tY4vJSyJhas=:iWEgH5M5bqsmZearWhnh1r Wq4O2wMiUYrVvQJjVBwih266q6BI2VUiEBbQA+KjO81N6SXKH8ht3TBkGYrjTPyrb99TLqXB3 0dZ12sBYexfUMAE+18ioNRVUuU8Lf/4Z8H+HIfVJZ+L1HOb+dmgJa9DWkFXaaxAVO0CT7ivdA k1JYTKTMtccLFkj8Vx2sTUXhmTp64So5/DGNgbRefmMYVtp7pPBbQpQb6syw31ys1jUuxq0wX knuQmWNTjLiAofpodUEF1gUH94tkPMy2KI5C+Bp48bqBcP9rwoBO5e36zj7/gcA73y1PW2X2x MsGkHZ9GoYOf32XOF/lxqe0ApFHNumV+CkIheC+HU3HcObrsAFCFCQL8DviWtBQSv/GwaiUCn c/s80Fm/N82X2c5PgDjfud874N/3rj6i28acvQss17DC0TimeKcmmSRh4i3wgqnuse62n8pOk xUupl8ocvR68exEMP07bd1An8Y1GAlgWepM34wxcysitssQpvMG/DWunBKXOSJHIiJFOxe182 zmoWp/K73S08nm6KH+aQcyQNiVWsqVR9LZRAm+cCLs1YqBkYlusT6lp7uTCTSzTSMX0KB9Mlh 6EczNbQWXQ5M3yHfEbS2/Wi/FCARiyBiIYPHUkGCnHBCIiDTRpNLNA2aXtbsgsFiNj1wD0wYy iivgrGZaT72HodIIOSXYUa+2p1ZTi2LT/2BvJ88cTOUinQ6CtFNRQLLt0sTGbgg6RHkbgexTY 0LzKPFvHlPCfHpNfC2jRypRR/qCSC10+vLfKdUITrMdDzUfguEeZooRBf6o= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 16:49:29 -0000 --Sig_/E8KD/6iqO/w/O1UozYGFrRv Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 29 May 2017 14:45:16 -0400 Ed Maste schrieb: > On 29 May 2017 at 04:59, O. Hartmann wrote: > > After updating several boxes running CURRENT after introduction of ino= 64, I > > have one box which persitently rejects compiling and installing > > devel/libunwind, as you can finde below. > > > > The box in question is running FreeBSD 12.0-CURRENT #22 r319083: Sun Ma= y 28 > > 21:18:52 CEST 2017 amd64, WITH_LLD_IS_LD=3Dyes set. =20 >=20 > What's the difference between this and the report in PR 219524? AFAICT > this is just a known issue with the libunwind port and LLD, and will > need a change in libunwind to fix. There is none, so far, it is due to WITH_LLD_IS_LD. I got a kind of confused, since libunwind seemingly compiles on one box wit= h both ino64 AND WITH_LLD_IS_LD, while it failed after an update of a bunch of systems t= owards ino64. Kind regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/E8KD/6iqO/w/O1UozYGFrRv Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWS2iiQAKCRDS528fyFhY lPQVAf0eN6EfkNuWDJzFowY7UcfhUdrzICItPtYQcF92wAG7aWFHFeEW8sVkNuNS 7sxiac3wNmaBckUx9b8vgO9RsrmFAf0eOAUNYPtvMDodpHfMrRTTmrBqHZqAA7Kr Socd63k9TWSJ99l/k3O/OYw4fYdOADGDgvxs6CuBnGKURCWaY2wC =H3Dn -----END PGP SIGNATURE----- --Sig_/E8KD/6iqO/w/O1UozYGFrRv-- From owner-freebsd-current@freebsd.org Tue May 30 18:01:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A61BB957D5 for ; Tue, 30 May 2017 18:01:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 638847313D for ; Tue, 30 May 2017 18:01:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 146e579a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 30 May 2017 11:01:00 -0700 (PDT) Subject: Re: INO64 Effecting Firefox To: freebsd-current@freebsd.org References: From: Pete Wright Message-ID: Date: Tue, 30 May 2017 11:00:59 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 18:01:02 -0000 On 05/28/2017 08:54, Pete Wright wrote: > Hi all, > > I can't imagine that this is related to INO64, but since upgrading my > world and kernel on drm-next (which merged upstream CURRENT as of May > 27 which should include the ino64 work) I am having segfaults running > firefox. Previous to this firefox was very stable for work/personal > daily use. > > The error I'm seeing is: > Full message: TypeError: malformed UTF-8 character sequence at offset 0 > > Firefox does start and I can load a page or two before it sefaults. > > The full console output is here: > > https://gist.github.com/anonymous/555202b1452503ad9e26750168f87d5f > > > Posting this here in the off chance that it's either related to ino64, > or some other recent change has caused this problem. > Just to close the loop on this. It looks like after upgrading to the latest official packages available i can now run Firefox w/o crashing. I am still getting the UTF-8 error mentioned above, but have not segfaulted yet. So apparently that error was a red herring. Interesting enough, firefox was *not* on the packages that was upgraded - so i assume a shared library was updated that trigger the fault. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue May 30 20:41:52 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0F86BED152 for ; Tue, 30 May 2017 20:41:52 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8A677910D for ; Tue, 30 May 2017 20:41:52 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x231.google.com with SMTP id w68so11764548itc.0 for ; Tue, 30 May 2017 13:41:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OrLKOB+1O2mfUtABYMaxId6LpRoybcgzmwYZIg3K19I=; b=MIJvX7FHovf3U+3Ne6lO5PdhNxzBH+NkcGBK2sTeAXJynRFgCpuXgTWx1LleHMVhK5 T4XceuCyxZC04RpBQ4Xh/SAMNwOs4P9/ZaOzcdluYtO3r5V0YBeKT/NTq0Dr4PdLWU0d gEJoyuLaacrpmOFGNL2DBdVzB7+oNXO8vafuVS+Lrmtop1Nim5hYR5epBS4v6iMvew65 S9BxnT76xfsgUX6E+N3/TLMEeys9dFrLw6DuH9xZUCbkFylJ5Yhc19E/OPGGxyIsAhno dqrpbEWwaiu/fEHKcH8ncncfESRTlx5NY6z3ZwVYfevawhGkYcgqDfct+eRLArb72TRl PKbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OrLKOB+1O2mfUtABYMaxId6LpRoybcgzmwYZIg3K19I=; b=VRB2cOBj3BtlIjlIhs5CrzXOEqjCGRjiMsoKE+xR5+agd1ituK5w8RZ0jij3HJihex /OX/X4pAftDpzqfXmOo/mkM8ZvMWbomcNWA3Q+etxpyaQVIK1SZs+cyymjYUSTE4oaVz LldGg9e9Jtdw8kE/uaZuJCIF7SfuYPZOhqJWVEessD4imdNiN6hVicpeKvDPNghopRuy NtAwjRcYgMd/Cc0qdu4HqfcGJ4YObaJrjbovXhpS/jF3LZq/jnxKpFnmxkFovWfL3lZX CNfcA/hgvbPmwTSBq5NiK22yZHxqSACJ1uDA+BKqXh/3JWcywVFDU/MPh0ITNUoYaBIV cXOA== X-Gm-Message-State: AODbwcALgUPgnGgS+VxZ8tXE5U9lumhuRsZNEtDnnCkm3Nkgf4aN4bvu fQl7/3evafivPQW7uCm4CX1pXV2GvuW/ X-Received: by 10.36.43.146 with SMTP id h140mr3896949ita.7.1496176911981; Tue, 30 May 2017 13:41:51 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Tue, 30 May 2017 13:41:31 -0700 (PDT) In-Reply-To: <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> References: <20170529105949.1cecf4e2@freyja.zeit4.iv.bundesimmobilien.de> <20170530184849.6e6eafe6@thor.intern.walstatt.dynvpn.de> From: Ed Maste Date: Tue, 30 May 2017 16:41:31 -0400 X-Google-Sender-Auth: 5VmBLnK4q22UCSweDj02cvGENV0 Message-ID: Subject: Re: After ino64 update: devel/libunwind failure: cannot preempt symbol '_Ux86_64_local_addr_space' defined To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 30 May 2017 20:41:53 -0000 On 30 May 2017 at 12:49, O. Hartmann wrote: > > I got a kind of confused, since libunwind seemingly compiles on one box with both ino64 > AND WITH_LLD_IS_LD, while it failed after an update of a bunch of systems towards ino64. So was this just confusion over what was actually built? I believe libunwind should always fail with LLD. From owner-freebsd-current@freebsd.org Wed May 31 16:21:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 395C7B7DB41; Wed, 31 May 2017 16:21:59 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msa01b.plala.or.jp (msa01.plala.or.jp [IPv6:2400:7800:0:5010::1]) by mx1.freebsd.org (Postfix) with ESMTP id 9C29781E20; Wed, 31 May 2017 16:21:58 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc02.plala.or.jp ([172.23.12.32]) by msa01b.plala.or.jp with ESMTP id <20170531162155.QKZS1726.msa01b.plala.or.jp@msc02.plala.or.jp>; Thu, 1 Jun 2017 01:21:55 +0900 Received: from localhost ([2400:7800:4d3a:6100:5e51:4fff:fe11:73f3]) by msc02.plala.or.jp with ESMTP id <20170531162155.QOVC2954.msc02.plala.or.jp@localhost>; Thu, 1 Jun 2017 01:21:55 +0900 Date: Thu, 01 Jun 2017 01:21:46 +0900 (JST) Message-Id: <20170601.012146.413650928099698078.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: Xorg error 'alphasort' From: Masachika ISHIZUKA In-Reply-To: <1116168837.2488786.1496080764980@mail.yahoo.com> References: <1116168837.2488786.1496080764980.ref@mail.yahoo.com> <1116168837.2488786.1496080764980@mail.yahoo.com> X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; msa01m; Thu, 1 Jun 2017 01:21:55 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 16:21:59 -0000 Hi. I was using 12-current r318249 and did 'pkg upgrade', and could not start xorg with alphasort error. After updating r319315, xorg works again. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Wed May 31 20:53:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5559B94602 for ; Wed, 31 May 2017 20:53:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward20m.cmail.yandex.net (forward20m.cmail.yandex.net [IPv6:2a02:6b8:b030::a1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3A8C680A5 for ; Wed, 31 May 2017 20:53:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp3j.mail.yandex.net (smtp3j.mail.yandex.net [95.108.130.68]) by forward20m.cmail.yandex.net (Yandex) with ESMTP id E3E8721C9F for ; Wed, 31 May 2017 23:53:34 +0300 (MSK) Received: from smtp3j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3j.mail.yandex.net (Yandex) with ESMTP id BE3EE6240A13 for ; Wed, 31 May 2017 23:53:34 +0300 (MSK) Received: by smtp3j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id zgbBPgp3z7-rXjqPpvW; Wed, 31 May 2017 23:53:33 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1496264013; bh=7E2JpWSRZ3wi4x2WqD05etNNdYqXS2TOHiqv2h+p3b4=; h=To:From:Subject:Message-ID:Date; b=e04Qh+F7I51eVRibiBqqvAa3VJTmL+N1+bq5C1r/66EZZ6pHfWV5ZveeQw89ceoOW F/0RFi9CK0UVxnC2wqJQ4uAnVE/XTliVFYljIh8/L9Z9ayffpBQBlG47Pprbxp5ZVk 2ROzkSBLcpzg3vMUEzwQdNrcCM+59nCP3sycz02M= Authentication-Results: smtp3j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0 To: freebsd-current@FreeBSD.org From: Boris Samorodov Subject: ino64, java and intellij products problem Message-ID: Date: Wed, 31 May 2017 23:53:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 20:53:39 -0000 Hi All, Seems that after ino64 transition some java programs stopped to fully function. I.e. java/intellij (IntellJ IDEA and Co) starts but does not show any files. I'm not sure if it's a java or IntelliJ problem. Any help to diagnose the culprit is welcome. Thanks. -- WBR, bsam From owner-freebsd-current@freebsd.org Wed May 31 21:27:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AD28B94EA6; Wed, 31 May 2017 21:27:33 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE2116A3F8; Wed, 31 May 2017 21:27:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::3531:dd34:c822:60f2] (unknown [IPv6:2001:470:7a58:0:3531:dd34:c822:60f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 37C2219190; Wed, 31 May 2017 23:27:24 +0200 (CEST) From: Dimitry Andric Content-Type: multipart/signed; boundary="Apple-Mail=_66BB4097-05BE-472A-9539-F0463C3653F2"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Firefox (and other Mozilla products) after ino64 Message-Id: <3FD47B4D-1C1E-485E-A305-9C4EF3FB5F74@FreeBSD.org> Date: Wed, 31 May 2017 23:27:16 +0200 Cc: FreeBSD Ports To: FreeBSD Current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 21:27:33 -0000 --Apple-Mail=_66BB4097-05BE-472A-9539-F0463C3653F2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Due to the recent ino64 update in 12.0-CURRENT, there have been some reports by Firefox port users about crashes. While I personally have not experienced these crashes, as I immediately rebuilt all my ports from scratch after the ino64 update, I think can explain why the following combination is very likely to have problems: * kernel+world after ino64 * www/firefox package from before ino64 It is because Firefox's JavaScript engine is doing tricks to get at libc structures and functions (via an FFI mechanism), and several structure layouts and offsets are hardcoded into its engine at build time. For instance, here is the place where the engine determines the offset of struct dirent's d_name field: = https://hg.mozilla.org/mozilla-central/file/tip/dom/system/OSFileConstants= .cpp#l648 Further down in the file, several offsets of fields in struct stats are similarly determined: = https://hg.mozilla.org/mozilla-central/file/tip/dom/system/OSFileConstants= .cpp#l677 Now, since ino64 changed quite a number of structure layouts, including struct dirent, struct stat, and others, such offsets determined in the past will no longer be valid! It is pretty likely that Firefox will attempt to access these fields, finding bogus values, or simply reading invalid memory, and crashing because of this. Or at the least, the behavior will be unstable. This also applies to other Mozilla products, such as Thunderbird, SeaMonkey, and so on. These should all be rebuilt from scratch under ino64. -Dimitry --Apple-Mail=_66BB4097-05BE-472A-9539-F0463C3653F2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlkvNTsACgkQsF6jCi4glqNvpwCg5eerGXuJHurTOjxZgOiFSyZt OwYAoIZgIrTUAG2vLbkDXU7w3Kuy5pIm =CvWl -----END PGP SIGNATURE----- --Apple-Mail=_66BB4097-05BE-472A-9539-F0463C3653F2-- From owner-freebsd-current@freebsd.org Wed May 31 21:29:35 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49687B94FE3 for ; Wed, 31 May 2017 21:29:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D33DC6A611 for ; Wed, 31 May 2017 21:29:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v4VLTPtO032352 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 1 Jun 2017 00:29:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v4VLTPtO032352 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v4VLTOvQ032351; Thu, 1 Jun 2017 00:29:24 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 1 Jun 2017 00:29:24 +0300 From: Konstantin Belousov To: Boris Samorodov Cc: freebsd-current@FreeBSD.org Subject: Re: ino64, java and intellij products problem Message-ID: <20170531212924.GV82323@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 21:29:35 -0000 On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: > Hi All, > > Seems that after ino64 transition some java programs stopped > to fully function. I.e. java/intellij (IntellJ IDEA and Co) > starts but does not show any files. > > I'm not sure if it's a java or IntelliJ problem. Any help to > diagnose the culprit is welcome. Is it after full rebuild of all ports for post-ino64, or with all ports built on pre-ino64 ? (Mixes are not supported and not supposed to work). Check java programs for JNI calls which return struct stat or struct dirent to java code, and java code which knows the layout. It is, e.g., the problem with Firefox and its javascript, but there the recompilation seems to work. From owner-freebsd-current@freebsd.org Wed May 31 22:59:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DA43BD35E3 for ; Wed, 31 May 2017 22:59:04 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D86EC6FFE5 for ; Wed, 31 May 2017 22:59:03 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-vk0-x22a.google.com with SMTP id x71so16407612vkd.0 for ; Wed, 31 May 2017 15:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Dr28KUEQK64aKKfzLS6MzGiUqLqJCtLrBkSZSFc188w=; b=jqJxpB+Sxs98xbN0m/BvVX4BsS+SDBC/0WzU7M1169YMCeuKSGXHsHA8EOX3obhCvA 3TMYUvl+05LV5uqSxQF7b6Yy8Q2Ry6Cb/KZFJHqOZZtf41+6qqRbxvR5gEUxncFjxiJt XmSzYIuTjzlmFJ88J2Pn4xTFf1X8AXTnTzV2CMLt8GMwyw4Z6q+nasdiGtOb6xWMoOY9 UEX5FCk2/QvqTpqlZJXKZEYW1muQUUOLiOB2hB19PJ1BAs1o3R6Nv5EZ3nhFyqyHM+aj U3X1sWiCuO5UJyjgYTgcg9zpf/cJBmnPZjiD8G0jAfcG+bwETlc4Iejt+IowcIBTB4yi Vh3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Dr28KUEQK64aKKfzLS6MzGiUqLqJCtLrBkSZSFc188w=; b=S/atSnh8TocM8fnET6tQV5RLMvQnY8vK/lmfEceSfw0aUYOy9Cdur2MVWNUThwzvjY I4YrIHsaDqWzc9wNsx3nHQa7liRTAuFE1MKXXylPN7rfguG4dT4knsZVyH0HjSWnl62K +Tk9d+6mH/bDay3H+BHzcqNUyxhXJLh/+SvYvtkcFo/NSPal4o7y2wOQ+j3/9l7zlLfB 3svHoFk9735cdcqPxoygyBsUq1W4IYi5xszBk+rvmMOMt6iPSaL5l4t3cO/nH8wt3gQy TMmLPNG+oUFQBfvwuwG/FTtxck7Z5k3J7jZVVk7d3cX6+JdaQgYJrRYuW7ccB0tsbVU8 KZDA== X-Gm-Message-State: AODbwcDjtF+Qd9P0fBYQ/inSA3WtNjbg6Byds6GppwjphRTeW48ojzfE 0IMYuelS2B2ILN3q7TdoEEWb8ugzkQ== X-Received: by 10.31.168.137 with SMTP id r131mr11126085vke.64.1496271542992; Wed, 31 May 2017 15:59:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.166.22 with HTTP; Wed, 31 May 2017 15:59:02 -0700 (PDT) Received: by 10.31.166.22 with HTTP; Wed, 31 May 2017 15:59:02 -0700 (PDT) In-Reply-To: <20170531212924.GV82323@kib.kiev.ua> References: <20170531212924.GV82323@kib.kiev.ua> From: Michael Zhilin Date: Thu, 1 Jun 2017 01:59:02 +0300 Message-ID: Subject: Re: ino64, java and intellij products problem To: Konstantin Belousov , bsam@passap.ru Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 31 May 2017 22:59:04 -0000 Hi, It may by worth to check other java monsters, but I see no problem with Eclipse and SQL Developer with ino64. Thanks! 1 =D0=B8=D1=8E=D0=BD. 2017 =D0=B3. 6:29 =D0=94=D0=9F =D0=BF=D0=BE=D0=BB=D1= =8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Konstantin Belousov" < kostikbel@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: > > Hi All, > > > > Seems that after ino64 transition some java programs stopped > > to fully function. I.e. java/intellij (IntellJ IDEA and Co) > > starts but does not show any files. > > > > I'm not sure if it's a java or IntelliJ problem. Any help to > > diagnose the culprit is welcome. > > Is it after full rebuild of all ports for post-ino64, or with all ports > built on pre-ino64 ? (Mixes are not supported and not supposed to work). > > Check java programs for JNI calls which return struct stat or struct > dirent to java code, and java code which knows the layout. It is, e.g., > the problem with Firefox and its javascript, but there the recompilation > seems to work. > _______________________________________________ > 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 Jun 1 00:01:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 358FDBED5B5; Thu, 1 Jun 2017 00:01:02 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBDE5719CD; Thu, 1 Jun 2017 00:01:01 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dGDXo-0001KA-Uj; Thu, 01 Jun 2017 02:00:53 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1dGDXo-00016s-Tf; Thu, 01 Jun 2017 02:00:52 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Thu, 01 Jun 2017 00:00:52 GMT From: "Jeffrey Bouquet" To: "Dimitry Andric" CC: "FreeBSD Current" , "FreeBSD Ports" Subject: Re: Firefox (and other Mozilla products) after ino64 Date: Wed, 31 May 2017 17:00:52 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: <3FD47B4D-1C1E-485E-A305-9C4EF3FB5F74@FreeBSD.org> Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 00:01:02 -0000 On Wed, 31 May 2017 23:27:16 +0200, Dimitry Andric wrote: > Hi, >=20 > Due to the recent ino64 update in 12.0-CURRENT, there have been some > reports by Firefox port users about crashes. While I personally have > not experienced these crashes, as I immediately rebuilt all my ports > from scratch after the ino64 update, I think can explain why the > following combination is very likely to have problems: >=20 > * kernel+world after ino64 > * www/firefox package from before ino64 >=20 > It is because Firefox's JavaScript engine is doing tricks to get at libc > structures and functions (via an FFI mechanism), and several structure > layouts and offsets are hardcoded into its engine at build time. >=20 > For instance, here is the place where the engine determines the offset > of struct dirent's d_name field: >=20 > https://hg.mozilla.org/mozilla-central/file/tip/dom/system/OSFileConsta= nts.cpp#l648 >=20 > Further down in the file, several offsets of fields in struct stats are > similarly determined: >=20 > https://hg.mozilla.org/mozilla-central/file/tip/dom/system/OSFileConsta= nts.cpp#l677 >=20 > Now, since ino64 changed quite a number of structure layouts, including > struct dirent, struct stat, and others, such offsets determined in the > past will no longer be valid! >=20 > It is pretty likely that Firefox will attempt to access these fields, > finding bogus values, or simply reading invalid memory, and crashing > because of this. Or at the least, the behavior will be unstable. >=20 > This also applies to other Mozilla products, such as Thunderbird, > SeaMonkey, and so on. These should all be rebuilt from scratch under > ino64. >=20 > -Dimitry What of machines where for some reason ports do not always build? [ for ins= tance,=20 ones with past workarounds for a failed installworld... ] that still are in critical use daily? And,or whe= re the system has been installed for so long without reinstall that some ports=20 segfault unless 'pkg lock' ... and not usually upgraded... and/or thus usi= ng binaries from backup...=20 Are upstream repositories to have those [ browser, email] ports? For in= stance, here iridium I cannot get to build...=20= From owner-freebsd-current@freebsd.org Thu Jun 1 08:20:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FAAABF0E5D; Thu, 1 Jun 2017 08:20:44 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EDFA06E4A1; Thu, 1 Jun 2017 08:20:43 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id E9C7A42182; Thu, 1 Jun 2017 10:20:40 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FS-2k73M_fic; Thu, 1 Jun 2017 10:20:40 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 5A6CA42180; Thu, 1 Jun 2017 10:20:40 +0200 (CEST) Subject: Re: Xorg error 'alphasort' To: Masachika ISHIZUKA , freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org References: <1116168837.2488786.1496080764980.ref@mail.yahoo.com> <1116168837.2488786.1496080764980@mail.yahoo.com> <20170601.012146.413650928099698078.ish@amail.plala.or.jp> From: Willem Jan Withagen Message-ID: <42c6421e-1b5d-1cc0-5d38-081b037a202e@digiware.nl> Date: Thu, 1 Jun 2017 10:20:41 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170601.012146.413650928099698078.ish@amail.plala.or.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 08:20:44 -0000 On 31/05/2017 18:21, Masachika ISHIZUKA wrote: > Hi. > > I was using 12-current r318249 and did 'pkg upgrade', and > could not start xorg with alphasort error. > After updating r319315, xorg works again. Right I had more or less the same with r319216. And I was going to reinstall from a snapshot, but now I'll try and move forward. --WjW From owner-freebsd-current@freebsd.org Thu Jun 1 09:16:35 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20209BF5892 for ; Thu, 1 Jun 2017 09:16:35 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward4j.cmail.yandex.net (forward4j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95CDD70B83 for ; Thu, 1 Jun 2017 09:16:34 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [95.108.130.59]) by forward4j.cmail.yandex.net (Yandex) with ESMTP id 9DC7120EFC; Thu, 1 Jun 2017 12:16:21 +0300 (MSK) Received: from smtp1j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1j.mail.yandex.net (Yandex) with ESMTP id 93DBB3C818F2; Thu, 1 Jun 2017 12:14:54 +0300 (MSK) Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id vti3QCgWrd-EsvOSnR7; Thu, 01 Jun 2017 12:14:54 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1496308494; bh=Z/2x11yj6DRTvPRtquSYGHyyGmYkzpKKRAu6AAt2vqY=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=ePhMgnvASfBqdL/agzLoaUFTZs7Y46Wa1LQAgwHSIXIkRM/E8gK7a2/yhAm+HUigy oXFrnaGoqBV5AyaEUqh0BVK194/gWcd64M3kdOIooLHZJb33EKGtV8KFdMqxQbEWjf VpFTb4DxpZ9tDHaD9hUgOLjosybP+GVxPEC4vKLQ= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: ino64, java and intellij products problem To: Konstantin Belousov Cc: freebsd-current@FreeBSD.org References: <20170531212924.GV82323@kib.kiev.ua> From: Boris Samorodov Message-ID: Date: Thu, 1 Jun 2017 12:13:55 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170531212924.GV82323@kib.kiev.ua> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 09:16:35 -0000 01.06.2017 00:29, Konstantin Belousov пишет: > On Wed, May 31, 2017 at 11:53:39PM +0300, Boris Samorodov wrote: >> Hi All, >> >> Seems that after ino64 transition some java programs stopped >> to fully function. I.e. java/intellij (IntellJ IDEA and Co) >> starts but does not show any files. >> >> I'm not sure if it's a java or IntelliJ problem. Any help to >> diagnose the culprit is welcome. > > Is it after full rebuild of all ports for post-ino64, or with all ports > built on pre-ino64 ? (Mixes are not supported and not supposed to work). Hm. I've rebuild all required ports: --- % pkg info -d intellij-2017.1.3 intellij-2017.1.3: python27-2.7.13_3 openjdk8-8.131.11 intellij-pty4j-0.5_1 intellij-fsnotifier-20160221_2 --- But sure not *all* ports. > Check java programs for JNI calls which return struct stat or struct > dirent to java code, and java code which knows the layout. It is, e.g., > the problem with Firefox and its javascript, but there the recompilation > seems to work. OK, thanks. I'll wait for FreeBSD cluster[*] to build post-ino64 packages, reinstall all of them and see what's next. [*] Seems to occur RSN. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@freebsd.org Thu Jun 1 16:14:30 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C9DAB7999F; Thu, 1 Jun 2017 16:14:30 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A3BD380F6C; Thu, 1 Jun 2017 16:14:29 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id g15so12516331wmc.2; Thu, 01 Jun 2017 09:14:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=PBDPnwqPqscEB3B6tjvfwQYRTKSYluqGfz2FAnTvbug=; b=BgH0AqvrYHoGWGvJLoViw2tPfED9gW4uEd5UwC6vVnIlFx1LRECQEpJdFaCtNJyAfS mrDURSWrfghZ1uOe+A8H6djb1N40O6+nWGkStc6pH5Vo70g331874ziKzl3NNnwf/L0Y zWo1Uww0Hfk+nqNcm3vtubrlUIgMQxqzlRExN//XBlii0aCX15oH9O64Yu/35vztUYNQ 1rNZAYxn6Qlp+LFS355cZ1z7vfLaYsiJLqp2DL4H4EGjr+bwT2yz4wv6pQqq1ZXGQzgf X1Vq5owP7G5LsuGjY4Plct7dAzYbsPWaRMaQcUD61XW1ZUoyWymLVHuOCMLEt4PVP9Su cQJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=PBDPnwqPqscEB3B6tjvfwQYRTKSYluqGfz2FAnTvbug=; b=Qntx95M4eIhGG5xxeO8xPqIjIcmymCuWfPGagtpFh2JuYR31plsDkLgbI2efW256qY DiDz6kvO6HxI1SFzxiQnzCiyJYCIkKybUXY7SECzaWkbTJIYDKiqjDvHCCVBlmJaHiFy iNV1TqZNQr+PBpRp0j0hCBj8HWgx1o6CxTZ92HQdg+ayBb+NRThTMS87oFXFBxYQ9M3D EuZHovnBHki+oGOsD2V0SCWOj3SmZRsABeCoTDujtS8Ll3sAwr6zWtDaAfioZTqPj/yC wBTZeCY5jgsalcj2QdMZwaBuNlhiAz5cuIpPQRIPwGKPl/RoeaKwzDuo2BCPY0cd9O+D 3rGw== X-Gm-Message-State: AODbwcCpwWkhy01JO0vNBrMhttGJRpsejbS0/gIuvJIEXCzTRvEvgf7N IFtOESjZTYxxCUru X-Received: by 10.28.141.136 with SMTP id p130mr2119015wmd.59.1496333667938; Thu, 01 Jun 2017 09:14:27 -0700 (PDT) Received: from ernst.home (p4FCA6D87.dip0.t-ipconnect.de. [79.202.109.135]) by smtp.gmail.com with ESMTPSA id u198sm36183811wmd.29.2017.06.01.09.14.26 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 01 Jun 2017 09:14:27 -0700 (PDT) Date: Thu, 1 Jun 2017 18:14:26 +0200 From: Gary Jennejohn To: Dimitry Andric Cc: FreeBSD Current , FreeBSD Ports Subject: Re: Firefox (and other Mozilla products) after ino64 Message-ID: <20170601181426.63025614@ernst.home> In-Reply-To: <3FD47B4D-1C1E-485E-A305-9C4EF3FB5F74@FreeBSD.org> References: <3FD47B4D-1C1E-485E-A305-9C4EF3FB5F74@FreeBSD.org> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 16:14:30 -0000 On Wed, 31 May 2017 23:27:16 +0200 Dimitry Andric wrote: [snip] > This also applies to other Mozilla products, such as Thunderbird, > SeaMonkey, and so on. These should all be rebuilt from scratch under > ino64. > FYI Seamonkey still works after updating kernel and world to ino64. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Jun 1 18:35:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34318B7C02E; Thu, 1 Jun 2017 18:35:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08558C09; Thu, 1 Jun 2017 18:35:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-pf0-x22a.google.com with SMTP id n23so34469269pfb.2; Thu, 01 Jun 2017 11:35:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=vETjLH0C+ifmD0gKVN9ub8sILJWWiWZnUJ9OOc5H+TA=; b=GDdp+6YJGagHvQDUsk6QTk94Fbk4mWbzMOK6DrpcFvahbwHY3wj0YiI6k8U3GuD4sm D0vTG1f+XvfwNlxmpP6l+o9w70MDM74EFAzULHbjZAtm6rHosX2TYdxVuPIjNbm4ExsT W01jCwWXeXE6IYtqCVrtPQYj1QOdfIu3IKkXJAKdRmHO5MwTPJGpGUlTjoWc7FQ+Gb2K KsZBHoF/4eXOdAAktDjKQTtJUSBr/WSSI2Ymg3zUlTE605sn5Sr7RhZjC/x7IjNjYmG8 lt2dpiFMq4qKwlvZYjIvRGRY/imBNAl2pmT4uK+LMu+uKlDXbW/l8lioq4RkZbsmtsyZ oRqg== 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=vETjLH0C+ifmD0gKVN9ub8sILJWWiWZnUJ9OOc5H+TA=; b=rmqGFjUuM7A9hVevhAHZ0/RXkXxEY1QnP5A+jveaP+3ar+eIXyY9NwNt1Gw+2PBgQ0 //y2Itk5uh2vw27U7vQR6jhh9vHhZkocKCtj9oMyI+3ZRTxvraCsUYW6sSUbsLzN+Ywy Iy1MyeIJqK+d4LgqjzwbdjuopOx8h90+qPFVOiSbK8LFY3wjN/9yK4oJaJMcoMwbJiNH MFKnx8lZ/kQTOURXK1d1OzUDgHOV7EVfmzS4bHzzySLDQzr4c+eGN0u9R+XOLDLOLg7V zbGCqCvEthZDU5XARpAnCzoc7dL8ejqngTJUSjtpwPrRuIr3ki94uYOTO/bu72doxFRY ksXQ== X-Gm-Message-State: AODbwcCG62kurN+CMYA6GAoOMpxwqqZIMigumMFJNVz5Dx/WqFtwyeO2 JOLaJjihi9DD7JZVpv3APmtEQXeODll4 X-Received: by 10.84.224.198 with SMTP id k6mr8729460pln.148.1496342132155; Thu, 01 Jun 2017 11:35:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.168.79 with HTTP; Thu, 1 Jun 2017 11:35:31 -0700 (PDT) From: blubee blubeeme Date: Fri, 2 Jun 2017 02:35:31 +0800 Message-ID: Subject: nvidia drivers mutex lock To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 18:35:33 -0000 I'm running nvidia-drivers 375.66 with a GTX 1070 on FreeBSD-Current This problem just started happening recently but, every so often my laptop screen will just blank out and then I have to power cycle to get the machine up and running again. It seems to be a problem with nvidia drivers acquiring duplicate lock. Any info on this? Jun 2 02:29:41 blubee kernel: acquiring duplicate lock of same type: "os.lock_mtx" Jun 2 02:29:41 blubee kernel: 1st os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: 2nd os.lock_mtx @ nvidia_os.c:841 Jun 2 02:29:41 blubee kernel: stack backtrace: Jun 2 02:29:41 blubee kernel: #0 0xffffffff80ab7770 at witness_debugger+0x70 Jun 2 02:29:41 blubee kernel: #1 0xffffffff80ab7663 at witness_checkorder+0xe23 Jun 2 02:29:41 blubee kernel: #2 0xffffffff80a35b93 at __mtx_lock_flags+0x93 Jun 2 02:29:41 blubee kernel: #3 0xffffffff82f4397b at os_acquire_spinlock+0x1b Jun 2 02:29:41 blubee kernel: #4 0xffffffff82c48b15 at _nv012002rm+0x185 Jun 2 02:29:41 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170303/nsarguments-205) Jun 2 02:29:42 blubee kernel: nvidia-modeset: Allocated GPU:0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI:0000:01:00.0 Best, Owen From owner-freebsd-current@freebsd.org Thu Jun 1 23:00:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 978A0B82A42 for ; Thu, 1 Jun 2017 23:00:04 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from sonic313-38.consmr.mail.ne1.yahoo.com (sonic313-38.consmr.mail.ne1.yahoo.com [66.163.185.61]) by mx1.freebsd.org (Postfix) with ESMTP id 6EAF7702D5 for ; Thu, 1 Jun 2017 23:00:03 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1496358002; bh=43VasqQNAraTtr+r+m94srDQs0+QnJmDQuDf6Rp1SGk=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=kS6C2gJVnan7fJ9Mz/qN02Dx3Gi1TuxX7qAKxTpjDoiB2RoiCeoO9d2rfLZll29b6LJ+SjE+S8ySPFLHDuJmqTIEHWTDl+Gxe71Tj99QxX3vXbEY3WO3aN+HrdJd5MjuF3ZDezWUzpmKNQnFNbdT8noAMNlxfH+SRap8M12K0+iMbhbAljhR8IyJnT5Ji1fOLeVZZIqfJua3q9b1haQnjSiLhdc2ALnHbPGyYzA+ZXgG0bnvQGfytRfJiUjdFs10J9uDqH6ytGvccGl/k+t07DNCMdWRIOyO6Y/jLv+j1Fj6GSwFdrp5G+MDbLcj5SKui2ZVYtdPSRTQRFjwlLQEsw== X-YMail-OSG: m96gPfkVM1nz6Vz0mUe7hrn_Sv8ZAN0ZfYZkEdTuaQNjXjesPyTXm6U9mbhvQ63 GDjEzxI6E7Mk2L5zzJ8hkgSmELbI2kmnksVqpvMnkVIGr0gTKGgLSXnkD0m7.kIwlUSHNhLY2Ajn BEagjnEKAXWfiDYxLu1ACA2AGl0eOAOIOJltKCrghbU2qtkCLCAOl0r8oOzWS3D.MsFZBjZs5QYY N5_CWg7PiibyTqmU32IXN.koEKc81_3pc4f7Vaq5TVtoA32yJBQKQpOuTMArB.YXWkcbffIEC7Mb UGE2oQng5yh8KHg5vk98IWrX7KC8EUkWvY_p6CFeZjFTElFDZweHwsMxeuFkdwrVBbcHapiIf8uV PqFyfvcaOWgg3_LfwzjasFclwp3Z0.OgtquAl3Uwr6WMqu1hwHlT73TnhxKfq76_nc4ZNVLKhhE6 dIStlxvdb1zgqffqZoE9UzrTKapKgvSE6rrkodDTdIv8VIjP45uA60ZQgormI_BQIoXzufVbhmP0 9d2viRiezVQrwEGYvJRxvND6QqmwSSBzgbgD.0MMwu116WEmZoNhDONrtnJlWBSI- Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.ne1.yahoo.com with HTTP; Thu, 1 Jun 2017 23:00:02 +0000 Date: Thu, 1 Jun 2017 22:35:46 +0000 (UTC) From: Jeffrey Bouquet Reply-To: Jeffrey Bouquet To: , , blubee blubeeme Message-ID: <1452547285.767963.1496356546815@mail.yahoo.com> Subject: Re: nvidia drivers mutex lock MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <1452547285.767963.1496356546815.ref@mail.yahoo.com> X-Mailer: WebService/1.1.9726 YahooMailBasic Mozilla/5.0 (X11; FreeBSD i386; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Lightning/5.1 X-Mailman-Approved-At: Thu, 01 Jun 2017 23:04:19 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 01 Jun 2017 23:00:04 -0000 I see the same message, upon load, ... -------------------------------------------- On Thu, 6/1/17, blubee blubeeme wrote: Subject: nvidia drivers mutex lock To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org Date: Thursday, June 1, 2017, 11:35 AM =20 I'm running nvidia-drivers 375.66 with a GTX 1070 on FreeBSD-Current =20 This problem just started happening recently but, every so often my laptop screen will just blank out and then I have to power cycle to get the machine up and running again. =20 It seems to be a problem with nvidia drivers acquiring duplicate lock. Any info on this? =20 Jun=C2=A0 2 02:29:41 blubee kernel: acquiring duplicate lock of same type: "os.lock_mtx" Jun=C2=A0 2 02:29:41 blubee kernel: 1st os.lock_mtx @ nvidia_os.c:841 Jun=C2=A0 2 02:29:41 blubee kernel: 2nd os.lock_mtx @ nvidia_os.c:841 Jun=C2=A0 2 02:29:41 blubee kernel: stack backtrace: Jun=C2=A0 2 02:29:41 blubee kernel: #0 0xffffffff80ab7770 at witness_debugger+0x70 Jun=C2=A0 2 02:29:41 blubee kernel: #1 0xffffffff80ab7663 at witness_checkorder+0xe23 Jun=C2=A0 2 02:29:41 blubee kernel: #2 0xffffffff80a35b93 at __mtx_lock_flags+0x93 Jun=C2=A0 2 02:29:41 blubee kernel: #3 0xffffffff82f4397b at os_acquire_spinlock+0x1b Jun=C2=A0 2 02:29:41 blubee kernel: #4 0xffffffff82c48b15 at _nv012002rm+0x185 Jun=C2=A0 2 02:29:41 blubee kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170303/nsarguments-205) Jun=C2=A0 2 02:29:42 blubee kernel: nvidia-modeset: Allocated GPU:0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ PCI:0000:01:00.0 =20 Best, Owen _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" =20 ... then Xorg will run happily twelve hours or so. The lockups here happen= usually when too large or too many of number of tabs/ large web pages with complex = CSS etc are opened at a time. =20 So no help, just a 'me too'. =20 From owner-freebsd-current@freebsd.org Fri Jun 2 06:47:27 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD7E9BF129D for ; Fri, 2 Jun 2017 06:47:27 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from mail.made4.biz (mail.made4.biz [195.154.164.132]) (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 6EEBC7D240 for ; Fri, 2 Jun 2017 06:47:27 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=freebsd.org ; s=20170531; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=wT6bn8N8XdoPt/qeXECXnEzFJFCbDQZxRTBCSytbmlE=; b=elW/hCOE0Vf5nkta4J+Zr5n9YI crK8cMuzi6xLqjpK4Pyot3mXS2S3HzxbzUuCB/3Zmm97BbXR5aGJH/VV5VNkDESnJXqbGRwthPmh6 l+1LNhPRCEw1ggDPj8EePtIB9lMVLrN1MEqIXVH88bhrZkjH1+pL88/MsKlnunlduFg4=; Received: from 141.7.19.93.rev.sfr.net ([93.19.7.141] helo=rosetta.dumbbell.fr) by mail.made4.biz with esmtpa (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dGgCq-000Ohh-2Q for freebsd-current@freebsd.org; Fri, 02 Jun 2017 08:37:08 +0200 Subject: Re: firefox/ rust failed to install on FreeBSD 12-CURRENT To: freebsd-current@freebsd.org References: From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= Organization: The FreeBSD Project Message-ID: Date: Fri, 2 Jun 2017 08:37:03 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="duVVjbgxRL6l3OSJg3Ux0IihgjIO7a3pn" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 06:47:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --duVVjbgxRL6l3OSJg3Ux0IihgjIO7a3pn Content-Type: multipart/mixed; boundary="oaJDvQOkeBKFkjRQm9eWbijALfnPQNpjT"; protected-headers="v1" From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= To: freebsd-current@freebsd.org Message-ID: Subject: Re: firefox/ rust failed to install on FreeBSD 12-CURRENT References: In-Reply-To: --oaJDvQOkeBKFkjRQm9eWbijALfnPQNpjT Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 28.05.2017 19:21, blubee blubeeme wrote: > =3D=3D=3D> Building for rust-1.17.0 > ... > extracting > rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/= lib/rustlib/x86_64-unknown-freebsd/lib/GNUSparseFile.0/librustc_llvm-74a1= be1110b5d4d0.so > gmake[7]: Leaving directory '/usr/ports/lang/rust/work/rustc-1.17.0-src= ' > *** Error code 1 Hi! This failure is caused by Python 2's tarfile module not supporting sparse files in archives. Python 3 supports them but the configure script insists on using Python 2. Before a proper fix is committed, you can change the following line in lang/rust/Makefile: https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L= 159 to say (this is a single line): gtar -c -C ${WRKSRC} -f - rust-std-1.16.0-${RUST_ARCH_${ARCH}}-unknown-freebsd | gzip > ${WRKSRC}/rustc.tbz Then, change the following line: https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L= 34 to say: BUILD_DEPENDS=3D cmake:devel/cmake \ gtar:archivers/gtar This will use GNU tar instead of BSD tar to recreate the bootstrap and GNU tar doesn't seem to produce sparse file entries in the archive. --=20 Jean-S=C3=A9bastien P=C3=A9dron --oaJDvQOkeBKFkjRQm9eWbijALfnPQNpjT-- --duVVjbgxRL6l3OSJg3Ux0IihgjIO7a3pn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEZwh/0a6uDhLbxqbwOemXYaX9lMwFAlkxB5NfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY3 MDg3RkQxQUVBRTBFMTJEQkM2QTZGMDM5RTk5NzYxQTVGRDk0Q0MACgkQOemXYaX9 lMzrvBAAtlxDIQm+OQrK7ETq+3dj2up/yhlFwDk4yh4PBPf6jO7qABmbNEUIDW6F igF7NkqHh7VxnEd4ZPYhs/1iiHrY8n6Izc1814SEJ6rygipLwOMBM7sNtMApgrJx HKBn27Vc36dVqGQlZa1ONX9mzgOjOjbwns0LS07i4T9OfhVHjIQwxIygTbzelE4G wvqAHo8KO2yKD08/rvxgdvqWKJEEdJkUhZ5+cmkpYAnerXMprJxYXdc+SrTtyhCl V0eVi6JnMkupsmqgOz04cb2Lq/Nc38GsibfR2e+hBsw2DbnpBhaimZSco+mmR0ir tnYNcll6koM1rq8T2mBIGQP4xKbm5qKTbwF/vhiJp9RVmGhzByl2yXK7heeO0Jm7 ezI9XQBhfXgmYluqsP3NgPLBN8WUHlwZzqeF/pXmSnGt4zpIgC7Rsy9hkLNALNVH YvMUXmIX+ljbUskPCEBxtYkEK9VsA0cicyYcy5qm+a+k5Hss6DRZXm+rvM0g/pkg 8ua0gSrDoFLtrzUueKS4GL+3uOnpQtj+dr4qK9klISWYcrrfJVVB5WRrCTkD3vOt k8eNQp6l8Xukw/8jKlnoDRKU806Psz0QJL4QTUmZ9K8jrhZk7t8HgnKChjYrkv6u XEmXI/CsEyKkRtEtpZdVh9Drt8yVFNxzPXslVWkO2xCysgfcark= =tExO -----END PGP SIGNATURE----- --duVVjbgxRL6l3OSJg3Ux0IihgjIO7a3pn-- From owner-freebsd-current@freebsd.org Fri Jun 2 07:45:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B49B6BF1F8A for ; Fri, 2 Jun 2017 07:45:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8647E880 for ; Fri, 2 Jun 2017 07:45:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 989CCBF1F89; Fri, 2 Jun 2017 07:45:22 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98210BF1F88 for ; Fri, 2 Jun 2017 07:45:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2FE847E87F; Fri, 2 Jun 2017 07:45:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v527jG8d087215 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 2 Jun 2017 10:45:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v527jG8d087215 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v527jGBs087214; Fri, 2 Jun 2017 10:45:16 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 2 Jun 2017 10:45:16 +0300 From: Konstantin Belousov To: current@freebsd.org Cc: bapt@freebsd.org Subject: kqueue(2) changes Message-ID: <20170602074516.GE82323@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.2 (2017-04-18) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jun 2017 07:45:22 -0000 I implemented an option to specify absolute time for kqueue(2) timers, and did required type changes to support larger values in struct kevent. Please see https://reviews.freebsd.org/D11025 for the patch, including man page update, and for some more detailed explanation. Please review. From owner-freebsd-current@freebsd.org Sat Jun 3 06:43:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02005B94DF0 for ; Sat, 3 Jun 2017 06:43:26 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (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 D0EB72035; Sat, 3 Jun 2017 06:43:25 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id v536QTda003125; Sat, 3 Jun 2017 06:26:29 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.101] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id bwjkn4xkjjjvxtvx7ygw3zvw6e; Sat, 03 Jun 2017 06:26:29 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: firefox/ rust failed to install on FreeBSD 12-CURRENT From: Tim Kientzle In-Reply-To: Date: Fri, 2 Jun 2017 23:26:29 -0700 Cc: FreeBSD current Content-Transfer-Encoding: quoted-printable Message-Id: <3348A21B-754F-41FE-A94D-C3F53AD691C8@kientzle.com> References: To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 06:43:26 -0000 > On Jun 1, 2017, at 11:37 PM, Jean-S=C3=A9bastien P=C3=A9dron = wrote: >=20 > On 28.05.2017 19:21, blubee blubeeme wrote: >> =3D=3D=3D> Building for rust-1.17.0 >> ... >> extracting >> = rust-std-1.16.0-x86_64-unknown-freebsd/rust-std-x86_64-unknown-freebsd/lib= /rustlib/x86_64-unknown-freebsd/lib/GNUSparseFile.0/librustc_llvm-74a1be11= 10b5d4d0.so >> gmake[7]: Leaving directory = '/usr/ports/lang/rust/work/rustc-1.17.0-src' >> *** Error code 1 >=20 > Hi! >=20 > This failure is caused by Python 2's tarfile module not supporting > sparse files in archives. Python 3 supports them but the configure > script insists on using Python 2. >=20 > Before a proper fix is committed, you can change the following line in > lang/rust/Makefile: > = https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L1= 59 >=20 > to say (this is a single line): > gtar -c -C ${WRKSRC} -f - > rust-std-1.16.0-${RUST_ARCH_${ARCH}}-unknown-freebsd | gzip > > ${WRKSRC}/rustc.tbz You could add --format=3Dustar to the existing command line; that would = force bsdtar to use the older "ustar" format (without any extensions = that might confuse Python's tar file module). > Then, change the following line: > = https://github.com/freebsd/freebsd-ports/blob/master/lang/rust/Makefile#L3= 4 >=20 > to say: > BUILD_DEPENDS=3D cmake:devel/cmake \ > gtar:archivers/gtar >=20 > This will use GNU tar instead of BSD tar to recreate the bootstrap and > GNU tar doesn't seem to produce sparse file entries in the archive. How ironic; using GNU tar in order to avoid having GNU sparse file = entries. ;-) Tim From owner-freebsd-current@freebsd.org Sat Jun 3 07:11:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D43EAB9532C for ; Sat, 3 Jun 2017 07:11:53 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 98C5D2A37 for ; Sat, 3 Jun 2017 07:11:53 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-21-125.dz.commufa.jp [124.18.21.125]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id v536Pk6r009850; Sat, 3 Jun 2017 15:25:46 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 3 Jun 2017 15:25:46 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: Jeffrey Bouquet , blubee blubeeme Subject: Re: nvidia drivers mutex lock Message-Id: <20170603152546.3a9f09b747b2ce24c03be404@dec.sakura.ne.jp> In-Reply-To: <1452547285.767963.1496356546815@mail.yahoo.com> References: <1452547285.767963.1496356546815.ref@mail.yahoo.com> <1452547285.767963.1496356546815@mail.yahoo.com> Organization: Junchoon corps X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 07:11:53 -0000 Hi. Version 381.22 (5 days newer than 375.66) of the driver states... [1] Fixed hangs and crashes that could occur when an OpenGL context is created while the system is out of available memory. Can this be related with your hang? IMHO, possibly allocating new resource (using os.lock_mtx guard) without checking the lock first while previous request is waiting for another can cause the duplicated lock situation. And high memory pressure would easily cause the situation. [1] http://www.nvidia.com/Download/driverResults.aspx/118527/en-us Hope it helps. On Thu, 1 Jun 2017 22:35:46 +0000 (UTC) Jeffrey Bouquet wrote: > I see the same message, upon load, ... > -------------------------------------------- > On Thu, 6/1/17, blubee blubeeme wrote: > > Subject: nvidia drivers mutex lock > To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org > Date: Thursday, June 1, 2017, 11:35 AM > > I'm running nvidia-drivers 375.66 with a GTX > 1070 on FreeBSD-Current > > This problem just started happening > recently but, every so often my laptop > screen will just blank out and then I > have to power cycle to get the > machine up and running again. > > It seems to be a problem with nvidia > drivers acquiring duplicate lock. Any > info on this? > > Jun$B".(B 2 02:29:41 blubee kernel: > acquiring duplicate lock of same type: > "os.lock_mtx" > Jun$B".(B 2 02:29:41 blubee kernel: 1st > os.lock_mtx @ nvidia_os.c:841 > Jun$B".(B 2 02:29:41 blubee kernel: 2nd > os.lock_mtx @ nvidia_os.c:841 > Jun$B".(B 2 02:29:41 blubee kernel: > stack backtrace: > Jun$B".(B 2 02:29:41 blubee kernel: #0 > 0xffffffff80ab7770 at > witness_debugger+0x70 > Jun$B".(B 2 02:29:41 blubee kernel: #1 > 0xffffffff80ab7663 at > witness_checkorder+0xe23 > Jun$B".(B 2 02:29:41 blubee kernel: #2 > 0xffffffff80a35b93 at > __mtx_lock_flags+0x93 > Jun$B".(B 2 02:29:41 blubee kernel: #3 > 0xffffffff82f4397b at > os_acquire_spinlock+0x1b > Jun$B".(B 2 02:29:41 blubee kernel: #4 > 0xffffffff82c48b15 at _nv012002rm+0x185 > Jun$B".(B 2 02:29:41 blubee kernel: > ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: > Argument #4 type mismatch - Found > [Buffer], ACPI requires [Package] > (20170303/nsarguments-205) > Jun$B".(B 2 02:29:42 blubee kernel: > nvidia-modeset: Allocated GPU:0 > (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ > PCI:0000:01:00.0 > > Best, > Owen > _______________________________________________ > freebsd-ports@freebsd.org > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > > ... then Xorg will run happily twelve hours or so. The lockups here happen usually > when too large or too many of number of tabs/ large web pages with complex CSS etc > are opened at a time. > So no help, just a 'me too'. > _______________________________________________ > 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" > > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Sat Jun 3 05:01:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC592B82505 for ; Sat, 3 Jun 2017 05:01:44 +0000 (UTC) (envelope-from 0100015c6c5499e9-e0158287-b6e0-44ae-81ba-d1715fb28927-000000@amazonses.com) Received: from a8-56.smtp-out.amazonses.com (a8-56.smtp-out.amazonses.com [54.240.8.56]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD70A84BE0 for ; Sat, 3 Jun 2017 05:01:44 +0000 (UTC) (envelope-from 0100015c6c5499e9-e0158287-b6e0-44ae-81ba-d1715fb28927-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1496466103; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=X9AR5LiS5pcZ4tmyoYuZHotUsWnCXAbYVo3KgzEGdmw=; b=p1jFa/rVIr+hpqMgOfycmgYH/M0cafO3dRYsIe8oZouOb+dwL6aNsywyNGkyQEDR 4ba4JJY7zb5Wa0mPNtLLWaxH0iw7NkkGpxVJv3ipKqLc452RgCFii4FSmqfrtV+Itfd L0wQ0NRk+LFG/YMNTHOJDWsv10W+iZoOcGL1EuHU= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1496466103; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=X9AR5LiS5pcZ4tmyoYuZHotUsWnCXAbYVo3KgzEGdmw=; b=RYvFQeRZ5uM1iz0Qg/74gqxyJYEVj7IQMCBNNPcqxHDiAQ8fKyTxKiBwYz7WiTuA 4PXKAVIxuXQc5aTCxnsDTyK9XCEMyAvjvOCBts4X2iyb76JuEHCoLEepYP0ba9tWhUM WkadJt5LFMJowCvr7jqwb/EJhuRpia8x4mHEXgrA= Subject: Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) To: Rick Macklem , "freebsd-current@freebsd.org" References: Cc: Andriy Gapon , "cem@freebsd.org" , "jeff@freebsd.org" , Ryan Stone From: Colin Percival Message-ID: <0100015c6c5499e9-e0158287-b6e0-44ae-81ba-d1715fb28927-000000@email.amazonses.com> Date: Sat, 3 Jun 2017 05:01:42 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2017.06.03-54.240.8.56 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-Mailman-Approved-At: Sat, 03 Jun 2017 11:18:48 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 05:01:45 -0000 On 05/28/17 13:16, Rick Macklem wrote: > cperciva@ is running a highly parallelized buuildworld and he sees better > slightly better elapsed times and much lower system CPU for SCHED_ULE. > > As such, I suspect it is the single threaded, processes mostly sleeping waiting > for I/O case that is broken. > I suspect this is how many people use NFS, since a highly parallelized make would > not be a typical NFS client task, I think? Running `make buildworld -j36` on an EC2 "c4.8xlarge" instance (36 vCPUs, 60 GB RAM, 10 GbE) with GENERIC-NODEBUG, ULE has a slight edge over 4BSD: GENERIC-NODEBUG, SCHED_4BSD: 1h14m12.48s real 6h25m44.59s user 1h4m53.42s sys 1h15m25.48s real 6h25m12.20s user 1h4m34.23s sys 1h13m34.02s real 6h25m14.44s user 1h4m09.55s sys 1h13m44.04s real 6h25m08.60s user 1h4m40.21s sys 1h14m59.69s real 6h25m53.13s user 1h4m55.20s sys 1h14m24.00s real 6h24m59.29s user 1h5m37.31s sys GENERIC-NODEBUG, SCHED_ULE: 1h13m00.61s real 6h02m47.59s user 26m45.89s sys 1h12m30.18s real 6h01m39.97s user 26m16.45s sys 1h13m08.43s real 6h01m46.94s user 26m39.20s sys 1h12m18.94s real 6h02m26.80s user 27m39.71s sys 1h13m21.38s real 6h00m46.13s user 27m14.96s sys 1h12m01.80s real 6h02m24.48s user 27m18.37s sys Running `make buildworld -j2` on an E2 "m4.large" instance (2 vCPUs, 8 GB RAM, ~ 500 Mbps network), 4BSD has a slight edge over ULE on real and sys time but is slightly worse on user time: GENERIC-NODEBUG, SCHED_4BSD: 6h29m25.17s real 7h2m56.02s user 14m52.63s sys 6h29m36.82s real 7h2m58.19s user 15m14.21s sys 6h28m27.61s real 7h1m38.24s user 14m56.91s sys 6h27m05.42s real 7h1m38.57s user 15m04.31s sys GENERIC-NODEBUG, SCHED_ULE: 6h34m19.41s real 6h59m43.99s user 18m8.62s sys 6h33m55.08s real 6h58m44.91s user 18m4.31s sys 6h34m49.68s real 6h56m03.58s user 17m49.83s sys 6h35m22.14s real 6h58m12.62s user 17m52.05s sys Note that in both cases there is lots of idle time (although far more in the -j36 case); this is partly due to a lack of parallelism in buildworld, but largely due to having /usr/obj mounted on Amazon EFS. These differences all seem within the range which could result from cache effects due to threads staying on one CPU rather than bouncing around; so whatever Rick is tripping over, it doesn't seem to be affecting these tests. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-current@freebsd.org Sat Jun 3 12:25:08 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE8F3BF0BA9 for ; Sat, 3 Jun 2017 12:25:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670081.outbound.protection.outlook.com [40.107.67.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5621B6ABC3; Sat, 3 Jun 2017 12:25:07 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0190.CANPRD01.PROD.OUTLOOK.COM (10.165.218.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1124.9; Sat, 3 Jun 2017 12:25:05 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1124.021; Sat, 3 Jun 2017 12:25:05 +0000 From: Rick Macklem To: Colin Percival , "freebsd-current@freebsd.org" CC: Andriy Gapon , "cem@freebsd.org" , "jeff@freebsd.org" , Ryan Stone Subject: Re: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) Thread-Topic: NFS client perf. degradation when SCHED_ULE is used (was when SMP enabled) Thread-Index: AQHS1mmgxqkdxhAY5U2DZ8FjIm51zqIIvdIkgAFvXYaACHL5gIAAeZGt Date: Sat, 3 Jun 2017 12:25:04 +0000 Message-ID: References: , <0100015c6c549e3d-228427b4-2734-4ab5-9eef-88fc9ae71f9a-000000@email.amazonses.com> In-Reply-To: <0100015c6c549e3d-228427b4-2734-4ab5-9eef-88fc9ae71f9a-000000@email.amazonses.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: FreeBSD.org; dkim=none (message not signed) header.d=none;FreeBSD.org; dmarc=none action=none header.from=uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0190; 7:PBYuF1+LjcoqmpWoEUHCpqz0QLUtXO++L6I6MQ6exsHJ3a0KHyQLhtnCCWqb1kAiCqR9kPM4qy3VHXwV5ElRea8urddil8cOrcJ/eMKVIHkCSwmEUKDSYiBoMMUWbstufRxMygx7XVH/PXkGKYzmfZ3eUvap0e6Rlt2t2Ckj2aodxaimqyzpzd1cb5CjDuaj4DWcZ7ILXSTWZXJYArJlsRh7m9KXfDNbUn9TIzJPbrZ+oR13WBKV3tVOaMecUPmeYEg9aXv1ws+3Z+OJAQcyl0bLTq/JMA+sn6UgmT6wGnrnPQ3ghH7UV79FaNajwLRWZiq7cy2YN8sDEyqhsLLN0g== x-ms-traffictypediagnostic: YTXPR01MB0190: x-ms-office365-filtering-correlation-id: 83af8286-1264-4527-d14e-08d4aa7b90a6 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:YTXPR01MB0190; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(100000703101)(100105400095)(10201501046)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR01MB0190; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR01MB0190; x-forefront-prvs: 0327618309 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39400400002)(39410400002)(39450400003)(39850400002)(39840400002)(24454002)(76176999)(2950100002)(53936002)(6246003)(74482002)(55016002)(189998001)(5660300001)(38730400002)(305945005)(74316002)(6506006)(77096006)(7696004)(102836003)(229853002)(6436002)(2900100001)(2906002)(3280700002)(14454004)(25786009)(3660700001)(4326008)(50986999)(54356999)(8676002)(122556002)(33656002)(9686003)(8936002)(54906002)(81166006)(2501003)(93886004)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0190; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2017 12:25:04.8758 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0190 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 12:25:08 -0000 Colin Percival wrote: >On 05/28/17 13:16, Rick Macklem wrote: >> cperciva@ is running a highly parallelized buuildworld and he sees bette= r >> slightly better elapsed times and much lower system CPU for SCHED_ULE. >> >> As such, I suspect it is the single threaded, processes mostly sleeping = waiting >> for I/O case that is broken. >> I suspect this is how many people use NFS, since a highly parallelized m= ake would >> not be a typical NFS client task, I think? > >Running `make buildworld -j36` on an EC2 "c4.8xlarge" instance (36 vCPUs, = 60 >GB RAM, 10 GbE) with GENERIC-NODEBUG, ULE has a slight edge over 4BSD: > >GENERIC-NODEBUG, SCHED_4BSD: > 1h14m12.48s real 6h25m44.59s user 1h4m53.42s sys > 1h15m25.48s real 6h25m12.20s user 1h4m34.23s sys > 1h13m34.02s real 6h25m14.44s user 1h4m09.55s sys > 1h13m44.04s real 6h25m08.60s user 1h4m40.21s sys > 1h14m59.69s real 6h25m53.13s user 1h4m55.20s sys > 1h14m24.00s real 6h24m59.29s user 1h5m37.31s sys > >GENERIC-NODEBUG, SCHED_ULE: > 1h13m00.61s real 6h02m47.59s user 26m45.89s sys > 1h12m30.18s real 6h01m39.97s user 26m16.45s sys > 1h13m08.43s real 6h01m46.94s user 26m39.20s sys > 1h12m18.94s real 6h02m26.80s user 27m39.71s sys > 1h13m21.38s real 6h00m46.13s user 27m14.96s sys > 1h12m01.80s real 6h02m24.48s user 27m18.37s sys > >Running `make buildworld -j2` on an E2 "m4.large" instance (2 vCPUs, 8 GB = RAM, >~ 500 Mbps network), 4BSD has a slight edge over ULE on real and sys >time but is slightly worse on user time: > >GENERIC-NODEBUG, SCHED_4BSD: > 6h29m25.17s real 7h2m56.02s user 14m52.63s sys > 6h29m36.82s real 7h2m58.19s user 15m14.21s sys > 6h28m27.61s real 7h1m38.24s user 14m56.91s sys > 6h27m05.42s real 7h1m38.57s user 15m04.31s sys > >GENERIC-NODEBUG, SCHED_ULE: > 6h34m19.41s real 6h59m43.99s user 18m8.62s sys > 6h33m55.08s real 6h58m44.91s user 18m4.31s sys > 6h34m49.68s real 6h56m03.58s user 17m49.83s sys > 6h35m22.14s real 6h58m12.62s user 17m52.05s sys Doing these test runs, but on the 36v CPU system would be closer to what I was testing. My tests do not use "-j" and run on an 8core chunk of real hardware. >Note that in both cases there is lots of idle time (although far more in t= he >-j36 case); this is partly due to a lack of parallelism in buildworld, but >largely due to having /usr/obj mounted on Amazon EFS. > >These differences all seem within the range which could result from cache >effects due to threads staying on one CPU rather than bouncing around; so >whatever Rick is tripping over, it doesn't seem to be affecting these test= s. Yep. Thanks for doing the testing, rick From owner-freebsd-current@freebsd.org Sat Jun 3 14:09:21 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9E0CBF220C for ; Sat, 3 Jun 2017 14:09:21 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from sonic306-48.consmr.mail.ne1.yahoo.com (sonic306-48.consmr.mail.ne1.yahoo.com [66.163.189.110]) by mx1.freebsd.org (Postfix) with ESMTP id B6AD370A35 for ; Sat, 3 Jun 2017 14:09:21 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1496498960; bh=bAW3ZKiez9vNzejl+D11y0dCUuKtgyJWFUXRHtwAG/8=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=cZsQ8ls90BEt0/TBi0KfXhpWJ2WbXXb14i2dA8nvuWZweiGHeXhLyKOxZU+Do/PaT9M+UVUpn9nfRfY4YtZoJUZwbuRBIUsaml86xXnZWR2KO4mfJwUSQ6uCAKCpK0fvN5e0NJCO3Kvsh+Q2GDfuIbLNF771+qQuAhDZJuVKN3rSslvz6uFSE2nEUIeeJdNpR8Yg4aWYgP6kEa2oDYCyT8FVNs1ercz+/srNpB9kLgiJp2U+0gT0OA9gdIiuSPVZBIHXytfP2J302nULf+2C78X1dmKpgdtiViOYSG+lmMKMVXZtlMhvR1zGywPp/0pSn8zqfj9/qj6dxLrskN7JbQ== X-YMail-OSG: KFIlrGgVM1nPRm8zg1ZFBUT1ntO77yZRZByU0IXL_o2snCJ_Rx4ZRADVQpKaBh. Z3OcKow8vyRdcqxgB0cl.FRnZWE83q2mPvSXL7Ht9NYXEDLuKbjoF1JOFm6iw8OUB9W6hz4JdGZ3 I1JEYRgOZfHtj1I7LzNzwGn5hVLg9B.7.McP3qSJRGkaWyNGJVYgeL1cBZaQMmiryX8DCgmDm30L FctMciwSBqAc5Qc_7TQbdkasxsZ4PWVP3n7B9WZ5oJmsHhU62HQsdz2IhRyppTxvoTkhc5iyOTeu 4CezZh0GSbcx3ia_ZKQ8auB2vBI6R3n_YUcekTOKAwiRGYyVpYahPGj4wSrm4Ve8gHaAZ3yWN1Yv WLKDcLg_nmS1odKGDZxpuwOepipMTwstbPgt1Ic5MU5JMzjK1x2TLYdXn3iz6t89e4NwSIh6c7f0 Bki3LCF4dxqf75cY1e7csdDuVd2aSrXJ1PkHYZVMS9VnerACcoGjfe.Wo.ZQ.otFEtisASEC2Vk8 rJhXYoEJHOt8hoCIcR92KmOV7LyJ4Z58pUbX5 Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ne1.yahoo.com with HTTP; Sat, 3 Jun 2017 14:09:20 +0000 Date: Sat, 3 Jun 2017 13:55:12 +0000 (UTC) From: Jeffrey Bouquet Reply-To: Jeffrey Bouquet To: , Tomoaki AOKI Cc: Jeffrey Bouquet , blubee blubeeme Message-ID: <1100140349.1166835.1496498112171@mail.yahoo.com> Subject: Re: nvidia drivers mutex lock MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <1100140349.1166835.1496498112171.ref@mail.yahoo.com> X-Mailer: WebService/1.1.9778 YahooMailBasic Mozilla/5.0 (X11; FreeBSD i386; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Lightning/5.1 X-Mailman-Approved-At: Sat, 03 Jun 2017 14:26:44 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 14:09:22 -0000 SOME LINES BOTTOM POSTED, SEE... -------------------------------------------- On Fri, 6/2/17, Tomoaki AOKI wrote: Subject: Re: nvidia drivers mutex lock To: freebsd-current@freebsd.org Cc: "Jeffrey Bouquet" , "blubee blubeeme" Date: Friday, June 2, 2017, 11:25 PM =20 Hi. Version 381.22 (5 days newer than 375.66) of the driver states... [1] =20 Fixed hangs and crashes that could occur when an OpenGL context is created while the system is out of available memory. =20 Can this be related with your hang? =20 IMHO, possibly allocating new resource (using os.lock_mtx guard) without checking the lock first while previous request is waiting for another can cause the duplicated lock situation. And high memory pressure would easily cause the situation. =20 [1] http://www.nvidia.com/Download/driverResults.aspx/118527/en-us =20 Hope it helps. =20 =20 On Thu, 1 Jun 2017 22:35:46 +0000 (UTC) Jeffrey Bouquet wrote: =20 > I see the same message, upon load, ... > -------------------------------------------- > On Thu, 6/1/17, blubee blubeeme wrote: >=20 >=C2=A0 Subject: nvidia drivers mutex lock >=C2=A0 To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org >=C2=A0 Date: Thursday, June 1, 2017, 11:35 AM >=C2=A0=20 >=C2=A0 I'm running nvidia-drivers 375.66 with a GTX >=C2=A0 1070 on FreeBSD-Current >=C2=A0=20 >=C2=A0 This problem just started happening >=C2=A0 recently but, every so often my laptop >=C2=A0 screen will just blank out and then I >=C2=A0 have to power cycle to get the >=C2=A0 machine up and running again. >=C2=A0=20 >=C2=A0 It seems to be a problem with nvidia >=C2=A0 drivers acquiring duplicate lock. Any >=C2=A0 info on this? >=C2=A0=20 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 acquiring duplicate lock of same type: >=C2=A0 "os.lock_mtx" >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: 1st >=C2=A0 os.lock_mtx @ nvidia_os.c:841 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: 2nd >=C2=A0 os.lock_mtx @ nvidia_os.c:841 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 stack backtrace: >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #0 >=C2=A0 0xffffffff80ab7770 at >=C2=A0 witness_debugger+0x70 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #1 >=C2=A0 0xffffffff80ab7663 at >=C2=A0 witness_checkorder+0xe23 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #2 >=C2=A0 0xffffffff80a35b93 at >=C2=A0 __mtx_lock_flags+0x93 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #3 >=C2=A0 0xffffffff82f4397b at >=C2=A0 os_acquire_spinlock+0x1b >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: #4 >=C2=A0 0xffffffff82c48b15 at _nv012002rm+0x185 >=C2=A0 Jun=E3=80=93 2 02:29:41 blubee kernel: >=C2=A0 ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: >=C2=A0 Argument #4 type mismatch - Found >=C2=A0 [Buffer], ACPI requires [Package] >=C2=A0 (20170303/nsarguments-205) >=C2=A0 Jun=E3=80=93 2 02:29:42 blubee kernel: >=C2=A0 nvidia-modeset: Allocated GPU:0 >=C2=A0 (GPU-54a7b304-c99d-efee-0117-0ce119063cd6) @ >=C2=A0 PCI:0000:01:00.0 >=C2=A0 =20 >=C2=A0 Best, >=C2=A0 Owen >=C2=A0 _______________________________________________ >=C2=A0 freebsd-ports@freebsd.org >=C2=A0 mailing list >=C2=A0 https://lists.freebsd.org/mailman/listinfo/freebsd-ports >=C2=A0 To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >=C2=A0=20 >=20 >=20 > ... then Xorg will run happily twelve hours or so.=C2=A0 The lockups here happen usually > when too large or too many of number of tabs/ large web pages with complex CSS etc > are opened at a time.=C2=A0=20 >=C2=A0 =C2=A0 So no help, just a 'me too'.=C2=A0=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 >=20 =20 =20 --=20 Tomoaki AOKI=C2=A0 =C2=A0 =20 ........................ might be a workaround Xorg/nvidia ran all night with this: nvidia-settings >> X server display configuration >> Advanced >> Force = Full Composition Pipeline ... for the laptop freezing. Could not hurt to try. " merge with Xorg.con= f " from nvidia-settings... ...................... 18 hours uptime so far, even past the 3 am periodic scripts. Have not rebooted out of the Xorg though so ma= y require edit-out of xorg.conf if that is the case, in other words differing from real-time appl= y and xorg initially start applies. =20 ........ =20 From owner-freebsd-current@freebsd.org Sat Jun 3 23:28:48 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21C37BFAD6A for ; Sat, 3 Jun 2017 23:28:48 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0956F8139E for ; Sat, 3 Jun 2017 23:28:48 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 08910BFAD67; Sat, 3 Jun 2017 23:28:48 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08022BFAD66; Sat, 3 Jun 2017 23:28:48 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF9BB8139D; Sat, 3 Jun 2017 23:28:47 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dHITG-0005ao-Af; Sun, 04 Jun 2017 01:28:38 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1dHITG-0006Jk-9e; Sun, 04 Jun 2017 01:28:38 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Sat, 03 Jun 2017 23:28:38 GMT From: "Jeffrey Bouquet" To: "current" CC: "ports" Subject: undefined symbol 'stat' Date: Sat, 03 Jun 2017 16:28:38 -0700 (PDT) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 23:28:48 -0000 The latest pkg updates broke firefox here, which won't build [ patches f= ail to apply ] Also seamonkey, but building sqlite3 locally fixed that. =20=20 [ not that I'd expect firefox to build anyway, not been that lucky recent= ly... ]=20 Web search turns up no 'undefined symbol stat' on 12.0-CURRENT that I can= find. Subject give the entirety of the error.=20 Building webkit-gtk2 locally as of now to try to fix it in a third round = of ports. ...=20= From owner-freebsd-current@freebsd.org Sat Jun 3 23:32:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 996E4BFAFA0 for ; Sat, 3 Jun 2017 23:32:14 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 76FAF817A3 for ; Sat, 3 Jun 2017 23:32:14 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6F02713E20 for ; Sat, 3 Jun 2017 23:32:06 +0000 (UTC) Subject: Re: undefined symbol 'stat' To: freebsd-current@freebsd.org References: From: Allan Jude Message-ID: <280bd5e8-e3d5-746e-3078-1bf615aee580@freebsd.org> Date: Sat, 3 Jun 2017 19:32:02 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Gt6x9M0T9rV3mflNc4i2bGnn44SrLiqvJ" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 03 Jun 2017 23:32:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Gt6x9M0T9rV3mflNc4i2bGnn44SrLiqvJ Content-Type: multipart/mixed; boundary="l2CBVdQ8GfXencBcEbHPkOQhiUJT38oxM"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: <280bd5e8-e3d5-746e-3078-1bf615aee580@freebsd.org> Subject: Re: undefined symbol 'stat' References: In-Reply-To: --l2CBVdQ8GfXencBcEbHPkOQhiUJT38oxM Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2017-06-03 19:28, Jeffrey Bouquet wrote: > The latest pkg updates broke firefox here, which won't build [ patch= es fail to apply ] > Also seamonkey, but building sqlite3 locally fixed that. > =20 > [ not that I'd expect firefox to build anyway, not been that lucky re= cently... ]=20 >=20 > Web search turns up no 'undefined symbol stat' on 12.0-CURRENT that I= can find. >=20 > Subject give the entirety of the error.=20 > Building webkit-gtk2 locally as of now to try to fix it in a third ro= und of ports. ...=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.o= rg" >=20 The ino64 change that went into -current recently changed a lot of stuff related to stat(), and versioned the symbol. You are trying to run apps compiled for a newer version of -current than you are running. You need to update your kernel and userland to patch what pkg is built against. --=20 Allan Jude --l2CBVdQ8GfXencBcEbHPkOQhiUJT38oxM-- --Gt6x9M0T9rV3mflNc4i2bGnn44SrLiqvJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJZM0b1AAoJEBmVNT4SmAt+M4wQANTDZgQIa0Sny2BVIy+Oakls D5oZrjSh9c1dby3IPkgJcCmD20jOc0eOGaNIy3pSX44aYezUhDAsjdmZNf84IMI3 YQhYFUC503f2yjHAu6hy0F6gldJRthdqav1+iSI3INpX6SgEwhZtDQizuqD3kZSD a25Anh9dGh5KXgD0MXSpqpMyPvjVIhB2OwTNJ3XtCvv0qDeBdziO/fcjAuVGhCm1 Qn6Sem2CjzrT6NRiCo2a0FafMTFSoZ/AAg6BVWtVQLCH2BKkc13cotfq2JEzNAJ1 02zxrtKrvBFvmWp/56oR/dPmmUREhQdJP8U4m1v/g5cwF7jAWT2E0cPnYfqji3LE eVf0OP22o3DX5xqgb1oVi3/wS1X9RDmEVhVjt/wIkegr53x2p7s5fc/K5NR1OG2+ kXMzLBdY3dvQFKQxFcGfCHnB2edfY6DC9XImxvIA/kdX1UgiYYd/735UhOFJnHvY bLCzm8ERbbInWec7HN6AwvgGrfIgFVqbVLI8OvzoTtknM9q1RClhGZaj0WTov2jh sn/N5+K+OSCGk58oSL6lhMGcjHV3SLy9bex010oBSCaXcbDK+lLiUxDvMCcZC8J9 eZZG65ksAPTwLLj33Cvyj0F/GWREd8kNSswAClJXnakBaEfDGl+DsY2mF2qcUWpp XDqZuFdRzk2BRJ48nMkk =wAA2 -----END PGP SIGNATURE----- --Gt6x9M0T9rV3mflNc4i2bGnn44SrLiqvJ--