From owner-freebsd-stable@freebsd.org Sun Mar 25 18:40:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C0EDF622F4; Sun, 25 Mar 2018 18:40:39 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 061A473286; Sun, 25 Mar 2018 18:40:38 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id B4B0F5A9F16; Sun, 25 Mar 2018 18:40:32 +0000 (UTC) Date: Sun, 25 Mar 2018 18:40:32 +0000 From: Brooks Davis To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Subject: Calling nxge(4) users Message-ID: <20180325184032.GA42437@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 25 Mar 2018 18:40:39 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE adapters has obvious bugs (by inspection) and it doesn't appear the company exists any more. We'd like to see if there are any significant users of this device and plan to remove it from FreeBSD-12 if not. -- Brooks --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJat+0fAAoJEKzQXbSebgfAwloIAKTzwact5dMn4JkLwJLKjdSk 18t75i4Exf5xjIulqxnSTo7sB02LJ/VT2XC043UeiyZDJRSMZz+kk0mDukMFhSAp 7VDOiDrNpClA6s62tUxxmHJXRY2rxhKgGTXsKIE+HZiYtxqIKGgbx+S9eiJWO31K Ty0Rva22BwBKQMpnxjWdaWrVssaNIertj1E8WGPBg8OREy4Q5XwRoMTBq8jF3g+d iAb2tMeQqJTttOt8dsgyxSlG1MAmZguo8rhLL069AqKXhtWME1ufac9AgcTSJILm e0k+LmrluaUuvIlox1wqs2DdNRbx3J6p/KeJjUZYLBJvu6FMg1F0Me0dti1URfg= =mbr2 -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-stable@freebsd.org Sun Mar 25 19:29:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18CFCF6666B; Sun, 25 Mar 2018 19:29:43 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 9DCC4751D3; Sun, 25 Mar 2018 19:29:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id x5so10014540vkd.7; Sun, 25 Mar 2018 12:29:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Wa9EnUkXPtExYq8S4Iauhf8G5DUxbsrtd5JNTE091Uk=; b=CHJy5Y79hdnxhqKjsC0UjMtPih5NgY0hsl096cbPXBXefcQFLyTm7gzyzgGLlk9odS lwNhD6kHqs+rcbsWfx5SCqZbNjNe0MqcmR24y+QjYqzxZgoEQw7TzUIdNY2kRGHnftyo YvptbqysG0Ed6IaEW/ppbLI/sVWPcGBLyWROtGk/AmgofzcaMd+aFPRCXUcNgueVd1K+ FtDOwubwKcbs+f7ULMMR+/i9afCE78RJljL8iRpIKOtbqoDegmNWYFTsrvPK+O/WVwbw Arj1ClSTkeEwgr4jf+e0L4SBWzDjkNxjKjMt1Db0A78YBxZgjyX0kqiWyoMDSd5Xrw2w s1bQ== 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=Wa9EnUkXPtExYq8S4Iauhf8G5DUxbsrtd5JNTE091Uk=; b=gi5lPeHclq4j/SEhqzaTK5w/wBieI0wv0uW2VuYxtPIeyrctfxkKb/kxpJzyOHu0Fc nCrWZhzLurjQR1ZXmEiRCpJcKOvpqxZj4A8VIsmNZkHMZq+r3sI9K4H21uvrEZ5amKGB SLlRX8S5PWSft3zrdYhFLx3APtibLZ5p/NhM0B8Ji0y5WSpFn8XeP1Fz7xD/L8YvIs2V xsbmosFL5aifZKTlNKxnaQTd+tWYfLf6NB7ZksUd3Nj6Ij9SMKCMJHg2qjBCSYrUW4bY MVVd/QP3TZyuPDSKOI8tRE+WWUwTr0xTlFJHDiAu9pLk6UA8utAx5ubzLJbnyIkXFAqI mIzg== X-Gm-Message-State: AElRT7HyljrX1kF9HMIBH1kSp05Xi5SP3pjkoVomRBtlzbw8nRT6yeNW shnwAj8mZw99APnubp7tv+5/SNfX0q5zrv5vi+n2cXlA X-Google-Smtp-Source: AG47ELscoeN6uNZwthvZgzf26PSQ+IspF5/0+11qMJqSt81jhVr/zzkt3D6ag9WOzkRyOG3MshjhWtB3LqMjOR5nsas= X-Received: by 10.31.252.68 with SMTP id a65mr21416873vki.78.1522006181734; Sun, 25 Mar 2018 12:29:41 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.91.5 with HTTP; Sun, 25 Mar 2018 12:29:41 -0700 (PDT) In-Reply-To: <20180325184032.GA42437@spindle.one-eyed-alien.net> References: <20180325184032.GA42437@spindle.one-eyed-alien.net> From: Kevin Oberman Date: Sun, 25 Mar 2018 12:29:41 -0700 X-Google-Sender-Auth: -D3f7Cby-sDa1Q_Pu1_RBJ_2imw Message-ID: Subject: Re: Calling nxge(4) users To: Brooks Davis Cc: FreeBSD-STABLE Mailing List , freebsd-net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 25 Mar 2018 19:29:43 -0000 On Sun, Mar 25, 2018 at 11:40 AM, Brooks Davis wrote: > The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > adapters has obvious bugs (by inspection) and it doesn't appear the > company exists any more. We'd like to see if there are any significant > users of this device and plan to remove it from FreeBSD-12 if not. > > -- Brooks > Just for the record, Neterion was acquired by Exar, an old-line hybrid IC company in 2010 and Exar was acquired last year by MaxLinear. Looks like Exar bought them for some of their tech and killed off the Ethernet products. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Sun Mar 25 20:09:31 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A91CF6927F; Sun, 25 Mar 2018 20:09:31 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E97576545; Sun, 25 Mar 2018 20:09:30 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w2PK9RgI043534; Sun, 25 Mar 2018 13:09:27 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w2PK9Rjk043533; Sun, 25 Mar 2018 13:09:27 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803252009.w2PK9Rjk043533@pdx.rh.CN85.dnsmgr.net> Subject: Re: Calling nxge(4) users In-Reply-To: <20180325184032.GA42437@spindle.one-eyed-alien.net> To: Brooks Davis Date: Sun, 25 Mar 2018 13:09:27 -0700 (PDT) CC: freebsd-stable@freebsd.org, freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 25 Mar 2018 20:09:31 -0000 > The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > adapters has obvious bugs (by inspection) and it doesn't appear the > company exists any more. We'd like to see if there are any significant > users of this device and plan to remove it from FreeBSD-12 if not. > > -- Brooks Neterion has been acquired by exar. https://www.eetimes.com/document.asp?doc_id=1173009 They have the datasheet for the Xframe-I here: https://www.exar.com/ds/xframedatasheet.pdf The cards appear to be readily avaliable on ebay. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-stable@freebsd.org Mon Mar 26 09:13:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8250DF554CD; Mon, 26 Mar 2018 09:13:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 322F1730C7; Mon, 26 Mar 2018 09:13:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 434A620D75; Mon, 26 Mar 2018 05:13:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 26 Mar 2018 05:13:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=lHIJqXJ14/Q9jG4BAxZLvIxeEW5Wy rJlxjdcDG4KxM4=; b=RVShMdHffo1ScfzU2I44IVkmB5m++N/N2lA2f3EOsnNQ3 yBf7N5rAJG/RjUvM+cB47AbdtIdaJIMmYRf/Qe+eeXMzFkv0tbxcrr8bmAMCCJev mDjUjrDjPMreqZweZj2BPwmV57Wud2fnqLb/qKQEG5Wjso8QEyeoN3QoduxLR5Z/ WKZ49yP+axz+4U+jSiDrjF2jGjAOUvvCQOqhJAU3vq3SVpxrtrXb4j/3YV0REdDN TAO05JQ457wawb0u2eUD4Nv5D8lf7OzUpSnXVNOiE47UG24II5rwrQytzrDYqAVe oIOK5vLDNpARz9geEHxtwI72BxStXfZyIqgxHppRg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=lHIJqX J14/Q9jG4BAxZLvIxeEW5WyrJlxjdcDG4KxM4=; b=Y4PPgmIkxMGBR5LBG717Lu VDHKZtNgFH+SWwVIEfcR5oOFvf4ZgFMHYIy5faGmyuFK4tOg16zZK0W769W2S9PR JO+GAKbyhQBspsacMyxwtGa+ftmZHszBS54m+NOsKt6iY2aMEWBspB+Su6VqDqIH 7g7/Jiq4aE3Uw8bY+TqQi1hOvbB2+ynjAdg/eRoH0I1RVV8INQUvJ0xUfji8f6tY 46u1chzcN+RKmvwy8RmGsI4i/3V+vdAmwYdLzn0DCyZ8EDNBB8LehqPCVK6waZTv AupCn7a9Bpp27nFQNxG6xtOW2zH7liGX62euE90yOfj1tj28JW+fhjpDONBvc1UA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id C327AE4426; Mon, 26 Mar 2018 05:13:17 -0400 (EDT) Subject: Re: libreoffice fails to build [SOLVED] To: freebsd-stable@freebsd.org References: Cc: freebsd-ports@freebsd.org From: tech-lists Message-ID: <626cd358-e2ae-052b-9533-fc95237f61a1@zyxst.net> Date: Mon, 26 Mar 2018 10:13:16 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 26 Mar 2018 09:13:25 -0000 On 24/03/2018 19:07, tech-lists wrote: > Hi, > > Building libreoffice (libreoffice-en_GB) complains about illegal > instruction and dumps core. Full script output is at > https://www.zyxst.net/errors/libreofficebuildfail.txt please ignore, libreoffice builds fine on a pristine installation. -- J. From owner-freebsd-stable@freebsd.org Mon Mar 26 22:29:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46C09F717B1; Mon, 26 Mar 2018 22:29:49 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 E94CD78714; Mon, 26 Mar 2018 22:29:48 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 511865A9F16; Mon, 26 Mar 2018 22:29:42 +0000 (UTC) Date: Mon, 26 Mar 2018 22:29:42 +0000 From: Brooks Davis To: "Rodney W. Grimes" Cc: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Subject: Re: Calling nxge(4) users Message-ID: <20180326222942.GB42437@spindle.one-eyed-alien.net> References: <20180325184032.GA42437@spindle.one-eyed-alien.net> <201803252009.w2PK9Rjk043533@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline In-Reply-To: <201803252009.w2PK9Rjk043533@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 26 Mar 2018 22:29:49 -0000 --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 25, 2018 at 01:09:27PM -0700, Rodney W. Grimes wrote: > > The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > > adapters has obvious bugs (by inspection) and it doesn't appear the > > company exists any more. We'd like to see if there are any significant > > users of this device and plan to remove it from FreeBSD-12 if not. > >=20 > > -- Brooks >=20 > Neterion has been acquired by exar.=20 > https://www.eetimes.com/document.asp?doc_id=3D1173009 >=20 > They have the datasheet for the Xframe-I here: > https://www.exar.com/ds/xframedatasheet.pdf >=20 > The cards appear to be readily avaliable on ebay. Given that most of these cards appear to have been PCI-X and the product failed in the market, I'm not finding that compelling. One could buy a Chelsio or Intel card for a similar price and have a supported driver. Unless someone has a significant deployment of these cards that will run past the EOL of FreeBSD 11 (2021) this driver is a net negative. -- Brooks --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJauXRVAAoJEKzQXbSebgfAza8H/iJ6bdHMZ/Vbl2q1F2ytd1cl MxUszVU0g77ld7cjan6zu0AgcIh7yhfCDXJBkuNvmE6RyuAdz0dJGnWElrq4DQo2 wrIkhbNAmsZojGqUwatiEcmNtz8zTfm4gOwGA4qjAqOXfdFFMhCBnktrZ4EZ1oUk 4ANq9EHqhOphEL4AgNGAJnqIN+9ywoIrZhI5VzjOe9CRusQ73Ym/H9BmoSa1d2Pg WZWKNJBpC5/bbv0UVFEAPhI6lJwLsXa8jsNTr0Zvds13RuZXBJMpX/XEFk2SjVgb MmD0WAbT5CoG4zruSRmB6KI5F8xNDhVWb4GUZApKCKIFnR8oZCHgjfj7oohgukY= =TB/r -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc-- From owner-freebsd-stable@freebsd.org Mon Mar 26 23:13:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BBCEF508C3 for ; Mon, 26 Mar 2018 23:13:16 +0000 (UTC) (envelope-from kevin.bowling@kev009.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 3364A7BC36 for ; Mon, 26 Mar 2018 23:13:16 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-io0-x235.google.com with SMTP id q80so14370214ioi.13 for ; Mon, 26 Mar 2018 16:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PchUdhr2BgHgQq220sY6PoGdBH7SH5COQ3Ogi+xthc4=; b=tNm3q4w0rHzNjzM5pZIBMEP8+UQYGK7/nD733AVVOZjeOD9EzbfE0UarPSkFT6blOG XaAa1QWMePiDyGGBfWKTmOkd0kyb7TtpMQ0+2LraDtiXzvtCOhPjdiL2eXJyJb5wKT7h CNij1HHX3HSSU+Mk3PssL8Q0stK5HF+NY2pdw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PchUdhr2BgHgQq220sY6PoGdBH7SH5COQ3Ogi+xthc4=; b=UeDwjVzb/i0ccmKaF/Q9B/eMpBvlBVP/1vmF/LET46AakPljf7N6xaB0+0u7UfQNOB 9KlBUT+ktu3ge2umkg/bDt+sIxRAIZUzZFInrWFVpNpBka6g0prk8ej3fSn22r83pl3i BfO3NvCQqtLo+/HweftO0RtQ6QVRYFJqE34WcwqI1hCWupkkekaTFBZeOC/ikjJAIn0B 1Om2w7FKAQkTI34Ar4TcUJOzbny1HNr++cXuHAs67hhrFcQ6RE9snrVk45FTqpVGUm2w AHIjA0+rBLw5P5MzpVJrgtM0aaGjqgdzDL+5FyhVWvSdWVPzmVES3+KNi+BolrmfL+tP 8EPg== X-Gm-Message-State: AElRT7Eob1Gvuai9NWx+phkHZbErILdCa5Jdg73nDkEGKD9lDH4rcDDm QwoAe+xpGazFg90eqLEI/a2m0X89Ae8CHuXV+bHMbkQl X-Google-Smtp-Source: AG47ELu6mZOG5/0uqMFJ7hy/CTEQljY9zMcDTX5p1RpnRv2EVtTrn7uRMj4j2JK38jQ52ZurAfl3HRMwP1q2A6NbVx0= X-Received: by 10.107.139.70 with SMTP id n67mr41538613iod.109.1522105995580; Mon, 26 Mar 2018 16:13:15 -0700 (PDT) MIME-Version: 1.0 References: <20180325184032.GA42437@spindle.one-eyed-alien.net> <201803252009.w2PK9Rjk043533@pdx.rh.CN85.dnsmgr.net> <20180326222942.GB42437@spindle.one-eyed-alien.net> In-Reply-To: <20180326222942.GB42437@spindle.one-eyed-alien.net> From: Kevin Bowling Date: Mon, 26 Mar 2018 23:13:04 +0000 Message-ID: Subject: Re: Calling nxge(4) users To: Brooks Davis Cc: "Rodney W. Grimes" , freebsd-net@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 26 Mar 2018 23:13:17 -0000 Agreed. Please cull the =E2=80=98ixgb=E2=80=99 driver for similar reasons On Mon, Mar 26, 2018 at 4:05 PM Brooks Davis wrote: > On Sun, Mar 25, 2018 at 01:09:27PM -0700, Rodney W. Grimes wrote: > > > The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > > > adapters has obvious bugs (by inspection) and it doesn't appear the > > > company exists any more. We'd like to see if there are any significa= nt > > > users of this device and plan to remove it from FreeBSD-12 if not. > > > > > > -- Brooks > > > > Neterion has been acquired by exar. > > https://www.eetimes.com/document.asp?doc_id=3D1173009 > > > > They have the datasheet for the Xframe-I here: > > https://www.exar.com/ds/xframedatasheet.pdf > > > > The cards appear to be readily avaliable on ebay. > > Given that most of these cards appear to have been PCI-X and the product > failed in the market, I'm not finding that compelling. One could buy > a Chelsio or Intel card for a similar price and have a supported driver. > > Unless someone has a significant deployment of these cards that will run > past the EOL of FreeBSD 11 (2021) this driver is a net negative. > > -- Brooks > From owner-freebsd-stable@freebsd.org Wed Mar 28 13:09:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B7A1F5B26B for ; Wed, 28 Mar 2018 13:09:13 +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 0700B68A5D for ; Wed, 28 Mar 2018 13:09:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f1Ap6-00015y-2R for freebsd-stable@freebsd.org; Wed, 28 Mar 2018 16:09:04 +0300 Date: Wed, 28 Mar 2018 16:09:04 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org Subject: KBI unexpexted change in stable/11 ? Message-ID: <20180328130903.GC6612@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.25 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, 28 Mar 2018 13:09:13 -0000 I am upgrade system to latest -STABLE and now see kernel crash: - loading virtualbox modules build on 11.1-RELEASE-p6 - loading nvidia module build on 11.1-RELEASE-p6 and start xdm Is this expected? I am mean about loading modules builded on 11.1-RELEASE on any 11.1-STABLE. From owner-freebsd-stable@freebsd.org Wed Mar 28 13:12:47 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0EABF5B996 for ; Wed, 28 Mar 2018 13:12:46 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 94C9E68F72 for ; Wed, 28 Mar 2018 13:12:46 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qk0-x22c.google.com with SMTP id v2so2283332qkh.10 for ; Wed, 28 Mar 2018 06:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wgvp14AXZGgFEGhV6AZjO/2Y1IkCnwtH9PgKHTc0YLk=; b=tdvKATlSGlEZ/+N5AUm5l1k5flx29rdYjvY1Gu3G8m/PmC5k4lfcG4Jh+FKrvVp4sD XBEARZ192u+VWIKrxC0Cyv+T2mVOZ35ITx5cVTe8gdzjH0woBEOWBy0Z0zEpV16rIe7P Hl3su/zTmOkcIZheogcOQuNJxtm4BWA2x6dGwX0AJ+dCdZ1smA2zgbxMSR3S5ur4fDNs 36HFQ4QrCQua6lroWbaWwD61wyrLh9/DqB6mg4dLr9JyhGN4PCSRX0skxBzHuhdzhtv7 /qEM1o3VLMrdHNQsk4IbrBAq9sLdQe9EUNSKHhK1oVPrafttJZEcusW+QV22JMB04BbM Im5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wgvp14AXZGgFEGhV6AZjO/2Y1IkCnwtH9PgKHTc0YLk=; b=AOhYxF8jT20OcpJk1kRhhdV2eFdo2JTpGSgAu1Zjh3c39LuBrp0zrM0F7VqhaL3DWW cExw4jISkXuhltKKvcdNtc5nujyzD+iBU1gWjJabHMPfFxI4imzVUV4h0KqA//pAKGLT 5NQNXPLExfXaRM7RW8T7LgzCiOhIdeNthw0hSJ62oSUFiu4bWFSNreZ4alhyx1pvvRjE Gp5uBUBzPiQ3bizNpMdnlIqOnG3bj5jJIREGze2KKcK6cHOZ2zb61MuMGNO5KozElx2g SCBoFrcfyY0U6E8loLU1bLACr14VxYYUFyGCPiNiFpk9QKZAk4TQpBatJDPx6jdTDqza UgZw== X-Gm-Message-State: AElRT7HU6g9xECkR0IibH8irP0f5bGGTQILLGoA9PV/KmuHrCMOKMLML 7YNE9+b2WRImFoZELLHTbfMuUl9XVdk= X-Google-Smtp-Source: AIpwx4+2MxNUDd8MTHjldhRpZLUCHyK/U5JS8nI4t0LwD0CiIHZU9jEZIvyuCmLZxvIpMnW/k6tvhQ== X-Received: by 10.55.200.1 with SMTP id c1mr4818648qkj.207.1522242765697; Wed, 28 Mar 2018 06:12:45 -0700 (PDT) Received: from ?IPv6:2600:1017:b42d:e8ff:de9:e889:8f40:41e1? ([2600:1017:b42d:e8ff:de9:e889:8f40:41e1]) by smtp.gmail.com with ESMTPSA id r28sm2798875qta.77.2018.03.28.06.12.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Mar 2018 06:12:44 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: KBI unexpexted change in stable/11 ? From: Mark Saad X-Mailer: iPhone Mail (15D100) In-Reply-To: <20180328130903.GC6612@zxy.spb.ru> Date: Wed, 28 Mar 2018 09:12:43 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180328130903.GC6612@zxy.spb.ru> To: Slawa Olhovchenkov X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 13:12:47 -0000 > On Mar 28, 2018, at 9:09 AM, Slawa Olhovchenkov wrote: >=20 > I am upgrade system to latest -STABLE and now see kernel crash: >=20 > - loading virtualbox modules build on 11.1-RELEASE-p6 > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm >=20 > Is this expected? I am mean about loading modules builded on > 11.1-RELEASE on any 11.1-STABLE. I had a similar issue and it caused a kernel coredump=20 I tracked the virtualbox issue to something in the vbox network module . Reb= uilding it fixes it but I am not sure what broke . I have a kernel core dump= if anyone wants a peak.=20 --- Mark Saad | nonesuch@longcount.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 Wed Mar 28 13:47:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20216F5F6D1 for ; Wed, 28 Mar 2018 13:47:59 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from v1.leiden.byshenk.net (v1.leiden.byshenk.net [37.97.209.179]) (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 BAD346B000 for ; Wed, 28 Mar 2018 13:47:58 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: by v1.leiden.byshenk.net (Postfix, from userid 1002) id 4D23975939; Wed, 28 Mar 2018 15:39:46 +0200 (CEST) Date: Wed, 28 Mar 2018 15:39:46 +0200 From: Gregory Byshenk To: freebsd-stable@freebsd.org Cc: Slawa Olhovchenkov Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328133946.GN51114@v1.leiden.byshenk.net> References: <20180328130903.GC6612@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180328130903.GC6612@zxy.spb.ru> User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 13:47:59 -0000 On Wed, Mar 28, 2018 at 04:09:04PM +0300, Slawa Olhovchenkov wrote: > I am upgrade system to latest -STABLE and now see kernel crash: > > - loading virtualbox modules build on 11.1-RELEASE-p6 > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > Is this expected? I am mean about loading modules builded on > 11.1-RELEASE on any 11.1-STABLE. Did you rebuild your virtualbox and nvidia modules for your new kernel? If you build a new kernel, then you need to rebuild any modules that were installed from ports for the new version. You can do this manually, or by adding a PORTS_MODULES line to /etc/make.conf. This will rebuild the listed modules from ports when you build a new kernel. I think this will do what you need (double-check that these are the right port names): PORTS_MODULES= emulators/virtualbox-ose-kmod x11/nvidia-driver -gregory -- gregory byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@freebsd.org Wed Mar 28 14:11:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AD95F619CD for ; Wed, 28 Mar 2018 14:11:53 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3709B6CA9F for ; Wed, 28 Mar 2018 14:11:52 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4536E20B1E for ; Wed, 28 Mar 2018 10:11:52 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 28 Mar 2018 10:11:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=cL2tDur8YGAQ6gQYAgS/RGIlVQ5g7 JR6uhnAVNck6/0=; b=AO0FTthyvBAUwFZkhRq6AbtW8oP5+ccCpIBn8lQMko6H3 Jx6GpVUMCGlxTM9ARTX85qX7GUwLN9cuOi5XeiNt7T/Pfrk7wk0QCwl4WidqOW9F +qN3NeVTi/INLVu2OU8X1b9dTu/O+684HW71ECpz8YhljQjGqmL2LyX6/jBLK7hM JaasBVc6MMfeQBSe2iKhPHAvdcLXeqpjM33sZv2u3Les7txw/GruC4IbIkbEdGOq SRxaot8was5sClPbGnd23NLo60+sn/W5YuM4Fa15tLVbIwzx8Kl77P4IZLrPaRs1 K6wGWhI1TQBrMp9TEHxPjWmuQuQ6eJfHHzm6kxJjw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=cL2tDu r8YGAQ6gQYAgS/RGIlVQ5g7JR6uhnAVNck6/0=; b=G60y4JWpvqIwPhZMc73ekm uRlAKTM+dpE7ur1vM+cIY5udG7tQVOgr1fF4K0q0o30Rlc8YCHIf5jDyPzG+p45I wMgm1BoqDFIaQ2B+jTeiLi2VQaWR8dXvcMR/HuVSuegfFfhQhpitEjcUscAN2GNI TJcPvu/SdzzY0XxlPL1I24GPrOv1FQZSoMYfaA10+dzNMVPp0r48b8BNn12Sq58u vNxU6fJaLrfZLIM7kpQqO/jDw0tazcbkIDMgdOySHBdtQDumH+d8MayxFyytWjLv oanCDQyrmV1h2OqQx1fBJRQki+MjuTbtY/78tbSQmBRfPm3GmEZJChmto80dgt8A == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id C391210259 for ; Wed, 28 Mar 2018 10:11:51 -0400 (EDT) Subject: Re: KBI unexpexted change in stable/11 ? To: freebsd-stable@freebsd.org References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> From: tech-lists Message-ID: Date: Wed, 28 Mar 2018 15:11:50 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180328133946.GN51114@v1.leiden.byshenk.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 14:11:53 -0000 On 28/03/2018 14:39, Gregory Byshenk wrote: > You can do this manually, or by adding a PORTS_MODULES line to > /etc/make.conf. This will rebuild the listed modules from ports > when you build a new kernel. Hi, Are you sure it's in /etc/make.conf and not /etc/src.conf? -- J. From owner-freebsd-stable@freebsd.org Wed Mar 28 14:20:15 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E13E6F625CB for ; Wed, 28 Mar 2018 14:20:15 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from v1.leiden.byshenk.net (v1.leiden.byshenk.net [37.97.209.179]) (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 82B376D2EA for ; Wed, 28 Mar 2018 14:20:15 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: by v1.leiden.byshenk.net (Postfix, from userid 1002) id 5386775955; Wed, 28 Mar 2018 16:20:14 +0200 (CEST) Date: Wed, 28 Mar 2018 16:20:14 +0200 From: Greg Byshenk To: tech-lists Cc: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328142014.GO51114@v1.leiden.byshenk.net> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 14:20:16 -0000 On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: > On 28/03/2018 14:39, Gregory Byshenk wrote: > > You can do this manually, or by adding a PORTS_MODULES line to > > /etc/make.conf. This will rebuild the listed modules from ports > > when you build a new kernel. > > Are you sure it's in /etc/make.conf and not /etc/src.conf? No. But it is in the man page for make.conf and not src.conf. -- gregory byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@freebsd.org Wed Mar 28 14:35:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3CA3F63ED3 for ; Wed, 28 Mar 2018 14:35:54 +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 4B7D36E5B7 for ; Wed, 28 Mar 2018 14:35:54 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f1CB5-0001XU-H6; Wed, 28 Mar 2018 17:35:51 +0300 Date: Wed, 28 Mar 2018 17:35:51 +0300 From: Slawa Olhovchenkov To: Gregory Byshenk Cc: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328143551.GD6612@zxy.spb.ru> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180328133946.GN51114@v1.leiden.byshenk.net> 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.25 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, 28 Mar 2018 14:35:54 -0000 On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote: > On Wed, Mar 28, 2018 at 04:09:04PM +0300, Slawa Olhovchenkov wrote: > > I am upgrade system to latest -STABLE and now see kernel crash: > > > > - loading virtualbox modules build on 11.1-RELEASE-p6 > > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > > > Is this expected? I am mean about loading modules builded on > > 11.1-RELEASE on any 11.1-STABLE. > > Did you rebuild your virtualbox and nvidia modules for your new > kernel? If you build a new kernel, then you need to rebuild any > modules that were installed from ports for the new version. Only for -CURRENT, not for -STABLE: https://lists.freebsd.org/pipermail/svn-src-all/2018-March/159649.html John Baldwin: "In theory we try to not break existing kernel modules on a stable branch. That is, one should be able to kldload an if_iwn.ko built on 11.0 on a 11-stable kernel." From owner-freebsd-stable@freebsd.org Wed Mar 28 15:13:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E202DF6779D for ; Wed, 28 Mar 2018 15:13:50 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from v1.leiden.byshenk.net (v1.leiden.byshenk.net [37.97.209.179]) (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 8425870A37 for ; Wed, 28 Mar 2018 15:13:50 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: by v1.leiden.byshenk.net (Postfix, from userid 1002) id DC38375937; Wed, 28 Mar 2018 17:13:48 +0200 (CEST) Date: Wed, 28 Mar 2018 17:13:48 +0200 From: Gregory Byshenk To: freebsd-stable@freebsd.org Cc: Slawa Olhovchenkov Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328151348.GP51114@v1.leiden.byshenk.net> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328143551.GD6612@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180328143551.GD6612@zxy.spb.ru> User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 15:13:51 -0000 On Wed, Mar 28, 2018 at 05:35:51PM +0300, Slawa Olhovchenkov wrote: > On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote: > > > > Did you rebuild your virtualbox and nvidia modules for your new > > kernel? If you build a new kernel, then you need to rebuild any > > modules that were installed from ports for the new version. > > Only for -CURRENT, not for -STABLE: > > https://lists.freebsd.org/pipermail/svn-src-all/2018-March/159649.html > > John Baldwin: "In theory we try to not break existing kernel > modules on a stable branch. That is, one should be able to kldload an > if_iwn.ko built on 11.0 on a 11-stable kernel." I understand that this is true for standard kernel modules, but I have frequently run into problems loading _ports_ modules on a new kernel - including in STABLE. -- gregory byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@freebsd.org Wed Mar 28 15:18:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DAE3F67E0E for ; Wed, 28 Mar 2018 15:18: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 294AD70CE7 for ; Wed, 28 Mar 2018 15:18: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 1f1Cq1-0001jH-VW; Wed, 28 Mar 2018 18:18:09 +0300 Date: Wed, 28 Mar 2018 18:18:09 +0300 From: Slawa Olhovchenkov To: Gregory Byshenk Cc: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328151809.GK4305@zxy.spb.ru> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328143551.GD6612@zxy.spb.ru> <20180328151348.GP51114@v1.leiden.byshenk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180328151348.GP51114@v1.leiden.byshenk.net> 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.25 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, 28 Mar 2018 15:18:11 -0000 On Wed, Mar 28, 2018 at 05:13:48PM +0200, Gregory Byshenk wrote: > On Wed, Mar 28, 2018 at 05:35:51PM +0300, Slawa Olhovchenkov wrote: > > On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote: > > > > > > Did you rebuild your virtualbox and nvidia modules for your new > > > kernel? If you build a new kernel, then you need to rebuild any > > > modules that were installed from ports for the new version. > > > > Only for -CURRENT, not for -STABLE: > > > > https://lists.freebsd.org/pipermail/svn-src-all/2018-March/159649.html > > > > John Baldwin: "In theory we try to not break existing kernel > > modules on a stable branch. That is, one should be able to kldload an > > if_iwn.ko built on 11.0 on a 11-stable kernel." > > I understand that this is true for standard kernel modules, but > I have frequently run into problems loading _ports_ modules on > a new kernel - including in STABLE. This is general _kernel_ rule, for loading all modules, mostly for third-party modules. From owner-freebsd-stable@freebsd.org Wed Mar 28 15:29:21 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5761CF68B65 for ; Wed, 28 Mar 2018 15:29:21 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id 05D637191D for ; Wed, 28 Mar 2018 15:29:20 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id DDED35646B; Wed, 28 Mar 2018 10:29:13 -0500 (CDT) Subject: Re: KBI unexpexted change in stable/11 ? To: Slawa Olhovchenkov , freebsd-stable@freebsd.org References: <20180328130903.GC6612@zxy.spb.ru> From: Eric van Gyzen Message-ID: <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> Date: Wed, 28 Mar 2018 10:29:10 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20180328130903.GC6612@zxy.spb.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 15:29:21 -0000 On 03/28/2018 08:09, Slawa Olhovchenkov wrote: > I am upgrade system to latest -STABLE and now see kernel crash: > > - loading virtualbox modules build on 11.1-RELEASE-p6 > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > Is this expected? I am mean about loading modules builded on > 11.1-RELEASE on any 11.1-STABLE. This is not expected. Can you bisect to find the stable/11 commit that broke this? If you can roll back to 11.1-RELEASE, you could probably just buildkernel and installkernel from various points along stable/11. That would save a lot of time by avoiding buildworld. Eric From owner-freebsd-stable@freebsd.org Wed Mar 28 15:30:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 207AEF68C57 for ; Wed, 28 Mar 2018 15:30:12 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC9ED719F4 for ; Wed, 28 Mar 2018 15:30:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EAFCD21130; Wed, 28 Mar 2018 11:30:00 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Wed, 28 Mar 2018 11:30:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=55GjsG3d1ABdYxBRRCa/3u10gkyw0 keso1NbJEHzVZQ=; b=wIE/56eIxzfEPhk21QrRF3foPOhgVkbdh5FgpI4Cn14ES m/4/XftxFX5UrqJ+Zq5CEBBK8l91RrP8OkWaD68csuy8sUBujf+m+5LUSlo6IFw6 PRSHA+sLmE8I9AoeXzWApB8I+GT7q4H2ceMaPbarSGkoMZ0NJR6epP7g3T1UR129 O3DmGUwFRb+jytiC3qKRoP8RFZfOUqfzxaMis2pIgK7NFdmM9Cs2NBGsfXCmMGMe Mait/hUAXEYi9rziosoeVah7JiTkd41dwa9e0+nszmoBB8zEcY6nRUm8OZgIj+gZ DXLlRfnRu8hVb/PaJsewBurgYKgQribifE/xjQmzw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=55GjsG 3d1ABdYxBRRCa/3u10gkyw0keso1NbJEHzVZQ=; b=K7Z2RUNJ7P2rEijG5TFr6N 9urPn40ipdKUcDbILFydiHlifKmF4OPSFh3tyQT37NxXKQE1n9iQqKCM1gq7cFKi nGXe6EForne/Mgs7Tp1qCftIgYJ2YW5dRydDrbkGtCGbsyMiP9qtPi2/yMdCJCQA B1XVe3AioVy6nzNUSXvFNj5ZmRxsffIqS1mCj1JtRp3jrFazI9EIi95tSFb4tbzR Uz8vyZLZ/AqGvB+BVSf0VVmSgBFSEbX7yqmDMNGUSv58TBP4Q+mBREreEA4pHnlH QGUfRuGNK6ABT66eAN1uZgfFOSjfyR3qzePy1qkr6Ti5cMiUs/eyZlJP+5/NA0bQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id BA617BA43B; Wed, 28 Mar 2018 11:30:00 -0400 (EDT) Message-Id: <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> From: John To: Greg Byshenk Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338 Date: Wed, 28 Mar 2018 16:30:00 +0100 Subject: Re: KBI unexpexted change in stable/11 ? In-Reply-To: <20180328142014.GO51114@v1.leiden.byshenk.net> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328142014.GO51114@v1.leiden.byshenk.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 15:30:12 -0000 On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote: > On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: > > On 28/03/2018 14:39, Gregory Byshenk wrote: > > > You can do this manually, or by adding a PORTS_MODULES line to > > > /etc/make.conf. This will rebuild the listed modules from ports > > > when you build a new kernel. > > > > Are you sure it's in /etc/make.conf and not /etc/src.conf? > > No. But it is in the man page for make.conf and not src.conf. yeah. That is... confusing! at least to me, because [I thought it would be] src.conf that's consulted when src is built. So I ran a couple of tests and found that it would work in either file HOWEVER if one ports module statement was in src.conf and another, different ports module statement was in make.conf, that the one in src.conf would get built but the one in make.conf would not. how confusing is that. This is on 11.1-stable. -- John tech-lists@zyxst.net From owner-freebsd-stable@freebsd.org Wed Mar 28 15:35:31 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C33CF69166 for ; Wed, 28 Mar 2018 15:35:31 +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 1C55472181 for ; Wed, 28 Mar 2018 15:35:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f1D6n-0001sq-SJ; Wed, 28 Mar 2018 18:35:29 +0300 Date: Wed, 28 Mar 2018 18:35:29 +0300 From: Slawa Olhovchenkov To: Eric van Gyzen Cc: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328153529.GL4305@zxy.spb.ru> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> 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.25 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, 28 Mar 2018 15:35:31 -0000 On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote: > On 03/28/2018 08:09, Slawa Olhovchenkov wrote: > > I am upgrade system to latest -STABLE and now see kernel crash: > > > > - loading virtualbox modules build on 11.1-RELEASE-p6 > > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > > > Is this expected? I am mean about loading modules builded on > > 11.1-RELEASE on any 11.1-STABLE. > > This is not expected. Can you bisect to find the stable/11 commit that > broke this? > > If you can roll back to 11.1-RELEASE, you could probably just > buildkernel and installkernel from various points along stable/11. That > would save a lot of time by avoiding buildworld. r325665 is previos point and is good. r331615 crashed. Can I use some script for bisect? From owner-freebsd-stable@freebsd.org Wed Mar 28 15:49:21 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52D4BF697FB for ; Wed, 28 Mar 2018 15:49:21 +0000 (UTC) (envelope-from se@freebsd.org) Received: from sonic308-33.consmr.mail.ir2.yahoo.com (sonic308-33.consmr.mail.ir2.yahoo.com [77.238.178.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8DBD72A45 for ; Wed, 28 Mar 2018 15:49:20 +0000 (UTC) (envelope-from se@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1522252158; bh=fdRA2mh5KeyHqWFiizfd2QfVqvva/GQg8KNsZAOZ4qE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From:Subject; b=fZ9bKve2QIzNPUXZssRs5DOKinVRCIGmv7AQ2eZ8CdQGlmyffNco5lbp/CgGv7vIFROqtgYj6WCn89/9/WRKymQ1NQfZeb/PjmjT60Ekx/h5iWNXo0VM7O3+JpMVGhQwaAcjfLsoMfs31PbjzYy4rWGXwBKeMjJTEeXo2bXcVwK/93ucEM2Uz+3+WLdooHvU6sojI0VzlilwJ12FI4D/9M9JNb2CNqVEQJC1uiAHusfYzUeHuLlFoHZCXuYQJhiVzsDAvAXHuTcamwQ4KnXBTzRqZf/cwmS3wBMzbybsbnGvOdxxkIkic1PWKxM3Gf9miwyOSkLK165YRFu9gkORYw== X-YMail-OSG: JaW0PyUVM1naekoLL4lXzUlr7DPkH5_qh_xHTMfeoDkFh04I_0rodrPojSbLMYM eVmjcIgSlbE.VrAoRO_TZDqv.H7I5d3gQVQ..LMn4IvHfOb0rMR75MwV1m8sou5_Sn8wDKF9LlbW PQhAYQQ8mWSGjX1bIm3eM8q1864KyPH6zjgQ03qJORMxXulYCqKyNLHgWv35IXlDuVOI0tkvZ89t MLmpH3dRCPPuKQF2srjRtLW7E_DiEVyy9E5UXE4T5UGp_o_Ziuj_GYpeabWMr41i4_jTLi2GeCPk Uv84dqR8.P2ywn3PoqcZd5x73QSIkgfmWOY.N.9Pu9itqBPGRynDxDcwjEoQyG6Cm4uz6dHPN3QL RYJkArCjdHgJ71EuNDM7xeUd5ia_FOhbVXRLMJFciSuM_M4DD_4PQU9oOhVySTknStePgGyxIHod 6_B7ys_ifcYw2z9duAQ5_SAc.AdNZ2.M.QELDs3Yw.Uc1WtLrnibvwaDsPRQPXOGc0Snu8X1yyHl ZcY0eQPkTxZuTOEWbHw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.ir2.yahoo.com with HTTP; Wed, 28 Mar 2018 15:49:18 +0000 Received: from p5797D1FA.dip0.t-ipconnect.de (EHLO Stefans-MBP-7.fritz.box) ([87.151.209.250]) by smtp422.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a47ec22949dbb7621ec366b96346ba7b; Wed, 28 Mar 2018 15:49:17 +0000 (UTC) Subject: Re: KBI unexpexted change in stable/11 ? To: John Cc: Greg Byshenk , freebsd-stable@freebsd.org References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328142014.GO51114@v1.leiden.byshenk.net> <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNLlN0ZWZhbiBFw59lciAoVC1PbmxpbmUpIDxzdC5lc3NlckB0LW9ubGluZS5kZT7CwH8E EwEIACkFAlhtTvQCGwMFCQWjmoAHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRBH67Xv Wv31RAn0B/9skuajrZxjtCiaOFeJw9l8qEOSNF6PKMN2i/wosqNK57yRQ9AS18x4+mJKXQtc mwyejjQTO9wasBcniKMYyUiie3p7iGuFR4kSqi4xG7dXKjMkYvArWH5DxeWBrVf94yPDexEV FnEG9t1sIXjL17iFR8ng5Kkya5yGWWmikmPdtZChj9OUq4NKHKR7/HGM2dxP3I7BheOwY9PF 4mhqVN2Hu1ZpbzzJo68N8GGBmpQNmahnTsLQ97lsirbnPWyMviWcbzfBCocI9IlepwTCqzlN FMctBpLYjpgBwHZVGXKucU+eQ/FAm+6NWatcs7fpGr7dN99S8gVxnCFX1Lzp/T1YzsBNBFVx iRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1MkVnCAhFbY9oecTB/togdKtfi loavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNUeMm+gtTDMSvloGAfr76RtFHs kdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPqz3B4IjiDAWTO2obD1wtAvSuH uUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSAly+hkY7NrDZydMMXVNQ7AJQu fWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpqThDMurqtQFn1ABEBAAHCwGUE GAEKAA8FAlVxiRICGwwFCQWjmoAACgkQR+u171r99UQEHAf/ZxNbMxwX1v/hXc2ytE6yCAil piZzOffT1VtS3ET66iQRe5VVKL1RXHoIkDRXP7ihm3WF7ZKy9yA9BafMmFxsbXR3+2f+oND6 nRFqQHpiVB/QsVFiRssXeJ2f0WuPYqhpJMFpKTTW/wUWhsDbytFAKXLLfesKdUlpcrwpPnJo KqtVbWAtQ2/o3y+icYOUYzUig+CHl/0pEPr7cUhdDWqZfVdRGVIk6oy00zNYYUmlkkVoU7MB V5D7ZwcBPtjs254P3ecG42szSiEo2cvY9vnMTCIL37tX0M5fE/rHub/uKfG2+JdYSlPJUlva RS1+ODuLoy1pzRd907hl8a7eaVLQWA== Message-ID: <19b642db-104c-0288-c485-562309071363@freebsd.org> Date: Wed, 28 Mar 2018 17:49:16 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 15:49:21 -0000 Am 28.03.18 um 17:30 schrieb John: > On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote: >> On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: >>> On 28/03/2018 14:39, Gregory Byshenk wrote: >>>> You can do this manually, or by adding a PORTS_MODULES line to >>>> /etc/make.conf. This will rebuild the listed modules from ports >>>> when you build a new kernel. >>> >>> Are you sure it's in /etc/make.conf and not /etc/src.conf? >> >> No. But it is in the man page for make.conf and not src.conf. > > yeah. That is... confusing! at least to me, because [I thought it would be] > src.conf that's consulted when src is built. So I ran a couple of tests and > found that it would work in either file HOWEVER if one ports module statement > was in src.conf and another, different ports module statement was in make.conf, > that the one in src.conf would get built but the one in make.conf would not. > > how confusing is that. This is on 11.1-stable. No, its not confusing at all, if you think about it ... ;-) /etc/make.conf is included in any case, but kernel and world builds will include /etc/src.conf thereafter (and overwrite earlier settings read from make.conf, unless ?= is used to preserve the earlier value, or += to append the new values). Regards, STefan From owner-freebsd-stable@freebsd.org Wed Mar 28 15:55:48 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 804CDF69E57 for ; Wed, 28 Mar 2018 15:55:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 073E0730D7 for ; Wed, 28 Mar 2018 15:55:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 7a0efc08-32a0-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 7a0efc08-32a0-11e8-91c6-33ffc249f3e8; Wed, 28 Mar 2018 15:55:47 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2SFteYU064199; Wed, 28 Mar 2018 09:55:40 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1522252540.49673.62.camel@freebsd.org> Subject: Re: KBI unexpexted change in stable/11 ? From: Ian Lepore To: John , Greg Byshenk Cc: freebsd-stable@freebsd.org Date: Wed, 28 Mar 2018 09:55:40 -0600 In-Reply-To: <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328142014.GO51114@v1.leiden.byshenk.net> <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 15:55:48 -0000 On Wed, 2018-03-28 at 16:30 +0100, John wrote: > On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote: > > > > On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: > > > > > > On 28/03/2018 14:39, Gregory Byshenk wrote: > > > > > > > > You can do this manually, or by adding a PORTS_MODULES line to > > > > /etc/make.conf. This will rebuild the listed modules from ports > > > > when you build a new kernel. > > > Are you sure it's in /etc/make.conf and not /etc/src.conf? > > No. But it is in the man page for make.conf and not src.conf. > yeah. That is... confusing! at least to me, because [I thought it would be]  > src.conf that's consulted when src is built. So I ran a couple of tests and  > found that it would work in either file HOWEVER if one ports module statement  > was in src.conf and another, different ports module statement was in make.conf,  > that the one in src.conf would get built but the one in make.conf would not.  > > how confusing is that. This is on 11.1-stable. > Make.conf is for building anything that uses make(1) and the build infrastructure in /usr/share/mk.  Src.conf is for building the freebsd sources only.  According to build(7), the freebsd sources include /usr/src, /usr/doc, and /usr/ports.  So settings in both make.conf and src.conf affect ports builds. The difference appears when you use make to build your own software that isn't part of freebsd.  For that, make.conf settings are applied, but not src.conf.  At least, that's what the docs say.  When I look at the .mk files in /usr/share/mk, it appears to me that src.conf gets used even for non-freebsd-source builds. When both files exist, variables set in src.conf will override same- named variables set in make.conf.  Using VAR += value in both files will accumulate values into VAR rather than replacing them. -- Ian From owner-freebsd-stable@freebsd.org Wed Mar 28 16:15:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BCDDF6A9F5 for ; Wed, 28 Mar 2018 16:15:10 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0141073EF8; Wed, 28 Mar 2018 16:15:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 26E9F2113B; Wed, 28 Mar 2018 12:15:09 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Wed, 28 Mar 2018 12:15:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=plDjpzKE6tgrE+khUDPVETsVczzVm MmMhWg15jL7H3s=; b=XRPYbtHY6dfiK0w0GHPDXt+itQaZfpiWW12FjQKGM8vVo aEp1p5DTVp+/wk2dDyc/B4OHohBhwEQOEqpF0hkx32RoSnvBtO2OPrtcnhoNY7SV aUgWdpglix8/8vDmgaT0uHY6OAPMdA8ri1z6Ktr1pMVxcGCo8ePzTVRtFPcJ9mK7 L6PneHX+wdMmdrunvbKF/gaeVOyRZgb5xPOskaZbb0pU2pf9VSTqr19nrY45yalp rsrZpf/4WCNViiu7pSEdLeY5wQWzfTLPsjZDE/4F/sTkCGJD0ntn/WbIWbVz9j5R 4GupWpsdKXXQFjXyGQA/jRZSbMnOJquIW1Y6UoaGg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=plDjpz KE6tgrE+khUDPVETsVczzVmMmMhWg15jL7H3s=; b=NsdBeR+sxHIpqunitNprkn YBZGX3IibXVXzljCVRHi1YyHAbj+1MFgXmIGR23beDEEl6yF8QNi+cY0Nwf4SA6w cXnRi4CGARzprqrnO3l7ZKBqFJc5tD/NetYfnUuqYtIE76kjXby4PnpWhRbDQJBf /lml44Gv9tyOJI/pZa2GQkd8lSTFAime5+zi3QTVC/EXi/aKi1+M3Tf9JBtRHehB W/flrdP1ZuLe35fClt8RXaV+UZVfq7vu9Xn8WbdwBLlswNKrOHCI4sd/lVL5L3Od aHOtVU6ntftAE22X658Sq08wlwHi0UFZJqyjJEg5+6gpuxCNFPVbG03BBti6cNSA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id E3B1ABA1AE; Wed, 28 Mar 2018 12:15:08 -0400 (EDT) Message-Id: <1522253708.3483189.1319177040.743BB327@webmail.messagingengine.com> From: John To: Stefan Esser Cc: Greg Byshenk , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338 In-Reply-To: <19b642db-104c-0288-c485-562309071363@freebsd.org> Subject: Re: KBI unexpexted change in stable/11 ? Date: Wed, 28 Mar 2018 17:15:08 +0100 References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328142014.GO51114@v1.leiden.byshenk.net> <1522251000.3459457.1319064600.0294FF59@webmail.messagingengine.com> <19b642db-104c-0288-c485-562309071363@freebsd.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 16:15:10 -0000 On Wed, 28 Mar 2018, at 16:49, Stefan Esser wrote: > No, its not confusing at all, if you think about it ... ;-) The bit for me which was confusing is that the PORTS_MODULES reference, as Gregory correctly pointed out, is in the man page for make.conf and not src.conf. So one would think what the man page referenced would go into the file that pertaining to that manpage. The reason I've always had things like KERNCONF=KERNCONF1 GENERIC and PORTS_MODULES in src.conf is because I figured "if it gets built when base gets built then it must go in src.conf". So when Gregory mentioned it goes in make.conf, I thought perhaps I was doing it all wrong, or in an outdated way. I was surprised finding that in these contexts it didn't matter as long as one remembers as you say += ?= in make.conf -- John tech-lists@zyxst.net From owner-freebsd-stable@freebsd.org Wed Mar 28 16:16:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A6BDF6AB3E for ; Wed, 28 Mar 2018 16:16:55 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id 1730D7404A for ; Wed, 28 Mar 2018 16:16:54 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id C58A25646B; Wed, 28 Mar 2018 11:16:52 -0500 (CDT) Subject: Re: KBI unexpexted change in stable/11 ? To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru> From: Eric van Gyzen Message-ID: <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> Date: Wed, 28 Mar 2018 11:16:49 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20180328153529.GL4305@zxy.spb.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 16:16:55 -0000 On 03/28/2018 10:35, Slawa Olhovchenkov wrote: > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote: > >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote: >>> I am upgrade system to latest -STABLE and now see kernel crash: >>> >>> - loading virtualbox modules build on 11.1-RELEASE-p6 >>> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm >>> >>> Is this expected? I am mean about loading modules builded on >>> 11.1-RELEASE on any 11.1-STABLE. >> >> This is not expected. Can you bisect to find the stable/11 commit that >> broke this? >> >> If you can roll back to 11.1-RELEASE, you could probably just >> buildkernel and installkernel from various points along stable/11. That >> would save a lot of time by avoiding buildworld. > > r325665 is previos point and is good. > r331615 crashed. > Can I use some script for bisect? I'm not aware of a script for this. The only tool I've used is "git bisect", which is very handy if you're already familiar with git. Eric From owner-freebsd-stable@freebsd.org Wed Mar 28 16:42:04 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96364F6BB7D; Wed, 28 Mar 2018 16:42:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 464CB75D0E; Wed, 28 Mar 2018 16:42:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id DF853C063; Wed, 28 Mar 2018 16:42:03 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 28 Mar 2018 16:42:02 +0000 From: Glen Barber To: freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: HEADS-UP: 11.2-RELEASE cycle starting in one month Message-ID: <20180328164202.GA59100@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 16:42:04 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [Several vendor contacts in BCC.] For those that did not notice the website update adding the 11.2-RELEASE cycle schedule, I apologize for sending this to public lists this late. I thought I had done this, but apparently not. The 11.2-RELEASE release cycle will begin April 20, 2018. The schedule for the release cycle is: stable/11 slush: April 20, 2018 stable/11 freeze: May 4, 2018 BETA1 build starts: May 11, 2018 doc/ tree slush: May 12, 2018 BETA2 build starts: May 18, 2018 BETA3 build starts: May 25, 2018 [*] doc/ tree tag: May 26, 2018 releng/11.2 branch: June 1, 2018 RC1 build starts: June 1, 2018 stable/11 thaw: June 3, 2018 RC2 build starts: June 8, 2018 RC3 build starts: June 15, 2018 [*] RELEASE build starts: June 22, 2018 RELEASE announcement: June 27, 2018 11.1-RELEASE EoL: September 30, 2018 Branch EoL: September 30, 2021 [*] - If needed The schedule is also available on the Project website at: https://www.freebsd.org/releases/11.2R/schedule.html As a reminder, the code "slush" is not a hard freeze on the tree and does not require formal approval from re@, however we ask that you refrain from adding new features, and focus on fixing existing issues. The code "freeze" is the point at which all commits to stable/11 will require explicit approval from re@. If you are aware of any problems in stable/11, please let re@ know as soon as possible. Additionally, if vendors have driver updates that are planned to be included in 11.2-RELEASE, please ensure the drivers are updated in head (preferably as soon as possible, to catch any issues), and merged to stable/11 following the minimum 3-day MFC timeframe. Thank you. Glen On behalf of: re@ --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlq7xdoACgkQAxRYpUeP 4pPG1Q/+I1WO+9LA92DzYFVNygSgKwnHbzs6/LWe78JQGfV5iRIeaJbpZVKQcqNI HEN4AM9wYavDzOmafNb6CSfBwPV9IYcdSfBSyk7/BI3Wo3jeTdVXkOZzEtn4Kix/ KT7sLJ354HTxXVmgdMVVCI8LxTwD9jYpem5Xq1s4gTKmz/Z9Km8/47MSUBLDTRi2 LFFUYp1xbekweTWXXpVjXXrlB0UkP3zvDu8QLHNCbQkV+UN0Hkrv5kF7zKzVMt+d vscrRl2H1xr88s9BkYpRPpfauWbrIJm15WrGm32Q8r3EK153hgn7BzkKO8gDIExT eRjgea+OMC7BFx49+oEJJzbN8EwJ8T8upZs5rDJaEzFqm+LJELthdUrig7flMK8R ZEUKqAGB3l3JPvUYKx35rcbls+OcJU5LnBWsj/oJSPsltGnkALbRwYHzZr99yF2U vZMgyKfWU05KVCotkxvszxS6YfqmWQwDZaJnJe5W6qVWUzZsyE+zJ9DrT0fUbHVR VRtILMwRWMELT0AFtS9BvByaWSNHNc15TR0SW2vM4Nt/jk5+kabmFB3Fgqz0pMAs a0h2G8Vnqg7K8RMmiHrZeUp1kkcW3NTgFYvPqr8j+N3zgr9kC3odAnYByZUKYQuM eg7JYkUmFGQR1jxLrY3JQ9AoRTwtIkO+O7uPWjzKbs4Efx1N7Ik= =qCZ0 -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-stable@freebsd.org Wed Mar 28 16:46:50 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89FA1F6BE40 for ; Wed, 28 Mar 2018 16:46:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.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 2756B76084 for ; Wed, 28 Mar 2018 16:46:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1f1EDm-000Axb-Ki; Wed, 28 Mar 2018 17:46:46 +0100 Date: Wed, 28 Mar 2018 17:46:46 +0100 From: Gary Palmer To: Slawa Olhovchenkov Cc: Eric van Gyzen , freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180328164646.GC59700@in-addr.com> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru> <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 28 Mar 2018 16:46:50 -0000 On Wed, Mar 28, 2018 at 11:16:49AM -0500, Eric van Gyzen wrote: > On 03/28/2018 10:35, Slawa Olhovchenkov wrote: > > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote: > > > >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote: > >>> I am upgrade system to latest -STABLE and now see kernel crash: > >>> > >>> - loading virtualbox modules build on 11.1-RELEASE-p6 > >>> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > >>> > >>> Is this expected? I am mean about loading modules builded on > >>> 11.1-RELEASE on any 11.1-STABLE. > >> > >> This is not expected. Can you bisect to find the stable/11 commit that > >> broke this? > >> > >> If you can roll back to 11.1-RELEASE, you could probably just > >> buildkernel and installkernel from various points along stable/11. That > >> would save a lot of time by avoiding buildworld. > > > > r325665 is previos point and is good. > > r331615 crashed. > > Can I use some script for bisect? > > I'm not aware of a script for this. The only tool I've used is "git > bisect", which is very handy if you're already familiar with git. You may want to try devel/p5-App-SVN-Bisect. Never used it, so no idea if it's functional or helpful, just found it doing a quick search Regards, Gary From owner-freebsd-stable@freebsd.org Thu Mar 29 03:37:06 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C6AEF6F3CA for ; Thu, 29 Mar 2018 03:37:06 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from mta2-em1.orleans.occnc.com (mta2-em1.orleans.occnc.com [IPv6:2001:470:88e6:1::140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta2.orleans.occnc.com", Issuer "OCCNC secondary CA (ca1a2a)" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C5DCD76814 for ; Thu, 29 Mar 2018 03:37:05 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from harbor2.v6only.occnc.com (harbor2-em2.v6only.occnc.com [IPv6:2001:470:88e6:2::231]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: curtis@occnc.com) by mta2-em1.orleans.occnc.com (Postfix) with ESMTPSA id 155AE103AC; Wed, 28 Mar 2018 23:37:03 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orleans.occnc.com; s=curtis-orleans-20180228-204217; t=1522294624; bh=CHBkn1RFduSx4IKf0MTJTL8lVFXdwplRm6uhFSA+kq4=; h=To:cc:Reply-To:Subject:From:Date; b=r1prHdVUYODvMvcHQu5IjAv2LT2Z8SowoJpZGm6lXJG5co1F1//OO0BrYgEyXqOT4 kCr3yufoawpWiW9/SCrL/MfIa4wnvhc0152+u9SKDirX7L03/xdZLgEcCy5sHZhbQy j2jWW76yomctBCfjJh7iaNtvKdbZ56wUaMaT2San4gCBMs8foBwRDoY2NW4OW+ACPL kwHy5T+GSW0+eBL559PFH8pnqd1t/mz7oKbutcD4Xl0z5Wq/l6jK8PNxNmm7pnlDmx w+ZS3r7Vizs5CCReTLpzNbpc08kAjAneVuHz7rDOFEG8SVuHCrLWrKkQlgB55sNagK GOoqe+Dar/eJQ== To: freebsd-stable@freebsd.org cc: Curtis Villamizar Reply-To: Curtis Villamizar Subject: kern.maxswzone causing serious problems From: Curtis Villamizar MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16788.1522294617.1@harbor2-em2.v6only.occnc.com> Date: Wed, 28 Mar 2018 23:36:58 -0400 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 03:37:06 -0000 I'm starting to upgrade a set of servers from FreeBSD 11.0-STABLE #0 r308356 (OK, rather old) to FreeBSD 11.1-STABLE #0 r331152 without much success. I'm getting the occasionally discussed kern.maxswzone problems but I really do need to configure that swap space. On an upgraded server I'm getting (line continuation added for readability): warning: total configured swap (5242880 pages) \ exceeds maximum recommended amount (112288 pages). warning: increase kern.maxswzone or reduce amount of swap. warning: total configured swap (10485760 pages) \ exceeds maximum recommended amount (112288 pages). warning: increase kern.maxswzone or reduce amount of swap. The value previously used was not working. I ended up temporarily cutting swap in half as well to get rid of the error. This is only a symptom of a greater problem. This machine has for a long time run multiple VM which total 17GB memory on a server with 8 GB of physical memory. Normally things are fine becuase most of these servers are idle most of the time and all but a small memory footprint can be paged out. I have for years had 40 GB swap, with 20GB each on two spindles (at least going back to FreeBSD 9) on drives identical partitioning with mirrored partitions. \begin{talesofwoe} % ignore if busy When just trying to install base system software using md devices on at a time (no VM running yet) I had been getting "killed: out of swap space" messages. I got rid of this by reducing the size of the VM root partitions (most VM run zfs on another partition with not much on root so this was OK). Next problem was running the VM. I worked around this by reducing some VM memory (-m in bhyve) by half. I can get the whole set of VM to boot but now installing additional software (which involved just moving files with scp and running tar) doesn't work. At this point I have 9 GB of VM running on 8 GB physical memory and still couldn't even install software. Once the maxswzone message went away, so did all of these problems except my VMs now have half as much RAM each. Now each of the VM are reporting swap problems. And this is just upgrading one server to 11.1. \end{talesofwoe} This is a major regression for FreeBSD 11.1. The same value used in FreeBSD 11.0 should just work or there should be some documentation on how to set this (preferably the error message). If nothing else, some advice on converting a kern.maxswzone value from 11.0 to a working value for 11.1 would be nice. The entry in the loader(8) man page is not very helpful. btw- Reporting swap size in MB or KB in the error message would be helpful. In addition to pages would be fine. Mentioning what the highest value kern.maxswzone could be set to would also be helpful. Changing "warning: increase kern.maxswzone" to "warning: increase kern.maxswzone to %d" would be very helpful. \begin{naiveananlysis} The magic (or mess, depending on perspective) is mostly in "void swap_pager_swap_init(void)" in the file vm/swap_pager.c between lines 484 and 563 (in current which is same as stable/11 in this function). The diffs from known working r308356 to current show a diff at "@@ -538,21 +518,25 @@" which has swpctrie_zone and swblk_zone computed based on maxswzone, then runs uma_zone_reserve_kva based on maxswzone and potentially reduces it. In the older code a "Swap zone entries reduced" message would be produced if uma_zone_reserve_kva cut back (which is moved and the message changed a bit). But I didn't see this message so uma_zone_reserve_kva ran fine the first time without reducing "n". In the new code swap_maxpages and swzone are then set. swapon_check_swzone gives the warning but does nothing as far as I can tell other than two printfs. It doesn't appear to do any harm to have too much swap and ignore this warning (you just can't use it). There is a multiplier by SWAP_META_PAGES which is defined to be PCTRIE_COUNT which in sys/pctrie.h is defined as (1 << PCTRIE_WIDTH) and PCTRIE_WIDTH is 4 or 3 depending on __LP64__. swap_pager_swap_init calculates swap_maxpages but swapon_check_swzone doesn't use it, calculating local variable maxpages (the same way) instead. Since it seems that npages / SWAP_META_PAGES is related to what you'd want to set kern.maxswzone to. If so, a better set of printf might at least give better information. Note that VM_SWZONE_SIZE_MAX defaults to (276 * 128 * 1024) which would seem to be 128K * SWAP_META_PAGES * PAGE_SIZE = 8GB or 16GB depending on if __LP64__ is defined, but that is for i386 only. There is no definition of VM_SWZONE_SIZE_MAX for amd64 unless it picks this up from i386 which apparently it does. One problem is the conditional for using maxswzone only allows the swzone size to be reduced and not increased. Those people frobbing kern.maxswzone (including me for a time) were hopelessly wasting their time. Based on my math the old max swap was about 4 * available RAM. Naive or horribly naive? I haven't tried this yet ... (compiles) \end{naiveananlysis} After some playing around I ended up with the diffs below. On the host with 8 GB RAM and back to 40 GB swap I got (indent and line continuation added): warning: total configured swap (10485760 pages, 40960 MB) \ exceeds maximum recommended amount (8100744 pages, 31643 MB). warning: increase kern.maxswzone from 0 to 275425296 \ or reduce amount of swap. After setting kern.maxswzone to 275425296 no complaint. Still needs more testing. Currently reinstalling the full set of VMs. Later I'll try this on some of the VMs that have been configured with various memory and swap sizes. Also will revert to the conditions that worked fine in prior versions and stopped working with 11.1. Curtis ps - about the diffs: On amd64 VM_SWZONE_SIZE_MAX is not defined. On i386 it is defined based on a guess of sizeof(struct swblk). On amd64 that size is 136 and the guess on i386 is 276 so I made the guess a #define and have a comparison in the code to complain if the guess is off. The original code lets maxswzone decrease swapzone but not increase it, unlike prior code. I put in a limit to how much it could be increased (but not sure even that is legitimate - why not more). The replaced code does a printf on an attempt to set too high and reduces the value. The swapon_check_swzone check gives much more useful information than it did before including exactly what to set kern.maxswzone to end up with the recommended twice the swzone space. Index: i386/include/param.h =================================================================== --- i386/include/param.h (revision 331152) +++ i386/include/param.h (working copy) @@ -133,7 +133,8 @@ * lower due to fragmentation. */ #ifndef VM_SWZONE_SIZE_MAX -#define VM_SWZONE_SIZE_MAX (276 * 128 * 1024) +#define SIZEOF_SWBLK_GUESS 276 +#define VM_SWZONE_SIZE_MAX (SIZEOF_SWBLK_GUESS * 128 * 1024) #endif /* Index: vm/swap_pager.c =================================================================== --- vm/swap_pager.c (revision 331152) +++ vm/swap_pager.c (working copy) @@ -520,8 +520,16 @@ * on the number of pages in the system. */ n = vm_cnt.v_page_count / 2; - if (maxswzone && n > maxswzone / sizeof(struct swblk)) + /* reduce size or make larger within limits */ + if (maxswzone && (n != maxswzone / sizeof(struct swblk))) { + if (4 * n < maxswzone / sizeof(struct swblk)) { + n *= 4; + printf("kern.maxswzone (%lu) set too high: " + "limit is %lu\n", maxswzone, + n * sizeof(struct swblk)); + } n = maxswzone / sizeof(struct swblk); + } swpctrie_zone = uma_zcreate("swpctrie", pctrie_node_size(), NULL, NULL, pctrie_zone_init, NULL, UMA_ALIGN_PTR, UMA_ZONE_NOFREE | UMA_ZONE_VM); @@ -2141,11 +2149,20 @@ /* recommend using no more than half that amount */ if (npages > maxpages / 2) { - printf("warning: total configured swap (%lu pages) " - "exceeds maximum recommended amount (%lu pages).\n", - npages, maxpages / 2); - printf("warning: increase kern.maxswzone " - "or reduce amount of swap.\n"); + printf("warning: total configured swap (%lu pages, %lu MB) " + "exceeds maximum recommended amount (%lu pages, %lu MB).\n", + npages, swap_total / (1024*1024), + maxpages / 2, (maxpages / 2) * PAGE_SIZE / (1024*1024)); + printf("warning: increase kern.maxswzone from %lu to %lu " + "or reduce amount of swap.\n", maxswzone, + (maxpages / SWAP_META_PAGES) * 2 + * sizeof(struct swblk)); +#ifdef SIZEOF_SWBLK_GUESS + if (SIZEOF_SWBLK_GUESS != sizeof(struct swblk)) + printf("warning: bad guess on swblk size: " + "%d != %lu\n", + SIZEOF_SWBLK_GUESS, sizeof(struct swblk)); +#endif } } From owner-freebsd-stable@freebsd.org Thu Mar 29 06:25:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7482AF51831 for ; Thu, 29 Mar 2018 06:25:10 +0000 (UTC) (envelope-from kob6558@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 064227D1A5; Thu, 29 Mar 2018 06:25:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x22d.google.com with SMTP id u9so3010634ual.13; Wed, 28 Mar 2018 23:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FwbMsJ8o01E2dqL0e7aJPWiIAARtK1aSUaQCdorBmZI=; b=Gtmkfyxw4GAdrvhUvBkmmuzNfYcJcRdWbrUoE6/KvAZIBnEbNrCbwwCcUIYntyjFAc sGUygUyeD4AGRhkJ5a6tnwf3FclkL/wjKUyZ7/3UOul85cKknjclo/KhUdoadAo54iyT S5rxD4yTJ/ZKq213G9348a/OmCxwwrYh7k1a10R3oINmsd9e+zp6YYFI9YHel5FQHgxX 0X662DJ4TrRN01p1Oooy8Pk0VFyb52O5F5TelInvH977Wux4iAqaXwEK5HbBw47/HQFr pfeUx1vstWkCDcXqgkmfICFgxixi4zRt1mQgrkBFiTIty7w6WSdqXtWt5dPVgK2cyTDT 7FZA== 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=FwbMsJ8o01E2dqL0e7aJPWiIAARtK1aSUaQCdorBmZI=; b=CkCskGjNuSYs2lqalleisAwZbjS4KBPY1FI+qb0sKkTJHK0cAhlGrZh/GQFl3mlJyn Y4vDco6tiPWJE4aEigJuIoz7r2GdPe7zdtI5pKbCQ+pb9QsQmC04+3hnXojbdy56/Uhf 6o1nExMMTqTeyfzLypZoWZqB9trjS7RMgvaL/iTY/T9G8Fd+0fnlvmacJ722FLTXNQVp hV8Hp8R2Kxaty80Ya71QGcByRZgWhqrifAFTgL/hOANSshDHsM2DiTzPs87+Mk2pdYTz mv6yk4Ee1N0W+6b+BH5joHQkzGBatrX2dgNE/GdocJ/mE9ehPrrAAJ4cLXvnajKuoOPV XKNA== X-Gm-Message-State: AElRT7H2lagvAnF2bMRPMb43QR6pWaCQklmyOTKXpV3aGtUTYFSkp3w5 Aug4+O7LjukIVBudTu4ZriFdd+4EKN0gafYiVfQMpFNZ X-Google-Smtp-Source: AIpwx4+uHZToBjZAucoNTGycKTtP/MHOgoFon8EuEpdih9gDI+Qbr1ZEsrLicA1hSmQ00cWJK+qyS9O5dHYL7ZnQkq8= X-Received: by 10.176.23.11 with SMTP id j11mr4566113uaf.133.1522304709128; Wed, 28 Mar 2018 23:25:09 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.91.5 with HTTP; Wed, 28 Mar 2018 23:25:08 -0700 (PDT) In-Reply-To: <20180328164646.GC59700@in-addr.com> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru> <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> <20180328164646.GC59700@in-addr.com> From: Kevin Oberman Date: Wed, 28 Mar 2018 23:25:08 -0700 X-Google-Sender-Auth: H0tMU0XYhVzho6b9pMEOC4hjonA Message-ID: Subject: Re: KBI unexpexted change in stable/11 ? To: Gary Palmer Cc: Slawa Olhovchenkov , Eric van Gyzen , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 06:25:10 -0000 On Wed, Mar 28, 2018 at 9:46 AM, Gary Palmer wrote: > On Wed, Mar 28, 2018 at 11:16:49AM -0500, Eric van Gyzen wrote: > > On 03/28/2018 10:35, Slawa Olhovchenkov wrote: > > > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote: > > > > > >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote: > > >>> I am upgrade system to latest -STABLE and now see kernel crash: > > >>> > > >>> - loading virtualbox modules build on 11.1-RELEASE-p6 > > >>> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > >>> > > >>> Is this expected? I am mean about loading modules builded on > > >>> 11.1-RELEASE on any 11.1-STABLE. > > >> > > >> This is not expected. Can you bisect to find the stable/11 commit > that > > >> broke this? > > >> > > >> If you can roll back to 11.1-RELEASE, you could probably just > > >> buildkernel and installkernel from various points along stable/11. > That > > >> would save a lot of time by avoiding buildworld. > > > > > > r325665 is previos point and is good. > > > r331615 crashed. > > > Can I use some script for bisect? > > > > I'm not aware of a script for this. The only tool I've used is "git > > bisect", which is very handy if you're already familiar with git. > > You may want to try devel/p5-App-SVN-Bisect. Never used it, so > no idea if it's functional or helpful, just found it doing a quick > search > > Regards, > > Gary > _______________________________________________ > 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" > Regardless of intent, updates to port based modules can and and will break when the kernel is updated. lsof breaks quite often, as well. It touches things in the kernel that are intended for internal use only, so that is to be expected. I can't say that virtualbox-ose-kmod has had to be rebuilt because I put it into PORTS_MODULES a couple of years ago after having it fail on several occasions. Every time it gets broken again thee are lots of threads in STABLE like this one. It would be nice if this could be fixed, but it is the case. -- 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 Mar 29 13:39:05 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 562C4F76FA0 for ; Thu, 29 Mar 2018 13:39:05 +0000 (UTC) (envelope-from Lena@lena.kiev.ua) Received: from lena.kiev.ua (lena.kiev.ua [212.109.198.40]) (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 E07AA6E5FB for ; Thu, 29 Mar 2018 13:39:04 +0000 (UTC) (envelope-from Lena@lena.kiev.ua) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lena.kiev.ua; s=3; h=In-Reply-To:Content-Type:Mime-Version:References: Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=vq8ex+8weLHAWMnZCwAQQAFY/6MA1xgNjQTMH4A9bto=; b=Tzq3Xp3E6UD688t1RiV7RxfJOc wwmpR7Iuj1zNb6BwUgGm2DbphGX/30NtIIWeeZJ4ZGseHdoU9R6u+WF2u+By3jpjNAIm2lL3zNbOt K2HUGqZV1c7w4cr7n0xO/NZ52gLP8wnFyVj4Ar1os6SEO4hUpUU8VWrwWsFoAoA5YXxE=; Received: from ip-1cd0.rusanovka-net.kiev.ua ([94.244.28.208] helo=bedside.lena.kiev.ua) by lena.kiev.ua with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1f1Xld-000Nyx-14 for freebsd-stable@freebsd.org; Thu, 29 Mar 2018 16:39:02 +0300 Received: from bedside.lena.kiev.ua (localhost.lena.kiev.ua [127.0.0.1]) by bedside.lena.kiev.ua (8.15.2/8.15.2) with ESMTP id w2TDcsrV007686 for ; Thu, 29 Mar 2018 16:38:54 +0300 (EEST) (envelope-from Lena@lena.kiev.ua) Received: (from lena@localhost) by bedside.lena.kiev.ua (8.15.2/8.15.2/Submit) id w2TDcshX007685 for freebsd-stable@freebsd.org; Thu, 29 Mar 2018 16:38:54 +0300 (EEST) (envelope-from Lena@lena.kiev.ua) Date: Thu, 29 Mar 2018 16:38:54 +0300 From: Lena@lena.kiev.ua To: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180329133853.GH805@lena.kiev> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 13:39:05 -0000 > From: Kevin Oberman > Regardless of intent, updates to port based modules can and and will break > when the kernel is updated. Are packages for pkg.freebsd.org built on -STABLE or latest -RELEASE? After 11.2 is released, if package for nvidia-driver is installed or upgraded on a machine with 11.1-RELEASE, will it crash the kernel? If the port nvidia-driver-304 is updated before 11.2 is released, will `pkg upgrade` crash the kernel? From owner-freebsd-stable@freebsd.org Thu Mar 29 13:45:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9056BF77777 for ; Thu, 29 Mar 2018 13:45:11 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) (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 39D406EC01 for ; Thu, 29 Mar 2018 13:45:11 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f51.google.com with SMTP id q5-v6so8476599lff.12 for ; Thu, 29 Mar 2018 06:45:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hBp4nxkP2KBsQw6JLlyzxIVSmY3BbWjZ1Je+QloS5xQ=; b=kmd0QZ63fiwFI6fohqzMBOCvcn/sI/348zn3Aewb6ogp/nTXiMeH4wOBLPBF0OtS2G KRpjJEFndoKPQFR6CODgzbmkh0dRtjO4K6dYe28ElxsNtq59XfYvDgRVjHTl4M2U4IEP nIyYZS+xpQXMP1zkOXNx6ctBT+CNdvZGLD1hWhN+PNUZ9dWddG6J9s23trffhN2tPcnG vSNzCyz5S/nN9DByAJr5RtH/6hAOYKwTb1jlXFYYWFhIyki4zGjX2bqx5TX6n3r2gf7Y oWth2qRibZV4kr92aGJ4ADjgtjqCllVQkkv1eTPHNzoQA8picS7k6usVsiN0nGR4azGA +Tyg== X-Gm-Message-State: AElRT7GSRgkeNmS9kcF+LZs6QdFbgfYCK72ursI/UOMzd0FCCOj6IWnX KZnjUGU/by4iFgsgHd3navFyEkgK X-Google-Smtp-Source: AIpwx4/uEH/lGF1/IRhoocOD0sk6XHcHGfKFsuavAmfbRXWwQSSyeDm1eSHKqP2R/RQgWTsCUnkIQQ== X-Received: by 2002:a19:a705:: with SMTP id q5-v6mr5225533lfe.2.1522331103314; Thu, 29 Mar 2018 06:45:03 -0700 (PDT) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com. [209.85.215.48]) by smtp.gmail.com with ESMTPSA id i18-v6sm1153732lfj.50.2018.03.29.06.45.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Mar 2018 06:45:03 -0700 (PDT) Received: by mail-lf0-f48.google.com with SMTP id u3-v6so8488392lff.5 for ; Thu, 29 Mar 2018 06:45:03 -0700 (PDT) X-Received: by 10.46.114.26 with SMTP id n26mr5641362ljc.74.1522331102923; Thu, 29 Mar 2018 06:45:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 29 Mar 2018 06:44:42 -0700 (PDT) In-Reply-To: <20180329133853.GH805@lena.kiev> References: <20180329133853.GH805@lena.kiev> From: Kyle Evans Date: Thu, 29 Mar 2018 08:44:42 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: KBI unexpexted change in stable/11 ? To: Lena@lena.kiev.ua Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 13:45:11 -0000 On Thu, Mar 29, 2018 at 8:38 AM, wrote: >> From: Kevin Oberman > >> Regardless of intent, updates to port based modules can and and will break >> when the kernel is updated. > > Are packages for pkg.freebsd.org built on -STABLE or latest -RELEASE? > > After 11.2 is released, if package for nvidia-driver > is installed or upgraded on a machine with 11.1-RELEASE, > will it crash the kernel? > > If the port nvidia-driver-304 is updated before 11.2 is released, > will `pkg upgrade` crash the kernel? Packages are built on the earliest supported release of a branch; never from the stable branch. These packages will be built from 11.1 until it goes EOL a couple months after 11.2 release. Breakage of packages from an earlier release of a branch is not ideal, so it would still be most helpful if someone could bissect this so that we can assess the breakage and figure out next steps before it becomes a bigger problem with the impending release. I've heard good things about the aforementioned devel/p5-App-SVN-Bisect for these purposes. Thanks, Kyle Evans From owner-freebsd-stable@freebsd.org Thu Mar 29 16:59:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E802CF60921 for ; Thu, 29 Mar 2018 16:59:54 +0000 (UTC) (envelope-from veronica.baker@showezdeligates.com) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) (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 73C6A785E9 for ; Thu, 29 Mar 2018 16:59:54 +0000 (UTC) (envelope-from veronica.baker@showezdeligates.com) Received: from homiemail-a45.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) by hapkido.dreamhost.com (Postfix) with ESMTP id E383E8E2CB for ; Thu, 29 Mar 2018 09:59:52 -0700 (PDT) Received: from homiemail-a45.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTP id 2814FE724 for ; Thu, 29 Mar 2018 09:59:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=showezdeligates.com; h= from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=showezdeligates.com; bh=vOs1z7EUgE AHVi5Ep4nJ4tAepQA=; b=d+y3VjuC3oKP2kTpJ6rXN+VUe5tse7bVbabsuueOm6 11Z29hOn0/rRWP6RDlc/fTHQrTZ7ddJ8oqdDfuPtmYRryBFSQm8evoFioJeZy/fU w55OstFGfSBWs1d/UmrmOeBK1jN7aXo5Z3OWgpe4+RzloYoTtBWzenCttgb8Ci3Y o= Received: from NESS14PC (unknown [106.51.21.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: veronica.baker@showezdeligates.com) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTPSA id 1A0D2E71E for ; Thu, 29 Mar 2018 09:59:44 -0700 (PDT) From: "Veronica Baker" To: References: In-Reply-To: Subject: Delegates Email list of Atlanta Apartment Association 2018 Date: Thu, 29 Mar 2018 12:59:28 -0400 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdPF05vJbzoiiCPDSMWN44RF3flbeABCPxQgACig98AAAAAV8AAAAAHgAAAABlAAAALsEAAAABQAAAAABgAAAAAHMAAAAAdgAAAACfAAAAINkAAAAi9gAAAAFKAAAAAIUA== Content-Language: en-in Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 16:59:55 -0000 Hi, Would you be interested in Attendees Email List Of Atlanta Apartment Association 2018.? Attendees: . Decision Makers . Apartment owners . Managers . Suppliers, and Professionals List includes: E-mails, contact number and other fields on an excel sheet. Would you like to see counts and pricing details available.? Looking forward for your email. Regards, Veronica Baker| B.D.Exe If you do not wish to receive future emails from us, please reply as "Exclude Me" From owner-freebsd-stable@freebsd.org Thu Mar 29 18:21:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A14E2F6A508 for ; Thu, 29 Mar 2018 18:21:52 +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 37CE67CA62; Thu, 29 Mar 2018 18:21:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1f1cBD-000GTp-Gm; Thu, 29 Mar 2018 21:21:43 +0300 Date: Thu, 29 Mar 2018 21:21:43 +0300 From: Slawa Olhovchenkov To: Kevin Oberman Cc: Gary Palmer , Eric van Gyzen , FreeBSD-STABLE Mailing List , kib@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180329182143.GE6612@zxy.spb.ru> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru> <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> <20180328164646.GC59700@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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.25 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, 29 Mar 2018 18:21:52 -0000 On Wed, Mar 28, 2018 at 11:25:08PM -0700, Kevin Oberman wrote: > > > > r325665 is previos point and is good. > > > > r331615 crashed. > > > > Can I use some script for bisect? > > > > > > I'm not aware of a script for this. The only tool I've used is "git > > > bisect", which is very handy if you're already familiar with git. > > > > You may want to try devel/p5-App-SVN-Bisect. Never used it, so > > no idea if it's functional or helpful, just found it doing a quick > > search > > It would be nice if this could be fixed, but it is the case. r328475 bad (tzdata) r328469 in progress (kib, sys/vm) r328463 in progress (don't touch kernel) r328462 good I mean r328469 break KBI. From owner-freebsd-stable@freebsd.org Thu Mar 29 20:22:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78F0CF73FAE for ; Thu, 29 Mar 2018 20:22:28 +0000 (UTC) (envelope-from kib@freebsd.org) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D254B83149; Thu, 29 Mar 2018 20:22:27 +0000 (UTC) (envelope-from kib@freebsd.org) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w2TKMGpA046515 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 29 Mar 2018 23:22:20 +0300 (EEST) (envelope-from kib@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w2TKMGpA046515 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w2TKMGp5046514; Thu, 29 Mar 2018 23:22:16 +0300 (EEST) (envelope-from kib@freebsd.org) X-Authentication-Warning: tom.home: kostik set sender to kib@freebsd.org using -f Date: Thu, 29 Mar 2018 23:22:16 +0300 From: Konstantin Belousov To: Slawa Olhovchenkov Cc: Kevin Oberman , Gary Palmer , Eric van Gyzen , FreeBSD-STABLE Mailing List Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <20180329202216.GH1774@kib.kiev.ua> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru> <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> <20180328164646.GC59700@in-addr.com> <20180329182143.GE6612@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180329182143.GE6612@zxy.spb.ru> User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 20:22:28 -0000 On Thu, Mar 29, 2018 at 09:21:43PM +0300, Slawa Olhovchenkov wrote: > On Wed, Mar 28, 2018 at 11:25:08PM -0700, Kevin Oberman wrote: > > > > > > r325665 is previos point and is good. > > > > > r331615 crashed. > > > > > Can I use some script for bisect? > > > > > > > > I'm not aware of a script for this. The only tool I've used is "git > > > > bisect", which is very handy if you're already familiar with git. > > > > > > You may want to try devel/p5-App-SVN-Bisect. Never used it, so > > > no idea if it's functional or helpful, just found it doing a quick > > > search > > > > It would be nice if this could be fixed, but it is the case. > > r328475 bad (tzdata) > r328469 in progress (kib, sys/vm) > r328463 in progress (don't touch kernel) > r328462 good > > I mean r328469 break KBI. This commit is basically required to avoid significant confusion between HEAD and stable code. Its absense might make other merges impossible or quite hard. In fact, my opinion is that the real bug is elsewere. We do provide vm_map_min/max KPI, but the KPI is not KBI-stable because it encodes struct vm_map layout into binaries which (correctly) use KPI instead of directly accessing struct vm_map. This should be fixed, I put the review https://reviews.freebsd.org/D14902 for it. From owner-freebsd-stable@freebsd.org Thu Mar 29 21:54:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41E7BF79939 for ; Thu, 29 Mar 2018 21:54:13 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "resqmta-po-01v.sys.comcast.net", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D575686CD6 for ; Thu, 29 Mar 2018 21:54:12 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-04v.sys.comcast.net with ESMTP id 1fU7f4XpUiTCi1fUpfgIce; Thu, 29 Mar 2018 21:54:11 +0000 Received: from koitsu.org ([71.198.44.84]) by resomta-po-01v.sys.comcast.net with SMTP id 1fUof8IwaVIeT1fUofhvNI; Thu, 29 Mar 2018 21:54:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3DDB81581F99; Thu, 29 Mar 2018 14:54:10 -0700 (PDT) Date: Thu, 29 Mar 2018 14:54:10 -0700 From: Jeremy Chadwick To: curtis@orleans.occnc.com Cc: freebsd-stable@freebsd.org Subject: Re: kern.maxswzone causing serious problems Message-ID: <20180329215410.GA60880@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-CMAE-Envelope: MS4wfMq0wjiRNSRGks93kHqNkJHEJTXe4gW3JarjnRvRbNz2XiT3gLwzm+kBqrUbzEPJ83h+BktJi1bwHN4xL7nEbv6UyNxy1q+8YoLIftDxceGEob1Ky4sS WB+hrfs4sukkRrf1Vffu/pK/vHixwt0x8EofUOLIHTIJcTcrdoXG8Tjfg7q8C7ededsSfQqwD+y2LdGQuWP+Oysc/ecIedsaFaU= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 29 Mar 2018 21:54:13 -0000 I am not subscribed to -stable, so please keep me CC'd. I mailed -stable about this problem, or a variation of it, earlier this month: https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088467.html What isn't publicly visible is the list of individuals I CC'd on that mail who had touched this code in recent days: kib@freebsd.org, des@freebsd.org, pluknet@freebsd.org, eadler@freebsd.org I received no response from them on this matter. At least two, however, have been extremely busy commit-wise, so I imagine folks are just swamped right now + have higher priorities. I did not read or review your {naiveanalysis} section or your patch, as tinkering with VM design/internals is *way* outside my comfort zone. I will say that printing the sizes in a unit other than pages would be generally helpful; I did try to figure out what value to use for kern.maxswzone as a workaround by digging through kernel code but gave up, as I wasn't able to truly determine what "pages" actually represented (size-wise) in this specific context. I hope someone with src commit bit will comment, as code slush for 11.2-RELEASE begins on April 20th: https://www.freebsd.org/releases/11.2R/schedule.html Else a separate PR can be opened if requested. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@freebsd.org Fri Mar 30 01:23:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AC34F60896 for ; Fri, 30 Mar 2018 01:23:11 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from mta2-em1.orleans.occnc.com (mta2-em1.orleans.occnc.com [IPv6:2001:470:88e6:1::140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta2.orleans.occnc.com", Issuer "OCCNC secondary CA (ca1a2a)" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A3AC56EA7D for ; Fri, 30 Mar 2018 01:23:10 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from spinnaker.v6only.occnc.com (spinnaker-em3.v6ds.occnc.com [IPv6:2001:470:88e6:3::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: smmsp@occnc.com) by mta2-em1.orleans.occnc.com (Postfix) with ESMTPSA id 58AF21044F; Thu, 29 Mar 2018 21:23:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orleans.occnc.com; s=curtis-orleans-20180228-204217; t=1522372989; bh=2xjOoS4pswtvICBGe64fW58xUBuqYy8IHPqupsP3zhY=; h=Subject:References:To:Cc:From:Date:In-Reply-To; b=xvV6/DrqhtR1NmvvXAIQPILaJMm0aoryEiv4455briMcKOM/15JgAklKPnnUvL6ET IbiyPX4mwjkKNwNj6e5EGk5eHmDq7Bacwla3bmscYniCWrDGD3/ho+sn2CTGxksUe+ /Yp7NgQmISDTLFp9t0FWf6AxgGnnXWyTkyKa9SCDaw4Y2480/wrx63uP8aIJeaPvCP SRpF7e+W4iWCsGL5xF1MRt9bk9yeQ3EFnLQ3ZQZ0IZmbzEP9oAtnTvOnNK1mmiDSXn KonFde0aOyxBxqXozPryTYDGwqlnCluW9TbDtBq0Lo46firnH405R6J9tZIMfHRgu5 BzfF7Yupm30RQ== Subject: Re: kern.maxswzone causing serious problems References: To: freebsd-stable@freebsd.org Cc: Curtis Villamizar From: Curtis Villamizar Message-ID: <387a65b7-d221-0a10-b801-1dd573054e10@orleans.occnc.com> Date: Thu, 29 Mar 2018 21:23:08 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 30 Mar 2018 01:23:11 -0000 Replying to myself. Oops - error in the diff: -+ (maxpages / SWAP_META_PAGES) * 2 ++ (npages / SWAP_META_PAGES) * 2 The prior code worked but only because it doubled the allowable swap. This provides the right value for kern.maxswzone for the amount of swap you have for the complaint to go away. I confirmed that by reducing the kern.maxswzone value by a small amount (under 1K) and the complaint returned. I am currently running a regression test over the host and the entire set of VMs running on it to makes sure there are no more surprises. Since I generate configs it is easy to change the way kern.maxswzone is computed when generating boot/loader.conf for a given host or VM. Will check back later after regression testing. Apparently the best way to get this to get some attention is to file a bug so once the changes are fully verified in the regression testing I'll do that. Just in case there is some further interaction with using more swap that recommended by the current code. Curtis On 03/28/18 23:36, Curtis Villamizar wrote: > I'm starting to upgrade a set of servers from FreeBSD 11.0-STABLE #0 > r308356 (OK, rather old) to FreeBSD 11.1-STABLE #0 r331152 without > much success. I'm getting the occasionally discussed kern.maxswzone > problems but I really do need to configure that swap space. > > On an upgraded server I'm getting (line continuation added for > readability): > > warning: total configured swap (5242880 pages) \ > exceeds maximum recommended amount (112288 pages). > warning: increase kern.maxswzone or reduce amount of swap. > warning: total configured swap (10485760 pages) \ > exceeds maximum recommended amount (112288 pages). > warning: increase kern.maxswzone or reduce amount of swap. > > The value previously used was not working. I ended up temporarily > cutting swap in half as well to get rid of the error. This is only a > symptom of a greater problem. > > This machine has for a long time run multiple VM which total 17GB > memory on a server with 8 GB of physical memory. Normally things are > fine becuase most of these servers are idle most of the time and all > but a small memory footprint can be paged out. I have for years had > 40 GB swap, with 20GB each on two spindles (at least going back to > FreeBSD 9) on drives identical partitioning with mirrored partitions. > > \begin{talesofwoe} % ignore if busy > > When just trying to install base system software using md devices on > at a time (no VM running yet) I had been getting "killed: out of swap > space" messages. I got rid of this by reducing the size of the VM > root partitions (most VM run zfs on another partition with not much on > root so this was OK). Next problem was running the VM. I worked > around this by reducing some VM memory (-m in bhyve) by half. I can > get the whole set of VM to boot but now installing additional software > (which involved just moving files with scp and running tar) doesn't > work. At this point I have 9 GB of VM running on 8 GB physical memory > and still couldn't even install software. Once the maxswzone message > went away, so did all of these problems except my VMs now have half as > much RAM each. Now each of the VM are reporting swap problems. And > this is just upgrading one server to 11.1. > > \end{talesofwoe} > > This is a major regression for FreeBSD 11.1. The same value used in > FreeBSD 11.0 should just work or there should be some documentation on > how to set this (preferably the error message). If nothing else, some > advice on converting a kern.maxswzone value from 11.0 to a working > value for 11.1 would be nice. The entry in the loader(8) man page is > not very helpful. > > btw- Reporting swap size in MB or KB in the error message would be > helpful. In addition to pages would be fine. Mentioning what the > highest value kern.maxswzone could be set to would also be helpful. > Changing "warning: increase kern.maxswzone" to "warning: increase > kern.maxswzone to %d" would be very helpful. > > \begin{naiveananlysis} > > The magic (or mess, depending on perspective) is mostly in "void > swap_pager_swap_init(void)" in the file vm/swap_pager.c between lines > 484 and 563 (in current which is same as stable/11 in this function). > The diffs from known working r308356 to current show a diff at "@@ > -538,21 +518,25 @@" which has swpctrie_zone and swblk_zone computed > based on maxswzone, then runs uma_zone_reserve_kva based on maxswzone > and potentially reduces it. > > In the older code a "Swap zone entries reduced" message would be > produced if uma_zone_reserve_kva cut back (which is moved and the > message changed a bit). But I didn't see this message so > uma_zone_reserve_kva ran fine the first time without reducing "n". In > the new code swap_maxpages and swzone are then set. > swapon_check_swzone gives the warning but does nothing as far as I can > tell other than two printfs. It doesn't appear to do any harm to have > too much swap and ignore this warning (you just can't use it). > > There is a multiplier by SWAP_META_PAGES which is defined to be > PCTRIE_COUNT which in sys/pctrie.h is defined as (1 << PCTRIE_WIDTH) > and PCTRIE_WIDTH is 4 or 3 depending on __LP64__. > > swap_pager_swap_init calculates swap_maxpages but swapon_check_swzone > doesn't use it, calculating local variable maxpages (the same way) > instead. Since it seems that npages / SWAP_META_PAGES is related to > what you'd want to set kern.maxswzone to. If so, a better set of > printf might at least give better information. > > Note that VM_SWZONE_SIZE_MAX defaults to (276 * 128 * 1024) which > would seem to be 128K * SWAP_META_PAGES * PAGE_SIZE = 8GB or 16GB > depending on if __LP64__ is defined, but that is for i386 only. There > is no definition of VM_SWZONE_SIZE_MAX for amd64 unless it picks this > up from i386 which apparently it does. > > One problem is the conditional for using maxswzone only allows the > swzone size to be reduced and not increased. Those people frobbing > kern.maxswzone (including me for a time) were hopelessly wasting their > time. > > Based on my math the old max swap was about 4 * available RAM. > > Naive or horribly naive? I haven't tried this yet ... (compiles) > > \end{naiveananlysis} > > After some playing around I ended up with the diffs below. > > On the host with 8 GB RAM and back to 40 GB swap I got (indent and > line continuation added): > > warning: total configured swap (10485760 pages, 40960 MB) \ > exceeds maximum recommended amount (8100744 pages, 31643 MB). > warning: increase kern.maxswzone from 0 to 275425296 \ > or reduce amount of swap. > > After setting kern.maxswzone to 275425296 no complaint. > > Still needs more testing. Currently reinstalling the full set of VMs. > Later I'll try this on some of the VMs that have been configured with > various memory and swap sizes. Also will revert to the conditions > that worked fine in prior versions and stopped working with 11.1. > > Curtis > > > ps - about the diffs: > > On amd64 VM_SWZONE_SIZE_MAX is not defined. On i386 it is defined > based on a guess of sizeof(struct swblk). On amd64 that size is 136 > and the guess on i386 is 276 so I made the guess a #define and have a > comparison in the code to complain if the guess is off. > > The original code lets maxswzone decrease swapzone but not increase > it, unlike prior code. I put in a limit to how much it could be > increased (but not sure even that is legitimate - why not more). The > replaced code does a printf on an attempt to set too high and reduces > the value. > > The swapon_check_swzone check gives much more useful information than > it did before including exactly what to set kern.maxswzone to end up > with the recommended twice the swzone space. > > > Index: i386/include/param.h > =================================================================== > --- i386/include/param.h (revision 331152) > +++ i386/include/param.h (working copy) > @@ -133,7 +133,8 @@ > * lower due to fragmentation. > */ > #ifndef VM_SWZONE_SIZE_MAX > -#define VM_SWZONE_SIZE_MAX (276 * 128 * 1024) > +#define SIZEOF_SWBLK_GUESS 276 > +#define VM_SWZONE_SIZE_MAX (SIZEOF_SWBLK_GUESS * 128 * 1024) > #endif > > /* > Index: vm/swap_pager.c > =================================================================== > --- vm/swap_pager.c (revision 331152) > +++ vm/swap_pager.c (working copy) > @@ -520,8 +520,16 @@ > * on the number of pages in the system. > */ > n = vm_cnt.v_page_count / 2; > - if (maxswzone && n > maxswzone / sizeof(struct swblk)) > + /* reduce size or make larger within limits */ > + if (maxswzone && (n != maxswzone / sizeof(struct swblk))) { > + if (4 * n < maxswzone / sizeof(struct swblk)) { > + n *= 4; > + printf("kern.maxswzone (%lu) set too high: " > + "limit is %lu\n", maxswzone, > + n * sizeof(struct swblk)); > + } > n = maxswzone / sizeof(struct swblk); > + } > swpctrie_zone = uma_zcreate("swpctrie", pctrie_node_size(), NULL, NULL, > pctrie_zone_init, NULL, UMA_ALIGN_PTR, > UMA_ZONE_NOFREE | UMA_ZONE_VM); > @@ -2141,11 +2149,20 @@ > > /* recommend using no more than half that amount */ > if (npages > maxpages / 2) { > - printf("warning: total configured swap (%lu pages) " > - "exceeds maximum recommended amount (%lu pages).\n", > - npages, maxpages / 2); > - printf("warning: increase kern.maxswzone " > - "or reduce amount of swap.\n"); > + printf("warning: total configured swap (%lu pages, %lu MB) " > + "exceeds maximum recommended amount (%lu pages, %lu MB).\n", > + npages, swap_total / (1024*1024), > + maxpages / 2, (maxpages / 2) * PAGE_SIZE / (1024*1024)); > + printf("warning: increase kern.maxswzone from %lu to %lu " > + "or reduce amount of swap.\n", maxswzone, > + (maxpages / SWAP_META_PAGES) * 2 > + * sizeof(struct swblk)); > +#ifdef SIZEOF_SWBLK_GUESS > + if (SIZEOF_SWBLK_GUESS != sizeof(struct swblk)) > + printf("warning: bad guess on swblk size: " > + "%d != %lu\n", > + SIZEOF_SWBLK_GUESS, sizeof(struct swblk)); > +#endif > } > } > From owner-freebsd-stable@freebsd.org Sat Mar 31 15:51:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57C31F6B332 for ; Sat, 31 Mar 2018 15:51:38 +0000 (UTC) (envelope-from nz@thiemo.net) Received: from nox.thiemo.net (nox.thiemo.net [IPv6:2a01:4f8:110:1345::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nox.thiemo.net", Issuer "thiemo.net CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB13969327 for ; Sat, 31 Mar 2018 15:51:37 +0000 (UTC) (envelope-from nz@thiemo.net) Received: from mygiea.ext.thiemo.net (styx.row.thiemo.net [217.7.216.36]) by nox.thiemo.net (8.15.2/8.15.2) with ESMTPS id w2VFpP9M074384 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 31 Mar 2018 17:51:36 +0200 (CEST) (envelope-from nz@thiemo.net) X-Clacks-Overhead: GNU Terry Pratchett Received: from gearloose.srv.thiemo.net (styx.row.thiemo.net [217.7.216.36]) (authenticated bits=0) by styx.row.thiemo.net (8.14.5/8.14.5) with ESMTP id w2VFpL8c032678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 31 Mar 2018 17:51:25 +0200 (CEST) Subject: Fwd: buildworld from 11.1-R-p8 to stable/11 fails in contrib/llvm References: To: freebsd-stable@freebsd.org From: Thiemo Nordenholz X-Forwarded-Message-Id: Message-ID: Date: Sat, 31 Mar 2018 17:51:24 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.6.2 (nox.thiemo.net [78.46.48.50]); Sat, 31 Mar 2018 17:51:36 +0200 (CEST) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (styx.row.thiemo.net [10.200.0.2]); Sat, 31 Mar 2018 17:51:25 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 31 Mar 2018 15:51:38 -0000 Hello, having first upgraded from 11.1-RELEASE to FreeBSD 11.1-RELEASE-p8 amd64 via freebsd-upgrade, I wanted to switch to -stable and svnup'ed to r331758. Subsequent "make buildworld" fails when compiling what looks like a part of llvm: c++ -O2 -pipe -I/usr/src/contrib/llvm/tools/lldb/include -I/usr/src/contrib/llvm/tools/lldb/source -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/FreeBSD -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/POSIX -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/Utility -I/usr/obj/usr/src/lib/clang/libllvm -I/usr/obj/usr/src/lib/clang/libclang -DLLDB_DISABLE_PYTHON -I/usr/src/contrib/llvm/tools/clang/include -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_STATIC_ANALYZER -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DDEFAULT_SYSROOT=\"\" -ffunction-sections -fdata-sections -MD -MF.depend.Host_common_MainLoop.o -MTHost/common/MainLoop.o -fstack-protector-strong -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/lldb/source/Host/common/MainLoop.cpp -o Host/common/MainLoop.o /usr/src/contrib/llvm/tools/lldb/source/Host/common/MainLoop.cpp:144:10: error: no viable conversion from returned value of type 'int' to function return type 'sigset_t' (aka '__sigset') return 0; As the respective source code seems to be in the tree for quite some time, I wonder why I cannot seem to find other such issues occurring - what am I missing here? I have no /etc/make.conf, no MAKEFLAGS set, and emptied /usr/obj/ before each of my attempts (-j8, -j4, and no flags, with clang and gcc (see below)). Trying "env WITHOUT_CLANG=YES WITH_GCC=YES make buildworld" also fails, however in /usr/src/lib/libc/tests/ssp (as make says): cc -O2 -pipe -fstack-protector-all -Wstack-protector -fsanitize=bounds -g -std=gnu99 -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Qunused-arguments -o h_raw.full h_raw.o /usr/obj/usr/src/tmp/usr/bin/ld: /usr/obj/usr/src/tmp/usr/lib/clang/5.0.1/lib/freebsd/libclang_rt.ubsan_standalone-x86_64.a: No such file: No such file or directory cc: error: linker command failed with exit code 1 (use -v to see invocation) Again - as I did not see similar issues on the mailing list, I wonder what's going on here. Perhaps anyone else can shed some light or give me a hint on how to proceed. I'd really like to try out the graphics/drm-next-kmod port... Best wishes, and happy holidays to those so inclined, Thiemo -- Query a PGP key server for my public key 0x11E4B9A92AAE0A34. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml From owner-freebsd-stable@freebsd.org Sat Mar 31 16:56:20 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB0BCF6FF2C for ; Sat, 31 Mar 2018 16:56:19 +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 577826BDFD for ; Sat, 31 Mar 2018 16:56:19 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0C75536A1D; Sat, 31 Mar 2018 18:56:18 +0200 (CEST) From: Dimitry Andric Message-Id: <8C30CD25-46EA-4E26-8E27-F6FB063AE232@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_1BEFC18A-5464-4C79-A185-39953F4F2D1B"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: buildworld from 11.1-R-p8 to stable/11 fails in contrib/llvm Date: Sat, 31 Mar 2018 18:56:17 +0200 In-Reply-To: Cc: freebsd-stable@freebsd.org To: Thiemo Nordenholz References: X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 31 Mar 2018 16:56:20 -0000 --Apple-Mail=_1BEFC18A-5464-4C79-A185-39953F4F2D1B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 31 Mar 2018, at 17:51, Thiemo Nordenholz wrote: >=20 > having first upgraded from 11.1-RELEASE to FreeBSD 11.1-RELEASE-p8 = amd64 via freebsd-upgrade, I wanted to switch to -stable and svnup'ed to = r331758. >=20 > Subsequent "make buildworld" fails when compiling what looks like a = part of llvm: >=20 > c++ -O2 -pipe -I/usr/src/contrib/llvm/tools/lldb/include = -I/usr/src/contrib/llvm/tools/lldb/source = -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/FreeBSD = -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/POSIX = -I/usr/src/contrib/llvm/tools/lldb/source/Plugins/Process/Utility = -I/usr/obj/usr/src/lib/clang/libllvm = -I/usr/obj/usr/src/lib/clang/libclang -DLLDB_DISABLE_PYTHON = -I/usr/src/contrib/llvm/tools/clang/include -DCLANG_ENABLE_ARCMT = -DCLANG_ENABLE_STATIC_ANALYZER -I/usr/src/lib/clang/include = -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL = -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG = -DLLVM_DEFAULT_TARGET_TRIPLE=3D\"x86_64-unknown-freebsd11.1\" = -DLLVM_HOST_TRIPLE=3D\"x86_64-unknown-freebsd11.1\" = -DDEFAULT_SYSROOT=3D\"\" -ffunction-sections -fdata-sections -MD = -MF.depend.Host_common_MainLoop.o -MTHost/common/MainLoop.o = -fstack-protector-strong -Qunused-arguments -std=3Dc++11 = -fno-exceptions -fno-rtti -stdlib=3Dlibc++ -Wno-c++11-extensions -c = /usr/src/contrib/llvm/tools/lldb/source/Host/common/MainLoop.cpp -o = Host/common/MainLoop.o > = /usr/src/contrib/llvm/tools/lldb/source/Host/common/MainLoop.cpp:144:10: = error: no viable conversion from returned value of type 'int' to = function return type 'sigset_t' (aka '__sigset') > return 0; >=20 > As the respective source code seems to be in the tree for quite some = time, I wonder why I cannot seem to find other such issues occurring - = what am I missing here? I have no /etc/make.conf, no MAKEFLAGS set, and = emptied /usr/obj/ before each of my attempts (-j8, -j4, and no flags, = with clang and gcc (see below)). My guess is that your source tree is inconsistently updated. This error = can only occur when SIGNAL_POLLING_UNSUPPORTED is defined to 1 in = MainLoop.cpp, and that can only occur if your copy of = lib/clang/include/lldb/Host/Config.h is either out of date, corrupt, or = empty. Can you check whether the following lines exist in your copy of = lib/clang/include/lldb/Host/Config.h: #define HAVE_SYS_EVENT_H 1 #define HAVE_PPOLL 1 If not, it is best to delete your source tree and do a fresh checkout. > Trying "env WITHOUT_CLANG=3DYES WITH_GCC=3DYES make buildworld" also = fails, however in /usr/src/lib/libc/tests/ssp (as make says): >=20 > cc -O2 -pipe -fstack-protector-all -Wstack-protector -fsanitize=3Dbounds= -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wall = -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body = -Wno-string-plus-int -Wno-unused-const-variable = -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality = -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef = -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum = -Wno-knr-promoted-parameter -Qunused-arguments -o h_raw.full h_raw.o > /usr/obj/usr/src/tmp/usr/bin/ld: = /usr/obj/usr/src/tmp/usr/lib/clang/5.0.1/lib/freebsd/libclang_rt.ubsan_sta= ndalone-x86_64.a: No such file: No such file or directory > cc: error: linker command failed with exit code 1 (use -v to see = invocation) >=20 > Again - as I did not see similar issues on the mailing list, I wonder = what's going on here. Perhaps anyone else can shed some light or give me = a hint on how to proceed. I'd really like to try out the = graphics/drm-next-kmod port... In this case, I think you would also need WITHOUT_CLANG_BOOTSTRAP. Or = alternatively, build using WITHOUT_TESTS. -Dimitry --Apple-Mail=_1BEFC18A-5464-4C79-A185-39953F4F2D1B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWr+9sQAKCRCwXqMKLiCW o1dBAKCq4G9X1Q2P/qWS92DtwLV2e+AkNwCgysJ4WmbDiRYzM3xJNVWsBVyKa/c= =uIgS -----END PGP SIGNATURE----- --Apple-Mail=_1BEFC18A-5464-4C79-A185-39953F4F2D1B-- From owner-freebsd-stable@freebsd.org Sat Mar 31 19:17:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB438F79499 for ; Sat, 31 Mar 2018 19:17:36 +0000 (UTC) (envelope-from nz@thiemo.net) Received: from nox.thiemo.net (nox.thiemo.net [IPv6:2a01:4f8:110:1345::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nox.thiemo.net", Issuer "thiemo.net CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D199721DB; Sat, 31 Mar 2018 19:17:36 +0000 (UTC) (envelope-from nz@thiemo.net) Received: from mygiea.ext.thiemo.net (styx.row.thiemo.net [217.7.216.36]) by nox.thiemo.net (8.15.2/8.15.2) with ESMTPS id w2VJHOIu076341 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 31 Mar 2018 21:17:35 +0200 (CEST) (envelope-from nz@thiemo.net) X-Clacks-Overhead: GNU Terry Pratchett Received: from gearloose.srv.thiemo.net (styx.row.thiemo.net [217.7.216.36]) (authenticated bits=0) by styx.row.thiemo.net (8.14.5/8.14.5) with ESMTP id w2VJHJ4X036634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 31 Mar 2018 21:17:24 +0200 (CEST) Subject: Re: buildworld from 11.1-R-p8 to stable/11 fails in contrib/llvm To: Dimitry Andric Cc: freebsd-stable@FreeBSD.org References: <8C30CD25-46EA-4E26-8E27-F6FB063AE232@FreeBSD.org> From: Thiemo Nordenholz Message-ID: <94832547-99f2-13ce-c4ac-89f8dfd113db@thiemo.net> Date: Sat, 31 Mar 2018 21:17:22 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <8C30CD25-46EA-4E26-8E27-F6FB063AE232@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.6.2 (nox.thiemo.net [78.46.48.50]); Sat, 31 Mar 2018 21:17:35 +0200 (CEST) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (styx.row.thiemo.net [10.200.0.2]); Sat, 31 Mar 2018 21:17:24 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 31 Mar 2018 19:17:37 -0000 Thank you, Dimitry! On 03/31/18 18:56, Dimitry Andric wrote:> Can you check whether the following lines exist in your copy of lib/clang/include/lldb/Host/Config.h: > > #define HAVE_SYS_EVENT_H 1 > #define HAVE_PPOLL 1 Yes, they are there. I have also updated to r331838 and tried again, and it looks like the one in freebsd.org's web svn browser. > If not, it is best to delete your source tree and do a fresh checkout. Even though it looks okay, I am trying that now. >> Trying "env WITHOUT_CLANG=YES WITH_GCC=YES make buildworld" also fails, however in /usr/src/lib/libc/tests/ssp (as make says): [ ... ] > In this case, I think you would also need WITHOUT_CLANG_BOOTSTRAP. Or alternatively, build using WITHOUT_TESTS. I will try that next in case the currently svnup'ing 331844-from-scratch also fails. Best wishes, Thiemo -- Query a PGP key server for my public key 0x11E4B9A92AAE0A34. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml From owner-freebsd-stable@freebsd.org Sat Mar 31 21:33:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBEB7F5233C for ; Sat, 31 Mar 2018 21:33:13 +0000 (UTC) (envelope-from thiemo@styx.row.thiemo.net) Received: from nox.thiemo.net (nox.thiemo.net [IPv6:2a01:4f8:110:1345::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nox.thiemo.net", Issuer "thiemo.net CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6238276EC1; Sat, 31 Mar 2018 21:33:13 +0000 (UTC) (envelope-from thiemo@styx.row.thiemo.net) Received: from styx.row.thiemo.net (styx.row.thiemo.net [217.7.216.36]) by nox.thiemo.net (8.15.2/8.15.2) with ESMTPS id w2VLX105079035 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 31 Mar 2018 23:33:11 +0200 (CEST) (envelope-from thiemo@styx.row.thiemo.net) X-Clacks-Overhead: GNU Terry Pratchett Received: from mygiea.srv.thiemo.net (localhost [127.0.0.1]) by styx.row.thiemo.net (8.14.5/8.14.5) with ESMTP id w2VLWtEg039113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Mar 2018 23:33:00 +0200 (CEST) Received: (from thiemo@localhost) by mygiea.srv.thiemo.net (8.14.5/8.14.5/Submit) id w2VLWtDT039112; Sat, 31 Mar 2018 23:32:55 +0200 (CEST) Date: Sat, 31 Mar 2018 23:32:55 +0200 From: Thiemo Nordenholz To: Dimitry Andric Cc: freebsd-stable@FreeBSD.org Subject: Re: [solved] buildworld from 11.1-R-p8 to stable/11 fails in contrib/llvm Message-ID: <20180331213255.GA39103@mygiea.srv.thiemo.net> References: <8C30CD25-46EA-4E26-8E27-F6FB063AE232@FreeBSD.org> <94832547-99f2-13ce-c4ac-89f8dfd113db@thiemo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94832547-99f2-13ce-c4ac-89f8dfd113db@thiemo.net> User-Agent: Mutt/1.5.22 (2013-10-16) X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-4.6.2 (nox.thiemo.net [78.46.48.50]); Sat, 31 Mar 2018 23:33:11 +0200 (CEST) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (styx.row.thiemo.net [0.0.0.0]); Sat, 31 Mar 2018 23:33:00 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 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, 31 Mar 2018 21:33:14 -0000 Deleting /usr/src and svnup'ing it again did indeed solve the problem. > > If not, it is best to delete your source tree and do a fresh checkout. > Even though it looks okay, I am trying that now. Thanks again! Thiemo -- Query a PGP key server (e.g. http://www.pgp.net/) for my public key 2AAE0A34. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml