From owner-freebsd-stable@freebsd.org Sun Jan 8 13:23:23 2017 Return-Path: Delivered-To: freebsd-stable@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 E115DCA5078 for ; Sun, 8 Jan 2017 13:23:23 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward1j.cmail.yandex.net (forward1j.cmail.yandex.net [5.255.227.19]) (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 9AA8E1D1A; Sun, 8 Jan 2017 13:23:23 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2m.mail.yandex.net (smtp2m.mail.yandex.net [77.88.61.129]) by forward1j.cmail.yandex.net (Yandex) with ESMTP id 604252025E; Sun, 8 Jan 2017 16:23:14 +0300 (MSK) Received: from smtp2m.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2m.mail.yandex.net (Yandex) with ESMTP id D458A2300BC5; Sun, 8 Jan 2017 16:23:12 +0300 (MSK) Received: by smtp2m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id BUQqpQQ8gN-NBOSbSCG; Sun, 08 Jan 2017 16:23:12 +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=yandex.ru; s=mail; t=1483881792; bh=Izm3Zg2kSVBQeRS7XzeO2WQ4gbaAkjAwu7OjGrNX42s=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=iE6+QHGSgiNHzNmXTd13ww/sfWbZX59Fp7ODEjFL+4KSoFOUMGjeGe2K+b7CiGanS lNz75PtTNOUWQRvqEYbKD3jjCQTkk40Xzc2FL7FDIJCjgnRfwIUjFXkKDmPVXHubbX 1EuSH9VbmkHcz75f24dG9FrmUNguaGgsg2rqS06o= Authentication-Results: smtp2m.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: coredump when loading cxgb after boot with routing daemon already running (RELENG11) To: Navdeep Parhar , Mike Tancsa References: Cc: FreeBSD-STABLE Mailing List , Gleb Smirnoff From: "Andrey V. Elsukov" Message-ID: <5cefdc60-2131-1eab-32fe-74212c93cc59@yandex.ru> Date: Sun, 8 Jan 2017 16:22:33 +0300 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=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 13:23:24 -0000 On 04.01.2017 22:07, Navdeep Parhar wrote: > What source line in releng-11 does ifioctl+0x6dd correspond to? > > (kgdb) l *(ifioctl+0x6dd) > > This might be race where the ifnet is being created or coming up and > zebra pokes it in some way before it's fully ready. If that's the > case it could affect any ifnet. Hi, from a quick look, it seems that ifnet becomes available for any actions just after if_alloc() and any strange things can happen in a window after if_alloc() and before if_attach(). Am I right? -- WBR, Andrey V. Elsukov From owner-freebsd-stable@freebsd.org Sun Jan 8 17:52:28 2017 Return-Path: Delivered-To: freebsd-stable@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 6672FCA54D9 for ; Sun, 8 Jan 2017 17:52:28 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 497B11084 for ; Sun, 8 Jan 2017 17:52:27 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id v08HqKvw061098 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 8 Jan 2017 09:52:20 -0800 (PST) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id v08HqKrn061097; Sun, 8 Jan 2017 09:52:20 -0800 (PST) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Sun, 8 Jan 2017 09:52:19 -0800 From: Gleb Smirnoff To: "Andrey V. Elsukov" Cc: Navdeep Parhar , Mike Tancsa , FreeBSD-STABLE Mailing List Subject: Re: coredump when loading cxgb after boot with routing daemon already running (RELENG11) Message-ID: <20170108175219.GW1647@FreeBSD.org> References: <5cefdc60-2131-1eab-32fe-74212c93cc59@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5cefdc60-2131-1eab-32fe-74212c93cc59@yandex.ru> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 17:52:28 -0000 On Sun, Jan 08, 2017 at 04:22:33PM +0300, Andrey V. Elsukov wrote: A> On 04.01.2017 22:07, Navdeep Parhar wrote: A> > What source line in releng-11 does ifioctl+0x6dd correspond to? A> > A> > (kgdb) l *(ifioctl+0x6dd) A> > A> > This might be race where the ifnet is being created or coming up and A> > zebra pokes it in some way before it's fully ready. If that's the A> > case it could affect any ifnet. A> A> Hi, A> A> from a quick look, it seems that ifnet becomes available for any actions A> just after if_alloc() and any strange things can happen in a window A> after if_alloc() and before if_attach(). Am I right? I believe so. That's why in projects/ifnet an interface will be attached by just if_alloc(). -- Totus tuus, Glebius. From owner-freebsd-stable@freebsd.org Mon Jan 9 15:02:14 2017 Return-Path: Delivered-To: freebsd-stable@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 4847FCA6C47 for ; Mon, 9 Jan 2017 15:02:14 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 0660B18A4 for ; Mon, 9 Jan 2017 15:02:14 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-ua0-x22d.google.com with SMTP id i68so359476991uad.0 for ; Mon, 09 Jan 2017 07:02:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=x1gAF6x1SeB9+hvUpsu7rRI+N/FLLkCFpBgKCc0mFZk=; b=Ie0dsDlffgIjyWN94OLnH/bQADOvsfvDhiP4QCquxe7m2zBXuf4QKoiW4YlpJ31aZH mIf9AOZA5Y7bSTJ6WUxLukjU8mGhTr8dXpb05o3H0+WYdFFT2x9WnYrLg2VPXCWto6Fv ptALipNJSEbrjAkNbxSuiUtTTyCNkcbYz67y4x/j8Q4cD1XHltvdO+vVhY6i8hsgb5ql dkOu8H+zDu1s+F35gN2A1ziZoN50Ecig9wDna3cMZk3yAl71azrA1gEeLXAd7iYTjHnb TYHRVjqPZVgywKaAKAn6cSPcyCZEGXS2hiUIIlgIS9HTUZCBsUJcATRlaUbNkPFR23j9 cTww== 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=x1gAF6x1SeB9+hvUpsu7rRI+N/FLLkCFpBgKCc0mFZk=; b=SHFBzT04zvmVXnkBNglpGDtUqjrj8RxByvBvYKDZPKsUdC1vk3S5kz8jinFg4266r6 AXlInch+Qj534aQeAZk0n1e4TJAnzOPi3NHWeC0LngbfdOimLGz2P6tmTg2f+A6Bie+M Ypm5D8H28GVpSPg2kULW+cAQ/+sAOYjxvvdyxc3/jMTQdXtAFTfQxkFJuKUh7M5a8aZe N2FCJh5x986jWbnE3s0KfY+nl8HkipzZRX6UZgmZLVL4oLVGBREijukzjQYhbBaOR43e Yb1PnQ37mSsQIbyiHX6IysoTCut+3lMa4e34akLktQVWPtMKkz4YT3TNIosMYBQDiww5 cNbw== X-Gm-Message-State: AIkVDXK26uBILJaPMv22tWSEcbI/i9CG/mMh+XpHFqW7ovikhunnc/ikrZLSfAl5U5a0cORfkybApbPw3wWgbA== X-Received: by 10.176.91.72 with SMTP id v8mr4256311uae.23.1483974130089; Mon, 09 Jan 2017 07:02:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.65.196 with HTTP; Mon, 9 Jan 2017 07:02:09 -0800 (PST) From: Pavel Timofeev Date: Mon, 9 Jan 2017 18:02:09 +0300 Message-ID: Subject: Additional daemon(8) functionality in STABLE? To: freebsd-stable stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 15:02:14 -0000 Hi, I noticed these useful commit that I'd highly appreciate in STABLE (11 in particular) https://svnweb.freebsd.org/base?view=revision&revision=307769 Is it possible? From owner-freebsd-stable@freebsd.org Mon Jan 9 15:14:31 2017 Return-Path: Delivered-To: freebsd-stable@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 A350BCA76BD for ; Mon, 9 Jan 2017 15:14:31 +0000 (UTC) (envelope-from me@cschwarz.com) Received: from orion.uberspace.de (orion.uberspace.de [95.143.172.79]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07F241451 for ; Mon, 9 Jan 2017 15:14:30 +0000 (UTC) (envelope-from me@cschwarz.com) Received: (qmail 13572 invoked from network); 9 Jan 2017 15:14:20 -0000 Received: from localhost (HELO csarch.local) (127.0.0.1) by orion.uberspace.de with SMTP; 9 Jan 2017 15:14:20 -0000 Received: by csarch.local (Postfix, from userid 1000) id 6DB2B4157A8; Mon, 9 Jan 2017 16:14:19 +0100 (CET) Date: Mon, 9 Jan 2017 16:14:19 +0100 From: Christian Schwarz To: Pavel Timofeev Cc: freebsd-stable stable Subject: Patches lost in Bugzilla: Was: Additional daemon(8) functionality in STABLE? Message-ID: <20170109151419.aqro6ogt3xnkuq7a@csarch> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20161126 (1.7.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 15:14:31 -0000 On Mon, Jan 09, 2017 at 06:02:09PM +0300, Pavel Timofeev wrote: > Hi, > I noticed these useful commit that I'd highly appreciate in STABLE (11 > in particular) > https://svnweb.freebsd.org/base?view=revision&revision=307769 > Is it possible? Only marginally related: I submitted a similar patch in February 2016. At the time, I didn't know about the existence of Phabricator because I was one year newer to the project than today. I imagine there are lots of useful patches in Bugzilla that are just never picked up. Maybe presenting an alert in Bugzilla when submitting a report with category 'base' and an attachment 'patch' could help there... Just sayin', Christian Schwarz From owner-freebsd-stable@freebsd.org Mon Jan 9 15:16:39 2017 Return-Path: Delivered-To: freebsd-stable@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 CE9C0CA78B5 for ; Mon, 9 Jan 2017 15:16:39 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 81C471693 for ; Mon, 9 Jan 2017 15:16:39 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v09FGVrT017860; Mon, 9 Jan 2017 15:16:31 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v09FGVQh017859; Mon, 9 Jan 2017 07:16:31 -0800 (PST) (envelope-from david) Date: Mon, 9 Jan 2017 07:16:31 -0800 From: David Wolfskill To: Pavel Timofeev Cc: freebsd-stable stable Subject: Re: Additional daemon(8) functionality in STABLE? Message-ID: <20170109151631.GT9748@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Pavel Timofeev , freebsd-stable stable References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XJ5wUQMT/jAb5xue" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 15:16:39 -0000 --XJ5wUQMT/jAb5xue Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 09, 2017 at 06:02:09PM +0300, Pavel Timofeev wrote: > Hi, > I noticed these useful commit that I'd highly appreciate in STABLE (11 > in particular) > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307769 > Is it possible? > .... Well, it looks *possible*: g1-252(11.0-S)[1] cd /usr/src g1-252(11.0-S)[2] svn info Path: . Working Copy Root Path: /usr/src URL: file:///svn/freebsd/src/base/stable/11 Relative URL: ^/stable/11 Repository Root: file:///svn/freebsd/src/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 311781 Node Kind: directory Schedule: normal Last Changed Author: kib Last Changed Rev: 311776 Last Changed Date: 2017-01-09 02:26:02 -0800 (Mon, 09 Jan 2017) g1-252(11.0-S)[3] svn merge -c 307769 --dry-run ^/head --- Merging r307769 into '.': U usr.sbin/daemon/daemon.8 U usr.sbin/daemon/daemon.c g1-252(11.0-S)[4] uname -a FreeBSD g1-252.catwhisker.org 11.0-STABLE FreeBSD 11.0-STABLE #217 r311776= M/311781:1100509: Mon Jan 9 04:57:48 PST 2017 root@g1-252.catwhisker.o= rg:/common/S1/obj/usr/src/sys/CANARY amd64 g1-252(11.0-S)[5]=20 I believe that you are requesting that jilles@ consider an MFC of r307769 to stable/11. Given the above, the change appears to "fit"; I believe that someone more familiar with the code (I have not even looked) would need to judge whether or not it would actually work. Peace, david --=20 David H. Wolfskill david@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying jerk??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --XJ5wUQMT/jAb5xue Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYc6lPXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XRHYH/i+fEfIIXFmAjCQL0N/M+Nyg ZRPj/bgaGmiqwZ8jN7t9VpRM4aYGlM39TmJCVgVxgbS8ytF6GxDvaSDLp+DqNnmP e7dQh2R4uEV1AC6Nm3+8TlWMNcmHNTEUJAFxHjrCaaZDkrFxPkfnTxxQt7zWIEPG tIh6x+ggUqrIyTT6+umz849KrrnOq8aKsJXgzBpB9dBnHtjhgm8iKJkCxJgP9MHP L86Ty+G+ouLmilMql2LDjrgcng76rRkg/RUPoxXzuCvoGiqgLvsBKxbEtEfGSYNE oRvrzdYJ85O0kC9L/hYaUQ/FyKiHvI6J+MISbRYEgHRNvV4PmRgfBjIIiZfN2zk= =r43G -----END PGP SIGNATURE----- --XJ5wUQMT/jAb5xue-- From owner-freebsd-stable@freebsd.org Tue Jan 10 10:37:50 2017 Return-Path: Delivered-To: freebsd-stable@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 E4157CA9B00 for ; Tue, 10 Jan 2017 10:37:50 +0000 (UTC) (envelope-from daniel.genis@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 519E61564 for ; Tue, 10 Jan 2017 10:37:49 +0000 (UTC) (envelope-from daniel.genis@gmx.de) Received: from [192.168.101.17] ([80.113.31.106]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MgtWa-1c4x1Y1cJc-00M4kV for ; Tue, 10 Jan 2017 11:32:28 +0100 To: freebsd-stable@freebsd.org From: Daniel Genis Subject: intel 10gbe nic bug in 10.3 - no carrier Message-ID: <11f0e9e6-cfe7-1cc7-49a0-4bc42fd0f99a@gmx.de> Date: Tue, 10 Jan 2017 11:32:29 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:uYcZpEZESBY9RTxyCGITAWu/4NW/Gwfo+Dl9xGCy9hOg3spZYyH /ZEA31l8/7KfkRC8dnpbjIyctJusxECnzhOyjXWJwFSoKQLbsUJyFm/jfxVur4pWqGh6tnk w/aQNBIanWMK/NaSngF31iuH9m9+bPwhpLE1zX1es0j1BZPpdTsIuoEWKloxs577W3jlMiF L1c1Uj5bcGYXjyJ2sYD2Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:Nd75CXk29V0=:dLMgbyRRclC5hrq3WYstGa Dsh/n2yO3ruI3mNx4E96GikRgWJdXgFwgqb9beAGJYc7pSDA1kjWZPvXR+kBSY4LhbdhaqS1a i9vB7lj4iw3MYCPSrcXeBGwB2I3mFYPEyDTs38DbwWKwLEZU50c0hAeYGJv2pxilZTQ1HmF/v +hWi7XBXo+2dO8MNPRaG4p3I6Pom1+vUh8X4xpT8LpdZceNZY54WD0Ilqv8ctRLRwQzXJ/Nc7 NFZ307Yb4rYEN8AcJ60cKubS1W46eNDpKiNrxwiSiEl2dYFKP7PbagUTrrbApjnUdrGEPrBUO Yfd8Ok3OV/XXq0cJ3enDhEgm2QtW/mz66vnly+wsu/NpgFEcCaVglALQi7kJV4rwgob+PbCEf hlYrMt2XrB2PajdJmgq5P5aacmux3+BJ+iqPdudSE0Gfl6AqRSTtF/oruW6Znmctb2j5sslpi frJP1+w3hlM5a105BYVw9shOSBNYTz9Ucf5Gl+aJVj9CvapPGX4J0er9QpLQuzVGs+vTYZVqc eir/aaBgqTr0TPahmNkBpzZgRDcoafsvuas9bA9WaXYpkdfx5RFoyT5HqlLeiYHKu2kvGqxgk 6ocz6uuuJuGqMaYkKIv3Y6DeQOa8kGyl3p56xpBd0TkAL5/rH0oo/8MklGvoYn0C1tQMBrupd 94rNWHFTdYh80azzyt0WkMbSzF2qOpR0HIrSz7Pp1jcWmJgPbjvHbmphDoahqrRuoVOpHF1jJ ep9YIapxnt45RXH/GguQcPTWlKJJT+S6pqTHt9fUHPQAZKm8HJO56jQyCQGjtWznf70ZSnroO 9oKgRxI X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 10:37:51 -0000 Hello everyone, we're trying to tackle a rare bug that is very hard to debug. Our 10.3-RELEASE servers can panic boot and subsequently can come up without network (2x - no carrier). We've seen this on 10.3-RELEASE-p0 we have never seen this before. root@storage ~ # pciconf -lv | grep -B3 network ix0@pci0:2:0:0: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' class = network -- ix1@pci0:2:0:1: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' class = network Our network is configured as active/passive using lagg. (/etc/rc.conf): ifconfig_ix0="up" ifconfig_ix1="up" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport ix0 laggport ix1 10.1.2.31/16" After panic boot the network show up like this: ix0: flags=8843 metric 0 mtu 1500 options=8407bb ether 60:08:10:d0:4e:9f nd6 options=29 media: (autoselect) status: no carrier ix1: flags=8843 metric 0 mtu 1500 options=8407bb ether 60:08:10:d0:4e:9f nd6 options=29 media: (autoselect) status: no carrier The network switch sees the connection as online. The LED's of the nic's suggest the same, they see the network as online (led's are on like in normal operation). Unplugging/replugging the network cable will get the network online. Shutting the port on the switch and reenabling it wil also get the network online. However another reboot will return the machine into the no-carrier state. I've built various kernels trying to find where the regression is without success. I tried porting the 10.2 nic driver (2.8.3) to 10.3 and subsequently the lagg code as well. I ported nic driver 3.1.14 from pfsense into 10.3-STABLE (2 december kernel) to no avail, also porting lagg code from 10.2 did not make any difference. Rebooting with those kernels the server remains in the no carrier state. We install our systems using mfsbsd for PXE boot. If I boot a machine which has the "no carrier" state using the 10.3 PXE boot, both nic's come online. If I then boot from disk again the machine returns into the "no carrier" state. Recently we got some new machines, so we can shuffle more around and also to try to debug this. We baseinstalled it using mfsbsd 10.3 pxe and configured it like always. Here interestingly one of the two nic's entered the "no carrier" state, the other nic remained operational. This remained persistent across reboots. The issue disappears after many reboots but it's not conclusive. I've had 2 machines with which I could experiment with. On one the problem it disappeared on it's own after a reboot (kernel 10.3-STABLE git hash d99ba5c aka r299900(?)). On the other one I pxe booted 10.1 live environment and then subsequently I booted into kernel 10.3-STABLE git hash 3673260fc9 aka r308456(?)). But I don't think anything can be concluded from that. That was the machine which had both nic's online after booting into the 10.3 pxe environment but subsequently returned into no carrier state when booting 10.3 from disk. We also tried many sysctl flags (and many reboots), but without success. For example: hw.ix.enable_msix=0 and hw.ix.enable_msi=0 At the moment I have no spare/empty machine in this state, we will empty one machine though which currently has this state (but is in production right now). I don't know how to trigger this state manually, which doesn't help for debugging. I could link reference where others report similar issues, for example https://www.reddit.com/r/PFSENSE/comments/45bcuq/10_gig_woes/ Here they suggest that the new intel nic driver 3.1.14 fixes it. Though I was not able to resolve the state by booting into a kernel with this driver. If I can provide any additional information please do not hesitate to ask. Any tips and suggestions for debugging are most welcome! With kind regards, Daniel From owner-freebsd-stable@freebsd.org Tue Jan 10 15:40:41 2017 Return-Path: Delivered-To: freebsd-stable@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 41CC8CA9150 for ; Tue, 10 Jan 2017 15:40:41 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (ingresso-1-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:411::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 135A51004 for ; Tue, 10 Jan 2017 15:40:41 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cQyXP-0009dv-On for freebsd-stable@freebsd.org; Tue, 10 Jan 2017 15:40:39 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87_1 (FreeBSD)) (envelope-from ) id 1cQyXP-000P3C-NE for freebsd-stable@freebsd.org; Tue, 10 Jan 2017 15:40:39 +0000 To: freebsd-stable@freebsd.org Subject: objcopy on 11-STABLE vs 10-STABLE Message-Id: From: Pete French Date: Tue, 10 Jan 2017 15:40:39 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 15:40:41 -0000 I run an iscsi setup booting using ixpe, which I build on the FreeBSD server. the last few steps of the build do this: objcopy -O binary -R .zinfo bin/ipxe.pxe.tmp bin/ipxe.pxe.bin objcopy -O binary -j .zinfo bin/ipxe.pxe.tmp bin/ipxe.pxe.zinfo This runs fine on 10-STABLE, but on 11-STABLE I get these warnings from the first command: objcopy: moving loadable section .bss.data16, is this intentional? objcopy: moving loadable section .bss.textdata, is this intentional? the resulting .bin file is not then useable and the build fails. If I copy over the objcopy from 10 and run that instead manually then it succeeds. Have been looking at the svn logs for the objcopy, and the thing which stands out is the PIE support stuff, but from my reading that has been reverted ? So I am a bit stumped - is this a bug in objcopy in 11 ? Or is is a change in default behaviour and the ipxe build needs to supply extra flags to get the old behaviour ? -pete. From owner-freebsd-stable@freebsd.org Tue Jan 10 18:33:31 2017 Return-Path: Delivered-To: freebsd-stable@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 328A5CA81B0 for ; Tue, 10 Jan 2017 18:33:31 +0000 (UTC) (envelope-from bounce@ims2.isendservice.com.br) Received: from ims2.isendservice.com.br (ims2.isendservice.com.br [54.232.111.224]) by mx1.freebsd.org (Postfix) with ESMTP id B01AC1848 for ; Tue, 10 Jan 2017 18:33:30 +0000 (UTC) (envelope-from bounce@ims2.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims2.isendservice.com.br (Postfix) with ESMTP id 5CC4B44A90 for ; Tue, 10 Jan 2017 16:29:04 -0200 (BRST) Date: Tue, 10 Jan 2017 16:29:04 -0200 (BRST) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: faculdadesenai@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <926929129.288612.1484072944231.JavaMail.root@ims2> Subject: =?ISO-8859-1?Q?Vestibular_SENAI_2017/1_-_Oportunidade_de_50%_?= =?ISO-8859-1?Q?de_desconto_no_1=BA_semestre_para_ex-aluno_SENAI?= bounce-key: <2420-22522874-1551230> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 18:33:31 -0000 From owner-freebsd-stable@freebsd.org Tue Jan 10 19:49:46 2017 Return-Path: Delivered-To: freebsd-stable@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 8313BCAA92D; Tue, 10 Jan 2017 19:49:46 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 80B631334; Tue, 10 Jan 2017 19:49:45 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [RFC/RFT] projects/ipsec To: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-stable@freebsd.org References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> From: "Andrey V. Elsukov" Message-ID: <3caafac9-d7ff-89bb-6fca-8968191ebb0a@FreeBSD.org> Date: Tue, 10 Jan 2017 22:48:59 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 19:49:46 -0000 Hi All, I ported the changes from projects/ipsec to stable/11 branch. So, if it is more suitable for testing, please, welcome. You can checkout the sources from github: https://github.com/bu7cher/freebsd/tree/stable/11 Also I made the standalone patch: https://people.freebsd.org/~ae/ipsec.diff Unfortunately, I did only compile test for stable branch. > I am pleased to announce that projects/ipsec, that I started several > months ago is ready for testing and review. > The main goals were: > * rework locking to make IPsec code more friendly for concurrent > processing; > * make lookup in SADB/SPDB faster; > * revise PFKEY implementation, remove stale code, make it closer > to RFC; > * implement IPsec VTI (virtual tunneling interface); > * make IPsec code loadable as kernel module. > > Currently all, except the last one is mostly done. So, I decided ask for > a help to test the what already done, while I will work on the last task. > > How to try? There are no patches, you need to checkout the full > projects/ipsec source tree, and build the kernel and the base system. > There are very few changes in the base system, mostly the kernel > changes. Thus for testing that old configuration is still work, it is > enough to build only the kernel. > > The approximate list of changes that may be visible to users: > * SA bundles now can have only 4 items in the chain. I think it is > enough, I can't imagine configurations when needed more. Also now SA > bundles supported for IPv6 too. > * due to changes in SPDB/SADB, systems where large number of SPs and SAs > are in use should get significant performance benefits. > * the memory consumption should slightly increase. There are several > hash tables and SP cache appeared. > * INPCB SP cache should noticeable increase network performance of > application when security policies are presence. > https://lists.freebsd.org/pipermail/freebsd-net/2015-April/042121.html > * use transport mode IPsec for forwarded IPv4 packets now unsupported. > This matches the IPv6 behavior, and since we can handle the replies, I > think it is useless. > * Added net.inet.ipsec.check_policy_history sysctl variable. When it is > set, each inbound packet that was handled by IPsec will be checked > according to matching security policy. If not all IPsec transforms were > applied, the check will fail, and packet will be dropped. > * Many PF_KEY messages handlers was updated, probably some IKEd now may > fail due to stricter checks. > * SPI now unique for each SA. This also can break something. > * Added if_ipsec interface. For more info look at > https://svnweb.freebsd.org/base?view=revision&revision=309115 > https://reviews.freebsd.org/P112 > * TCP_SIGNATURE code was reworked and now it behaves closer to RFC > https://svnweb.freebsd.org/base?view=revision&revision=309610 > * NAT-T support was reworked. > https://svnweb.freebsd.org/base?view=revision&revision=309808 > Also I made the patch to racoon that adds better support of NAT-T, > you can use this port to build patched racoon: > https://people.freebsd.org/~ae/ipsec-tools.tgz > > What results is interesting to me? > If you have some nontrivial configuration, please test. > If you have some configuration, that did't work, please test this branch. > If you have performance problems, please test. But don't forget that > this is head/ branch, you need to disable all debugging first. > If you just want to test, pay attention to the output of > `vmstat -m | egrep "sec|sah|pol|crypt"`. > If you have used TCP_SIGNATURE, IPSEC_NAT_T options, please test, this > support was significantly changed. IPsec as kernel modules was reported here: https://lists.freebsd.org/pipermail/freebsd-net/2016-December/046762.html Some additional testing also needed with this... -- WBR, Andrey V. Elsukov From owner-freebsd-stable@freebsd.org Tue Jan 10 21:21:07 2017 Return-Path: Delivered-To: freebsd-stable@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 DF822CAA7FC for ; Tue, 10 Jan 2017 21:21:07 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::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 A8374169F for ; Tue, 10 Jan 2017 21:21:07 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id r185so58439804ita.0 for ; Tue, 10 Jan 2017 13:21:07 -0800 (PST) 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=u5c1Dnd5bVQ+7Nd2BWqJvJnkS9tVT+Ol0Lo5i0Esz04=; b=MN6EG1Qry1XaEs9F4gX+inVrVB+a4evMKY9rBV/DEnZoCsnwyIoNltuj8Q81RdoVx+ 6AnVEyOfoKrM/uYcBH2rdDWXh4aEoeL6qklOiyu96g2xlOiBT6TDFf4oAh7DB9y3o5F8 mrhPYN2HuEKFRviBDJLdX2dSuRBMlt+uCFCRfB6FFBz5B5dRojwsR+Wk8eZBnjQrHaKp oR4V8d+K/qgGnjfd3DydCDAIHGlROIykffDztE5YIza3kzUeZFBpz2K7Hru7LghJ5hRr 5ZCIm47FtImPj6l03BI9r7DCN/YVAyxMglNY9M+eYwu5MtusSkbmkZIRW9Acjr9Z2jNM v+CA== 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=u5c1Dnd5bVQ+7Nd2BWqJvJnkS9tVT+Ol0Lo5i0Esz04=; b=NygSeoU9+cioXhbMvyZcjay2UWP9ugX3H4wOZJ/CfJPfUQG/8EgXcL+6wsbhEYek34 Vdp81CX5fHY82ruNMDf0G9/38y0Zaj9Do1RoKs58KnLjQt8NUXyYB3/RsxJ5hlzTvB69 t5sdHfPAPc3HYxTjE71yZI1WK/5Yk1WJ81oNg8gPyqIFeFhLbOY7gWyu6bbAPOkny/RM yHM7fzf4uCYPQLhsNddNkEmhWtB5Wm5n3zgAZJBFJQWE0MnJy8Pj/vSaWLcq9cbWhS30 kmoncEEaOOujAeLq9I2vkfUaX/R5uZPPxAGiU00njcPHTT0ZXFuab/uDFgT0moBCh8YS HByg== X-Gm-Message-State: AIkVDXK/LK0i+LCESbGsah+GGJB6kvb2IEODWHHZpYaw1GIH7zGLRs06Lbel2KmtpmqfoyO9OvKGqhu3UwAc2A== X-Received: by 10.36.240.11 with SMTP id s11mr2176120ith.16.1484083265420; Tue, 10 Jan 2017 13:21:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.43.67 with HTTP; Tue, 10 Jan 2017 13:21:04 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Fernando_Herrero_Carr=C3=B3n?= Date: Tue, 10 Jan 2017 22:21:04 +0100 Message-ID: Subject: Re: Cannot update system from 11-RELEASE-p2 to 11-RELEASE-p6 To: Holger Kipp Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 21:21:08 -0000 2017-01-07 23:38 GMT+01:00 Holger Kipp : > Dear Fernando, > > > On 7 Jan 2017, at 23:27, Fernando Herrero Carr=C3=B3n > wrote: > > > > Hi, > > > > I am seeing a strange behaviour. I run freebsd-update fetch: > > > > % sudo freebsd-update fetch > > Password: > > Looking up update.FreeBSD.org mirrors... 4 mirrors found. > > Fetching metadata signature for 11.0-RELEASE from update6.freebsd.org..= . > > done. > > Fetching metadata index... done. > > Inspecting system... done. > > Preparing to download files... done. > > > > No updates needed to update system to 11.0-RELEASE-p6. > > > > But: > > > > % uname -a > > FreeBSD pantera 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 > > 06:55:27 UTC 2016 > > > > Does this make sense? > > uname -a gives the version of the running OS. > > freebsd-version -ku gives installed versions for kernel and userland. > > Hi! Indeed that is the case: %% freebsd-version -ku 11.0-RELEASE-p2 11.0-RELEASE-p6 Thanks for the info! Best, Fernando From owner-freebsd-stable@freebsd.org Tue Jan 10 23:27:50 2017 Return-Path: Delivered-To: freebsd-stable@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 C8306CAA0A3; Tue, 10 Jan 2017 23:27:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 920A01BB1; Tue, 10 Jan 2017 23:27:50 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [IPv6:2001:470:923f:2:45dc:b573:f9f6:3f1e] (unknown [IPv6:2001:470:923f:2:45dc:b573:f9f6:3f1e]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 6AF39BF1; Wed, 11 Jan 2017 02:27:40 +0300 (MSK) Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org From: Lev Serebryakov Subject: IPv6 works on em0 () but not on em1 () - what's wrong? Organization: FreeBSD Message-ID: <58756DDE.5000503@FreeBSD.org> Date: Wed, 11 Jan 2017 02:27:26 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:27:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb Content-Type: multipart/mixed; boundary="7cBXNCGcc6249uUSx8mBLvafUtq8sGafB"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Message-ID: <58756DDE.5000503@FreeBSD.org> Subject: IPv6 works on em0 () but not on em1 () - what's wrong? --7cBXNCGcc6249uUSx8mBLvafUtq8sGafB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I have MoBo (Supermicro X9SCL-F) with two 1G NICs, first one (em0) is based on 82579LM, and second one (em1) is based on 82574L. When I'm using em0 with simple config: ifconfig_em0=3D"inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" ifconfig_em0_ipv6=3D"inet6 accept_rtadv" everything works fine - em0 get IPv6 prefix from rtadvd of my router and "tspdump -n -i em0 icmp6" shows some traffic, like router and prefix announcements. So far so good. I want to use em1 (and don't use em0 at all), because 82579LM has some known bugs according to SuperMicro support and someties hangs whole syste= m. So, I change config to ifconfig_em1=3D"inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" ifconfig_em1_ipv6=3D"inet6 accept_rtadv" connect em1 instead of em0 to the switch and reboot. And after that interface (em1) can not get IPv6 prefix, don't get global address (and shows only link-local one)and "tcpdump -n -i em1 icmp6" shows nothing at all! IPv4 works fine, though. What do I do wrong? Is it known issue of 82574L? I'm running 10-STABLE r311462. --=20 // Lev Serebryakov AKA Black Lion --7cBXNCGcc6249uUSx8mBLvafUtq8sGafB-- --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb 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) iQJ8BAEBCgBmBQJYdW3qXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePTYsQAKXgwFax2jAIyW2KyfPMRU47 wV2jlqSyAbuPQEY5WuNWspalRpUF/JfFLmDrbOfJudgTAsw/jZhFf5r04tbafcv+ njcy5vST3xqToqmpZzcWMjAJ61z+XOEGYN/+DYsu+GjZjBi5lJptEVuv5HRYS0ZR E+ZPRrPoBT4nJ3XV0nZzBVb5/I0Gg3sDg7zaqUF4BBgHUDVWQlOZfFwbEosUgFbg XEnDI2EVXNBpX99ES3dd8oyU6VPmt5VORw8m8kTUtIaxV7j/TuFXZ37N4P6UJ+u5 KCN3WAIQbcHrpLREb6oJ+v9JwRu/eGOjMsxFXRHd1oZ1vXN/tUVzpIDx7HWcHGv7 sJALLQIZhCoLV5bey/o2bOt2TtMrJylbamN8xe8mCvkks7EYYRFCBZhSp21leIbp W0VztHvgnJ3thrGRV7i6/e6ACvcOltQN6C0J0fm3NoD4fWhzlt6m5tUCR1cpqo4v a8IXO4VMMX+/CDFZWPYGrrZ8LeZIFkjDfIdA3NEUXoTi8XnVOEsvAY2DDNGRHwBh Cw1zEYhV80yYDyDujiCcnDz2/ff2ABLGLRZ9uyla1DPHGOfRVGCilWXeHk8WWtiC 8OYXcaMSYLodiBSDzj9C6S4ESQgfQdzNKHHSGv1CfLzNdikpnqtpHiCWWq0TtpG1 IUo4Sx9l6o+waj6WZ/Vn =ZW0l -----END PGP SIGNATURE----- --OSQIEdTTTT9av1bFQMCCaJmchsQ79ETgb-- From owner-freebsd-stable@freebsd.org Tue Jan 10 23:45:49 2017 Return-Path: Delivered-To: freebsd-stable@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 26AF2CAA8F2; Tue, 10 Jan 2017 23:45:49 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.allbsd.org", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87E5616E0; Tue, 10 Jan 2017 23:45:48 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail-d.allbsd.org (p2027-ipbf1605funabasi.chiba.ocn.ne.jp [123.225.191.27]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id v0ANjP83072743 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) (Client CN "/OU=GT07882699/OU=See+20www.rapidssl.com/resources/cps+20+28c+2915/OU=Domain+20Control+20Validated+20-+20RapidSSL+28R+29/CN=*.allbsd.org", Issuer "/C=US/O=GeoTrust+20Inc./CN=RapidSSL+20SHA256+20CA+20-+20G3"); Wed, 11 Jan 2017 08:45:44 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from alph.allbsd.org (alph.allbsd.org [192.168.0.10]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id v0ANi959076580 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Jan 2017 08:44:09 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.15.2/8.15.2) with ESMTPA id v0ANi7Ic076576; Wed, 11 Jan 2017 08:44:09 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 11 Jan 2017 08:43:28 +0900 (JST) Message-Id: <20170111.084328.1155081177427359974.hrs@allbsd.org> To: lev@FreeBSD.org Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: IPv6 works on em0 () but not on em1 () - what's wrong?,IPv6 works on em0 () but not on em1 () - what's wrong? From: Hiroki Sato In-Reply-To: <58756DDE.5000503@FreeBSD.org> References: <58756DDE.5000503@FreeBSD.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jan_11_08_43_28_2017_181)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.4.3 (mail.allbsd.org [133.31.130.32]); Wed, 11 Jan 2017 08:45:45 +0900 (JST) X-Spam-Status: No, score=-98.9 required=13.0 tests=CONTENT_TYPE_PRESENT, FAKEDWORD_ONE,FAKEDWORD_VERTICALLINE,QENCPTR1,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on gatekeeper.allbsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:45:49 -0000 ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lev Serebryakov wrote in <58756DDE.5000503@FreeBSD.org>,<58756DDE.5000503@FreeBSD.org>: le> le> I have MoBo (Supermicro X9SCL-F) with two 1G NICs, first one (em0) is le> based on 82579LM, and second one (em1) is based on 82574L. le> le> When I'm using em0 with simple config: le> le> ifconfig_em0="inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" le> ifconfig_em0_ipv6="inet6 accept_rtadv" le> le> everything works fine - em0 get IPv6 prefix from rtadvd of my router le> and "tspdump -n -i em0 icmp6" shows some traffic, like router and prefix le> announcements. So far so good. le> le> I want to use em1 (and don't use em0 at all), because 82579LM has some le> known bugs according to SuperMicro support and someties hangs whole system. le> le> So, I change config to le> le> ifconfig_em1="inet 192.168.134.2 netmask 255.255.255.0 mtu 9000" le> ifconfig_em1_ipv6="inet6 accept_rtadv" le> le> connect em1 instead of em0 to the switch and reboot. And after that le> interface (em1) can not get IPv6 prefix, don't get global address (and le> shows only link-local one)and "tcpdump -n -i em1 icmp6" shows nothing at le> all! IPv4 works fine, though. le> le> What do I do wrong? Is it known issue of 82574L? le> le> I'm running 10-STABLE r311462. What happens by typing the following command? % ping6 ff02::1%em1 -- Hiroki ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlh1caAACgkQTyzT2CeTzy0JSwCgqt5XrlsxqIO9wDWtEsJ4Gdnv d+wAniNiFLYgtmVop7U53AzogMHR2pI3 =iqLm -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jan_11_08_43_28_2017_181)---- From owner-freebsd-stable@freebsd.org Tue Jan 10 23:49:29 2017 Return-Path: Delivered-To: freebsd-stable@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 E7C28CAAC40 for ; Tue, 10 Jan 2017 23:49:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-ua0-x241.google.com (mail-ua0-x241.google.com [IPv6:2607:f8b0:400c:c08::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 A53B01AD9 for ; Tue, 10 Jan 2017 23:49:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-ua0-x241.google.com with SMTP id 96so47620286uaq.2 for ; Tue, 10 Jan 2017 15:49:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=7TN/3hviHONgBAts3kSPsH/e5OyMOnAqYi657hSsPMo=; b=NBkTRUvX66fhyaZh2Q792JvN4ooQ6XPBhATAZXavFPr+zXEtPS3hlN8ZFCST4HL6hK 0QZezUKSdc5xdznaakVmnT4u2GupkQ3lzOUt2YW3aMteFmU5sMrg/AQgUUE4IqdApKJj GtbhVnb9HzAdPn4V31QixJl1ep6L7UnW9H7XEUaDdTc4UErigBeESCGs003jV0P0vDn1 GKRHglFCRqljZirueQBXfJpEGz95uqgWvruvR9nR3AAA3+ex+mFyt6KLU+zcthOtPPoL daL0XTB/tBZLN1MLhpCEECTTEPsN9Yf6720fzNlQcICXdOPgv5irxFBSFzsSwLb+yEqY s47w== 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:cc; bh=7TN/3hviHONgBAts3kSPsH/e5OyMOnAqYi657hSsPMo=; b=PvBfKd6c5XqGWkxdBrrhwG8WucfL2pPzlH3EEWQFsrAz4hhXm/iWeDUR5wpXzuRNHw iOrPrC4yifRHpD180Zib0bEJZ16ZOYV/QZEW0DlUU3HIghXx7fdBKNapP/L4n9SzPHwK Y1X8SZJ4hIl3zHTfpn2qTeCSNftGQXRVTPpCGRgotAjngGzmPK411pyrzQNkSekMB4pb w293jm4+G+VBJtUBiaiDSszQcP2r0XEk27v1kUUjeTVm6nvefTT/DBeZ4dxDMoN/TWLB Wx3q30IVwopa/I7/bhTCN4p3c1b+eVsw8DZqiZLHZ1RZGi2EOIEJDADQDuHOcDcEk+sJ sMQg== X-Gm-Message-State: AIkVDXIUgi+DTu5ls6QUkjfEemIqfGVi5nq/aA+9Yf3Vuq5oYAmyQ829wkynlJ5YCIViRGEybjXChGEW18I11g== X-Received: by 10.159.51.18 with SMTP id o18mr2616104uab.14.1484092168828; Tue, 10 Jan 2017 15:49:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.74.150 with HTTP; Tue, 10 Jan 2017 15:49:28 -0800 (PST) From: Lee Brown Date: Tue, 10 Jan 2017 15:49:28 -0800 Message-ID: Subject: General question about 1GB vs 10GB NIC's To: lev@freebsd.org Cc: freebsd-net , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:49:30 -0000 I want to build a router that has 2 x 500mb/s radio ISP facing, 2 x 500mb/s radio's facing another site, plus a 1gb/s link to the LAN. I plan to plug everything into a switch so I can have redundant routers. So my question is should I go with 5 x 1GB NIC's or 2x10GB NIC's on the motherboard. Assume NIC's will be Intel or IBM. Going 10GB pushes the switch price ten-times, so I'd like to avoid that if possible. I'm planning to get a 4 core Xeon @3.4GHz and it would be nice to know if this is a moot point or not. Thanks -- lee From owner-freebsd-stable@freebsd.org Tue Jan 10 23:58:32 2017 Return-Path: Delivered-To: freebsd-stable@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 70FE9CAA48A; Tue, 10 Jan 2017 23:58:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3FC8F136F; Tue, 10 Jan 2017 23:58:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:e0f4:994:662:862]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2EBF2C04; Wed, 11 Jan 2017 02:58:31 +0300 (MSK) Date: Wed, 11 Jan 2017 02:58:33 +0300 From: Lev Serebryakov Reply-To: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <13626377.20170111025833@serebryakov.spb.ru> To: Hiroki Sato CC: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: IPv6 works on em0 () but not on em1 () - what's wrong?,IPv6 works on em0 () but not on em1 () - what's wrong? In-Reply-To: <20170111.084328.1155081177427359974.hrs@allbsd.org> References: <58756DDE.5000503@FreeBSD.org> <20170111.084328.1155081177427359974.hrs@allbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 23:58:32 -0000 Hello Hiroki, Wednesday, January 11, 2017, 2:43:28 AM, you wrote: > What happens by typing the following command? > % ping6 ff02::1%em1 % ping6 ff02::1%em1 PING6(56=40+8+8 bytes) fe80::225:90ff:fe24:6bf8%em1 --> ff02::1%em1 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=0 hlim=64 time=0.163 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=0 hlim=64 time=0.737 ms(DUP!) 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=1 hlim=64 time=0.132 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=1 hlim=64 time=0.766 ms(DUP!) 16 bytes from fe80::225:90ff:fe24:6bf8%em1, icmp_seq=2 hlim=64 time=0.086 ms 16 bytes from fe80::222:4dff:fe9d:e093%em1, icmp_seq=2 hlim=64 time=0.713 ms(DUP!) ... BTW, when I add address and default route by hands, everything starts to work. So, this NIC doesn't have problems with IPv6 per se! Looks like some weird configuration problem. -- Best regards, Lev mailto:lev@FreeBSD.org From owner-freebsd-stable@freebsd.org Wed Jan 11 14:40:04 2017 Return-Path: Delivered-To: freebsd-stable@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 6B9B5CAAEF3 for ; Wed, 11 Jan 2017 14:40:04 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 124B41FAF for ; Wed, 11 Jan 2017 14:40:03 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id EC4A61110D4 for ; Wed, 11 Jan 2017 08:31:52 -0600 (CST) To: FreeBSD-STABLE Mailing List From: Karl Denninger Subject: Ugh -- attempted to update this morning, and got a nasty panic in ZFS.... Message-ID: Date: Wed, 11 Jan 2017 08:31:41 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms060807040908090103090707" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 14:40:04 -0000 This is a cryptographically signed message in MIME format. --------------ms060807040908090103090707 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable During the reboot, immediately after the daemons started up on the machine (the boot got beyond mounting all the disks and was well into starting up all the background stuff it runs), I got a double-fault. =2E.... (there were a LOT more of this same; it pretty clearly was a recursive call sequence that ran the system out of stack space) #294 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #295 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010c8f27b0) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3127= #296 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #297 0xffffffff822e464d in vdev_queue_io_done (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:913 #298 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff8010cff0b88) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3152= #299 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #300 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010cff0b88) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3127= #301 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #302 0xffffffff822e464d in vdev_queue_io_done (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:913 #303 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff8010c962000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3152= #304 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #305 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010c962000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3127= #306 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #307 0xffffffff822e464d in vdev_queue_io_done (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:913 #308 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff80102175000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3152= #309 0xffffffff822fdcfd in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1666= #310 0xffffffff80b2585a in taskqueue_run_locked (queue=3D) at /usr/src/sys/kern/subr_taskqueue.c:454 #311 0xffffffff80b26a48 in taskqueue_thread_loop (arg=3D) at /usr/src/sys/kern/subr_taskqueue.c:724 #312 0xffffffff80a7eb05 in fork_exit ( callout=3D0xffffffff80b26960 , arg=3D0xfffff800b8824c30, frame=3D0xfffffe0667430c00) at /usr/src/sys/kern/kern_fork.c:1040 #313 0xffffffff80f87c3e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #314 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) =2E.... NewFS.denninger.net dumped core - see /var/crash/vmcore.3 Wed Jan 11 08:15:33 CST 2017 FreeBSD NewFS.denninger.net 11.0-STABLE FreeBSD 11.0-STABLE #14 r311927M: Wed Ja n 11 07:55:20 CST 2017 =20 karl@NewFS.denninger.net:/usr/obj/usr/src/sys/KSD-SMP amd64 panic: double fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for detail= s. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal double fault rip =3D 0xffffffff822e3c5d rsp =3D 0xfffffe066742af90 rbp =3D 0xfffffe066742b420 cpuid =3D 15; apic id =3D 35 panic: double fault cpuid =3D 15 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0649ddee30 vpanic() at vpanic+0x186/frame 0xfffffe0649ddeeb0 panic() at panic+0x43/frame 0xfffffe0649ddef10 dblfault_handler() at dblfault_handler+0xa2/frame 0xfffffe0649ddef30 Xdblfault() at Xdblfault+0xac/frame 0xfffffe0649ddef30 --- trap 0x17, rip =3D 0xffffffff822e3c5d, rsp =3D 0xfffffe066742af90, rb= p =3D 0xfffff e066742b420 --- # Work around for this CPU from 11.x eratta vm.pmap.pcid_enabled=3D0 # # # Try to avoid kernel stack exhaustion due to TRIM storms. kern.kstack_pages=3D"6" I have kstack_pages set to "6" to try to avoid another panic that I got occasionally during zfs backup operations which appeared to be linked to "too many" TRIMs, and looks very similar to this one. I rebooted back to kernel.old, which was built in October, and the machine came up normally. I'll try the newer build again and see if this was transient and related to delayed TRIM operations on the disks related to the installworld/installkernel. But if it is then it remains a problem -- and setting stackpages didn't help! I've got the dump if anything in particular would be of help. The prompt to do this in the first place was the openssh CVE that was recently issued..... --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms060807040908090103090707 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAxMTExNDMxNDFaME8GCSqGSIb3DQEJBDFCBECRL4ZN +LxpNeb0BsuqGt3hb82auRNiQiUQit+4RwwW70JZ3QZFda3F9oBrA+46+xyai9haslBg1slE E/iIeI/AMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIAhlJJSzf02a1X wLAWkuBXOF0Kt4LXdbcISV0Eg9EjPHfG4GU/rT1y4kbTmgzm1pm3N+W/vvtUZGP1KQYIrpPN o1YVdq/eviiBOIlP/pxFrOg/RnBhcUeE1QW55jeQgvzkWrqA/pEoPkrYC3dPOrqqcCkL7Ffi ZyjqipAWiGVSiha1+wcqHKvwmZSq0yHmjb7WRWVKJkOzQC1zHdS2DRXWVMfp90LcELcQ3i8t r0Qsbo6MY/UWV6JLxTkD8mlbr/7/Q1Fw9ZpeoyozBOeik1T7CXK45mGcPhOD9Vz/NYxUvgJL BSb8c3EANmceqeQsrES9+EqOPm+9g9FmKCIGuCJSUFQTWzYQYgC+fzvrwqTQcail27YDUBvb xgv16+tIwHNFyX0UV5BZnaFdY6N129ZscHT7D16C/tij8F37eA+g6rrsKEibxPoqmCMI6JBw J8TV1QNEp6gZcCgpGC+702269oWvIiTzUYHOCmwYDo0spteMAi0sJIXvMZ6/N0NshTy3VQNr QW+0jyIJ3rRcfUWdrHy2Jum1rlvdt2DsuLzCqIYn2DevNn6LUrYQ+EeHEw39hLjDgOJFE+eZ Wea7tGMgHXVxKUS5NbjdiXl8e88nLc+TImw6OcdKuWAay5IJDf5RB0GZ+05zolfKwqjSFFyf 0BT4vp31QMTHgvmkneaI3IkAAAAAAAA= --------------ms060807040908090103090707-- From owner-freebsd-stable@freebsd.org Wed Jan 11 14:41:42 2017 Return-Path: Delivered-To: freebsd-stable@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 02D50CAA150 for ; Wed, 11 Jan 2017 14:41:42 +0000 (UTC) (envelope-from mnandan@saraexim.in) 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 D747613AF for ; Wed, 11 Jan 2017 14:41:41 +0000 (UTC) (envelope-from mnandan@saraexim.in) Received: by mailman.ysv.freebsd.org (Postfix) id D69E1CAA14F; Wed, 11 Jan 2017 14:41:41 +0000 (UTC) Delivered-To: stable@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 D6443CAA14E for ; Wed, 11 Jan 2017 14:41:41 +0000 (UTC) (envelope-from mnandan@saraexim.in) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 9878013AD for ; Wed, 11 Jan 2017 14:41:41 +0000 (UTC) (envelope-from mnandan@saraexim.in) Received: by mail-qk0-x22b.google.com with SMTP id a20so211301158qkc.1 for ; Wed, 11 Jan 2017 06:41:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=saraexim-in.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=M2j4PfPlJtqgwls9h1XnzGNKVuDtMIUKThuiVKWm8Fk=; b=xovtYeRhpoVbtAq71MmwSZCPStb8tg4pHMQ7mqf0G+A116UxqskKZpG8umLSz5V55W GIMQnoXg317Qs5JIdsyyGVZwStQm/iSbMOdY6ntXXHrWXK3B68tKmUtB+hLnwotkaIZq IORQ6C9jVp3zd23rUv4zj+/AQBTCb6B75RzvMjTsggZ0OOaR/8Sp/dg3Q1XMWp8n4BOh Z1gJ8GjbpnTKUyeqobZnJcZxuwGPeZ63sXB3ipukvmMKArLyg2RsOLRD1uUcsv0G/w4j BdRbNYsdmGZW3RgUmNgI2ng5Et9GLcQoQYlrwBYNC85MXTzVbkoj6VlyQu2QjOZq0IjX EDMA== 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=M2j4PfPlJtqgwls9h1XnzGNKVuDtMIUKThuiVKWm8Fk=; b=rFWfsdM/fb+j+PfsqtwRimcwsJs2KiuYkanJXqEK3Gm5N9uzcTSTuiXPjLW6KfCbTB O4odeKwSAFz7i/GtiHICcmT5ubZUO/OvHN0+gaVsJibdb0aYEj4mO2D8Ng5teUobJvy2 dYzEWB2r5WmlDZbXPQLoWe2yPS5QdAhY0ADGxQghgBem6CmkJsj94QSVipqTJmIEgm2j zOmknucFj0u1bNcXKpJJs9LSBYvh+hP/Y+to1WtDTg52lu30m6594e/7dYosw3J78eZ4 MrMIhfpgVs/K9tn3jKpUfOTiGRwmCok13ArlErG/sE3UnYEVJUX/pF8mPTCdht1M+NR8 JdJA== X-Gm-Message-State: AIkVDXLy16zmj7cIjMH1x8664ZUqw0ai4M4dUFOus0OcXjmJh1zl8L5Y29DWxlVgX19FJpj+iSgtaS80DDR3WQ== X-Received: by 10.55.9.14 with SMTP id 14mr8119376qkj.250.1484145699944; Wed, 11 Jan 2017 06:41:39 -0800 (PST) Received: from 776393159873 named unknown by gmailapi.google.com with HTTPREST; Wed, 11 Jan 2017 06:39:20 -0800 MIME-Version: 1.0 Received: by 10.195.6.97 with HTTP; Thu, 5 Jan 2017 05:33:21 -0800 (PST) From: Mousumi Nandan Date: Wed, 11 Jan 2017 06:39:20 -0800 Message-ID: Subject: Season's Greetings To: stable@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-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 14:41:42 -0000 [image: Inline image 1] Please reply to this email if you want to unsubscribe. Best Regards *Mousumi Nandan * SARA | Business Development Executive Mobile: +91 987 45678 47 Office: +91 33 400 88 333 Email: mousumi.sarainternational@gmail.com sales.sarainternational@gmail.com info.sarainternational@gmail.com Sara International =E2=80=9CWe believe in building long term relationship=E2=80=9D 55 Ezra Street, 2nd Floor, Kolkata West Bengal, India Add a magic button to Gmail From owner-freebsd-stable@freebsd.org Wed Jan 11 14:50:52 2017 Return-Path: Delivered-To: freebsd-stable@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 CBBDCCAA6A3 for ; Wed, 11 Jan 2017 14:50:52 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) (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 7186518A8 for ; Wed, 11 Jan 2017 14:50:52 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 160D31110E9 for ; Wed, 11 Jan 2017 08:50:50 -0600 (CST) Subject: Re: Ugh -- attempted to update this morning, and got a nasty panic in ZFS.... To: freebsd-stable@freebsd.org References: From: Karl Denninger Message-ID: Date: Wed, 11 Jan 2017 08:50:39 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms040201020101040609020401" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 14:50:52 -0000 This is a cryptographically signed message in MIME format. --------------ms040201020101040609020401 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable A second attempt to come up on the new kernel was successful -- so this had to be due to queued I/Os that were pending at the time of the shutdown.... On 1/11/2017 08:31, Karl Denninger wrote: > During the reboot, immediately after the daemons started up on the > machine (the boot got beyond mounting all the disks and was well into > starting up all the background stuff it runs), I got a double-fault. > > ..... (there were a LOT more of this same; it pretty clearly was a > recursive call sequence that ran the system out of stack space) > > #294 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #295 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010c8f27b0)= > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 27 > #296 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #297 0xffffffff822e464d in vdev_queue_io_done (zio=3D) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:91= 3 > #298 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff8010cff0b88) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 52 > #299 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #300 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010cff0b88)= > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 27 > #301 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #302 0xffffffff822e464d in vdev_queue_io_done (zio=3D) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:91= 3 > #303 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff8010c962000) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 52 > #304 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #305 0xffffffff8230130e in zio_vdev_io_start (zio=3D0xfffff8010c962000)= > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 27 > #306 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #307 0xffffffff822e464d in vdev_queue_io_done (zio=3D) > at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:91= 3 > #308 0xffffffff823014c9 in zio_vdev_io_done (zio=3D0xfffff80102175000) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:31= 52 > #309 0xffffffff822fdcfd in zio_execute (zio=3D) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:16= 66 > #310 0xffffffff80b2585a in taskqueue_run_locked (queue=3D out>) > at /usr/src/sys/kern/subr_taskqueue.c:454 > #311 0xffffffff80b26a48 in taskqueue_thread_loop (arg=3D) > at /usr/src/sys/kern/subr_taskqueue.c:724 > #312 0xffffffff80a7eb05 in fork_exit ( > callout=3D0xffffffff80b26960 , > arg=3D0xfffff800b8824c30, frame=3D0xfffffe0667430c00) > at /usr/src/sys/kern/kern_fork.c:1040 > #313 0xffffffff80f87c3e in fork_trampoline () > at /usr/src/sys/amd64/amd64/exception.S:611 > #314 0x0000000000000000 in ?? () > Current language: auto; currently minimal > (kgdb) > > ..... > > > NewFS.denninger.net dumped core - see /var/crash/vmcore.3 > > Wed Jan 11 08:15:33 CST 2017 > > FreeBSD NewFS.denninger.net 11.0-STABLE FreeBSD 11.0-STABLE #14 > r311927M: Wed Ja > n 11 07:55:20 CST 2017 =20 > karl@NewFS.denninger.net:/usr/obj/usr/src/sys/KSD-SMP > amd64 > > panic: double fault > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and yo= u are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for deta= ils. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > Fatal double fault > rip =3D 0xffffffff822e3c5d > rsp =3D 0xfffffe066742af90 > rbp =3D 0xfffffe066742b420 > cpuid =3D 15; apic id =3D 35 > panic: double fault > cpuid =3D 15 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe0649ddee30 > vpanic() at vpanic+0x186/frame 0xfffffe0649ddeeb0 > panic() at panic+0x43/frame 0xfffffe0649ddef10 > dblfault_handler() at dblfault_handler+0xa2/frame 0xfffffe0649ddef30 > Xdblfault() at Xdblfault+0xac/frame 0xfffffe0649ddef30 > --- trap 0x17, rip =3D 0xffffffff822e3c5d, rsp =3D 0xfffffe066742af90, = rbp =3D > 0xfffff > e066742b420 --- > > # Work around for this CPU from 11.x eratta > vm.pmap.pcid_enabled=3D0 > # > # > # Try to avoid kernel stack exhaustion due to TRIM storms. > kern.kstack_pages=3D"6" > > I have kstack_pages set to "6" to try to avoid another panic that I got= > occasionally during zfs backup operations which appeared to be linked t= o > "too many" TRIMs, and looks very similar to this one. > > I rebooted back to kernel.old, which was built in October, and the > machine came up normally. I'll try the newer build again and see if > this was transient and related to delayed TRIM operations on the disks > related to the installworld/installkernel. But if it is then it remain= s > a problem -- and setting stackpages didn't help! > > I've got the dump if anything in particular would be of help. > > The prompt to do this in the first place was the openssh CVE that was > recently issued..... > > --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms040201020101040609020401 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAxMTExNDUwMzlaME8GCSqGSIb3DQEJBDFCBEDCIM2n cX1tewY0iP3pR4zDeqkuvjQF04VOEj84c0NB/WgkN7h4xJvjq0nLqlm8REn0tWQNhVsxImTg UoioKO1xMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIAtgjmXpsrriXc o3oXYlQ07zpf371emoDkU/jGasKy6HT+uo89je3BS5ZOReKtnT3cA0Iwm5r9W//1ZegN7kTy a45o8Y9aAPZXE84EFDLnGRlIMMkb35v7f+P9V0D9ImU4UjhJxXegajNrqpnEeDRKxGwcz/ck SVwEECf21b4kgYNq1jZn2D9sJ5IGTu4d+CIUY3dzJwIzWo0DH9+MxaV5VuEIWC8Dgwj0ZSQ+ BAK31UlCLVSW8jODZRURBprIT1t2/mDBVzQkwF7izIQoUHEV2DWOYpprStj2QShhZyBeNTRn i0pW6z98yaRgGTSlSNtKW2RpldgNPixcmwfaAZoWkAASo57yz+p5gybF0h68vSE3NVGK4ltt 1Xo7a/J+IKs4f5ZZKgQJv8FKAB8M30AAxhibJLqjeJ14oGNTJCiMmdxWFHl+r+u1qbTGTVfS E7J3Wxj5UudIKEbQ8bNddt6BjrJU9Y+4qwId1eiTSksw3d58y/LKXEVYyQyUQ8jLxsezJCTM 2WLvEu9NYoyrWsBbU+wNNzzcGZKJ3MHEfziNpgYwyoThivnlBMQSZrLBByWDk97XkMNVMiab kfGEUrN0Yr6nEckYvCsSWho9ovZ4CNilYHLpcUn2jdvW+cSjtiRfEuOTUp6/3ENsiyZUSh/8 9ewJ3IeuL4PoYOriNSgmGUQAAAAAAAA= --------------ms040201020101040609020401-- From owner-freebsd-stable@freebsd.org Wed Jan 11 18:30:33 2017 Return-Path: Delivered-To: freebsd-stable@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 1F356CAB5E8 for ; Wed, 11 Jan 2017 18:30:33 +0000 (UTC) (envelope-from David.Boyd49@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F08D915E7 for ; Wed, 11 Jan 2017 18:30:32 +0000 (UTC) (envelope-from David.Boyd49@twc.com) Received: from [96.28.207.162] ([96.28.207.162:60362] helo=bashful.bsd1.net) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 0C/56-03829-10976785; Wed, 11 Jan 2017 18:27:13 +0000 Message-ID: <1484159232.4082.0.camel@twc.com> Subject: Re: Regression in pciconf utility in releng/11.0 From: David Boyd To: freebsd-stable@freebsd.org Date: Wed, 11 Jan 2017 13:27:12 -0500 In-Reply-To: <1482938097.5904.5.camel@twc.com> References: <1482938097.5904.5.camel@twc.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.64.88:25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 18:30:33 -0000 -----Original Message-----From: David Boyd To: freebsd-stable@freebsd.org Subject: Regression in pciconf utility in releng/11.0 Date: Wed, 28 Dec 2016 10:14:57 -0500 pciconf -lv em0@pci0:6:0:0: returns the following error: pciconf: cannont parse selector em0:pci0:6:0:0: This is contrary to the man page documentation which specifies that the trailing colon is optional and ignored. I have verified that this worked properly (as documented) in releng/10.3. A diff of pciconf.c between releng/11.0 and releng/10.3 show that the "parsesel" function received a major rewrite. Thanks. If I should submit a PR, just let me know. From owner-freebsd-stable@freebsd.org Wed Jan 11 19:22:59 2017 Return-Path: Delivered-To: freebsd-stable@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 F2C47CAABEE for ; Wed, 11 Jan 2017 19:22:59 +0000 (UTC) (envelope-from jlehen@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 A55B7190D for ; Wed, 11 Jan 2017 19:22:59 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-vk0-x22a.google.com with SMTP id r136so49277211vke.1 for ; Wed, 11 Jan 2017 11:22:59 -0800 (PST) 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=oXHtMTq66CuozTaCs+jptKI7McZaqi90ArCxlFBCySA=; b=eXAW7U3AbNGfL3p4L0/fP8s9trlnzzuCPe8n10ioF5oa0yVxIZWi4ot6fxqi8uLcfF Vc9Igf/upTfA8CrObUbtvufCQo2rzDviNNOZJ1oB0AHBu/HDVGiAAr20GVJuiiB8vbjH J98JM+pF90lanhYcZVyBb8cLXXYjIBy3fdGMC0UrKXFmauVuP8eBJmPuGIthmlW/d1ZX IcU29qJJJRGaUq/EKlKYudDfldSQJbB+I+rkCNfgS5XLIcE7MmhDATQ3VG7zvynRzDhy nzRekOvFYMIIwPnAmOif0On86KFvzuLgJ8hPe8PVkpDpFtIsWNjdpuUsAwWgJcPDVfJ8 Ajyw== 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=oXHtMTq66CuozTaCs+jptKI7McZaqi90ArCxlFBCySA=; b=RslNXbEXOJoPw2VjVWXS4h394YXnozVvDf+hFxVSIVmPd4aUAFvZ/fanzQrKBzEAG0 UekEPK7iwhpPQFEiDAkfWUWE3DaElCNZBTyVj9zRq2qvSyoVCb5mSz35arAWEi2aHO+X syd6W+K3DJBMQUtW35QDPR1lqwJ4j+D6LLA3YGAWjJehcwOLYtsLmcVoCsYn8FP5lXhz hG3zrfqIcYstkjlMI/CpJaNL+vbJnG4Yu6JQwTx8Y1BfRRSddnOscSUPl8pJOLPQGV6g 7DX+jXsxyZL194vdDdGfhB8TZtHYMpt2QnCUFhEnIsCqM/hGcHZeEmNUYEVh+zqZ9gX5 XRwA== X-Gm-Message-State: AIkVDXJ8tweo2mCciV/Npr3QlQaBx7AWlATNWs0MvmF7Pcy8/Xm7U4RyzWRAsm4HZwTZOfJVlbLlf57e2X6UhQ== X-Received: by 10.31.208.2 with SMTP id h2mr4828581vkg.24.1484162578695; Wed, 11 Jan 2017 11:22:58 -0800 (PST) MIME-Version: 1.0 Sender: jlehen@gmail.com Received: by 10.103.33.4 with HTTP; Wed, 11 Jan 2017 11:22:58 -0800 (PST) Received: by 10.103.33.4 with HTTP; Wed, 11 Jan 2017 11:22:58 -0800 (PST) In-Reply-To: References: From: Jeremie Le Hen Date: Wed, 11 Jan 2017 20:22:58 +0100 X-Google-Sender-Auth: JGgkbe2Juvo6V4_SPk-Y8-CglF4 Message-ID: Subject: Can't boot on ZFS -- /boot/zfsloader not found To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 19:23:00 -0000 Hi, I'm in the process of transferring my home server to an Intel NUC. I've zfs send/receive'd the whole pool to the new drive and first followed [ZfsOnGpt] but it fails in the first stage boot loader. The USB keyboard doesn't seem to be recognized so I can't really debug anything. Then I tried both [ZfsInMbrSlice] but it complains that it can't find /boot/zfsloader. Again USB keyboard doesn't work. Both times I've been very careful to install the bootcodes at the right place. 1. Any idea why the USB keyboard doesn't work? 2. Any idea what can be wrong in the setups I tried? How can I debug this? [ZfsOnGpt] https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot [ZfsInMbrSlice] https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition -jlh From owner-freebsd-stable@freebsd.org Wed Jan 11 19:44:07 2017 Return-Path: Delivered-To: freebsd-stable@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 E956CCAB7A1 for ; Wed, 11 Jan 2017 19:44:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wj0-x22e.google.com (mail-wj0-x22e.google.com [IPv6:2a00:1450:400c:c01::22e]) (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 745A210BA for ; Wed, 11 Jan 2017 19:44:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wj0-x22e.google.com with SMTP id i20so109692513wjn.2 for ; Wed, 11 Jan 2017 11:44:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=KdmPqaEJF+BiG93YBXR4mVyMZkOf5ZWMewLPDtDISvo=; b=gslRTjf/lj9xo13VbYqus4J8OMN6JMlzLdJ2Sf7MzDPR33oQoboda8FpI1G42LYDOP RvffHBQ7ByA2feh76m5zPj/wZHbnM8s15HJi/aliHd4dBJGrmJ2u53Y6lo3hnQiYoIaJ q4BGFEO+iMKSz1UFNsExQf/GN4xPHapYZDSHG1QfUjE5tMBk0y17ERDTXjEe+DkMychJ a0ONYVMNWYIMXq5CU1Ls2kG+4MvMI+3yJiNAr2l17FX+tdMjCuy4UnCL/hwYfdrqlXYZ +nxFiNsfHYJz06304xtWowl7kg1Pp1DtPtRarQ6IUX0yrNgHiBydA5cinrSGOInuMiDm Zpsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=KdmPqaEJF+BiG93YBXR4mVyMZkOf5ZWMewLPDtDISvo=; b=gdq4yeprzLUUsUQodoyRfSU16gfccluRkAOidOAUQrcm1ocYcZhHmOgzXLvYp4z4TA BNh0bJWCeAR6sHBV3fG8OUq1JnqoXhVLiKZeeN7NeXMJd6E3sfWHmdaJ6YF3YFiGG7m9 R6O//Rg7ZnS66WQ9rTqOQpzYjuNzXUOss7J8qA8EagA2hQ2+V+hOg0RGRM+jbZw/oNQ4 ajKBK00invxhyTSfPY5RwHp6HU3JiFh51CFPIx6NJTWF2MSCJBO0VzHAqzdzmcD++N1N gAHfRJfIHbZ9EEyIJZSpv56wZjHZS5I5A08dmOpzHFeRo6eYXR4zN5ZFm9uIOVrMa5JC QrFQ== X-Gm-Message-State: AIkVDXJkx8Ct+tqJRBEteRN8f5e2JliZnYeIBQV8uWekwqIorT/yRz+ANSc87wKOTV2FiELG X-Received: by 10.194.147.140 with SMTP id tk12mr1584528wjb.71.1484163845190; Wed, 11 Jan 2017 11:44:05 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id j6sm10039418wjk.25.2017.01.11.11.44.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jan 2017 11:44:04 -0800 (PST) Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: freebsd-stable@freebsd.org References: From: Steven Hartland Message-ID: <17f908e5-728c-c4c3-962d-67edefe8fd6e@multiplay.co.uk> Date: Wed, 11 Jan 2017 19:44:10 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 19:44:08 -0000 As your not at the boot loader stage yet for keyboard enabling legacy USB keyboard / mouse support in BIOS may help. If you see issues with keyboard after the kernel takes over setting hint.ehci.0.disabled=1 may help. If your installing 11.x then the guides boot partition size is out of date and you should use 512K for your freebsd-boot partition. For the GPT version (I've never used MBR one) what actual error do you get? On 11/01/2017 19:22, Jeremie Le Hen wrote: > Hi, > > I'm in the process of transferring my home server to an Intel NUC. I've zfs > send/receive'd the whole pool to the new drive and first followed > [ZfsOnGpt] but it fails in the first stage boot loader. The USB keyboard > doesn't seem to be recognized so I can't really debug anything. > > Then I tried both [ZfsInMbrSlice] > but it complains that it can't find /boot/zfsloader. Again USB keyboard > doesn't work. > > Both times I've been very careful to install the bootcodes at the right > place. > > 1. Any idea why the USB keyboard doesn't work? > 2. Any idea what can be wrong in the setups I tried? How can I debug this? > > [ZfsOnGpt] https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot > [ZfsInMbrSlice] https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > > -jlh > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Wed Jan 11 20:24:28 2017 Return-Path: Delivered-To: freebsd-stable@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 9EDA9CABE0E for ; Wed, 11 Jan 2017 20:24:28 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 67387110F for ; Wed, 11 Jan 2017 20:24:28 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0BKOK4W060105 for ; Wed, 11 Jan 2017 15:24:26 -0500 (EST) (envelope-from george+freebsd@m5p.com) To: FreeBSD Stable Mailing List From: George Mitchell Subject: 10.3-RELEASE-p13 "unsupported file layout" Message-ID: Date: Wed, 11 Jan 2017 15:24:14 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bB9k3Uh6ASc9ovaERa2FpBixCS8M7GnnQ" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 15:24:26 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 20:24:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bB9k3Uh6ASc9ovaERa2FpBixCS8M7GnnQ Content-Type: multipart/mixed; boundary="46jGPM7uSCaoqs4Tm0eP6qbj55BFDj4qR"; protected-headers="v1" From: George Mitchell To: FreeBSD Stable Mailing List Message-ID: Subject: 10.3-RELEASE-p13 "unsupported file layout" --46jGPM7uSCaoqs4Tm0eP6qbj55BFDj4qR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable After today's OpenSSH security message, I did: cd /usr rm -rf obj cd src svn update -r311916 make buildworld After a while, I got to: building shared library libc.so.7 cc (a very long compile line) =2E/libc.so.7: unsupported file layout *** Error code 1 Stop. make[4]: stopped in /usr/src/lib/libc *** Error code 1 Stop. make[3]: stopped in /usr/src *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src freebsd-version -ku 10.3-RELEASE-p13 10.3-RELEASE-p15 I am using a generic kernel, except for using SCHED_4BSD. If it weren't for that, I would just use freebsd-update. Googling suggests that my build tree is somehow mixing up 32 and 64 bit files. (I'm running on an amd64 machine.) How do I get this cleared up? -- George --46jGPM7uSCaoqs4Tm0eP6qbj55BFDj4qR-- --bB9k3Uh6ASc9ovaERa2FpBixCS8M7GnnQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh2lHQACgkQwRES3m+p 4flynBAAtMU0SaZ/VYI876TtgjEbrM2Y9sOMW3juy18pMHHTn3HmtX5RqIzX9CXJ J81SlIiP1OQDz3GiwDlKR8ia8DY/BEri/hvCXN4a9olz/xStyA3RyqflPX6z8oes 4EHWkZS2whT1mZrkwma7182gvADBgF+sPyvK2qVhp1paLoxc+aojU8e24DFFWVPj fA2uWXxe8rDZqquWy+c6lV0EGpeCUa93imF86GMvayqso9hfefxi5+AtzAJEVaDD er51ycNakXxxk2NEb8ZE5bFhS+Ok2HhBVq/5fQv/TR2EUuijAAq15jomJqsE1Nmu XKerS/1lSiPjJ0919ly8vf1MiAXYWmQTtPfuVM4Goerwtk5jhBFyLxVLcw4l9iJJ nSvSonv2qWm1Hp3F3n/ATzZOwrhTimdnO+CNKcfCUtxF1XomeV6TiUmzNUIxHAvA 1bVuawOQPylf4fpZ+FRjTL9tN9/o2I2gc/vpMH11hW8DaMTCG6cZAy3yHz7Y/BkM 9qAaZ0+jeiy/M99UtwWFB8XTChc64jnMlYPrJLgID1ECLGckVtbRD63P3XB9EMOO ijVL10b+7PczAOhSjPqE0ODyw8frAksglgnWD/WElX2KPneNroBMvXsrWnM6M/E2 prUz6oFGZv/fX17ngasDaKmUExy/wvyNYd8OKUmKOri9A9s6s6Q= =BMWd -----END PGP SIGNATURE----- --bB9k3Uh6ASc9ovaERa2FpBixCS8M7GnnQ-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:20:17 2017 Return-Path: Delivered-To: freebsd-stable@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 B59C8CABF2F for ; Wed, 11 Jan 2017 22:20:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wj0-x232.google.com (mail-wj0-x232.google.com [IPv6:2a00:1450:400c:c01::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 4ACCD105B for ; Wed, 11 Jan 2017 22:20:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wj0-x232.google.com with SMTP id ew7so910247wjc.3 for ; Wed, 11 Jan 2017 14:20:17 -0800 (PST) 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=bHUSbFB9yXYKMUZ1qmkwKY8DOPZ+IK0wUqdznXLnTzg=; b=G1q+FUuRGYP2mFdsRQC1WSfvpMO8umAZc5b/SoFlrhno/MDxYsHfaS5KM4ylQ2/sP5 +g5aPfkJ0jCc+3IMHrlJH3r/IaLDLqOxyLdnaWYjhCeIcpe8CJOQk4wAagxf1vU8cRWL IQeUO+kBXBmp+PP0QLJ4eXg2phkZOcOYtkd0kSMZ/zqxtASGa82zBSE1BRwZ7SbOh/nK ggvCR5KBwThh4hrxaKUte568gs0amrR/Hvx+SNl2Bg+JFeLWue2CRtpd2ZOmOVLpwthh yHXrKe+74yIo+6JtK+9c0YHimaeV+wXZuHM5I0gLvoZd0azf96TAXtiwXbb0IloEwOfv 01hw== 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=bHUSbFB9yXYKMUZ1qmkwKY8DOPZ+IK0wUqdznXLnTzg=; b=IvCrnSj3LUqK00wBHkI6bEba04doqpdEZeur0cLwbOBTo7D/gB0PrUXkSgeJiO/QxH v48uiELNAhbpUYsd4wuIJQShrITsgAWUj7CXfNayLlTqTrDUM4SvUZJH9f7UA1xWkiCA yfguMYLzLrmvU4QZwA43djT6+3oju6YePms+tp2q+FeXdg/OkLNX3yu945pSDUd+VKs9 O8+re/eXTnQQsCM1vmpcurQgygKfv+hHV1KkKeKGzwBrSM/eT8MFXplEIw6D3BJY9Kiu dF0qJttVEeTgGSwr7xmcgxtSdWn+8po5TXmSFRjhGDlkbCk+IczxKkERmJXXEyo8RTqz L3PQ== X-Gm-Message-State: AIkVDXKfAOJCjylzY0tJBi/yJrpN+EvsylYVi3rCaPWiHtp4Sr8v1jOJ4KDsLkCTAd3D8alYrT+7UEz4x13Ddg== X-Received: by 10.194.93.37 with SMTP id cr5mr6455867wjb.95.1484173215513; Wed, 11 Jan 2017 14:20:15 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.51.78 with HTTP; Wed, 11 Jan 2017 14:20:14 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Wed, 11 Jan 2017 14:20:14 -0800 X-Google-Sender-Auth: lqhbXz9-txNeno2pETMQUjaPw_U Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: George Mitchell Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:20:17 -0000 On Wed, Jan 11, 2017 at 12:24 PM, George Mitchell wrote: > After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > *** Error code 1 > > Stop. > make[4]: stopped in /usr/src/lib/libc > *** Error code 1 > > Stop. > make[3]: stopped in /usr/src > *** Error code 1 > > Stop. > make[2]: stopped in /usr/src > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > freebsd-version -ku > 10.3-RELEASE-p13 > 10.3-RELEASE-p15 > > I am using a generic kernel, except for using SCHED_4BSD. If it > weren't for that, I would just use freebsd-update. > > Googling suggests that my build tree is somehow mixing up 32 and 64 > bit files. (I'm running on an amd64 machine.) How do I get this > cleared up? -- George > While I have no suggestions about the error building libc, your statement that you can't use freebsd-update due to your use of a custom kernel is incorrect. This is a common misconception and, in cases of very limited disk space, may be true, it is rare. It is helped by the fact that the man page makes no mention of how to so this. (You do still need to build a new kernel if the update does, indeed, touch the kernel.) All you need is a GENERIC kernel in /boot/GENERIC. You can either build it or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCustom = Kernels with FreeBSD 9.X and Later=E2=80=9D for details on downloading a GENERIC kernel. Before any upgrade, major or minor, you might wat to re-reas that section. Once the GENERIC kernel is in /boot, you may use freebsd-update and, if the GENERIC kernel is not updated, you're good to go. If it is, you will need to build and install a new custom kernel and reboot. Since most security patches don't touch the kernel, this is usually not needed. I believe that the 10.3 kernel was last touched in p11. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Wed Jan 11 22:25:28 2017 Return-Path: Delivered-To: freebsd-stable@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 19D33CAB320 for ; Wed, 11 Jan 2017 22:25:28 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (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 D66DF15C7 for ; Wed, 11 Jan 2017 22:25:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::7049:d69d:d97f:c66f] (unknown [IPv6:2001:7b8:3a7:0:7049:d69d:d97f:c66f]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 477FD254F6; Wed, 11 Jan 2017 23:25:25 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_D0845F83-0A51-4353-8C6B-F8B8BCAF8D1C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" From: Dimitry Andric In-Reply-To: Date: Wed, 11 Jan 2017 23:25:14 +0100 Cc: FreeBSD Stable Mailing List Message-Id: References: To: George Mitchell X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:25:28 -0000 --Apple-Mail=_D0845F83-0A51-4353-8C6B-F8B8BCAF8D1C Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 11 Jan 2017, at 21:24, George Mitchell wrote: > > After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj Hmm, not sure if it is wise to completely remove the /usr/obj directory. Did you re-create it afterwards? > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout If things went correctly, the libc.so.7 file should be in /usr/obj/usr/src/lib/libc. If so, can you post the output of: file /usr/obj/usr/src/lib/libc/libc.so.7 readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 -Dimitry --Apple-Mail=_D0845F83-0A51-4353-8C6B-F8B8BCAF8D1C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlh2sNQACgkQsF6jCi4glqPJvwCfSCOpS98xFJlxLTmlcen75gi4 c8cAn1NbubgaLJ7mrN0HnX7mtyR2VR9w =N1Cd -----END PGP SIGNATURE----- --Apple-Mail=_D0845F83-0A51-4353-8C6B-F8B8BCAF8D1C-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:35:18 2017 Return-Path: Delivered-To: freebsd-stable@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 08F62CABB23 for ; Wed, 11 Jan 2017 22:35:18 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ABA3C1380; Wed, 11 Jan 2017 22:35:17 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0BMZA1e061045; Wed, 11 Jan 2017 17:35:15 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: Dimitry Andric References: Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> Date: Wed, 11 Jan 2017 17:35:03 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p65Dfls28m7JxvOuFVTIlfoh9c3COGx0v" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 17:35:16 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:35:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --p65Dfls28m7JxvOuFVTIlfoh9c3COGx0v Content-Type: multipart/mixed; boundary="c1Ci3SdwEE4Wd41GPcMGURVJFDctX0d4c"; protected-headers="v1" From: George Mitchell To: Dimitry Andric Cc: FreeBSD Stable Mailing List Message-ID: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: In-Reply-To: --c1Ci3SdwEE4Wd41GPcMGURVJFDctX0d4c Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:25, Dimitry Andric wrote: > On 11 Jan 2017, at 21:24, George Mitchell wrot= e: >> >> After today's OpenSSH security message, I did: >> >> cd /usr >> rm -rf obj >=20 > Hmm, not sure if it is wise to completely remove the /usr/obj directory= =2E > Did you re-create it afterwards? In the past, "make buildworld" has taken care of that (as far as I could tell). >=20 >=20 >> cd src >> svn update -r311916 >> make buildworld >> >> After a while, I got to: >> >> building shared library libc.so.7 >> cc (a very long compile line) >> ./libc.so.7: unsupported file layout >=20 > If things went correctly, the libc.so.7 file should be in > /usr/obj/usr/src/lib/libc. If so, can you post the output of: >=20 > file /usr/obj/usr/src/lib/libc/libc.so.7 > readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 >=20 > -Dimitry >=20 root@sullivan:/usr/src # file /usr/obj/usr/src/lib/libc/libc.so.7 /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped root@sullivan:/usr/src # readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 ELF Header: Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - FreeBSD ABI Version: 0 Type: DYN (Shared object file) Machine: Advanced Micro Devices X86-64 Version: 0x1 Entry point address: 0x3aee0 Start of program headers: 64 (bytes into file) Start of section headers: 1644696 (bytes into file) Flags: 0x0 Size of this header: 64 (bytes) Size of program headers: 56 (bytes) Number of program headers: 6 Size of section headers: 64 (bytes) Number of section headers: 40 Section header string table index: 37 That isn't the only libc.so.7 in my build tree, though: /usr/obj/usr/src/tmp/lib/libc.so.7: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped /usr/obj/lib32/usr/src/lib/libc/libc.so.7: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped --c1Ci3SdwEE4Wd41GPcMGURVJFDctX0d4c-- --p65Dfls28m7JxvOuFVTIlfoh9c3COGx0v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh2sxcACgkQwRES3m+p 4flHGhAApS1CxNDvDJFYTUeH5CCXl3qbaDdRFEosBBfIVhSnGb6ZuGwVMhDo7hH8 T3c0qTlF/Gm6jA2GGqC8yH2K/ebdbO8Cu2+BmQBnA4sCWrDoqJwVnVKIKnILjRw7 UZY/0XO3sVcUBGPizqxwhjagin1llAV62yVWM3mPp0g9iodErazlEobgYL6NtjrL LWRdhe3mCoEjH4im3Hi4ff7TmW3eqKlk0BFyTsT5txe998K++kjYOVlwFjo3N8kV vnX70aXdW61p3CTBdY5odkj1rieogFGHyaUsfPiNjujTDgkVv2vDiEHWl3B5JKJT SncOXVYL1GiNGeIMDSZ7DXmEDbKBcFRhao8NpW3GC6r3ZOMoIQmYG/5YplrUcJJE zdgSbyfsLOBphwl2EOmRbXwDZO8QuYJH73/qL0LqBMGDy17MUR+txiqY0iU8qou7 2hlvuC9kfpggasXg6JTCfPNC2fUUeAbF4vRwOuaedxOcVMMLdOiuryXPQGnyKdTG HLqAcmFj8jLLIfqu1HnJIoin0v8u88/QmONPA1G2J7dHDe0psON+C2njbVy+HBth jZE0p41uPOdlh5oj6POCmWOUltxH7RAXsB7vZY2CUQR5BdAzybr4Y08WjgQs5MuZ 9Kif4HZjUFNP92Sf/CbsgoQzvyOMx8JZSTHMOBG6vs6ajE+GGnA= =yjvH -----END PGP SIGNATURE----- --p65Dfls28m7JxvOuFVTIlfoh9c3COGx0v-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:40:11 2017 Return-Path: Delivered-To: freebsd-stable@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 3C26DCABE74 for ; Wed, 11 Jan 2017 22:40:11 +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 C19371811 for ; Wed, 11 Jan 2017 22:40:10 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::7049:d69d:d97f:c66f] (unknown [IPv6:2001:7b8:3a7:0:7049:d69d:d97f:c66f]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1CB6D25543; Wed, 11 Jan 2017 23:40:08 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_83952FD6-D0D9-43A7-9849-662618F5B091"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" From: Dimitry Andric In-Reply-To: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> Date: Wed, 11 Jan 2017 23:40:07 +0100 Cc: FreeBSD Stable Mailing List Message-Id: <3095417A-E707-42C2-A3DA-F7E07AFED9F8@FreeBSD.org> References: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:40:11 -0000 --Apple-Mail=_83952FD6-D0D9-43A7-9849-662618F5B091 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=windows-1252 On 11 Jan 2017, at 23:35, George Mitchell wrote: > > On 01/11/17 17:25, Dimitry Andric wrote: >> On 11 Jan 2017, at 21:24, George Mitchell wrote: ... >>> building shared library libc.so.7 >>> cc (a very long compile line) >>> ./libc.so.7: unsupported file layout >> >> If things went correctly, the libc.so.7 file should be in >> /usr/obj/usr/src/lib/libc. If so, can you post the output of: >> >> file /usr/obj/usr/src/lib/libc/libc.so.7 >> readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 >> >> -Dimitry >> > root@sullivan:/usr/src # file /usr/obj/usr/src/lib/libc/libc.so.7 > /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared object, > x86-64, version 1 (FreeBSD), dynamically linked, not stripped > root@sullivan:/usr/src # readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 > ELF Header: > Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 > Class: ELF64 > Data: 2's complement, little endian > Version: 1 (current) > OS/ABI: UNIX - FreeBSD > ABI Version: 0 > Type: DYN (Shared object file) > Machine: Advanced Micro Devices X86-64 > Version: 0x1 > Entry point address: 0x3aee0 > Start of program headers: 64 (bytes into file) > Start of section headers: 1644696 (bytes into file) > Flags: 0x0 > Size of this header: 64 (bytes) > Size of program headers: 56 (bytes) > Number of program headers: 6 > Size of section headers: 64 (bytes) > Number of section headers: 40 > Section header string table index: 37 > > That isn't the only libc.so.7 in my build tree, though: > > /usr/obj/usr/src/tmp/lib/libc.so.7: ELF 64-bit LSB shared object, > x86-64, version 1 (FreeBSD), dynamically linked, not stripped > /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared object, > x86-64, version 1 (FreeBSD), dynamically linked, not stripped > /usr/obj/lib32/usr/src/lib/libc/libc.so.7: ELF 32-bit LSB shared object, > Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped Hm, that all looks perfectly normal, supposing that you are on amd64. Maybe it's the stripping that fails? Do you have STRIP defined in your environment, or make.conf? -Dimitry --Apple-Mail=_83952FD6-D0D9-43A7-9849-662618F5B091 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlh2tEcACgkQsF6jCi4glqMt6QCgpZjlSMtEvSPpf72sb2BheqZG EEAAnR1KCUxkUT/RrRu+885S6g5PXnNf =XyRj -----END PGP SIGNATURE----- --Apple-Mail=_83952FD6-D0D9-43A7-9849-662618F5B091-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:46:23 2017 Return-Path: Delivered-To: freebsd-stable@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 9A99BCAB30C for ; Wed, 11 Jan 2017 22:46:23 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A4FF1FFD for ; Wed, 11 Jan 2017 22:46:23 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0BMkGvP061134; Wed, 11 Jan 2017 17:46:21 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: Kevin Oberman References: Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: Date: Wed, 11 Jan 2017 17:46:09 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 17:46:22 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:46:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm Content-Type: multipart/mixed; boundary="UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1"; protected-headers="v1" From: George Mitchell To: Kevin Oberman Cc: FreeBSD Stable Mailing List Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: In-Reply-To: --UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:20, Kevin Oberman wrote: > [...] >=20 > While I have no suggestions about the error building libc, your stateme= nt > that you can't use freebsd-update due to your use of a custom kernel is= > incorrect. This is a common misconception and, in cases of very limited= > disk space, may be true, it is rare. It is helped by the fact that the = man > page makes no mention of how to so this. (You do still need to build a = new > kernel if the update does, indeed, touch the kernel.) >=20 > All you need is a GENERIC kernel in /boot/GENERIC. You can either build= it > or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCus= tom Kernels > with FreeBSD 9.X and Later=E2=80=9D > > for details on downloading a GENERIC kernel. Before any upgrade, major = or > minor, you might wat to re-reas that section. >=20 > Once the GENERIC kernel is in /boot, you may use freebsd-update and, if= the > GENERIC kernel is not updated, you're good to go. If it is, you will ne= ed > to build and install a new custom kernel and reboot. Since most securit= y > patches don't touch the kernel, this is usually not needed. I believe t= hat > the 10.3 kernel was last touched in p11. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" >=20 Thanks, I'll try that the next time I have a chance. When I naively tried a straight "freebsd-update" a few months ago, of course it overwrote my SCHED_4BSD kernel with a SCHED_ULE one. -- George --UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1-- --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh2tbEACgkQwRES3m+p 4flClw//cILXOVZq3Tz+PoVThfnCP6mMSiw3W+gj/6g9b432vMIPugwsOt02Egh7 hMvnKLL0jIo/oW4GveqMuOiqv/lSKUIUFYGC3JRH8qmL4u1c3UKiAU6sdFZ8L9+b PCKeHD4RsudlL3obpg40RqekzLCRawU8q/K7Zwayhuvfe7zHT30PBWP/dfrCAFq1 E3x0q/+Aqey2KdUCkqOVEmPz+tY8tZlLNPAf5D8S/e06h7pfjVtbP01c2K0ejg5S fi0EFBQ5gV9lS3/PfCpdRLmps+F5afwWdXJDtA4bWR9/Lt5ug3MC0rPWECldOzLs E6fIpXEWKOKaqbbXFB4RrQcIKYX+3FJOvtfP51ZHGNa+M5fKim8b2iQjbGoOKRK8 xmMWWH5LvYVpMaUFcqYxPya9WkngP+dpD9AKN5zc4UkkwrYOqcFEzA3edkmcfIXl ad7WlT60Ql41IUUKA979/7fWdpxLp78Hl22p9D3VrS+bH+gnHfx9QHKdo+zulik+ /hrGKHh6GQHZv96tDwZA8gSv+ylqNNjpFxGqfdleGS9ApNFS3vzSLQv0302047iG +bliKxv0iRLb7YFJkQITLxcbsIYDt7pQLlU30jiTPf6ByPjryvCThZ/XYicfNxBH VIYykrWxdsD1oWK3eHNCG7AQ+kTSrSyTvzbubnnR1U1IeciCNc0= =847g -----END PGP SIGNATURE----- --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:47:53 2017 Return-Path: Delivered-To: freebsd-stable@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 06850CAB44F for ; Wed, 11 Jan 2017 22:47:53 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C515E1162; Wed, 11 Jan 2017 22:47:52 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0BMljSd061145; Wed, 11 Jan 2017 17:47:50 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: Dimitry Andric References: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> <3095417A-E707-42C2-A3DA-F7E07AFED9F8@FreeBSD.org> Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: Date: Wed, 11 Jan 2017 17:47:45 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <3095417A-E707-42C2-A3DA-F7E07AFED9F8@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qVsBkILSVmh9TNiVfb0e1EuLhIRg9E8PX" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 17:47:51 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:47:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qVsBkILSVmh9TNiVfb0e1EuLhIRg9E8PX Content-Type: multipart/mixed; boundary="onBMKSNXevSKFUTKBGhIik725joXWFqPC"; protected-headers="v1" From: George Mitchell To: Dimitry Andric Cc: FreeBSD Stable Mailing List Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: <63bc650f-60d3-4f24-0c5f-4b02f602e21d@m5p.com> <3095417A-E707-42C2-A3DA-F7E07AFED9F8@FreeBSD.org> In-Reply-To: <3095417A-E707-42C2-A3DA-F7E07AFED9F8@FreeBSD.org> --onBMKSNXevSKFUTKBGhIik725joXWFqPC Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:40, Dimitry Andric wrote: > On 11 Jan 2017, at 23:35, George Mitchell wrot= e: >> >> On 01/11/17 17:25, Dimitry Andric wrote: >>> On 11 Jan 2017, at 21:24, George Mitchell wr= ote: > ... >>>> building shared library libc.so.7 >>>> cc (a very long compile line) >>>> ./libc.so.7: unsupported file layout >>> >>> If things went correctly, the libc.so.7 file should be in >>> /usr/obj/usr/src/lib/libc. If so, can you post the output of: >>> >>> file /usr/obj/usr/src/lib/libc/libc.so.7 >>> readelf -h /usr/obj/usr/src/lib/libc/libc.so.7 >>> >>> -Dimitry >>> >> root@sullivan:/usr/src # file /usr/obj/usr/src/lib/libc/libc.so.7 >> /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared object, >> x86-64, version 1 (FreeBSD), dynamically linked, not stripped >> root@sullivan:/usr/src # readelf -h /usr/obj/usr/src/lib/libc/libc.so.= 7 >> ELF Header: >> Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 >> Class: ELF64 >> Data: 2's complement, little endian >> Version: 1 (current) >> OS/ABI: UNIX - FreeBSD >> ABI Version: 0 >> Type: DYN (Shared object file) >> Machine: Advanced Micro Devices X86-64 >> Version: 0x1 >> Entry point address: 0x3aee0 >> Start of program headers: 64 (bytes into file) >> Start of section headers: 1644696 (bytes into file) >> Flags: 0x0 >> Size of this header: 64 (bytes) >> Size of program headers: 56 (bytes) >> Number of program headers: 6 >> Size of section headers: 64 (bytes) >> Number of section headers: 40 >> Section header string table index: 37 >> >> That isn't the only libc.so.7 in my build tree, though: >> >> /usr/obj/usr/src/tmp/lib/libc.so.7: ELF 64-bit LSB shared objec= t, >> x86-64, version 1 (FreeBSD), dynamically linked, not stripped >> /usr/obj/usr/src/lib/libc/libc.so.7: ELF 64-bit LSB shared objec= t, >> x86-64, version 1 (FreeBSD), dynamically linked, not stripped >> /usr/obj/lib32/usr/src/lib/libc/libc.so.7: ELF 32-bit LSB shared objec= t, >> Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped >=20 > Hm, that all looks perfectly normal, supposing that you are on amd64. > Maybe it's the stripping that fails? Do you have STRIP defined in your= > environment, or make.conf? >=20 > -Dimitry >=20 No, STRIP is not defined anywhere. -- George --onBMKSNXevSKFUTKBGhIik725joXWFqPC-- --qVsBkILSVmh9TNiVfb0e1EuLhIRg9E8PX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh2thEACgkQwRES3m+p 4fnuxg//d2px9DSSLAeUFNjjadl49tS6/0+nHrwCvtd+aQwBg0XvX4STOZWrPhCE +QruVdzHrXfSq7FrdKcoCXhLqJVJxO7m6NHmsLvSnYzZgY7heZRWlW7XkfcUdO2t 16smzNtxMw7nub4k2T/FcB9bP/VeAgBYHfzFOliDViPALfYyW1h8ctJQHD31hFpf C9VG1D83Xbq7l4+SW9VIa1NW0dT32pNWaK/aFvG4xgMRyt9fQaNThzI/YA5kSgqM 0sz0+wFDIWik6pthiT6tGRL41CrUcLms0dOK+QH0dTeNF4UBpT4cQyZFBZ4cY9un 4bU8RtTEOHQsMTYRIAZajyljpjUKwHe/ivEV9b6OVqdSX2Otqre2Bc+Yubs/zVQg v64c0ryka1DA0fD6CG7QzuTrRX0Zo1KE2X9iSirwxiLBnkyY44lSFz4TThpc6Ij2 FUctnfDN4KAu4NoBkZICdvcTYxpe/vo7nc4sUe+bJDD+L91JhKaZ3t3qz0x3O3a8 5hJpXItS+gqe/jXVt/oeH8FwdNBqcnpaBLAUHcwVXqZEY5omheMhkmCZ7LdpaJ4R NlbnD/OPS4jP01PJlPfF/aRKxc+u8N96MArc5r5c1aKFjMYOntfLmP3ZBXvBlPnb LjmxJYvXMsHOgPvjhj/AnkXtDq5y5u0FmrOZrzqSgszyG4ElQSE= =sTFg -----END PGP SIGNATURE----- --qVsBkILSVmh9TNiVfb0e1EuLhIRg9E8PX-- From owner-freebsd-stable@freebsd.org Wed Jan 11 22:58:25 2017 Return-Path: Delivered-To: freebsd-stable@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 F0B0ECABA14 for ; Wed, 11 Jan 2017 22:58:25 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 AA5E81C40 for ; Wed, 11 Jan 2017 22:58:25 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-ua0-x236.google.com with SMTP id 35so2028927uak.1 for ; Wed, 11 Jan 2017 14:58:25 -0800 (PST) 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=H1GS29bFm75sf9d5e3koHhAIdNGnqc6Z+Zd38Lmgqg4=; b=vgMjUq5aaUjiHfmsR0jmWzZ/2XCijbQ+mVXUQde+3HkESMS6MrF7hWZD07M4BJkLiO 5EWyt1eKsXDfCnZ4uEpIKlLoLoR6ScVLL4HtjjiDEBGZ8GHXeX+idkrzWlruf7ZXeVUu 7enFG60wTEFYL2TztZmNT97b7I1h0fKwQCzFXWCimIF16T4D0x6Aq88BpbssD4WidzeL iFY9WCIKJKbKVj2WfPKmJ8Nh6hPsLqA4NSKhpoKwncMlCPQeSx8lqi8L7E09dSiWfs9k AYtD4ATHQJES98HuxrKJ5ftqXf/elzOKDWtASYAgm2ybnULoij9yyzMGeslcgH/wBnoD W1kw== 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=H1GS29bFm75sf9d5e3koHhAIdNGnqc6Z+Zd38Lmgqg4=; b=bONcVdTWV7HhVgn1Bt/NaY0qhCp2QMypccoAx6HsKBUu4WFU5zb8Br1sygjqUE+pJj 6d9IL6ScxK9JAcdUgiYMUePlRM9QLW05zsfYMJOlAoD3EhDvkAez5LnlhvxZdWbCW5Tb VB+tngKFNE00xkIil5SPPCh9cUhPMQhheD35agq/ZXz6dgrsjryebdi0bUxHDhTWQrVQ UU0O3rteaIcnjeeyKNSIYcd5GWuCB+6iv8SN8xnQGKoxr+LhENN0gi4CyapGMJTBIHJY J7WuJE3TPB8WLqky40tIHkv5xqomxt047M9uEFgtU5/1OMDUsl4UX07PpoWuqe9HD9CQ FsCA== X-Gm-Message-State: AIkVDXIwu/82MRU4muKx1kxb/fJaOkOYkxbBnVR/qgmDkEdUcAAGztZ+/u7UN4mrLOXRbWCqgeF5i47UT4fvHQ== X-Received: by 10.176.3.44 with SMTP id 41mr6204661uat.157.1484175504846; Wed, 11 Jan 2017 14:58:24 -0800 (PST) MIME-Version: 1.0 Sender: jlehen@gmail.com Received: by 10.103.33.4 with HTTP; Wed, 11 Jan 2017 14:58:24 -0800 (PST) From: Jeremie Le Hen Date: Wed, 11 Jan 2017 23:58:24 +0100 X-Google-Sender-Auth: VniOFoxrdnKkqMXU0A0JD_lcW3g Message-ID: Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: freebsd-stable@freebsd.org, Steven Hartland Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 22:58:26 -0000 (Sorry I had to copy-paste this email from the archives to a new thread, because I'm not subscribed to -stable@. Would you mind cc:ing me next time please?) > As your not at the boot loader stage yet for keyboard enabling legacy > USB keyboard / mouse support in BIOS may help. That worked, thanks for the tip. > If you see issues with keyboard after the kernel takes over setting > hint.ehci.0.disabled=1 may help. > > If your installing 11.x then the guides boot partition size is out of > date and you should use 512K for your freebsd-boot partition. Oh, really? I'll update it once I'll have figure it all out. That's weird though because /boot/gptzfsboot is less than 90 KB. > For the GPT version (I've never used MBR one) what actual error do you get? When I just start up the NUC, I get: """ \Can't find /boot/zfsloader FreeBSD/x86 boot Default: zroot:/boot/kernel/kernel boot: \ Can't find /boot/kernel/kernel """ I though it was the first stage boot loader, but it may be the second stage. -jlh > > On 11/01/2017 19:22, Jeremie Le Hen wrote: > > Hi, > > > > I'm in the process of transferring my home server to an Intel NUC. I've zfs > > send/receive'd the whole pool to the new drive and first followed > > [ZfsOnGpt] but it fails in the first stage boot loader. The USB keyboard > > doesn't seem to be recognized so I can't really debug anything. > > > > Then I tried both [ZfsInMbrSlice] > > but it complains that it can't find /boot/zfsloader. Again USB keyboard > > doesn't work. > > > > Both times I've been very careful to install the bootcodes at the right > > place. > > > > 1. Any idea why the USB keyboard doesn't work? > > 2. Any idea what can be wrong in the setups I tried? How can I debug this? > > > > [ZfsOnGpt] https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot > > [ZfsInMbrSlice] https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition > > > > -jlh > > _______________________________________________ > > freebsd-stable at freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" -- Jeremie Le Hen jlh@FreeBSD.org From owner-freebsd-stable@freebsd.org Thu Jan 12 00:12:34 2017 Return-Path: Delivered-To: freebsd-stable@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 2B21DCAB583 for ; Thu, 12 Jan 2017 00:12:34 +0000 (UTC) (envelope-from karly@kipshouse.net) Received: from mgmt.ironboy.kipshouse.net (ironboy.kipshouse.net [IPv6:2001:470:835a:4242::42]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mx.kipshouse.net", Issuer "Starfield Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD6C41755 for ; Thu, 12 Jan 2017 00:12:33 +0000 (UTC) (envelope-from karly@kipshouse.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kipshouse.org; i=@kipshouse.org; q=dns/txt; s=kh-ss; t=1484179953; x=1515715953; h=date:from:to:subject:message-id:mime-version; z=Date:=20Wed,=2011=20Jan=202017=2015:47:37=20-0800|From: =20Karl=20Young=20|To:=20FreeBSD=20S table=20Mailing=20List=20 |Subject:=20NFS=20and=20amd=20on=20older=20FreeBSD |Message-ID:=20<20170111234737.GK26386@mailboy.kipshouse. net>|MIME-Version:=201.0; bh=TtZGTrLfN1GbZ+GejAn3RolRTQg5Wx5zITRkGDq/USg=; b=aPXZ704qrBjj4hLDDLNxpEQK6x8EWE97ypTIcZM9B8XrDZNYbkp37JFU /GqJbewmzj7xRKrxllLEIpg1S6Kz3iKI3ewsqa0r9+IIqIt7exctstLVs C956hf6wY/x1DWpQ079Hx2pcb74u9WUBXctAU2uSRkieYn8ODBwzUx2NT tkKyBqa6R1GfyFw0UkG+tkWKiygfqjtpkwI0qw6HY+ZX9IFU8KHMM2uoY L/oCJficNzI/L7AOYAG3gXmLsy0W5rc9yYOIxyo+f8no1k27C+dUp7EEW b0w4A2n66mYRgMTd8yNdD6Rli3WjjFrlyHvlVYHJWVpebqXLrPx3TBlQl g==; Authentication-Results: d2.ironport.kipshouse.net; dkim=none (message not signed) header.i=none; spf=None smtp.pra=karly@kipshouse.org; spf=None smtp.mailfrom=karly@kipshouse.net; spf=None smtp.helo=postmaster@mailboy.kipshouse.net Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.org) identity=pra; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.org"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.net) identity=mailfrom; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.net"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of postmaster@mailboy.kipshouse.net) identity=helo; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="postmaster@mailboy.kipshouse.net"; x-conformance=sidf_compatible X-SBRS: None X-MID: 231196 X-RemoteIP: 2001:470:835a:1010::26 X-RemoteHost: 2001:470:835a:1010::26, mailboypriv.kipshouse.net X-IronPort-AV: E=McAfee;i="5700,7163,8405"; a="231196" Received: from mailboypriv.kipshouse.net (HELO mailboy.kipshouse.net) ([IPv6:2001:470:835a:1010::26]) by d2.ironport.kipshouse.net with ESMTP; 11 Jan 2017 16:12:32 -0800 Received: by mailboy.kipshouse.net (Postfix, from userid 500) id A1F7D43F97; Wed, 11 Jan 2017 15:47:37 -0800 (PST) Date: Wed, 11 Jan 2017 15:47:37 -0800 From: Karl Young To: FreeBSD Stable Mailing List Subject: NFS and amd on older FreeBSD Message-ID: <20170111234737.GK26386@mailboy.kipshouse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.kipshouse.org/karly X-Work-URL: http://www.cisco.com/ X-Disclaimer: My opinions do not necessarily represent those of my employer. User-Agent: Mutt/1.5.20 (2009-12-10) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 00:12:34 -0000 I inherited a lab that has a few hundred hosts running FreeBSD 7.2. These hosts run test scripts that access files that are stored on FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS On the 7.2 hosts, I can see the exported directory: $ showmount -e 6.3-host Exports list on 6.3-host /data Everyone And access it with amd $ ls -l /net/6-3.host/data drwxr-xr-x 5 root wheel 512 Jun 4 2009 git drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's old, but it's the best I can do for now). I export the /data directory on the 9.3 system, and I can see it on my 7.2 hosts. $ showmount -e 9.3-host Exports list on 9.3-host: /data Everyone But I can't automount it: $ ls -l /net/9.3-host/data ls: /net/9.3-host/data: No such file or directory If I manually mount the exported directory, it works: $ sudo mount -t nfs 9.3-host:/data /mnt/data/ $ mount | grep nfs 9.3-host:/data on /mnt/data (nfs) $ ls -l /mnt/data total 4 drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 I've spent some time on Google, but haven't found a solution. I realize these are very old versions, but I'm not in a position to upgrade them right now. My last resort will be to use /etc/fstab to do the NFS mount, but I'd rather avoid that if I can. Thanks for any pointers on how to resolve this. -karl From owner-freebsd-stable@freebsd.org Thu Jan 12 00:32:54 2017 Return-Path: Delivered-To: freebsd-stable@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 5A836CABF9A for ; Thu, 12 Jan 2017 00:32:54 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wj0-x22f.google.com (mail-wj0-x22f.google.com [IPv6:2a00:1450:400c:c01::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 DB6A314A4 for ; Thu, 12 Jan 2017 00:32:53 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wj0-x22f.google.com with SMTP id tn15so2284797wjb.1 for ; Wed, 11 Jan 2017 16:32:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=4iQ02s4+b+ygrL5d0jSHK7yIk5GO4OCpqKXaZz3qH+s=; b=SvBeJMNfPeJmSSvGUXiPek0OKYkbrh6ORskG9fjCx56tDuQgMCDQoE3sHbAl5MPkUG RGqLYCIYR0/UKSNNpv/ku7W2F75fs0cxTts9NGwSC6vmohSG33Jhxu4RnvxbWi1N6c4W y7uV4xlk/gqVsmLFVi+4O1BFweVGeRIl7ucQkr1n6WGjKIl+iUJ4ysnzBy1GhltiV+nl 2l0PWva/tMUHslPZ/GIbpZGCObeZhX2tDo3JwKFhfv5ZbWy14RksLYLx6ljKdheyonGx kN0cZC6Qh4bSfRmBEy4ZblaCammRn8XMoLWYXPnePOEvOyrp5ZsaP0JkXUFaWgEc42VJ 2B2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=4iQ02s4+b+ygrL5d0jSHK7yIk5GO4OCpqKXaZz3qH+s=; b=KJxxGWgIXfC7RcIM5mgJPuphgLA9xA9T3p55pWbk6MzGcR/d7vOGTuXRF07qmBkLpO kNVoxCsxpIkGMZj1XyoCoISKUVbL2Ax3T3RDByZon36QvnCugkxLZyCjwmqjLO43sadZ zGZP06JKIfdVUSi1keIg8tVa79Qsqww2ge4ZLdQLl45DbVT4perBwOZ3yLKBsTyWgZH3 NkOxWsvLaPczcyijS4rurt+zuRcWOPQ4WyLCfab3voZCnJpaReBorWd/Lj3liQm/Lu/q sRI3sOpnCQP8L400D0WuR7vKuurINenpC0FA4eSEeGlsz38nwOCmQDgra+HA9kS85cuI 3hHQ== X-Gm-Message-State: AIkVDXIyTcnj4+KYvcAPMihw88EdyaV3ADhZLzSNgvylAFtJgIsF5zAeXO6Fe4c8NEP7e9Xm X-Received: by 10.194.179.198 with SMTP id di6mr8274245wjc.148.1484181172295; Wed, 11 Jan 2017 16:32:52 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id a13sm473783wma.0.2017.01.11.16.32.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jan 2017 16:32:51 -0800 (PST) Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: Jeremie Le Hen , freebsd-stable@freebsd.org References: From: Steven Hartland Message-ID: Date: Thu, 12 Jan 2017 00:32:57 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 00:32:54 -0000 On 11/01/2017 22:58, Jeremie Le Hen wrote: > (Sorry I had to copy-paste this email from the archives to a new > thread, because I'm not subscribed to -stable@. Would you mind cc:ing > me next time please?) > >> As your not at the boot loader stage yet for keyboard enabling legacy >> USB keyboard / mouse support in BIOS may help. > That worked, thanks for the tip. > > >> If you see issues with keyboard after the kernel takes over setting >> hint.ehci.0.disabled=1 may help. >> >> If your installing 11.x then the guides boot partition size is out of >> date and you should use 512K for your freebsd-boot partition. > Oh, really? I'll update it once I'll have figure it all out. That's > weird though because /boot/gptzfsboot is less than 90 KB. 11.x du -h /boot/gptzfsboot 97K /boot/gptzfsboot 12.x du -h /boot/gptzfsboot 113K /boot/gptzfsboot The reason I'd recommend 512k for boot is to provide room for expansion moving forward, as repartitioning to upgrade is a scary / hard thing to do. Remember it wasn't long ago when it was well under 64k and that's what was recommend, its not like with disk sizes these days you'll miss the extra 384k ;-) > > >> For the GPT version (I've never used MBR one) what actual error do you get? > When I just start up the NUC, I get: > """ > \Can't find /boot/zfsloader > > FreeBSD/x86 boot > Default: zroot:/boot/kernel/kernel > boot: > \ > Can't find /boot/kernel/kernel > """ > > I though it was the first stage boot loader, but it may be the second stage. Boot to a live cd, I'd recommend mfsbsd, and make sure the boot loader was written to ALL boot disks correctly e.g. if you have a mirrored pool with ada0 and ada1: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 If this doesn't help the output from gpart show, uname -a and zpool status would also be helpful. This is all assuming standard BIOS mode and not UEFI which is done differently. > > -jlh > >> On 11/01/2017 19:22, Jeremie Le Hen wrote: >>> Hi, >>> >>> I'm in the process of transferring my home server to an Intel NUC. I've zfs >>> send/receive'd the whole pool to the new drive and first followed >>> [ZfsOnGpt] but it fails in the first stage boot loader. The USB keyboard >>> doesn't seem to be recognized so I can't really debug anything. >>> >>> Then I tried both [ZfsInMbrSlice] >>> but it complains that it can't find /boot/zfsloader. Again USB keyboard >>> doesn't work. >>> >>> Both times I've been very careful to install the bootcodes at the right >>> place. >>> >>> 1. Any idea why the USB keyboard doesn't work? >>> 2. Any idea what can be wrong in the setups I tried? How can I debug this? >>> >>> [ZfsOnGpt] https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot >>> [ZfsInMbrSlice] https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >>> >>> -jlh >>> _______________________________________________ >>> freebsd-stable at freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" > From owner-freebsd-stable@freebsd.org Thu Jan 12 01:08:00 2017 Return-Path: Delivered-To: freebsd-stable@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 57603CA9F9E for ; Thu, 12 Jan 2017 01:08:00 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2408B1E55 for ; Thu, 12 Jan 2017 01:08:00 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0C17qXB062006 for ; Wed, 11 Jan 2017 20:07:58 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: FreeBSD Stable Mailing List References: From: George Mitchell Message-ID: <7a468a4f-00f4-69c0-a678-fe376edf9b86@m5p.com> Date: Wed, 11 Jan 2017 20:07:45 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="W9rEqj01orslKIdOVSKDoAiuimj7x10qI" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 20:07:58 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 01:08:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --W9rEqj01orslKIdOVSKDoAiuimj7x10qI Content-Type: multipart/mixed; boundary="4rWtQqgd0rwjNQi8mwuOau0Vi1pK68HIP"; protected-headers="v1" From: George Mitchell To: FreeBSD Stable Mailing List Message-ID: <7a468a4f-00f4-69c0-a678-fe376edf9b86@m5p.com> Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: In-Reply-To: --4rWtQqgd0rwjNQi8mwuOau0Vi1pK68HIP Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 15:24, George Mitchell wrote: > After today's OpenSSH security message, I did: >=20 > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld >=20 > After a while, I got to: >=20 > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > *** Error code 1 >=20 > Stop. > make[4]: stopped in /usr/src/lib/libc > *** Error code 1 >=20 > Stop. > make[3]: stopped in /usr/src > *** Error code 1 >=20 > Stop. > make[2]: stopped in /usr/src > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/src > *** Error code 1 >=20 > Stop. > make: stopped in /usr/src >=20 > freebsd-version -ku > 10.3-RELEASE-p13 > 10.3-RELEASE-p15 >=20 > I am using a generic kernel, except for using SCHED_4BSD. If it > weren't for that, I would just use freebsd-update. >=20 > Googling suggests that my build tree is somehow mixing up 32 and 64 > bit files. (I'm running on an amd64 machine.) How do I get this > cleared up? -- George >=20 For the sake of completeness, here's the complete build log that terminated in the above error: http://m5p.com/typescript.xz -- George --4rWtQqgd0rwjNQi8mwuOau0Vi1pK68HIP-- --W9rEqj01orslKIdOVSKDoAiuimj7x10qI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh21ugACgkQwRES3m+p 4fm7fQ//b6aI/e7JK4n05p0qR6yqva4rK8yZcbq2zO+8BpRH3FectbnJhBN0d1Ri kV5SB0ixJoKDgPv1RNH18VJgl5CLYNEFUPDO+nCZg3LqyrrNTL2QjA23cMRPzFq4 SEUMSXLPpUhhnofENn8uhj+mWbDmxWNSU+yDEDSlAzhbRJo+9aAXAv21/5nM+wRv lccHwu18T1jzDfEVMK0YczZTRVph6w9U5EwKnHEJGBGKQotMidg3AlR8f9WTTwTX XqPETDZ23gCvAuHApC84S37vaBInYE8mUDbJ+ty8LcQ9COpE6COlITMr5NVMlad3 6QXER7nL+ZNyGhOuAOPPST1WPLO2prbXfXTnKRSBfWeVxjpmHpLr32Qqvm4UZZz/ Es3wsqj/db7SWJ874sNESzVPZniHWOQsDIlmcWtK48pxc58uZU0D8eNWWSHmueDt +IpGV4PbAI3nztdTTqJg70CwOZ/swiHSvzUXBgRft4QnxtJCY3EIwvp04EI0H+92 AytdX2g/7An6D+pLOsCzFfFgKPojUedFwG3t6dzz8H1RBo4KFVc8PyRb8KRId4z+ zNzpKK09fpzJ8qwuSpEwXeQRyH2Iwjs0Dh6KjKLLPLHXIWzehLtmxMgjTHbeu55a UYt/YVFq5DtfGJYrhzmuLTjmBoK+rOZYsVvCyPeODW1cGnHUHnM= =ZNrM -----END PGP SIGNATURE----- --W9rEqj01orslKIdOVSKDoAiuimj7x10qI-- From owner-freebsd-stable@freebsd.org Thu Jan 12 04:24:33 2017 Return-Path: Delivered-To: freebsd-stable@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 DA431CAC487 for ; Thu, 12 Jan 2017 04:24:33 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A10FB1AD8 for ; Thu, 12 Jan 2017 04:24:33 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0C4OPhP063106; Wed, 11 Jan 2017 23:24:30 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: Kevin Oberman References: Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: Date: Wed, 11 Jan 2017 23:24:18 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 23:24:32 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 04:24:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3 Content-Type: multipart/mixed; boundary="fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM"; protected-headers="v1" From: George Mitchell To: Kevin Oberman Cc: FreeBSD Stable Mailing List Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: In-Reply-To: --fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:46, George Mitchell wrote: > On 01/11/17 17:20, Kevin Oberman wrote: >> [...] >> >> While I have no suggestions about the error building libc, your statem= ent >> that you can't use freebsd-update due to your use of a custom kernel i= s >> incorrect. This is a common misconception and, in cases of very limite= d >> disk space, may be true, it is rare. It is helped by the fact that the= man >> page makes no mention of how to so this. (You do still need to build a= new >> kernel if the update does, indeed, touch the kernel.) >> >> All you need is a GENERIC kernel in /boot/GENERIC. You can either buil= d it >> or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCu= stom Kernels >> with FreeBSD 9.X and Later=E2=80=9D >> >> for details on downloading a GENERIC kernel. Before any upgrade, major= or >> minor, you might wat to re-reas that section. >> >> Once the GENERIC kernel is in /boot, you may use freebsd-update and, i= f the >> GENERIC kernel is not updated, you're good to go. If it is, you will n= eed >> to build and install a new custom kernel and reboot. Since most securi= ty >> patches don't touch the kernel, this is usually not needed. I believe = that >> the 10.3 kernel was last touched in p11. >> -- >> Kevin Oberman, Part time kid herder and retired Network Engineer >> E-mail: rkoberman@gmail.com >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.o= rg" >> > Thanks, I'll try that the next time I have a chance. When I naively > tried a straight "freebsd-update" a few months ago, of course it > overwrote my SCHED_4BSD kernel with a SCHED_ULE one. -- George >=20 Just to refresh my memory of what happened a few months ago, I tried the following experiment. I copied my current modified kernel: rsync -av /boot/kernel/ /boot/my.kernel/ Then with my modified kernel still in place, I said: freebsd-update fetch freebsd-update install With not a qualm in the world, freebsd-update installed a fresh SCHED_ULE kernel in /boot. (Happily, it did save my current kernel in /boot/kernel.old.) That's what happened last year, too. Why didn't freebsd-update notice that I had a modified kernel and at least notify me that something funky was going on? -- George --fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM-- --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh3BPkACgkQwRES3m+p 4flmiA/+LaZs3cktQtS6WxkZFeK/nw51YARZ7JxmB6qw8A1mBERgTgr6bjJ7G21t GoID3dwm6q4I1hC86pd/JGSjVpmf8MDpz3BxgbzTJ+1L6okIHarIhLtlHo7d6Ozv ll/Yex6Biw54HZcA4hM0xuFWSlBZ5G79MY1UMsb66c869fiv7sf2frezYw/GC7tw ZPZ3PLb/sCyfvqFKrwDo2L0X65pzAb9STHXadCuTaTMk6S+daecNzmQAIJw2DbSG wLKHVg40KLks7bGF51WudDWniudCqo7h401nqSUWHPdHaxOa1wslLCZiRBDLsFiR 5OLNeFeDnag4Xv4R9tFRSoLmlMiuKczYLhxXLLOnfENYDLPidcPIo4sZMcz1wWea sywDmtMRZn0U2KLnGG6G8flrQcgAZPfeOfg7wrAj9waPnYwBzNFfivAj52uhdTME HP4kpyoGkNO6m8hgHDJbYetdSkwO0cyM8ygLhyyCcTOhSRwOMGDc1WfMEB6OS/b7 SVw5bnCbO7Lr8nv6rqfsDTd8ke6CLLO50IByikmW1uPQTif3KR+erHZYqsiO7Qml kEhjYREI1V8X5ERwRBFwmij1ZndUN0OlBdxrzDuZFRD9Kg/ErKOdqJCObumk2vol XeJ+Il+60ATvaqXib6zYQsviwmlCl3b9sfG3zCYFeNq+vzIUzIs= =N5e+ -----END PGP SIGNATURE----- --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3-- From owner-freebsd-stable@freebsd.org Thu Jan 12 05:07:04 2017 Return-Path: Delivered-To: freebsd-stable@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 5D725CACEE0 for ; Thu, 12 Jan 2017 05:07:04 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wj0-x229.google.com (mail-wj0-x229.google.com [IPv6:2a00:1450:400c:c01::229]) (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 E40C91D96 for ; Thu, 12 Jan 2017 05:07:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wj0-x229.google.com with SMTP id i20so4547999wjn.2 for ; Wed, 11 Jan 2017 21:07:03 -0800 (PST) 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=mgdyuugAvjtic5G81MzcpavJeVxv7FblzJZzqGeXHCI=; b=Trm181Q00YSAGC0VV1jZks/4IDi1PlWahf5ei5pWMm+EHkw+3XGvGeA0da1hh+7neW An8vy1Oq7AKyz6F/0AyxVwFoOcwCE30r1HrZzfy+wpQoldf6NWGRqGE+9QbfLPC7jvOM aX0i0b/arhb6gVuzKrqfOeCzu2EXLhM6fR+e52a/zuPlhC5BRarzrH+CjtalVCZvqdIy pONQsMh+INl0icCCB137b1JOOC8yW+fVSrDtD6Day3uVPJ912q1zIw75Gj5fKpFnd6eg hY8RC4ZaOzZRscME6DCLltCRGBhnL1NxwuBDDLQ2HT/Mettd3fU37/VawOnkrjCAMOng r5DA== 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=mgdyuugAvjtic5G81MzcpavJeVxv7FblzJZzqGeXHCI=; b=hH5V9wR84udy9SYck8OeG2kgrCXGzNtSi1lX4ubCypxWvvQgYO/TGTv4NGuhd88q2O IvSJ76UPkqup/xRST4Usd5gSiDfJ73KUOC/H6ipZ+yIvzX5f4WBG6dxlVUZVn3eWFzUL k7wu/Ndqx9z6O8JNw4DwAuLdZ+kSPvqdDReciM/rkFBPuLWE+pwRRP4idpxJ89AfPzoH xT83TLQ3K2vLIIkGjwBZWUZSVBVQ+c/0xVHSQSm2rE/xEGfh40kY9a5BSbilIr+yB5qz c0yHii6Zlfg6JAtaeo7ngcpXEhhUA/zkpl/EX2Jz3cL7PvTjOPzK/JQCNyIleU3FYCBF GB5A== X-Gm-Message-State: AIkVDXKy9Z42bPhWrU2gWwZsJ2fYbW8LYefkiLBnXyqZQ+LQh9IX3KNP29RDuQ5tsjB2/E7PjQBHbb8qf3630g== X-Received: by 10.194.122.231 with SMTP id lv7mr3084419wjb.231.1484197621585; Wed, 11 Jan 2017 21:07:01 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.51.78 with HTTP; Wed, 11 Jan 2017 21:07:01 -0800 (PST) In-Reply-To: References: From: Kevin Oberman Date: Wed, 11 Jan 2017 21:07:01 -0800 X-Google-Sender-Auth: VT9szv4gbvpUf4Lhimlpc7XS9cg Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: George Mitchell Cc: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 05:07:04 -0000 On Wed, Jan 11, 2017 at 8:24 PM, George Mitchell wrote: > On 01/11/17 17:46, George Mitchell wrote: > > On 01/11/17 17:20, Kevin Oberman wrote: > >> [...] > >> > >> While I have no suggestions about the error building libc, your > statement > >> that you can't use freebsd-update due to your use of a custom kernel i= s > >> incorrect. This is a common misconception and, in cases of very limite= d > >> disk space, may be true, it is rare. It is helped by the fact that the > man > >> page makes no mention of how to so this. (You do still need to build a > new > >> kernel if the update does, indeed, touch the kernel.) > >> > >> All you need is a GENERIC kernel in /boot/GENERIC. You can either buil= d > it > >> or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCu= stom > Kernels > >> with FreeBSD 9.X and Later=E2=80=9D > >> handbook/updating-upgrading-freebsdupdate.html#freebsd- > update-custom-kernel-9x> > >> for details on downloading a GENERIC kernel. Before any upgrade, major > or > >> minor, you might wat to re-reas that section. > >> > >> Once the GENERIC kernel is in /boot, you may use freebsd-update and, i= f > the > >> GENERIC kernel is not updated, you're good to go. If it is, you will > need > >> to build and install a new custom kernel and reboot. Since most securi= ty > >> patches don't touch the kernel, this is usually not needed. I believe > that > >> the 10.3 kernel was last touched in p11. > >> -- > >> Kevin Oberman, Part time kid herder and retired Network Engineer > >> E-mail: rkoberman@gmail.com > >> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@ > freebsd.org" > >> > > Thanks, I'll try that the next time I have a chance. When I naively > > tried a straight "freebsd-update" a few months ago, of course it > > overwrote my SCHED_4BSD kernel with a SCHED_ULE one. -- George > > > Just to refresh my memory of what happened a few months ago, I tried > the following experiment. I copied my current modified kernel: > > rsync -av /boot/kernel/ /boot/my.kernel/ > > Then with my modified kernel still in place, I said: > > freebsd-update fetch > freebsd-update install > > With not a qualm in the world, freebsd-update installed a fresh > SCHED_ULE kernel in /boot. (Happily, it did save my current kernel > in /boot/kernel.old.) That's what happened last year, too. Why > didn't freebsd-update notice that I had a modified kernel and at > least notify me that something funky was going on? -- George I'm a bit surprised that there was no message about the kernel being non-GENERIC, but I've never tried. The key is the presence of /boot/GENERIC. If it is present, the kernel in /boot/kernel is left untouched and /boot/GENERIC is updated to the new version. If /boot/GENERIC does not exist, then the update is performed on /boot/kernel/kernel. (N.B. Kernel modules are always updated when or if needed!) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Thu Jan 12 07:55:30 2017 Return-Path: Delivered-To: freebsd-stable@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 E0E00CAB72D for ; Thu, 12 Jan 2017 07:55:30 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 A0E4D1D0D for ; Thu, 12 Jan 2017 07:55:30 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from imac.bs.cs.huji.ac.il ([132.65.179.42]) by kabab.cs.huji.ac.il with esmtp id 1cRa8R-000I9n-9z; Thu, 12 Jan 2017 09:49:23 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: NFS and amd on older FreeBSD From: Daniel Braniss In-Reply-To: <20170111234737.GK26386@mailboy.kipshouse.net> Date: Thu, 12 Jan 2017 09:49:22 +0200 Cc: FreeBSD Stable Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170111234737.GK26386@mailboy.kipshouse.net> To: Karl Young X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 07:55:31 -0000 > On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >=20 > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > These hosts run test scripts that access files that are stored on > FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS >=20 >=20 > On the 7.2 hosts, I can see the exported directory: >=20 > $ showmount -e 6.3-host > Exports list on 6.3-host > /data Everyone >=20 > And access it with amd >=20 > $ ls -l /net/6-3.host/data >=20 > drwxr-xr-x 5 root wheel 512 Jun 4 2009 git > drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home >=20 > I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's > old, but it's the best I can do for now). >=20 > I export the /data directory on the 9.3 system, and I can see it on my > 7.2 hosts. >=20 > $ showmount -e 9.3-host > Exports list on 9.3-host: > /data Everyone >=20 > But I can't automount it: >=20 > $ ls -l /net/9.3-host/data > ls: /net/9.3-host/data: No such file or directory >=20 > If I manually mount the exported directory, it works: >=20 > $ sudo mount -t nfs 9.3-host:/data /mnt/data/ > $ mount | grep nfs > 9.3-host:/data on /mnt/data (nfs) >=20 > $ ls -l /mnt/data > total 4 > drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 >=20 > I've spent some time on Google, but haven't found a solution. I = realize > these are very old versions, but I'm not in a position to upgrade them > right now. My last resort will be to use /etc/fstab to do the NFS > mount, but I'd rather avoid that if I can. >=20 > Thanks for any pointers on how to resolve this. >=20 > -karl >=20 >=20 if you changed the export file on the server after you tried to mount in = on the client, and will not realise this, if that=E2=80=99s the case, usually rebooting = the client helps. my .5 cents danny >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Jan 12 08:06:13 2017 Return-Path: Delivered-To: freebsd-stable@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 C5D71CABC29 for ; Thu, 12 Jan 2017 08:06:13 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from v1.leiden.byshenk.net (v1.leiden.byshenk.net [37.97.209.179]) by mx1.freebsd.org (Postfix) with ESMTP id 862CD11C9 for ; Thu, 12 Jan 2017 08:06:13 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: by v1.leiden.byshenk.net (Postfix, from userid 1002) id 267237594C; Thu, 12 Jan 2017 08:58:16 +0100 (CET) Date: Thu, 12 Jan 2017 08:58:16 +0100 From: Greg Byshenk To: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD Message-ID: <20170112075816.GQ731@v1.leiden.byshenk.net> References: <20170111234737.GK26386@mailboy.kipshouse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170111234737.GK26386@mailboy.kipshouse.net> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 08:06:13 -0000 On Wed, Jan 11, 2017 at 03:47:37PM -0800, Karl Young wrote: > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > These hosts run test scripts that access files that are stored on > FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS > > [...] > > $ showmount -e 9.3-host > Exports list on 9.3-host: > /data Everyone > > But I can't automount it: > > $ ls -l /net/9.3-host/data > ls: /net/9.3-host/data: No such file or directory > > If I manually mount the exported directory, it works: > > $ sudo mount -t nfs 9.3-host:/data /mnt/data/ > $ mount | grep nfs > 9.3-host:/data on /mnt/data (nfs) > > $ ls -l /mnt/data > total 4 > drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 > > I've spent some time on Google, but haven't found a solution. I realize > these are very old versions, but I'm not in a position to upgrade them > right now. My last resort will be to use /etc/fstab to do the NFS > mount, but I'd rather avoid that if I can. If you can mount the share manually, there is almost certainly nothing wrong with the server. Based on the error ("No such file or directory"), I would recommend checking your amd config on the client. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@freebsd.org Thu Jan 12 08:25:07 2017 Return-Path: Delivered-To: freebsd-stable@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 2E265CAA3BB for ; Thu, 12 Jan 2017 08:25:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 E16F31318 for ; Thu, 12 Jan 2017 08:25:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from imac.bs.cs.huji.ac.il ([132.65.179.42]) by kabab.cs.huji.ac.il with esmtp id 1cRagx-000IqD-PQ; Thu, 12 Jan 2017 10:25:04 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: NFS and amd on older FreeBSD From: Daniel Braniss In-Reply-To: Date: Thu, 12 Jan 2017 10:25:03 +0200 Cc: FreeBSD Stable Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170111234737.GK26386@mailboy.kipshouse.net> To: Karl Young X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 08:25:07 -0000 > On 12 Jan 2017, at 9:49 AM, Daniel Braniss = wrote: >=20 >=20 >> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >>=20 >> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. >> These hosts run test scripts that access files that are stored on >> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS >>=20 >>=20 >> On the 7.2 hosts, I can see the exported directory: >>=20 >> $ showmount -e 6.3-host >> Exports list on 6.3-host >> /data Everyone >>=20 >> And access it with amd >>=20 >> $ ls -l /net/6-3.host/data >>=20 >> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >> drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home >>=20 >> I'm trying to retire the 6.3 host and replace it with 9.3 (I know = it's >> old, but it's the best I can do for now). >>=20 >> I export the /data directory on the 9.3 system, and I can see it on = my >> 7.2 hosts. >>=20 >> $ showmount -e 9.3-host >> Exports list on 9.3-host: >> /data Everyone >>=20 >> But I can't automount it: >>=20 >> $ ls -l /net/9.3-host/data >> ls: /net/9.3-host/data: No such file or directory >>=20 >> If I manually mount the exported directory, it works: >>=20 >> $ sudo mount -t nfs 9.3-host:/data /mnt/data/ >> $ mount | grep nfs >> 9.3-host:/data on /mnt/data (nfs) >>=20 >> $ ls -l /mnt/data >> total 4 >> drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 >>=20 >> I've spent some time on Google, but haven't found a solution. I = realize >> these are very old versions, but I'm not in a position to upgrade = them >> right now. My last resort will be to use /etc/fstab to do the NFS >> mount, but I'd rather avoid that if I can. >>=20 >> Thanks for any pointers on how to resolve this. >>=20 >> -karl >>=20 >>=20 >=20 > if you changed the export file on the server after you tried to mount = in on the client, > and will not realise this, if that=E2=80=99s the case, usually = rebooting the client helps. >=20 s/and/amd/ ^%$# hate spell checkers > my .5 cents >=20 > danny >=20 >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Jan 12 19:25:05 2017 Return-Path: Delivered-To: freebsd-stable@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 7214BCACE2B for ; Thu, 12 Jan 2017 19:25:05 +0000 (UTC) (envelope-from karly@kipshouse.net) Received: from mgmt.ironboy.kipshouse.net (ironboy.kipshouse.net [IPv6:2001:470:835a:4242::42]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mx.kipshouse.net", Issuer "Starfield Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 23B0F1474 for ; Thu, 12 Jan 2017 19:25:05 +0000 (UTC) (envelope-from karly@kipshouse.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kipshouse.org; i=@kipshouse.org; q=dns/txt; s=kh-ss; t=1484249105; x=1515785105; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; z=Date:=20Thu,=2012=20Jan=202017=2011:00:07=20-0800|From: =20Karl=20Young=20|To:=20Greg=20Bysh enk=20|Cc:=20FreeBSD=20Stable=20Mail ing=20List=20|Subject:=20Re: =20NFS=20and=20amd=20on=20older=20FreeBSD|Message-ID:=20< 20170112190007.GQ26386@mailboy.kipshouse.net>|References: =20<20170111234737.GK26386@mailboy.kipshouse.net>=0D=0A =20<20170112075816.GQ731@v1.leiden.byshenk.net> |MIME-Version:=201.0|In-Reply-To:=20<20170112075816.GQ731 @v1.leiden.byshenk.net>; bh=VAgmLtTyA40TU9bu6N7V42krto7i4URF5AFDNK+hcVA=; b=Pi96VG0zKyJ27sryjAfs1zgdQVD41c9e1FGC1UkPSzMXVGicZKzDGya8 11JIhgJyl2UkGnRCiNBhkMDegJJRS2Ew++Io064rfAoQeOar9UBcnjVvC 5ELt2uK98O9fvlyUyndPwvzL8oEG6S4YfBgBE3yeV5KZPs8M/QEwNibis rEXOOEOqfdlEoteTKyxFgwfaVNpuhovfkU+jNNEOvky+axsXIuShySUOq GdyEqvYVAfzm2Oz5k+TCa575Nwn6nMUox+prwtSBci/PY+x5cumRIWWvx FJGtombXAe6ltn1sKkDHSbMwWoEWV2p21/P2C3JNcNbQ89ba9GMVPFTfD Q==; Authentication-Results: d2.ironport.kipshouse.net; dkim=none (message not signed) header.i=none; spf=None smtp.pra=karly@kipshouse.org; spf=None smtp.mailfrom=karly@kipshouse.net; spf=None smtp.helo=postmaster@mailboy.kipshouse.net Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.org) identity=pra; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.org"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.net) identity=mailfrom; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.net"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of postmaster@mailboy.kipshouse.net) identity=helo; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="postmaster@mailboy.kipshouse.net"; x-conformance=sidf_compatible X-SBRS: None X-MID: 231327 X-RemoteIP: 2001:470:835a:1010::26 X-RemoteHost: 2001:470:835a:1010::26, mailboypriv.kipshouse.net X-IronPort-AV: E=McAfee;i="5700,7163,8406"; a="231327" Received: from mailboypriv.kipshouse.net (HELO mailboy.kipshouse.net) ([IPv6:2001:470:835a:1010::26]) by d2.ironport.kipshouse.net with ESMTP; 12 Jan 2017 11:25:04 -0800 Received: by mailboy.kipshouse.net (Postfix, from userid 500) id EE35B43F91; Thu, 12 Jan 2017 11:00:07 -0800 (PST) Date: Thu, 12 Jan 2017 11:00:07 -0800 From: Karl Young To: Greg Byshenk Cc: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD Message-ID: <20170112190007.GQ26386@mailboy.kipshouse.net> References: <20170111234737.GK26386@mailboy.kipshouse.net> <20170112075816.GQ731@v1.leiden.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170112075816.GQ731@v1.leiden.byshenk.net> X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.kipshouse.org/karly X-Work-URL: http://www.cisco.com/ X-Disclaimer: My opinions do not necessarily represent those of my employer. User-Agent: Mutt/1.5.20 (2009-12-10) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 19:25:05 -0000 Thanks Greg One correction. The new server is FreeBSD 9.2, not 9.3. Replies below Greg Byshenk(freebsd@byshenk.net)@2017.01.12 08:58:16 +0100: > On Wed, Jan 11, 2017 at 03:47:37PM -0800, Karl Young wrote: > > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > > These hosts run test scripts that access files that are stored on > > FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS > > > > [...] > > > > $ showmount -e 9.3-host > > Exports list on 9.3-host: > > /data Everyone > > > > But I can't automount it: > > > > $ ls -l /net/9.3-host/data > > ls: /net/9.3-host/data: No such file or directory > > > > If I manually mount the exported directory, it works: > > > > $ sudo mount -t nfs 9.3-host:/data /mnt/data/ > > $ mount | grep nfs > > 9.3-host:/data on /mnt/data (nfs) > > > > $ ls -l /mnt/data > > total 4 > > drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 > > > > I've spent some time on Google, but haven't found a solution. I realize > > these are very old versions, but I'm not in a position to upgrade them > > right now. My last resort will be to use /etc/fstab to do the NFS > > mount, but I'd rather avoid that if I can. > > If you can mount the share manually, there is almost > certainly nothing wrong with the server. Based on the > error ("No such file or directory"), I would recommend > checking your amd config on the client. > Yes, that makes sense, but I'm using the same client in both cases. In rc.conf on client, I have: nfs_reserved_port_only="YES" nfs_client_enable="YES" amd_enable="YES" And ps shows the amd process started with these flags: /usr/sbin/amd -p -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map amd.map is the default $ cat /etc/amd.map # $FreeBSD: src/etc/amd.map,v 1.10.8.1 2009/04/15 03:14:26 kensmith Exp # $ # /defaults type:=host;fs:=${autodir}/${rhost}/host;rhost:=${key} * opts:=rw,grpid,resvport,vers=3,proto=tcp,nosuid,nodev This is the same default amd.map as 9.2. Another data point: I see the same behavior with a 9.2 client: I can automount a share from my 6.3 server, but not from the 9.2 server. Thanks -karl > > -- > greg byshenk - gbyshenk@byshenk.net - Leiden, NL > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Jan 12 19:26:25 2017 Return-Path: Delivered-To: freebsd-stable@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 09FE2CACF97 for ; Thu, 12 Jan 2017 19:26:25 +0000 (UTC) (envelope-from karly@kipshouse.net) Received: from mgmt.ironboy.kipshouse.net (ironboy.kipshouse.net [IPv6:2001:470:835a:4242::42]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mx.kipshouse.net", Issuer "Starfield Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9532C1608 for ; Thu, 12 Jan 2017 19:26:24 +0000 (UTC) (envelope-from karly@kipshouse.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kipshouse.org; i=@kipshouse.org; q=dns/txt; s=kh-ss; t=1484249184; x=1515785184; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; z=Date:=20Thu,=2012=20Jan=202017=2011:01:27=20-0800|From: =20Karl=20Young=20|To:=20Daniel=20Br aniss=20|Cc:=20FreeBSD=20Stable=20Ma iling=20List=20|Subject:=20Re :=20NFS=20and=20amd=20on=20older=20FreeBSD|Message-ID:=20 <20170112190125.GR26386@mailboy.kipshouse.net> |References:=20<20170111234737.GK26386@mailboy.kipshouse. net>=0D=0A=20=0D=0A=20|MIME-Version:=201.0 |Content-Transfer-Encoding:=208bit|In-Reply-To:=20; bh=3uoDVK18Kc+L8YYMHopVNhaPLbTiqw8Z4Wvp9V5J/0s=; b=XktvWRf8T/K6QOU55f4mS1JfOIpGDNH5Q81gifn4cictalW9L14xswwx SroeWH/QYvR5vIWX4LtOVHTxqE0hp4LZeHmEjDAeERNapmOeyENE7qtZa TCpnbip3Pd+Gj7H5mvH0CrUE8a7NwVJRFBBlE5LEXMm1tiVOOSTbJMWGs dh5u2C3ZUNByu7an3/0f8GG8lJHAZ8dCE2bo3AOBQ1t5xDULMe83Nu2Ff ojkLDM8LoUnWWHN5rFNA7lL43UnvgDBD1+cVlCJ6oC1OzKqRvjjnTyQmW gGMolxswHar4rUgNVNhMqYgT5r/p3w+dGpfOnvUS/AsxoVdSBjA0C8NNu Q==; Authentication-Results: d2.ironport.kipshouse.net; dkim=none (message not signed) header.i=none; spf=None smtp.pra=karly@kipshouse.org; spf=None smtp.mailfrom=karly@kipshouse.net; spf=None smtp.helo=postmaster@mailboy.kipshouse.net Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.org) identity=pra; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.org"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.net) identity=mailfrom; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.net"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of postmaster@mailboy.kipshouse.net) identity=helo; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="postmaster@mailboy.kipshouse.net"; x-conformance=sidf_compatible X-SBRS: None X-MID: 231329 X-RemoteIP: 2001:470:835a:1010::26 X-RemoteHost: 2001:470:835a:1010::26, mailboypriv.kipshouse.net X-IronPort-AV: E=McAfee;i="5700,7163,8406"; a="231329" Received: from mailboypriv.kipshouse.net (HELO mailboy.kipshouse.net) ([IPv6:2001:470:835a:1010::26]) by d2.ironport.kipshouse.net with ESMTP; 12 Jan 2017 11:26:24 -0800 Received: by mailboy.kipshouse.net (Postfix, from userid 500) id 7CCAD43F97; Thu, 12 Jan 2017 11:01:27 -0800 (PST) Date: Thu, 12 Jan 2017 11:01:27 -0800 From: Karl Young To: Daniel Braniss Cc: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD Message-ID: <20170112190125.GR26386@mailboy.kipshouse.net> References: <20170111234737.GK26386@mailboy.kipshouse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.kipshouse.org/karly X-Work-URL: http://www.cisco.com/ X-Disclaimer: My opinions do not necessarily represent those of my employer. User-Agent: Mutt/1.5.20 (2009-12-10) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 19:26:25 -0000 Daniel Braniss(danny@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: > > > On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: > > > > > >> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: > >> > >> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > >> These hosts run test scripts that access files that are stored on > >> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS > >> > >> > >> On the 7.2 hosts, I can see the exported directory: > >> > >> $ showmount -e 6.3-host > >> Exports list on 6.3-host > >> /data Everyone > >> > >> And access it with amd > >> > >> $ ls -l /net/6-3.host/data > >> > >> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git > >> drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home > >> > >> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's > >> old, but it's the best I can do for now). > >> > >> I export the /data directory on the 9.3 system, and I can see it on my > >> 7.2 hosts. > >> > >> $ showmount -e 9.3-host > >> Exports list on 9.3-host: > >> /data Everyone > >> > >> But I can't automount it: > >> > >> $ ls -l /net/9.3-host/data > >> ls: /net/9.3-host/data: No such file or directory > >> > >> If I manually mount the exported directory, it works: > >> > >> $ sudo mount -t nfs 9.3-host:/data /mnt/data/ > >> $ mount | grep nfs > >> 9.3-host:/data on /mnt/data (nfs) > >> > >> $ ls -l /mnt/data > >> total 4 > >> drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 > >> > >> I've spent some time on Google, but haven't found a solution. I realize > >> these are very old versions, but I'm not in a position to upgrade them > >> right now. My last resort will be to use /etc/fstab to do the NFS > >> mount, but I'd rather avoid that if I can. > >> > >> Thanks for any pointers on how to resolve this. > >> > >> -karl > >> > >> > > > > if you changed the export file on the server after you tried to mount in on the client, > > and will not realise this, if that’s the case, usually rebooting the client helps. > > > s/and/amd/ ^%$# hate spell checkers > Thanks Danny I did try rebooting the client (and server) multiple times to no avail. -karl > > my .5 cents > > > > danny > > > >> > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Thu Jan 12 20:42:49 2017 Return-Path: Delivered-To: freebsd-stable@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 D7137CAD7CE for ; Thu, 12 Jan 2017 20:42:49 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (www2.alogis.com [212.184.102.7]) (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 6992513CA for ; Thu, 12 Jan 2017 20:42:48 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from msx3.exchange.alogis.com (msxcn2.exchange.alogis.com [10.1.1.22]) by alogis.com (8.13.4/8.13.1) with ESMTP id v0CKgMcI084643; Thu, 12 Jan 2017 21:42:22 +0100 (CET) (envelope-from Holger.Kipp@alogis.com) Received: from MSX3.exchange.alogis.com ([10.1.1.26]) by msxcn2.exchange.alogis.com ([fe80::11b6:f5c4:b8ee:4a89%15]) with mapi id 14.03.0279.002; Thu, 12 Jan 2017 21:42:22 +0100 From: Holger Kipp To: Karl Young CC: Daniel Braniss , FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD Thread-Topic: NFS and amd on older FreeBSD Thread-Index: AQHSbGjPiOyv47BQlES3tXFaVDN/X6E0ZzEAgAAJ+ICAALHPgIAALPXB Date: Thu, 12 Jan 2017 20:42:21 +0000 Message-ID: <742E8981-90FD-4F5D-AB72-D241F3D11305@alogis.com> References: <20170111234737.GK26386@mailboy.kipshouse.net> , <20170112190125.GR26386@mailboy.kipshouse.net> In-Reply-To: <20170112190125.GR26386@mailboy.kipshouse.net> Accept-Language: de-DE, en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 20:42:49 -0000 Dear Karl, > On 12 Jan 2017, at 20:29, Karl Young wrote: >=20 > Daniel Braniss(danny@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >>=20 >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: >>>=20 >>>=20 >>>> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >>>>=20 >>>> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. >>>> These hosts run test scripts that access files that are stored on >>>> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS >>>>=20 >>>>=20 >>>> On the 7.2 hosts, I can see the exported directory: >>>>=20 >>>> $ showmount -e 6.3-host >>>> Exports list on 6.3-host >>>> /data Everyone >>>>=20 >>>> And access it with amd >>>>=20 >>>> $ ls -l /net/6-3.host/data >>>>=20 >>>> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >>>> drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home >>>>=20 >>>> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's >>>> old, but it's the best I can do for now). >>>>=20 >>>> I export the /data directory on the 9.3 system, and I can see it on my >>>> 7.2 hosts. >>>>=20 >>>> $ showmount -e 9.3-host >>>> Exports list on 9.3-host: >>>> /data Everyone >>>>=20 >>>> But I can't automount it: >>>>=20 >>>> $ ls -l /net/9.3-host/data >>>> ls: /net/9.3-host/data: No such file or directory >>>>=20 >>>> If I manually mount the exported directory, it works: >>>>=20 >>>> $ sudo mount -t nfs 9.3-host:/data /mnt/data/ >>>> $ mount | grep nfs >>>> 9.3-host:/data on /mnt/data (nfs) >>>>=20 >>>> $ ls -l /mnt/data >>>> total 4 >>>> drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 >>>>=20 >>>> I've spent some time on Google, but haven't found a solution. I reali= ze >>>> these are very old versions, but I'm not in a position to upgrade them >>>> right now. My last resort will be to use /etc/fstab to do the NFS >>>> mount, but I'd rather avoid that if I can. >>>>=20 >>>> Thanks for any pointers on how to resolve this. >>>>=20 >>>> -karl >>>>=20 >>>>=20 >>>=20 >>> if you changed the export file on the server after you tried to mount i= n on the client, >>> and will not realise this, if that=92s the case, usually rebooting the = client helps. >>>=20 >> s/and/amd/ ^%$# hate spell checkers >>=20 >=20 > Thanks Danny >=20 > I did try rebooting the client (and server) multiple times to no avail. >=20 > -karl I'm not sure if this is related, but afaik FreeBSD up to 8.x used oldNFS by= default. Are you using option -o for nfsd on your 9.3 nfs Server to force = using old NFS? It is just a guess of mine, I'm usually not working much with nfs. Best regards, Holger= From owner-freebsd-stable@freebsd.org Thu Jan 12 21:12:24 2017 Return-Path: Delivered-To: freebsd-stable@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 24CD8CAC29D for ; Thu, 12 Jan 2017 21:12:24 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: from mail-vk0-x241.google.com (mail-vk0-x241.google.com [IPv6:2607:f8b0:400c:c05::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 D33A811C3 for ; Thu, 12 Jan 2017 21:12:23 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-vk0-x241.google.com with SMTP id j12so2371307vkd.0 for ; Thu, 12 Jan 2017 13:12:23 -0800 (PST) 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=7ziZ2qFe+49HBr3D/Ku7vD3HPQ+BW4VXIUwgL5Hf73w=; b=hn9BdM4Qz3nlCRdnEEbHnX2r80zw8ESZ6IXJqMqVPg51c2jQy80my7vG9n6tBgieO3 lWdDXFgugK1a4hp0KTCknPBPIOB/c53CfPElb/Sa/b1XGy8CaJa/CSv8WstLAb1wP4bq 8Sgx96S3RZTvp1bizMoeTQT9C6JzYektAznx0resqrLTTMIJbqeBQ7cQWbKAW18/qhtB 1HtuXFHrqeZcVFYjilbrWYcsHyl6RabqJYeHcTCLYCMOKsmdHmVtByQBNu7OomVTT7O7 EEx36nqYbQs0k8UTNQ8eKabTqazPz8NVKVdqNMd0EMR1zVzL/LDIAgHZJumwChQTh7t8 7xGw== 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=7ziZ2qFe+49HBr3D/Ku7vD3HPQ+BW4VXIUwgL5Hf73w=; b=QKhUNX0lpeGZLKMf/9mzJfyv2pTbzscPlVEM5Q/pPvEeydKeutlmkOYk1p3uOA+ZyY UOr9iUjWdSV2Hd4hkl6kTC8eSG0ugVX9RKB/SPCedoWPL+uc0KSCHB9ulovezs0GwCYg Gl1E2UwnV/rGDA7O0QMbIAPwhpJT17dbo+pOw7Pb1gRqXojZEvW0pAtbyqLiTqtytr9V HHkT8j3A1zXKnDrRV2HQoDENWBLNhHsQv9wcbu/C2fuLTrhrDgd5QMIHAi5a+yjOOxD1 ofIg8+yF7IBF9wXpIYlRB/+nEFrMSyhsSNeB9wjLWU7fTYKc85w4rWBrXqgZivogaU9e 6btg== X-Gm-Message-State: AIkVDXJMbfpJwsTmJxt4ZD/i2S3mfrV1pPjvSysUXxO13oXJvgYAS9kN7rJbq1eJ5JzHBGjclWRDDiHJeQp4/w== X-Received: by 10.31.166.7 with SMTP id p7mr7491862vke.136.1484255542825; Thu, 12 Jan 2017 13:12:22 -0800 (PST) MIME-Version: 1.0 Sender: jlehen@gmail.com Received: by 10.103.33.4 with HTTP; Thu, 12 Jan 2017 13:12:22 -0800 (PST) In-Reply-To: References: From: Jeremie Le Hen Date: Thu, 12 Jan 2017 22:12:22 +0100 X-Google-Sender-Auth: 7wBj1CrzVh20N9dPeUynEVcpAwI Message-ID: Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: Steven Hartland Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 21:12:24 -0000 Hey Steven, (Please cc: me on reply) On Thu, Jan 12, 2017 at 1:32 AM, Steven Hartlan > The reason I'd recommend 512k for boot is to provide room for expansion > moving forward, as repartitioning to upgrade is a scary / hard thing to do. > Remember it wasn't long ago when it was well under 64k and that's what was > recommend, its not like with disk sizes these days you'll miss the extra > 384k ;-) Yeah, that's wise you're right. > Boot to a live cd, I'd recommend mfsbsd, and make sure the boot loader was > written to ALL boot disks correctly e.g. > if you have a mirrored pool with ada0 and ada1: > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > > If this doesn't help the output from gpart show, uname -a and zpool status > would also be helpful. > > This is all assuming standard BIOS mode and not UEFI which is done > differently. I just use the installation media on an USB key and then drop to the shell. This is a full FreeBSD running, so that's fine. % # gpart show ada0 % => 40 312581728 ada0 GPT (149G) % 40 1024 1 freebsd-boot (512K) % 1064 8387840 2 freebsd-swap (4.0G) % 8388904 304192864 3 freebsd-zfs (145G) % % # uname -a % FreeBSD 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016 % % root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 % % # zpool status % pool: zroot % state: ONLINE % scan: none requested % config: % % NAME STATE READ WRITE CKSUM % zroot ONLINE 0 0 0 % gptid/1c387d3b-d892-11e6-944b-f44d30620eeb ONLINE 0 0 0 % % errors: No known data errors Here are the steps to write the bootloader: % # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 % partcode written to ada0p1 % bootcode written to ada0 % # zpool get bootfs zroot % NAME PROPERTY VALUE SOURCE % zroot bootfs zroot local -- Jeremie Le Hen jlh@FreeBSD.org From owner-freebsd-stable@freebsd.org Thu Jan 12 21:55:10 2017 Return-Path: Delivered-To: freebsd-stable@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 E7990CAD8F7 for ; Thu, 12 Jan 2017 21:55:10 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 79301106A for ; Thu, 12 Jan 2017 21:55:10 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x229.google.com with SMTP id c206so42187358wme.0 for ; Thu, 12 Jan 2017 13:55:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=cFQIcc9ratLelzlIeLlGql+2h8F3FkWGQvQX/xV69NM=; b=LKsYTqivi+Slh39ycIOvBetg0YMxGv9LapupKxPRUvU+bvbnPzqerfWKFvUUNLTMIq VN3P9Ma65GLC6FSj6z5tIhu026E2Crx2bWVOLTjUz0W5qaIwVSwLWOMORRTKx9LsTFEx d9oP1KMDnQSmkSSt6KSz8XjjSzkA2+UAaO0S78YN3cqsy9zud7wuyvmZyJikLFvi6zJP PEmh0L85hQHJMQeaG9rfhUZrziUjQJRfpcIlVyETkSFl6BtUGYaZe2yL74OLPotcJymj Jgypgv5mLZJIuEjR6ONLlpFif/HSaQMZZCyrwO0ZrmgQWVG6CA5owPQBjILkV3QZssu2 Iy3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=cFQIcc9ratLelzlIeLlGql+2h8F3FkWGQvQX/xV69NM=; b=mzSWGKVQvaqsJjyABEi/Gn4nl/dTDxr7q1FRZPNyCWdTZbLLGAQq0GQpM0dGeqbukl qthxbwYNFFKxN/BfflSt85jHSe4S4PVGcnQe/G2WpTCzPFNfRuWa3NDGn1uE8YFmDh3M PUsJGjzl3TwnEVyINXVxtnDnhLhAqifc5OY+kkcnxlI1TIhIYBQmZSy6W1KBIELX6grV cDGbPyZZBS6GMn73wXFVOL3D8DnuCUvgvsZr/6jlsgdk+Xm/PP+xDhQqFuFm0PGEWT/d zKuHtBBmfT5pvd3gwSkHqk6+60fegm2fHuFGFo+sSaN99FmLuNh9MkUJ1LuZlQFgGaEw QDIA== X-Gm-Message-State: AIkVDXIJqsyZq4aI523Vjmr1OZTx89jnn2exnaCNh22zKNNZzq+gRZrfAAfTQZSubPyENyql X-Received: by 10.28.158.196 with SMTP id h187mr165642wme.59.1484258108913; Thu, 12 Jan 2017 13:55:08 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id a13sm5823704wma.0.2017.01.12.13.55.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jan 2017 13:55:08 -0800 (PST) Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: Jeremie Le Hen References: Cc: freebsd-stable@freebsd.org From: Steven Hartland Message-ID: Date: Thu, 12 Jan 2017 21:55:15 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 21:55:11 -0000 On 12/01/2017 21:12, Jeremie Le Hen wrote: > Hey Steven, > > (Please cc: me on reply) > > On Thu, Jan 12, 2017 at 1:32 AM, Steven Hartlan >> The reason I'd recommend 512k for boot is to provide room for expansion >> moving forward, as repartitioning to upgrade is a scary / hard thing to do. >> Remember it wasn't long ago when it was well under 64k and that's what was >> recommend, its not like with disk sizes these days you'll miss the extra >> 384k ;-) > Yeah, that's wise you're right. > >> Boot to a live cd, I'd recommend mfsbsd, and make sure the boot loader was >> written to ALL boot disks correctly e.g. >> if you have a mirrored pool with ada0 and ada1: >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 >> >> If this doesn't help the output from gpart show, uname -a and zpool status >> would also be helpful. >> >> This is all assuming standard BIOS mode and not UEFI which is done >> differently. > I just use the installation media on an USB key and then drop to the > shell. This is a full FreeBSD running, so that's fine. > > % # gpart show ada0 > % => 40 312581728 ada0 GPT (149G) > % 40 1024 1 freebsd-boot (512K) > % 1064 8387840 2 freebsd-swap (4.0G) > % 8388904 304192864 3 freebsd-zfs (145G) > % > % # uname -a > % FreeBSD 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep > 29 01:43:23 UTC 2016 % % > root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > % > % # zpool status > % pool: zroot > % state: ONLINE > % scan: none requested > % config: > % > % NAME STATE READ > WRITE CKSUM > % zroot ONLINE 0 > 0 0 > % gptid/1c387d3b-d892-11e6-944b-f44d30620eeb ONLINE 0 > 0 0 > % > % errors: No known data errors > > Here are the steps to write the bootloader: > > % # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > % partcode written to ada0p1 > % bootcode written to ada0 > % # zpool get bootfs zroot > % NAME PROPERTY VALUE SOURCE > % zroot bootfs zroot local Two things spring to mind Idea 1: Is your root fs actually your direct pool or is it actually /root off your pool. If so you want to run: zpool set bootfs=zroot/root zroot Idea 2: You mentioned in your original post and you used zfs send / recv to restore the pool, so I wonder if your cache file is out of date. Try the following: |zpool export zroot zpool import -R /mnt -o cachefile=/boot/zfs/zpool.cache zroot cp /boot/zfs/zpool.cache /mnt/boot/zfs/zpool.cache zpool set bootfs=zroot/root zroot Regards Steve | From owner-freebsd-stable@freebsd.org Thu Jan 12 22:30:00 2017 Return-Path: Delivered-To: freebsd-stable@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 334E9CAD9C8 for ; Thu, 12 Jan 2017 22:30:00 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03D12166B for ; Thu, 12 Jan 2017 22:29:59 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 555B1311AAE for ; Thu, 12 Jan 2017 22:29:57 +0000 (UTC) From: Stefan Bethke Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: zpool asize problem on 11.0 Message-Id: <01B0C796-CB6D-412D-AB93-05836906BC89@lassitu.de> Date: Thu, 12 Jan 2017 23:29:56 +0100 To: freebsd-stable X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 22:30:00 -0000 I=E2=80=99ve just created two pools on a freshly partitioned disk, using = 11.0 amd64, and the shift appears to be 9: # zpool status -v host pool: host state: ONLINE status: One or more devices are configured to use a non-native block = size. Expect reduced performance. action: Replace affected devices with devices that support the configured block size, or migrate data to a properly configured pool. scan: none requested config: NAME STATE READ WRITE CKSUM host ONLINE 0 0 0 gpt/host0 ONLINE 0 0 0 block size: 512B = configured, 4096B native errors: No known data errors # zdb host | grep ashift ashift: 9 ashift: 9 But: # sysctl vfs.zfs.min_auto_ashift vfs.zfs.min_auto_ashift: 12 Of course, I=E2=80=99ve noticed this only after restoring all the = backups, and getting ready to put the box back into production. Is this expected behaviour? I guess there=E2=80=99s no simple fix, and = I have to start over from scratch? Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-stable@freebsd.org Thu Jan 12 22:57:48 2017 Return-Path: Delivered-To: freebsd-stable@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 5EF27CAD930 for ; Thu, 12 Jan 2017 22:57:48 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E2D61A57 for ; Thu, 12 Jan 2017 22:57:48 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id C6830311BF2 for ; Thu, 12 Jan 2017 22:57:46 +0000 (UTC) From: Stefan Bethke Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: zpool asize problem on 11.0 Date: Thu, 12 Jan 2017 23:57:45 +0100 References: <01B0C796-CB6D-412D-AB93-05836906BC89@lassitu.de> To: freebsd-stable In-Reply-To: <01B0C796-CB6D-412D-AB93-05836906BC89@lassitu.de> Message-Id: X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 22:57:48 -0000 > Am 12.01.2017 um 23:29 schrieb Stefan Bethke : >=20 > I=E2=80=99ve just created two pools on a freshly partitioned disk, = using 11.0 amd64, and the shift appears to be 9: >=20 > # zpool status -v host > pool: host > state: ONLINE > status: One or more devices are configured to use a non-native block = size. > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: none requested > config: >=20 > NAME STATE READ WRITE CKSUM > host ONLINE 0 0 0 > gpt/host0 ONLINE 0 0 0 block size: 512B = configured, 4096B native >=20 > errors: No known data errors >=20 > # zdb host | grep ashift > ashift: 9 > ashift: 9 >=20 > But: > # sysctl vfs.zfs.min_auto_ashift > vfs.zfs.min_auto_ashift: 12 >=20 > Of course, I=E2=80=99ve noticed this only after restoring all the = backups, and getting ready to put the box back into production. >=20 > Is this expected behaviour? I guess there=E2=80=99s no simple fix, = and I have to start over from scratch? I had falsely assumed that vfs.zfs.min_auto_ashift would be 12 in all = circumstances. It appears when running FreeBSD 11.0p2 in VirtualBox, it = can be 9. And my target disk was attached to the host and mapped into = the VM as a =E2=80=9Enative disk image=E2=80=9C, but the 4k native = sector size apparently got lost in that abstraction. The output above is with the disk installed in the target system with a = native AHCI connection, and the system booted from that disk. I=E2=80=99ve certainly learned to double check the ashift property on = creating pools. Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-stable@freebsd.org Thu Jan 12 23:30:53 2017 Return-Path: Delivered-To: freebsd-stable@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 1203DCA90EC for ; Thu, 12 Jan 2017 23:30:53 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 AB94F1546 for ; Thu, 12 Jan 2017 23:30:52 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x231.google.com with SMTP id n129so7780205wmn.0 for ; Thu, 12 Jan 2017 15:30:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=/mglYDtjEXUon0FFbyIBKgM2Z8/lX/asefwKGoGkwns=; b=L4P20QspbnHBu9ex+swDDl149sol5db+oA+FXaSovu8EKMsmQ/EyBe7jUIsA7qPqF7 4X4WIAnQQd0UwbMKoUcw4nPHp/aBgEOuImYVUamai51lQnuQTmP4wkvO3TwHm+SC1uX4 p9YQYXRbuJ/fukHo2a+7clgTLuxlo7d2B4VQ1ZqiHblK9tVmNir9aL6sdDmBuAqrOctH tvgTYsEPKmG81Nmsyc0eBAVzIPD37A+WM61QfwTor9UXT5WwAsRDkvt3ihDQWKkXoVxN +ixNMuM79szl9A0HB1c9yj1ue284MsFdl1a0xG8Xbn0psQSG6TGKD7K0QJbz9h51y23N oWeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=/mglYDtjEXUon0FFbyIBKgM2Z8/lX/asefwKGoGkwns=; b=fzM41lFhqjRHzWREysqdeLGEgvBXPT3YdYVr8PIvBXUYaNvGb/SB5YwkHSqVdZbQZ+ qCDCTkwoQRAZAs3qyXK48eE2kQhvZ9iO2KsXEzT5xYjmcTfx+ioU0g1U7e9NSQm5+psX t0LfLa7tjJa4bzuWHXG6sqNwQ0CYq7Vxp0STBHTioOTSn4Bx19S8tjClXXcVDZLLv+ve 3rWh6/KfkM84OARL3eRV+js4TrKD9gVZ1WraRcWUJdfjr+PWrk6lWXTZIKbcKb6gkxDf orH1Gnia5OkhL0SSfVTBIHnmd/SZF10+w5q05WOxekumj6W7VjH2COBUkmHClEdY3Sfq JarA== X-Gm-Message-State: AIkVDXIm7+n8j8qVKPk5cArj9msd5RzsOu+Tp2tkcu7Ku3n0FA4oCSKWbSEcqaUzJCtL4+ST X-Received: by 10.28.207.70 with SMTP id f67mr339550wmg.72.1484263850470; Thu, 12 Jan 2017 15:30:50 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id w7sm6255921wmd.24.2017.01.12.15.30.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jan 2017 15:30:49 -0800 (PST) Subject: Re: zpool asize problem on 11.0 To: freebsd-stable@freebsd.org References: <01B0C796-CB6D-412D-AB93-05836906BC89@lassitu.de> From: Steven Hartland Message-ID: <3035d642-bffa-84b9-a4bc-b7134541fc78@multiplay.co.uk> Date: Thu, 12 Jan 2017 23:30:56 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 23:30:53 -0000 On 12/01/2017 22:57, Stefan Bethke wrote: > Am 12.01.2017 um 23:29 schrieb Stefan Bethke : >> I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, and the shift appears to be 9: >> >> # zpool status -v host >> pool: host >> state: ONLINE >> status: One or more devices are configured to use a non-native block size. >> Expect reduced performance. >> action: Replace affected devices with devices that support the >> configured block size, or migrate data to a properly configured >> pool. >> scan: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> host ONLINE 0 0 0 >> gpt/host0 ONLINE 0 0 0 block size: 512B configured, 4096B native >> >> errors: No known data errors >> >> # zdb host | grep ashift >> ashift: 9 >> ashift: 9 >> >> But: >> # sysctl vfs.zfs.min_auto_ashift >> vfs.zfs.min_auto_ashift: 12 >> >> Of course, I’ve noticed this only after restoring all the backups, and getting ready to put the box back into production. >> >> Is this expected behaviour? I guess there’s no simple fix, and I have to start over from scratch? > I had falsely assumed that vfs.zfs.min_auto_ashift would be 12 in all circumstances. It appears when running FreeBSD 11.0p2 in VirtualBox, it can be 9. And my target disk was attached to the host and mapped into the VM as a „native disk image“, but the 4k native sector size apparently got lost in that abstraction. > > The output above is with the disk installed in the target system with a native AHCI connection, and the system booted from that disk. > > I’ve certainly learned to double check the ashift property on creating pools. > The default value for vfs.zfs.min_auto_ashift is 9, so unless you specifically set it to 12 you will get the behaviour you described. Regards Steve From owner-freebsd-stable@freebsd.org Fri Jan 13 08:07:08 2017 Return-Path: Delivered-To: freebsd-stable@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 0253ECAD3ED for ; Fri, 13 Jan 2017 08:07:08 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 B3ABC1CC1 for ; Fri, 13 Jan 2017 08:07:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.81.13]) by kabab.cs.huji.ac.il with esmtp id 1cRwsy-000JTa-8b; Fri, 13 Jan 2017 10:06:56 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: NFS and amd on older FreeBSD From: Daniel Braniss In-Reply-To: <20170112190125.GR26386@mailboy.kipshouse.net> Date: Fri, 13 Jan 2017 10:06:56 +0200 Cc: FreeBSD Stable Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <343F8AE3-1428-4B0E-A3C3-C60D5B6DB905@cs.huji.ac.il> References: <20170111234737.GK26386@mailboy.kipshouse.net> <20170112190125.GR26386@mailboy.kipshouse.net> To: Karl Young X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 08:07:08 -0000 > On 12 Jan 2017, at 21:01, Karl Young wrote: >=20 > Daniel Braniss(danny@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >>=20 >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss = wrote: >>>=20 >>>=20 >>>> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >>>>=20 >>>> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. >>>> These hosts run test scripts that access files that are stored on >>>> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS >>>>=20 >>>>=20 >>>> On the 7.2 hosts, I can see the exported directory: >>>>=20 >>>> $ showmount -e 6.3-host >>>> Exports list on 6.3-host >>>> /data Everyone >>>>=20 >>>> And access it with amd >>>>=20 >>>> $ ls -l /net/6-3.host/data >>>>=20 >>>> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >>>> drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home >>>>=20 >>>> I'm trying to retire the 6.3 host and replace it with 9.3 (I know = it's >>>> old, but it's the best I can do for now). >>>>=20 >>>> I export the /data directory on the 9.3 system, and I can see it on = my >>>> 7.2 hosts. >>>>=20 >>>> $ showmount -e 9.3-host >>>> Exports list on 9.3-host: >>>> /data Everyone >>>>=20 >>>> But I can't automount it: >>>>=20 >>>> $ ls -l /net/9.3-host/data >>>> ls: /net/9.3-host/data: No such file or directory >>>>=20 >>>> If I manually mount the exported directory, it works: >>>>=20 >>>> $ sudo mount -t nfs 9.3-host:/data /mnt/data/ >>>> $ mount | grep nfs >>>> 9.3-host:/data on /mnt/data (nfs) >>>>=20 >>>> $ ls -l /mnt/data >>>> total 4 >>>> drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 >>>>=20 >>>> I've spent some time on Google, but haven't found a solution. I = realize >>>> these are very old versions, but I'm not in a position to upgrade = them >>>> right now. My last resort will be to use /etc/fstab to do the NFS >>>> mount, but I'd rather avoid that if I can. >>>>=20 >>>> Thanks for any pointers on how to resolve this. >>>>=20 >>>> -karl >>>>=20 >>>>=20 >>>=20 >>> if you changed the export file on the server after you tried to = mount in on the client, >>> and will not realise this, if that=E2=80=99s the case, usually = rebooting the client helps. >>>=20 >> s/and/amd/ ^%$# hate spell checkers >>=20 >=20 > Thanks Danny >=20 > I did try rebooting the client (and server) multiple times to no = avail. what does amq say? you can, from another host do: amq -h client-host btw, I thing that nfs_server must also run on the client =E2=80=A6 I have nfs_server_enable=3DYES danny From owner-freebsd-stable@freebsd.org Fri Jan 13 14:24:56 2017 Return-Path: Delivered-To: freebsd-stable@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 AAE19CAE76F for ; Fri, 13 Jan 2017 14:24:56 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (www2.alogis.com [212.184.102.7]) (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 2A77D1309 for ; Fri, 13 Jan 2017 14:24:55 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from msx3.exchange.alogis.com (msxcn4.exchange.alogis.com [10.1.1.18]) by alogis.com (8.13.4/8.13.1) with ESMTP id v0DEOrd7004621 for ; Fri, 13 Jan 2017 15:24:53 +0100 (CET) (envelope-from Holger.Kipp@alogis.com) Received: from MSX3.exchange.alogis.com ([10.1.1.26]) by MSXCN4 ([10.1.1.18]) with mapi id 14.03.0319.002; Fri, 13 Jan 2017 15:24:53 +0100 From: Holger Kipp To: "freebsd-stable@freebsd.org" Subject: pkg upgrade wants to install old postgresql-client-version. why? Thread-Topic: pkg upgrade wants to install old postgresql-client-version. why? Thread-Index: AQHSbajNfnIm+mGtQEe/Cdvkq2fsDg== Date: Fri, 13 Jan 2017 14:24:52 +0000 Message-ID: <877F58D1-9D84-48D7-BC74-BC20170E901A@alogis.com> Accept-Language: de-DE, en-GB, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.184.101.130] Content-Type: text/plain; charset="us-ascii" Content-ID: <4BAF96FC664DA2458485BF33AFF28DC1@exchange.alogis.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 14:24:56 -0000 Dear all, I have a little FreeBSD system upgraded from 10.2-p24 to 10.3-p11. GENERIC = Kernel. This also included upgrading postgresql from 9.5.4 to 9.5.5_1. and about 22= 0 other ports. Most were upgraded using pkg upgrade, but postgresql had to be upgraded usi= ng the manual make, make package, make deinstall && make reinstall. root@gw2:~ # pkg info | grep postgresql postgresql95-client-9.5.5_1 PostgreSQL database (client) postgresql95-contrib-9.5.5 The contrib utilities from the PostgreSQL di= stribution postgresql95-server-9.5.5_1 PostgreSQL is the most advanced open-source = database available anywhere root@gw2:~ # All Ports were originally installed from source but with default config. -------- Now pkg upgrade wants to install postgresql-client 9.3.15_1: root@gw2:~ # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (28 candidates): 100% Processing candidates (28 candidates): 100% The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: postgresql93-client: 9.3.15_1 Installed packages to be REINSTALLED: p5-Pg-2.1.1_4,1 (direct dependency changed: perl5) p5-DBD-Pg-3.5.3 (direct dependency changed: p5-DBI) Number of packages to be installed: 1 Number of packages to be reinstalled: 2 The process will require 9 MiB more space. 2 MiB to be downloaded. Proceed with this action? [y/N]: -------- My programs using p5-Pg or p5-DBD-Pg seem to work just fine, and perl5 has = current version perl5-5.24.1.r4_1. However I had to reinstall both packages manually because they were not pro= perly working after upgrade via pkg upgrade. How can I check where from pkg upgrade gets the idea to install old 9.3.15_= 1 postgresql client? And is there a way to rectify this? Many thanks and best regards, Holger __________________________________________________________ Holger Kipp Diplom-Mathematiker Senior Consultant Tel. : +49 30 436 58 114 Fax. : +49 30 436 58 214 Mobil: +49 178 36 58 114 Email: holger.kipp@alogis.com alogis AG Alt-Moabit 90b D-10559 Berlin http://www.alogis.com __________________________________________________________ alogis AG Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 Vorstand: Arne Friedrichs, Joern Samuelson Aufsichtsratsvorsitzender: Reinhard Mielke From owner-freebsd-stable@freebsd.org Fri Jan 13 14:42:17 2017 Return-Path: Delivered-To: freebsd-stable@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 4F30ACAEC7A for ; Fri, 13 Jan 2017 14:42:17 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E1001B91 for ; Fri, 13 Jan 2017 14:42:16 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id A529E7A9; Fri, 13 Jan 2017 09:42:08 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: pkg upgrade wants to install old postgresql-client-version. why? From: Paul Mather In-Reply-To: <877F58D1-9D84-48D7-BC74-BC20170E901A@alogis.com> Date: Fri, 13 Jan 2017 09:42:08 -0500 Cc: "freebsd-stable@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <1B1319FA-B572-4947-88DD-E8B708320CB8@gromit.dlib.vt.edu> References: <877F58D1-9D84-48D7-BC74-BC20170E901A@alogis.com> To: Holger Kipp X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 14:42:17 -0000 On Jan 13, 2017, at 9:24 AM, Holger Kipp wrote: > Dear all, >=20 > I have a little FreeBSD system upgraded from 10.2-p24 to 10.3-p11. = GENERIC Kernel. > This also included upgrading postgresql from 9.5.4 to 9.5.5_1. and = about 220 other ports. > Most were upgraded using pkg upgrade, but postgresql had to be = upgraded using the manual > make, make package, make deinstall && make reinstall. >=20 > root@gw2:~ # pkg info | grep postgresql > postgresql95-client-9.5.5_1 PostgreSQL database (client) > postgresql95-contrib-9.5.5 The contrib utilities from the = PostgreSQL distribution > postgresql95-server-9.5.5_1 PostgreSQL is the most advanced = open-source database available anywhere > root@gw2:~ # >=20 > All Ports were originally installed from source but with default = config. >=20 > -------- >=20 > Now pkg upgrade wants to install postgresql-client 9.3.15_1: >=20 > root@gw2:~ # pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking for upgrades (28 candidates): 100% > Processing candidates (28 candidates): 100% > The following 3 package(s) will be affected (of 0 checked): >=20 > New packages to be INSTALLED: > postgresql93-client: 9.3.15_1 >=20 > Installed packages to be REINSTALLED: > p5-Pg-2.1.1_4,1 (direct dependency changed: perl5) > p5-DBD-Pg-3.5.3 (direct dependency changed: p5-DBI) >=20 > Number of packages to be installed: 1 > Number of packages to be reinstalled: 2 >=20 > The process will require 9 MiB more space. > 2 MiB to be downloaded. >=20 > Proceed with this action? [y/N]: >=20 > -------- > My programs using p5-Pg or p5-DBD-Pg seem to work just fine, and perl5 = has current version perl5-5.24.1.r4_1. > However I had to reinstall both packages manually because they were = not properly working after upgrade via pkg upgrade. You are using the official FreeBSD packages for your upgrade. They are = built with postgresql93 as the default version of PostgreSQL. Thus, = p5-Pg and p5-DBD-Pg will both have a dependency on the postgresql-client = packages (for libraries allowing them to interface with PostgreSQL = servers), which, in the FreeBSD repository, is postgresql93-client. Because postgresql93-client conflicts with postgresql95-client, it will = try and uninstall the latter when trying to satisfy the = postgresql93-client dependency. The same will be true of any other = package you try and use from the FreeBSD repository that has a = dependency upon PostgreSQL. > How can I check where from pkg upgrade gets the idea to install old = 9.3.15_1 postgresql client? > And is there a way to rectify this? I would imagine that, like you did with the PostgreSQL 9.5 ports, you = would also have to build and reinstall p5-Pg and p5-DBD-Pg manually, = too. Be sure to add "DEFAULT_VERSIONS+=3D pgsql=3D9.5" or otherwise = amend your DEFAULT_VERSIONS setting in /etc/make.conf before building so = that p5-Pg and p5-DBD-Pg depend upon the version of PostgreSQL you want. Mixing custom local ports and stock ports from the FreeBSD official = packages repository will often lead to these sorts of problems, due to = differences in build options and such. Another way to rectify it is to build your own ports using something = like Poudriere. Cheers, Paul. From owner-freebsd-stable@freebsd.org Fri Jan 13 15:20:04 2017 Return-Path: Delivered-To: freebsd-stable@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 7E8D7CAE947 for ; Fri, 13 Jan 2017 15:20:04 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (www2.alogis.com [212.184.102.7]) (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 DC03110A8 for ; Fri, 13 Jan 2017 15:20:03 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from msx3.exchange.alogis.com (msxcn2.exchange.alogis.com [10.1.1.22]) by alogis.com (8.13.4/8.13.1) with ESMTP id v0DFJucI005763; Fri, 13 Jan 2017 16:19:56 +0100 (CET) (envelope-from Holger.Kipp@alogis.com) Received: from MSX3.exchange.alogis.com ([10.1.1.26]) by msxcn2.exchange.alogis.com ([fe80::11b6:f5c4:b8ee:4a89%15]) with mapi id 14.03.0279.002; Fri, 13 Jan 2017 16:19:55 +0100 From: Holger Kipp To: Paul Mather CC: "freebsd-stable@freebsd.org" Subject: Re: pkg upgrade wants to install old postgresql-client-version. why? Thread-Topic: pkg upgrade wants to install old postgresql-client-version. why? Thread-Index: AQHSbajNz+T97OnPMEG6L7pbBEF/4qE2alkAgAAKjoA= Date: Fri, 13 Jan 2017 15:19:55 +0000 Message-ID: <63933012-A522-4E9C-8968-FD418867047C@alogis.com> References: <877F58D1-9D84-48D7-BC74-BC20170E901A@alogis.com> <1B1319FA-B572-4947-88DD-E8B708320CB8@gromit.dlib.vt.edu> In-Reply-To: <1B1319FA-B572-4947-88DD-E8B708320CB8@gromit.dlib.vt.edu> Accept-Language: de-DE, en-GB, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.184.101.130] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 15:20:04 -0000 RGVhciBQYXVsLA0KDQpBbSAxMy4wMS4yMDE3IHVtIDE1OjQ5IHNjaHJpZWIgUGF1bCBNYXRoZXIg PHBhdWxAZ3JvbWl0LmRsaWIudnQuZWR1PG1haWx0bzpwYXVsQGdyb21pdC5kbGliLnZ0LmVkdT4+ Og0KDQpPbiBKYW4gMTMsIDIwMTcsIGF0IDk6MjQgQU0sIEhvbGdlciBLaXBwIDxIb2xnZXIuS2lw cEBhbG9naXMuY29tPG1haWx0bzpIb2xnZXIuS2lwcEBhbG9naXMuY29tPj4gd3JvdGU6DQoNCkRl YXIgYWxsLA0KDQpJIGhhdmUgYSBsaXR0bGUgRnJlZUJTRCBzeXN0ZW0gdXBncmFkZWQgZnJvbSAx MC4yLXAyNCB0byAxMC4zLXAxMS4gR0VORVJJQyBLZXJuZWwuDQpUaGlzIGFsc28gaW5jbHVkZWQg dXBncmFkaW5nIHBvc3RncmVzcWwgZnJvbSA5LjUuNCB0byA5LjUuNV8xLiBhbmQgYWJvdXQgMjIw IG90aGVyIHBvcnRzLg0KTW9zdCB3ZXJlIHVwZ3JhZGVkIHVzaW5nIHBrZyB1cGdyYWRlLCBidXQg cG9zdGdyZXNxbCBoYWQgdG8gYmUgdXBncmFkZWQgdXNpbmcgdGhlIG1hbnVhbA0KbWFrZSwgbWFr ZSBwYWNrYWdlLCBtYWtlIGRlaW5zdGFsbCAmJiBtYWtlIHJlaW5zdGFsbC4NCg0Kcm9vdEBndzI6 fiAjIHBrZyBpbmZvIHwgZ3JlcCBwb3N0Z3Jlc3FsDQpwb3N0Z3Jlc3FsOTUtY2xpZW50LTkuNS41 XzEgICAgUG9zdGdyZVNRTCBkYXRhYmFzZSAoY2xpZW50KQ0KcG9zdGdyZXNxbDk1LWNvbnRyaWIt OS41LjUgICAgIFRoZSBjb250cmliIHV0aWxpdGllcyBmcm9tIHRoZSBQb3N0Z3JlU1FMIGRpc3Ry aWJ1dGlvbg0KcG9zdGdyZXNxbDk1LXNlcnZlci05LjUuNV8xICAgIFBvc3RncmVTUUwgaXMgdGhl IG1vc3QgYWR2YW5jZWQgb3Blbi1zb3VyY2UgZGF0YWJhc2UgYXZhaWxhYmxlIGFueXdoZXJlDQpy b290QGd3Mjp+ICMNCg0KQWxsIFBvcnRzIHdlcmUgb3JpZ2luYWxseSBpbnN0YWxsZWQgZnJvbSBz b3VyY2UgYnV0IHdpdGggZGVmYXVsdCBjb25maWcuDQoNCi0tLS0tLS0tDQoNCk5vdyBwa2cgdXBn cmFkZSB3YW50cyB0byBpbnN0YWxsIHBvc3RncmVzcWwtY2xpZW50IDkuMy4xNV8xOg0KDQpyb290 QGd3Mjp+ICMgcGtnIHVwZ3JhZGUNClVwZGF0aW5nIEZyZWVCU0QgcmVwb3NpdG9yeSBjYXRhbG9n dWUuLi4NCkZyZWVCU0QgcmVwb3NpdG9yeSBpcyB1cC10by1kYXRlLg0KQWxsIHJlcG9zaXRvcmll cyBhcmUgdXAtdG8tZGF0ZS4NCkNoZWNraW5nIGZvciB1cGdyYWRlcyAoMjggY2FuZGlkYXRlcyk6 IDEwMCUNClByb2Nlc3NpbmcgY2FuZGlkYXRlcyAoMjggY2FuZGlkYXRlcyk6IDEwMCUNClRoZSBm b2xsb3dpbmcgMyBwYWNrYWdlKHMpIHdpbGwgYmUgYWZmZWN0ZWQgKG9mIDAgY2hlY2tlZCk6DQoN Ck5ldyBwYWNrYWdlcyB0byBiZSBJTlNUQUxMRUQ6DQogICAgICBwb3N0Z3Jlc3FsOTMtY2xpZW50 OiA5LjMuMTVfMQ0KDQpJbnN0YWxsZWQgcGFja2FnZXMgdG8gYmUgUkVJTlNUQUxMRUQ6DQogICAg ICBwNS1QZy0yLjEuMV80LDEgKGRpcmVjdCBkZXBlbmRlbmN5IGNoYW5nZWQ6IHBlcmw1KQ0KICAg ICAgcDUtREJELVBnLTMuNS4zIChkaXJlY3QgZGVwZW5kZW5jeSBjaGFuZ2VkOiBwNS1EQkkpDQoN Ck51bWJlciBvZiBwYWNrYWdlcyB0byBiZSBpbnN0YWxsZWQ6IDENCk51bWJlciBvZiBwYWNrYWdl cyB0byBiZSByZWluc3RhbGxlZDogMg0KDQpUaGUgcHJvY2VzcyB3aWxsIHJlcXVpcmUgOSBNaUIg bW9yZSBzcGFjZS4NCjIgTWlCIHRvIGJlIGRvd25sb2FkZWQuDQoNClByb2NlZWQgd2l0aCB0aGlz IGFjdGlvbj8gW3kvTl06DQoNCi0tLS0tLS0tDQpNeSBwcm9ncmFtcyB1c2luZyBwNS1QZyBvciBw NS1EQkQtUGcgc2VlbSB0byB3b3JrIGp1c3QgZmluZSwgYW5kIHBlcmw1IGhhcyBjdXJyZW50IHZl cnNpb24gcGVybDUtNS4yNC4xLnI0XzEuDQpIb3dldmVyIEkgaGFkIHRvIHJlaW5zdGFsbCBib3Ro IHBhY2thZ2VzIG1hbnVhbGx5IGJlY2F1c2UgdGhleSB3ZXJlIG5vdCBwcm9wZXJseSB3b3JraW5n IGFmdGVyIHVwZ3JhZGUgdmlhIHBrZyB1cGdyYWRlLg0KDQoNCllvdSBhcmUgdXNpbmcgdGhlIG9m ZmljaWFsIEZyZWVCU0QgcGFja2FnZXMgZm9yIHlvdXIgdXBncmFkZS4gIFRoZXkgYXJlIGJ1aWx0 IHdpdGggcG9zdGdyZXNxbDkzIGFzIHRoZSBkZWZhdWx0IHZlcnNpb24gb2YgUG9zdGdyZVNRTC4g VGh1cywgcDUtUGcgYW5kIHA1LURCRC1QZyB3aWxsIGJvdGggaGF2ZSBhIGRlcGVuZGVuY3kgb24g dGhlIHBvc3RncmVzcWwtY2xpZW50IHBhY2thZ2VzIChmb3IgbGlicmFyaWVzIGFsbG93aW5nIHRo ZW0gdG8gaW50ZXJmYWNlIHdpdGggUG9zdGdyZVNRTCBzZXJ2ZXJzKSwgd2hpY2gsIGluIHRoZSBG cmVlQlNEIHJlcG9zaXRvcnksIGlzIHBvc3RncmVzcWw5My1jbGllbnQuDQoNCkJlY2F1c2UgcG9z dGdyZXNxbDkzLWNsaWVudCBjb25mbGljdHMgd2l0aCBwb3N0Z3Jlc3FsOTUtY2xpZW50LCBpdCB3 aWxsIHRyeSBhbmQgdW5pbnN0YWxsIHRoZSBsYXR0ZXIgd2hlbiB0cnlpbmcgdG8gc2F0aXNmeSB0 aGUgcG9zdGdyZXNxbDkzLWNsaWVudCBkZXBlbmRlbmN5LiAgVGhlIHNhbWUgd2lsbCBiZSB0cnVl IG9mIGFueSBvdGhlciBwYWNrYWdlIHlvdSB0cnkgYW5kIHVzZSBmcm9tIHRoZSBGcmVlQlNEIHJl cG9zaXRvcnkgdGhhdCBoYXMgYSBkZXBlbmRlbmN5IHVwb24gUG9zdGdyZVNRTC4NCg0KDQpIb3cg Y2FuIEkgY2hlY2sgd2hlcmUgZnJvbSBwa2cgdXBncmFkZSBnZXRzIHRoZSBpZGVhIHRvIGluc3Rh bGwgb2xkIDkuMy4xNV8xIHBvc3RncmVzcWwgY2xpZW50Pw0KQW5kIGlzIHRoZXJlIGEgd2F5IHRv IHJlY3RpZnkgdGhpcz8NCg0KDQpJIHdvdWxkIGltYWdpbmUgdGhhdCwgbGlrZSB5b3UgZGlkIHdp dGggdGhlIFBvc3RncmVTUUwgOS41IHBvcnRzLCB5b3Ugd291bGQgYWxzbyBoYXZlIHRvIGJ1aWxk IGFuZCByZWluc3RhbGwgcDUtUGcgYW5kIHA1LURCRC1QZyBtYW51YWxseSwgdG9vLiAgQmUgc3Vy ZSB0byBhZGQgIkRFRkFVTFRfVkVSU0lPTlMrPSBwZ3NxbD05LjUiIG9yIG90aGVyd2lzZSBhbWVu ZCB5b3VyIERFRkFVTFRfVkVSU0lPTlMgc2V0dGluZyBpbiAvZXRjL21ha2UuY29uZiBiZWZvcmUg YnVpbGRpbmcgc28gdGhhdCBwNS1QZyBhbmQgcDUtREJELVBnIGRlcGVuZCB1cG9uIHRoZSB2ZXJz aW9uIG9mIFBvc3RncmVTUUwgeW91IHdhbnQuDQoNCk1peGluZyBjdXN0b20gbG9jYWwgcG9ydHMg YW5kIHN0b2NrIHBvcnRzIGZyb20gdGhlIEZyZWVCU0Qgb2ZmaWNpYWwgcGFja2FnZXMgcmVwb3Np dG9yeSB3aWxsIG9mdGVuIGxlYWQgdG8gdGhlc2Ugc29ydHMgb2YgcHJvYmxlbXMsIGR1ZSB0byBk aWZmZXJlbmNlcyBpbiBidWlsZCBvcHRpb25zIGFuZCBzdWNoLg0KDQpBbm90aGVyIHdheSB0byBy ZWN0aWZ5IGl0IGlzIHRvIGJ1aWxkIHlvdXIgb3duIHBvcnRzIHVzaW5nIHNvbWV0aGluZyBsaWtl IFBvdWRyaWVyZS4NCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgdGhlIGdvb2QgZXhwbGFuYXRp b24uIEnigJlsbCBnbyB3aXRoIHRoZSBERUZBVUxUX1ZFUlNJT05TLVNldHRpbmcgaW4gbWFrZS5j b25mIHRoZW4uDQpJcyB0aGVyZSBhIGxpc3Qgb2YgZGVwZW5kZW5jaWVzIGZvciB0aGUgRnJlZUJT RCByZXBvc2l0b3J5IHNvIEkgY2FuIGNoZWNrIGlmIG15IHN5c3RlbSBpcyBhbHNvIGFmZmVjdGVk IHRoZXJlPw0KDQpNYW55IHRoYW5rcyBhbmQgYmVzdCByZWdhcmRzLA0KSG9sZ2VyDQoNCg0K From owner-freebsd-stable@freebsd.org Fri Jan 13 15:43:45 2017 Return-Path: Delivered-To: freebsd-stable@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 202C8CAD0F1 for ; Fri, 13 Jan 2017 15:43:45 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (www2.alogis.com [212.184.102.7]) (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 BFBF01FCD for ; Fri, 13 Jan 2017 15:43:44 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from msx3.exchange.alogis.com (msxcn4.exchange.alogis.com [10.1.1.18]) by alogis.com (8.13.4/8.13.1) with ESMTP id v0DFhgkF006211 for ; Fri, 13 Jan 2017 16:43:42 +0100 (CET) (envelope-from Holger.Kipp@alogis.com) Received: from MSX3.exchange.alogis.com ([10.1.1.26]) by MSXCN4 ([10.1.1.18]) with mapi id 14.03.0319.002; Fri, 13 Jan 2017 16:43:41 +0100 From: Holger Kipp To: "freebsd-stable@freebsd.org" Subject: pkg upgrade problem with Perl 5.24 Thread-Topic: pkg upgrade problem with Perl 5.24 Thread-Index: AQHSbbPQ4ah0ruBhlEaag1wPxo8PDg== Date: Fri, 13 Jan 2017 15:43:41 +0000 Message-ID: Accept-Language: de-DE, en-GB, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [212.184.101.130] Content-Type: text/plain; charset="utf-8" Content-ID: <13B36C006A3CAD4CB43DE1FE9710C4B2@exchange.alogis.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 15:43:45 -0000 RGVhciBhbGwsDQoNCkkgdXBncmFkZWQgUGVybCB0byA1LjI0KDEucjRfMSkgKHZpYSBwa2cgdXBn cmFkZSkuDQpXaGVuIEkgbm93IHRyeSB0byBpbnN0YWxsIHRoZSBsYXRlc3QgdmVyc2lvbiBmcm9t IHBvcnRzICgxLnI1XzEpLCB0aGUgc3lzdGVtIGNhbuKAmXQgaW5zdGFsbCB0aGUgbmV3IHZlcnNp b24gYmVjYXVzZSBvZiB0aGUgb2xkZXIgdmVyc2lvbiwgYnV0IGNhbuKAmXQgZGVpbnN0YWxsKCop IHRoZSBvbGRlciB2ZXJzaW9uIChlZy4gdmlhIG1ha2UgZGVpbnN0YWxsICYmIG1ha2UgcmVpbnN0 YWxsKS4NCg0KDQoNCnJvb3RAZ3cyOi91c3IvcG9ydHMvbGFuZy9wZXJsNS4yNCAjIHBrZyBpbmZv IHwgZ3JlcCBwZXJsDQpwNS1EYXRhLUR1bXBlci0yLjE2MSAgICAgICAgICAgU3RyaW5naWZpZWQg cGVybCBkYXRhIHN0cnVjdHVyZXMsIHN1aXRhYmxlIGZvciBib3RoIHByaW50aW5nIGFuZCBldmFs DQpwNS1QZy0yLjEuMV80LDEgICAgICAgICAgICAgICAgSW50ZXJmYWNlIGZvciB1c2luZyBwZXJs NSB0byBhY2Nlc3MgUG9zdGdyZVNRTCBkYXRhYmFzZXMNCnA1LVNjYWxhci1MaXN0LVV0aWxzLTEu NDUsMSAgICBQZXJsIHN1YnJvdXRpbmVzIHRoYXQgd291bGQgYmUgbmljZSB0byBoYXZlIGluIHRo ZSBwZXJsIGNvcmUNCnBlcmw1LTUuMjQuMS5yNF8xICAgICAgICAgICAgICBQcmFjdGljYWwgRXh0 cmFjdGlvbiBhbmQgUmVwb3J0IExhbmd1YWdlDQoNCnNvIGN1cnJlbnRseSB2aWEgcGtnIHVwZ3Jh ZGUgSSBnb3QgcGVybDUtNS4yNC4xLnI0XzEsIHdoaWNoIHBlcmwgaXRzZWxmIGNvbmZpcm1zOg0K cm9vdEBndzI6L3Vzci9wb3J0cy9sYW5nL3Blcmw1LjI0ICMgcGVybCAtdg0KDQpUaGlzIGlzIHBl cmwgNSwgdmVyc2lvbiAyNCwgc3VidmVyc2lvbiAxICh2NS4yNC4xKSBidWlsdCBmb3IgYW1kNjQt ZnJlZWJzZC10aHJlYWQtbXVsdGkNCih3aXRoIDEgcmVnaXN0ZXJlZCBwYXRjaCwgc2VlIHBlcmwg LVYgZm9yIG1vcmUgZGV0YWlsKQ0KDQpUaGlzIGlzIHRoZW4gb2J2aW91c2x5IHRoZSB2ZXJzaW9u IGZyb20gRnJlZUJTRCByZXBvc2l0b3J5Lg0KDQpJZiBJIHRyeSB0byBpbnN0YWxsIHRoZSBsYXRl c3QgdmVyc2lvbiBmcm9tIHBvcnRzIChwZXJsNS01LjI0LjEucjVfMSksIEkgZ2V0IHRoZSBmb2xs b3dpbmcgKG1ha2UgaW5zdGFsbCBqdXN0IHRvIGdldCB0aGUgbWVzc2FnZXMpOg0KDQoNCnJvb3RA Z3cyOi91c3IvcG9ydHMvbGFuZy9wZXJsNS4yNCAjIG1ha2UgaW5zdGFsbA0KPT09PiAgSW5zdGFs bGluZyBmb3IgcGVybDUuMjQtNS4yNC4xLnI1XzENCj09PT4gIENoZWNraW5nIGlmIHBlcmw1LjI0 IGFscmVhZHkgaW5zdGFsbGVkDQo9PT0+ICAgUmVnaXN0ZXJpbmcgaW5zdGFsbGF0aW9uIGZvciBw ZXJsNS4yNC01LjI0LjEucjVfMQ0KSW5zdGFsbGluZyBwZXJsNS4yNC01LjI0LjEucjVfMS4uLg0K cGtnLXN0YXRpYzogcGVybDUuMjQtNS4yNC4xLnI1XzEgY29uZmxpY3RzIHdpdGggcGVybDUtNS4y NC4xLnI0XzEgKGluc3RhbGxzIGZpbGVzIGludG8gdGhlIHNhbWUgcGxhY2UpLiAgUHJvYmxlbWF0 aWMgZmlsZTogL3Vzci9sb2NhbC9iaW4vcGVybDUuMjQuMQ0KKioqIEVycm9yIGNvZGUgNzANCg0K U3RvcC4NCm1ha2VbMV06IHN0b3BwZWQgaW4gL3Vzci9wb3J0cy9sYW5nL3Blcmw1LjI0DQoqKiog RXJyb3IgY29kZSAxDQoNClN0b3AuDQptYWtlOiBzdG9wcGVkIGluIC91c3IvcG9ydHMvbGFuZy9w ZXJsNS4yNA0KDQoNCkRlaW5zdGFsbGluZyB0aGUgZXhpc3RpbmcgdmVyc2lvbiBkb2VzIG5vdCB3 b3JrOg0KDQpyb290QGd3MjovdXNyL3BvcnRzL2xhbmcvcGVybDUuMjQgIyBtYWtlIGRlaW5zdGFs bA0KPT09PiAgRGVpbnN0YWxsaW5nIGZvciBwZXJsNS4yNA0KPT09PiAgIHBlcmw1LjI0IG5vdCBp bnN0YWxsZWQsIHNraXBwaW5nDQoNCkJ1dCBhY2NvcmRpbmcgdG8gcGtnIGluZm8gaXQgaXMgaW5z dGFsbGVkOg0KDQpyb290QGd3MjovdXNyL3BvcnRzL2xhbmcvcGVybDUuMjQgIyBwa2cgaW5mbyBw ZXJsNQ0KcGVybDUtNS4yNC4xLnI0XzENCk5hbWUgICAgICAgICAgIDogcGVybDUNClZlcnNpb24g ICAgICAgIDogNS4yNC4xLnI0XzENCkluc3RhbGxlZCBvbiAgIDogVGh1IEphbiAxMiAxMjo1MTow MyAyMDE3IENFVA0KT3JpZ2luICAgICAgICAgOiBsYW5nL3Blcmw1LjI0DQoNCg0KVGhpcyBzZWVz IHRvIGJlIGEgYml0IHN0cmFuZ2UuDQoNCigqKSBJIGhhdmUgbm93IHJlbW92ZWQgdGhlIHBhY2th Z2UgdXNpbmcgcGtnIGRlbGV0ZSAtZiAtbiBwZXJsNS01LjI0LjEucjRfMSBhbmQgd2FzIHRoZW4g YWJsZSB0byBpbnN0YWxsIGZyb20gcG9ydHMgd2l0aG91dCBwcm9ibGVtczoNCg0Kcm9vdEBndzI6 L3Vzci9wb3J0cy9sYW5nL3Blcmw1LjI0ICMgcGtnIGluZm8gcGVybDUuMjQtNS4yNC4xLnI1XzEN CnBlcmw1LjI0LTUuMjQuMS5yNV8xDQpOYW1lICAgICAgICAgICA6IHBlcmw1LjI0DQpWZXJzaW9u ICAgICAgICA6IDUuMjQuMS5yNV8xDQpJbnN0YWxsZWQgb24gICA6IFRodSBKYW4gMTIgMTc6NTM6 NDUgMjAxNyBDRVQNCk9yaWdpbiAgICAgICAgIDogbGFuZy9wZXJsNS4yNA0KDQoNCkFueSBpZGVh cyB3aGF0IGhhcHBlbmVkIGhlcmU/IEnigJltIG5vdCBzdXJlIGlmIHRoaXMgaXMgZXhwZWN0ZWQg YmVoYXZpb3VyLg0KDQpNYW55IHRoYW5rcyBhbmQgYmVzdCByZWdhcmRzLA0KSG9sZ2VyDQoNCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Cg0KSG9sZ2VyIEtpcHANCkRpcGxvbS1NYXRoZW1hdGlrZXINClNlbmlvciBDb25zdWx0YW50DQoN ClRlbC4gOiArNDkgMzAgNDM2IDU4IDExNA0KRmF4LiA6ICs0OSAzMCA0MzYgNTggMjE0DQpNb2Jp bDogKzQ5IDE3OCAzNiA1OCAxMTQNCkVtYWlsOiBob2xnZXIua2lwcEBhbG9naXMuY29tDQoNCmFs b2dpcyBBRw0KQWx0LU1vYWJpdCA5MGINCkQtMTA1NTkgQmVybGluDQoNCmh0dHA6Ly93d3cuYWxv Z2lzLmNvbQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXw0KDQphbG9naXMgQUcNClNpdHovUmVnaXN0ZXJnZXJpY2h0OiBCZXJsaW4vQUcg Q2hhcmxvdHRlbmJ1cmcsIEhSQiA3MTQ4NA0KVm9yc3RhbmQ6IEFybmUgRnJpZWRyaWNocywgSm9l cm4gU2FtdWVsc29uDQpBdWZzaWNodHNyYXRzdm9yc2l0emVuZGVyOiBSZWluaGFyZCBNaWVsa2UN Cg0K From owner-freebsd-stable@freebsd.org Fri Jan 13 16:18:24 2017 Return-Path: Delivered-To: freebsd-stable@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 B5A08CADC85 for ; Fri, 13 Jan 2017 16:18:24 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49FCD10E0 for ; Fri, 13 Jan 2017 16:18:24 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 1E06A206D for ; Fri, 13 Jan 2017 16:18:20 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/1E06A206D; dkim=none; dkim-atps=neutral Subject: Re: pkg upgrade problem with Perl 5.24 To: freebsd-stable@freebsd.org References: From: Matthew Seaman Message-ID: Date: Fri, 13 Jan 2017 16:18:12 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="09fd4ij6nRRsonxXcikMPXAmuBIAx4Adb" X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_00,RCVD_IN_RP_RNBL, RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 16:18:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --09fd4ij6nRRsonxXcikMPXAmuBIAx4Adb Content-Type: multipart/mixed; boundary="93BRwvXCqi482mdhJET8hU6ipl1b6fx32"; protected-headers="v1" From: Matthew Seaman To: freebsd-stable@freebsd.org Message-ID: Subject: Re: pkg upgrade problem with Perl 5.24 References: In-Reply-To: --93BRwvXCqi482mdhJET8hU6ipl1b6fx32 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017/01/13 15:43, Holger Kipp wrote: > so currently via pkg upgrade I got perl5-5.24.1.r4_1, which perl itself= confirms: ^^^^^ > =3D=3D=3D> Installing for perl5.24-5.24.1.r5_1 ^^^^^^^^ Notice the difference in package names. One is calling itself 'perl5' and the other 'perl5.24' which means pkg(8) thinks they are completely different packages. This is why compiling from ports can't delete the version you installed as a pkg. The reason for the different names is because in one case, that port was designated the default perl version when the package was built, and in the other case it wasn't. 5.24 is currently the default version of perl in the FreeBSD package build cluster, as of the beginning of this month for the latest quarterly branch. Check your /etc/make.conf or similar -- do you have a DEFAULT_VERSIONS setting for perl? You should use something like: DEFAULT_VERSIONS+=3D perl5=3D5.24 which will at least make the pkg cluster and your own-build packages agree on the package name. Cheers, Matthew --93BRwvXCqi482mdhJET8hU6ipl1b6fx32-- --09fd4ij6nRRsonxXcikMPXAmuBIAx4Adb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYeP3LXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnH+gP/1Ci9RYEZmdGnc42M0YWCRpO DM0XGyrktdpAnX4oUSssUlsuzXFPTpzBT+xzQRNZB3zdq0SBTJlRGAwli+nVdWBN zbr00bHaZDQyMddLASGJTW3S4zJjmCPbTlkN+XqihucxJVvtfG60t/xQ6EDTi4Q4 G7bHk1aUWAE9Ef5j1gwWYMqE9axwhyLmkrFeyZ0yUJV+9eHLqnz11kfIo+nLgUzQ lMdC5k+Mhrl7jr8BzXoNVtRnGI34EENRNsXolnBGar+sDr0dj98inOIkfkvKLKEc 8Vrcv9TWDJfRYeKiSGRlMBz1Tshgk03uwHzzTcsxlM+x6wTmJFeN3imbAJ17JNRR lx2bSUeHbPmy50SvWCqKsiUj4pW7vSyGtUaj3Rfwpo7FgugjpuYQvpWEZ956QrFU BSVMpjWI8YdKg76isvD/7H7YCPAEaHHaxUFvYEYCiW4INfClbO53gVwzK6TCyTB8 28XlYJjOdP2BVheMvR9GwnsczEBF+0ivBSBIdvjhrFweTyffthWOCudjkZ7vdwnG 83SiFw4FmjrCAaPGhsxS9kEYV4BaKKWEqhuaTFMuUq9r++W1QumgjUFmf7opdrek O+XABk2gkmFtDyd31DmXjKoFIqQwl4Ru6dbg93a/wW9bCSEaTuKlgKwVTiicMyVs a614vjX/N2cTOCLgQnY/ =ahVX -----END PGP SIGNATURE----- --09fd4ij6nRRsonxXcikMPXAmuBIAx4Adb-- From owner-freebsd-stable@freebsd.org Fri Jan 13 16:31:17 2017 Return-Path: Delivered-To: freebsd-stable@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 84D01CAE191 for ; Fri, 13 Jan 2017 16:31:17 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 571171A38 for ; Fri, 13 Jan 2017 16:31:16 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v0DGVEG6069254 for ; Fri, 13 Jan 2017 08:31:20 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: From: "Chris H" Subject: Re: pkg upgrade problem with Perl 5.24 Date: Fri, 13 Jan 2017 08:31:20 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 16:31:17 -0000 On Fri, 13 Jan 2017 15:43:41 +0000 Holger Kipp wrote > Dear all, > > I upgraded Perl to 5.24(1.r4_1) (via pkg upgrade). > When I now try to install the latest version from ports (1.r5_1), the system > can’t install the new version because of the older version, but can’t > deinstall(*) the older version (eg. via make deinstall && make reinstall). > > > > root@gw2:/usr/ports/lang/perl5.24 # pkg info | grep perl > p5-Data-Dumper-2.161 Stringified perl data structures, suitable for > both printing and eval p5-Pg-2.1.1_4,1 Interface for using > perl5 to access PostgreSQL databases p5-Scalar-List-Utils-1.45,1 Perl > subroutines that would be nice to have in the perl core perl5-5.24.1.r4_1 > Practical Extraction and Report Language > > so currently via pkg upgrade I got perl5-5.24.1.r4_1, which perl itself > confirms: root@gw2:/usr/ports/lang/perl5.24 # perl -v > > This is perl 5, version 24, subversion 1 (v5.24.1) built for > amd64-freebsd-thread-multi (with 1 registered patch, see perl -V for more > detail) > > This is then obviously the version from FreeBSD repository. > > If I try to install the latest version from ports (perl5-5.24.1.r5_1), I get > the following (make install just to get the messages): > > > root@gw2:/usr/ports/lang/perl5.24 # make install > ===> Installing for perl5.24-5.24.1.r5_1 > ===> Checking if perl5.24 already installed > ===> Registering installation for perl5.24-5.24.1.r5_1 > Installing perl5.24-5.24.1.r5_1... > pkg-static: perl5.24-5.24.1.r5_1 conflicts with perl5-5.24.1.r4_1 (installs > files into the same place). Problematic file: /usr/local/bin/perl5.24.1 > *** Error code 70 > > Stop. > make[1]: stopped in /usr/ports/lang/perl5.24 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/lang/perl5.24 > > > Deinstalling the existing version does not work: > > root@gw2:/usr/ports/lang/perl5.24 # make deinstall > ===> Deinstalling for perl5.24 > ===> perl5.24 not installed, skipping > > But according to pkg info it is installed: > > root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5 > perl5-5.24.1.r4_1 > Name : perl5 > Version : 5.24.1.r4_1 > Installed on : Thu Jan 12 12:51:03 2017 CET > Origin : lang/perl5.24 > > > This sees to be a bit strange. > > (*) I have now removed the package using pkg delete -f -n perl5-5.24.1.r4_1 > and was then able to install from ports without problems: > > root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5.24-5.24.1.r5_1 > perl5.24-5.24.1.r5_1 > Name : perl5.24 > Version : 5.24.1.r5_1 > Installed on : Thu Jan 12 17:53:45 2017 CET > Origin : lang/perl5.24 > > > Any ideas what happened here? I’m not sure if this is expected behaviour. > > Many thanks and best regards, > Holger As a general rule: install from pkg(8) remove with pkg(8) install from ports(7), remove with ports(7) That said; I didn't notice any evidence of which version of FreeBSD, you're running (uname -a) -- It's important where Perl is concerned. How about make.conf(5)? Anything interesting in there; DEFAULT_VERSIONS+= or WITH_PKGNG= HTH --Chris From owner-freebsd-stable@freebsd.org Fri Jan 13 16:39:10 2017 Return-Path: Delivered-To: freebsd-stable@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 11C33CAE53D for ; Fri, 13 Jan 2017 16:39:10 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF9681F2A for ; Fri, 13 Jan 2017 16:39:09 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id A5B8B2086 for ; Fri, 13 Jan 2017 16:39:06 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/A5B8B2086; dkim=none; dkim-atps=neutral Subject: Re: pkg upgrade problem with Perl 5.24 To: freebsd-stable@freebsd.org References: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net> From: Matthew Seaman Message-ID: <5c07feaa-d49d-43bb-40e1-a3507a679edb@FreeBSD.org> Date: Fri, 13 Jan 2017 16:38:59 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ft0FcC8PVSMCETQPU8tLlNos6CSrS4cBu" X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_00,RCVD_IN_RP_RNBL, RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 16:39:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ft0FcC8PVSMCETQPU8tLlNos6CSrS4cBu Content-Type: multipart/mixed; boundary="8QLr0PXda6cHQ5vqlkK8cleq31WbNuRSS"; protected-headers="v1" From: Matthew Seaman To: freebsd-stable@freebsd.org Message-ID: <5c07feaa-d49d-43bb-40e1-a3507a679edb@FreeBSD.org> Subject: Re: pkg upgrade problem with Perl 5.24 References: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net> In-Reply-To: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net> --8QLr0PXda6cHQ5vqlkK8cleq31WbNuRSS Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2017/01/13 16:31, Chris H wrote: > As a general rule: > install from pkg(8) remove with pkg(8) > install from ports(7), remove with ports(7) >=20 Sorry -- this is completely bogus. You can freely mix and match either way. Just make sure that the package names match up. In fact the ports removes packages using pkg(8), so it all comes down to the same thing in the end. Cheers, Matthew --8QLr0PXda6cHQ5vqlkK8cleq31WbNuRSS-- --ft0FcC8PVSMCETQPU8tLlNos6CSrS4cBu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYeQKqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnw0wQAKq+E6kHkmCdIUtlUSoje4yk U90MzAa1TCykx9SDq/1kFKwh5TopNbgSuc83k20QypoFmTti0CbyKsVQ9daCADVz zn4zCpr/uwBMoWP+0wygE76gWZ+RhlnTECHleUjKWOqA/8gMoDpJfWYynozSoWlC F6ilOvnSdVsgBi+V/JFOqVryNUYNui4sIcwMjG7qDwEAwdpjyLgb89aAUTVDcsYu H0/J7JJnSznDMIJAILUo40hWt6uWxE4aHIL/VakSX2eeLsdVY+m5bAoMOAzV4dgh QHWAf9l0pcOJ37q4RB4tUtgQgfRdgB61rg7pclu+xVeK2cnd6rUDI4pZPi2EGAIV xiPS7CoLZ/EF5lC2YZMtGUXX1TWEORgL/SFtcb5WZ8j+ULg9nhwj3DOBpQvv6C4N JZhclYnpcAZLjlgsnsn9mbKMAfcPh4PHVnh3C0eAMPb3ScX9EATbFanyH1ge/HBD dI2sBEwKGhXY4m1YEpL4hdIysjhiOzM3IuOPKfrEqB0ZymNVI8LzmGIvkck0hdSi 9WZ7MXCq7WQDfg5JSzTiT8KzIf66Jny9ZckAjFpwa323qRT3q0mjHxnpBrP59vUu olQGbr/UV6xkbkulsAw9OdpXKgPmlM42iQeuSKgcuvoYpzmXS05ZUfSRLr4i/m2q co6wXiM1O+Y3CcrQG5oe =GwE0 -----END PGP SIGNATURE----- --ft0FcC8PVSMCETQPU8tLlNos6CSrS4cBu-- From owner-freebsd-stable@freebsd.org Fri Jan 13 16:52:10 2017 Return-Path: Delivered-To: freebsd-stable@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 3CAC4CAEA86 for ; Fri, 13 Jan 2017 16:52:10 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF791ABF for ; Fri, 13 Jan 2017 16:52:09 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v0DGqD3W071465 for ; Fri, 13 Jan 2017 08:52:19 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <5c07feaa-d49d-43bb-40e1-a3507a679edb@FreeBSD.org> References: <5b13bb8420bc5e6429b905bdfc4027cf@ultimatedns.net>, <5c07feaa-d49d-43bb-40e1-a3507a679edb@FreeBSD.org> From: "Chris H" Subject: Re: pkg upgrade problem with Perl 5.24 Date: Fri, 13 Jan 2017 08:52:19 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <1ad47d672f07464e22fabb8b703c22e6@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 16:52:10 -0000 On Fri, 13 Jan 2017 16:38:59 +0000 Matthew Seaman wrote > On 2017/01/13 16:31, Chris H wrote: > > As a general rule: > > install from pkg(8) remove with pkg(8) > > install from ports(7), remove with ports(7) > > > > Sorry -- this is completely bogus. Not entirely. > You can freely mix and match either > way. Just make sure that the package names match up. > > In fact the ports removes packages using pkg(8), so it all comes down to > the same thing in the end. That is the *intended* outcome, to be sure. *But* as noted in the OP[1], and from some edge cases I've personally run into; the "general rule" I listed, does apply. :) > > Cheers, > > Matthew I have now removed the package using pkg delete -f -n perl5-5.24.1.r4_1 and was then able to install from ports without problems: [1] root@gw2:/usr/ports/lang/perl5.24 # pkg info perl5.24-5.24.1.r5_1 perl5.24-5.24.1.r5_1 Name : perl5.24 Version : 5.24.1.r5_1 Installed on : Thu Jan 12 17:53:45 2017 CET Origin : lang/perl5.24 --Chris From owner-freebsd-stable@freebsd.org Fri Jan 13 19:18:43 2017 Return-Path: Delivered-To: freebsd-stable@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 91F57CACBB0 for ; Fri, 13 Jan 2017 19:18:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5576116C4 for ; Fri, 13 Jan 2017 19:18:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id A5A3B7E5; Fri, 13 Jan 2017 14:18:41 -0500 (EST) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: pkg upgrade wants to install old postgresql-client-version. why? From: Paul Mather In-Reply-To: <63933012-A522-4E9C-8968-FD418867047C@alogis.com> Date: Fri, 13 Jan 2017 14:18:41 -0500 Cc: "freebsd-stable@freebsd.org" Message-Id: References: <877F58D1-9D84-48D7-BC74-BC20170E901A@alogis.com> <1B1319FA-B572-4947-88DD-E8B708320CB8@gromit.dlib.vt.edu> <63933012-A522-4E9C-8968-FD418867047C@alogis.com> To: Holger Kipp X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 19:18:43 -0000 On Jan 13, 2017, at 10:19 AM, Holger Kipp = wrote: > Dear Paul, >=20 >> Am 13.01.2017 um 15:49 schrieb Paul Mather >: >>=20 >> On Jan 13, 2017, at 9:24 AM, Holger Kipp > wrote: >>=20 >>> Dear all, >>>=20 >>> I have a little FreeBSD system upgraded from 10.2-p24 to 10.3-p11. = GENERIC Kernel. >>> This also included upgrading postgresql from 9.5.4 to 9.5.5_1. and = about 220 other ports. >>> Most were upgraded using pkg upgrade, but postgresql had to be = upgraded using the manual >>> make, make package, make deinstall && make reinstall. >>>=20 >>> root@gw2:~ # pkg info | grep postgresql >>> postgresql95-client-9.5.5_1 PostgreSQL database (client) >>> postgresql95-contrib-9.5.5 The contrib utilities from the = PostgreSQL distribution >>> postgresql95-server-9.5.5_1 PostgreSQL is the most advanced = open-source database available anywhere >>> root@gw2:~ # >>>=20 >>> All Ports were originally installed from source but with default = config. >>>=20 >>> -------- >>>=20 >>> Now pkg upgrade wants to install postgresql-client 9.3.15_1: >>>=20 >>> root@gw2:~ # pkg upgrade >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>> Checking for upgrades (28 candidates): 100% >>> Processing candidates (28 candidates): 100% >>> The following 3 package(s) will be affected (of 0 checked): >>>=20 >>> New packages to be INSTALLED: >>> postgresql93-client: 9.3.15_1 >>>=20 >>> Installed packages to be REINSTALLED: >>> p5-Pg-2.1.1_4,1 (direct dependency changed: perl5) >>> p5-DBD-Pg-3.5.3 (direct dependency changed: p5-DBI) >>>=20 >>> Number of packages to be installed: 1 >>> Number of packages to be reinstalled: 2 >>>=20 >>> The process will require 9 MiB more space. >>> 2 MiB to be downloaded. >>>=20 >>> Proceed with this action? [y/N]: >>>=20 >>> -------- >>> My programs using p5-Pg or p5-DBD-Pg seem to work just fine, and = perl5 has current version perl5-5.24.1.r4_1. >>> However I had to reinstall both packages manually because they were = not properly working after upgrade via pkg upgrade. >>=20 >>=20 >> You are using the official FreeBSD packages for your upgrade. They = are built with postgresql93 as the default version of PostgreSQL. Thus, = p5-Pg and p5-DBD-Pg will both have a dependency on the postgresql-client = packages (for libraries allowing them to interface with PostgreSQL = servers), which, in the FreeBSD repository, is postgresql93-client. >>=20 >> Because postgresql93-client conflicts with postgresql95-client, it = will try and uninstall the latter when trying to satisfy the = postgresql93-client dependency. The same will be true of any other = package you try and use from the FreeBSD repository that has a = dependency upon PostgreSQL. >>=20 >>=20 >>> How can I check where from pkg upgrade gets the idea to install old = 9.3.15_1 postgresql client? >>> And is there a way to rectify this? >>=20 >>=20 >> I would imagine that, like you did with the PostgreSQL 9.5 ports, you = would also have to build and reinstall p5-Pg and p5-DBD-Pg manually, = too. Be sure to add "DEFAULT_VERSIONS+=3D pgsql=3D9.5" or otherwise = amend your DEFAULT_VERSIONS setting in /etc/make.conf before building so = that p5-Pg and p5-DBD-Pg depend upon the version of PostgreSQL you want. >>=20 >> Mixing custom local ports and stock ports from the FreeBSD official = packages repository will often lead to these sorts of problems, due to = differences in build options and such. >>=20 >> Another way to rectify it is to build your own ports using something = like Poudriere. >=20 > Thank you very much for the good explanation. I=E2=80=99ll go with the = DEFAULT_VERSIONS-Setting in make.conf then. > Is there a list of dependencies for the FreeBSD repository so I can = check if my system is also affected there? I'm not sure if this is what you're asking, but one thing you can do is = query the FreeBSD packages repository for such information. See "pkg = help rquery" for details. E.g., to see what packages (and versions) the = p5-DBD-Pg package depends upon, use the following command: pkg rquery %dn-%dv p5-DBD-Pg Currently, this returns: p5-DBI-1.636 perl5-5.24.1.r4_1 postgresql93-client-9.3.15_1 To see which packages potentially are affected by manually installing a = different version of PostgreSQL (i.e., those packages that depend upon = postgresql93-client), use the following command: pkg rquery %ro postgresql93-client This currently returns a list of 115 packages. Note also that the standard FreeBSD package repository distributed with = recent releases is based upon the "quarterly" ports tree. Make sure you = use the same source in your local /usr/ports, otherwise you have scope = for even more divergence between your local ports being built and the = ones you're using from the official FreeBSD package repository. = Alternatively, you could point your FreeBSD.conf pkg repo to "latest" to = make /usr/ports match up. Cheers, Paul.= From owner-freebsd-stable@freebsd.org Fri Jan 13 19:21:40 2017 Return-Path: Delivered-To: freebsd-stable@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 8F413CACEE4 for ; Fri, 13 Jan 2017 19:21:40 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 049181AB7 for ; Fri, 13 Jan 2017 19:21:39 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v0DJLSRj033810 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 13 Jan 2017 20:21:29 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v0DJLNsM084438 for ; Sat, 14 Jan 2017 02:21:23 +0700 (KRAT) (envelope-from eugen@grosbein.net) To: FreeBSD Stable From: Eugene Grosbein Subject: stable/11 debugging kernel unable to produce crashdump X-Enigmail-Draft-Status: N1110 Message-ID: <587928B3.2050607@grosbein.net> Date: Sat, 14 Jan 2017 02:21:23 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 19:21:40 -0000 Hi! I'm struggling to debug a panic in 11.0-STABLE/i386 that successfully produces crashdump but I want more information. So I've rebuilt my custom kernel to include options INVARIANTS, WITNESS and DEADLKRES. Now any panic results in quick unclean reboot without crashdump generation. Serial console shows: Script started on Sat Jan 14 02:03:16 2017 Command: cu -l cuau0 -s 115200 Connected root@gw:~ # sysctl debug.kdb.panic=1 debug.kdb.panic:panic: kdb_sysctl_panic KDB: stack backtrace: db_trace_self_wrapper(e8bc2ae8,0,e8bc2ae8,e8bc2a48,c06b4af4,...) at 0xc04c457b = db_trace_self_wrapper+0x2b/frame 0xe8bc2a20 vpanic(c0a4916e,e8bc2a54,e8bc2a54,e8bc2a5c,c06e881f,...) at 0xc06b4a7f = vpanic+0x6f/frame 0xe8bc2a34 panic(c0a4916e,1,c0ae7e48,e8bc2a88,c06bfdd3,...) at 0xc06b4af4 = panic+0x14/frame 0xe8bc2a48 kdb_sysctl_panic(c0ae7e48,0,0,0,e8bc2ae8) at 0xc06e881f = kdb_sysctl_panic+0x4f/frame 0xe8bc2a5c sysctl_root_handler_locked(0,0,e8bc2ae8,e8bc2aa8) at 0xc06bfdd3 = sysctl_root_handler_locked+0x83/frame 0xe8bc2a88 sysctl_root(0,e8bc2ae8) at 0xc06bf744 = sysctl_root+0x144/frame 0xe8bc2ad8 userland_sysctl(c759f9c0,e8bc2b60,3,0,0,0,bfbfdc5c,4,e8bc2bc0,0) at 0xc06bfb9d = userland_sysctl+0x12d/frame 0xe8bc2b30 sys___sysctl(c759f9c0,e8bc2c00) at 0xc06bfa32 = sys___sysctl+0x52/frame 0xe8bc2bd0 syscall(e8bc2ce8) at 0xc0980801 = syscall+0x2a1/frame 0xe8bc2cdc Xint0x80_syscall() at 0xc096e45e = Xint0x80_syscall+0x2e/frame 0xe8bc2cdc --- syscall (202, FreeBSD ELF32, sys___sysctl), eip = 0x2818541b, esp = 0xbfbfdbc8, ebp = 0xbfbfdbf0 --- Uptime: 4m36s panic: malloc: called with spinlock or critical section held Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 Uptime: 4m36s panic: /boot/config: -D FreeBSD/x86 boot Default: 0:ad(0,a)/boot/loader boot: Also, I get a Lock Order Reversal at boot time: lock order reversal: 1st 0xc6c2aa30 ufs (ufs) @ /home/src/sys/kern/vfs_subr.c:2523 2nd 0xd99a3b80 bufwait (bufwait) @ /home/src/sys/ufs/ffs/ffs_vnops.c:277 3rd 0xc6c53a30 ufs (ufs) @ /home/src/sys/kern/vfs_subr.c:2523 stack backtrace: #0 0xc0700442 at witness_debugger+0x62 #1 0xc0700386 at witness_checkorder+0xb56 #2 0xc069757c at __lockmgr_args+0x5bc #3 0xc0908db2 at ffs_lock+0x62 #4 0xc099f63f at VOP_LOCK1_APV+0xbf #5 0xc0762b8e at _vn_lock+0x8e #6 0xc0755477 at vget+0x57 #7 0xc0749783 at vfs_hash_get+0xb3 #8 0xc0904da7 at ffs_vgetf+0x27 #9 0xc08fc47d at softdep_sync_buf+0xa1d #10 0xc09099b1 at ffs_syncvnode+0x281 #11 0xc090758c at ffs_sync+0x19c #12 0xc074eb93 at dounmount+0x583 #13 0xc074e529 at sys_unmount+0x229 #14 0xc0980801 at syscall+0x2a1 #15 0xc096e45e at Xint0x80_syscall+0x2e Done This is r311924 with custom kernel having SCHED_4BSD instead of default SCHED_ULE: # GW kernel config # CPU Geode LX 800 options INCLUDE_CONFIG_FILE machine i386 cpu I586_CPU cpu I686_CPU options CPU_GEODE options CPU_SOEKRIS ident GW maxusers 0 options SCHED_4BSD options INET #InterNETworking options SCTP options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KTRACE #ktrace(1) support options UFS_GJOURNAL # Enable gjournal-based UFS journaling options GEOM_JOURNAL options GEOM_LABEL options GEOM_CACHE options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options UDF options LIBICONV options CD9660_ICONV options MSDOSFS_ICONV options UDF_ICONV options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options PRINTF_BUFR_SIZE=512 # Prevent printf output being interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options NFSCL # Network Filesystem Client options NFSD # Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options COMPAT_LINUX options PROCFS # Process filesystem (requires PSEUDOFS) options LINPROCFS options PSEUDOFS # Pseudo-filesystem framework device eisa device pci device atkbdc device atkbd options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP=ru.koi8-r device vga device sc options SC_HISTORY_SIZE=4000 options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=cp866 device uart device speaker device miibus # MII bus support device vr device loop # Network loopback device random device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md device gif # IPv6 and IPv4 tunneling device vlan device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) device fwip # IP over FireWire (RFC 2734,3146) device dcons # Dumb console driver device dcons_crom # Configuration ROM for dcons device bpf #Berkeley packet filter device ata device ohci device ehci device usb # USB Bus (required) device umass # Disks/Mass storage - Requires scbus and da device ulpt options USB_VERBOSE device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) options LIBALIAS options IPFIREWALL options IPDIVERT options IPFIREWALL_NAT options DUMMYNET makeoptions DEBUG=-g options NETGRAPH options NETGRAPH_BPF options NETGRAPH_ECHO options NETGRAPH_ETHER options NETGRAPH_IFACE options NETGRAPH_EIFACE options NETGRAPH_IPFW options NETGRAPH_SOCKET options NETGRAPH_KSOCKET options NETGRAPH_L2TP options NETGRAPH_TEE options NETGRAPH_NAT options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_TCPMSS options NETGRAPH_PPTPGRE options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_VJC device crypto device glxsb device enc options IPSEC #option IPSEC_SUPPORT options IPSEC_FILTERTUNNEL device cpuctl options ROUTETABLES=16 # Debugging kernel options KDB # Enable kernel debugger support. options KDB_UNATTENDED # Enable kernel debugger support. options KDB_TRACE # Enable kernel debugger support. options KDTRACE_HOOKS options DDB # Support DDB. options DDB_NUMSYM options GDB # Support remote GDB. options ALT_BREAK_TO_DEBUGGER options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options DEADLKRES options WITNESS options WITNESS_SKIPSPIN device wlan # 802.11 support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device ath # Atheros pci/cardbus NIC's device ath_hal # pci/cardbus chip support device ath_pci options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors device ath_rate_sample # SampleRate tx rate control for ath Can anyone verify if debugging kernel fails to generate crashdump in stable/11? Egene Grosbein From owner-freebsd-stable@freebsd.org Fri Jan 13 19:31:08 2017 Return-Path: Delivered-To: freebsd-stable@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 38223CAE39F for ; Fri, 13 Jan 2017 19:31:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (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 E67B7101E for ; Fri, 13 Jan 2017 19:31:07 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt0-x243.google.com with SMTP id l7so7414261qtd.3 for ; Fri, 13 Jan 2017 11:31:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=LNWqIAUD3JHzlKYpT0suhZmcMqyqQKRINs69EQy6X5E=; b=MS1py9zVbeY5sJrYDLWkM2toUA6TR8CKChZiZZnxiBqFychewVBGDf81Au3wql9Vcq bYNpwDNmSUQ9jbEK2ppcziiVYbIC/yXKZbVmd0f/1FQ/w2ZNMHdNCWRzNzeFsvW6kYDe nsPN58GDYv9GZKWZ/kuPBhq8XkCYdqD0cA+MHG0X37BIrKFKD52EQHlu7ibuvGfoZuy6 djEq6qQoHE5UzfVdWao4KMyddkS2zIm/WWVJh6JzYMQRawu/YmyQVGG6Xth/3cufVreG 3niouHxcPIAuE0Uw7/VqSgJqzDhOyqtnCQ4H6VPPB+pVUPGHfE2WLF1fgdtPx7qmHqzf ikxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=LNWqIAUD3JHzlKYpT0suhZmcMqyqQKRINs69EQy6X5E=; b=i2KvCdt3qBRRt/d+PF78z5P7y1Xu9jaXlTUGhkDm8x47/t4T4O+/dkIhJTAIwkiLEc yadffFPsIiomw6u8CAQexVSwZMj23hNceyhc06HpQgFDYW66GNmuwxBwcGiX3wy8Az0j gp3jHbBEYt2b0g1bRaSD2W5rhlCtkEM6b6CG6l5ujtvJ/YFdjaMj9ucYRWDSpe6AZWOJ w7OopDq7bnDZreBGPhQZou5NjTB4NUpQB9triy/shL6EACjf8HhKqzfUyMQByPEjghT0 t+d3Gp6xQrN8/vywloiw0an94tUlm9QHMoqf6rE3jBqdUjCOIFfkPZWQX1CkYf7XEi5+ SEwQ== X-Gm-Message-State: AIkVDXLyc0W7ciCQCuwWpMl51Q4uqgmAkqAup75LXzfuY2ryPRV1o3DL1EPNa7HzdSz4JA== X-Received: by 10.237.52.199 with SMTP id x65mr18563923qtd.152.1484335867118; Fri, 13 Jan 2017 11:31:07 -0800 (PST) Received: from wkstn-mjohnston.west.isilon.com (c-76-104-201-218.hsd1.wa.comcast.net. [76.104.201.218]) by smtp.gmail.com with ESMTPSA id b16sm9888760qka.9.2017.01.13.11.31.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Jan 2017 11:31:06 -0800 (PST) Sender: Mark Johnston Date: Fri, 13 Jan 2017 11:37:26 -0800 From: Mark Johnston To: Eugene Grosbein Cc: FreeBSD Stable Subject: Re: stable/11 debugging kernel unable to produce crashdump Message-ID: <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com> References: <587928B3.2050607@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <587928B3.2050607@grosbein.net> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 19:31:08 -0000 On Sat, Jan 14, 2017 at 02:21:23AM +0700, Eugene Grosbein wrote: > Hi! > > I'm struggling to debug a panic in 11.0-STABLE/i386 that successfully produces crashdump > but I want more information. So I've rebuilt my custom kernel to include > options INVARIANTS, WITNESS and DEADLKRES. Now any panic results in quick unclean reboot > without crashdump generation. Serial console shows: > > Script started on Sat Jan 14 02:03:16 2017 > Command: cu -l cuau0 -s 115200 > Connected > > root@gw:~ # sysctl debug.kdb.panic=1 > debug.kdb.panic:panic: kdb_sysctl_panic > KDB: stack backtrace: > db_trace_self_wrapper(e8bc2ae8,0,e8bc2ae8,e8bc2a48,c06b4af4,...) at 0xc04c457b = db_trace_self_wrapper+0x2b/frame 0xe8bc2a20 > vpanic(c0a4916e,e8bc2a54,e8bc2a54,e8bc2a5c,c06e881f,...) at 0xc06b4a7f = vpanic+0x6f/frame 0xe8bc2a34 > panic(c0a4916e,1,c0ae7e48,e8bc2a88,c06bfdd3,...) at 0xc06b4af4 = panic+0x14/frame 0xe8bc2a48 > kdb_sysctl_panic(c0ae7e48,0,0,0,e8bc2ae8) at 0xc06e881f = kdb_sysctl_panic+0x4f/frame 0xe8bc2a5c > sysctl_root_handler_locked(0,0,e8bc2ae8,e8bc2aa8) at 0xc06bfdd3 = sysctl_root_handler_locked+0x83/frame 0xe8bc2a88 > sysctl_root(0,e8bc2ae8) at 0xc06bf744 = sysctl_root+0x144/frame 0xe8bc2ad8 > userland_sysctl(c759f9c0,e8bc2b60,3,0,0,0,bfbfdc5c,4,e8bc2bc0,0) at 0xc06bfb9d = userland_sysctl+0x12d/frame 0xe8bc2b30 > sys___sysctl(c759f9c0,e8bc2c00) at 0xc06bfa32 = sys___sysctl+0x52/frame 0xe8bc2bd0 > syscall(e8bc2ce8) at 0xc0980801 = syscall+0x2a1/frame 0xe8bc2cdc > Xint0x80_syscall() at 0xc096e45e = Xint0x80_syscall+0x2e/frame 0xe8bc2cdc > --- syscall (202, FreeBSD ELF32, sys___sysctl), eip = 0x2818541b, esp = 0xbfbfdbc8, ebp = 0xbfbfdbf0 --- > Uptime: 4m36s > panic: malloc: called with spinlock or critical section held > Uptime: 4m36s > panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /home/src/sys/cam/ata/ata_da.c:3382 I suspect that this is because we only stop the scheduler upon a panic if SMP is configured. Can you retest with the patch below applied? Index: sys/kern/kern_shutdown.c =================================================================== --- sys/kern/kern_shutdown.c (revision 312082) +++ sys/kern/kern_shutdown.c (working copy) @@ -713,6 +713,7 @@ CPU_CLR(PCPU_GET(cpuid), &other_cpus); stop_cpus_hard(other_cpus); } +#endif /* * Ensure that the scheduler is stopped while panicking, even if panic @@ -719,7 +720,6 @@ * has been entered from kdb. */ td->td_stopsched = 1; -#endif bootopt = RB_AUTOBOOT; newpanic = 0; From owner-freebsd-stable@freebsd.org Fri Jan 13 20:40:18 2017 Return-Path: Delivered-To: freebsd-stable@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 A2418CAE723 for ; Fri, 13 Jan 2017 20:40:18 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: from mail-vk0-x244.google.com (mail-vk0-x244.google.com [IPv6:2607:f8b0:400c:c05::244]) (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 5B4171A3B for ; Fri, 13 Jan 2017 20:40:18 +0000 (UTC) (envelope-from jlehen@gmail.com) Received: by mail-vk0-x244.google.com with SMTP id 23so4588450vkc.2 for ; Fri, 13 Jan 2017 12:40:18 -0800 (PST) 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=wMPrQifEYljP26eH44RrEIbTQaM88y2JLOwa50HAHw4=; b=k6DOSxZNPzdVQlf2pqn66PWwNRuiF0Vrp/sGwCGUhvxIjLiv0x8XsT6Ge9+cYj3YZb 0HqBVuUNwlmmLPuWh3wVyvF6UTtdid5179dAsylI6L9KMwVjOUSRaEFHD9i14yTHWjCT pYoWWnHm51Wml1ngftMxFkni8Y9pvp5FLvVmlnuVJkflH5Mei5i/1SUn6KMkKN0eLeU0 /K8iXFvQ9W5nV/ahph+jupDslROJ7rltHt7XtLcWjUwwtKQjpDZnALXO7tICGV6zf375 p4DjiJPVsg9BgEO44mNMUe+gqURcY79E8Ro9xC1IMJO0t+4pDXIfRq/vnVgbHIfyHquG pxLg== 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=wMPrQifEYljP26eH44RrEIbTQaM88y2JLOwa50HAHw4=; b=I9X40yv1ZMrM1aA+wAJcr97lPO0R7D3lUekwFBUpq9OncSotNptl+dOinIqe6zVj/8 Mcb5Kp85RTKbHJiVAprABp1ws4QGbqjsfnsoqVHLLcdN4jB4r5QMC/xjGaUQI8CsR71b B7t9asOF6oztCh2jmwxIUfks1juFVQgRIdQ2HM2bZPvePi9zD3UKp3uJZbkO7o9D5Pha qfbdZUhfzfJz7WkGQTuqWAJ4YcRMvFI+1INBk2xqX0lj7FpMgXGVRiQ5Dou1BSBeV5gu gBTcg3/zKfdjSUnjMYEK44UQih/N+I1F2C6kloBlL/9XOeCAyQ2EKVtH1AFwvQhhHaLC O+/w== X-Gm-Message-State: AIkVDXKANrmOb9dVtZMXVkDPJdHt6/bl8ZTS15A7BoF5nTYM6WK67IntUcJugp+i1TT1m1NzTDY/GP6sZrMb3A== X-Received: by 10.31.63.133 with SMTP id m127mr10873916vka.42.1484340016852; Fri, 13 Jan 2017 12:40:16 -0800 (PST) MIME-Version: 1.0 Sender: jlehen@gmail.com Received: by 10.103.13.5 with HTTP; Fri, 13 Jan 2017 12:40:16 -0800 (PST) In-Reply-To: References: From: Jeremie Le Hen Date: Fri, 13 Jan 2017 21:40:16 +0100 X-Google-Sender-Auth: jYBB5eCj1OWB1CZUWtjxRuhGVbE Message-ID: Subject: Re: Can't boot on ZFS -- /boot/zfsloader not found To: Steven Hartland Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 20:40:18 -0000 On Thu, Jan 12, 2017 at 10:55 PM, Steven Hartland wrote: > On 12/01/2017 21:12, Jeremie Le Hen wrote: > > Hey Steven, > > (Please cc: me on reply) > > On Thu, Jan 12, 2017 at 1:32 AM, Steven Hartlan > > The reason I'd recommend 512k for boot is to provide room for expansion > moving forward, as repartitioning to upgrade is a scary / hard thing to do. > Remember it wasn't long ago when it was well under 64k and that's what was > recommend, its not like with disk sizes these days you'll miss the extra > 384k ;-) > > Yeah, that's wise you're right. > > Boot to a live cd, I'd recommend mfsbsd, and make sure the boot loader was > written to ALL boot disks correctly e.g. > if you have a mirrored pool with ada0 and ada1: > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > > If this doesn't help the output from gpart show, uname -a and zpool status > would also be helpful. > > This is all assuming standard BIOS mode and not UEFI which is done > differently. > > I just use the installation media on an USB key and then drop to the > shell. This is a full FreeBSD running, so that's fine. > > % # gpart show ada0 > % => 40 312581728 ada0 GPT (149G) > % 40 1024 1 freebsd-boot (512K) > % 1064 8387840 2 freebsd-swap (4.0G) > % 8388904 304192864 3 freebsd-zfs (145G) > % > % # uname -a > % FreeBSD 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep > 29 01:43:23 UTC 2016 % % > root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > % > % # zpool status > % pool: zroot > % state: ONLINE > % scan: none requested > % config: > % > % NAME STATE READ > WRITE CKSUM > % zroot ONLINE 0 > 0 0 > % gptid/1c387d3b-d892-11e6-944b-f44d30620eeb ONLINE 0 > 0 0 > % > % errors: No known data errors > > Here are the steps to write the bootloader: > > % # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > % partcode written to ada0p1 > % bootcode written to ada0 > % # zpool get bootfs zroot > % NAME PROPERTY VALUE SOURCE > % zroot bootfs zroot local > > Two things spring to mind > > Idea 1: > Is your root fs actually your direct pool or is it actually /root off your > pool. > If so you want to run: > zpool set bootfs=zroot/root zroot That was it. My boot volume is "zroot/root" and I was just following brainlessly the doc which said to use "zroot". This didn't shock me because this at least points to the right pool > > Idea 2: > You mentioned in your original post and you used zfs send / recv to restore > the pool, so I wonder if your cache file is out of date. > > Try the following: > zpool export zroot > zpool import -R /mnt -o cachefile=/boot/zfs/zpool.cache zroot > cp /boot/zfs/zpool.cache /mnt/boot/zfs/zpool.cache > zpool set bootfs=zroot/root zroot I think that was wrong too, but this would probably have caused problems later in the boot I think. Anyway, thanks a lot for your help. I'll give a quick lifting to the wiki page. -jlh > > Regards > Steve -- Jeremie Le Hen jlh@FreeBSD.org From owner-freebsd-stable@freebsd.org Fri Jan 13 22:39:47 2017 Return-Path: Delivered-To: freebsd-stable@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 15133CAE66D for ; Fri, 13 Jan 2017 22:39:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0052.outbound.protection.outlook.com [104.47.41.52]) (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 C0FAE1E69 for ; Fri, 13 Jan 2017 22:39:45 +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_256_CBC_SHA384_P384) id 15.1.845.12; Fri, 13 Jan 2017 22:39:43 +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.0845.014; Fri, 13 Jan 2017 22:39:43 +0000 From: Rick Macklem To: Daniel Braniss , Karl Young CC: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD Thread-Topic: NFS and amd on older FreeBSD Thread-Index: AQHSbXQQS5PHP1jaNEG6/WhpTp9cAKE3AJPb Date: Fri, 13 Jan 2017 22:39:43 +0000 Message-ID: References: <20170111234737.GK26386@mailboy.kipshouse.net> <20170112190125.GR26386@mailboy.kipshouse.net>, <343F8AE3-1428-4B0E-A3C3-C60D5B6DB905@cs.huji.ac.il> In-Reply-To: <343F8AE3-1428-4B0E-A3C3-C60D5B6DB905@cs.huji.ac.il> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: 4658c535-73a7-4ad1-e2f9-08d43c0511a4 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0190; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0190; 7:OZ24RJ9VXmrLgvIjD3cZtijmA2GqQbAG7gq/d96dbUjhtRuUO3/ohe+wDOy2r7XavU06+DmGL9QtQ+lw0KqUbc5qLYwx/suQX4pi9rOPc3qNrSZ9QziiQgiY67jRH7IEJ8s4oIoJYVF1IV5qCwdOk+oh9gjum7j/UVtKa4+8JwJNeQLLkrJGr79/ylebzBxsn4aVpZUUx5xK+vT/x9ha9ReFeNK349iepQLPSSznL8RNID9exnwsH+0DYibg1VrFLq8whO8nabHlh6Zvz01h20mXibdFDJ3iRfz2YeCstYSZ6lC5Usq3PXDpJMVLROICELrO9FkZ08uU/jQ9IVtmyi7lL1eNRoixx+hpObrSdwSz6vda07s4xiN6U9YNOdr2nESKe7SsiDQODWuYA3CU+DBJHHN89TCU7oJ6HXaXRUAIkHx5tly7RRjlJeAym8LeWkxoZd0C/DKoQ4MK1stKIA== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(788757137089)(75325880899374); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(6072148); SRVR:YTXPR01MB0190; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0190; x-forefront-prvs: 018632C080 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(24454002)(189002)(377454003)(199003)(74316002)(93886004)(6436002)(6506006)(229853002)(77096006)(81166006)(38730400001)(3660700001)(81156014)(4326007)(68736007)(106116001)(105586002)(106356001)(8936002)(8676002)(2906002)(305945005)(86362001)(101416001)(6306002)(122556002)(50986999)(54356999)(55016002)(76176999)(102836003)(3280700002)(2950100002)(92566002)(33656002)(189998001)(97736004)(9686003)(7696004)(5660300001)(2900100001)(5001770100001)(74482002)(27001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0190; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2017 22:39:43.3503 (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-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 22:39:47 -0000 Do you have exactly the same export options specified in /etc/exports for the 9.3 server as the 6.3 one? Beyond that, I can only suggest capturing packets when the automount fails and looking at them in wireshark to see what is actually happening. rick ________________________________________ From: owner-freebsd-stable@freebsd.org o= n behalf of Daniel Braniss Sent: Friday, January 13, 2017 3:06:56 AM To: Karl Young Cc: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD > On 12 Jan 2017, at 21:01, Karl Young wrote: > > Daniel Braniss(danny@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >> >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: >>> >>> >>>> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >>>> >>>> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. >>>> These hosts run test scripts that access files that are stored on >>>> FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS >>>> >>>> >>>> On the 7.2 hosts, I can see the exported directory: >>>> >>>> $ showmount -e 6.3-host >>>> Exports list on 6.3-host >>>> /data Everyone >>>> >>>> And access it with amd >>>> >>>> $ ls -l /net/6-3.host/data >>>> >>>> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >>>> drwxr-xr-x 4586 root wheel 83968 Nov 2 04:50 home >>>> >>>> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's >>>> old, but it's the best I can do for now). >>>> >>>> I export the /data directory on the 9.3 system, and I can see it on my >>>> 7.2 hosts. >>>> >>>> $ showmount -e 9.3-host >>>> Exports list on 9.3-host: >>>> /data Everyone >>>> >>>> But I can't automount it: >>>> >>>> $ ls -l /net/9.3-host/data >>>> ls: /net/9.3-host/data: No such file or directory >>>> >>>> If I manually mount the exported directory, it works: >>>> >>>> $ sudo mount -t nfs 9.3-host:/data /mnt/data/ >>>> $ mount | grep nfs >>>> 9.3-host:/data on /mnt/data (nfs) >>>> >>>> $ ls -l /mnt/data >>>> total 4 >>>> drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 >>>> >>>> I've spent some time on Google, but haven't found a solution. I reali= ze >>>> these are very old versions, but I'm not in a position to upgrade them >>>> right now. My last resort will be to use /etc/fstab to do the NFS >>>> mount, but I'd rather avoid that if I can. >>>> >>>> Thanks for any pointers on how to resolve this. >>>> >>>> -karl >>>> >>>> >>> >>> if you changed the export file on the server after you tried to mount i= n on the client, >>> and will not realise this, if that=92s the case, usually rebooting the = client helps. >>> >> s/and/amd/ ^%$# hate spell checkers >> > > Thanks Danny > > I did try rebooting the client (and server) multiple times to no avail. what does amq say? you can, from another host do: amq -h client-host btw, I thing that nfs_server must also run on the client =85 I have nfs_server_enable=3DYES danny _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Sat Jan 14 00:07:42 2017 Return-Path: Delivered-To: freebsd-stable@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 DC933CAE5E1; Sat, 14 Jan 2017 00:07:42 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70D351AF1; Sat, 14 Jan 2017 00:07:42 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3v0fvZ4zWHz11x; Sat, 14 Jan 2017 01:07:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1484352454; x=1486944455; bh=jzvzgQxbA+in1ugFP2kuc6yEFkitcHn8dWS Fsf1WGNU=; b=F2XIec2ALUpSb4xkKCuzCDsagK61aqqc+x1nRoRv6DusTGnD6k4 wopfvQ4vSqvtTNYu6fjdvU+jk1oSs5ZG12+awkrd0uwKyFRL26eV6PnX7qwn+mRv 6UYu5nveOP2FoJrXaBCwZs6EnpkGPGFs2V084UtZuhhVJquatf/gBaWI= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id TAVPuYA8mmvk; Sat, 14 Jan 2017 01:07:34 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3v0fv20NQ0z11V; Sat, 14 Jan 2017 01:07:10 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3v0fv16bQ5zcQ; Sat, 14 Jan 2017 01:07:09 +0100 (CET) Received: from upc.si.94.140.92.23.dc.cable.static.telemach.net ([94.140.92.23]) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Sat, 14 Jan 2017 01:07:09 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 14 Jan 2017 01:07:09 +0100 From: Mark Martinec To: ports@freebsd.org, freebsd-stable@freebsd.org Subject: Does building linux packages under poudriere require linux compatibility emulation? Organization: Jozef Stefan Institute Message-ID: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 00:07:43 -0000 When building packages under poudriere on 11.0-RELEASE-p7 (from a command line in a terminal window) I'm noticing occasional streams of diagnostic: ELF binary type "3" not known. which seem to be related to building some linux packages (example below, parallel builds). Poudriere still reports success for these builds. The host where poudriere is running does not have linux.ko loaded. Does building such packages really require linuxilator configured on the build host ??? Mark [00:23:56] ====>> [02][00:00:00] Starting build of www/linux-c6-qt47-webkit [00:23:57] ====>> [13][00:00:00] Starting build of textproc/linux-c6-libxml2 ELF binary type "3" not known. ELF binary type "3" not known. [00:24:09] ====>> [19][00:00:28] Finished build of textproc/linux-c6-aspell: Success [00:24:11] ====>> [19][00:00:00] Starting build of devel/qt4-makeqpf [00:24:11] ====>> [11][00:00:24] Finished build of security/linux-c6-openssl-compat: Success ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:12] ====>> [11][00:00:00] Starting build of x11-toolkits/vte ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:16] ====>> [07][00:00:24] Finished build of graphics/linux-c6-glx-utils: Success ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:17] ====>> [07][00:00:00] Starting build of devel/qt4-qdoc3 ELF binary type "3" not known. ELF binary type "3" not known. [00:24:19] ====>> [13][00:00:22] Finished build of textproc/linux-c6-libxml2: Success [00:24:19] ====>> [13][00:00:00] Starting build of graphics/goocanvas [00:24:27] ====>> [10][00:02:26] Finished build of graphics/sdl_gfx: Success [00:24:29] ====>> [10][00:00:00] Starting build of multimedia/mjpegtools [00:24:34] ====>> [04][00:02:15] Finished build of devel/linux-c6-devtools: Success [00:24:35] ====>> [04][00:00:00] Starting build of devel/linux-c6-ncurses-base From owner-freebsd-stable@freebsd.org Sat Jan 14 09:18:29 2017 Return-Path: Delivered-To: freebsd-stable@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 523EDCACB51; Sat, 14 Jan 2017 09:18:29 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::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 01B061BB5; Sat, 14 Jan 2017 09:18:29 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id s140so77633060qke.0; Sat, 14 Jan 2017 01:18:28 -0800 (PST) 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=CXlg7pFNdWbg1DYWX9jUBkWNC71YFdSqBGnTE3QTxHM=; b=aRYf8qb0umin3e7w2busjOmSun+7vWPqy1yGRBA1/Z92brGtVXpQtHPjxvzkTPleO+ +pmfl41rgmtbBJAo5SFCIohCrWcSX1nGtjrF9bCuKdsMmXv+gZ07C7vHFTpN6rSYNica bQ17W1Jb4dDhDI6e3aTQtrBsiteB8o1apHhugKmPjqC+iBHpJAboBqRjG5zF/jJ9HY6a 04Gf9nTW1/iKYAxsVoTOMSRgC4lJf5tL9G2axgyQVoJyPsChQ3qRxRJnwrssIJjVLOxK wlDEDf7+13jZKsyPv/muo5IfF6Cl+ne9wfrJdQQk2J+BMnXL9ONWIw89GvMuak0Fn3Su x5Og== 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=CXlg7pFNdWbg1DYWX9jUBkWNC71YFdSqBGnTE3QTxHM=; b=nLCfPcbju5ybSZw+dgnEJnPIWPKmIZxO9kVkGGtqmijUG6gzIYkFbzrVOk0wXQm76v oXa/LTpyhe6b39Z4xYQJnk/AkjVusoNzkfSfza3gB7kEPlG4Z3u75ETzXIbU310pK3LG 69Xl/Q6/wOH2mTbpnpfHyw2OAwntikil54g0MTI0tbrsKzAoVb4WgFU0TJZlsCHkbOUL XCvDpHvpyWQeLhv0B7eY+cJLk3klAKdcJd89Tcu4piAZtxxChkMGdjkmAaThxRHD/g3w u6pVB0YWKpOkH63cG9qicReUBlRw7SqxxV/k8wX0+nGB1Bd4t7lWJPk0pRjYJOXqVu8Y a4HA== X-Gm-Message-State: AIkVDXLvM6CZQs13nIeCQRDyQY2RE6sWL/rk04VnD7vvN2z3IH+obT/VuQOQvq//su6LTixrH4292Q4avv/ZSQ== X-Received: by 10.55.17.27 with SMTP id b27mr24856499qkh.200.1484385508240; Sat, 14 Jan 2017 01:18:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.40.150 with HTTP; Sat, 14 Jan 2017 01:18:27 -0800 (PST) Received: by 10.55.40.150 with HTTP; Sat, 14 Jan 2017 01:18:27 -0800 (PST) In-Reply-To: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> From: =?UTF-8?Q?Ren=C3=A9_Ladan?= Date: Sat, 14 Jan 2017 10:18:27 +0100 Message-ID: Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? To: Mark Martinec Cc: freebsd-stable@freebsd.org, "ports@freebsd.org Ports" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 09:18:29 -0000 Op 14 jan. 2017 01:07 schreef "Mark Martinec" : When building packages under poudriere on 11.0-RELEASE-p7 (from a command line in a terminal window) I'm noticing occasional streams of diagnostic: ELF binary type "3" not known. which seem to be related to building some linux packages (example below, parallel builds). Poudriere still reports success for these builds. The host where poudriere is running does not have linux.ko loaded. Does building such packages really require linuxilator configured on the build host ??? Mark I rhink the host wouldn't need the linuxolator for building the Linux packages, unless those packages run other Linux packages for their build. Ren=C3=A9 [00:23:56] =3D=3D=3D=3D>> [02][00:00:00] Starting build of www/linux-c6-qt4= 7-webkit [00:23:57] =3D=3D=3D=3D>> [13][00:00:00] Starting build of textproc/linux-c= 6-libxml2 ELF binary type "3" not known. ELF binary type "3" not known. [00:24:09] =3D=3D=3D=3D>> [19][00:00:28] Finished build of textproc/linux-c6-aspell: Success [00:24:11] =3D=3D=3D=3D>> [19][00:00:00] Starting build of devel/qt4-makeqp= f [00:24:11] =3D=3D=3D=3D>> [11][00:00:24] Finished build of security/linux-c6-openssl-compat: Success ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:12] =3D=3D=3D=3D>> [11][00:00:00] Starting build of x11-toolkits/vte ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:16] =3D=3D=3D=3D>> [07][00:00:24] Finished build of graphics/linux-c6-glx-utils: Success ELF binary type "3" not known. ELF binary type "3" not known. ELF binary type "3" not known. [00:24:17] =3D=3D=3D=3D>> [07][00:00:00] Starting build of devel/qt4-qdoc3 ELF binary type "3" not known. ELF binary type "3" not known. [00:24:19] =3D=3D=3D=3D>> [13][00:00:22] Finished build of textproc/linux-c6-libxml2: Success [00:24:19] =3D=3D=3D=3D>> [13][00:00:00] Starting build of graphics/goocanv= as [00:24:27] =3D=3D=3D=3D>> [10][00:02:26] Finished build of graphics/sdl_gfx= : Success [00:24:29] =3D=3D=3D=3D>> [10][00:00:00] Starting build of multimedia/mjpeg= tools [00:24:34] =3D=3D=3D=3D>> [04][00:02:15] Finished build of devel/linux-c6-d= evtools: Success [00:24:35] =3D=3D=3D=3D>> [04][00:00:00] Starting build of devel/linux-c6-ncurses-base _______________________________________________ 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" From owner-freebsd-stable@freebsd.org Sat Jan 14 09:38:36 2017 Return-Path: Delivered-To: freebsd-stable@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 5ADF4CAD165; Sat, 14 Jan 2017 09:38:36 +0000 (UTC) (envelope-from annulen@yandex.ru) Received: from forward2h.cmail.yandex.net (forward2h.cmail.yandex.net [87.250.230.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 D28B31823; Sat, 14 Jan 2017 09:38:35 +0000 (UTC) (envelope-from annulen@yandex.ru) Received: from mxback2m.mail.yandex.net (mxback2m.mail.yandex.net [IPv6:2a02:6b8:0:2519::10b]) by forward2h.cmail.yandex.net (Yandex) with ESMTP id C098820C4A; Sat, 14 Jan 2017 12:38:30 +0300 (MSK) Received: from web13m.yandex.ru (web13m.yandex.ru [37.140.138.104]) by mxback2m.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Qk5BFQNFG3-cURCmk5a; Sat, 14 Jan 2017 12:38:30 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1484386710; bh=AhgVN6Ec1WEqys6tHvpNwLCF0p4JzkdvSEYC2bKzuM8=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=IioUJeI063mXy+H4G7bsVfr4JS59vO45e0vZo34JkxLnbK23unjcH6WAQ82EKpqky PajlbbwZLTbfYI0N9xplB2w32vyC2JHP0eoFqwvJ1PXyqclcNGtN8tRCQ4MCm5xFuw BF0QaKcNDWGAQ4coBhoKcadtn5eSQxYLR3PB5Bsc= Authentication-Results: mxback2m.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by web13m.yandex.ru with HTTP; Sat, 14 Jan 2017 12:38:30 +0300 From: Konstantin Tokarev To: =?utf-8?B?UmVuw6kgTGFkYW4=?= , Mark Martinec Cc: "ports@freebsd.org Ports" , "freebsd-stable@freebsd.org" In-Reply-To: References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? MIME-Version: 1.0 Message-Id: <3658201484386710@web13m.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 14 Jan 2017 12:38:30 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 09:38:36 -0000 14.01.2017, 12:18, "René Ladan" : > Op 14 jan. 2017 01:07 schreef "Mark Martinec" > : > > When building packages under poudriere on 11.0-RELEASE-p7 (from a command > line in a terminal window) I'm noticing occasional streams of diagnostic: > >   ELF binary type "3" not known. > > which seem to be related to building some linux packages (example below, > parallel builds). Poudriere still reports success for these builds. > > The host where poudriere is running does not have linux.ko loaded. > > Does building such packages really require linuxilator configured > on the build host ??? For example, your log includes building qdoc3. It is likely to be used in build process of other Qt packages. > >    Mark > > I rhink the host wouldn't need the linuxolator for building the Linux > packages, unless those packages run other Linux packages for their build. > > René > > [00:23:56] ====>> [02][00:00:00] Starting build of www/linux-c6-qt47-webkit > [00:23:57] ====>> [13][00:00:00] Starting build of textproc/linux-c6-libxml2 > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:09] ====>> [19][00:00:28] Finished build of > textproc/linux-c6-aspell: Success > [00:24:11] ====>> [19][00:00:00] Starting build of devel/qt4-makeqpf > [00:24:11] ====>> [11][00:00:24] Finished build of > security/linux-c6-openssl-compat: Success > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:12] ====>> [11][00:00:00] Starting build of x11-toolkits/vte > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:16] ====>> [07][00:00:24] Finished build of > graphics/linux-c6-glx-utils: Success > ELF binary type "3" not known. > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:17] ====>> [07][00:00:00] Starting build of devel/qt4-qdoc3 > ELF binary type "3" not known. > ELF binary type "3" not known. > [00:24:19] ====>> [13][00:00:22] Finished build of > textproc/linux-c6-libxml2: Success > [00:24:19] ====>> [13][00:00:00] Starting build of graphics/goocanvas > [00:24:27] ====>> [10][00:02:26] Finished build of graphics/sdl_gfx: Success > [00:24:29] ====>> [10][00:00:00] Starting build of multimedia/mjpegtools > [00:24:34] ====>> [04][00:02:15] Finished build of devel/linux-c6-devtools: > Success > [00:24:35] ====>> [04][00:00:00] Starting build of > devel/linux-c6-ncurses-base > _______________________________________________ > 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" > _______________________________________________ > 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" -- Regards, Konstantin From owner-freebsd-stable@freebsd.org Sat Jan 14 11:40:21 2017 Return-Path: Delivered-To: freebsd-stable@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 DE772CAF1FC for ; Sat, 14 Jan 2017 11:40:21 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C4401F3B; Sat, 14 Jan 2017 11:40:21 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v0EBeBYX038194 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 14 Jan 2017 12:40:11 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: markj@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v0EBe2a0039176; Sat, 14 Jan 2017 18:40:02 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: stable/11 debugging kernel unable to produce crashdump To: Mark Johnston References: <587928B3.2050607@grosbein.net> <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com> Cc: FreeBSD Stable From: Eugene Grosbein Message-ID: <587A0E12.7070205@grosbein.net> Date: Sat, 14 Jan 2017 18:40:02 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 11:40:22 -0000 > I suspect that this is because we only stop the scheduler upon a panic > if SMP is configured. Can you retest with the patch below applied? > > Index: sys/kern/kern_shutdown.c > =================================================================== > --- sys/kern/kern_shutdown.c (revision 312082) > +++ sys/kern/kern_shutdown.c (working copy) > @@ -713,6 +713,7 @@ > CPU_CLR(PCPU_GET(cpuid), &other_cpus); > stop_cpus_hard(other_cpus); > } > +#endif > > /* > * Ensure that the scheduler is stopped while panicking, even if panic > @@ -719,7 +720,6 @@ > * has been entered from kdb. > */ > td->td_stopsched = 1; > -#endif > > bootopt = RB_AUTOBOOT; > newpanic = 0; > > Indeed, my router is uniprocessor system and your patch really solves the problem. Now kernel generates crashdump just fine in case of panic. Please commit the fix, thanks! Eugene Grosbein From owner-freebsd-stable@freebsd.org Sat Jan 14 12:41:57 2017 Return-Path: Delivered-To: freebsd-stable@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 8ADD8CAEF78; Sat, 14 Jan 2017 12:41:57 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 28C461C78; Sat, 14 Jan 2017 12:41:56 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v0ECfluV038482 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 14 Jan 2017 13:41:48 +0100 (CET) (envelope-from egrosbein@rdtc.ru) X-Envelope-From: egrosbein@rdtc.ru X-Envelope-To: freebsd-stable@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v0ECff2U080700; Sat, 14 Jan 2017 19:41:42 +0700 (KRAT) (envelope-from egrosbein@rdtc.ru) To: FreeBSD Stable Cc: freebsd-ipfw@FreeBSD.org From: Eugene Grosbein Subject: kernel ipfw rlock/wlock panic in stable/11 X-Enigmail-Draft-Status: N1110 Message-ID: <587A1C85.90205@rdtc.ru> Date: Sat, 14 Jan 2017 19:41:41 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) * 0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 12:41:57 -0000 Hi! My 11.0-STABLE/i386 r311924 debugging kernel catches _rm_assert(rm, RA_RLOCKED, file, line) in sys/netpfil/ipfw:ipfw_chk() function trying to do IPFW_PF_RUNLOCK(chain) on an object that was not rlocked but wlocked: #17 0xc06b0255 in _rm_runlock_debug (rm=0xc0bce37c, file=, line=) at /home/src/sys/kern/kern_rmlock.c:690 690 _rm_assert(rm, RA_RLOCKED, file, line); (kgdb) p rm $1 = (struct rmlock *) 0xc0bce37c (kgdb) p *rm $2 = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 50528256, lo_data = 0, lo_witness = 0xc50c6a20}, rm_writecpus = { __bits = 0xc0bce38c}, rm_activeReaders = {lh_first = 0x0}, _rm_lock = {_rm_wlock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, _rm_lock_mtx = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, _rm_lock_sx = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, sx_lock = 4}}} Full kgdb script here: http://www.grosbein.net/freebsd/crash/20170114/kgdb.log There are vmcore, kernel.debug and crashinfo available in the same directory. Is it ipfw bug of assertion bug? From owner-freebsd-stable@freebsd.org Sat Jan 14 12:41:58 2017 Return-Path: Delivered-To: freebsd-stable@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 174CBCAEF7D; Sat, 14 Jan 2017 12:41:58 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AAACB1D67; Sat, 14 Jan 2017 12:41:56 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v0ECfp7N038485 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 14 Jan 2017 13:41:52 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-stable@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v0ECflhV080761; Sat, 14 Jan 2017 19:41:48 +0700 (KRAT) (envelope-from eugen@grosbein.net) To: FreeBSD Stable Cc: freebsd-ipfw@FreeBSD.org From: Eugene Grosbein Subject: kernel ipfw rlock/wlock panic in stable/11 X-Enigmail-Draft-Status: N1110 Message-ID: <587A1C8B.80301@grosbein.net> Date: Sat, 14 Jan 2017 19:41:47 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 12:41:58 -0000 Hi! My 11.0-STABLE/i386 r311924 debugging kernel catches _rm_assert(rm, RA_RLOCKED, file, line) in sys/netpfil/ipfw:ipfw_chk() function trying to do IPFW_PF_RUNLOCK(chain) on an object that was not rlocked but wlocked: #17 0xc06b0255 in _rm_runlock_debug (rm=0xc0bce37c, file=, line=) at /home/src/sys/kern/kern_rmlock.c:690 690 _rm_assert(rm, RA_RLOCKED, file, line); (kgdb) p rm $1 = (struct rmlock *) 0xc0bce37c (kgdb) p *rm $2 = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 50528256, lo_data = 0, lo_witness = 0xc50c6a20}, rm_writecpus = { __bits = 0xc0bce38c}, rm_activeReaders = {lh_first = 0x0}, _rm_lock = {_rm_wlock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, _rm_lock_mtx = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, _rm_lock_sx = {lock_object = {lo_name = 0xc0a802a2 "IPFW static rules", lo_flags = 16842752, lo_data = 0, lo_witness = 0x0}, sx_lock = 4}}} Full kgdb script here: http://www.grosbein.net/freebsd/crash/20170114/kgdb.log There are vmcore, kernel.debug and crashinfo available in the same directory. Is it ipfw bug of assertion bug? From owner-freebsd-stable@freebsd.org Sat Jan 14 12:42:23 2017 Return-Path: Delivered-To: freebsd-stable@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 84818CAE059; Sat, 14 Jan 2017 12:42:23 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::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 4AA5D1F8C; Sat, 14 Jan 2017 12:42:23 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by mail-io0-x235.google.com with SMTP id l66so62900571ioi.1; Sat, 14 Jan 2017 04:42:23 -0800 (PST) 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=5pjns3GZyBe38efGcNGuiBHr9WOilCPzOPSplQNVZ4o=; b=toYzAUypAo3fzsOhecWAcbWqH16wg/1hJpbQJb6LKoatxRiOQcX0AfwgfZYzOgljt3 V0ut3TTCg1U8t+SlVKPQztY3N0kCW3mVyEtYUKFUZ4x81nNhGIWHH1tomy3bgFMpT0wu Vg/gqkJGaJyNjFUHenHPhMEGe1WUlTMnGQySV3Q+8h7aM5yRXOzJanbSBcGzKXV1FIEO wH3N+0DNQU6QyrsKCU+XF8o5IdsdEJGagTPnnFC+xaZsbDJiwcRAZ+qk/Y95ZUA69Deg m4NoQb9MlpyD4LkUOBkufzeI0iIy0WG9jso9uTLFXDzhf0p7/UY2Oaxkps28wbOhpRgA FYcw== 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=5pjns3GZyBe38efGcNGuiBHr9WOilCPzOPSplQNVZ4o=; b=hbGEBRDyHvXt9xmNIYCO78br8qTR+wlqPU0oV5gympm4EcTejRC2Ue0PDbW8iquVOl EwbVJyIYzXW2B1Y9vHz4k96QAChmR3XbHVXGDTPos7GRLTLfd0801+q2vQJ1roga7dzO rFjdcxVZO6V6DMC2eFbKk8Wh+b2eHBcwVzh9Uzyj7R4uqMc7zsilwvi4BmgbEC/iZWC7 I2SFzm85MCo5L7k+XXuqHfVyPQsycOLMgiFU+8/hPMzzZtGNVWU6U+7U3uEpi3leTq8l PZE6sZhx57O6vMbIJ5LfCJRx0T2xKCqoMaZq/1HROD8KjxPe736AXw6dJ03Gg68ghdaT cS8g== X-Gm-Message-State: AIkVDXLqTvTd6A6w8leEftPO34yZB07vLOq1yulJ5Cq88XJgRq1u3u6x2QZb0+MEIWJwbl/JSBBii5n5nB+8dQ== X-Received: by 10.107.2.138 with SMTP id 132mr7563726ioc.67.1484397741519; Sat, 14 Jan 2017 04:42:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.192.138 with HTTP; Sat, 14 Jan 2017 04:42:20 -0800 (PST) In-Reply-To: <3658201484386710@web13m.yandex.ru> References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> <3658201484386710@web13m.yandex.ru> From: Brandon Allbery Date: Sat, 14 Jan 2017 12:42:20 +0000 Message-ID: Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? To: Konstantin Tokarev Cc: =?UTF-8?Q?Ren=C3=A9_Ladan?= , Mark Martinec , "ports@freebsd.org Ports" , "freebsd-stable@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-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 12:42:23 -0000 On Sat, Jan 14, 2017 at 9:38 AM, Konstantin Tokarev wrote: > 14.01.2017, 12:18, "Ren=C3=A9 Ladan" : > > Op 14 jan. 2017 01:07 schreef "Mark Martinec" < > Mark.Martinec+freebsd@ijs.si > >> : > > When building packages under poudriere on 11.0-RELEASE-p7 (from a comma= nd > > line in a terminal window) I'm noticing occasional streams of diagnosti= c: > > > > ELF binary type "3" not known. > > > > which seem to be related to building some linux packages (example below= , > > parallel builds). Poudriere still reports success for these builds. > > > > The host where poudriere is running does not have linux.ko loaded. > > > > Does building such packages really require linuxilator configured > > on the build host ??? > > For example, your log includes building qdoc3. It is likely to be used in > build process of other Qt packages. qmake, moc, various utilities for maintaining Qt object registries... there will be a lot of build tools, and you would need to force them to build native instead of linux if you wanted to get away with not having the linuxulator installed. (This will be hard if they are part of another build that needs to be linux.) Same applies to gtk and dependents. And their respective upstreams likely have no interest in what amounts to a cross-compilation setup: too much difficult (and difficult for them to test) work, very little demand. --=20 brandon s allbery kf8nh sine nomine associate= s allbery.b@gmail.com ballbery@sinenomine.ne= t unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.ne= t From owner-freebsd-stable@freebsd.org Sat Jan 14 14:11:46 2017 Return-Path: Delivered-To: freebsd-stable@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 C3922CAFFF9; Sat, 14 Jan 2017 14:11:46 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay116.isp.belgacom.be (mailrelay116.isp.belgacom.be [195.238.20.143]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 122661F2A; Sat, 14 Jan 2017 14:11:45 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2DoAgBOMXpY//s+sVteGwEBAQMBAQEJA?= =?us-ascii?q?QEBgzkBAQEBAR9QgRiNWHKRIicBlQSCC4YiAoIXQBgBAgEBAQEBAQFjKIRqAQU?= =?us-ascii?q?6HCMQCxgJJQ8qHgYTiQeyeYoQAQEBAQEFAQEBAQEjiyyKLAWbOpFSdJAGkmwfO?= =?us-ascii?q?IEnKgiFJYFIPTWJGgEBAQ?= X-IPAS-Result: =?us-ascii?q?A2DoAgBOMXpY//s+sVteGwEBAQMBAQEJAQEBgzkBAQEBAR9?= =?us-ascii?q?QgRiNWHKRIicBlQSCC4YiAoIXQBgBAgEBAQEBAQFjKIRqAQU6HCMQCxgJJQ8qH?= =?us-ascii?q?gYTiQeyeYoQAQEBAQEFAQEBAQEjiyyKLAWbOpFSdJAGkmwfOIEnKgiFJYFIPTW?= =?us-ascii?q?JGgEBAQ?= Received: from 251.62-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.62.251]) by relay.skynet.be with ESMTP; 14 Jan 2017 15:11:43 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id v0EEBgYg024344; Sat, 14 Jan 2017 15:11:43 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Sat, 14 Jan 2017 15:11:42 +0100 From: Tijl Coosemans To: Mark Martinec Cc: ports@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? Message-ID: <20170114151142.205b9b4b@kalimero.tijl.coosemans.org> In-Reply-To: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 14:11:46 -0000 On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec wrote: > When building packages under poudriere on 11.0-RELEASE-p7 (from a > command line in a terminal window) I'm noticing occasional streams of > diagnostic: > > ELF binary type "3" not known. > > which seem to be related to building some linux packages (example below, > parallel builds). Poudriere still reports success for these builds. > > The host where poudriere is running does not have linux.ko loaded. > > Does building such packages really require linuxilator configured > on the build host ??? To build a package, its dependencies need to be installed and on installation some packages may need to run certain commands and for linux packages these commands may be linux programs. So, yes, if you need to build linux packages the build host should have USE_LINUX=yes in /etc/rc.conf. From owner-freebsd-stable@freebsd.org Sat Jan 14 16:26:53 2017 Return-Path: Delivered-To: freebsd-stable@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 53945CAF919; Sat, 14 Jan 2017 16:26:53 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 326CE1EC9; Sat, 14 Jan 2017 16:26:53 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from mather.chumby.lan (c-71-63-91-41.hsd1.va.comcast.net [71.63.91.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 23DEB861; Sat, 14 Jan 2017 11:26:46 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? From: Paul Mather In-Reply-To: <20170114151142.205b9b4b@kalimero.tijl.coosemans.org> Date: Sat, 14 Jan 2017 11:26:45 -0500 Cc: Mark Martinec , ports@freebsd.org, freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <308E7994-9C4F-462F-B7AD-8CB88D00B4B5@gromit.dlib.vt.edu> References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> <20170114151142.205b9b4b@kalimero.tijl.coosemans.org> To: Tijl Coosemans X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 16:26:53 -0000 On Jan 14, 2017, at 9:11 AM, Tijl Coosemans wrote: > On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec = wrote: >> When building packages under poudriere on 11.0-RELEASE-p7 (from a=20 >> command line in a terminal window) I'm noticing occasional streams of >> diagnostic: >>=20 >> ELF binary type "3" not known. >>=20 >> which seem to be related to building some linux packages (example = below, >> parallel builds). Poudriere still reports success for these builds. >>=20 >> The host where poudriere is running does not have linux.ko loaded. >>=20 >> Does building such packages really require linuxilator configured >> on the build host ??? >=20 > To build a package, its dependencies need to be installed and on > installation some packages may need to run certain commands and for > linux packages these commands may be linux programs. So, yes, if you > need to build linux packages the build host should have USE_LINUX=3Dyes > in /etc/rc.conf. The only thing you need on the host is to have the linux kernel module = loaded. (You don't need to have any Linux packages installed there.) = The default setting in /usr/local/etc/poudriere.conf is to have = NOLINUX=3Dyes commented out, i.e., Linux support in Poudriere is enabled = unless you explicitly disable it. The easiest way to load the linux kernel module on the host for use with = Poudriere is to add it to the "kld_list" setting in /etc/rc.conf, e.g., kld_list=3D"linux" Cheers, Paul.= From owner-freebsd-stable@freebsd.org Sat Jan 14 18:40:11 2017 Return-Path: Delivered-To: freebsd-stable@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 A2784CAFBAE for ; Sat, 14 Jan 2017 18:40:11 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 670E11F3E for ; Sat, 14 Jan 2017 18:40:11 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cSTFI-0009jU-DQ for freebsd-stable@freebsd.org; Sat, 14 Jan 2017 21:40:08 +0300 Date: Sat, 14 Jan 2017 21:40:08 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org Subject: dev.cpu.0.freq/dev.cpu.0.freq_levels support on E5v4 Message-ID: <20170114184008.GA58505@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 18:40:11 -0000 I am have stable/11 and E5v4. I am don't see cpufreq support by sysctl: # sysctl dev.cpu.0 dev.cpu.0.cx_method: C1/hlt dev.cpu.0.cx_usage_counters: 61755 dev.cpu.0.cx_usage: 100.00% last 1us dev.cpu.0.cx_lowest: C2 dev.cpu.0.cx_supported: C1/1/1 dev.cpu.0.%parent: acpi0 dev.cpu.0.%pnpinfo: _HID=ACPI0007 _UID=0 dev.cpu.0.%location: handle=\_SB_.SCK0.CP00 _PXM=0 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: ACPI CPU # grep -i freq /var/run/dmesg.boot Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 350 Event timer "HPET1" frequency 14318180 Hz quality 340 Event timer "HPET2" frequency 14318180 Hz quality 340 Event timer "HPET3" frequency 14318180 Hz quality 340 Event timer "HPET4" frequency 14318180 Hz quality 340 Event timer "HPET5" frequency 14318180 Hz quality 340 Event timer "HPET6" frequency 14318180 Hz quality 340 Event timer "HPET7" frequency 14318180 Hz quality 340 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 est0: on cpu0 est1: on cpu1 est2: on cpu2 est3: on cpu3 est4: on cpu4 est5: on cpu5 est6: on cpu6 est7: on cpu7 est8: on cpu8 est9: on cpu9 est10: on cpu10 est11: on cpu11 est12: on cpu12 est13: on cpu13 est14: on cpu14 est15: on cpu15 est16: on cpu16 est17: on cpu17 est18: on cpu18 est19: on cpu19 est20: on cpu20 est21: on cpu21 est22: on cpu22 est23: on cpu23 Timecounter "TSC-low" frequency 1100023294 Hz quality 1000 How to enable cpufreq support for powerd? From owner-freebsd-stable@freebsd.org Sat Jan 14 19:27:07 2017 Return-Path: Delivered-To: freebsd-stable@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 23C88CAFA62; Sat, 14 Jan 2017 19:27:07 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay110.isp.belgacom.be (mailrelay110.isp.belgacom.be [195.238.20.137]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57EC614E4; Sat, 14 Jan 2017 19:27:05 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2CIBgCqenpY//s+sVtdGwEBAQMBAQEJA?= =?us-ascii?q?QEBgzkBAQEBAR9QgRiOSpEiJwGXD4YiAoIXRBQBAgEBAQEBAQFjKIRqAQU6HCM?= =?us-ascii?q?QCxgJJQ8qHgYTiQeyaIoFAQEBAQEFAQEBAQEjiyyKLAWbOpFSdJAGkmw2IYEnK?= =?us-ascii?q?giFJYFIPTWJGgEBAQ?= X-IPAS-Result: =?us-ascii?q?A2CIBgCqenpY//s+sVtdGwEBAQMBAQEJAQEBgzkBAQEBAR9?= =?us-ascii?q?QgRiOSpEiJwGXD4YiAoIXRBQBAgEBAQEBAQFjKIRqAQU6HCMQCxgJJQ8qHgYTi?= =?us-ascii?q?QeyaIoFAQEBAQEFAQEBAQEjiyyKLAWbOpFSdJAGkmw2IYEnKgiFJYFIPTWJGgE?= =?us-ascii?q?BAQ?= Received: from 251.62-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.62.251]) by relay.skynet.be with ESMTP; 14 Jan 2017 20:27:03 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id v0EJR24h029447; Sat, 14 Jan 2017 20:27:03 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Sat, 14 Jan 2017 20:27:02 +0100 From: Tijl Coosemans To: Mark Martinec Cc: ports@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Does building linux packages under poudriere require linux compatibility emulation? Message-ID: <20170114202702.44add0f1@kalimero.tijl.coosemans.org> In-Reply-To: <20170114151142.205b9b4b@kalimero.tijl.coosemans.org> References: <82be98ff42ad41e6ba73927eb54ed2ce@ijs.si> <20170114151142.205b9b4b@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 19:27:07 -0000 On Sat, 14 Jan 2017 15:11:42 +0100 Tijl Coosemans wrote: > On Sat, 14 Jan 2017 01:07:09 +0100 Mark Martinec wrote: >> When building packages under poudriere on 11.0-RELEASE-p7 (from a >> command line in a terminal window) I'm noticing occasional streams of >> diagnostic: >> >> ELF binary type "3" not known. >> >> which seem to be related to building some linux packages (example below, >> parallel builds). Poudriere still reports success for these builds. >> >> The host where poudriere is running does not have linux.ko loaded. >> >> Does building such packages really require linuxilator configured >> on the build host ??? > > To build a package, its dependencies need to be installed and on > installation some packages may need to run certain commands and for > linux packages these commands may be linux programs. So, yes, if you > need to build linux packages the build host should have USE_LINUX=yes > in /etc/rc.conf. That should be linux_enable="YES" in /etc/rc.conf, not USE_LINUX. From owner-freebsd-stable@freebsd.org Sat Jan 14 22:16:56 2017 Return-Path: Delivered-To: freebsd-stable@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 00CBACAFFCD for ; Sat, 14 Jan 2017 22:16:56 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 C4FF41156 for ; Sat, 14 Jan 2017 22:16:55 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x243.google.com with SMTP id 19so989878pfo.3 for ; Sat, 14 Jan 2017 14:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=wVYIAmGdT9hiKPP/DWv8JfMH0di/phvfpJBNvmWhuaQ=; b=oFcoNjzedHi/NFMHYoWH3LqrlD+ukHbN2gjA2qn1lcRLlkXUBZRC8G3xP7NIet+lIx edCdQ5Zc5qObJjyC8wErVVswix4z+IE78bTpgut7exHxrPCeiPI36WDBCU/pSMyrI0Zn hQ85BX7nlSwAa6U/B390wMN61+7HNTJz2QFmi61mwmFSBeAVeWwd9WDn0mc91tEXhjVb BZIZRfrLcAkyx3JWmLZK6CvIGwWEzqbe1Z+oOjdhbYBkG1j6D5Zkys3iz/OLIPsNAcFr ixbzwXDUjNtWdrmbYdE2ukSwEOWzq/6ZkdiEi0HWoLPss7MkHvIOXvtnV5Kbv4LTfyUF BQ7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=wVYIAmGdT9hiKPP/DWv8JfMH0di/phvfpJBNvmWhuaQ=; b=gR7zPg6SDI46m+WaxkTmRr6OUiH4TSgeXEFF/8zyWx1GAMhN3gdzjhG/BIZiNEpuqU sJnpFyC/K6H1409r+Brw+fhq+T+BT8vQqcNSBodvdqwfBCTSnjKhxrWf4bT9W6vqhf0x 9Yj4LuAVB7pcPzXBM3AyBOLCfBHkzWxE04bdZOCIUTFC45Nis4E/tOZw3eRerNRnJMAy aX3Gc0N+6Kr5nbYyhCxIci+svKhW7lVfgvjE0mCb3a/qlvhpK7zCwfmnq0Qu6/Bqfttn 06d3SzqhOjeuKSJTRxreNp+0qjmxes/iv5UCaxnqLXJ7SeNph7tFnnigDYkxuDnKNION OWcw== X-Gm-Message-State: AIkVDXKOJA7reLNUv9d/0HDhNDVX5o9FhMhUtGW6xvhv1u4ayrVZAx7OpTBP4JRQiBmijA== X-Received: by 10.99.116.22 with SMTP id p22mr31343190pgc.161.1484432215413; Sat, 14 Jan 2017 14:16:55 -0800 (PST) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id w125sm37285678pfb.8.2017.01.14.14.16.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Jan 2017 14:16:54 -0800 (PST) Sender: Mark Johnston Date: Sat, 14 Jan 2017 14:16:53 -0800 From: Mark Johnston To: Eugene Grosbein Cc: FreeBSD Stable Subject: Re: stable/11 debugging kernel unable to produce crashdump Message-ID: <20170114221653.GC18065@raichu> References: <587928B3.2050607@grosbein.net> <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com> <587A0E12.7070205@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <587A0E12.7070205@grosbein.net> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 22:16:56 -0000 On Sat, Jan 14, 2017 at 06:40:02PM +0700, Eugene Grosbein wrote: > > > I suspect that this is because we only stop the scheduler upon a panic > > if SMP is configured. Can you retest with the patch below applied? > > > > Index: sys/kern/kern_shutdown.c > > =================================================================== > > --- sys/kern/kern_shutdown.c (revision 312082) > > +++ sys/kern/kern_shutdown.c (working copy) > > @@ -713,6 +713,7 @@ > > CPU_CLR(PCPU_GET(cpuid), &other_cpus); > > stop_cpus_hard(other_cpus); > > } > > +#endif > > > > /* > > * Ensure that the scheduler is stopped while panicking, even if panic > > @@ -719,7 +720,6 @@ > > * has been entered from kdb. > > */ > > td->td_stopsched = 1; > > -#endif > > > > bootopt = RB_AUTOBOOT; > > newpanic = 0; > > > > > > Indeed, my router is uniprocessor system and your patch really solves the problem. > Now kernel generates crashdump just fine in case of panic. Please commit the fix, thanks! Thanks, committed as r312199.