From owner-freebsd-current@freebsd.org Sun Mar 18 00:22:55 2018 Return-Path: Delivered-To: freebsd-current@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 8C2FEF51D78; Sun, 18 Mar 2018 00:22:55 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out1-8.antispamcloud.com (out1-8.antispamcloud.com [185.201.16.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1436D751CD; Sun, 18 Mar 2018 00:22:54 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx68.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1exL9m-0001hX-L6; Sun, 18 Mar 2018 00:22:35 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To: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=+H+zsfLrn6V8ZSfXNGgWDnp8U3aglkEras7fIFVJ2vU=; b=p4+t8GUjP6R22WXoE8M/GOrPtM qkmpKNncC486Apy88bmWpZ58m7hAsRmX41+Su8q/jQAYIZ+4x0jSMm9ZZNZ1RLFMFK6hliZlt4mcw hwW6cYy6c3YM7yffDTxubcVdgRZG0EPZhTDNd3rk/OvVv1jx8lZFKqErsSIHEI07ZMYWsOV1/y9vl dV5RmlIasXjmhMGMT6BU84ezI00iQX4Bk+G/vK3JF4vBM5SjuQnmPqy5MJ4BF3DOrUql90ctYKglC Q54M/54ZzEjxbDEsLujFpJYuY15CgXDnX0eTEB5Dttqu6xWMIrPI28fEkdbgEYnPn+ynZL63EceOo saogU+lg==; Received: from [114.125.71.99] (port=20499 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1exL90-000A3Z-Mx; Sun, 18 Mar 2018 06:21:48 +0700 Date: Sun, 18 Mar 2018 07:21:44 +0800 From: Erich Dollansky To: John Darrah Cc: "freebsd-advocacy@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: FreeBSD has a politics problem Message-ID: <20180318072144.086159f7.freebsd.ed.lists@sumeritec.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: unsure X-AntiSpamCloud-Outgoing-Evidence: Combined (0.19) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5r+NrL/6wJn8YZ0sdJOUVdJ602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO0/JJwM+iVZeflWpnUAuMMLFawUChm01d5Zi5ht0DRUtVpK+UKTeqxZu93ei7Y6eyjPh pwpWMvXiZeXQODcnrejS/HVROkBNqcvr/bciyBoPwiBKLDAfGz+10a+UbvXHL0hazMG2OHERT1yz aUX65+WT+qCz3rOuuBbhlgCCQrHU5EYKk9ePgXGbt5xuMhAKm1ZiUSAofzQZyw1No2+95uQ6gYbz xPOdHt4zTzsNacyUK5uN4Nhp7uOkWlmbQCkb22ZahCgUvTCueR5bi0bHK/w3ATosvvqzp8/PsONp VctjnX/YV1uhlLsE1ItIMqOyMsYOCF60QpvOtT4vxKgu+A0+zaac9FtcRdqoRoYWsjypxomYtyRb /Y0Qmcr3YH+dmOJfV7nG/M60EZk5Ho2E0olS9wT7oELqxavbwzdX3Qz/smYfpztwdkx9TF8kMvPG 0wdeM0Ie3DuEGYjrS15nAitkzc24eG3hqHeMqlV71Dl1jEnj+0/sukBX17j8hn6eiIca+nPOKTKf xsYujFD/DBF6EipRzMVZ5LqwTx7Vvn9SRzhgGf79uaniwv5Hh/GRz2pHRSCRJIpQrNpZSg1x5LbR iwUPKZlo6KckRIyRq/7l07FIUfTWCI262DbfSR+/XweYUOp7A73HI6oJg7w/VodinzK+aIr2uM5I 16ENOtmGAr2ix9Sq1CEJNVKbaltYgMqvrIlo2twg9ePmEITdKglRTjOpxMWUu9fSkZCWuoNZxo8z PwnTK8T72k1Yf3tGFHLYM3A6BXfvel8OEFDbU502QgPOmoupwzGrYADRwav3XS9dWjzMfcFbK8nX ELAYgY7MTnEIRSj09o40PG20cuoYl2KZhkai6KglYqQxpUcabCB/BBd46AYXoop3Vb1ozNbMOYhZ VhWQD3muHGZxwbWWy+otarr+opjdZJqHfSEAtUIdKz+aOJRGwNbXQ/h3fd5hso0p2qEK9vLLH6Iw Xw+egMwrtwdodggrHZMuX9HK X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 00:22:55 -0000 Hi, just one word. I am from Kissing. My neighbours are from Fucking. I bet, the 'CoC' people will discriminate me and my neighbours now. Erich From owner-freebsd-current@freebsd.org Sun Mar 18 04:42:11 2018 Return-Path: Delivered-To: freebsd-current@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 79827F5DD41; Sun, 18 Mar 2018 04:42:11 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out2-2.antispamcloud.com (out2-2.antispamcloud.com [185.201.17.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03D587E35A; Sun, 18 Mar 2018 04:42:10 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx65.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1exQ8u-0009fD-42; Sun, 18 Mar 2018 05:42:01 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To: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=GXvrxFinQ0kgXGMUdIMZYpILKCedOS1o9H1QkbmAQ98=; b=F8R0c/tNGo+tP5sP2SMSHMqFSg ixybsfctLVxDB+OJ/wxErtpqBDg1JgapwYwzf2mF3MyJ9n/SgE3uC6TXEULSJEYWSZnhqtKP4wFHO r0usVgos3YsQLt62I9/KjP3W+OIOIDWBkhgQIPRp+CMvhLa1tmA38WTh9HpuDkSew2cJOeHe9XIkY SVw3+Qb6UI5DncxaZiStyNL+b3+YftoCXOTME5PS4meJPC7h9eRns4PPAP3bVK7IIvbSXzDwuKlmD 0YgF9Uql+VSeRjV6wAbm7TVEQRAG4+G+qS5tU1ynQTJEIZpT/f5kob9RmygomYI7siRLNuHGuHPoC kCT0/Q7w==; Received: from [114.125.71.99] (port=62494 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1exQ85-00009b-7W; Sun, 18 Mar 2018 11:41:12 +0700 Date: Sun, 18 Mar 2018 12:40:56 +0800 From: Erich Dollansky To: Kate Dawson Cc: John Darrah , "freebsd-advocacy@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: FreeBSD has a politics problem Message-ID: <20180318124056.28721454.freebsd.ed.lists@sumeritec.com> In-Reply-To: <20180318010839.n2vk3eaibaslzxcj@apple.rat.burntout.org> References: <20180318072144.086159f7.freebsd.ed.lists@sumeritec.com> <20180318010839.n2vk3eaibaslzxcj@apple.rat.burntout.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: ham X-AntiSpamCloud-Outgoing-Evidence: Combined (0.03) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5jg7mHPEYYVr+F/CyE5W1x1602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO2rMUlCP2c+sCsbRaUMVm2NXqlC5tkllgtdNbZ8u9WhJH6LMPyuBVtD0Js2qY3ru190l iM7/stV+RIKHh1clMjWd8WYR0XMaFOqFRVnzou9yseOhP/a0E96hZ2ee1noFSoSEW5u6PjsRr51H jINLXVRAQnsLO8OlL77d3bdz3iqGy2SuIzSkh5fKCO8CIBOBXCP1HaH27Qjry/056DPMnxdyoy4G zhQePiGnhTgXiVSsWSlmRJUKMrJ+ahcq82ahPl2NJQvocU/eAGjxnyzURttrw8ufacz9YqLFdAzV jgI7YV71ph5khcG8tMyqX3Qp7jRUfqpvKqbGSF1ibAzX87g1XG8Ftr2UW8JU7GqLuGHZgMuLbVaO YX4NUbgN+pHwxUwzxPv6OleYcjgzAbIebFhuJILS8/mqhtUoeuCLaCLIhaC2TJpFrGrq1WX76kTm g5w7R2/M+XaT5BLifEp8KpVKwStkfxgYPbwqTBhR8Odxa+HDctSZyW8CR81P4pQCFNG5tr1naPLr D+uYvNqtQnWYBq6S+OMHcfXl6o0I271KKTjECb0PwpN4olPuA0AI9xjc7g2EoU4CV0Up8Y6HRn4b 35FIiW3pSd4uZTgW9iG3YA+vhAemeI7KkPbXCfTZi4YxVb/ScwloiM5nYXzLBSGyi84om/v/xrU2 a2FUwzCVGprWRAemCnhgmqCEduvRJZSf/Gik20TtVXisp3Olekx1y6fkYWuA6EUTF8j0R1ZDgCQE jZnRrAJbvIRIQl4nKgFgMmailPUx0SHEDrUVlSc8CVsONrMJuGzuoGnKTKcyQhVVEe2MyzpaLjDx Ql7u+SulS0jlT2mw+eaFQMrv5Dai5qsA/LTJoK7PkpCz4njHQA8PC5NBesxO/gc2I+P8qf27lItO pPwlvQ6ktwDuRituj6ZEfB9v4x8THVh0rVtlyOZYRaCjaXhrY3nerbmurOCmBvDHmXRE5wvZqiqE c9Nr9/Mn670rgEzRrsP4YRqd+4FHNKsiy9wMVtQ6ai8zTQ== X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 04:42:11 -0000 Hi, On Sun, 18 Mar 2018 01:08:41 +0000 Kate Dawson wrote: > Actually you sound like you come from under a bridge. You know... > "Trolling" it just shows your low education level. You could have checked maps.google.com. But you did not. Erich > > xxx > > On Sun, Mar 18, 2018 at 07:21:44AM +0800, Erich Dollansky wrote: > > Hi, > > > > just one word. I am from Kissing. My neighbours are from Fucking. I > > bet, the 'CoC' people will discriminate me and my neighbours now. > > > > Erich > > _______________________________________________ > > freebsd-advocacy@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-advocacy > > To unsubscribe, send any mail to > > "freebsd-advocacy-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Sun Mar 18 07:35:57 2018 Return-Path: Delivered-To: freebsd-current@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 8670CF63E33; Sun, 18 Mar 2018 07:35:57 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out1-5.antispamcloud.com (out1-5.antispamcloud.com [185.201.16.5]) (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 E58E883EFF; Sun, 18 Mar 2018 07:35:56 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx65.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1exSrB-0009E4-DA; Sun, 18 Mar 2018 08:35:54 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To: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=GhfskNXG/sHFZZd0Oy7HksW/Iqv67OtKsJp0kvbU6NE=; b=YeIkFobajQIcGbD4d4dETaFnd2 ZLOQg1P4XSn3pvQsh3e7snqausANwY+b69WH/KV71lmXXjhUtZqDC/YDZfEjeIigI9R2zUXdZuJQu PhRj6ZeMr7AHL18KpysALc1KQn1Jx54B7NsdW17igQ6aUen2AyAoq+HfyzxUdjj6cQE4IlQefIN/V ABiSko7DVDF78A4ToWab3wZ49WRM90vvv3yf8rm8zBZxAvcZSTp443QuN5fO+Fs+Gp+UF1WlqPGhM fqv0vkRjsmCqEU79W1/SMEacRTYWg8ItSpfd56fMcgdxlqP7uIRPrJzlVnjSLlR2OZHMjm9w/YnZ5 cD+YK4pg==; Received: from [114.125.71.99] (port=43181 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1exSr5-0007fX-7t; Sun, 18 Mar 2018 14:35:49 +0700 Date: Sun, 18 Mar 2018 15:35:44 +0800 From: Erich Dollansky To: "Meixner, Johannes" Cc: Kate Dawson , "freebsd-advocacy@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: FreeBSD has a politics problem Message-ID: <20180318153544.30513850.freebsd.ed.lists@sumeritec.com> In-Reply-To: References: <20180318072144.086159f7.freebsd.ed.lists@sumeritec.com> <20180318010839.n2vk3eaibaslzxcj@apple.rat.burntout.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: ham X-AntiSpamCloud-Outgoing-Evidence: Combined (0.07) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5qbiP8vw3D9xNBpWSQAY0Rt602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO6eF70B3Lj3rfqBpTFQb98RgXNaBeaVbnd8zddEF1C065imK6OSL0ipqjxPCGz3ycNdn MMdh3DCGKt9vuk81flZNToj9+8OqN0DtPyqVqzyRy3FqN+FgUWFsPAgep0EQCdwAsFLMoj0NEqWo IAqpAc78/5GXUowA27L/ZS2nAM68qJ2jUG6iVD0cGbSjkzfIDr9TmatVsoElQUin5D/I7csPOVnz PAFPgn1Tt0PKIc8ckVWClPVvbW5lVyQanRxw5nmS7Qi4DDvwnPe/m0ZwJgtxD1DiyUTmBzDSBY7R LYhBbVHuHhwyqjQEd+48pMRgSp1HitB6EIOmaecgMbUvQBES2fFERa4r4HcIzkK0VPtRbQ5Y/N7O 6FAYfqkcI796xfxr6l90dcauQFkSylif/DMiyHWENuDMAF9wxsndQKwaQy17Ychxni5a2VYVYiL6 p0zFIS4eFFedtqTPxkQeRTOMykK9C7GvVGVAhXhVjEzWWVd3bTro3dLvSMcacWlYMRgYrswXUAHW 7yTWdn+ESHMVibkyMxsuFG9+hHfpakcKEzeC1KhzCfYJEuCSXJfc1xqZR3KVQgqF/fPYYAfEfsit wvzcXRivHP13Wq/H8J6UvM7TbnYXLKODO/GpYzNQ6HpjjYM6OyCTvH9DGztRmt7YttXSvAKthFGk IMWfjXH9SNt+8Md3sxKdF1BL+K7+lF98BpoJuogPIYnHWgXfKKWxmx7wc9+AMT0yqgxR4cOX8JWF 19gzMLCoxSZaDKQwLEkMqw50QKDIGDcbRRw0v1PRZ4YizZEe9VMcrJA1Ttxdghx7VXz56ipAqVHd YT3ITcOpyKA69LF1Ge2GaGfxmfrChd8MEkzTofVEK6FHjWTh5Pmioa+M64E8jKRtHb3ypkWXJryJ 9+EiOvBe6vFbUGRrwytzyq4nhu0+m3/YUu4UI2GoiS4jWHSkvyyyS8KErSXsfQKqMtMBmJYQFNz7 u6HBEySMWQF2Dk2FUoK1HKpU9jihx+Za/cV70jOJzN2r4A== X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 07:35:57 -0000 Hi, On Sun, 18 Mar 2018 06:43:47 +0100 "Meixner, Johannes" wrote: > You must have never been to Southern Germany or Austria. and Alaska. Erich From owner-freebsd-current@freebsd.org Sun Mar 18 08:47:37 2018 Return-Path: Delivered-To: freebsd-current@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 431AAF66609 for ; Sun, 18 Mar 2018 08:47:37 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CA5B686347 for ; Sun, 18 Mar 2018 08:47:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8B309F66608; Sun, 18 Mar 2018 08:47:36 +0000 (UTC) Delivered-To: current@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 63F2CF66607 for ; Sun, 18 Mar 2018 08:47:36 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C22A086346 for ; Sun, 18 Mar 2018 08:47:35 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id d10so15594404wrf.3 for ; Sun, 18 Mar 2018 01:47:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:reply-to:mime-version :content-transfer-encoding; bh=K66jFDNhe/X5OFRnocPl6s/RqpWi1JwBSSMN1ywkOHY=; b=OHGgME9cFCJXPTxEoWjFxQsBRFHh9u5oNrFKTGF6U3vnZTNrfQoQmkHdZzJd3igW4y ZDzN5lVHz2gjdECY0KUS4D7NXwDYggr2dXau45MUw6IikukLd+FQH3Zb1I3qQ3tu7wuw fqj6SS0+UF4mnPuaXobADMa6b8g0LqVwiNXtxy3uw8G9VE3UUc3zMNyg9s3k8ngPAyh3 gjAG+rEcQJS3XlLBBzHouenJCtSF7ZY3Nx3VP2jOUHooPS6MVOst9andWTikeZws6nlm 0SgqCW8wi+ZtWb978X2TShccJL5sL6fwgdaaQVjMbdxqEHxv+Yqi09Fb7WpyU3kj4kgU 6PhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=K66jFDNhe/X5OFRnocPl6s/RqpWi1JwBSSMN1ywkOHY=; b=my6LJQeXhF8cCs/T21GIRD7IMOSuqezY8Xcez9VGhubQHEcz7g2Bm2XPQ8KG1hdlSg n5ZQd6sHl4dunOy/Z1OHgUpCpkVj75BYPNX5p+iwGr9u4mGMX8113odkBAjxs0BocDM5 OHVOL77oL0mIpX7QSMfraHGm8eqS3JotLHP2T2vJsLLYf6vGkXwOcgsl8LUjGdnFHxE6 vTOLIK9pguNQaFmuYlF+1n9B/03CAAXmuC9cu6eZHj4eJSk0mUKnm2MbElhJxZ/u4TeK NGST93kpheTs+LXQxXOV+qVXQV9zGprI34scvxXYvuotlFk/OWmUpT1L5ppNwpS8iZZr g9cA== X-Gm-Message-State: AElRT7FcyMK4+wLGqkGoEqDspD/A572nGKbcx7X+/8uc/QazD0HFozTt 9du+QdfkDHvZ1a2xtwwK9A64Iw== X-Google-Smtp-Source: AG47ELvXVbwA0htzzAXlT9z4M29BB5guz1gI9uvJMi0BDAZHG+IiGDKjkzG3RGH2gQ9ACWTwOyrbSQ== X-Received: by 10.223.200.2 with SMTP id d2mr5925829wrh.81.1521362853766; Sun, 18 Mar 2018 01:47:33 -0700 (PDT) Received: from ernst.home (p5B02330E.dip0.t-ipconnect.de. [91.2.51.14]) by smtp.gmail.com with ESMTPSA id d48sm4914026wrd.12.2018.03.18.01.47.32 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 18 Mar 2018 01:47:32 -0700 (PDT) Date: Sun, 18 Mar 2018 09:47:31 +0100 From: Gary Jennejohn To: current@freebsd.org Subject: network performance over 1GBps links degraded Message-ID: <20180318094731.52dba55b@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 08:47:37 -0000 I have two computers, both with 1Gbps interfaces plugged into a 1Gb switch. One computer is running FreeBSD HEAD and the other some version of Linux. Under FreeBSD I have re0 and under Linux I don't know what the hardware is. Both interfaces are using a MTU of 4088 because that's the maximum my re0 supports. I tend to copy files from one to the other using ftp fairly frequently. I noticed that the transfer speed has dropped to only about 12MBps. I'm used to seeing about 27MBps during the ftp transfers. I also observed the drop in transfer speed between FreeBSD and a Windows 10 computer. Formerly, I was seeing about 30MBps. Windows 10 also has MTU 4088 set. I tested with a FreeBSD kernel from March 7 and one from March 17, but both show the miserable performance. Unfortunately, I don't have any older kernels backed up. I can't say exactly when the performance degraded, but possibly there was some change to the kernel on or before March 7 which caused it. Has anyone else seen this? There were several changes to the networking stack lately. I wonder whether anyone has an idea what could be the cause of the performance degredation, and what sysctls I could set to get the old performance back. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Mar 18 10:55:20 2018 Return-Path: Delivered-To: freebsd-current@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 6BCC0F43D44 for ; Sun, 18 Mar 2018 10:55:20 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 02F0A6A61F for ; Sun, 18 Mar 2018 10:55:20 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B4AC2F43D43; Sun, 18 Mar 2018 10:55:19 +0000 (UTC) Delivered-To: current@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 A0B24F43D42 for ; Sun, 18 Mar 2018 10:55:19 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (lab.alexdupre.com [93.151.207.39]) (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 E9B7E6A61E for ; Sun, 18 Mar 2018 10:55:18 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: (qmail 36948 invoked from network); 18 Mar 2018 10:48:36 -0000 Received: from unknown (HELO ?192.168.178.163?) (sysadmin@alexdupre.com@192.168.178.163) by lab.alexdupre.com with ESMTPSA; 18 Mar 2018 10:48:36 -0000 Subject: Re: network performance over 1GBps links degraded To: gljennjohn@gmail.com, current@freebsd.org References: <20180318094731.52dba55b@ernst.home> From: Alex Dupre Message-ID: Date: Sun, 18 Mar 2018 11:48:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.2 MIME-Version: 1.0 In-Reply-To: <20180318094731.52dba55b@ernst.home> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 10:55:20 -0000 Gary Jennejohn wrote: > I have two computers, both with 1Gbps interfaces plugged into a > 1Gb switch. One computer is running FreeBSD HEAD and the other > some version of Linux. Under FreeBSD I have re0 and under Linux > I don't know what the hardware is. > > I noticed that the transfer speed has dropped to only about > 12MBps. I'm used to seeing about 27MBps during the ftp > transfers. Do you see "re0: watchdog timeout" errors? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 -- Alex Dupre From owner-freebsd-current@freebsd.org Sun Mar 18 11:21:59 2018 Return-Path: Delivered-To: freebsd-current@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 581AFF4A286 for ; Sun, 18 Mar 2018 11:21:59 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E49656B810 for ; Sun, 18 Mar 2018 11:21:58 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A62CEF4A284; Sun, 18 Mar 2018 11:21:58 +0000 (UTC) Delivered-To: current@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 842F7F4A283 for ; Sun, 18 Mar 2018 11:21:58 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3CF16B808; Sun, 18 Mar 2018 11:21:57 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id c24so3957958wrc.6; Sun, 18 Mar 2018 04:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=rMrny0zebLbS80vuoGnzL5wtayyfpA3fx8qDYffguSU=; b=Iz+N1zZn2/O0Cwy3zjjQrdnyAyPXD0OZaZDv+0DxcFiKzu808mpV2xpQvjcjnPeDMd JCgOtRfp5H1cv0vj1RzNHnkqnD4p2ifJN8YsHQjzmeabmjJxK3Ds9fGrxXYk7iYxjLZs Kvlg7X2/v0/X+uhM+GKmuMhwWKkRE9jF4Sp6VrkmjI5WG8e0fN4XeJhRUjVY+lgRRIvL j7YH0ypG+JPixKmI/3Qnk2V2DxHIVfWT0uvhx2LQMFn12ALW+O8HERVv3VtzdSIKQjT0 GsT1TY7itlSZWuBQGyCO/GU/ecr0ToIMFn0H7qI5OyLIMa/d55hpJm7hdu/o7azz9kY3 Yrww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=rMrny0zebLbS80vuoGnzL5wtayyfpA3fx8qDYffguSU=; b=s6EQCbb0MY+eGtjSx1wH7nkWJdUCX7S8Tr3QXa7Ap7y7PLRXURWLriqnX+uWxxRMVL AA931w+5qp4sC9g7FPFrQ29EC07XEfU4udAuR74Np7hq7dZu7my27gHs0Z6vmdSdlVE9 QxeRN+wm6SZR0R1wos5XVlpovpfJIMRKImtrD4voMzP/nwsM36FXuzdaNfQ9ueLm4MrY 8dLTXqLUZnlqrZnxuevhOW1J2R804xb/4ZitGUA7wy/0lpP076cJKnAfQXwRefj6enQi T9NaYceAx5oWEVCeAQ6geQP534HLpT4bNfR1Ej1S6vhZHNPbY+Dx2lvDXi76HnO9t/DA 764g== X-Gm-Message-State: AElRT7HBaUjZcjoMVZhFcrvnPp4BDF8uiaD73wQrG3iWNgeW+AJfP6Um C7I0VdfnKuzhoCrh0lhDU+0UPg== X-Google-Smtp-Source: AG47ELvYePD6o7nOkFce6MdRRnreauFjZXlDYC/oX5byFTRAD4TuRrSY8i/KdUes1pQRTJguHzYU/A== X-Received: by 10.223.134.213 with SMTP id 21mr6103614wry.221.1521372116737; Sun, 18 Mar 2018 04:21:56 -0700 (PDT) Received: from ernst.home (p5B02330E.dip0.t-ipconnect.de. [91.2.51.14]) by smtp.gmail.com with ESMTPSA id u62sm12576373wma.15.2018.03.18.04.21.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 18 Mar 2018 04:21:55 -0700 (PDT) Date: Sun, 18 Mar 2018 12:21:54 +0100 From: Gary Jennejohn To: Alex Dupre Cc: current@freebsd.org Subject: Re: network performance over 1GBps links degraded Message-ID: <20180318122154.2b70661f@ernst.home> In-Reply-To: References: <20180318094731.52dba55b@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 11:21:59 -0000 On Sun, 18 Mar 2018 11:48:32 +0100 Alex Dupre wrote: > Gary Jennejohn wrote: > > I have two computers, both with 1Gbps interfaces plugged into a > > 1Gb switch. One computer is running FreeBSD HEAD and the other > > some version of Linux. Under FreeBSD I have re0 and under Linux > > I don't know what the hardware is. > > > > I noticed that the transfer speed has dropped to only about > > 12MBps. I'm used to seeing about 27MBps during the ftp > > transfers. > > Do you see "re0: watchdog timeout" errors? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 > Thanks, but I just copied some 30GB between the FreeBSD and Windows 10 computer and didn't see a single error message. I tried r330300, but the behavior didn't change. Maybe I should go even further back in time. One possibilty is the new BIOS I installed on my Ryzen (FreeBSD) box. I checked that the settings are all optimized, but who knows what Asus changed? -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Mar 18 15:12:21 2018 Return-Path: Delivered-To: freebsd-current@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 BE197F5B6F2 for ; Sun, 18 Mar 2018 15:12:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A27375C0A for ; Sun, 18 Mar 2018 15:12:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8D39019497 for ; Sun, 18 Mar 2018 15:12:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IFCKal075916 for ; Sun, 18 Mar 2018 15:12:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IFCKKE075906 for freebsd-current@FreeBSD.org; Sun, 18 Mar 2018 15:12:20 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-current@FreeBSD.org Subject: [Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT Date: Sun, 18 Mar 2018 15:12:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ml+freebsd@vishwin.info X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mandree@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 18 Mar 2018 15:39:34 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 15:12:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226700 Charlie Li changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-current@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sun Mar 18 16:13:50 2018 Return-Path: Delivered-To: freebsd-current@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 E3F5EF5FC8C for ; Sun, 18 Mar 2018 16:13:49 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6560078EBD for ; Sun, 18 Mar 2018 16:13:49 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 24C8DF5FC8A; Sun, 18 Mar 2018 16:13:49 +0000 (UTC) Delivered-To: current@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 02DF3F5FC89 for ; Sun, 18 Mar 2018 16:13:49 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EBF478EB3; Sun, 18 Mar 2018 16:13:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id f125so2817639wme.4; Sun, 18 Mar 2018 09:13:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=qMM2GpY9KPz0Xt1c0ELsxSN22mWugr5Iz0K60cn41Mc=; b=BAl3FgN7lsLAbNZyLxpLX1jOmx/wRbzgssnIKpT8DTMJQfS3FoHUXTUm+dIgmB2skM I+FiXFNTC2MZDWVnMEDIWwkQctZboQrE5NujH+O3XHGZiiXc7nhlfR0Gbbwfzx+3frCo y5V6rf6sh9fCYHF5OM2dET9RKCkjvhLTWFCFXJvKmzxmxR6HLkR029pIWvkM43UQrMp8 2jzfAVfpWvGey6Txui6FlbKcvlRrM+3eBE60dWk7dh1rqXnTit78XYNKMnncZO0O02WY Ddm/K90/v3KqFg4rtrerhbDXvdMUP1RZy8P95Y61bzLaj+Kh9QYTOFs6zsNi469aALTT GnRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=qMM2GpY9KPz0Xt1c0ELsxSN22mWugr5Iz0K60cn41Mc=; b=BATHRFgxb/JnyslIor7eNMAB2uM/usppnP42pSatBTWxpP1jd+LGi0MQPQv66k5zoe +488wfYk7hE37gcw4rPnaPRMV+BGXhOSa1DV8WlI7z8ZtflQskPKpnPYfd+l+3oONDGr 5haWHu3v+dx+uJOS71bniZWLKWSl2KxoumDtNPKASl6uF48IUCyv5kxuTsZHdOp0tqRe zIwAHyINvn6iWNeU2B8Nrh1AgsGlxT8Fd77EDD7/yMIADozbnUv+7IOMHhSRnFMkmhgU HqpY6k7OAWCW+gXhdUaXHnoKlQllm0+o4BXq4aHGmq003Caj7xGDv+npBKJmY7+dEAeH SjSA== X-Gm-Message-State: AElRT7EEZbEQApy1FftCuai5zZHhvYMEg/Vyn2SdrqnT+q+bPYZ5v4SW hoUOYIRMAR/ecsNSXXzGMhEbAw== X-Google-Smtp-Source: AG47ELutl1SG57EIeb9FGD9FiL0ELeZoU94+KAwmVfjeAxnldwDBX2LfIzMJvgNghsg0EhYc6jmoXQ== X-Received: by 10.28.165.12 with SMTP id o12mr6249778wme.120.1521389627045; Sun, 18 Mar 2018 09:13:47 -0700 (PDT) Received: from ernst.home (p5B02330E.dip0.t-ipconnect.de. [91.2.51.14]) by smtp.gmail.com with ESMTPSA id j21sm18774247wrb.49.2018.03.18.09.13.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 18 Mar 2018 09:13:45 -0700 (PDT) Date: Sun, 18 Mar 2018 17:13:45 +0100 From: Gary Jennejohn To: Alex Dupre Cc: gljennjohn@gmail.com, current@freebsd.org Subject: Re: network performance over 1GBps links degraded Message-ID: <20180318171345.125186a4@ernst.home> In-Reply-To: <20180318122154.2b70661f@ernst.home> References: <20180318094731.52dba55b@ernst.home> <20180318122154.2b70661f@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 16:13:50 -0000 On Sun, 18 Mar 2018 12:21:54 +0100 Gary Jennejohn wrote: > On Sun, 18 Mar 2018 11:48:32 +0100 > Alex Dupre wrote: > > > Gary Jennejohn wrote: > > > I have two computers, both with 1Gbps interfaces plugged into a > > > 1Gb switch. One computer is running FreeBSD HEAD and the other > > > some version of Linux. Under FreeBSD I have re0 and under Linux > > > I don't know what the hardware is. > > > > > > I noticed that the transfer speed has dropped to only about > > > 12MBps. I'm used to seeing about 27MBps during the ftp > > > transfers. > > > > Do you see "re0: watchdog timeout" errors? > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 > > > > Thanks, but I just copied some 30GB between the FreeBSD and Windows > 10 computer and didn't see a single error message. > > I tried r330300, but the behavior didn't change. Maybe I should go even > further back in time. > > One possibilty is the new BIOS I installed on my Ryzen (FreeBSD) box. > I checked that the settings are all optimized, but who knows what Asus > changed? > So, Stefan Esser (se@) hit me with a clue bat and asked what ifconfig shows for the speed. Well, it's 100baseTX. Not too surprising that it maxes out at 12MBps. Up until recently the speed was always automatically set to 1000baseTX. AFAIK nothing has changed in regards to the hardware (contollers, switches, etc.). Anyway, I'll try setting mediaopts in rc.conf and see what happens. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Mar 18 17:19:16 2018 Return-Path: Delivered-To: freebsd-current@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 82090F64AB4 for ; Sun, 18 Mar 2018 17:19:16 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [104.225.8.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd-11-64", Issuer "freebsd-11-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 357E77C45B for ; Sun, 18 Mar 2018 17:19:15 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [104.225.8.138]) by mail.neu.net (8.15.2/8.15.2) with ESMTPS id w2IHJ84k033538 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 18 Mar 2018 13:19:09 -0400 (EDT) (envelope-from andy@neu.net) Date: Sun, 18 Mar 2018 13:19:08 -0400 (EDT) From: AN To: freebsd-current@freebsd.org Subject: /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main Message-ID: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.neu.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:19:16 -0000 Fyi, I started seeing this error today during buildworld compile. FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #15 r331021: Thu Mar 15 16:30:40 EDT 2018 root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1200060 # svnlite info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 331135 Node Kind: directory Schedule: normal Last Changed Author: markj Last Changed Rev: 331135 Last Changed Date: 2018-03-18 13:03:26 -0400 (Sun, 18 Mar 2018) ------------------------------------------------------------------------------------- --- all_subdir_lib/libcasper --- --- all_subdir_lib/libcasper/services/cap_sysctl --- /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main >>> referenced by crt1.c:74 (/usr/src/lib/csu/amd64/crt1.c:74) >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_start) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_create >>> referenced by cap_sysctl.c:64 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:64) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_string >>> referenced by cap_sysctl.c:65 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:65) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_string >>> referenced by cap_sysctl.c:66 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:66) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_number >>> referenced by cap_sysctl.c:67 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:67) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_null >>> referenced by cap_sysctl.c:69 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:69) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_number >>> referenced by cap_sysctl.c:71 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:71) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_add_binary >>> referenced by cap_sysctl.c:73 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:73) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: cap_xfer_nvlist >>> referenced by cap_sysctl.c:74 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:74) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_get_number >>> referenced by cap_sysctl.c:77 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:77) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_get_number >>> referenced by cap_sysctl.c:78 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:78) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_destroy >>> referenced by cap_sysctl.c:79 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:79) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_get_number >>> referenced by cap_sysctl.c:84 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:84) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_get_binary >>> referenced by cap_sysctl.c:86 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:86) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_destroy >>> referenced by cap_sysctl.c:91 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:91) >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: service_register >>> referenced by cap_sysctl.c:295 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:295) >>> /tmp/cap_sysctl-cfa2f8.o:(init_casper_service) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_next >>> referenced by cap_sysctl.c:209 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_get_number >>> referenced by cap_sysctl.c:212 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:212) >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_next >>> referenced by cap_sysctl.c:209 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: nvlist_error >>> referenced by cap_sysctl.c:110 (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:110) >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_command) /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors) --- all_subdir_lib/libpam --- --- pam_setcred.3.gz --- gzip -cn /usr/src/contrib/openpam/doc/man/pam_setcred.3 > pam_setcred.3.gz --- all_subdir_lib/ncurses --- --- all_subdir_lib/ncurses/form --- --- fld_dup.po --- cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -pg -O2 -pipe -I. -I/usr/obj/usr/src/amd64.amd64/lib/ncurses/ncurses -I/usr/src/lib/ncurses/ncurses -I/usr/src/lib/ncurses/ncurses -I/usr/src/contrib/ncurses/include -I/usr/src/contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -I/usr/src/contrib/ncurses/form -I/usr/src/contrib/ncurses/menu -g -MD -MF.depend.fld_dup.po -MTfld_dup.po -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -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 -Qunused-arguments -c /usr/src/contrib/ncurses/form/fld_dup.c -o fld_dup.po --- all_subdir_lib/libpam --- --- pam_setenv.3.gz --- --- all_subdir_lib/libcasper --- cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [cap_sysctl] Error code 1 make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl 1 error make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl *** [all_subdir_lib/libcasper/services/cap_sysctl] Error code 2 make[5]: stopped in /usr/src/lib/libcasper/services 1 error make[5]: stopped in /usr/src/lib/libcasper/services --- all_subdir_lib/libpam --- gzip -cn /usr/src/contrib/openpam/doc/man/pam_setenv.3 > pam_setenv.3.gz --- all_subdir_lib/libcasper --- *** [all_subdir_lib/libcasper/services] Error code 2 make[4]: stopped in /usr/src/lib/libcasper 1 error make[4]: stopped in /usr/src/lib/libcasper --- all_subdir_lib/libpam --- A failure has been detected in another branch of the parallel make --- all_subdir_lib/libcasper --- *** [all_subdir_lib/libcasper] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/libpam --- make[5]: stopped in /usr/src/lib/libpam/libpam *** [all_subdir_lib/libpam/libpam] Error code 2 make[4]: stopped in /usr/src/lib/libpam 1 error make[4]: stopped in /usr/src/lib/libpam *** [all_subdir_lib/libpam] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/ncurses --- A failure has been detected in another branch of the parallel make make[5]: stopped in /usr/src/lib/ncurses/form *** [all_subdir_lib/ncurses/form] Error code 2 make[4]: stopped in /usr/src/lib/ncurses --- all_subdir_lib/libarchive --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/lib/libarchive *** [all_subdir_lib/libarchive] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/ncurses --- --- all_subdir_lib/ncurses/menu --- A failure has been detected in another branch of the parallel make make[5]: stopped in /usr/src/lib/ncurses/menu *** [all_subdir_lib/ncurses/menu] Error code 2 make[4]: stopped in /usr/src/lib/ncurses --- all_subdir_lib/ncurses/ncursesw --- A failure has been detected in another branch of the parallel make make[5]: stopped in /usr/src/lib/ncurses/ncursesw *** [all_subdir_lib/ncurses/ncursesw] Error code 2 make[4]: stopped in /usr/src/lib/ncurses 3 errors make[4]: stopped in /usr/src/lib/ncurses *** [all_subdir_lib/ncurses] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/libprocstat --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/lib/libprocstat *** [all_subdir_lib/libprocstat] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/libunbound --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/lib/libunbound *** [all_subdir_lib/libunbound] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/atf --- A failure has been detected in another branch of the parallel make make[5]: stopped in /usr/src/lib/atf/libatf-c++ *** [all_subdir_lib/atf/libatf-c++] Error code 2 make[4]: stopped in /usr/src/lib/atf 1 error make[4]: stopped in /usr/src/lib/atf *** [all_subdir_lib/atf] Error code 2 make[3]: stopped in /usr/src/lib --- all_subdir_lib/libsqlite3 --- A failure has been detected in another branch of the parallel make make[4]: stopped in /usr/src/lib/libsqlite3 *** [all_subdir_lib/libsqlite3] Error code 2 make[3]: stopped in /usr/src/lib 8 errors make[3]: stopped in /usr/src/lib *** [all_subdir_lib] Error code 2 make[2]: stopped in /usr/src 1 error make[2]: stopped in /usr/src *** [everything] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src From owner-freebsd-current@freebsd.org Sun Mar 18 17:30:25 2018 Return-Path: Delivered-To: freebsd-current@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 41746F6591F for ; Sun, 18 Mar 2018 17:30:25 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (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 BCE337CEE8 for ; Sun, 18 Mar 2018 17:30:24 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Received: by mail-pl0-x230.google.com with SMTP id f5-v6so8821655plj.13 for ; Sun, 18 Mar 2018 10:30:24 -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=0HeJzpraTDxPe9CqPFJa2bKVJRp/OkH3y0HF9TIsLv4=; b=cb7j5KhW9NXgf4WFPgGfilmzxr6++AYRCw0749Vmn81BSj3c1tHvAAkhvCj5FlZzJJ qsxKsxi/Id8jEOb2/eqsDSPw9JtGE6TPd3LxcvgY9NOppzTskW3CbeMZUy16wPlO+Vd7 K+CFnypVZ6Y29Gf4yRKaRP5a+Yj8ldcIyq4sEc3mnJOGIE9ue339uBsEV9kyfXYtvS91 5bU0neMdzVdbs1jsYkElxz+pQSlgl0Tctm9E+JW4JXUZGZE13tJ/uztiY+EiIkGONtN+ lft9FQVutXf4Vr9TrGQF77Scc3jZ2K+dT+rLfZS7QKtNoPWZgK5Q+t1b7nEWCXc3+rtQ 4nDQ== 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=0HeJzpraTDxPe9CqPFJa2bKVJRp/OkH3y0HF9TIsLv4=; b=huUXQYPG+sV8P9QYCjlyx3ngNnA6bb5F94qIL4u33EwCjIfG6h6cZeqqBPgIiNi8qb 1qK7qG8utYsKs3XUotZXn7qGrZ8+2J0D8nOfebDgqjVcREdqQ05hfrhsCAhYH65GaflW /iM7dx5I8b9x3WQPDk7MaHXkw8gtJiPbR3bZd1p2ulazeidV6Qa6A2/97Ljf0Gd+fPHR 2tGE5Nkx9KnZKHcJJalREQ7rfEedZra4QnHTaLCSJp7bTQptlPyil8CqZGPQE/SYJz+O 5JyH6t9DlTbBxYkJftnkV5evHxCpAlshyNMN6pGeQXY8Cx/VzNznaxPqKx2NPAI3ZA3p 2hsA== X-Gm-Message-State: AElRT7Fm242XNaYygacDNZ3Voz5Nrxyc3NC+udrbGtJ/xUIM/oAFhCnf E++OQga4gxnEWB/OpRqB6Xz0K7ofbF5YJVYqKyA= X-Google-Smtp-Source: AG47ELuKa74eq8xLXDmmdNSdVzAGG6qZQEDjiEPgt0gD7l8wKF/vKKSPAQ4Ncb3rJjnwhzPWVyUJvcmwkpHDyBxCbk4= X-Received: by 2002:a17:902:7c18:: with SMTP id x24-v6mr3714068pll.112.1521394223618; Sun, 18 Mar 2018 10:30:23 -0700 (PDT) MIME-Version: 1.0 Sender: oshogbo.vx@gmail.com Received: by 10.100.185.4 with HTTP; Sun, 18 Mar 2018 10:30:23 -0700 (PDT) In-Reply-To: References: From: Mariusz Zaborski Date: Sun, 18 Mar 2018 18:30:23 +0100 X-Google-Sender-Auth: DOE1fw7tbmfWFMgd7yuF80c-lqY Message-ID: Subject: Re: /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main To: AN Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:30:25 -0000 Thank you for reporting - I'm checking it. Do you use option MK_CASPER=no ? On 18 March 2018 at 18:19, AN wrote: > Fyi, I started seeing this error today during buildworld compile. > > FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #15 r331021: Thu Mar 15 > 16:30:40 EDT 2018 root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL > amd64 1200060 > > # svnlite info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 331135 > Node Kind: directory > Schedule: normal > Last Changed Author: markj > Last Changed Rev: 331135 > Last Changed Date: 2018-03-18 13:03:26 -0400 (Sun, 18 Mar 2018) > ------------------------------------------------------------------------------------- > > --- all_subdir_lib/libcasper --- > --- all_subdir_lib/libcasper/services/cap_sysctl --- > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main >>>> >>>> referenced by crt1.c:74 (/usr/src/lib/csu/amd64/crt1.c:74) >>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_start) > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_create >>>> >>>> referenced by cap_sysctl.c:64 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:64) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_string >>>> >>>> referenced by cap_sysctl.c:65 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:65) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_string >>>> >>>> referenced by cap_sysctl.c:66 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:66) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_number >>>> >>>> referenced by cap_sysctl.c:67 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:67) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_null >>>> >>>> referenced by cap_sysctl.c:69 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:69) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_number >>>> >>>> referenced by cap_sysctl.c:71 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:71) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_add_binary >>>> >>>> referenced by cap_sysctl.c:73 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:73) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > cap_xfer_nvlist >>>> >>>> referenced by cap_sysctl.c:74 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:74) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_get_number >>>> >>>> referenced by cap_sysctl.c:77 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:77) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_get_number >>>> >>>> referenced by cap_sysctl.c:78 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:78) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_destroy >>>> >>>> referenced by cap_sysctl.c:79 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:79) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_get_number >>>> >>>> referenced by cap_sysctl.c:84 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:84) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_get_binary >>>> >>>> referenced by cap_sysctl.c:86 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:86) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_destroy >>>> >>>> referenced by cap_sysctl.c:91 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:91) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > service_register >>>> >>>> referenced by cap_sysctl.c:295 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:295) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(init_casper_service) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_next >>>> >>>> referenced by cap_sysctl.c:209 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_get_number >>>> >>>> referenced by cap_sysctl.c:212 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:212) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_next >>>> >>>> referenced by cap_sysctl.c:209 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: > nvlist_error >>>> >>>> referenced by cap_sysctl.c:110 > > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:110) >>>> >>>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_command) > > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: too many errors emitted, > stopping now (use -error-limit=0 to see all errors) > --- all_subdir_lib/libpam --- > --- pam_setcred.3.gz --- > gzip -cn /usr/src/contrib/openpam/doc/man/pam_setcred.3 > pam_setcred.3.gz > --- all_subdir_lib/ncurses --- > --- all_subdir_lib/ncurses/form --- > --- fld_dup.po --- > cc -target x86_64-unknown-freebsd12.0 > --sysroot=/usr/obj/usr/src/amd64.amd64/tmp > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -pg -O2 -pipe -I. > -I/usr/obj/usr/src/amd64.amd64/lib/ncurses/ncurses > -I/usr/src/lib/ncurses/ncurses -I/usr/src/lib/ncurses/ncurses > -I/usr/src/contrib/ncurses/include -I/usr/src/contrib/ncurses/ncurses -Wall > -DNDEBUG -DHAVE_CONFIG_H -I/usr/src/contrib/ncurses/form > -I/usr/src/contrib/ncurses/menu -g -MD -MF.depend.fld_dup.po > -MTfld_dup.po -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror > -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -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 -Qunused-arguments -c > /usr/src/contrib/ncurses/form/fld_dup.c -o fld_dup.po > --- all_subdir_lib/libpam --- > --- pam_setenv.3.gz --- > --- all_subdir_lib/libcasper --- > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** [cap_sysctl] Error code 1 > > make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl > 1 error > > make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl > *** [all_subdir_lib/libcasper/services/cap_sysctl] Error code 2 > > make[5]: stopped in /usr/src/lib/libcasper/services > 1 error > > make[5]: stopped in /usr/src/lib/libcasper/services > --- all_subdir_lib/libpam --- > gzip -cn /usr/src/contrib/openpam/doc/man/pam_setenv.3 > pam_setenv.3.gz > --- all_subdir_lib/libcasper --- > *** [all_subdir_lib/libcasper/services] Error code 2 > > make[4]: stopped in /usr/src/lib/libcasper > 1 error > > make[4]: stopped in /usr/src/lib/libcasper > --- all_subdir_lib/libpam --- > A failure has been detected in another branch of the parallel make > --- all_subdir_lib/libcasper --- > *** [all_subdir_lib/libcasper] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libpam --- > > make[5]: stopped in /usr/src/lib/libpam/libpam > *** [all_subdir_lib/libpam/libpam] Error code 2 > > make[4]: stopped in /usr/src/lib/libpam > 1 error > > make[4]: stopped in /usr/src/lib/libpam > *** [all_subdir_lib/libpam] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/ncurses --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in /usr/src/lib/ncurses/form > *** [all_subdir_lib/ncurses/form] Error code 2 > > make[4]: stopped in /usr/src/lib/ncurses > --- all_subdir_lib/libarchive --- > A failure has been detected in another branch of the parallel make > > make[4]: stopped in /usr/src/lib/libarchive > *** [all_subdir_lib/libarchive] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/ncurses --- > --- all_subdir_lib/ncurses/menu --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in /usr/src/lib/ncurses/menu > *** [all_subdir_lib/ncurses/menu] Error code 2 > > make[4]: stopped in /usr/src/lib/ncurses > --- all_subdir_lib/ncurses/ncursesw --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in /usr/src/lib/ncurses/ncursesw > *** [all_subdir_lib/ncurses/ncursesw] Error code 2 > > make[4]: stopped in /usr/src/lib/ncurses > 3 errors > > make[4]: stopped in /usr/src/lib/ncurses > *** [all_subdir_lib/ncurses] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libprocstat --- > A failure has been detected in another branch of the parallel make > > make[4]: stopped in /usr/src/lib/libprocstat > *** [all_subdir_lib/libprocstat] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libunbound --- > A failure has been detected in another branch of the parallel make > > make[4]: stopped in /usr/src/lib/libunbound > *** [all_subdir_lib/libunbound] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/atf --- > A failure has been detected in another branch of the parallel make > > make[5]: stopped in /usr/src/lib/atf/libatf-c++ > *** [all_subdir_lib/atf/libatf-c++] Error code 2 > > make[4]: stopped in /usr/src/lib/atf > 1 error > > make[4]: stopped in /usr/src/lib/atf > *** [all_subdir_lib/atf] Error code 2 > > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libsqlite3 --- > A failure has been detected in another branch of the parallel make > > make[4]: stopped in /usr/src/lib/libsqlite3 > *** [all_subdir_lib/libsqlite3] Error code 2 > > make[3]: stopped in /usr/src/lib > 8 errors > > make[3]: stopped in /usr/src/lib > *** [all_subdir_lib] Error code 2 > > make[2]: stopped in /usr/src > 1 error > > make[2]: stopped in /usr/src > *** [everything] Error code 2 > > make[1]: stopped in /usr/src > 1 error > > make[1]: stopped in /usr/src > *** [buildworld] Error code 2 > > make: stopped in /usr/src > 1 error > > make: stopped in /usr/src > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sun Mar 18 17:30:36 2018 Return-Path: Delivered-To: freebsd-current@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 AA06AF65977 for ; Sun, 18 Mar 2018 17:30:35 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13BFE7CF00; Sun, 18 Mar 2018 17:30:34 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.74.225]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MCwbX-1eoVJR0Bb1-009gL1; Sun, 18 Mar 2018 18:30:10 +0100 Date: Sun, 18 Mar 2018 18:29:33 +0100 From: "O. Hartmann" Cc: AN , freebsd-current@freebsd.org, Mark Johnston , Mariusz Zaborski Subject: Re: /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main Message-ID: <20180318183000.2c6fc352@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/3FMC7ruO+2Y_M86+=ngfJ5B"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:bevXJadPMfVYTt6J7miQ4SH4VJK41ujpbHNYKcrAH79RUD9/0hD xq0Z2oauLDf2+3Ui/gTbT6/bTdBWtv+dpNr/wj2FAO7oYAvdxyzFjRusu9Hapbn3cvgUdpv Dw8RVy7iCqIaCNaaDwToLiRnu3ZBu5jE1hU/QQ8dEiPa7/liM9BvnXbmfu4lC9cqfD3NrSQ pkAq2JtHGisiwqCUdYRqQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:oCui6bJUJUI=:7sO7GGNRiJnLCUYqIDxBUo IuZdgtNI3mNaFKnwQPSIQoqB74dUOtzUW99Z1qyx9LkhhiHS+DLOtyCs7HlxczXXA5HGWVqm6 0ZdcoL0+foWSTNSGXY4X5XFjEI3lEw71gkV+umaKL50WIqSNbOksc5q58Gjc0pkql0q71308/ cA9eMDn6BzqopNfQ10nQVRsNbDH7MNOxbA231b3A1/ky5uVZwvI3V7NpCkpHRO5KJ/Y+SZ+gR +kexAoh22JyPeF0z8pFRf78C89NspTIowfS24OCSonfLlBC5H/cWmt6ST5lWYUY1l1MIY2UQG 1KkWLBRYxrWaFglPLGdwuQZLheNEpefgLvEGRMHxGHKDmGrblhPTxefJdWyZTg4Br4V3lUfhr cLLkLOdiAQJLxtdEeme8ewMR/LI5/vV7SvneIZfakMGkdeP4E8qqw7LuojcTQwAkKlsbzyrWX ASZTuQAZIdBtIyBt0eOzEOKtabHFul4d4Gl7j70Y7XHDQfsfczXDKwKV7MIBsBdEotayhTmRW 8aiXZDeilq4pqT+hJFhRinzwBaoi8TDMQ4yEm5eOYq6vx4T/MJOaxgVjHpiJG15ubQqx1QoGa kfL2kIb2/Lzo1kT2H0E/EGvV7iNqxNUQ/fL69zGP5lqVR9RnyS2a0wo6QGrtDFYmgeuZLBEJt kHKYTNWx7cSt21CH6+yiL6CVqI2WSqLHI4F6N9Chhdl/Glcc3J/0bslmPdJ7yEmHmDz/YZzWU V0Ky01j15PqTkSf7L3IkA+0KK1nbXBFzSwXuauOkBsVr/JDAJqn0Gf2hhuIh1cmC5CgXFf8qW w4v1JaIWllRTY4w1tZ0ghdT26q//Q== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:30:36 -0000 --Sig_/3FMC7ruO+2Y_M86+=ngfJ5B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 18 Mar 2018 13:19:08 -0400 (EDT) AN schrieb: > Fyi, I started seeing this error today during buildworld compile. >=20 > FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #15 r331021: Thu Mar 15= =20 > 16:30:40 EDT 2018=20 > root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1200060 >=20 > # svnlite info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 331135 > Node Kind: directory > Schedule: normal > Last Changed Author: markj > Last Changed Rev: 331135 > Last Changed Date: 2018-03-18 13:03:26 -0400 (Sun, 18 Mar 2018) > -------------------------------------------------------------------------= ------------ >=20 > --- all_subdir_lib/libcasper --- > --- all_subdir_lib/libcasper/services/cap_sysctl --- > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main > >>> referenced by crt1.c:74 (/usr/src/lib/csu/amd64/crt1.c:74) > >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_start= ) =20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_create > >>> referenced by cap_sysctl.c:64 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:64) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_string > >>> referenced by cap_sysctl.c:65 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:65) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_string > >>> referenced by cap_sysctl.c:66 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:66) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_number > >>> referenced by cap_sysctl.c:67 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:67) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_null > >>> referenced by cap_sysctl.c:69 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:69) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_number > >>> referenced by cap_sysctl.c:71 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:71) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_add_binary > >>> referenced by cap_sysctl.c:73 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:73) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > cap_xfer_nvlist > >>> referenced by cap_sysctl.c:74 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:74) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_get_number > >>> referenced by cap_sysctl.c:77 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:77) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_get_number > >>> referenced by cap_sysctl.c:78 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:78) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_destroy > >>> referenced by cap_sysctl.c:79 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:79) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_get_number > >>> referenced by cap_sysctl.c:84 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:84) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_get_binary > >>> referenced by cap_sysctl.c:86 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:86) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_destroy > >>> referenced by cap_sysctl.c:91 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:91) > >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > service_register > >>> referenced by cap_sysctl.c:295 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:295) > >>> /tmp/cap_sysctl-cfa2f8.o:(init_casper_service) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_next > >>> referenced by cap_sysctl.c:209 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) > >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_get_number > >>> referenced by cap_sysctl.c:212 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:212) > >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_next > >>> referenced by cap_sysctl.c:209 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) > >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol:=20 > nvlist_error > >>> referenced by cap_sysctl.c:110 =20 > (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:110) > >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_command) =20 >=20 > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: too many errors=20 > emitted, stopping now (use -error-limit=3D0 to see all errors) > --- all_subdir_lib/libpam --- > --- pam_setcred.3.gz --- > gzip -cn /usr/src/contrib/openpam/doc/man/pam_setcred.3 > pam_setcred.3.gz > --- all_subdir_lib/ncurses --- > --- all_subdir_lib/ncurses/form --- > --- fld_dup.po --- > cc -target x86_64-unknown-freebsd12.0=20 > --sysroot=3D/usr/obj/usr/src/amd64.amd64/tmp=20 > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -pg -O2 -pipe -I.=20 > -I/usr/obj/usr/src/amd64.amd64/lib/ncurses/ncurses=20 > -I/usr/src/lib/ncurses/ncurses -I/usr/src/lib/ncurses/ncurses=20 > -I/usr/src/contrib/ncurses/include -I/usr/src/contrib/ncurses/ncurses=20 > -Wall -DNDEBUG -DHAVE_CONFIG_H -I/usr/src/contrib/ncurses/form=20 > -I/usr/src/contrib/ncurses/menu -g -MD -MF.depend.fld_dup.po=20 > -MTfld_dup.po -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wer= ror=20 > -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes=20 > -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign= =20 > -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable=20 > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality=20 > -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef=20 > -Wno-address-of-packed-member -Qunused-arguments -c=20 > /usr/src/contrib/ncurses/form/fld_dup.c -o fld_dup.po > --- all_subdir_lib/libpam --- > --- pam_setenv.3.gz --- > --- all_subdir_lib/libcasper --- > cc: error: linker command failed with exit code 1 (use -v to see=20 > invocation) > *** [cap_sysctl] Error code 1 >=20 > make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl > 1 error >=20 > make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl > *** [all_subdir_lib/libcasper/services/cap_sysctl] Error code 2 >=20 > make[5]: stopped in /usr/src/lib/libcasper/services > 1 error >=20 > make[5]: stopped in /usr/src/lib/libcasper/services > --- all_subdir_lib/libpam --- > gzip -cn /usr/src/contrib/openpam/doc/man/pam_setenv.3 > pam_setenv.3.gz > --- all_subdir_lib/libcasper --- > *** [all_subdir_lib/libcasper/services] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/libcasper > 1 error >=20 > make[4]: stopped in /usr/src/lib/libcasper > --- all_subdir_lib/libpam --- > A failure has been detected in another branch of the parallel make > --- all_subdir_lib/libcasper --- > *** [all_subdir_lib/libcasper] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libpam --- >=20 > make[5]: stopped in /usr/src/lib/libpam/libpam > *** [all_subdir_lib/libpam/libpam] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/libpam > 1 error >=20 > make[4]: stopped in /usr/src/lib/libpam > *** [all_subdir_lib/libpam] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/ncurses --- > A failure has been detected in another branch of the parallel make >=20 > make[5]: stopped in /usr/src/lib/ncurses/form > *** [all_subdir_lib/ncurses/form] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/ncurses > --- all_subdir_lib/libarchive --- > A failure has been detected in another branch of the parallel make >=20 > make[4]: stopped in /usr/src/lib/libarchive > *** [all_subdir_lib/libarchive] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/ncurses --- > --- all_subdir_lib/ncurses/menu --- > A failure has been detected in another branch of the parallel make >=20 > make[5]: stopped in /usr/src/lib/ncurses/menu > *** [all_subdir_lib/ncurses/menu] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/ncurses > --- all_subdir_lib/ncurses/ncursesw --- > A failure has been detected in another branch of the parallel make >=20 > make[5]: stopped in /usr/src/lib/ncurses/ncursesw > *** [all_subdir_lib/ncurses/ncursesw] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/ncurses > 3 errors >=20 > make[4]: stopped in /usr/src/lib/ncurses > *** [all_subdir_lib/ncurses] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libprocstat --- > A failure has been detected in another branch of the parallel make >=20 > make[4]: stopped in /usr/src/lib/libprocstat > *** [all_subdir_lib/libprocstat] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libunbound --- > A failure has been detected in another branch of the parallel make >=20 > make[4]: stopped in /usr/src/lib/libunbound > *** [all_subdir_lib/libunbound] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/atf --- > A failure has been detected in another branch of the parallel make >=20 > make[5]: stopped in /usr/src/lib/atf/libatf-c++ > *** [all_subdir_lib/atf/libatf-c++] Error code 2 >=20 > make[4]: stopped in /usr/src/lib/atf > 1 error >=20 > make[4]: stopped in /usr/src/lib/atf > *** [all_subdir_lib/atf] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > --- all_subdir_lib/libsqlite3 --- > A failure has been detected in another branch of the parallel make >=20 > make[4]: stopped in /usr/src/lib/libsqlite3 > *** [all_subdir_lib/libsqlite3] Error code 2 >=20 > make[3]: stopped in /usr/src/lib > 8 errors >=20 > make[3]: stopped in /usr/src/lib > *** [all_subdir_lib] Error code 2 >=20 > make[2]: stopped in /usr/src > 1 error >=20 > make[2]: stopped in /usr/src > *** [everything] Error code 2 >=20 > make[1]: stopped in /usr/src > 1 error >=20 > make[1]: stopped in /usr/src > *** [buildworld] Error code 2 >=20 > make: stopped in /usr/src > 1 error >=20 > make: stopped in /usr/src >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" me, too here. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/3FMC7ruO+2Y_M86+=ngfJ5B Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWq6iGAAKCRDS528fyFhY lNLcAf44QpiRkVmUiDMV0+zD9GNK0t+k6rIQ67PVz6CWsVIghbt9mwkvu4eRekeq u68lR2Ece3XshLNSyha5YOtBNaS2Af9oDvdSaNSVMhjkv4WsPE2N2O/88rFDdG7K GMMhaCQoKIQcD4ZeErBVJ4jwbQeac54kd7oZQlT6Tu9cqN7kuUzz =kP6G -----END PGP SIGNATURE----- --Sig_/3FMC7ruO+2Y_M86+=ngfJ5B-- From owner-freebsd-current@freebsd.org Sun Mar 18 16:15:05 2018 Return-Path: Delivered-To: freebsd-current@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 0EAAFF5FDC8 for ; Sun, 18 Mar 2018 16:15:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E12078FC4 for ; Sun, 18 Mar 2018 16:15:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EC7D119CDE for ; Sun, 18 Mar 2018 16:15:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IGF3oA029079 for ; Sun, 18 Mar 2018 16:15:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IGF3aH029075 for freebsd-current@FreeBSD.org; Sun, 18 Mar 2018 16:15:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-current@FreeBSD.org Subject: [Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT Date: Sun, 18 Mar 2018 16:15:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mandree@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 18 Mar 2018 17:32:09 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 16:15:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226700 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-current@FreeBSD.org |cem@freebsd.org --- Comment #3 from Conrad Meyer --- Please do not CC huge mailing lists on bugs. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sun Mar 18 17:42:32 2018 Return-Path: Delivered-To: freebsd-current@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 91483F66B12 for ; Sun, 18 Mar 2018 17:42:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 247B47DBEF for ; Sun, 18 Mar 2018 17:42:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4BA1C1A93B for ; Sun, 18 Mar 2018 17:42:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IHgVh6060002 for ; Sun, 18 Mar 2018 17:42:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IHgVCg060001 for freebsd-current@FreeBSD.org; Sun, 18 Mar 2018 17:42:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-current@FreeBSD.org Subject: [Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT Date: Sun, 18 Mar 2018 17:42:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ml+freebsd@vishwin.info X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mandree@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 18 Mar 2018 18:00:01 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:42:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226700 Charlie Li changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-current@FreeBSD.org --- Comment #5 from Charlie Li --- In that case I do have WITH_ZONEINFO_LEAPSECONDS_SUPPORT set in src.conf. T= his setting also breaks databases/postgresql-server but it's a known quantity there. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sun Mar 18 17:50:52 2018 Return-Path: Delivered-To: freebsd-current@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 66C90F674AE for ; Sun, 18 Mar 2018 17:50:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 060037E25E for ; Sun, 18 Mar 2018 17:50:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3F0BF1A95A for ; Sun, 18 Mar 2018 17:50:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IHop70073216 for ; Sun, 18 Mar 2018 17:50:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IHop86073215 for freebsd-current@FreeBSD.org; Sun, 18 Mar 2018 17:50:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-current@FreeBSD.org Subject: [Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT Date: Sun, 18 Mar 2018 17:50:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ml+freebsd@vishwin.info X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mandree@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 18 Mar 2018 18:50:02 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:50:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226700 --- Comment #6 from Charlie Li --- Also could someone remove current@ again? I accidentally used a cached page= to comment and didn't pay attention to the CC list. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sun Mar 18 17:58:00 2018 Return-Path: Delivered-To: freebsd-current@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 D9981F67ADA for ; Sun, 18 Mar 2018 17:58:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60E6E7E74A for ; Sun, 18 Mar 2018 17:58:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A18A81AAA2 for ; Sun, 18 Mar 2018 17:57:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2IHvxvA090819 for ; Sun, 18 Mar 2018 17:57:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2IHvxSb090818 for freebsd-current@FreeBSD.org; Sun, 18 Mar 2018 17:57:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-current@FreeBSD.org Subject: [Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT Date: Sun, 18 Mar 2018 17:57:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: w.schwarzenfeld@utanet.at X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mandree@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 18 Mar 2018 18:50:12 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 17:58:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226700 w.schwarzenfeld@utanet.at changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-current@FreeBSD.org |w.schwarzenfeld@utanet.at --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sun Mar 18 19:38:12 2018 Return-Path: Delivered-To: freebsd-current@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 8EE85F4DB04 for ; Sun, 18 Mar 2018 19:38:12 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11B908307A; Sun, 18 Mar 2018 19:38:12 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id m68so6173319pfm.11; Sun, 18 Mar 2018 12:38:12 -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:content-transfer-encoding; bh=Shb26oZ+mtxqVCaHWlk/V5YIh1Y1KeWaR0AGlKfbKPw=; b=vOQU32mHWqmebp8yyf9oZHSul0zevFjNhi2Oyvv16zoAG0nQsZe1MgEVCBJv7Ikdr8 FhwPnQhlxVvntCTD5ug0H208deAKXhdeDagaCDsiKu7XrrBS0pZqyksErJRcNZei8IJN 3Vu4erpicEJek59CDpi1CRPLUQwTGOaRxxR+eAyyv5aW2J/SffBptEo9g7WBTyHHAWgT Lsk+YuYbktELiF3LmQDf34veBhXjBzF638gJscN7whfkaVX+7HBTyCxx1l0nNynFpltI pcqmhCHrZsBo9rT3B1H2iiix2/KhYIAu3uBB8CooHWl8onhUGHU1NlVYCLV09Ps4XSsT kV5g== 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:content-transfer-encoding; bh=Shb26oZ+mtxqVCaHWlk/V5YIh1Y1KeWaR0AGlKfbKPw=; b=ZniUy/ZwuniAfbN/rLRf0XKvy2r4Io1uPf8M+QSH2Yxm7oSZI5G0swIWBHFssxHSOy nfoFP1H8jT9zIO5ULd4DxD7jVrXip4FsY10lTWVSeB7VVts6cjmueCnwYIdjiqFz3rXc RFXDiAW12uhEm+Ga1r6a/5XjxGcZKsDbNcPgvPO5yHnDqsILB4Q/52Pb6AkeO1RTdBxf JLFdueLsjNX8vuIsUALiKhHW4mW2sPazoxWrdU0my/VXKLXS8HGV5+KFVseGdbvCHwnJ Wuhpjbht5ZLA9wh03Tqc5U9MZprebD+5nuvc+9JHsU5Ck0HzlTkLSAvMkvrNXXSnQAfA 8FAQ== X-Gm-Message-State: AElRT7Hz/ofAh8q12pic9sauG5PEHIHxRZREgNw1YLhFkR/KTJ+i8VFY i4x80HP8z23K8FtepRgJoajMZqP9mwXZHlCqSnDUuKtQ2UY= X-Google-Smtp-Source: AG47ELv56zW10jbV7ynCfrB69U1cPqWDE7R8c2xpdb+1Z54YA7GRWREiIXen2M9d6Hk3j9jXe0kd7WxEhbKXgbz9oIo= X-Received: by 10.101.66.132 with SMTP id j4mr5091270pgp.47.1521401890906; Sun, 18 Mar 2018 12:38:10 -0700 (PDT) MIME-Version: 1.0 Sender: oshogbo.vx@gmail.com Received: by 10.100.185.4 with HTTP; Sun, 18 Mar 2018 12:38:10 -0700 (PDT) In-Reply-To: <20180318183000.2c6fc352@thor.intern.walstatt.dynvpn.de> References: <20180318183000.2c6fc352@thor.intern.walstatt.dynvpn.de> From: Mariusz Zaborski Date: Sun, 18 Mar 2018 20:38:10 +0100 X-Google-Sender-Auth: 3SjzbnIyXw-N519f7_YczH2lgCg Message-ID: Subject: Re: /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: main To: "O. Hartmann" Cc: AN , FreeBSD Current , Mark Johnston Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 19:38:12 -0000 I think r331137 fix the problem. Thanks, Mariusz On 18 March 2018 at 18:29, O. Hartmann wrote: > Am Sun, 18 Mar 2018 13:19:08 -0400 (EDT) > AN schrieb: > >> Fyi, I started seeing this error today during buildworld compile. >> >> FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #15 r331021: Thu Mar 15 >> 16:30:40 EDT 2018 >> root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1200060 >> >> # svnlite info >> Path: . >> Working Copy Root Path: /usr/src >> URL: svn://svn.freebsd.org/base/head >> Relative URL: ^/head >> Repository Root: svn://svn.freebsd.org/base >> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >> Revision: 331135 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: markj >> Last Changed Rev: 331135 >> Last Changed Date: 2018-03-18 13:03:26 -0400 (Sun, 18 Mar 2018) >> ------------------------------------------------------------------------= ------------- >> >> --- all_subdir_lib/libcasper --- >> --- all_subdir_lib/libcasper/services/cap_sysctl --- >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: ma= in >> >>> referenced by crt1.c:74 (/usr/src/lib/csu/amd64/crt1.c:74) >> >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_star= t) >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_create >> >>> referenced by cap_sysctl.c:64 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:64) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_string >> >>> referenced by cap_sysctl.c:65 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:65) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_string >> >>> referenced by cap_sysctl.c:66 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:66) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_number >> >>> referenced by cap_sysctl.c:67 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:67) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_null >> >>> referenced by cap_sysctl.c:69 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:69) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_number >> >>> referenced by cap_sysctl.c:71 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:71) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_add_binary >> >>> referenced by cap_sysctl.c:73 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:73) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> cap_xfer_nvlist >> >>> referenced by cap_sysctl.c:74 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:74) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_get_number >> >>> referenced by cap_sysctl.c:77 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:77) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_get_number >> >>> referenced by cap_sysctl.c:78 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:78) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_destroy >> >>> referenced by cap_sysctl.c:79 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:79) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_get_number >> >>> referenced by cap_sysctl.c:84 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:84) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_get_binary >> >>> referenced by cap_sysctl.c:86 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:86) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_destroy >> >>> referenced by cap_sysctl.c:91 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:91) >> >>> /tmp/cap_sysctl-cfa2f8.o:(cap_sysctlbyname) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> service_register >> >>> referenced by cap_sysctl.c:295 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:295) >> >>> /tmp/cap_sysctl-cfa2f8.o:(init_casper_service) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_next >> >>> referenced by cap_sysctl.c:209 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >> >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_get_number >> >>> referenced by cap_sysctl.c:212 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:212) >> >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_next >> >>> referenced by cap_sysctl.c:209 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:209) >> >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_limit) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: undefined symbol: >> nvlist_error >> >>> referenced by cap_sysctl.c:110 >> (/usr/src/lib/libcasper/services/cap_sysctl/cap_sysctl.c:110) >> >>> /tmp/cap_sysctl-cfa2f8.o:(sysctl_command) >> >> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld: error: too many errors >> emitted, stopping now (use -error-limit=3D0 to see all errors) >> --- all_subdir_lib/libpam --- >> --- pam_setcred.3.gz --- >> gzip -cn /usr/src/contrib/openpam/doc/man/pam_setcred.3 > pam_setcred.3.= gz >> --- all_subdir_lib/ncurses --- >> --- all_subdir_lib/ncurses/form --- >> --- fld_dup.po --- >> cc -target x86_64-unknown-freebsd12.0 >> --sysroot=3D/usr/obj/usr/src/amd64.amd64/tmp >> -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -pg -O2 -pipe -I. >> -I/usr/obj/usr/src/amd64.amd64/lib/ncurses/ncurses >> -I/usr/src/lib/ncurses/ncurses -I/usr/src/lib/ncurses/ncurses >> -I/usr/src/contrib/ncurses/include -I/usr/src/contrib/ncurses/ncurses >> -Wall -DNDEBUG -DHAVE_CONFIG_H -I/usr/src/contrib/ncurses/form >> -I/usr/src/contrib/ncurses/menu -g -MD -MF.depend.fld_dup.po >> -MTfld_dup.po -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -We= rror >> -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes >> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sig= n >> -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 -Qunused-arguments -c >> /usr/src/contrib/ncurses/form/fld_dup.c -o fld_dup.po >> --- all_subdir_lib/libpam --- >> --- pam_setenv.3.gz --- >> --- all_subdir_lib/libcasper --- >> cc: error: linker command failed with exit code 1 (use -v to see >> invocation) >> *** [cap_sysctl] Error code 1 >> >> make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl >> 1 error >> >> make[6]: stopped in /usr/src/lib/libcasper/services/cap_sysctl >> *** [all_subdir_lib/libcasper/services/cap_sysctl] Error code 2 >> >> make[5]: stopped in /usr/src/lib/libcasper/services >> 1 error >> >> make[5]: stopped in /usr/src/lib/libcasper/services >> --- all_subdir_lib/libpam --- >> gzip -cn /usr/src/contrib/openpam/doc/man/pam_setenv.3 > pam_setenv.3.gz >> --- all_subdir_lib/libcasper --- >> *** [all_subdir_lib/libcasper/services] Error code 2 >> >> make[4]: stopped in /usr/src/lib/libcasper >> 1 error >> >> make[4]: stopped in /usr/src/lib/libcasper >> --- all_subdir_lib/libpam --- >> A failure has been detected in another branch of the parallel make >> --- all_subdir_lib/libcasper --- >> *** [all_subdir_lib/libcasper] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/libpam --- >> >> make[5]: stopped in /usr/src/lib/libpam/libpam >> *** [all_subdir_lib/libpam/libpam] Error code 2 >> >> make[4]: stopped in /usr/src/lib/libpam >> 1 error >> >> make[4]: stopped in /usr/src/lib/libpam >> *** [all_subdir_lib/libpam] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/ncurses --- >> A failure has been detected in another branch of the parallel make >> >> make[5]: stopped in /usr/src/lib/ncurses/form >> *** [all_subdir_lib/ncurses/form] Error code 2 >> >> make[4]: stopped in /usr/src/lib/ncurses >> --- all_subdir_lib/libarchive --- >> A failure has been detected in another branch of the parallel make >> >> make[4]: stopped in /usr/src/lib/libarchive >> *** [all_subdir_lib/libarchive] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/ncurses --- >> --- all_subdir_lib/ncurses/menu --- >> A failure has been detected in another branch of the parallel make >> >> make[5]: stopped in /usr/src/lib/ncurses/menu >> *** [all_subdir_lib/ncurses/menu] Error code 2 >> >> make[4]: stopped in /usr/src/lib/ncurses >> --- all_subdir_lib/ncurses/ncursesw --- >> A failure has been detected in another branch of the parallel make >> >> make[5]: stopped in /usr/src/lib/ncurses/ncursesw >> *** [all_subdir_lib/ncurses/ncursesw] Error code 2 >> >> make[4]: stopped in /usr/src/lib/ncurses >> 3 errors >> >> make[4]: stopped in /usr/src/lib/ncurses >> *** [all_subdir_lib/ncurses] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/libprocstat --- >> A failure has been detected in another branch of the parallel make >> >> make[4]: stopped in /usr/src/lib/libprocstat >> *** [all_subdir_lib/libprocstat] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/libunbound --- >> A failure has been detected in another branch of the parallel make >> >> make[4]: stopped in /usr/src/lib/libunbound >> *** [all_subdir_lib/libunbound] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/atf --- >> A failure has been detected in another branch of the parallel make >> >> make[5]: stopped in /usr/src/lib/atf/libatf-c++ >> *** [all_subdir_lib/atf/libatf-c++] Error code 2 >> >> make[4]: stopped in /usr/src/lib/atf >> 1 error >> >> make[4]: stopped in /usr/src/lib/atf >> *** [all_subdir_lib/atf] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> --- all_subdir_lib/libsqlite3 --- >> A failure has been detected in another branch of the parallel make >> >> make[4]: stopped in /usr/src/lib/libsqlite3 >> *** [all_subdir_lib/libsqlite3] Error code 2 >> >> make[3]: stopped in /usr/src/lib >> 8 errors >> >> make[3]: stopped in /usr/src/lib >> *** [all_subdir_lib] Error code 2 >> >> make[2]: stopped in /usr/src >> 1 error >> >> make[2]: stopped in /usr/src >> *** [everything] Error code 2 >> >> make[1]: stopped in /usr/src >> 1 error >> >> make[1]: stopped in /usr/src >> *** [buildworld] Error code 2 >> >> make: stopped in /usr/src >> 1 error >> >> make: stopped in /usr/src >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" > > me, too here. > > -- > O. Hartmann > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Ab= s. 4 BDSG). From owner-freebsd-current@freebsd.org Sun Mar 18 21:09:41 2018 Return-Path: Delivered-To: freebsd-current@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 CCA77F54681 for ; Sun, 18 Mar 2018 21:09:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 35FC28755B; Sun, 18 Mar 2018 21:09:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2IL8Tf9099868 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Mar 2018 14:08:30 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2IL8RYe099867; Sun, 18 Mar 2018 14:08:27 -0700 (PDT) (envelope-from fbsd) Date: Sun, 18 Mar 2018 14:08:27 -0700 From: bob prohaska To: Jeff Roberson Cc: "O. Hartmann" , Roman Bogorodskiy , "Danilo G. Baio" , "Rodney W. Grimes" , Trond Endrest?l , FreeBSD current , Kurt Jaeger , bob prohaska Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180318210827.GB99651@www.zefox.net> References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> 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-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 21:09:42 -0000 On Sun, Mar 11, 2018 at 10:43:58AM -1000, Jeff Roberson wrote: > Also, if you could try going back to r328953 or r326346 and let me know if > the problem exists in either. That would be very helpful. If anyone is Not sure this is relevant, but r326343 is able to run a j4 buildworld to completion on an RPi3 with 3 gigs of microSD-based swap. There are periods of seeming distress at times (lots of swread, pfault state in top along with high %idle) in top, but the compilation completes. In contrast, r328953 could not complete buildworld using -j4. Buildworld would stop, usually reporting c++ killed, apparently for want of swap, even though swap usage never exceeded about 30% accoring to top. The machine employs UFS filesystems, the kernel config can be seen at http://www.zefox.net/~fbsd/rpi3/kernel_config/ZEFOX Thanks for reading, I hope it's useful. bob prohaska From owner-freebsd-current@freebsd.org Sun Mar 18 22:35:36 2018 Return-Path: Delivered-To: freebsd-current@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 93F9FF59FA8; Sun, 18 Mar 2018 22:35:36 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [104.225.8.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd-11-64", Issuer "freebsd-11-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D5A776A9E5; Sun, 18 Mar 2018 22:35:35 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [104.225.8.138]) by mail.neu.net (8.15.2/8.15.2) with ESMTPS id w2IMZRIJ034447 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Mar 2018 18:35:29 -0400 (EDT) (envelope-from andy@neu.net) Date: Sun, 18 Mar 2018 18:35:27 -0400 (EDT) From: AN To: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead Message-ID: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.neu.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 22:35:36 -0000 FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #12 r331138: Sun Mar 18 15:09:37 EDT 2018 root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 I recently started to see strange behavior on 2 different machines and was wondering if anyone else has run into it. Within the last few days, I have been experiencing a reproduceable problem with sound. It happens in VLC and also in Virtualbox watching video in a browser. I get the following log entry: Mar 18 18:10:26 BSD_12 kernel: pcm1: chn_write(): pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead and then sound is dead in all applications. Any ideas what to do? I tried the following: rebuilt world and kernel several times rebuilt libvorbis rebuilt ffmpeg rebuilt vlc rebuilt Vbox and kmod The only thing I can think of as a possible issue is an update to libvorbis recently, cc'ing ports just in case. Is there a way to restart the audio subsystem without rebooting the machine? Is there anymore info I can provide to troubleshoot? # dmesg | grep pcm pcm0: at nid 3 on hdaa0 pcm1: at nid 20,22,21,23 and 24,26 on hdaa1 pcm2: at nid 27 and 25 on hdaa1 pcm1: chn_write(): pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead # pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x7a341462 chip=0x14501022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Family 17h (Models 00h-0fh) Root Complex' class = bridge subclass = HOST-PCI hdac0@pci0:34:0:1: class=0x040300 card=0xaa681545 chip=0xaa681002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' device = 'Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series]' class = multimedia subclass = HDA hdac1@pci0:36:0:3: class=0x040300 card=0xda341462 chip=0x14571022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Family 17h (Models 00h-0fh) HD Audio Controller' class = multimedia subclass = HDA Thanks in advance for any advice. From owner-freebsd-current@freebsd.org Sun Mar 18 22:58:55 2018 Return-Path: Delivered-To: freebsd-current@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 10381F5BA20 for ; Sun, 18 Mar 2018 22:58:55 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95C976BDF9 for ; Sun, 18 Mar 2018 22:58:54 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qk0-x243.google.com with SMTP id d206so16512813qkb.3 for ; Sun, 18 Mar 2018 15:58:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:from:to:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=bEKCiMYFAnnH48gsSl76H5D9EDytu4gVb0fryzuD+JA=; b=rpvQokt+pWMcAgjbxI4z5a0Kd2TPrDHi2x1nx0a8SoeXhdebIQHUp66V6v1ctmOfS6 7yYS/bZGiSPoDZmhhVzLTdVNV84DV4/ENUwu/Z7bQYQn8ZWaXCg5KFQCyMgQlu/BrBIp NLPynLlZ39nB9ZVwb0+281Ggj7WY27ScpcR2AYlnRM8NICpy6pRYO1YQsnBJHGw92PCN IdpNlOmk76aqgT25jXopewQK3XMV2AIqa9RBlsDh1WWqfwQ0hH4BWISaxvYhrBf/f9AS /ckh1gW0tj5Vj5CzsvGSU2L6gA/fyBwKD1KECK2gpFqQnPy/GnmKznVfcD85XqiYMKXq uAhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:from:to:references:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=bEKCiMYFAnnH48gsSl76H5D9EDytu4gVb0fryzuD+JA=; b=bMgY9gv9dqDrj4OTfmbuzaKovm8IIWislpP1GFHB9CKfo9s4uWvNhBLPSaVqMNscvo 4HDtNSul04riO3aJ8Z50qwRV6PychH/2nPBL1/S8awnNq3u16DdHXAyZPunSBhY3T7OX 5Zcs+xUGABCAz4anhZnX+KkQBVPdl1rdlvF4j1VZ6jqM8u8JnnUxtXhbf5E5EKghVMnS Zn/++YvgJeCPxFwxWwTvS3fV7vytS7rLiiUiPPhWJd6bKC28gQItP7qWFLG8vIriyhjA Fhs8LghRSw+IdrnGhZf/waL1NhESoh0l5osh/2f5caFEy3MvCaLvHK6I+w3155OCriD1 aNlg== X-Gm-Message-State: AElRT7Fh60iAWIUhOWLrvRf5MP7sRIZdPzC+H+5NUC2SHhdTUCiYc1TM qcp7sPTzU0OUkzEColzk3JM+yYBl X-Google-Smtp-Source: AG47ELtkuDoqXln8FA8/jd7iWRE3YoAiBZYMyRmq7KUZd+LmpXlfBeZcWD+8E1KatWE8BU8aWRRAxA== X-Received: by 10.55.110.197 with SMTP id j188mr14589917qkc.155.1521413934175; Sun, 18 Mar 2018 15:58:54 -0700 (PDT) Received: from [155.41.26.230] (dhcp-wifi-8021x-155-41-26-230.bu.edu. [155.41.26.230]) by smtp.gmail.com with ESMTPSA id f6sm8935463qth.44.2018.03.18.15.58.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Mar 2018 15:58:53 -0700 (PDT) Sender: Theron Tarigo Subject: Re: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead From: Theron Tarigo To: freebsd-current@freebsd.org References: <764e2df5-613d-a131-5d7d-6df54599509b@gmail.com> Message-ID: <94c78258-4b78-01ad-3730-66cf298ae1fb@gmail.com> Date: Sun, 18 Mar 2018 18:58:53 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <764e2df5-613d-a131-5d7d-6df54599509b@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 22:58:55 -0000 On 03/18/18 18:52, Theron Tarigo wrote: > On 03/18/18 18:35, AN wrote: >> Is there a way to restart the audio subsystem without rebooting the >> machine? > Building kernel with sound and snd_* as loadable modules should enable > this to be accomplished with kldunload/kldload.  In my experience > though all sound device files must be closed before unloading these > modules to avoid some lockup issues. From owner-freebsd-current@freebsd.org Sun Mar 18 22:52:10 2018 Return-Path: Delivered-To: freebsd-current@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 7D4AFF5B2ED; Sun, 18 Mar 2018 22:52:10 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12C0C6B9B0; Sun, 18 Mar 2018 22:52:10 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qk0-x244.google.com with SMTP id b198so16490516qkg.9; Sun, 18 Mar 2018 15:52:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=5Ad/8pAJjW8GAusrizE6fNjxK1onikKKFTsmLjQhr1A=; b=eF2cr3WKpRkkOgVXJivbOIgTHgTGA216pIvNn9wcRuT+FbQSn1hyMfeGfCOF6mInv2 bngnuJwtTdWRPMdYNWtqXfywpWF5Xcem30Z00PMWSRazKZtxaOeWMeJcF9WvWrXwD/O3 c2KjaWQu7+ISjen1sIhrWDjSTx9XvyHVSm2atOc7rim3/E0C4yUC+V9GkgW+WLdZcMW4 cc8wV2lG6WkS1/0hLMmok1BXrnJwyhypjQ65wOO6ed6i+8x1jgN0MJxpcjBBTf9RQ1Mn N8P/eclPMG4RzGeG/ktYOc1EYCxsu2wznXU8iwPZ/fuI3kramJMkq6+hdM41GQvt4gss 6S/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=5Ad/8pAJjW8GAusrizE6fNjxK1onikKKFTsmLjQhr1A=; b=tmMhvoiWFn6azL7zFLemTlDMN8u6E/QPENkFvwk5vCvUKQzv3LRtW2UYLeQ/I3mMw+ eKLcyMRn59Y+/Qm69CRtKqhnD/SWyO6HomwYKg5jMptYIrLa3HgAsrcv66Ax/pbjV96r LAKSdoTdWziI620TPYpwIzZ/+DQvre8kMhCvGI0ehTKIms9KjBqoRLILS5GefpOAfpmQ ocrvmPCtx6WZSQTY7h40H8yvIoQHiQIQgQ7RSa9dqLvWjCCKvd+KR71TeGnvHd5GayrA VB81Me3p7BUIRC+e+slURdN6MluXMF25jPeazPFVRQEhSqox6Ed23pG/scLSs6v63D6P nsSA== X-Gm-Message-State: AElRT7GoFvSBG49KiIleKEnhLUIlsHqTzO9/KUg9YIdfe7W6ppEZWk0R ibQDzIyFOBSZ2fFM6KLGcH7hTiVe X-Google-Smtp-Source: AG47ELvm5XQCAnR8Ln95TTmrMJXJ/aHhiaeSuJKE8qhDpc4FsJgOasITxgxqyffXNf5svsDhhQqJDQ== X-Received: by 10.55.190.1 with SMTP id o1mr14792762qkf.333.1521413529561; Sun, 18 Mar 2018 15:52:09 -0700 (PDT) Received: from [155.41.26.230] (dhcp-wifi-8021x-155-41-26-230.bu.edu. [155.41.26.230]) by smtp.gmail.com with ESMTPSA id c25sm9152606qtn.9.2018.03.18.15.52.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Mar 2018 15:52:09 -0700 (PDT) Sender: Theron Tarigo Subject: Re: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead To: AN , freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org References: From: Theron Tarigo Message-ID: <764e2df5-613d-a131-5d7d-6df54599509b@gmail.com> Date: Sun, 18 Mar 2018 18:52:08 -0400 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; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Mailman-Approved-At: Sun, 18 Mar 2018 23:11:22 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 22:52:10 -0000 On 03/18/18 18:35, AN wrote: > Is there a way to restart the audio subsystem without rebooting the > machine? Building kernel with sound and snd_* as loadable modules should enable this to be accomplished with kldunload/kldload.  In my experience though all sound device files must be closed before unloading these modules to avoid some lockup issues. From owner-freebsd-current@freebsd.org Sun Mar 18 23:44:34 2018 Return-Path: Delivered-To: freebsd-current@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 0CAF9F5EA89; Sun, 18 Mar 2018 23:44:34 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 824206DCA5; Sun, 18 Mar 2018 23:44:33 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id xhw0e0GJ7XziTxhw2etD6d; Sun, 18 Mar 2018 17:41:55 -0600 X-Authority-Analysis: v=2.3 cv=X6B81lbe c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=8nJEP1OIZ-IA:10 a=v2DPQv5-lfwA:10 a=pGLkceISAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=N8H_fjdTwb6thRU9oSUA:9 a=wPNLvfGTeEIA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 286D5274; Sun, 18 Mar 2018 16:41:52 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w2INfpLs004206; Sun, 18 Mar 2018 16:41:51 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w2INfppM004203; Sun, 18 Mar 2018 16:41:51 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201803182341.w2INfppM004203@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Theron Tarigo cc: AN , freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead In-Reply-To: Message from Theron Tarigo of "Sun, 18 Mar 2018 18:52:08 -0400." <764e2df5-613d-a131-5d7d-6df54599509b@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Sun, 18 Mar 2018 16:41:51 -0700 X-CMAE-Envelope: MS4wfNP4snWt3AU8J7a/COJ/lWFO/GxOi+6NQh49pMZkQv+WmEjYmLuh6s6G/tUlJKadQxr7xl0Lwuc7nIxSoKI/jOoZ8r+jEJTfvHl2RT2CN30ZzBE1qT04 quoKpkyPQ0p0vQ5SUzEYJFrv1JKngyQ+KCoXnG4IjcXBV+G8cov/80vMysDqHC2DehdZUju9Ufo4PmE2jDA0yjreRdxpYWeGrK/d+QyJv8ACc9yrfPw8kKTo X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 23:44:34 -0000 In message <764e2df5-613d-a131-5d7d-6df54599509b@gmail.com>, Theron Tarigo writ es: > On 03/18/18 18:35, AN wrote: > > Is there a way to restart the audio subsystem without rebooting the > > machine? > Building kernel with sound and snd_* as loadable modules should enable > this to be accomplished with kldunload/kldload.  In my experience though > all sound device files must be closed before unloading these modules to > avoid some lockup issues. The other thing you might want to check out is if you multiboot your laptop that any non-FreeBSD operating system may put hardware into an inconsistent state. For example, my Acer laptop loses sound if I boot Windows then boot FreeBSD. The workaround is either adjust the HDA inputs/outputs through sysctl or simply power cycle the laptop. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Mon Mar 19 02:15:30 2018 Return-Path: Delivered-To: freebsd-current@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 ADC48F67A9C for ; Mon, 19 Mar 2018 02:15:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic316-9.consmr.mail.gq1.yahoo.com (sonic316-9.consmr.mail.gq1.yahoo.com [98.137.69.33]) (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 39F2272C61 for ; Mon, 19 Mar 2018 02:15:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: rE0oZnAVM1mxi4HPio9DRYFQNwffAuQyDqxJsZWL5NRVxnlxuX1UgFJ7eBmw_X1 N5VJ5exL31_99x41UKQPm99XjGoKXx6lcoagDshisvhafMvQnlPjuKPzPCJVELN6nh7fWXnS8be. HpvdLdSJLQx9.Y1pgBTII14GutZ0G1dpZ5YxPItlcGA03ZhoTHtmdwKlDcfBA4NaOJMMj4KlKb4u jKmVSKNKoabgZhAOSHL91S9bvgetDJOE.xrTOduJfInZBknIIrKwbfO.IMU08pV_zi180A28EZtu XA2Eq9lpJfAoW_hPmaD9EcgoAejvy_WHWzFxGU4pVIFrIAhI9OafB9yUMBdV5JnDfCQzcdPkT6eU FMT_Cks0rmeFGUh6Oh0avOBKp0u_ChFdiCsxk.Yb6Z0LrGnrGGF2.A.yQNGtM2Anle497npEw92w 8RLqQOI1l00Efh1EX0g3jYgY78kkPQn4JjrN8hcLQYGLrlIRoBK2u18QPJqaJzzirrKXC Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Mon, 19 Mar 2018 02:15:28 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp401.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 735257d409091420e7a27ef0d04c0c87; Mon, 19 Mar 2018 00:54:31 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-Id: <1F7066EE-2419-4C91-8D76-9ADCE0444AEA@yahoo.com> Date: Sun, 18 Mar 2018 17:54:30 -0700 Cc: "O. Hartmann" To: bob prohaska , Jeff Roberson , freebsd-current@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 02:15:30 -0000 bob prohaska fbsd at www.zefox.net wrote on Sun Mar 18 21:09:42 UTC 2018 : > On Sun, Mar 11, 2018 at 10:43:58AM -1000, Jeff Roberson wrote: >=20 > > Also, if you could try going back to r328953 or r326346 and let me = know if=20 > > the problem exists in either. That would be very helpful. If = anyone is=20 >=20 > Not sure this is relevant, but r326343 is able to run a j4 buildworld > to completion on an RPi3 with 3 gigs of microSD-based swap. There are > periods of seeming distress at times (lots of swread, pfault state > in top along with high %idle) in top, but the compilation completes. >=20 > In contrast, r328953 could not complete buildworld using -j4. = Buildworld > would stop, usually reporting c++ killed, apparently for want of swap, > even though swap usage never exceeded about 30% accoring to top. >=20 > The machine employs UFS filesystems, . . . Sounds like -r326346 would be an interesting kernel to test (the next check-in on head after -r326343, one of Jeff's check-ins). -r328953 was just before Jeff's: Author: jeff Date: Tue Feb 6 22:10:07 2018 New Revision: 328954 URL:=20 https://svnweb.freebsd.org/changeset/base/328954 Log: Use per-domain locks for vm page queue free. Move paging control from global to per-domain state. Protect reservations with the free lock from the domain that they belong to. Refactor to make vm domains more of a first class object. So, if -r328953 behaves oddly and -r326343 does not, then the question is if -r326346 makes the difference: Author: jeff Date: Tue Nov 28 23:18:35 2017 New Revision: 326346 URL:=20 https://svnweb.freebsd.org/changeset/base/326346 Log: Move domain iterators into the page layer where domain selection = should take place. This makes the majority of the phys layer explicitly domain = specific. (Unfortunately my FreeBSD time is currently greatly limited.) It is also interesting that your test context is UFS. O. Hartmann has reported problems for UFS in a more modern version: -r330608 . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Mar 19 03:50:34 2018 Return-Path: Delivered-To: freebsd-current@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 5012CF4A6B3 for ; Mon, 19 Mar 2018 03:50:34 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A61BD77860 for ; Mon, 19 Mar 2018 03:50:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2J3oYQm001507 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Mar 2018 20:50:35 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2J3oXB3001506; Sun, 18 Mar 2018 20:50:33 -0700 (PDT) (envelope-from fbsd) Date: Sun, 18 Mar 2018 20:50:33 -0700 From: bob prohaska To: Mark Millard Cc: Jeff Roberson , freebsd-current@freebsd.org, "O. Hartmann" , bob prohaska Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180319035033.GA473@www.zefox.net> References: <1F7066EE-2419-4C91-8D76-9ADCE0444AEA@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1F7066EE-2419-4C91-8D76-9ADCE0444AEA@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 03:50:34 -0000 On Sun, Mar 18, 2018 at 05:54:30PM -0700, Mark Millard wrote: > bob prohaska fbsd at www.zefox.net wrote on > Sun Mar 18 21:09:42 UTC 2018 : > > > On Sun, Mar 11, 2018 at 10:43:58AM -1000, Jeff Roberson wrote: > > > > > Also, if you could try going back to r328953 or r326346 and let me know if > > > the problem exists in either. That would be very helpful. If anyone is > > > > Not sure this is relevant, but r326343 is able to run a j4 buildworld > > to completion on an RPi3 with 3 gigs of microSD-based swap. There are > > periods of seeming distress at times (lots of swread, pfault state > > in top along with high %idle) in top, but the compilation completes. > > > > In contrast, r328953 could not complete buildworld using -j4. Buildworld > > would stop, usually reporting c++ killed, apparently for want of swap, > > even though swap usage never exceeded about 30% accoring to top. > > > > The machine employs UFS filesystems, . . . > > > Sounds like -r326346 would be an interesting kernel to test (the > next check-in on head after -r326343, one of Jeff's check-ins). > > -r328953 was just before Jeff's: > My intent was to try 326346. Somehow 326343 arrived in its place. Do architectures affect revision numbers? I thought not, but... > Author: jeff > Date: Tue Feb 6 22:10:07 2018 > New Revision: 328954 > URL: > https://svnweb.freebsd.org/changeset/base/328954 > > > Log: > Use per-domain locks for vm page queue free. Move paging control from > global to per-domain state. Protect reservations with the free lock > from the domain that they belong to. Refactor to make vm domains more > of a first class object. > > > > So, if -r328953 behaves oddly and -r326343 does not, then the > question is if -r326346 makes the difference: > > Author: jeff > Date: Tue Nov 28 23:18:35 2017 > New Revision: 326346 > URL: > https://svnweb.freebsd.org/changeset/base/326346 > > > Log: > Move domain iterators into the page layer where domain selection should take > place. This makes the majority of the phys layer explicitly domain specific. > > > (Unfortunately my FreeBSD time is currently greatly limited.) > > It is also interesting that your test context is UFS. O. Hartmann > has reported problems for UFS in a more modern version: -r330608 . > When "out of swap" problems appeared I cobbled up a custom kernel, in the hope that a smaller kernel might help. It has since developed that the custom kernel can't boot, but GENERIC still boots. The system is now running a j4 buildworld on r331153 with a GENERIC kernel to see if maybe the problem has already been fixed in a way that was obscured by the customization. The kernel config is at http://www.zefox.net/~fbsd/rpi3/kernel_config/ZEFOX Thanks for reading, bob prohaska From owner-freebsd-current@freebsd.org Mon Mar 19 16:57:02 2018 Return-Path: Delivered-To: freebsd-current@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 46AC8F5B3A7; Mon, 19 Mar 2018 16:57:02 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AF0D79431; Mon, 19 Mar 2018 16:57:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2JGv2r8003732 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Mar 2018 09:57:03 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2JGv2CT003731; Mon, 19 Mar 2018 09:57:02 -0700 (PDT) (envelope-from fbsd) Date: Mon, 19 Mar 2018 09:57:01 -0700 From: bob prohaska To: Mark Millard Cc: Jeff Roberson , freebsd-current@freebsd.org, "O. Hartmann" , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180319165701.GA3701@www.zefox.net> References: <1F7066EE-2419-4C91-8D76-9ADCE0444AEA@yahoo.com> <20180319035033.GA473@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180319035033.GA473@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 16:57:02 -0000 On Sun, Mar 18, 2018 at 08:50:33PM -0700, bob prohaska wrote: > On Sun, Mar 18, 2018 at 05:54:30PM -0700, Mark Millard wrote: > > bob prohaska fbsd at www.zefox.net wrote on > > Sun Mar 18 21:09:42 UTC 2018 : > > > > > On Sun, Mar 11, 2018 at 10:43:58AM -1000, Jeff Roberson wrote: > > > > > > > Also, if you could try going back to r328953 or r326346 and let me know if > > > > the problem exists in either. That would be very helpful. If anyone is > > > > > > Not sure this is relevant, but r326343 is able to run a j4 buildworld > > > to completion on an RPi3 with 3 gigs of microSD-based swap. There are > > > periods of seeming distress at times (lots of swread, pfault state > > > in top along with high %idle) in top, but the compilation completes. > > > > > > In contrast, r328953 could not complete buildworld using -j4. Buildworld > > > would stop, usually reporting c++ killed, apparently for want of swap, > > > even though swap usage never exceeded about 30% accoring to top. > > > > > > The machine employs UFS filesystems, . . . > > > > > > Sounds like -r326346 would be an interesting kernel to test (the > > next check-in on head after -r326343, one of Jeff's check-ins). > > > > -r328953 was just before Jeff's: > > > > My intent was to try 326346. Somehow 326343 arrived in its place. > Do architectures affect revision numbers? I thought not, but... > > > > When "out of swap" problems appeared I cobbled up a custom kernel, > in the hope that a smaller kernel might help. It has since developed > that the custom kernel can't boot, but GENERIC still boots. The system > is now running a j4 buildworld on r331153 with a GENERIC kernel The -j4 buildworld using a GENERIC kernel crashed at the 1.6 MB point in the logfile, which is the usual place for trouble. The debris collected is at http://www.zefox.net/~fbsd/rpi3/crashes/20180319/ Being on an RPi3, I'm still uncertain whether the problems seen are connected to the original subject. If they are not, please inform me. Thanks for reading, bob prohaska From owner-freebsd-current@freebsd.org Mon Mar 19 23:00:09 2018 Return-Path: Delivered-To: freebsd-current@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 36DD4F518A0 for ; Mon, 19 Mar 2018 23:00:09 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 84E606AA7A for ; Mon, 19 Mar 2018 23:00:07 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w2JN04fx007127; Tue, 20 Mar 2018 08:00:05 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201803192300.w2JN04fx007127@kx.openedu.org> Date: Tue, 20 Mar 2018 08:00:04 +0900 From: KIRIYAMA Kazuhiko To: freebsd-current@freebsd.org Cc: kiri@kx.openedu.org Subject: ZFS i/o error in recent 12.0 User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 23:00:09 -0000 Hi, I've been encountered suddenly death in ZFS full volume machine(r330434) about 10 days after installation[1]: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zroot gptzfsboot: failed to mount default pool zroot FreeBSD/x86 boot ZFS: i/o error - all block copies unavailable ZFS: can't find dataset u Default: zroot/<0x0>: boot: Partition is bellow: # gpart show /dev/mfid0 => 40 31247564720 mfid0 GPT (15T) 40 409600 1 efi (200M) 409640 1024 2 freebsd-boot (512K) 410664 984 - free - (492K) 411648 268435456 3 freebsd-swap (128G) 268847104 30978715648 4 freebsd-zfs (14T) 31247562752 2008 - free - (1.0M) # But nothing had beed happend in old current ZFS full volume machine(r327038M). According to [2] the reason is boot/zfs/zpool.cache inconsistent. I've tried to cope with this by repairing /boot [3] from rescue bootable USB as follows: # kldload zfs # zpool import pool: zroot id: 17762298124265859537 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: zroot ONLINE mfid0p4 ONLINE # zpool import -fR /mnt zroot # df -h Filesystem Size Used Avail Capacity Mounted on /dev/da0p2 14G 1.6G 11G 13% / devfs 1.0K 1.0K 0B 100% /dev zroot/.dake 14T 18M 14T 0% /mnt/.dake zroot/ds 14T 96K 14T 0% /mnt/ds zroot/ds/backup 14T 88K 14T 0% /mnt/ds/backup zroot/ds/backup/kazu.pis 14T 31G 14T 0% /mnt/ds/backup/kazu.pis zroot/ds/distfiles 14T 7.9M 14T 0% /mnt/ds/distfiles zroot/ds/obj 14T 10G 14T 0% /mnt/ds/obj zroot/ds/packages 14T 4.0M 14T 0% /mnt/ds/packages zroot/ds/ports 14T 1.3G 14T 0% /mnt/ds/ports zroot/ds/src 14T 2.6G 14T 0% /mnt/ds/src zroot/tmp 14T 88K 14T 0% /mnt/tmp zroot/usr/home 14T 136K 14T 0% /mnt/usr/home zroot/usr/local 14T 10M 14T 0% /mnt/usr/local zroot/var/audit 14T 88K 14T 0% /mnt/var/audit zroot/var/crash 14T 88K 14T 0% /mnt/var/crash zroot/var/log 14T 388K 14T 0% /mnt/var/log zroot/var/mail 14T 92K 14T 0% /mnt/var/mail zroot/var/ports 14T 11M 14T 0% /mnt/var/ports zroot/var/tmp 14T 6.0M 14T 0% /mnt/var/tmp zroot/vm 14T 2.8G 14T 0% /mnt/vm zroot/vm/tbedfc 14T 1.6G 14T 0% /mnt/vm/tbedfc zroot 14T 88K 14T 0% /mnt/zroot # zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 51.1G 13.9T 88K /mnt/zroot zroot/.dake 18.3M 13.9T 18.3M /mnt/.dake zroot/ROOT 1.71G 13.9T 88K none zroot/ROOT/default 1.71G 13.9T 1.71G /mnt/mnt zroot/ds 45.0G 13.9T 96K /mnt/ds zroot/ds/backup 30.8G 13.9T 88K /mnt/ds/backup zroot/ds/backup/kazu.pis 30.8G 13.9T 30.8G /mnt/ds/backup/kazu.pis zroot/ds/distfiles 7.88M 13.9T 7.88M /mnt/ds/distfiles zroot/ds/obj 10.4G 13.9T 10.4G /mnt/ds/obj zroot/ds/packages 4.02M 13.9T 4.02M /mnt/ds/packages zroot/ds/ports 1.26G 13.9T 1.26G /mnt/ds/ports zroot/ds/src 2.56G 13.9T 2.56G /mnt/ds/src zroot/tmp 88K 13.9T 88K /mnt/tmp zroot/usr 10.4M 13.9T 88K /mnt/usr zroot/usr/home 136K 13.9T 136K /mnt/usr/home zroot/usr/local 10.2M 13.9T 10.2M /mnt/usr/local zroot/var 17.4M 13.9T 88K /mnt/var zroot/var/audit 88K 13.9T 88K /mnt/var/audit zroot/var/crash 88K 13.9T 88K /mnt/var/crash zroot/var/log 388K 13.9T 388K /mnt/var/log zroot/var/mail 92K 13.9T 92K /mnt/var/mail zroot/var/ports 10.7M 13.9T 10.7M /mnt/var/ports zroot/var/tmp 5.98M 13.9T 5.98M /mnt/var/tmp zroot/vm 4.33G 13.9T 2.75G /mnt/vm zroot/vm/tbedfc 1.58G 13.9T 1.58G /mnt/vm/tbedfc # zfs mount zroot/ROOT/default # cd /mnt/mnt/ # mv boot boot.bak # cp -RPp boot.bak boot # gpart show /dev/mfid0 => 40 31247564720 mfid0 GPT (15T) 40 409600 1 efi (200M) 409640 1024 2 freebsd-boot (512K) 410664 984 - free - (492K) 411648 268435456 3 freebsd-swap (128G) 268847104 30978715648 4 freebsd-zfs (14T) 31247562752 2008 - free - (1.0M) # gpart bootcode -b /mnt/mnt/boot/pmbr -p /boot/gptzfsboot -i 2 mfid0 partcode written to mfid0p2 bootcode written to mfid0 # cd # zpool export zroot # But can not boot: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zroot gptzfsboot: failed to mount default pool zroot FreeBSD/x86 boot Any idea? Best regards [1] http://ds.truefc.org/~kiri/freebsd/current/zfs/messages [2] https://lists.freebsd.org/pipermail/freebsd-questions/2016-February/270505.html [3] https://forums.freebsd.org/threads/zfs-i-o-error-all-block-copies-unavailable-invalid-format.55227/#post-312830 --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Mon Mar 19 23:09:33 2018 Return-Path: Delivered-To: freebsd-current@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 468BFF5231A for ; Mon, 19 Mar 2018 23:09:33 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6C796B1E2 for ; Mon, 19 Mar 2018 23:09:32 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 644D21428D; Mon, 19 Mar 2018 23:09:26 +0000 (UTC) Subject: Re: ZFS i/o error in recent 12.0 To: KIRIYAMA Kazuhiko , freebsd-current@freebsd.org References: <201803192300.w2JN04fx007127@kx.openedu.org> From: Allan Jude Message-ID: Date: Mon, 19 Mar 2018 19:09:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803192300.w2JN04fx007127@kx.openedu.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zenOVxIYLQXM9LPpOVLPmpwA7MS5LlRSN" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 23:09:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --zenOVxIYLQXM9LPpOVLPmpwA7MS5LlRSN Content-Type: multipart/mixed; boundary="L9RDf21KmKJBz1ri2GYLixyraeFX3VorL"; protected-headers="v1" From: Allan Jude To: KIRIYAMA Kazuhiko , freebsd-current@freebsd.org Message-ID: Subject: Re: ZFS i/o error in recent 12.0 References: <201803192300.w2JN04fx007127@kx.openedu.org> In-Reply-To: <201803192300.w2JN04fx007127@kx.openedu.org> --L9RDf21KmKJBz1ri2GYLixyraeFX3VorL Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2018-03-19 19:00, KIRIYAMA Kazuhiko wrote: > Hi, >=20 > I've been encountered suddenly death in ZFS full volume > machine(r330434) about 10 days after installation[1]: >=20 > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot >=20 > FreeBSD/x86 boot > ZFS: i/o error - all block copies unavailable > ZFS: can't find dataset u > Default: zroot/<0x0>: > boot:=20 >=20 > Partition is bellow: >=20 > # gpart show /dev/mfid0 > =3D> 40 31247564720 mfid0 GPT (15T) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 984 - free - (492K) > 411648 268435456 3 freebsd-swap (128G) > 268847104 30978715648 4 freebsd-zfs (14T) > 31247562752 2008 - free - (1.0M) >=20 > #=20 >=20 > But nothing had beed happend in old current ZFS full volume > machine(r327038M). According to [2] the reason is boot/zfs/zpool.cache > inconsistent. I've tried to cope with this by repairing > /boot [3] from rescue bootable USB as follows: >=20 > # kldload zfs > # zpool import=20 > pool: zroot > id: 17762298124265859537 > state: ONLINE > action: The pool can be imported using its name or numeric identifier.= > config: >=20 > zroot ONLINE > mfid0p4 ONLINE > # zpool import -fR /mnt zroot > # df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/da0p2 14G 1.6G 11G 13% / > devfs 1.0K 1.0K 0B 100% /dev > zroot/.dake 14T 18M 14T 0% /mnt/.dake > zroot/ds 14T 96K 14T 0% /mnt/ds > zroot/ds/backup 14T 88K 14T 0% /mnt/ds/back= up > zroot/ds/backup/kazu.pis 14T 31G 14T 0% /mnt/ds/back= up/kazu.pis > zroot/ds/distfiles 14T 7.9M 14T 0% /mnt/ds/dist= files > zroot/ds/obj 14T 10G 14T 0% /mnt/ds/obj > zroot/ds/packages 14T 4.0M 14T 0% /mnt/ds/pack= ages > zroot/ds/ports 14T 1.3G 14T 0% /mnt/ds/port= s > zroot/ds/src 14T 2.6G 14T 0% /mnt/ds/src > zroot/tmp 14T 88K 14T 0% /mnt/tmp > zroot/usr/home 14T 136K 14T 0% /mnt/usr/hom= e > zroot/usr/local 14T 10M 14T 0% /mnt/usr/loc= al > zroot/var/audit 14T 88K 14T 0% /mnt/var/aud= it > zroot/var/crash 14T 88K 14T 0% /mnt/var/cra= sh > zroot/var/log 14T 388K 14T 0% /mnt/var/log= > zroot/var/mail 14T 92K 14T 0% /mnt/var/mai= l > zroot/var/ports 14T 11M 14T 0% /mnt/var/por= ts > zroot/var/tmp 14T 6.0M 14T 0% /mnt/var/tmp= > zroot/vm 14T 2.8G 14T 0% /mnt/vm > zroot/vm/tbedfc 14T 1.6G 14T 0% /mnt/vm/tbed= fc > zroot 14T 88K 14T 0% /mnt/zroot > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > zroot 51.1G 13.9T 88K /mnt/zroot > zroot/.dake 18.3M 13.9T 18.3M /mnt/.dake > zroot/ROOT 1.71G 13.9T 88K none > zroot/ROOT/default 1.71G 13.9T 1.71G /mnt/mnt > zroot/ds 45.0G 13.9T 96K /mnt/ds > zroot/ds/backup 30.8G 13.9T 88K /mnt/ds/backup > zroot/ds/backup/kazu.pis 30.8G 13.9T 30.8G /mnt/ds/backup/kazu.pis > zroot/ds/distfiles 7.88M 13.9T 7.88M /mnt/ds/distfiles > zroot/ds/obj 10.4G 13.9T 10.4G /mnt/ds/obj > zroot/ds/packages 4.02M 13.9T 4.02M /mnt/ds/packages > zroot/ds/ports 1.26G 13.9T 1.26G /mnt/ds/ports > zroot/ds/src 2.56G 13.9T 2.56G /mnt/ds/src > zroot/tmp 88K 13.9T 88K /mnt/tmp > zroot/usr 10.4M 13.9T 88K /mnt/usr > zroot/usr/home 136K 13.9T 136K /mnt/usr/home > zroot/usr/local 10.2M 13.9T 10.2M /mnt/usr/local > zroot/var 17.4M 13.9T 88K /mnt/var > zroot/var/audit 88K 13.9T 88K /mnt/var/audit > zroot/var/crash 88K 13.9T 88K /mnt/var/crash > zroot/var/log 388K 13.9T 388K /mnt/var/log > zroot/var/mail 92K 13.9T 92K /mnt/var/mail > zroot/var/ports 10.7M 13.9T 10.7M /mnt/var/ports > zroot/var/tmp 5.98M 13.9T 5.98M /mnt/var/tmp > zroot/vm 4.33G 13.9T 2.75G /mnt/vm > zroot/vm/tbedfc 1.58G 13.9T 1.58G /mnt/vm/tbedfc > # zfs mount zroot/ROOT/default > # cd /mnt/mnt/ > # mv boot boot.bak > # cp -RPp boot.bak boot > # gpart show /dev/mfid0 > =3D> 40 31247564720 mfid0 GPT (15T) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 984 - free - (492K) > 411648 268435456 3 freebsd-swap (128G) > 268847104 30978715648 4 freebsd-zfs (14T) > 31247562752 2008 - free - (1.0M) >=20 > # gpart bootcode -b /mnt/mnt/boot/pmbr -p /boot/gptzfsboot -i 2 mfid0 > partcode written to mfid0p2 > bootcode written to mfid0 > # cd > # zpool export zroot > #=20 >=20 > But can not boot: >=20 > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot >=20 > FreeBSD/x86 boot >=20 > Any idea? >=20 > Best regards >=20 > [1] http://ds.truefc.org/~kiri/freebsd/current/zfs/messages > [2] https://lists.freebsd.org/pipermail/freebsd-questions/2016-February= /270505.html > [3] https://forums.freebsd.org/threads/zfs-i-o-error-all-block-copies-u= navailable-invalid-format.55227/#post-312830 >=20 > --- > KIRIYAMA Kazuhiko > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 Since you were about to 'zpool import' on the USB stick, this suggests the problem is with the boot blocks, not ZFS. The early boot phase (gptzfsboot) does not read zpool.cache, since that only lives ON the pool, and the pool has not been imported yet. Maybe kevans@ or imp@ who have been working on the boot code have some insight. --=20 Allan Jude --L9RDf21KmKJBz1ri2GYLixyraeFX3VorL-- --zenOVxIYLQXM9LPpOVLPmpwA7MS5LlRSN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJasEMsAAoJEBmVNT4SmAt+dAAQAKgSdxlJ/Dg1bT79SmWUHDhJ D0Yfsqwd83n80cwEAzZF2ZbQGGSbrDWYYcbfgWJaaOnsh7Tbq5WopLQtigE0N8D+ uANF2ERkPM9/Lgy8acYUYrE5GnAxYQvxaPbxBIvoyxXDMpUlSobQAuhPoikvyCHb J7cww/gYaCbJDFi7GH8Hwrf1mdBVPeHmDjTDOEqhFo2aSFbg9So1krWcwtNTOLQ1 D8ISm54V4Lurw9UY2f84du9HHabvKEi/FoHeOU/J3dPJavzEAIS6+G7eZ2vhTdUC Y6VTXp2TWpYtQc6I3Zfj/pOY0dkWfLlfBLRNFVA8+YH1522saCmhXCyAJmtyD6fR IL2MV11TY/UT6aduAHQrqakrGbzst7WLt6V15vzPTRcvWVr5/f6vmE2SdfKfe6ht nr0DNS+kJuvAKBahxPj/N4tl2F+sZV429i2kkZQa44HcLUaywx7JiGRSjn2Gghcd zDiI6/ytFvY/pbofs3TaUbY+gmMlznESckrADundiQ9oTu+qzlDyKbEUzn6zOSyP RlXdjBZjSVpvTP+h8iiiokPpOtAz6RgTbvyrAYlDq0BROfu05M1LCmLmJ84w8HFt kohC5IrYfzCjMle0xCh1uZuXYi2spZEooKNTwaQ+b0sPu86dVn0cqIRjuJWKX0bn u5ykKcfS7tBJakXe8+Vv =OM4I -----END PGP SIGNATURE----- --zenOVxIYLQXM9LPpOVLPmpwA7MS5LlRSN-- From owner-freebsd-current@freebsd.org Tue Mar 20 07:08:09 2018 Return-Path: Delivered-To: freebsd-current@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 9C0CBF5829F for ; Tue, 20 Mar 2018 07:08:09 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D13AD835EC for ; Tue, 20 Mar 2018 07:08:08 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w2K77slj027190 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=OK); Tue, 20 Mar 2018 18:08:03 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w2K77jsD012891 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO); Tue, 20 Mar 2018 18:07:46 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w2K77jRo012890; Tue, 20 Mar 2018 18:07:45 +1100 (AEDT) (envelope-from peter) Date: Tue, 20 Mar 2018 18:07:45 +1100 From: Peter Jeremy To: Jeff Roberson Cc: FreeBSD current Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180320070745.GA12880@server.rulingia.com> References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=x-unknown; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 07:08:09 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Mar-11 10:43:58 -1000, Jeff Roberson wrot= e: >Also, if you could try going back to r328953 or r326346 and let me know if= =20 >the problem exists in either. That would be very helpful. If anyone is= =20 >willing to debug this with me contact me directly and I will send some=20 >test patches or debugging info after you have done the above steps. I ran into this on 11-stable and tracked it to r326619 (MFC of r325851). I initially got around the problem by reverting that commit but either it or something very similar is still present in 11-stable r331053. I've seen it in my main server (32GB RAM) but haven't managed to reproduce it in smaller VBox guests - one difficulty I faced was artificially filling ARC. --=20 Peter Jeremy --jI8keyz6grp/JLjh Content-Type: application/pgp-signature; name="signature.asc" /usr/local/bin/gpg --no-verbose --batch --output - --passphrase-fd 0 --pinentry-mode loopback --armor --detach-sign --textmode -u 0x1D9214A2699F8CB2 /tmp/mutt-server-acr62wLd --jI8keyz6grp/JLjh-- From owner-freebsd-current@freebsd.org Tue Mar 20 07:09:52 2018 Return-Path: Delivered-To: freebsd-current@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 71BA1F584D4 for ; Tue, 20 Mar 2018 07:09:52 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EEAAC83780 for ; Tue, 20 Mar 2018 07:09:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w2K79UYI035603 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 20 Mar 2018 08:09:31 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w2K79UU1035600; Tue, 20 Mar 2018 08:09:30 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 20 Mar 2018 08:09:29 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: KIRIYAMA Kazuhiko cc: freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 In-Reply-To: <201803192300.w2JN04fx007127@kx.openedu.org> Message-ID: References: <201803192300.w2JN04fx007127@kx.openedu.org> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 07:09:52 -0000 On Tue, 20 Mar 2018 08:00+0900, KIRIYAMA Kazuhiko wrote: > Hi, > > I've been encountered suddenly death in ZFS full volume > machine(r330434) about 10 days after installation[1]: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > FreeBSD/x86 boot > ZFS: i/o error - all block copies unavailable > ZFS: can't find dataset u > Default: zroot/<0x0>: > boot: > > Partition is bellow: > > # gpart show /dev/mfid0 > => 40 31247564720 mfid0 GPT (15T) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 984 - free - (492K) > 411648 268435456 3 freebsd-swap (128G) > 268847104 30978715648 4 freebsd-zfs (14T) > 31247562752 2008 - free - (1.0M) > > # > > But nothing had beed happend in old current ZFS full volume > machine(r327038M). According to [2] the reason is boot/zfs/zpool.cache > inconsistent. I've tried to cope with this by repairing > /boot [3] from rescue bootable USB as follows: > > # kldload zfs > # zpool import > pool: zroot > id: 17762298124265859537 > state: ONLINE > action: The pool can be imported using its name or numeric identifier. > config: > > zroot ONLINE > mfid0p4 ONLINE > # zpool import -fR /mnt zroot > # df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/da0p2 14G 1.6G 11G 13% / > devfs 1.0K 1.0K 0B 100% /dev > zroot/.dake 14T 18M 14T 0% /mnt/.dake > zroot/ds 14T 96K 14T 0% /mnt/ds > zroot/ds/backup 14T 88K 14T 0% /mnt/ds/backup > zroot/ds/backup/kazu.pis 14T 31G 14T 0% /mnt/ds/backup/kazu.pis > zroot/ds/distfiles 14T 7.9M 14T 0% /mnt/ds/distfiles > zroot/ds/obj 14T 10G 14T 0% /mnt/ds/obj > zroot/ds/packages 14T 4.0M 14T 0% /mnt/ds/packages > zroot/ds/ports 14T 1.3G 14T 0% /mnt/ds/ports > zroot/ds/src 14T 2.6G 14T 0% /mnt/ds/src > zroot/tmp 14T 88K 14T 0% /mnt/tmp > zroot/usr/home 14T 136K 14T 0% /mnt/usr/home > zroot/usr/local 14T 10M 14T 0% /mnt/usr/local > zroot/var/audit 14T 88K 14T 0% /mnt/var/audit > zroot/var/crash 14T 88K 14T 0% /mnt/var/crash > zroot/var/log 14T 388K 14T 0% /mnt/var/log > zroot/var/mail 14T 92K 14T 0% /mnt/var/mail > zroot/var/ports 14T 11M 14T 0% /mnt/var/ports > zroot/var/tmp 14T 6.0M 14T 0% /mnt/var/tmp > zroot/vm 14T 2.8G 14T 0% /mnt/vm > zroot/vm/tbedfc 14T 1.6G 14T 0% /mnt/vm/tbedfc > zroot 14T 88K 14T 0% /mnt/zroot > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > zroot 51.1G 13.9T 88K /mnt/zroot > zroot/.dake 18.3M 13.9T 18.3M /mnt/.dake > zroot/ROOT 1.71G 13.9T 88K none > zroot/ROOT/default 1.71G 13.9T 1.71G /mnt/mnt > zroot/ds 45.0G 13.9T 96K /mnt/ds > zroot/ds/backup 30.8G 13.9T 88K /mnt/ds/backup > zroot/ds/backup/kazu.pis 30.8G 13.9T 30.8G /mnt/ds/backup/kazu.pis > zroot/ds/distfiles 7.88M 13.9T 7.88M /mnt/ds/distfiles > zroot/ds/obj 10.4G 13.9T 10.4G /mnt/ds/obj > zroot/ds/packages 4.02M 13.9T 4.02M /mnt/ds/packages > zroot/ds/ports 1.26G 13.9T 1.26G /mnt/ds/ports > zroot/ds/src 2.56G 13.9T 2.56G /mnt/ds/src > zroot/tmp 88K 13.9T 88K /mnt/tmp > zroot/usr 10.4M 13.9T 88K /mnt/usr > zroot/usr/home 136K 13.9T 136K /mnt/usr/home > zroot/usr/local 10.2M 13.9T 10.2M /mnt/usr/local > zroot/var 17.4M 13.9T 88K /mnt/var > zroot/var/audit 88K 13.9T 88K /mnt/var/audit > zroot/var/crash 88K 13.9T 88K /mnt/var/crash > zroot/var/log 388K 13.9T 388K /mnt/var/log > zroot/var/mail 92K 13.9T 92K /mnt/var/mail > zroot/var/ports 10.7M 13.9T 10.7M /mnt/var/ports > zroot/var/tmp 5.98M 13.9T 5.98M /mnt/var/tmp > zroot/vm 4.33G 13.9T 2.75G /mnt/vm > zroot/vm/tbedfc 1.58G 13.9T 1.58G /mnt/vm/tbedfc > # zfs mount zroot/ROOT/default > # cd /mnt/mnt/ > # mv boot boot.bak > # cp -RPp boot.bak boot > # gpart show /dev/mfid0 > => 40 31247564720 mfid0 GPT (15T) > 40 409600 1 efi (200M) > 409640 1024 2 freebsd-boot (512K) > 410664 984 - free - (492K) > 411648 268435456 3 freebsd-swap (128G) > 268847104 30978715648 4 freebsd-zfs (14T) > 31247562752 2008 - free - (1.0M) > > # gpart bootcode -b /mnt/mnt/boot/pmbr -p /boot/gptzfsboot -i 2 mfid0 > partcode written to mfid0p2 > bootcode written to mfid0 > # cd > # zpool export zroot This step has been big no-no in the past. Never leave your bootpool/rootpool in an exported state if you intend to boot from it. For all I know, this advice might be superstition for the present versions of FreeBSD. >From what I can tell from the above, you never created a new zpool.cache and copied it to its rightful place. If you suspect your zpool.cache is out of date, then this should do the trick: zpool import -o cachefile=/tmp/zpool.cache -fR /mnt zroot If you have additional pools, you may want to treat them the same way. cp -p /tmp/zpool.cache /mnt/mnt/boot/zfs/zpool.cache reboot > # > > But can not boot: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > FreeBSD/x86 boot > > Any idea? > > Best regards > > [1] http://ds.truefc.org/~kiri/freebsd/current/zfs/messages > [2] https://lists.freebsd.org/pipermail/freebsd-questions/2016-February/270505.html > [3] https://forums.freebsd.org/threads/zfs-i-o-error-all-block-copies-unavailable-invalid-format.55227/#post-312830 -- Trond. From owner-freebsd-current@freebsd.org Tue Mar 20 08:02:05 2018 Return-Path: Delivered-To: freebsd-current@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 A9FAFF5B947 for ; Tue, 20 Mar 2018 08:02:05 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mail.dudes.ch (mail.dudes.ch [193.73.211.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.dudes.ch", Issuer "StartCom Class 3 OV Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D7E885C4D for ; Tue, 20 Mar 2018 08:02:04 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mwoffice.virtualtec.office (pippin.virtualtec.ch [93.189.66.120]) (authenticated bits=0) by mail.dudes.ch (8.15.2/8.15.2) with ESMTPSA id w2K8oP1H039330 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 20 Mar 2018 09:50:25 +0100 (CET) (envelope-from fbsd-lists@dudes.ch) X-Authentication-Warning: mail.dudes.ch: Host pippin.virtualtec.ch [93.189.66.120] claimed to be mwoffice.virtualtec.office Date: Tue, 20 Mar 2018 08:50:28 +0100 From: Markus Wild To: freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 Message-ID: <20180320085028.0b15ff40@mwoffice.virtualtec.office> In-Reply-To: <201803192300.w2JN04fx007127@kx.openedu.org> References: <201803192300.w2JN04fx007127@kx.openedu.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 193.73.211.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 08:02:05 -0000 Hi there, > I've been encountered suddenly death in ZFS full volume > machine(r330434) about 10 days after installation[1]: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > 268847104 30978715648 4 freebsd-zfs (14T) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I had faced the exact same issue on a HP Microserver G8 with 8TB disks and a 16TB zpool on FreeBSD 11 about a year ago. My conclusion was, that over time (and updating the kernel), the blocks for that kernel file were reallocated to a later spot on the disks, and that however the loader fetches those blocks, it now failed doing so (perhaps a 2/4TB limit/bug with the BIOS of that server? Unfortunately, there was no UEFI support for it, don't know whether that changed in the meantime). The pool was always importable fine with the USB stick, the problem was only with the boot loader. I worked around the problem stealing space from the swap partitions on two disks to build a "zboot" pool, just containing the /boot directory, having the boot loader load the kernel from there, and then still mount the real root pool to run the system off using loader-variables in loader.conf of the boot pool. It's a hack, but it's working fine since (the server is being used as a backup repository). This is what I have in the "zboot" boot/loader.conf: # zfs boot kludge due to buggy bios vfs.root.mountfrom="zfs:zroot/ROOT/fbsd11" If you're facing the same problem, you might give this a shot? You seem to have plenty of swap to canibalize as well;) Cheers, Markus From owner-freebsd-current@freebsd.org Tue Mar 20 08:21:02 2018 Return-Path: Delivered-To: freebsd-current@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 8D90FF5D0F3 for ; Tue, 20 Mar 2018 08:21:02 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 375028686F for ; Tue, 20 Mar 2018 08:21:02 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P5V00K00QXN1Q00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Tue, 20 Mar 2018 08:20:59 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1521534059; bh=j9sSfNc1277Ik8vm+e0c/HnxsvB5e6K9RUfuZZ37Re0=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=LuB3LXLoJSzMFNe0NNRf5nYkyJ79/TrBt6iFxneBcI5WG6ZKuD4C7wdyUJMDrPs00 VcTHdS7BJbGLFluSI5Of5rqBfxG67bank/Zu0Wjk+FuMCdbtumlroDXE67J3As5Uo+ MLnav+oX7hcBBSb6vkSLP0F2hE9sH45fIVV3rhDdx6zYIrAOM+U9WK/G2VObpA4sMk 65v9Cto9BTuH4tLxxNIvFFKG4qxWTVq5GPES8dTvHowhV/DSOEr8quCSQyvv2u++IJ /DezYgf1LmbI6lYJir9JytQRbzNHr6IPCTvR/N4dOlnagonGInM2o65UumrJ1BLynL Bx8M921sIG2dw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P5V00FUNR6W6D20@st13p35im-asmtp002.me.com>; Tue, 20 Mar 2018 08:20:58 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-20_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1803200100 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: ZFS i/o error in recent 12.0 From: Toomas Soome In-reply-to: <20180320085028.0b15ff40@mwoffice.virtualtec.office> Date: Tue, 20 Mar 2018 10:21:02 +0200 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <6680868D-F08A-4AF4-B68D-7E20ADBA67D4@me.com> References: <201803192300.w2JN04fx007127@kx.openedu.org> <20180320085028.0b15ff40@mwoffice.virtualtec.office> To: Markus Wild X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 08:21:02 -0000 > On 20 Mar 2018, at 09:50, Markus Wild wrote: >=20 > Hi there, >=20 >> I've been encountered suddenly death in ZFS full volume >> machine(r330434) about 10 days after installation[1]: >>=20 >> ZFS: i/o error - all block copies unavailable >> ZFS: can't read MOS of pool zroot >> gptzfsboot: failed to mount default pool zroot >>=20 >=20 >> 268847104 30978715648 4 freebsd-zfs (14T) >=20 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >=20 >=20 > I had faced the exact same issue on a HP Microserver G8 with 8TB disks = and a 16TB zpool on FreeBSD 11 about a year ago. > My conclusion was, that over time (and updating the kernel), the = blocks for that kernel file were reallocated to a > later spot on the disks, and that however the loader fetches those = blocks, it now failed doing so (perhaps a 2/4TB > limit/bug with the BIOS of that server? Unfortunately, there was no = UEFI support for it, don't know whether that > changed in the meantime). The pool was always importable fine with the = USB stick, the problem was only with the boot > loader. I worked around the problem stealing space from the swap = partitions on two disks to build a "zboot" pool, just > containing the /boot directory, having the boot loader load the kernel = from there, and then still mount the real root > pool to run the system off using loader-variables in loader.conf of = the boot pool. It's a hack, but it's working > fine since (the server is being used as a backup repository). This is = what I have in the "zboot" boot/loader.conf: >=20 > # zfs boot kludge due to buggy bios > vfs.root.mountfrom=3D"zfs:zroot/ROOT/fbsd11" >=20 >=20 > If you're facing the same problem, you might give this a shot? You = seem to have plenty of swap to canibalize as well;) >=20 please check with lsdev -v from loader OK prompt - do the reported = disk/partition sizes make sense. Another thing is, even if you do update = the current build, you want to make sure your installed boot blocks are = updated as well - otherwise you will have new binary in the /boot = directory, but it is not installed on boot block area=E2=80=A6 rgds, toomas From owner-freebsd-current@freebsd.org Tue Mar 20 14:29:53 2018 Return-Path: Delivered-To: freebsd-current@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 067D4F51EAC for ; Tue, 20 Mar 2018 14:29:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (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 69D7D7551A for ; Tue, 20 Mar 2018 14:29:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id l191-v6so2882611lfe.1 for ; Tue, 20 Mar 2018 07:29:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IoNNl3s6QCfBH3v2IgN8jozzPoajNZUgenZ/YgK5qQk=; b=c8k0OlZgQJKlCpgx26SfjmUv6aOv4gblSTLciuNBHCm/wCncqu8QgH1QSPCGwcs1wi Pfxx/LAVCtG3Gx3pamVp2lGF0wE/JZykbt3pd6oXDhXtHSqqICeh+suBGFTgy8n1D5Fu oDJW2FOi/8hwoIMtnZi+UFPxZt11OfrZVZmW1ZpWE5whHjCF7ZjLZpdpHswdifvIcppQ q5fbQVbGwqB/RwsgRyF5Pt4tIfWkzTes0UDi7zv53eGkmaVTRdGZAtCOSG0M51VDtk2h fCdgzbkr6bXo2abFevPq4VRZr8gdCgDYzOqEuZJaOZMsRpK+/aWoVrPAlU68L32QYHlV 2Tgg== X-Gm-Message-State: AElRT7F5aTZyhjkNBimN+eN2h+IT0hPWCf2Xzags85LgOnG3L3806yMQ WOa920phWkAkaJ0z2EQ/RWODiwoFRfg= X-Google-Smtp-Source: AG47ELvOMplY2rO3wshDi0Pyo74K92DEXjFEskkoYm+hP4sF+sQbQ+ajf763nGRFx4mreJYw2YNeWQ== X-Received: by 10.46.124.8 with SMTP id x8mr10552349ljc.121.1521556184913; Tue, 20 Mar 2018 07:29:44 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id l78-v6sm472818lfi.36.2018.03.20.07.29.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 07:29:44 -0700 (PDT) Subject: Re: ZFS i/o error in recent 12.0 To: =?UTF-8?Q?Trond_Endrest=c3=b8l?= , KIRIYAMA Kazuhiko Cc: freebsd-current@freebsd.org References: <201803192300.w2JN04fx007127@kx.openedu.org> From: Andriy Gapon Message-ID: <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org> Date: Tue, 20 Mar 2018 16:29:43 +0200 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-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 14:29:53 -0000 On 20/03/2018 09:09, Trond Endrestøl wrote: > This step has been big no-no in the past. Never leave your > bootpool/rootpool in an exported state if you intend to boot from it. > For all I know, this advice might be superstition for the present > versions of FreeBSD. Yes, it is. That does not matter at all now. > From what I can tell from the above, you never created a new > zpool.cache and copied it to its rightful place. For the _rooot_ pool zpool.cache does not matter as well. It matters only for auto-import of additional pools, if any. -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Mar 20 15:09:52 2018 Return-Path: Delivered-To: freebsd-current@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 6C205F54B72 for ; Tue, 20 Mar 2018 15:09:52 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [IPv6:2a01:4f8:201:2327:144:76:253:226]) (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 F3DD176FCC; Tue, 20 Mar 2018 15:09:51 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from [10.137.3.13] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id 40BFDBD1C3C; Tue, 20 Mar 2018 15:09:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.tyknet.dk 40BFDBD1C3C DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1521558589; bh=7wn5ylN9M+OGmXAiGhX26macWikB6enFtGEyyIRZtJk=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=miVpZxyjc4RS4K46W3hWjA4+rwpLGDf/P/Hfbdd+xjnaSbLeCrJjic1bERq7AJSoO 401D0qUgnVnrPnYfrYA8+LYz3lJFEHuSCU9ZTAiJrG7oneDM5P4UmP2nAurIbIwMD+ xj1xSzt3IB71UuwmubOI5HoXvPz9svRoKci79dLyLSHOnVN1SlE08Ejv33eUPRLBzf RrsLshhIOhnw80wmYN50QlBC1Iu3mej9gaCKArgtjZLRJEiwTyvfglnaFUVYRiS5+E fM+aXjQu7U3X1NiKvWnl8f+wn6+2IFcFffeURbeeiuQrO/sk9Ud+Gq3Vw1oUK/Xep7 RVJ28qLSnRn8g== Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT To: Jeff Roberson Cc: "O. Hartmann" , Roman Bogorodskiy , "Danilo G. Baio" , "Rodney W. Grimes" , Trond Endrest?l , FreeBSD current , Kurt Jaeger References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> From: Thomas Steen Rasmussen Message-ID: Date: Tue, 20 Mar 2018 16:09:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 15:09:52 -0000 On 03/11/2018 09:43 PM, Jeff Roberson wrote: > Also, if you could try going back to r328953 or r326346 and let me > know if the problem exists in either.  That would be very helpful.  If > anyone is willing to debug this with me contact me directly and I will > send some test patches or debugging info after you have done the above > steps. > Hello, I am seeing this issue (high swap, arc not backing down) on two jail/bhyve hosts running 11-STABLE r325275 and r325235 - which sounds like it is earlier than the two patches you mention? The two machines are at 98 and 138 days uptime, and both are currently using more than 90% swap, and I've had to shut down non-critical stuff because I was getting out-of-swap errors. Just wanted to let everyone know, since I haven't seen any revisions as early as r325275 in the "me too" posts here. More information available on request. Best regards, Thomas Steen Rasmussen From owner-freebsd-current@freebsd.org Tue Mar 20 17:10:47 2018 Return-Path: Delivered-To: freebsd-current@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 8397FF5DA3F for ; Tue, 20 Mar 2018 17:10:47 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31AB27CC48 for ; Tue, 20 Mar 2018 17:10:47 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 2684614578 for ; Tue, 20 Mar 2018 17:10:45 +0000 (UTC) Subject: Re: ZFS i/o error in recent 12.0 To: freebsd-current@freebsd.org References: <201803192300.w2JN04fx007127@kx.openedu.org> <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org> From: Allan Jude Message-ID: <67af9c19-0a42-a435-d922-1e5ce23d1d1c@freebsd.org> Date: Tue, 20 Mar 2018 13:10:50 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <888ab314-fb1b-0e08-89d9-0447e7943b76@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 17:10:47 -0000 On 2018-03-20 10:29, Andriy Gapon wrote: > On 20/03/2018 09:09, Trond Endrestøl wrote: >> This step has been big no-no in the past. Never leave your >> bootpool/rootpool in an exported state if you intend to boot from it. >> For all I know, this advice might be superstition for the present >> versions of FreeBSD. > > Yes, it is. That does not matter at all now. > >> From what I can tell from the above, you never created a new >> zpool.cache and copied it to its rightful place. > > For the _rooot_ pool zpool.cache does not matter as well. > It matters only for auto-import of additional pools, if any. > As I mentioned previously, the error reported by the user is before it is even possible to read zpool.cache, so it is definitely not the source of the problem. -- Allan Jude From owner-freebsd-current@freebsd.org Wed Mar 21 07:01:34 2018 Return-Path: Delivered-To: freebsd-current@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 62148F4DE80 for ; Wed, 21 Mar 2018 07:01:34 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [IPv6:2a01:4f8:201:2327:144:76:253:226]) (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 F010E7FB52 for ; Wed, 21 Mar 2018 07:01:33 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from [10.137.3.13] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id 39E03BD7AC7; Wed, 21 Mar 2018 07:01:25 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.tyknet.dk 39E03BD7AC7 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1521615685; bh=/p9zlM4IuX6tjxGovWKyCi4lTVQHohUzcEGpse+h8I4=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=CiI4kn03xIs4WSo9C6Nje6WdXJJKtZrWW1TiXsxocK9fsrnkdNfOYKtqiyk9bUYC+ l5ipDj3vyXMaNyZYLzuaGAnG+QMhIdovnXjZrvgJDnYLh57bZDFfoLoqMHAw/Wtyx4 ZTXbRUMVqaPUgCwsUsy6rl1Oo1Z6tmZlOeZFpeN6+l/cNcBZuZv5LG0u0dDsdZjG8L 3Q7mUre9ET1ztqUflka3jJ5XrbOSC5qvY2x06bNFrbvhv+ljDtNopy3pAWHXJYmp46 4y8BRH9xyuQwizjX6aaBg2l7HnaH3kkV6t6WeuJofF67oU2DFaK+JJRL/C38AbKVAB ulTTWZ4tr7IqA== Subject: Re: ZFS i/o error in recent 12.0 To: KIRIYAMA Kazuhiko References: <201803192300.w2JN04fx007127@kx.openedu.org> Cc: freebsd-current@freebsd.org From: Thomas Steen Rasmussen Message-ID: <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> Date: Wed, 21 Mar 2018 08:01:24 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <201803192300.w2JN04fx007127@kx.openedu.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 07:01:34 -0000 On 03/20/2018 12:00 AM, KIRIYAMA Kazuhiko wrote: > Hi, > > I've been encountered suddenly death in ZFS full volume > machine(r330434) about 10 days after installation[1]: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > FreeBSD/x86 boot > ZFS: i/o error - all block copies unavailable > ZFS: can't find dataset u > Default: zroot/<0x0>: > boot: Has this pool had new vdevs addded to it since the server was installed? What does a "zpool status" look like when the pool is imported? /Thomas From owner-freebsd-current@freebsd.org Wed Mar 21 07:20:44 2018 Return-Path: Delivered-To: freebsd-current@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 B3128F4EF93 for ; Wed, 21 Mar 2018 07:20:44 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [IPv6:2a01:4f8:201:2327:144:76:253:226]) (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 4B97A80652 for ; Wed, 21 Mar 2018 07:20:44 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from [10.137.3.13] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id E7770BD7AFD; Wed, 21 Mar 2018 07:20:42 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.tyknet.dk E7770BD7AFD DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1521616843; bh=STSMwvrCYZDLryF7bHWTDjWkYYeXxAB98Fo0eYBykYs=; h=Subject:To:References:From:Date:In-Reply-To; b=q4aBe52bFsKv4f8166xxfwgYfv8HIeJNi7B0OWOH5FiXyEOLDgEwwJL8X+wLS54zU fYiY21EJD98RsI/7JQLyRHBJhyVutRk3USJV44/gY4c5v7AZ8YaOqiRfEytbpovWUr vmhx9z1i1nqNt/nlEa4uspA2l2hjgLYnVTX1xO6BCsHkJzaqJrj8/bjor1SrHmX3N2 eIhPsrL68cLWsuKKUrHqLeIAssfsjqiakUU2ZIM1XlP9872a6IZ9o+HnJKw0Kyo0rY lAAoQO6owVHR07Y/sXsOO0lVYwb9MyY2L/LbMDDURipFjfessLBWUCpOnyYqGjzKed 9kXNtVB4cgp/Q== Subject: Re: ZFS i/o error in recent 12.0 To: Markus Wild , freebsd-current@freebsd.org References: <201803192300.w2JN04fx007127@kx.openedu.org> <20180320085028.0b15ff40@mwoffice.virtualtec.office> From: Thomas Steen Rasmussen Message-ID: Date: Wed, 21 Mar 2018 08:20:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180320085028.0b15ff40@mwoffice.virtualtec.office> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 07:20:44 -0000 On 03/20/2018 08:50 AM, Markus Wild wrote: > > I had faced the exact same issue on a HP Microserver G8 with 8TB disks and a 16TB zpool on FreeBSD 11 about a year ago. Hello, I will ask you the same question as I asked the OP: Has this pool had new vdevs addded to it since the server was installed? What does a "zpool status" look like when the pool is imported? Explanation: Some controllers only make a small fixed number of devices visible to the bios during boot. Imagine a zpool was booted with, say, 4 disks in a pool, and 4 more was added. If the HBA only shows 4 drives to the bios during boot, you see this error. If you think this might be relevant you need to chase down a setting called "maximum int13 devices for this adapter" or something like that. See page 3-4 in this documentation: https://supermicro.com/manuals/other/LSI_HostRAID_2308.pdf The setting has been set to 4 on a bunch of servers I've bought over the last years. Then you install the server with 4 disks, later add new disks, reboot one day and nothing works until you set it high enough that the bootloader can see the whole pool, and you're good again. /Thomas From owner-freebsd-current@freebsd.org Wed Mar 21 09:29:01 2018 Return-Path: Delivered-To: freebsd-current@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 50C77F57685 for ; Wed, 21 Mar 2018 09:29:01 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mail.dudes.ch (mail.dudes.ch [193.73.211.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.dudes.ch", Issuer "StartCom Class 3 OV Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D52B58578D for ; Wed, 21 Mar 2018 09:29:00 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mwoffice.virtualtec.office (pippin.virtualtec.ch [93.189.66.120]) (authenticated bits=0) by mail.dudes.ch (8.15.2/8.15.2) with ESMTPSA id w2LASjvY047816 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 21 Mar 2018 11:28:45 +0100 (CET) (envelope-from fbsd-lists@dudes.ch) X-Authentication-Warning: mail.dudes.ch: Host pippin.virtualtec.ch [93.189.66.120] claimed to be mwoffice.virtualtec.office Date: Wed, 21 Mar 2018 10:28:48 +0100 From: Markus Wild To: freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 Message-ID: <20180321102848.20a9f48a@mwoffice.virtualtec.office> In-Reply-To: References: <201803192300.w2JN04fx007127@kx.openedu.org> <20180320085028.0b15ff40@mwoffice.virtualtec.office> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 193.73.211.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 09:29:01 -0000 Hello Thomas, > > I had faced the exact same issue on a HP Microserver G8 with 8TB disks and a 16TB zpool on FreeBSD 11 about a year > > ago. > I will ask you the same question as I asked the OP: > > Has this pool had new vdevs addded to it since the server was installed? No. This is a microserver with only 4 (not even hotplug) trays. It was set up using the freebsd installer originally. I had to apply the (then patch, don't know whether it's included standard now) btx loader fix to retry a failed read to get around BIOS bugs with that server, but after that, the server booted fine. It's only after a bit of use and a kernel update that things went south. I tried many different things at that time, but the only approach that worked for me was to steal 2 of the 4 swap partitions which I placed on every disk initially, and build a mirrored boot zpool from those. The loader had no problem loading the kernel from that, and when the kernel took over, it had no problem using the original root pool (that the boot loader wasn't able to find/load). Whence my conclusion that the 2nd stage boot loader has a problem (probably due to yet another bios bug on that server) loading blocks beyond a certain limit, which could be 2TB or 4TB. > What does a "zpool status" look like when the pool is imported? $ zpool status pool: zboot state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Wed Mar 21 03:58:36 2018 config: NAME STATE READ WRITE CKSUM zboot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/zfs-boot0 ONLINE 0 0 0 gpt/zfs-boot1 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scan: scrub repaired 0 in 6h49m with 0 errors on Sat Mar 10 10:17:49 2018 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/zfs0 ONLINE 0 0 0 gpt/zfs1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gpt/zfs2 ONLINE 0 0 0 gpt/zfs3 ONLINE 0 0 0 errors: No known data errors Please note: this server is in use at a customer now, it's workin fine with this workaround. I just brought it up to give a possible explanation to the observed problem of the original poster, and that it _might_ have nothing to do with a newer version of the current kernel, but rather be due to the updated kernel being written to a new location on disk, which can't be read properly by the boot loader. Cheers, Markus From owner-freebsd-current@freebsd.org Wed Mar 21 11:07:27 2018 Return-Path: Delivered-To: freebsd-current@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 94A13F5DE2D for ; Wed, 21 Mar 2018 11:07:27 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA31169844 for ; Wed, 21 Mar 2018 11:07:26 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MPZuP-1euSrG1D7p-004g4J for ; Wed, 21 Mar 2018 12:07:19 +0100 Date: Wed, 21 Mar 2018 12:07:18 +0100 From: "Hartmann, O." To: FreeBSD CURRENT Subject: CURRENT r331284: crashing with USB Message-ID: <20180321120710.4eb3b944@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:3ILziKMAbP7VXUcM83yjF1DyZQ7DqFX8SQYelKc1QuxWaJYRmIB c9+sT1ReT5CfllLZbJLgDh9kH8Kw8necNeV6iXzAIeNTSW05GEsoLMMpdoeoPzyEV34VRuU lpqNUHh5BdyZYq9Qfd/wfU3BDs5+erCMmOld5lw2e+K6SMzlL7+Wcl4Cif2TLw6TOLsiyQ1 Maiu4zx4ExL4l1bVzrvsg== X-UI-Out-Filterresults: notjunk:1;V01:K0:OJw0kuR/Vmg=:7QSnL0uPFAOj/qo/vj/ph2 L4LdPZ8/ufnByuz+PLpSnS6P1Xtw0//SXnbQ8zPktXOl/k//8UpXmONHGNLpeEm+2Mfco+JUC vrK+tsQPrOFiSBrykhaT0TNefkQ51VuWLSYt8/vXnUNDlcybSvTXE+L3lkp48nL+Cqjf4fSBT +l+CzKSIl0QbI4e2UzXxThiAuvw/WD8sEejRmCZ+RKsvDqeQDsmlLlCENcZhLsUU9xcz3qFOH 9falYf7bx+YLTmmKI2YmK28F0MXwdn/2bbMpN9+G//oBvbA73IUkRZOHVQijksuuG/ULpoCHG LgS6JsvKjQB9SBdJfgynx4WBclxQer8pb8KkTA4GE6iqMdk6vcv+iSoFHzYnIMsQDdddERehK oVhHDpQ5KZQGWMYU4SdhxidJcY2uK/5uyxGzmX9u6rpmyVRXcf04LgqeVIjseMlIZmw8/hpDR TXNeugEPMihUlT9T28qBcJXDUc+32gmpC8y2pJsJnDsLU5hCAl+j33Q4ztJTTPXKLNYPxadYu 7PnRyyCsL57r7wL2gKiiDqIS3mTVkQ/2KlwufXygvH0bWYdaj2vGNcqvWTmMC7EMuVvFLvJE2 8+wUha4LYY/0yWTxs2b1kKYNapKrmTDcjE1O2n4BvXHXbZZAk/N1sgJD6HV7uKyj/2W1J5ZMd Kq47J+AMLaNWX6TZZFgLYzJ+IqnG2WtPHZ7v3hwNKzFlm3FFCIAe0tjngMkS3+S7LAu3bWrPN I1iUhmclAtHtZfXez6B4tG55SpX2UrPiTdbO9qmu7nG46InwCVAwpO4rB9kVtY6kxbTqwO7lO aJrdrqlfpCFs+bct1SnX5CV5SBMhv2QAjRg+fgR6rx+KD6yM+s= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 11:07:27 -0000 Hello. Incident: CURRENT r331284 can be brought down reliably with an USB flash drive plugged in and out without mounting or doing anything with it. I first recognized the incident with a ZFS on a SanDisk 32GB USB 3.0 flash drive. Plugging the USB flash and typing "zpool import" revealed the very first time I issue this command the existence of the ZFS fielsystem. Usually, I import then this USB drive for maintenance purposes. Now, typing "zpool import" a second time, nothing is shown at all. I see that umass0 has been destroyed - although the USB drive is still plugged in. Pulling the USB flash drive without having actually imported the ZFS makes CURRENT crash and reboot. I tried different USB flash drives, 3.0, 2.0, different boxes running CURRENT, different hardware (Notebooks, Fujitsu workstations, HP servers). It seems that the USB subsystem does have a serious problem - not the ZFS. I can plugin the USB and then unplug it and after two or three times doing this, the box goes down. Does anyone else observe this bug? By the way: all ZFS USB drives I use or all other USB flash drives cause no problem on FreeBSD 11.1-RELENG-p7! Kind regards, Oliver From owner-freebsd-current@freebsd.org Wed Mar 21 11:23:02 2018 Return-Path: Delivered-To: freebsd-current@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 24982F5F133 for ; Wed, 21 Mar 2018 11:23:02 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 BA52A6A3A6 for ; Wed, 21 Mar 2018 11:23:01 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3CA5B260071; Wed, 21 Mar 2018 12:22:59 +0100 (CET) Subject: Re: CURRENT r331284: crashing with USB To: "Hartmann, O." , FreeBSD CURRENT References: <20180321120710.4eb3b944@hermann> From: Hans Petter Selasky Message-ID: <237b6b65-ab80-1193-d91d-11de089b737a@selasky.org> Date: Wed, 21 Mar 2018 12:22:53 +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: <20180321120710.4eb3b944@hermann> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 11:23:02 -0000 On 03/21/18 12:07, Hartmann, O. wrote: > Hello. > > Incident: CURRENT r331284 can be brought down reliably with an USB > flash drive plugged in and out without mounting or doing anything with > it. > > I first recognized the incident with a ZFS on a SanDisk 32GB USB 3.0 > flash drive. Plugging the USB flash and typing "zpool import" revealed > the very first time I issue this command the existence of the ZFS > fielsystem. Usually, I import then this USB drive for maintenance > purposes. Now, typing "zpool import" a second time, nothing is shown at > all. I see that umass0 has been destroyed - although the USB drive is > still plugged in. > > Pulling the USB flash drive without having actually imported the > ZFS makes CURRENT crash and reboot. > > I tried different USB flash drives, 3.0, 2.0, different boxes running > CURRENT, different hardware (Notebooks, Fujitsu workstations, HP > servers). It seems that the USB subsystem does have a serious problem - > not the ZFS. I can plugin the USB and then unplug it and after two or > three times doing this, the box goes down. > > > Does anyone else observe this bug? > > By the way: all ZFS USB drives I use or all other USB flash drives > cause no problem on FreeBSD 11.1-RELENG-p7! > I've seen something similar, but I thought the issue was fixed by: https://reviews.freebsd.org/D14456 --HPS From owner-freebsd-current@freebsd.org Wed Mar 21 12:09:53 2018 Return-Path: Delivered-To: freebsd-current@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 8DEBDF62AC7 for ; Wed, 21 Mar 2018 12:09:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 285C26BEFE for ; Wed, 21 Mar 2018 12:09:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id D6AB0F62ABF; Wed, 21 Mar 2018 12:09:52 +0000 (UTC) Delivered-To: current@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 C40F4F62ABE for ; Wed, 21 Mar 2018 12:09:52 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1258C6BEFD for ; Wed, 21 Mar 2018 12:09:51 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w2LC9gmn045161 for ; Wed, 21 Mar 2018 12:09:42 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w2LC9gYM045160 for current@freebsd.org; Wed, 21 Mar 2018 05:09:42 -0700 (PDT) (envelope-from david) Date: Wed, 21 Mar 2018 05:09:42 -0700 From: David Wolfskill To: current@freebsd.org Subject: "panic: Unholding 5 with cnt = 0" head/amd64 @r331290 Message-ID: <20180321120942.GV1233@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sIvENLKIDbNLrB32" Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 12:09:53 -0000 --sIvENLKIDbNLrB32 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is on my build machine, running a GENERIC kernel. (Laptop is still building lib32 shim libraries as I type). Here's a copy/paste from the serial console: da3: Attempt to query device size failed: NOT READY, Medium not present da3: quirks=3D0x2 da3: Delete methods: GEOM: new disk da1 GEOM: new disk da2 GEOM: new disk da3 (da1:umass-sim0:0:0:1): PREVENT ALLOW MEDIUM REMOVAL not supported. ugen0.4: at usbus0 (dpanic: Unholding 5 with cnt =3D 0 cpuid =3D 3 time =3D 1521633742 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0000491= 3c0 vpanic() at vpanic+0x18d/frame 0xfffffe0000491420 panic() at panic+0x43/frame 0xfffffe0000491480 dadone() at dadone+0x1cc9/frame 0xfffffe00004919e0 xpt_done_process() at xpt_done_process+0x390/frame 0xfffffe0000491a20 xpt_done_td() at xpt_done_td+0xf6/frame 0xfffffe0000491a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000491ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000491ab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- KDB: enter: panic [ thread pid 15 tid 100065 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db>=20 Anything I can/should do to poke at it before trying to capture a dump? Peace, david --=20 David H. Wolfskill david@catwhisker.org An investigator who doesn't make a perp nervous isn't doing his job. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --sIvENLKIDbNLrB32 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGSBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqyS4ZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfJFgf3dA0CxOq0PIt3drB3zAMuYgaF3v6D4WRS5alNZ1Lk9ZF9WCfsRPhuRnd+ /WN7dyOdOcb/xaFhbrFK39MfQUwUvkAxiWM08NRKqEfUdeHnT6ti5XkeGu5TOk5m trD4zXRWeV+drKEBbo6c4XE0TZD1o/4nX5/8B1gLCaY9Z0RqzCy73uvf/nvFkl0E d+kFSRsbou+yTxQ9c/N+fWGl4nUfNp5vSS06gpLZFNTagaSKF+wKXzygyzZZ4Dw6 342A7vguQ5anmreop2SZ+C0RvoBfVUYmtVK2hAWOYHIdyWTK7lKIpnNGewI/cdGf aF3uL8xgThGUClj8qElyBpRnHVdv =GjV5 -----END PGP SIGNATURE----- --sIvENLKIDbNLrB32-- From owner-freebsd-current@freebsd.org Wed Mar 21 12:27:13 2018 Return-Path: Delivered-To: freebsd-current@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 05C03F63E06 for ; Wed, 21 Mar 2018 12:27:13 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 87F336CA69 for ; Wed, 21 Mar 2018 12:27:12 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 45DFBF63E03; Wed, 21 Mar 2018 12:27:12 +0000 (UTC) Delivered-To: current@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 238A6F63E02 for ; Wed, 21 Mar 2018 12:27:12 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94EC46CA66; Wed, 21 Mar 2018 12:27:11 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id e5-v6so7555212lfb.7; Wed, 21 Mar 2018 05:27:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=pfWFTyhCTrQpZ7tuVydCqBJm3B4yOqW00FjWkkHl1EQ=; b=Iz2ARbF2B6QdhJ/JQhMROB9STT9SJA1RTp0QhY/ntkJRtxBK19fLjVFsvpfhqlxqHR FivuWEhDRhqROO08358x6Pt1kwglle1SgQyEgZ3Uz1x0Ro/drPuWAXmQppTHw8fZvRVN B8Lq7ajKBfTU4H0a4yZtnJNli/t6ShxxhwuEK0gedKJPiHjFmbC3XYsaQ/k8HPzJsP1I T19i8wniSXJXAqZUsg0vTBAoL8+IyUF39u+czSkLdAJYTZTQDHwxVd+4/PwParHD8wRg UpG4bQbhdCwx4qCZYrAxB/IEEk33rSsFgOUXTWNz9w3kQ0PzQnSp67QD5q9KFiecHIGt hs4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=pfWFTyhCTrQpZ7tuVydCqBJm3B4yOqW00FjWkkHl1EQ=; b=cB0lpJ/nr34WtZPuDc2LwFyZbH+jqcQEH8FkPJlgv7Wm0ZV0wrCNPWPg3ENCecUVHc 61msJAf0wD0DlB92bRJJOXX+A2qU9i3koXcqXLs3ISTJ4YrlnY0urmHV51LJjG560QNS OJAp6ptc+drSUTGWaWaW5B/BxBla7MhxEuF67xPZXGX6Sc/nwDprDN3Y1CJPMK6AEaZ6 QZ/TbkE3EmD2zflj8yGn2CzjKsPnap9tnxRqHQM28Fdi/7HucMh4d5jjG4fg1SJIsIM4 V5kSRXyP6VFH0lbbPQj8rlsO9+BE+75lYaRJZCTyw/ZqsEZJYfv1lJWBUR+z8iTtxmeA zVzw== X-Gm-Message-State: AElRT7FJNue867HG5RsXa0+hzgc04GvOeXqnN71CZLzfh83e3NlYePhF /CXidX3qjPBdUExPZN7kg9CSpg== X-Google-Smtp-Source: AG47ELuZMzWC8B6cZ2mGowV/UurVz5V1v7uLuqlSoSmFM8hq69rAjzb6sx9Bfl4yBT6c2Kuer1mU2A== X-Received: by 2002:a19:9e95:: with SMTP id h143-v6mr14429980lfe.129.1521635229994; Wed, 21 Mar 2018 05:27:09 -0700 (PDT) Received: from kloomba ([95.104.130.87]) by smtp.gmail.com with ESMTPSA id 31-v6sm1010166lfs.57.2018.03.21.05.27.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 05:27:09 -0700 (PDT) Sender: Roman Bogorodskiy Date: Wed, 21 Mar 2018 16:26:57 +0400 From: Roman Bogorodskiy To: David Wolfskill , current@freebsd.org Cc: imp@FreeBSD.org Subject: Re: "panic: Unholding 5 with cnt = 0" head/amd64 @r331290 Message-ID: <20180321122656.GA40816@kloomba> References: <20180321120942.GV1233@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <20180321120942.GV1233@albert.catwhisker.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 12:27:13 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable David Wolfskill wrote: > This is on my build machine, running a GENERIC kernel. (Laptop is still > building lib32 shim libraries as I type). >=20 > Here's a copy/paste from the serial console: >=20 > da3: Attempt to query device size failed: NOT READY, Medium not present > da3: quirks=3D0x2 > da3: Delete methods: > GEOM: new disk da1 > GEOM: new disk da2 > GEOM: new disk da3 > (da1:umass-sim0:0:0:1): PREVENT ALLOW MEDIUM REMOVAL not supported. > ugen0.4: at usbus0 > (dpanic: Unholding 5 with cnt =3D 0 > cpuid =3D 3 > time =3D 1521633742 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00004= 913c0 > vpanic() at vpanic+0x18d/frame 0xfffffe0000491420 > panic() at panic+0x43/frame 0xfffffe0000491480 > dadone() at dadone+0x1cc9/frame 0xfffffe00004919e0 > xpt_done_process() at xpt_done_process+0x390/frame 0xfffffe0000491a20 > xpt_done_td() at xpt_done_td+0xf6/frame 0xfffffe0000491a70 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000491ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000491ab0 > --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- > KDB: enter: panic > [ thread pid 15 tid 100065 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db>=20 >=20 >=20 > Anything I can/should do to poke at it before trying to capture a dump? Looks like it's related to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226510#c18 > Peace, > david > --=20 > David H. Wolfskill david@catwhisker.org > An investigator who doesn't make a perp nervous isn't doing his job. >=20 > See http://www.catwhisker.org/~david/publickey.gpg for my public key. Roman Bogorodskiy --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJask+QAAoJEMltX/4IwiJqN7EIALGUQqNr8+TO42m7HrrpcJfs 6wQuUddeH1Qnf/yGgc00B9+7sbd7JY0hoFzdbI3HH8gtzGGdfRRjgowYfXvt8GfW 5IOhO6SHQFI9TZMu3xDSF+xjjb7eGDpiMeZPl5zqEpF/reUBAToEyW0yzOD4O7/H ysNMfbREfsrTdCl9nvA+iLPMNBdNZHbMBlU5UEg2eB+h6QcwtaeWR5qNGp5eeeg2 BUISLDjUBIShBE0sj8BwE/BXVkf3HYa07lrtQwKo7Lt+iXukQvnUQzk3kjTYN74x eC4xZG5Mx6eGb1KY++c0O8boOjgW4VTDbiFtHD0EJofxeZL1YxoXiTAaGQNGRFU= =AJV5 -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-current@freebsd.org Wed Mar 21 12:57:35 2018 Return-Path: Delivered-To: freebsd-current@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 4BEF0F65D77 for ; Wed, 21 Mar 2018 12:57:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D44B66E01A for ; Wed, 21 Mar 2018 12:57:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 90E3FF65D76; Wed, 21 Mar 2018 12:57:34 +0000 (UTC) Delivered-To: current@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 6C111F65D75 for ; Wed, 21 Mar 2018 12:57:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1D876E015 for ; Wed, 21 Mar 2018 12:57:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id e98-v6so6630149itd.4 for ; Wed, 21 Mar 2018 05:57:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ooHNbY1B9Z4szNY+S/JnEU1qW+2nNErO5QZ0up0wN+Y=; b=Etqf7bHmhCgEIv4oQt3zJtIk8BazfVERwUq5StFpm2fWSEf/fj0dpVC2NAMek5tNFn SOuPJy74yhZfAX/7lHeWnrQB6nic0GSC79SxnAya7bpWjvYgEXtyCdSN6wXCvumULhZ2 GTWN0rIRakptmKlo5p3TcXxS4J1UU7yAF7Gm8trURO2jCvVd00TR1ccUO28qWnq8RVPc 3mfELbdseyDPkJzzbmDnMBKyfONJ81IY9Bp3fbBNzeQj46fnCw+CwZSrAzuyObAF5Sln EXaIflHx/b1c87yQP7AoZPbHnV4czs8VDyLW61OoqY9KXH25ih8jd383/Gl42QkenyhS tkrA== 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=ooHNbY1B9Z4szNY+S/JnEU1qW+2nNErO5QZ0up0wN+Y=; b=bU3FkCVCJRm+ImoO+uB7NZzG6fHOM7K+MKM5wCVFUTYvGTCKNq6fOCEI8QLirh98cI 3fr8gBKYoyC4waRsDir+Y+frty1FX8PHwy+9a0zWbVOsxnaolyA7dY62Emi/JEnLFvRe ZiSSMcaICFaT5txlwchdWF7T9+W2UVlc5FQLXmHEGKZDifIpw9Vu7Yf6Timpzp9NFw5M txfS02OuFPqQ5ZxBTHtKBLVP52VRt5q0DxteZ5tZ0iiB5QzFTw5HQheguqhiggtFYtBj 2RihxjRHQ4WEU2dIuM0FUFT6hXhCMSxY6kw1tINaSqHWbbnBteP3Qc57F3ZXh5XUQsiW rIVA== X-Gm-Message-State: AElRT7FD7qG584H5DZKin90afsTlqRg01sRoza8PbVIAwh3dfIYtlGqt UzxwAMxt1bbty9Iy943eq3ZuPBhPekWQbsrPZKQzMA== X-Google-Smtp-Source: AG47ELulHA0NmWo0RGT/GGKJSaa4+efhTDh/yKOQZ7uPBOUuzlC1nrK26e75yZI8cAB2EUS72AS7Vao4hwJCzftDksI= X-Received: by 2002:a24:6f04:: with SMTP id x4-v6mr4063228itb.51.1521637052810; Wed, 21 Mar 2018 05:57:32 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 05:57:32 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <20180321122656.GA40816@kloomba> References: <20180321120942.GV1233@albert.catwhisker.org> <20180321122656.GA40816@kloomba> From: Warner Losh Date: Wed, 21 Mar 2018 06:57:32 -0600 X-Google-Sender-Auth: bTpjqP5ltMs7E7wbb3aAAaEIz-M Message-ID: Subject: Re: "panic: Unholding 5 with cnt = 0" head/amd64 @r331290 To: Roman Bogorodskiy Cc: David Wolfskill , FreeBSD Current , Warner Losh Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 12:57:35 -0000 i've reverted r331273. In trying to fix the too many refs problem, I created the too few refs problem. Warner On Wed, Mar 21, 2018 at 6:26 AM, Roman Bogorodskiy wrote: > David Wolfskill wrote: > > > This is on my build machine, running a GENERIC kernel. (Laptop is still > > building lib32 shim libraries as I type). > > > > Here's a copy/paste from the serial console: > > > > da3: Attempt to query device size failed: NOT READY, Medium not present > > da3: quirks=0x2 > > da3: Delete methods: > > GEOM: new disk da1 > > GEOM: new disk da2 > > GEOM: new disk da3 > > (da1:umass-sim0:0:0:1): PREVENT ALLOW MEDIUM REMOVAL not supported. > > ugen0.4: at usbus0 > > (dpanic: Unholding 5 with cnt = 0 > > cpuid = 3 > > time = 1521633742 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00004913c0 > > vpanic() at vpanic+0x18d/frame 0xfffffe0000491420 > > panic() at panic+0x43/frame 0xfffffe0000491480 > > dadone() at dadone+0x1cc9/frame 0xfffffe00004919e0 > > xpt_done_process() at xpt_done_process+0x390/frame 0xfffffe0000491a20 > > xpt_done_td() at xpt_done_td+0xf6/frame 0xfffffe0000491a70 > > fork_exit() at fork_exit+0x84/frame 0xfffffe0000491ab0 > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000491ab0 > > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > KDB: enter: panic > > [ thread pid 15 tid 100065 ] > > Stopped at kdb_enter+0x3b: movq $0,kdb_why > > db> > > > > > > Anything I can/should do to poke at it before trying to capture a dump? > > Looks like it's related to: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226510#c18 > > > Peace, > > david > > -- > > David H. Wolfskill david@catwhisker.org > > An investigator who doesn't make a perp nervous isn't doing his job. > > > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > > > > Roman Bogorodskiy > From owner-freebsd-current@freebsd.org Wed Mar 21 13:02:53 2018 Return-Path: Delivered-To: freebsd-current@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 578BEF664B1 for ; Wed, 21 Mar 2018 13:02:53 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D56516E557 for ; Wed, 21 Mar 2018 13:02:52 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 87A69F664B0; Wed, 21 Mar 2018 13:02:52 +0000 (UTC) Delivered-To: current@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 60E00F664AE for ; Wed, 21 Mar 2018 13:02:52 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C07E6E54F; Wed, 21 Mar 2018 13:02:51 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w2LD2mF0048096; Wed, 21 Mar 2018 13:02:48 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w2LD2mfY048095; Wed, 21 Mar 2018 06:02:48 -0700 (PDT) (envelope-from david) Date: Wed, 21 Mar 2018 06:02:48 -0700 From: David Wolfskill To: Roman Bogorodskiy Cc: current@freebsd.org, imp@FreeBSD.org Subject: Re: "panic: Unholding 5 with cnt = 0" head/amd64 @r331290 Message-ID: <20180321130248.GW1233@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Roman Bogorodskiy , current@freebsd.org, imp@FreeBSD.org References: <20180321120942.GV1233@albert.catwhisker.org> <20180321122656.GA40816@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="a5Skt5M1uR2CgtYq" Content-Disposition: inline In-Reply-To: <20180321122656.GA40816@kloomba> User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 13:02:53 -0000 --a5Skt5M1uR2CgtYq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 21, 2018 at 04:26:57PM +0400, Roman Bogorodskiy wrote: > ... > > Anything I can/should do to poke at it before trying to capture a dump? >=20 > Looks like it's related to: >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226510#c18 > ..... Hmm... OK; thanks. I went ahead and grabbed crash dump; it may be found at (along with core.txt). Also, my laptop (running a kernel based on GENERIC, but with a few bits snipped out and things like IPFIREWALL_DEFAULT_TO_ACCEPT turned off) did not exhibit an issue. I am presently re-building head @r331290 on each machine (on a different slice); this time, without the Forth loader stuff being built (and with the Lua loader stuff being built). I mention this, not because I think the loader has anything to do with this, but because at this time, I have but a single failure out of two possible; smoke-testing the current builds will provide a chance to see if I somehow did something weird to the build machine earlier. Anyway, Warner should know how to reach me. :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org An investigator who doesn't make a perp nervous isn't doing his job. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --a5Skt5M1uR2CgtYq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqyV/hfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7he4qwf+Krq9Qt1qy8004zsJW3XfIHUqM5KuuJjzjKky9/1S6x2E3pxc0suW/bnQ xrVIsCJFsOLFO6zAnvLQMQItNjH5+Isq8QBkiSP2/2bIL2mycAdCkgN2FzORz3wm GPZma5ayY0uz5x50jO6I/CrFnytEW4imzWVpHTwSBapuHFVtchQcmJuFFiC8iM+S XlKSjcMEeCJpDf9Z7Bh8hR3Ilaix2o9TEz2SuSeKzSMUf+56X0hfQPhPZ9hgPAVP uweoUEHKz8YAyTJAfJ4nWGzpN5tPQDLju2Rz2YWWzZIhBEJDdf7//z9M904UX8MR HhM93WDxFt2Zx5OP1D+LbvNGT82OdQ== =yl9E -----END PGP SIGNATURE----- --a5Skt5M1uR2CgtYq-- From owner-freebsd-current@freebsd.org Wed Mar 21 13:28:39 2018 Return-Path: Delivered-To: freebsd-current@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 9D377F681B6 for ; Wed, 21 Mar 2018 13:28:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 332136F5C9 for ; Wed, 21 Mar 2018 13:28:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id E51E4F681B2; Wed, 21 Mar 2018 13:28:38 +0000 (UTC) Delivered-To: current@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 C2E3CF681AF for ; Wed, 21 Mar 2018 13:28:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5835C6F5C5 for ; Wed, 21 Mar 2018 13:28:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id h23so6632731iob.11 for ; Wed, 21 Mar 2018 06:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=B7ACgUzL9Lo4MZe2f62MbPXX1q4WjtH/OF88TFGgae4=; b=tF7u9GDrsAjM8sgrrBAKfx3ydCboU91WQqyNxIwN/QWAWPKJQfnPlpISoxtzhPRRQG +5xxCB/oV8wktdSdv6MZZZUbW6T1l94fTx2BfsnFTrW456+gnrWmMAbwfbLbsrEbfA3t +WPhTa5b0M0LX0NIfE3Cwm25W+fu7ypAk3Ys/0fDCqx9LZSx14LEvVc/ytmaWHCW79YU SZPMA994OqnzqxwKkodpGGhk4J5Zyfkkdj/fD0XDkqfegoUmECAFilnn3z6KXz7/sDGL 1n1X3otoXXvR9K2dgRwCCVpEBBY2krEJQO+Sd07evf+sl0DfexQ2u4KAo7V8CBAucyhH UbXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=B7ACgUzL9Lo4MZe2f62MbPXX1q4WjtH/OF88TFGgae4=; b=hJE/RtD/3EmhqUnBYMeTeWIOYkYnwKPxB/KhKV0q2Nt38mrghVeBidXG4K95podJLB miUXSic7r3BBeMlQ3UMHSbwLxcqBmVjsmNAnAH02wD0o6N+4Yu0Lf++SrOiZumGTlaAF ldp6XbQ2nampQdNWk8PaeACN5x3eVslDGRNbiN27OoX8MVO6gF563gOgDJ1hk6LOEPac mgToVYLZfsrZM1zuSUiJPYv2pV6OzFjrWJDOVcA/uaGfCREwbVGL9aLrpy3wc+RPekXx AecKguwz48QL5oc2tmKYIowmeo5YdIWg4li/HPAihvbrSmuhqDPA7KQ2iZHni4QFoqmJ y1PQ== X-Gm-Message-State: AElRT7H6wIxjS2AjPD67f6JMUOPZDSU/pj6W1vm7om5im/1keyjjEHPd qlap8zWjs4CXTGkcYQVs+mi7sQp5eYMNDiQEkEYybg== X-Google-Smtp-Source: AG47ELudwYFJKEqhjaikhokdlGhdkVLO/cqHkhP6hJrrPA4ynB8UToJ9x+m63YXtmFT6p4AUr2veeWCJVPdR+YmMUL8= X-Received: by 10.107.144.11 with SMTP id s11mr20967260iod.37.1521638917513; Wed, 21 Mar 2018 06:28:37 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 06:28:36 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:b173:8715:8433:2600] Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 06:28:36 -0700 (PDT) In-Reply-To: <20180321130248.GW1233@albert.catwhisker.org> References: <20180321120942.GV1233@albert.catwhisker.org> <20180321122656.GA40816@kloomba> <20180321130248.GW1233@albert.catwhisker.org> From: Warner Losh Date: Wed, 21 Mar 2018 07:28:36 -0600 X-Google-Sender-Auth: -C-Osym0Z_MypuLOHyOXP3hDJBk Message-ID: Subject: Re: "panic: Unholding 5 with cnt = 0" head/amd64 @r331290 To: David Wolfskill , Roman Bogorodskiy , current@freebsd.org, imp@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 13:28:39 -0000 On Mar 21, 2018 7:02 AM, "David Wolfskill" wrote: On Wed, Mar 21, 2018 at 04:26:57PM +0400, Roman Bogorodskiy wrote: > ... > > Anything I can/should do to poke at it before trying to capture a dump? > > Looks like it's related to: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226510#c18 > ..... Hmm... OK; thanks. I went ahead and grabbed crash dump; it may be found at (along with core.txt). Also, my laptop (running a kernel based on GENERIC, but with a few bits snipped out and things like IPFIREWALL_DEFAULT_TO_ACCEPT turned off) did not exhibit an issue. I am presently re-building head @r331290 on each machine (on a different slice); this time, without the Forth loader stuff being built (and with the Lua loader stuff being built). I mention this, not because I think the loader has anything to do with this, but because at this time, I have but a single failure out of two possible; smoke-testing the current builds will provide a chance to see if I somehow did something weird to the build machine earlier. Anyway, Warner should know how to reach me. :-) The fix is in 331291.. at least the back out for other issues... Warner Peace, david -- David H. Wolfskill david@catwhisker.org An investigator who doesn't make a perp nervous isn't doing his job. See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Wed Mar 21 15:36:58 2018 Return-Path: Delivered-To: freebsd-current@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 327C9F4E21F for ; Wed, 21 Mar 2018 15:36:58 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [104.225.8.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd-11-64", Issuer "freebsd-11-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1CF0763E0 for ; Wed, 21 Mar 2018 15:36:57 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [104.225.8.138]) by mail.neu.net (8.15.2/8.15.2) with ESMTPS id w2LFam1Y046596 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 21 Mar 2018 11:36:50 -0400 (EDT) (envelope-from andy@neu.net) Date: Wed, 21 Mar 2018 11:36:48 -0400 (EDT) From: AN To: freebsd-current@freebsd.org Subject: problem with [intr{swi4: clock (0)}] Message-ID: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.neu.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 15:36:58 -0000 Hi: I would appreciate any help with this issue, this is a new machine built in the last week and if it is a hardware issue I want to return it. The problem seems to have started in the last 24 hours or so. I am seeing a really high cpu utilization for [intr{swi4: clock (0)}]. I have tried a couple things to troubleshoot: rebuilt world and kernel turned off Virtualbox ( did not load kernel module) turned off in BIOS network, audio installed disk from another similar machine, booted and it shows the exact same problem. Here is what I see in top: last pid: 56553; load averages: 0.09, 0.44, 0.26 up 0+00:04:38 11:25:24 472 processes: 14 running, 418 sleeping, 40 waiting CPU 0: 0.0% user, 0.0% nice, 0.0% system, 27.5% interrupt, 72.5% idle CPU 1: 0.7% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.3% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 4: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 5: 0.0% user, 0.0% nice, 0.7% system, 0.0% interrupt, 99.3% idle CPU 6: 0.8% user, 0.0% nice, 0.8% system, 0.0% interrupt, 98.5% idle CPU 7: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 10: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 1096M Active, 53M Inact, 300K Laundry, 568M Wired, 290M Buf, 14G Free Swap: 21G Total, 21G Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 155 ki31 0K 192K CPU1 1 4:32 100.00% [idle{idle: cpu1}] 11 root 155 ki31 0K 192K CPU8 8 4:31 100.00% [idle{idle: cpu8}] 11 root 155 ki31 0K 192K CPU9 9 4:30 100.00% [idle{idle: cpu9}] 11 root 155 ki31 0K 192K CPU2 2 4:30 100.00% [idle{idle: cpu2}] 11 root 155 ki31 0K 192K CPU10 10 4:30 100.00% [idle{idle: cpu10}] 11 root 155 ki31 0K 192K CPU5 5 4:27 100.00% [idle{idle: cpu5}] 11 root 155 ki31 0K 192K RUN 11 4:25 99.82% [idle{idle: cpu11}] 11 root 155 ki31 0K 192K CPU6 6 4:30 98.93% [idle{idle: cpu6}] 11 root 155 ki31 0K 192K CPU7 7 4:31 96.83% [idle{idle: cpu7}] 11 root 155 ki31 0K 192K CPU3 3 4:27 94.94% [idle{idle: cpu3}] 11 root 155 ki31 0K 192K CPU4 4 4:29 94.11% [idle{idle: cpu4}] 11 root 155 ki31 0K 192K RUN 0 3:45 71.60% [idle{idle: cpu0}] 12 root -60 - 0K 656K CPU0 0 0:53 28.43% [intr{swi4: clock (0)}] 28.20% [intr{swi4: clock (0)}] - the process is using close to 30% cpu time. I have no idea what could be causing this, any advice would be appreciated. Thanks in advance. 12 root -60 - 0K 656K WAIT 0 1:27 28.80% [intr{swi4: clock (0)}] systat shows: 1 users Load 0.20 0.16 0.18 Mar 21 11:35 Mem usage: 11%Phy 1%Kmem Mem: KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 1357104 111928 4267688 193328 14176K count All 1357984 112656 4285556 211028 pages Proc: Interrupts r p d s w Csw Trp Sys Int Sof Flt 8 ioflt 996k total 1 314 2.0 296 2213 133 1.0 155 cow atkbd0 1 8 zfod 996k cpu0:timer 0.1%Sys 1.9%Intr 0.1%User 0.0%Nice 98.0%Idle ozfod 68 xhci0 259 | | | | | | | | | | %ozfod ahci0 260 + daefr 5 re0 261 4 dtbuf prcfr hdac0 262 Namei Name-cache Dir-cache 349771 desvn 21 totfr hdac1 280 Calls hits % hits % 3740 numvn react 4 cpu6:timer 474 474 100 958 frevn pdwak 5 cpu10:time 456 pdpgs 11 cpu7:timer Disks ada0 pass0 intrn 10 cpu11:time KB/t 0.00 0.00 469596 wire 3 cpu1:timer tps 0 0 1121780 act 2 cpu8:timer MB/s 0.00 0.00 170492 inact 8 cpu9:timer %busy 0 0 300 laund 5 cpu4:timer 14516016 free 2 cpu2:timer 183472 buf 7 cpu5:timer 7 cpu3:timer FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #18 r331138: Sun Mar 18 16:08:31 EDT 2018 root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1200060 FreeBSD 12.0-CURRENT #18 r331138: Sun Mar 18 16:08:31 EDT 2018 root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(vga): resolution 640x480 CPU: AMD Ryzen 5 1600X Six-Core Processor (3600.10-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x7 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16596353024 (15827 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs FreeBSD/SMP: 1 package(s) x 2 cache groups x 3 core(s) x 2 hardware threads random: unblocking device. Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180313/tbfadt-796) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff809e79e0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard From owner-freebsd-current@freebsd.org Wed Mar 21 21:12:48 2018 Return-Path: Delivered-To: freebsd-current@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 3C254F679C8 for ; Wed, 21 Mar 2018 21:12:48 +0000 (UTC) (envelope-from 482254ac@razorfever.net) Received: from pmta21.teksavvy.com (pmta21.teksavvy.com [76.10.157.36]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "*.teksavvy.com", Issuer "DigiCert SHA2 High Assurance Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C58EE68753 for ; Wed, 21 Mar 2018 21:12:47 +0000 (UTC) (envelope-from 482254ac@razorfever.net) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GKJQAXyrJa/0StpUVdGgEBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYIIgTUpOANthASIXowtAUIBAQQFAXklNQFekyiBTD0LExIHhA2EIyI?= =?us-ascii?q?2FgECAQEBAQEBAgNoHAxCEAGCFARLLC8BAQEBAQEBAQEBAQEBAQEaAg2BBxUeD?= =?us-ascii?q?0kCJgI7JA0IAQGEfQ0PrFGCIIRZg22BdgUTdodFgQiBMIV7AoEdg0WCVAOYOwg?= =?us-ascii?q?BAoYMiSCBS4N+gkIQhRuHQ4FwhncMgSYjCyeBUh9cgwiFfopsJDqGf4huAQE?= X-IPAS-Result: =?us-ascii?q?A2GKJQAXyrJa/0StpUVdGgEBAQEBAgEBAQEIAQEBAYIIgTU?= =?us-ascii?q?pOANthASIXowtAUIBAQQFAXklNQFekyiBTD0LExIHhA2EIyI2FgECAQEBAQEBA?= =?us-ascii?q?gNoHAxCEAGCFARLLC8BAQEBAQEBAQEBAQEBAQEaAg2BBxUeD0kCJgI7JA0IAQG?= =?us-ascii?q?EfQ0PrFGCIIRZg22BdgUTdodFgQiBMIV7AoEdg0WCVAOYOwgBAoYMiSCBS4N+g?= =?us-ascii?q?kIQhRuHQ4FwhncMgSYjCyeBUh9cgwiFfopsJDqGf4huAQE?= X-IronPort-AV: E=Sophos;i="5.48,341,1517893200"; d="scan'208";a="24931830" Received: from 69-165-173-68.dsl.teksavvy.com (HELO mail.razorfever.net) ([69.165.173.68]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2018 17:12:46 -0400 Received: from [127.0.0.1] (mail.razorfever.net [192.168.0.4]) by mail.razorfever.net (8.15.2/8.14.9) with ESMTP id w2LLCjGb012064 for ; Wed, 21 Mar 2018 17:12:45 -0400 (EDT) (envelope-from 482254ac@razorfever.net) X-Authentication-Warning: mail.razorfever.net: Host mail.razorfever.net [192.168.0.4] claimed to be [127.0.0.1] To: FreeBSD Current From: "Derek (freebsd lists)" <482254ac@razorfever.net> Subject: freebsd-update: to a specific patch level - help please? Message-ID: Date: Wed, 21 Mar 2018 17:12:45 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, FROM_STARTS_WITH_NUMS,RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.razorfever.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 21:12:48 -0000 Hi! I was surprised when using freebsd-update, that there was no way to specify a patch level. In my day to day, I need to ensure security patches are applied. I also need to assess the impact of patches, and ensure consistency (ie. versions) in my environments. This can take time. Here's a story for context, please feel free to skip: We are planning to cut our 10.3-RELEASE infrastructure over to 11.1-RELEASE before the end of the month, because it's EoL in April. We updated and cut over our production load balancer March 6th (and patted ourselves on the back for being ahead of schedule), and within less than 12 hours, updated our backup load balancers. Unfortunately, we're now on ever so slightly different versions (-p6/-p7), and we're not affected by the -p7 problems. This makes my eye twitch slightly, especially when -p7 was the first patch of 2018. Now we need to upgrade our application servers, that are running our trusted code, and -p8 comes out. I'm nervous about just applying -p8, but I definitely want to upgrade to 11.1-RELEASE asap. After assessing the impact of -p8 on our infrastructure, I feel the security risk is relatively low in the short term (and we've waited this long anyway), but I feel the probability of introducing unintended side-effects is high, and want some time to test and asses. /story It would seem to me, for repeatable environments, that binary updates from FreeBSD that can be pinned to specific version are highly desireable. I've gone ahead and created a patch for my use here: https://github.com/derekmarcotte/freebsd/commit/009015a7dda5d1f1c46f4706c222614f17fb535c (there's a 10.3-specific one here: https://github.com/derekmarcotte/freebsd/commit/458879f36ae984add0ff525fb6c2765fcf1fba67 ) I'd be happy to open a PR, and to iterate and improve on this PoC, but if there's no support from the project, I'll keep it to myself. I guess what I'm asking is, for these reasons, is anyone willing to work with me (in mentorship+commit bits) to add this feature (maybe not this particular implementation) to freebsd-update? Thanks! Derek From owner-freebsd-current@freebsd.org Wed Mar 21 21:26:16 2018 Return-Path: Delivered-To: freebsd-current@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 D6B10F68B4E for ; Wed, 21 Mar 2018 21:26:15 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 27207694CF for ; Wed, 21 Mar 2018 21:26:14 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Wed, 21 Mar 2018 22:24:07 +0100 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B91B0524-6295-420C-AF34-06863F30B763.1 envelope-from (authenticated bits=0); Wed, 21 Mar 2018 22:23:56 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: freebsd-update: to a specific patch level - help please? From: Rainer Duffner In-Reply-To: Date: Wed, 21 Mar 2018 22:24:22 +0100 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Derek (freebsd lists)" <482254ac@razorfever.net> X-Mailer: Apple Mail (2.3445.5.20) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=12 total_conn=6 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 5154, bad: 2, connections: 5651, history: 5152, asn_score: 108, asn_connections: 115, asn_good: 108, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 21:26:16 -0000 > Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists) = <482254ac@razorfever.net>: >=20 > Hi! >=20 > I was surprised when using freebsd-update, that there was no way to = specify a patch level. AFAIK, the usual answer to these kinds of requests is: =E2=80=9ERun your = own freebsd-update server=E2=80=9C. Mirroring one of the existing ones is AFAIK neither guaranteed to work = nor desired by the current =E2=80=9Eadministration=E2=80=9C. I=E2=80=99ve contemplated doing both, but never had enough heart-ache to = do it and never thought the pay-off would be greater than the potential = problems. It=E2=80=99s also a somewhat transient problem now because - AFAIK - = FreeBSD will see packaged base and you can probably mirror those = packages and snapshot the directory at any point in time. And/Or it=E2=80=99s just easier to create these base-packages yourselves = vs. running your own freebsd-update server. From owner-freebsd-current@freebsd.org Thu Mar 22 00:45:50 2018 Return-Path: Delivered-To: freebsd-current@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 1A052F53B83 for ; Thu, 22 Mar 2018 00:45:50 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 7F0657220D for ; Thu, 22 Mar 2018 00:45:49 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id p142-v6so10584448lfd.6 for ; Wed, 21 Mar 2018 17:45:49 -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:from:date:message-id:subject:to; bh=AFRy55gyT5u/ZP2T1pRwRs9blLyOAws3eYIdjxkXnSM=; b=oMkpqT7a4JSOFIf0R+rWX48ohlV4UD1LJj+W5Fa+0UeKaHPThCYKxQ6vXLK1SldN/z KlBEYdZKJu4Ikukn6SBBKzm4nl8V8s/5p5cyD+jbH0ulU5sf/6kgATZ9C0F4nzB6CpN+ oQBNX6SJ4amdxMm2alzKwhzJWWEBxVni/EVG8WnVOC5toj2ZkN2kQhst7AsmOXcTtNIN W6Fo/hDOpwSoQBwvrbz8nNBrAv88VRAhybAFPQzpRZfQ4Kz0qmlG8RuuQfUgMRinFAiO eZqtfzsXPhyNMdU0xRYtK5hKm3KUdzaIcW8/SGCJYrgkV76APSKPM1/XFWqEWRcrQpP3 713g== X-Gm-Message-State: AElRT7GbZRDavYUbdlxzF4t06N39D3CT9KS/S5PM2W09BXsQbmIcOLSY DKfJVnzX+ZaqfDbpvchGlzF2lBQ3 X-Google-Smtp-Source: AG47ELurL9/A31/g7hsG41OEuhSYsmAdhFsgr/iTSmH4CJnSXpGc7XRTN/l3iyRxcVLZRSMfH9Ajuw== X-Received: by 10.46.125.10 with SMTP id y10mr15555493ljc.23.1521679541519; Wed, 21 Mar 2018 17:45:41 -0700 (PDT) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com. [209.85.215.41]) by smtp.gmail.com with ESMTPSA id q24sm1114059ljj.68.2018.03.21.17.45.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 17:45:41 -0700 (PDT) Received: by mail-lf0-f41.google.com with SMTP id g203-v6so10570501lfg.11 for ; Wed, 21 Mar 2018 17:45:41 -0700 (PDT) X-Received: by 2002:a19:b516:: with SMTP id e22-v6mr15946674lff.47.1521679541255; Wed, 21 Mar 2018 17:45:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Wed, 21 Mar 2018 17:45:20 -0700 (PDT) From: Kyle Evans Date: Wed, 21 Mar 2018 19:45:20 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Call for Testing: UEFI Changes To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 00:45:50 -0000 Hello! A number of changes have gone in recently pertaining to UEFI booting and UEFI runtime services. The changes with the most damaging potential are: We now put UEFI runtime services into virtual address mode, fixing runtime services with U-Boot/UEFI as well as the firmware implementation in many Lenovos. The previously observed behavior was a kernel panic upon invocation of efibootmgr/efivar, or a kernel panic just loading efirt.ko or compiling EFIRT into the kernel. Graphics mode selection is now done differently to avoid regression caused by r327058 while still achieving the same effect. The observed regression was that the kernel would usually end up drawing incorrectly at the old resolution on a subset of the screen, due to incorrect framebuffer information. Explicit testing of these changes, the latest of which happened in r331326, and any feedback from this testing would be greatly appreciated. Testing should be done with either `options EFIRT` in your kernel config or efirt.ko loaded along with updated bootloader bits. I otherwise plan to MFC commits involved with the above-mentioned changes by sometime in the first week of April, likely no earlier than two (2) weeks from now on April 4th. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Mar 21 23:11:55 2018 Return-Path: Delivered-To: freebsd-current@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 4DDAFF4C58D for ; Wed, 21 Mar 2018 23:11:55 +0000 (UTC) (envelope-from mailinglist@diamondbox.dk) Received: from mailrelay3-2.pub.mailoutpod1-cph3.one.com (mailrelay3-2.pub.mailoutpod1-cph3.one.com [46.30.212.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B577F6DDE6 for ; Wed, 21 Mar 2018 23:11:54 +0000 (UTC) (envelope-from mailinglist@diamondbox.dk) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=diamondbox.dk; s=20140924; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=qYyzqZJekYTdxTfNAZpDbwqzRE9GtZoADT3dYDHIca4=; b=kiO5mHhzfKoXjn+3qJ0R64DhR+PMnyd/sqLjb1WgpebHGt6WYo279C90byYUJAPVwdppIgWaCx7j8 eq75IvEIMtQW40SKp2uI4Vpff7dcaKKoE1FDE5EHDQ8hqvn9Yq+Foax1sP3SECgMIqrvuLIkhN+o6a a2DKLe5yKIWCKMhE= X-HalOne-Cookie: 2d2abfa4253228afae1b7718a23a88c25161ec88 X-HalOne-ID: 147a13b8-2d5d-11e8-bf23-d0431ea8bb03 Received: from diamond.diamondbox.dk (unknown [212.237.134.130]) by mailrelay3.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA id 147a13b8-2d5d-11e8-bf23-d0431ea8bb03; Wed, 21 Mar 2018 23:10:43 +0000 (UTC) Subject: Re: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead To: Cy Schubert , Theron Tarigo Cc: AN , freebsd-ports@freebsd.org, freebsd-current@freebsd.org References: <201803182341.w2INfppM004203@slippy.cwsent.com> From: Nikolaj Thygesen Organization: diamondbox.dk Message-ID: Date: Thu, 22 Mar 2018 00:10:42 +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: <201803182341.w2INfppM004203@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: da X-Mailman-Approved-At: Thu, 22 Mar 2018 01:00:17 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2018 23:11:55 -0000 On 03/19/2018 00:41, Cy Schubert wrote: > The other thing you might want to check out is if you multiboot your > laptop that any non-FreeBSD operating system may put hardware into an > inconsistent state. For example, my Acer laptop loses sound if I boot > Windows then boot FreeBSD. The workaround is either adjust the HDA > inputs/outputs through sysctl or simply power cycle the laptop. I fixed that issue by changing the Windows sound driver to the generic hda driver instead of the Realtek driver.     N :o) From owner-freebsd-current@freebsd.org Thu Mar 22 02:42:21 2018 Return-Path: Delivered-To: freebsd-current@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 80FC3F5EA01 for ; Thu, 22 Mar 2018 02:42:21 +0000 (UTC) (envelope-from hyun@caffeinated.codes) 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 2009C780FA for ; Thu, 22 Mar 2018 02:42:20 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D1E752088E; Wed, 21 Mar 2018 22:42:19 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute7.internal (MEProxy); Wed, 21 Mar 2018 22:42:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= caffeinated.codes; 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=fm1; bh=ivnDDJ h8UNozi8nhv08P8B3TNhmk7wx0LSeDDAwC9OI=; b=GSYR4X5v4ne6j4o8GQwxyC nrLA/Vwk9+2UJsc5AcNY21GTcXLNuXP8r5GKgVE9fGhAJhVvU5eXR+9MDKiNwprF BtN/K54sgkfvQaiFyd+6uVHAl2U7O6cwAcPQmy86oB7GkhLvhFKgO/twPcWd8k8F 5Yvw2YKdRHVcAwX+SoioxW998fk4z/Kxm1Vn2Of2mXlMj4qA0K20RW2ZfMOppw9S 2x7A60DIc7G8pB/sr2F9PAMADBBmFC16zy6iwaqPR79PbdUS4nsqjDvief6yOFk6 psfdmevH/Lq1IUWnN4c+2IKZEKap87+st9MXeQPQIHvgr8zvUuS0/0ZO7byGECLw == 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=ivnDDJ h8UNozi8nhv08P8B3TNhmk7wx0LSeDDAwC9OI=; b=gWX55bi3UzjOrfduPh9Z9y cks4Gi9SAR1MLnMB5Pyo4jOkmdsGJyR+pL/42jiiVHZDl2HwIjU0PilxIZUPv4Sf s7SekUoCmohXSvQ01jlvHoaJCPj0HdD0dN8/FLXpoRUmt+ap808zs5BTx3bBhFjV CggYKvJNZ9VZfI75uhjpLB9N1ZGy+UUVUgsVtvKwG54UEuF5vcrHUON05Ca6QVAh 8X0KUysUpUlvFzAe/dOvqbGMBtFRqoZ7nFpxsWr2tQ4yU5C143fsZtazbE75N/lz I54M3yu9CUf7bIk7/zz4tTWsBMiE0tkCyzfK5keBXDMqXLlNIjOw91QjmsolX1VQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id AA1FD940A2; Wed, 21 Mar 2018 22:42:19 -0400 (EDT) Message-Id: <1521686539.3047757.1311778784.3E60E604@webmail.messagingengine.com> From: Hyun Hwang To: "Hartmann, O." Cc: FreeBSD CURRENT MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba Date: Wed, 21 Mar 2018 22:42:19 -0400 In-Reply-To: <20180321120710.4eb3b944@hermann> References: <20180321120710.4eb3b944@hermann> Subject: Re: CURRENT r331284: crashing with USB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 02:42:21 -0000 On Wednesday, March 21, 2018, 12:07 PM (UTC+0100), "Hartmann, O." wrote: > Hello. > > Incident: CURRENT r331284 can be brought down reliably with an USB > flash drive plugged in and out without mounting or doing anything with > it. > > [...] > > Does anyone else observe this bug? > Can confirm: whenever I plug my Transcend USB microSD reader into my builder (amd64, r331284), the kernel does attach da0 then immediately panics and falls down to `db>` prompt. > I can plugin the USB and then unplug it and after two or three times doing this, the box goes down. I did not even have to plug-unplug the reader three times; plug the reader in and bam! immediate panic. AFAIK, r331115 did not have this issue because I was able to update my RPi 2 with the very reader from the very builder. I managed to salvage kernel binary dump; in case the dump is needed, please let me know. -- Hyun Hwang From owner-freebsd-current@freebsd.org Thu Mar 22 04:49:39 2018 Return-Path: Delivered-To: freebsd-current@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 BA26DF67D61; Thu, 22 Mar 2018 04:49:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 204B47E031; Thu, 22 Mar 2018 04:49:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2M4nYEZ014376 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 21 Mar 2018 21:49:35 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2M4nY2L014375; Wed, 21 Mar 2018 21:49:34 -0700 (PDT) (envelope-from fbsd) Date: Wed, 21 Mar 2018 21:49:34 -0700 From: bob prohaska To: "Hartmann, O." Cc: FreeBSD CURRENT , freebsd-arm@freebsd.org, bob prohaska Subject: Re: CURRENT r331284: crashing with USB Message-ID: <20180322044934.GA13553@www.zefox.net> References: <20180321120710.4eb3b944@hermann> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180321120710.4eb3b944@hermann> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 04:49:40 -0000 On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote: > > not the ZFS. I can plugin the USB and then unplug it and after two or > three times doing this, the box goes down. > > > Does anyone else observe this bug? > An RPI2 running r331179 didn't crash, but it did complain about setting addresses. The same error crops up from time to time when pl2303 serial adapters have been in use for some time (hours): login: ugen0.5: at usbus0 (disconnected) uftdi0: at uhub1, port 4, addr 5 (disconnected) uftdi0: detached ugen0.5: at usbus0 umass1 on uhub1 umass1: on usbus0 umass1: SCSI over Bulk-Only; quirks = 0x0100 umass1:1:1: Attached to scbus1 da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: Removable Direct Access SPC-4 SCSI device da1: Serial Number AA010428162242131598 da1: 40.000MB/s transfers da1: 59836MB (122544516 512 byte sectors) da1: quirks=0x2 FreeBSD/arm (www.zefox.com) (ttyu0) login: ugen0.5: at usbus0 (disconnected) umass1: at uhub1, port 5, addr 5 (disconnected) da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: s/n AA010428162242131598 detached (da1:umass-sim1:1:0:0): Periph destroyed umass1: detached ugen0.5: at usbus0 umass1 on uhub1 umass1: on usbus0 umass1: SCSI over Bulk-Only; quirks = 0x0100 umass1:1:1: Attached to scbus1 da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: Removable Direct Access SPC-4 SCSI device da1: Serial Number AA010428162242131598 da1: 40.000MB/s transfers da1: 59836MB (122544516 512 byte sectors) da1: quirks=0x2 ugen0.5: at usbus0 (disconnected) umass1: at uhub1, port 5, addr 5 (disconnected) da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: s/n AA010428162242131598 detached (da1:umass-sim1:1:0:0): Periph destroyed umass1: detached usbd_req_re_enumerate: addr=5, set address failed! (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_IOERROR usbd_req_re_enumerate: addr=5, set address failed! (USB_ERR_IOERROR, ignored) usbd_setup_device_desc: getting device descriptor at addr 5 failed, USB_ERR_IOERROR usb_alloc_device: Failure selecting configuration index 0:USB_ERR_IOERROR, port 5, addr 5 (ignored) ugen0.5: at usbus0 ugen0.5: at usbus0 (disconnected) ugen0.5: at usbus0 umass1 on uhub1 umass1: on usbus0 umass1: SCSI over Bulk-Only; quirks = 0x0100 umass1:1:1: Attached to scbus1 da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: Removable Direct Access SPC-4 SCSI device da1: Serial Number AA010428162242131598 da1: 40.000MB/s transfers da1: 59836MB (122544516 512 byte sectors) da1: quirks=0x2 Thanks for reading, I hope it's useful. bob prohaska From owner-freebsd-current@freebsd.org Thu Mar 22 05:17:42 2018 Return-Path: Delivered-To: freebsd-current@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 DAE66F698EF for ; Thu, 22 Mar 2018 05:17:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 645007F614 for ; Thu, 22 Mar 2018 05:17:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id y20-v6so9539412itc.5 for ; Wed, 21 Mar 2018 22:17:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+dzTV3sW2fxV9InblVW2WLZHk7Dj5MBQ92G+gDUZgn8=; b=jld+ivL4GtBSW7ut7HU1g9pMr2/y6CH0qXyNAEJaUTD3T1p2hmVwcoSxWMmHaNDjw3 0vZR1l/cx1mdW6KyX8BtLbup4VvCPMKwWrZXZzKsd+EGP2rls32LKI80oKnSDHTH/sFu oV/ZyGxP1BE4UL46Pqi6QF3ZD3YZmAnPJTAePXpuorSggq4tlB/p2mgPcB1VhwteW7HQ JqxgASema3S+4nIi184FgumSAGvlSBPKs6qETTShTi7iXiRXdXXAf7EkzTe2K+Amg2ON N/QaGKfLO1Mo9TeOjR46kseySnGSm4Cqem16dc2M0tQqLGYW1PmwmE7SnZ1HSMrYHZpk nfOA== 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=+dzTV3sW2fxV9InblVW2WLZHk7Dj5MBQ92G+gDUZgn8=; b=IUq3SNInBlwa+OgIqZLoH6Ucge3hOdbVrEH5nAASS+O1TbHemMd+IniI7NfgjWYIOa GJo6Cm78wZrectYwrdiLB1LY+nnYFrMaTJrLDNVgQRPudD8SAvruF4mDOO0J6dt4vFsE hJ72HM2Fjf+ukm9Gb/PpM196bTiuIRVm+nZRACVGAoYlFfLh7lLmJ88hQVatnj3tf5Ku kw6YWh60F/TQpMIoOj56GWWGqBJV/A12oZXjjCK/Uc0zLCwa+ofwiypxmxAQ/4F4Fylp K3T5eNcs9LGa5xYxW0vwb5xDxj3PVq6+ffEnugj1VIiHnCZMECdb+1FgSEtxovZngh9r cIkA== X-Gm-Message-State: AElRT7EnteLzubZwXKywu7/qpJmf9sfQ6CMVsl6QJ6+JESughgo7omtP WAacS8cuXRbhofgwu2tsyBSmtDr04+eU+YudJ7UsC6/g X-Google-Smtp-Source: AG47ELtnQgWdGm2vVRrQwE7REIoOHlsp0YfWyGmiX9KtzWCtmWnde89F/WbFgMNhqpstWle0q7B5oJTtNh7z9VKVZ5g= X-Received: by 2002:a24:fa83:: with SMTP id v125-v6mr7435186ith.36.1521695860542; Wed, 21 Mar 2018 22:17:40 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 22:17:39 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <1521686539.3047757.1311778784.3E60E604@webmail.messagingengine.com> References: <20180321120710.4eb3b944@hermann> <1521686539.3047757.1311778784.3E60E604@webmail.messagingengine.com> From: Warner Losh Date: Wed, 21 Mar 2018 23:17:39 -0600 X-Google-Sender-Auth: A0FEkMzFR-EDeZHGVl19SkdwdXg Message-ID: Subject: Re: CURRENT r331284: crashing with USB To: Hyun Hwang Cc: "Hartmann, O." , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 05:17:42 -0000 On Wed, Mar 21, 2018 at 8:42 PM, Hyun Hwang wrote: > On Wednesday, March 21, 2018, 12:07 PM (UTC+0100), "Hartmann, O." < > ohartmann@walstatt.org> wrote: > > Hello. > > > > Incident: CURRENT r331284 can be brought down reliably with an USB > > flash drive plugged in and out without mounting or doing anything with > > it. > > > > [...] > > > > Does anyone else observe this bug? > > > > Can confirm: whenever I plug my Transcend USB microSD reader into my > builder (amd64, r331284), the kernel does attach da0 then immediately > panics and falls down to `db>` prompt. > Do you have a traceback? Warner > > I can plugin the USB and then unplug it and after two or three times > doing this, the box goes down. > > I did not even have to plug-unplug the reader three times; plug the reader > in and bam! immediate panic. > > AFAIK, r331115 did not have this issue because I was able to update my RPi > 2 with the very reader from the very builder. > I managed to salvage kernel binary dump; in case the dump is needed, > please let me know. > -- > Hyun Hwang > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu Mar 22 05:42:01 2018 Return-Path: Delivered-To: freebsd-current@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 0E80CF6B572 for ; Thu, 22 Mar 2018 05:42:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 897AA808FF for ; Thu, 22 Mar 2018 05:42:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id k135-v6so9801112ite.2 for ; Wed, 21 Mar 2018 22:42:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6zmF6oKg/D56mZguLoRUrwnDkfZLhxIQDN973J9QbNo=; b=O3IGGvDboqY4bPQy2PFcanYpMWa0NHtcULg0+SoaIXGVeNOVWKNCAwAxtzgXzjwMNx OfeZ23SRoXV0YquACClTydCVzdkT9qSuOuTNZOGZwxGjmZCYv/XOjEVLfeDQMF0hsSBJ TGjCryzgDKIvA1g9wY6vjJIA5LMPetVBHlrXf7duy0il5oSAkTOav1oqofuXMQKm5hKN 9HmrNDdsvLquZNBBgwvGTd/Lc2kkaLDCEViAC+aoB/ZOE1Q1E0dpD6yMEcSyZEHLMuH0 ckmvvTTgv+/vU5+zGhDZAR7lrnAijUPbXD2menTlznTVpgwoauHjedepRw8dz7hOs4at DYNg== 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=6zmF6oKg/D56mZguLoRUrwnDkfZLhxIQDN973J9QbNo=; b=GY0tMVAoIqLXSdSON5DC/xvS4TKrk4OkxPxOhUJbktutzDQlBio2z0e2gsUyHkOTjD k3rVfBFS/rAa+e6TdpifDttEuFP1PhqPYgvFrB0dKFb47FinM8RqtsQgTdtJlRk29bHa fH/cohC/zYVNkSxtfcRBtF++ng5UHOqx8MQATnGsKCLUWgzsJc52dPZW0z7DsSkBVth1 RXYKBBtsBnDaWByxwkeuCm5Ol2nxgOJ4Cc1u57s6PhvRKnxLACRGVODQPgHKFaVQsGH7 l5GNH2ERjkBCtZdYCCLDyvD5rhj89hEMwoImSCU8IwF3AGQgGt0wjaLVWWrN1p+BlSO4 fTKg== X-Gm-Message-State: AElRT7HQbnxgQ16I2wRojy9cFSuNs+kjIeVTZZMLxxPiY4AyZaYyO2Ux UF4kLdehwCjRXHUvUa9pnlZsRmXy8GmsrcSKkEV9OQ== X-Google-Smtp-Source: AG47ELskDl+LJIwM5oEiJqfdAmkL0itHhAMKpHAyS0xNuVMBIppzg4h6RPtAIF5cXN/qUuQWcYNkwKfyVK2DE/S6BZQ= X-Received: by 2002:a24:6f04:: with SMTP id x4-v6mr7513451itb.51.1521697319917; Wed, 21 Mar 2018 22:41:59 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Wed, 21 Mar 2018 22:41:59 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20180321120710.4eb3b944@hermann> <1521686539.3047757.1311778784.3E60E604@webmail.messagingengine.com> From: Warner Losh Date: Wed, 21 Mar 2018 23:41:59 -0600 X-Google-Sender-Auth: _B6F9VDcWnMlMFcmd4UvJMFgLRY Message-ID: Subject: Re: CURRENT r331284: crashing with USB To: Hyun Hwang Cc: "Hartmann, O." , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 05:42:01 -0000 On Wed, Mar 21, 2018 at 11:17 PM, Warner Losh wrote: > > > On Wed, Mar 21, 2018 at 8:42 PM, Hyun Hwang > wrote: > >> On Wednesday, March 21, 2018, 12:07 PM (UTC+0100), "Hartmann, O." < >> ohartmann@walstatt.org> wrote: >> > Hello. >> > >> > Incident: CURRENT r331284 can be brought down reliably with an USB >> > flash drive plugged in and out without mounting or doing anything with >> > it. >> > >> > [...] >> > >> > Does anyone else observe this bug? >> > >> >> Can confirm: whenever I plug my Transcend USB microSD reader into my >> builder (amd64, r331284), the kernel does attach da0 then immediately >> panics and falls down to `db>` prompt. >> > > Do you have a traceback? > actually, can you test https://reviews.freebsd.org/D14792 for me please? The hardware I bought to provoke this wound up in my wife's bags for a trip she's still on and I won't be able to test until Friday (which is why I've been slow to fix this). I hesitate to commit another change I'm sure will fix it on the off chance I'll be wrong again... Occasionally, we'll send a TUR to the device. To make sure that the periph doesn't go away while that's going on, we acquire a reference to the device. When the command completes we release it. The problem is that there's a race that the new asserts I put in uncovered. If we've sent a TUR to the device, but it hasn't completed when damediapoll timeout fires, it will think that we can send a TUR since we cleared the TUR work flag. This bumps the count, and bang! we have two TURs in flight. The Transend USB reader, at least the one I got takes a long time for TUR to return, so this can trigger the race. The above fix simply says that if a TUR is in flight, don't schedule another one. We'll poll again later anyway, and we have the TUR in flight already, so we'll accomplish the goal of TUR even though we chose to omit one we might otherwise do. Warner > Warner > > >> > I can plugin the USB and then unplug it and after two or three times >> doing this, the box goes down. >> >> I did not even have to plug-unplug the reader three times; plug the >> reader in and bam! immediate panic. >> >> AFAIK, r331115 did not have this issue because I was able to update my >> RPi 2 with the very reader from the very builder. >> I managed to salvage kernel binary dump; in case the dump is needed, >> please let me know. >> -- >> Hyun Hwang >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@freebsd.org Thu Mar 22 06:26:23 2018 Return-Path: Delivered-To: freebsd-current@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 06F58F6E417 for ; Thu, 22 Mar 2018 06:26:23 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (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 4BE93829C6 for ; Thu, 22 Mar 2018 06:26:21 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w2M6Q9KE061507; Thu, 22 Mar 2018 15:26:10 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201803220626.w2M6Q9KE061507@kx.openedu.org> Date: Thu, 22 Mar 2018 15:26:09 +0900 From: KIRIYAMA Kazuhiko To: Thomas Steen Rasmussen Cc: KIRIYAMA Kazuhiko , freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 In-Reply-To: <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> References: <201803192300.w2JN04fx007127@kx.openedu.org> <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 06:26:23 -0000 At Wed, 21 Mar 2018 08:01:24 +0100, Thomas Steen Rasmussen wrote: > > On 03/20/2018 12:00 AM, KIRIYAMA Kazuhiko wrote: > > Hi, > > > > I've been encountered suddenly death in ZFS full volume > > machine(r330434) about 10 days after installation[1]: > > > > ZFS: i/o error - all block copies unavailable > > ZFS: can't read MOS of pool zroot > > gptzfsboot: failed to mount default pool zroot > > > > FreeBSD/x86 boot > > ZFS: i/o error - all block copies unavailable > > ZFS: can't find dataset u > > Default: zroot/<0x0>: > > boot: > > Has this pool had new vdevs addded to it since the server was installed? No. /dev/mfid0p4 is a RAID60 disk of AVAGO MegaRAID driver[1]. > What does a "zpool status" look like when the pool is imported? Like below: root@t1:~ # zpool import -fR /mnt zroot root@t1:~ # zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mfid0p4 ONLINE 0 0 0 errors: No known data errors root@t1:~ # [1] http://ds.truefc.org/~kiri/freebsd/current/zfs/dmesg.boot > > /Thomas > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > --- KIRIYAMA Kazuhiko From owner-freebsd-current@freebsd.org Thu Mar 22 10:45:02 2018 Return-Path: Delivered-To: freebsd-current@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 ABAEEF59420 for ; Thu, 22 Mar 2018 10:45:02 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 487076D100; Thu, 22 Mar 2018 10:45:01 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-18bc70d5.06-431-73746f70.cust.bredbandsbolaget.se ([213.112.188.24] helo=sigyn.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1eyxDp-000191-5m; Thu, 22 Mar 2018 11:13:25 +0100 Received: from gw.bright-group.se ([193.12.143.142] helo=[192.168.30.20]) by sigyn.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1eyxDo-0007fI-Gt; Thu, 22 Mar 2018 11:13:24 +0100 From: Jakob Alvermark Subject: Re: Call for Testing: UEFI Changes To: Kyle Evans , FreeBSD Current References: Message-ID: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> Date: Thu, 22 Mar 2018 11:13:24 +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-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 10:45:03 -0000 Hi! Just updated to r331345. Two problems: 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still included in loader.rc. Loader fails to load it and subsequently fails to load modules. Reinstalling efi.4th problem 2 appears. 2. Fixing problem 1 and adding efirt_load="YES" to /boot/loader.conf makes the kernel panic instantly. Photo of panic: https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 Jakob On 03/22/18 01:45, Kyle Evans wrote: > Hello! > > A number of changes have gone in recently pertaining to UEFI booting > and UEFI runtime services. The changes with the most damaging > potential are: > > We now put UEFI runtime services into virtual address mode, fixing > runtime services with U-Boot/UEFI as well as the firmware > implementation in many Lenovos. The previously observed behavior was a > kernel panic upon invocation of efibootmgr/efivar, or a kernel panic > just loading efirt.ko or compiling EFIRT into the kernel. > > Graphics mode selection is now done differently to avoid regression > caused by r327058 while still achieving the same effect. The observed > regression was that the kernel would usually end up drawing > incorrectly at the old resolution on a subset of the screen, due to > incorrect framebuffer information. > > Explicit testing of these changes, the latest of which happened in > r331326, and any feedback from this testing would be greatly > appreciated. Testing should be done with either `options EFIRT` in > your kernel config or efirt.ko loaded along with updated bootloader > bits. > > I otherwise plan to MFC commits involved with the above-mentioned > changes by sometime in the first week of April, likely no earlier than > two (2) weeks from now on April 4th. > > Thanks, > > Kyle Evans > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to"freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Mar 22 10:52:12 2018 Return-Path: Delivered-To: freebsd-current@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 8B154F59CF0 for ; Thu, 22 Mar 2018 10:52:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 393D56D6D6 for ; Thu, 22 Mar 2018 10:52:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P5Z00P00MZC1000@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 22 Mar 2018 10:51:38 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1521715898; bh=qIc69tpv6jn/+S90Vr/noS5kCnvI2jLoJ4NimfSJBGA=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=5SFI0Iso6GBwPu8v3OIa+qkJ5WPt0FBojLDJazKuj2D3MzBNcCKqgNFTGlFjgdpeS t/JsRQQkX8jhnxLIudsGCJn8suFoVb6HMfTpAzrxVGm7EZgQVUhbRmHMJypMr18Icb pKeZ/WKwoLUZieHOAfPpVMYOvHknkQXJqwpw2uTHZqqpmz0KvNp8DE7WAxImHSarv2 C2cz/RA4hsb/BwgfztentM2Ev0Ydor3SafpwtlNzy+tvn/13AvTZ0cJKWvecVUyyMf 7t+bF07XFBOisaJMxdZCZKEGZeR3bBvCcv87g+zHDqmEnWDIAjkVosKqAT87uvGoST Cvey5oMzP7D8g== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P5Z00IPXNHX7240@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 22 Mar 2018 10:51:36 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-22_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1803220131 From: Toomas Soome Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Call for Testing: UEFI Changes Date: Thu, 22 Mar 2018 12:51:33 +0200 References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> To: FreeBSD Current In-reply-to: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> Message-id: <901CE994-0A28-4538-A4A9-A23E0B7E4879@me.com> X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 10:52:12 -0000 > On 22 Mar 2018, at 12:13, Jakob Alvermark wrote: >=20 > Hi! >=20 >=20 > Just updated to r331345. >=20 > Two problems: >=20 > 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still = included in loader.rc. Loader fails to load it and subsequently fails to = load modules. Reinstalling efi.4th problem 2 appears. >=20 >=20 > 2. Fixing problem 1 and adding efirt_load=3D"YES" to /boot/loader.conf = makes the kernel panic instantly. Photo of panic: = https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 >=20 >=20 > Jakob The efi.4th was introduced and later removed by Warner, a bit too = hastily perhaps=E2=80=A6 but perhaps it is better to note the partial = revert of the removal or something like that:) rgds, toomas >=20 >=20 > On 03/22/18 01:45, Kyle Evans wrote: >> Hello! >>=20 >> A number of changes have gone in recently pertaining to UEFI booting >> and UEFI runtime services. The changes with the most damaging >> potential are: >>=20 >> We now put UEFI runtime services into virtual address mode, fixing >> runtime services with U-Boot/UEFI as well as the firmware >> implementation in many Lenovos. The previously observed behavior was = a >> kernel panic upon invocation of efibootmgr/efivar, or a kernel panic >> just loading efirt.ko or compiling EFIRT into the kernel. >>=20 >> Graphics mode selection is now done differently to avoid regression >> caused by r327058 while still achieving the same effect. The observed >> regression was that the kernel would usually end up drawing >> incorrectly at the old resolution on a subset of the screen, due to >> incorrect framebuffer information. >>=20 >> Explicit testing of these changes, the latest of which happened in >> r331326, and any feedback from this testing would be greatly >> appreciated. Testing should be done with either `options EFIRT` in >> your kernel config or efirt.ko loaded along with updated bootloader >> bits. >>=20 >> I otherwise plan to MFC commits involved with the above-mentioned >> changes by sometime in the first week of April, likely no earlier = than >> two (2) weeks from now on April 4th. >>=20 >> Thanks, >>=20 >> Kyle Evans >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail = to"freebsd-current-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Mar 22 11:24:27 2018 Return-Path: Delivered-To: freebsd-current@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 51D81F5C216 for ; Thu, 22 Mar 2018 11:24:27 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C2F366EACB for ; Thu, 22 Mar 2018 11:24:26 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?utf-8?B?TSZTIC0gS3Jhc3puYWkgQW5kcsOhcw==?= To: Toomas Soome , FreeBSD Current Subject: RE: Call for Testing: UEFI Changes Thread-Topic: Call for Testing: UEFI Changes Thread-Index: AQHTwXezI18KWufRT0GhZAnzTjgx8aPb+R8AgAAKqYCAABLIMA== Date: Thu, 22 Mar 2018 11:09:15 +0000 Message-ID: <3cc35af8376840728a1af5f7836930f2@MSEXCH13.mands.hu> References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <901CE994-0A28-4538-A4A9-A23E0B7E4879@me.com> In-Reply-To: <901CE994-0A28-4538-A4A9-A23E0B7E4879@me.com> Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.4.90] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 11:24:27 -0000 SGkNCg0KSSBmb3VuZCB0aGlzIHByb2JsZW0gdG9kYXkgbW9ybmluZy4gRm9ydHVuYXRlbHkgSSBj YW4gY29weSB0aGUgZWZpLjR0aCBmaWxlIGJhY2sgdG8gL2Jvb3QgZnJvbSAvdXNyL3NyYy9zdGFu ZC9mb3J0aA0KDQpPbiB0aGUgb3RoZXIgaGFuZCwgcmVtb3ZpbmcgdGhlIHJlZmVyZW5jZSB0byBl ZmkuNHRoIGZyb20gbG9hZGVyLnJjIGNhdXNlcyB0aGUgYm9vdCBzdG9wIGF0IHRoZSBsb2FkZXIg cHJvbXB0DQoNCnJnZHMNCkFuZHLDoXMgS3Jhc3puYWkNCg0KDQotLS0tLUVyZWRldGkgw7x6ZW5l dC0tLS0tDQpGZWxhZMOzOiBvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcgW21haWx0 bzpvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmddIE1lZ2hhdGFsbWF6w7MgVG9vbWFz IFNvb21lDQpLw7xsZHZlOiAyMDE4LiBtw6FyY2l1cyAyMi4gMTE6NTINCkPDrW16ZXR0OiBGcmVl QlNEIEN1cnJlbnQNClTDoXJneTogUmU6IENhbGwgZm9yIFRlc3Rpbmc6IFVFRkkgQ2hhbmdlcw0K DQoNCg0KPiBPbiAyMiBNYXIgMjAxOCwgYXQgMTI6MTMsIEpha29iIEFsdmVybWFyayA8amFrb2JA YWx2ZXJtYXJrLm5ldD4gd3JvdGU6DQo+IA0KPiBIaSENCj4gDQo+IA0KPiBKdXN0IHVwZGF0ZWQg dG8gcjMzMTM0NS4NCj4gDQo+IFR3byBwcm9ibGVtczoNCj4gDQo+IDEuIGJvb3QvZWZpLjR0aCBp cyBhZGRlZCB0byAvdXNyL3NyYy9PYnNvbGV0ZUZpbGVzLmluYyBidXQgc3RpbGwgaW5jbHVkZWQg aW4gbG9hZGVyLnJjLiBMb2FkZXIgZmFpbHMgdG8gbG9hZCBpdCBhbmQgc3Vic2VxdWVudGx5IGZh aWxzIHRvIGxvYWQgbW9kdWxlcy4gUmVpbnN0YWxsaW5nIGVmaS40dGggcHJvYmxlbSAyIGFwcGVh cnMuDQo+IA0KPiANCj4gMi4gRml4aW5nIHByb2JsZW0gMSBhbmQgYWRkaW5nIGVmaXJ0X2xvYWQ9 IllFUyIgdG8gL2Jvb3QvbG9hZGVyLmNvbmYgDQo+IG1ha2VzIHRoZSBrZXJuZWwgcGFuaWMgaW5z dGFudGx5LiBQaG90byBvZiBwYW5pYzogDQo+IGh0dHBzOi8vcGhvdG9zLmFwcC5nb28uZ2wvcGgz eVF1a09BVWRRcHN2SzINCj4gDQo+IA0KPiBKYWtvYg0KDQpUaGUgZWZpLjR0aCB3YXMgaW50cm9k dWNlZCBhbmQgbGF0ZXIgcmVtb3ZlZCBieSBXYXJuZXIsIGEgYml0IHRvbyBoYXN0aWx5IHBlcmhh cHPigKYgYnV0IHBlcmhhcHMgaXQgaXMgYmV0dGVyIHRvIG5vdGUgdGhlIHBhcnRpYWwgcmV2ZXJ0 IG9mIHRoZSByZW1vdmFsIG9yIHNvbWV0aGluZyBsaWtlIHRoYXQ6KQ0KDQpyZ2RzLA0KdG9vbWFz DQoNCg0KPiANCj4gDQo+IE9uIDAzLzIyLzE4IDAxOjQ1LCBLeWxlIEV2YW5zIHdyb3RlOg0KPj4g SGVsbG8hDQo+PiANCj4+IEEgbnVtYmVyIG9mIGNoYW5nZXMgaGF2ZSBnb25lIGluIHJlY2VudGx5 IHBlcnRhaW5pbmcgdG8gVUVGSSBib290aW5nIA0KPj4gYW5kIFVFRkkgcnVudGltZSBzZXJ2aWNl cy4gVGhlIGNoYW5nZXMgd2l0aCB0aGUgbW9zdCBkYW1hZ2luZyANCj4+IHBvdGVudGlhbCBhcmU6 DQo+PiANCj4+IFdlIG5vdyBwdXQgVUVGSSBydW50aW1lIHNlcnZpY2VzIGludG8gdmlydHVhbCBh ZGRyZXNzIG1vZGUsIGZpeGluZyANCj4+IHJ1bnRpbWUgc2VydmljZXMgd2l0aCBVLUJvb3QvVUVG SSBhcyB3ZWxsIGFzIHRoZSBmaXJtd2FyZSANCj4+IGltcGxlbWVudGF0aW9uIGluIG1hbnkgTGVu b3Zvcy4gVGhlIHByZXZpb3VzbHkgb2JzZXJ2ZWQgYmVoYXZpb3Igd2FzIA0KPj4gYSBrZXJuZWwg cGFuaWMgdXBvbiBpbnZvY2F0aW9uIG9mIGVmaWJvb3RtZ3IvZWZpdmFyLCBvciBhIGtlcm5lbCAN Cj4+IHBhbmljIGp1c3QgbG9hZGluZyBlZmlydC5rbyBvciBjb21waWxpbmcgRUZJUlQgaW50byB0 aGUga2VybmVsLg0KPj4gDQo+PiBHcmFwaGljcyBtb2RlIHNlbGVjdGlvbiBpcyBub3cgZG9uZSBk aWZmZXJlbnRseSB0byBhdm9pZCByZWdyZXNzaW9uIA0KPj4gY2F1c2VkIGJ5IHIzMjcwNTggd2hp bGUgc3RpbGwgYWNoaWV2aW5nIHRoZSBzYW1lIGVmZmVjdC4gVGhlIG9ic2VydmVkIA0KPj4gcmVn cmVzc2lvbiB3YXMgdGhhdCB0aGUga2VybmVsIHdvdWxkIHVzdWFsbHkgZW5kIHVwIGRyYXdpbmcg DQo+PiBpbmNvcnJlY3RseSBhdCB0aGUgb2xkIHJlc29sdXRpb24gb24gYSBzdWJzZXQgb2YgdGhl IHNjcmVlbiwgZHVlIHRvIA0KPj4gaW5jb3JyZWN0IGZyYW1lYnVmZmVyIGluZm9ybWF0aW9uLg0K Pj4gDQo+PiBFeHBsaWNpdCB0ZXN0aW5nIG9mIHRoZXNlIGNoYW5nZXMsIHRoZSBsYXRlc3Qgb2Yg d2hpY2ggaGFwcGVuZWQgaW4gDQo+PiByMzMxMzI2LCBhbmQgYW55IGZlZWRiYWNrIGZyb20gdGhp cyB0ZXN0aW5nIHdvdWxkIGJlIGdyZWF0bHkgDQo+PiBhcHByZWNpYXRlZC4gVGVzdGluZyBzaG91 bGQgYmUgZG9uZSB3aXRoIGVpdGhlciBgb3B0aW9ucyBFRklSVGAgaW4gDQo+PiB5b3VyIGtlcm5l bCBjb25maWcgb3IgZWZpcnQua28gbG9hZGVkIGFsb25nIHdpdGggdXBkYXRlZCBib290bG9hZGVy IA0KPj4gYml0cy4NCj4+IA0KPj4gSSBvdGhlcndpc2UgcGxhbiB0byBNRkMgY29tbWl0cyBpbnZv bHZlZCB3aXRoIHRoZSBhYm92ZS1tZW50aW9uZWQgDQo+PiBjaGFuZ2VzIGJ5IHNvbWV0aW1lIGlu IHRoZSBmaXJzdCB3ZWVrIG9mIEFwcmlsLCBsaWtlbHkgbm8gZWFybGllciANCj4+IHRoYW4gdHdv ICgyKSB3ZWVrcyBmcm9tIG5vdyBvbiBBcHJpbCA0dGguDQo+PiANCj4+IFRoYW5rcywNCj4+IA0K Pj4gS3lsZSBFdmFucw0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18NCj4+IGZyZWVic2QtY3VycmVudEBmcmVlYnNkLm9yZyAgbWFpbGluZyBsaXN0IA0K Pj4gaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtY3Vy cmVudA0KPj4gVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8iZnJlZWJzZC1jdXJyZW50 LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX18NCj4gZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qub3JnIG1h aWxpbmcgbGlzdCANCj4gaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZv L2ZyZWVic2QtY3VycmVudA0KPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJl ZWJzZC1jdXJyZW50LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KDQpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qu b3JnIG1haWxpbmcgbGlzdCBodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGlu Zm8vZnJlZWJzZC1jdXJyZW50DQpUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJl ZWJzZC1jdXJyZW50LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0K From owner-freebsd-current@freebsd.org Thu Mar 22 12:12:29 2018 Return-Path: Delivered-To: freebsd-current@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 7616AF608D1 for ; Thu, 22 Mar 2018 12:12:29 +0000 (UTC) (envelope-from hyun@caffeinated.codes) 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 208FD71394 for ; Thu, 22 Mar 2018 12:12:28 +0000 (UTC) (envelope-from hyun@caffeinated.codes) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C09B420F5B; Thu, 22 Mar 2018 08:12:26 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute7.internal (MEProxy); Thu, 22 Mar 2018 08:12:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= caffeinated.codes; 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=fm1; bh=hEmczX 55bkVRAvV6k7//o96EHIo4EW3v+vvTKoovALY=; b=Qtqnwg+BaZYSgeM3Rtraiw Blgj4kALIu8c2dOTbpEbo5ezFrPfISgta78FyFVuZOMqna6u+rpSSiLfue6VZ4KD NgsZtjeKZKMImQ3UdCwWfX49wAJpxahbzISbdslZN9oEKibXEKfv+/twEU/uCQyg lulQ9W7vGsrdaGOf00S4jepNW0FJ8ruAQ/XBqPlCRJWLmOrH/2rjJIeReal2RVxg aYQOxYj3f+ce1ZAuPj4IJRrUeS/GqSYUv4SuWyEjTY+NGSpaJdXe/FIpLRmZ2kga vSCsckih65YR2QBxXOWCmdZdVfg88nP1rOa5JxCUNFZfppbFBXxmIHqTDTMwXMPw == 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=hEmczX 55bkVRAvV6k7//o96EHIo4EW3v+vvTKoovALY=; b=c9hK36j4ovR4iXCrr+EZKy X6PBN3I1vIp+Vh3FCB+6zR56jAb94jg7DEsbu3g0Mpyz4fu2kJE/Qy3YeUjGLWmo WZ/0oNM5J7fOOMAMk1b4PeHISsYcn+rA8zFQ+5HDoU0m7GvgPxHQ7DNo36hdKw63 zoog+iHzZBPDqxDbc/qdfoEsF2wSG/uMjFpNZ8gTBv5mEHerVUbQGzLQOa6XLqe2 a4rnfkH8zxJVGWByslBJLNPR6kLrSsK2uyqHCPrTkSr4mwwV0LFge2QFpHfqXBUi Up9ivL+vUEGsb9N87PCMOe24s/IdC0kGp2978TCRwdnapKobgjdax/e00cZgIiTg == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 99923940A0; Thu, 22 Mar 2018 08:12:26 -0400 (EDT) Message-Id: <1521720746.3254795.1312152432.3AC8FB5F@webmail.messagingengine.com> From: Hyun Hwang To: Warner Losh Cc: "Hartmann, O." , FreeBSD CURRENT MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ce6c4ba References: <20180321120710.4eb3b944@hermann> <1521686539.3047757.1311778784.3E60E604@webmail.messagingengine.com> Date: Thu, 22 Mar 2018 08:12:26 -0400 In-Reply-To: Subject: Re: CURRENT r331284: crashing with USB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 12:12:29 -0000 On Wednesday, March 21, 2018, 11:41 PM (UTC-0600), Warner Losh wrote: > Do you have a traceback? This I got from core.txt: ``` db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe000046e3c0 vpanic() at vpanic+0x18d/frame 0xfffffe000046e420 panic() at panic+0x43/frame 0xfffffe000046e480 dadone() at dadone+0x1cc9/frame 0xfffffe000046e9e0 xpt_done_process() at xpt_done_process+0x390/frame 0xfffffe000046ea20 xpt_done_td() at xpt_done_td+0xf6/frame 0xfffffe000046ea70 fork_exit() at fork_exit+0x84/frame 0xfffffe000046eab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000046eab0 ``` Is this suffice? Full dump is available [here](https://www.amazon.com/clouddrive/share/48KzBn0452wRk6bS56oDu1MGXG8p8ug7TGsj8yhGkKN) if you need. (I'll unshare this next month.) Also, judging by the stack trace, this problem looks very similar to [this](https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068900.html), I guess? > actually, can you test https://reviews.freebsd.org/D14792 for me please? I would love to and I can try, but... > I won't be able to test until Friday Same here, I cannot physically access the machine of interest until Friday. :( -- Hyun Hwang From owner-freebsd-current@freebsd.org Thu Mar 22 12:53:13 2018 Return-Path: Delivered-To: freebsd-current@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 903D1F63E7A for ; Thu, 22 Mar 2018 12:53:13 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 F31D172D68 for ; Thu, 22 Mar 2018 12:53:12 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id p142-v6so12964596lfd.6 for ; Thu, 22 Mar 2018 05:53:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=DHyiUIJU4htCApkSqynU+PI/fB4lCooQuNQZGZoT6Ig=; b=cicYpabAMt18xtY2ju9Vvu+peqs2IuP16+sRemeZGG8lHY51tpSMIS2VR1y3+ug8X5 W7OBhmNWG421lstyxUjeCN0FGU4aB0wS6/7ys3sVFcM9+gO98qp8NRI+VhIl8v35JArF qGPZPKT7Ug1uQkIbjWTjJiCQVez1+9OZT1A3gIGbf/FY8p9QpWhRyVuhwyj5N1BFBwZi gDAImG3GPY8d6AFkoK9uo3aOyOgSFqHvUNxn0hm4iwpmKzLdzfJQUZAObaw0OWNnC+gX Fh+8uV1ZRsnaroWT3qdMzSUSFydfWIh0drLMAiB0iD8oHtAQhg/1OokTGCysoj5LWeA9 NECg== X-Gm-Message-State: AElRT7EYouLnt1rjDVWtQ6ImCYMabRDvvqxWodOpdgjfSPXucyGxyr3n +aKh6kR9BRNsmIgJqV83Ryz+5UV9 X-Google-Smtp-Source: AG47ELuaOTsS/32N1FqSGlnlDfdt3DKZvfeQkgUXpobLbRnGn0jgc4mLkz/HcB//EEm79nELLR8WNg== X-Received: by 10.46.93.219 with SMTP id v88mr16147581lje.88.1521723190857; Thu, 22 Mar 2018 05:53:10 -0700 (PDT) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com. [209.85.215.45]) by smtp.gmail.com with ESMTPSA id l1sm1366605ljc.91.2018.03.22.05.53.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 05:53:10 -0700 (PDT) Received: by mail-lf0-f45.google.com with SMTP id x205-v6so12972299lfa.0 for ; Thu, 22 Mar 2018 05:53:10 -0700 (PDT) X-Received: by 2002:a19:e9cc:: with SMTP id j73-v6mr14764195lfk.99.1521723190415; Thu, 22 Mar 2018 05:53:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 05:52:49 -0700 (PDT) In-Reply-To: <3cc35af8376840728a1af5f7836930f2@MSEXCH13.mands.hu> References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <901CE994-0A28-4538-A4A9-A23E0B7E4879@me.com> <3cc35af8376840728a1af5f7836930f2@MSEXCH13.mands.hu> From: Kyle Evans Date: Thu, 22 Mar 2018 07:52:49 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: =?UTF-8?Q?M=26S_=2D_Krasznai_Andr=C3=A1s?= Cc: Toomas Soome , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 12:53:13 -0000 On Thu, Mar 22, 2018 at 6:09 AM, M&S - Krasznai Andr=C3=A1s wrote: >> -----Eredeti =C3=BCzenet----- >> Felad=C3=B3: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-cur= rent@freebsd.org] Meghatalmaz=C3=B3 Toomas Soome >> K=C3=BCldve: 2018. m=C3=A1rcius 22. 11:52 >> C=C3=ADmzett: FreeBSD Current >> T=C3=A1rgy: Re: Call for Testing: UEFI Changes >> >> >> >>> On 22 Mar 2018, at 12:13, Jakob Alvermark wrote: >>> >>> Hi! >>> >>> >>> Just updated to r331345. >>> >>> Two problems: >>> >>> 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still includ= ed in loader.rc. Loader fails to load it and subsequently fails to load mod= ules. Reinstalling efi.4th problem 2 appears. >>> >>> >>> 2. Fixing problem 1 and adding efirt_load=3D"YES" to /boot/loader.conf >>> makes the kernel panic instantly. Photo of panic: >>> https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 >>> >>> >>> Jakob >> >> The efi.4th was introduced and later removed by Warner, a bit too hastil= y perhaps=E2=80=A6 but perhaps it is better to note the partial revert of t= he removal or something like that:) >> >> rgds, >> toomas > > Hi > > I found this problem today morning. Fortunately I can copy the efi.4th fi= le back to /boot from /usr/src/stand/forth > > On the other hand, removing the reference to efi.4th from loader.rc cause= s the boot stop at the loader prompt > > rgds > Andr=C3=A1s Krasznai > Hi, efi.4th has been reinstated as of r331353- things should work a little more smoothly now. From owner-freebsd-current@freebsd.org Thu Mar 22 13:22:52 2018 Return-Path: Delivered-To: freebsd-current@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 02EE9F66AC6 for ; Thu, 22 Mar 2018 13:22:52 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) (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 623FC74391 for ; Thu, 22 Mar 2018 13:22:51 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f46.google.com with SMTP id a22-v6so13097740lfg.9 for ; Thu, 22 Mar 2018 06:22:51 -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=17hqci1DJIe3Fu6F8w1BIXgDtPiZf66XtZZas4KyK7g=; b=m6Db6WaC5o9OYMTCypuf6Ex8MmjVLAHOEOaaW6gHh43juZNSop0hzI0s3RX2Gotqgu xbjEV38vcEKquXnEMSDl2suKlkEdOkhvEwmLoW+Q2NADNNhWVfX5xrFSsPX2ry4YrK9N +ocgOaFCyK3EG8DqNz7nyuuNzV2BQLqyafvp0AxhTit4j4DVuBOIvZpjXME+vny7llal +xA1Rm/1wuABW4Cc/kKM03Hm3x08hCvnf84LODLWh0fmktNTgv//jV/7PJyKLR7Y5+Gh huqjKDnorfI77YXteVe6wWoVRR5kuuke8bL/U/RhaRxWEzhtzu804BIiYQoRunDaSorN C2AQ== X-Gm-Message-State: AElRT7Em0CRVx1ukX6jpt+r9BGAQAm2KkQ5Hc18YXgzkDX48Y7LZ2Pf0 wrWmkF/4Q/EGxbmzDzRlj+8AmIU2 X-Google-Smtp-Source: AG47ELuApeYWJTz2vaC9GoAliR/QhRspULhLfypqFQLCobYT//UokX+horKAsi4T6gl+fEMwik3veQ== X-Received: by 10.46.155.204 with SMTP id w12mr16150999ljj.76.1521724953953; Thu, 22 Mar 2018 06:22:33 -0700 (PDT) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com. [209.85.215.52]) by smtp.gmail.com with ESMTPSA id a139-v6sm56542lfa.36.2018.03.22.06.22.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 06:22:33 -0700 (PDT) Received: by mail-lf0-f52.google.com with SMTP id m16-v6so9373543lfc.4 for ; Thu, 22 Mar 2018 06:22:33 -0700 (PDT) X-Received: by 10.46.68.14 with SMTP id r14mr9135312lja.44.1521724953624; Thu, 22 Mar 2018 06:22:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 06:22:13 -0700 (PDT) In-Reply-To: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> From: Kyle Evans Date: Thu, 22 Mar 2018 08:22:13 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Jakob Alvermark Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 13:22:52 -0000 On Thu, Mar 22, 2018 at 5:13 AM, Jakob Alvermark wrote: > Hi! > > > Just updated to r331345. > > Two problems: > > 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still included in > loader.rc. Loader fails to load it and subsequently fails to load modules. > Reinstalling efi.4th problem 2 appears. > > > 2. Fixing problem 1 and adding efirt_load="YES" to /boot/loader.conf makes > the kernel panic instantly. Photo of panic: > https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 > > > Jakob > > Hi, The efi.4th removal has been reverted in r331353. A couple of inquiries for you: 1.) Before loading efirt, can you show me what `sysctl machdep.efi_map` looks like? 2.) After `kldload efirt` and getting a panic, can you show me what `show registers` looks like? 3.) Have you used efirt successfully before? Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Thu Mar 22 13:57:01 2018 Return-Path: Delivered-To: freebsd-current@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 3AD4FF698F4 for ; Thu, 22 Mar 2018 13:57:01 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85FC975BC4; Thu, 22 Mar 2018 13:57:00 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w2MDujG6028661; Thu, 22 Mar 2018 22:56:46 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 22 Mar 2018 22:56:44 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: kevans@freebsd.org, jakob@alvermark.net, andrew@FreeBSD.org Subject: Re: Call for Testing: UEFI Changes Message-Id: <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 13:57:01 -0000 Hi. For problem 2, try reverting r331241 alone. This worked for my ThinkPad T420. On Thu, 22 Mar 2018 08:22:13 -0500 Kyle Evans wrote: > On Thu, Mar 22, 2018 at 5:13 AM, Jakob Alvermark wrote: > > Hi! > > > > > > Just updated to r331345. > > > > Two problems: > > > > 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still included in > > loader.rc. Loader fails to load it and subsequently fails to load modules. > > Reinstalling efi.4th problem 2 appears. > > > > > > 2. Fixing problem 1 and adding efirt_load="YES" to /boot/loader.conf makes > > the kernel panic instantly. Photo of panic: > > https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 > > > > > > Jakob > > > > > > Hi, > > The efi.4th removal has been reverted in r331353. A couple of inquiries for you: > > 1.) Before loading efirt, can you show me what `sysctl > machdep.efi_map` looks like? > > 2.) After `kldload efirt` and getting a panic, can you show me what > `show registers` looks like? > > 3.) Have you used efirt successfully before? > > Thanks, > > Kyle Evans > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Thu Mar 22 15:16:52 2018 Return-Path: Delivered-To: freebsd-current@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 ED0B1F4D1E0 for ; Thu, 22 Mar 2018 15:16:51 +0000 (UTC) (envelope-from peter.lei@ieee.org) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6516079FF0 for ; Thu, 22 Mar 2018 15:16:51 +0000 (UTC) (envelope-from peter.lei@ieee.org) Received: by mail-wr0-x243.google.com with SMTP id z73so9097645wrb.0 for ; Thu, 22 Mar 2018 08:16:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=wj9GFPus7p2b4Km+Cgqd7c4FZTxAYpGQNqOpCZv3n+Q=; b=s+R+synJI+3GFT1sVXIdTkU8sEVz4SL6Fy1sTyBjr9IU5yGr5b+N6j4TjrvnzVqh8P K0Iv+W5XnkrvfMm1ESNonsGBt3u76WAW0oIBFT+PRxh+okhodLYTjZGRF9jcFPdSwHNo LnY1LI9rAQFsTKssezxnCriFtDcZRVkop56cW6d8+sg8HGmJ7eIchY/NTSLjqJtYj2eM zzY+GOXsCpLIzKEKG914os7enazDzwl0HBTrGn5hRE6g3p2WfkzfyvGCj/b+6xuRVYU2 a61ZtNPoe9M+eRAalKJxf4nZs8MRrKCsT2DpzZJpR7cX/o4l6XDzUozbUIdQOaCTDkF0 7IIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=wj9GFPus7p2b4Km+Cgqd7c4FZTxAYpGQNqOpCZv3n+Q=; b=rtjix1jH9GI60EviQUJuwZCHmOdfFEmyD6BbvaXMZ73dyhk2pE7302tRON/4XXUxmF 8/0j9jt6RxazQptQU20jGNX2PHB74cwaB/4d6rRgZcp/M+GhmjiM0SBFwNi764NCMjbp oHgddx2xsLfDF7AXoTaHUqOSbYihHnZmYPOZT9JNMs2wHWu+mFk16aWWjkdecrdAEnhs E9wW+2z4JqdbkJs6xXGlQo2X3qQDHZ0UTjDSetoNgD1O9Ry38Kt/1wifA/7tPTN78p7d Oe3mVTaP8n2sqpsqV2zLtdtQwBfYlNNFuFk+Oov+/T5BNfouN0kxTTAypv1o5vyaaZUD ADMA== X-Gm-Message-State: AElRT7EvFURIZTgU4uv1AM5GFUQKPwo0b82m5zZZprjSHSGuahtDW9tp QuZCqVncUO4nhmRqW6/I91fHEA== X-Google-Smtp-Source: AG47ELvurqEV2MS+fY2/dk+bbSJY8JoTo+cVQ31Un4bCR+62BhPhvLX2JqxTymP9fJpAQslvyGm0ww== X-Received: by 10.223.154.47 with SMTP id z44mr17367274wrb.239.1521731809608; Thu, 22 Mar 2018 08:16:49 -0700 (PDT) Received: from dhcp-9881.meeting.ietf.org ([2001:67c:1232:144:1082:5047:180:bd5b]) by smtp.gmail.com with ESMTPSA id x17sm8067311wrg.32.2018.03.22.08.16.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 08:16:48 -0700 (PDT) Subject: Re: Call for Testing: UEFI Changes To: Tomoaki AOKI , freebsd-current@freebsd.org Cc: kevans@freebsd.org, jakob@alvermark.net, andrew@FreeBSD.org References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> From: Peter Lei Message-ID: Date: Thu, 22 Mar 2018 10:16:47 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030307060002070201040400" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 15:16:52 -0000 This is a cryptographically signed message in MIME format. --------------ms030307060002070201040400 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 3/22/18 8:56 AM, Tomoaki AOKI wrote: > Hi. > For problem 2, try reverting r331241 alone. > This worked for my ThinkPad T420. I also hit this after updating to latest and was about to post when I saw this thread - I build efirt into the kernel and it's now doing a panic on boot. It appears to be due to this recent addition in dev/efidev/efirt.c by r33124= 1: > if (!efi_is_in_map(map, efihdr->memory_size / efihdr->descripto= r_size, > efihdr->descriptor_size, (vm_offset_t)efi_runtime->rt_getti= me)) { The faulting address is for "efi_runtime->rt_gettime" (and is still a phys addr here). --peter >=20 > On Thu, 22 Mar 2018 08:22:13 -0500 > Kyle Evans wrote: >=20 >> On Thu, Mar 22, 2018 at 5:13 AM, Jakob Alvermark = wrote: >>> Hi! >>> >>> >>> Just updated to r331345. >>> >>> Two problems: >>> >>> 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still incl= uded in >>> loader.rc. Loader fails to load it and subsequently fails to load mod= ules. >>> Reinstalling efi.4th problem 2 appears. >>> >>> >>> 2. Fixing problem 1 and adding efirt_load=3D"YES" to /boot/loader.con= f makes >>> the kernel panic instantly. Photo of panic: >>> https://photos.app.goo.gl/ph3yQukOAUdQpsvK2 >>> >>> >>> Jakob >>> >>> >> >> Hi, >> >> The efi.4th removal has been reverted in r331353. A couple of inquirie= s for you: >> >> 1.) Before loading efirt, can you show me what `sysctl >> machdep.efi_map` looks like? >> >> 2.) After `kldload efirt` and getting a panic, can you show me what >> `show registers` looks like? >> >> 3.) Have you used efirt successfully before? >> >> Thanks, >> >> Kyle Evans >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.= org" >> >=20 >=20 --------------ms030307060002070201040400 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC Cx4wggUwMIIEGKADAgECAhEA5uRbT5dO2Nji0P2d3zpsSDANBgkqhkiG9w0BAQsFADCBlzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0Eg Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTcxMTA5MDAw MDAwWhcNMTgxMTA5MjM1OTU5WjAjMSEwHwYJKoZIhvcNAQkBFhJwZXRlci5sZWlAaWVlZS5v cmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCxBMAPv3y1gA/CpG9WGm3dIJR9 2ch1Vk4InSVWXHV11mt1j2gNajK8Sa+IyPSf4/xeP/MQfkworYIM2n0Ob5F6/t2oNS4w/G2y 0CaCSxQAtbk46wKKErx20t4s4ODDs3YXzf38juNMB93YCVhFrs8jyKP1/Y7RwkjaKrRF8KBK PxHUcqxhZir3TjOJtu2P2STWtPD2fRpRkvN+gEh2ejd+n1HHBst/9Rtz0vb8yHFWl1n1YISi KQOXT73a0MFrdFGYlJwvoZJZWmV7XGthlLGt7h41f01Ug91eKY19XB3K6CmZLdiwy/6Ir8nG QMC0OH7LcudUfbu6wk7MY+ceTO4PAgMBAAGjggHoMIIB5DAfBgNVHSMEGDAWgBSCr2yM+MX+ lmF86B89K3FIXsSLwDAdBgNVHQ4EFgQU9tUteyjHW7DsqMhulCpoaT1DlQMwDgYDVR0PAQH/ BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUC MBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsG AQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBaBgNVHR8EUzBRME+gTaBL hklodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9SU0FDbGllbnRBdXRoZW50aWNhdGlv bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGLBggrBgEFBQcBAQR/MH0wVQYIKwYBBQUHMAKGSWh0 dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET1JTQUNsaWVudEF1dGhlbnRpY2F0aW9uYW5k U2VjdXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNv bTAdBgNVHREEFjAUgRJwZXRlci5sZWlAaWVlZS5vcmcwDQYJKoZIhvcNAQELBQADggEBAHBU iY1f7LKqo0sQAs/YRvlvL2ydz+9oCDf6BNnyTjDXOiET4D2t5kMh0fceGKhlpfAOA47Nob1s MNS+6sjOqEm8e10SjVv69dq6ZmjFVqTZ1MZjt1Mmi7XpsNYiLE66dF9Ff0ne8bHhcqHVHtFT 6MU7Fq1N8r5mnqCB7zPxuDYV9DprrnOYm2g68CRVGsKhH5kYSsYogMQpxgZ5PP0gdnpfKV+X ROtXTpZg4Ln6WCaeGh5oVdCw095af07hIG8F9VM559N8jv4Z9/R5MsrM6AfwJvXmVUQ9XGKk qZw0MUbf8FQCS928I3h111Ur5zap+rXiu+lJ4cI6T6/h3p3TdCswggXmMIIDzqADAgECAhBq m+E4O/8ra58B1dm4p1JWMA0GCSqGSIb3DQEBDAUAMIGFMQswCQYDVQQGEwJHQjEbMBkGA1UE CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P RE8gQ0EgTGltaXRlZDErMCkGA1UEAxMiQ09NT0RPIFJTQSBDZXJ0aWZpY2F0aW9uIEF1dGhv cml0eTAeFw0xMzAxMTAwMDAwMDBaFw0yODAxMDkyMzU5NTlaMIGXMQswCQYDVQQGEwJHQjEb MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK ExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAL6znlesKHZ1QBbHOAOY08YYdiFQ8yV5C0y1oNF9Olg+nKcxLqf2NHbZhGra0D00 SOTq9bus3/mxgUsg/Wh/eXQ0pnp8tZ8XZWAnlyKMpjL+qUByRjXCA6RQyDMqVaVUkbIr5SU0 RDX/kSsKwer3H1pT/HUrBN0X8sKtPTdGX8XAWt/VdMLBrZBlgvnkCos+KQWWCo63OTTqRvaq 8aWccm+KOMjTcE6s2mj6RkalweyDI7X+7U5lNo6jzC8RTXtVV4/Vwdax720YpMPJQaDaElmO upyTf1Qib+cpukNJnQmwygjD8m046DQkLnpXNCAGjuJy1F5NATksUsbfJAr7FLUCAwEAAaOC ATwwggE4MB8GA1UdIwQYMBaAFLuvfgI9+qbxPISOre44mOzZMjLUMB0GA1UdDgQWBBSCr2yM +MX+lmF86B89K3FIXsSLwDAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAR BgNVHSAECjAIMAYGBFUdIAAwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL2NybC5jb21vZG9j YS5jb20vQ09NT0RPUlNBQ2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcmwwcQYIKwYBBQUHAQEE ZTBjMDsGCCsGAQUFBzAChi9odHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9SU0FBZGRU cnVzdENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMA0GCSqG SIb3DQEBDAUAA4ICAQB4XLKBKDRPPO5fVs6fl1bsj6JrF/bz9kkIBtTYLzXN30D+03Hj6OxC DBEaIeNmsBhrJmuubvyE7HtoSmR809AgcYboW+rcTNZ/8u/Hv+GTrNI/AhqX2/kiQNxmgUPt /eJPs92Qclj0HnVyy9TnSvGkSDU7I5Px+TbO+88G4zipA2psZaWeEykgzClZlPz1FjTCkk77 ZXp5cQYYexE6zeeN4/0OqqoAloFrjAF4o50YJafX8mnahjp3I2Y2mkjhk0xQfhNqbzlLWPoT 3m7j7U26u7zg6swjOq8hITYc3/np5tM5aVyu6t99p17bTbY7+1RTWBviN9YJzK8HxzObXYWB f/L+VGOYNsQDTxAk0Hbvb1j6KjUhg7fO294F29QIhhmiNOr84JHoy+fNLpfvYc/Q9EtFOI5I SYgOxLk3nD/whbUe9rmEQXLp8MB933Ij474gwwCPUpwv9mj2PMnXoc7mbrS22XUSeTwxCTP9 bcmUdp4jmIoWfhQm7X9w/Zgddg+JZ/YnIHOwsGsaTUgj7fIvxqith7DoJC91WJ8Lce3CVJqb 1XWeKIJ84F7YLXZN0oa7TktYgDdmQVxYkZo1c5noaDKH9Oq9cbm/vOYRUM1cWcef20Wkyk5S /GFyyPJwG0fR1nRas3DqAf4cXxMiEKcff7PNa4M3RGTqH0pWR8p6EjGCBDgwggQ0AgEBMIGt MIGXMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQH EwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RP IFJTQSBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAObkW0+X TtjY4tD9nd86bEgwDQYJYIZIAWUDBAIBBQCgggJbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE4MDMyMjE1MTY0N1owLwYJKoZIhvcNAQkEMSIEINHH1O/j Bgh6HrfGdJGEibj4NQ8xolnyqkibgY4Jim24MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUD BAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgb4GCSsGAQQBgjcQBDGBsDCBrTCBlzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0Eg Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDm5FtPl07Y2OLQ /Z3fOmxIMIHABgsqhkiG9w0BCRACCzGBsKCBrTCBlzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP IENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhlbnRpY2F0aW9u IGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDm5FtPl07Y2OLQ/Z3fOmxIMA0GCSqGSIb3DQEBAQUA BIIBAHe6aYBFkbTTPD8+mY6z9f37wm2HOyo4fvyrA9TOaEKcPWiCvsf7JiP9d2z2OGuvf9+e bmOeHVcErvrZc0Ka8bFgGqct49mK/j9W19b/mq91g7NMQBlmy82PXscZokSaKA0gUs3qQL5X nf/us8IfdIar4ej9pkCYGvuRcgvetGsItq2Q95NJ60enifYYc1ecnxfcQrtMkJgJEn9H+UaJ 09u8JFH6oWFE2LMl6SQP1o01aV76o5XX6Mvt7+RnWF+Nt11MEFPcrcnHJB4YjGfJl8o37MKo cg3UfGUrAsqBM3AQkOBonLP56ABpEtRAamHO8FwgVwlq9WUrcMoHWHN1T3QAAAAAAAA= --------------ms030307060002070201040400-- From owner-freebsd-current@freebsd.org Thu Mar 22 15:35:03 2018 Return-Path: Delivered-To: freebsd-current@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 ED97DF4F197 for ; Thu, 22 Mar 2018 15:35:02 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f68.google.com (mail-lf0-f68.google.com [209.85.215.68]) (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 611B67B595; Thu, 22 Mar 2018 15:35:02 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f68.google.com with SMTP id g203-v6so13791522lfg.11; Thu, 22 Mar 2018 08:35:02 -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=9LmCpWlIRw6dWleZvPdm2YoZyQ2Snsc5YEI9kQzvLdc=; b=D9C9q75cZZQMAU+d0GOs00NB/hZtcgLi2J8PlxfYASMQh+y3Yw1QbSUVxu2UnLNzgN E+/oAAyRl5k6k5s5uozG5SycxuYvOSGspNycLKa7ErRdeX0417KchsVZbQSuhXfkdGNT dFbaxQ9jR2AuvElALKsgwVODna6UXg0jzK5Bc1bYLgDgMl31OTk7HDY7+EfWahdQMFZ1 oc82YvXZkP07H4L7/nV+YjvFGZCKNYmdVtVowHzSNzMiEgppcxC2jilps89H1H6MrGGA +Lpjw9C7BgjftPmYpJhgEPqy74AkLTJjT6gO6lUe5JEiSgWzc6ukoo3tnw4No8xWC9T4 vwcA== X-Gm-Message-State: AElRT7Fso/eGGVrtiNno4XWkZrueNz0KYqy0Rupqg1d7lqCSHxStGbWY YeWAPRfhGsgjzc/YtzziFoLGNTKS X-Google-Smtp-Source: AG47ELtZr5ARiUK6tOkdfu6OLChcmkkhykWNRGoQUxKI0iOjfpGpmOGbDJKdwvhcWx4Xmp5GphzrWQ== X-Received: by 2002:a19:a003:: with SMTP id j3-v6mr16386895lfe.8.1521732894635; Thu, 22 Mar 2018 08:34:54 -0700 (PDT) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com. [209.85.215.41]) by smtp.gmail.com with ESMTPSA id o88-v6sm1702523lfg.34.2018.03.22.08.34.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 08:34:54 -0700 (PDT) Received: by mail-lf0-f41.google.com with SMTP id a22-v6so13796633lfg.9; Thu, 22 Mar 2018 08:34:54 -0700 (PDT) X-Received: by 2002:a19:e9cc:: with SMTP id j73-v6mr15143039lfk.99.1521732894233; Thu, 22 Mar 2018 08:34:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 08:34:33 -0700 (PDT) In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> From: Kyle Evans Date: Thu, 22 Mar 2018 10:34:33 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Kyle Evans Cc: Peter Lei , Tomoaki AOKI , FreeBSD Current , Jakob Alvermark , Andrew Turner Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 15:35:03 -0000 On Thu, Mar 22, 2018 at 10:18 AM, Kyle Evans wrote: > On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei wrote: >> On 3/22/18 8:56 AM, Tomoaki AOKI wrote: >>> Hi. >>> For problem 2, try reverting r331241 alone. >>> This worked for my ThinkPad T420. >> >> >> I also hit this after updating to latest and was about to post when I >> saw this thread - >> >> I build efirt into the kernel and it's now doing a panic on boot. It >> appears to be due to this recent addition in dev/efidev/efirt.c by r331241: >> >>> if (!efi_is_in_map(map, efihdr->memory_size / efihdr->descriptor_size, >>> efihdr->descriptor_size, (vm_offset_t)efi_runtime->rt_gettime)) { >> >> The faulting address is for "efi_runtime->rt_gettime" (and is still a >> phys addr here). >> > > The following patch [1] (I can't guarantee how long he'll keep it > available there) should fix this class of problems. > > [1] https://people.freebsd.org/~andrew/0001-Enter-into-the-EFI-environment-before-check-the-GetT.patch Now committed as of r331361. From owner-freebsd-current@freebsd.org Thu Mar 22 15:42:44 2018 Return-Path: Delivered-To: freebsd-current@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 EA18BF4FE7F for ; Thu, 22 Mar 2018 15:42:43 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (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 57F287BEDB; Thu, 22 Mar 2018 15:42:43 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f67.google.com with SMTP id m16-v6so10112727lfc.4; Thu, 22 Mar 2018 08:42:43 -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=+gJE8RuPPwInlc79Ifp/DIU6aBXEbY54l8eDdSl3D5A=; b=H+3RPgKkVTC2jAtfYu2/UvnmzpppyXALRvAlAXIrdetdnFy3Yfgnd7WNmARKYef96+ y+LYj4RkhebvNXmX3hLUP/RCbirVg43xsMIwj3f1zyP8GXkxh5WzLx5RBwMMyM6BCajX PDqGAd+6m6+EheDmCFbR3f5C06suUeoKxwn7DcABwrX4NQ9LjiM77Gd9xAq//6ftAYzc rBE2PxreQW9j4q4W/FjixUteir+TMVk0qL/6nLz0bfzdzQ32De7ALaosT7yKg8EEdmLr 7A4m/FxeeIltcq0wzDE0tYc2XLnEX4UCpKgKeo3/yRxSSyR43Oz2piImihTIoM6dYn6z xShA== X-Gm-Message-State: AElRT7G0XoI1d/7bmHU0nA7W1UyW2ywCve/zS5AEEleqA9P8xm4iZW45 dyXqKrDN9ywoH6YDAszwYE3izELq X-Google-Smtp-Source: AG47ELvIjiijj15wkq8Kqk2Pvogsi46Y04zib8DiVQT3tb2P1JBFmEeVulpzeRbIQBJIfl1SUwUbFQ== X-Received: by 10.46.137.13 with SMTP id d13mr10138743lji.27.1521731934747; Thu, 22 Mar 2018 08:18:54 -0700 (PDT) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com. [209.85.215.41]) by smtp.gmail.com with ESMTPSA id o8sm1442057ljj.42.2018.03.22.08.18.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 08:18:54 -0700 (PDT) Received: by mail-lf0-f41.google.com with SMTP id l4-v6so9395333lfg.12; Thu, 22 Mar 2018 08:18:54 -0700 (PDT) X-Received: by 2002:a19:6919:: with SMTP id e25-v6mr16630216lfc.52.1521731934438; Thu, 22 Mar 2018 08:18:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 08:18:33 -0700 (PDT) In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> From: Kyle Evans Date: Thu, 22 Mar 2018 10:18:33 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Peter Lei Cc: Tomoaki AOKI , FreeBSD Current , Jakob Alvermark , Andrew Turner Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 15:42:44 -0000 On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei wrote: > On 3/22/18 8:56 AM, Tomoaki AOKI wrote: >> Hi. >> For problem 2, try reverting r331241 alone. >> This worked for my ThinkPad T420. > > > I also hit this after updating to latest and was about to post when I > saw this thread - > > I build efirt into the kernel and it's now doing a panic on boot. It > appears to be due to this recent addition in dev/efidev/efirt.c by r331241: > >> if (!efi_is_in_map(map, efihdr->memory_size / efihdr->descriptor_size, >> efihdr->descriptor_size, (vm_offset_t)efi_runtime->rt_gettime)) { > > The faulting address is for "efi_runtime->rt_gettime" (and is still a > phys addr here). > The following patch [1] (I can't guarantee how long he'll keep it available there) should fix this class of problems. [1] https://people.freebsd.org/~andrew/0001-Enter-into-the-EFI-environment-before-check-the-GetT.patch From owner-freebsd-current@freebsd.org Thu Mar 22 16:56:18 2018 Return-Path: Delivered-To: freebsd-current@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 3DDE5F56562 for ; Thu, 22 Mar 2018 16:56:18 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 CB8517F346; Thu, 22 Mar 2018 16:56:17 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mail-qk0-x22e.google.com with SMTP id b198so9938697qkg.9; Thu, 22 Mar 2018 09:56:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=rRi5P1n1w7H2iZtA+huxdqREkuK2U+TYaQ2zmo7ZG98=; b=p2cPPzSJc8Gw5g9GfgEodcc4e57q+C+gDtO1HoBSlGMGxoItfnqtq1Sq+l537s5G/5 WGqfjF9vITE5T+2pW+Nc+qM9jhYa7k8a+25Gwd6I+5fdgII4w/7Q7ClUqs5xkkRT8vPE bOdNhX6kpHA9c23t4qSBl6S+aCAg/hcDibYRG2/Ec0SjAC1msnC8fF/xBrBhZxCwBSKS 5asHWR6Krf9N8c67OncBbpgvCFC1VGeiGcD039t67+uQLfEusu3dHklWSrVDQhLqLwU/ NDdbBi/Moj9w2OBx8n2makc+6gdC7y6Tb4Q6sBBp/UQSkIabO8wxtTYfi+Ndf1ijBwDD 3mEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rRi5P1n1w7H2iZtA+huxdqREkuK2U+TYaQ2zmo7ZG98=; b=E16w6X1GXURDBCPxiBZKlwGpUeqRP+FjAAgtm4D5SN6SkZ3YGkvDmgPpLSUYVQ2UKB SRUnhC34MBmQ1qFCh73vEX0BovpD7v1JInvQ8J4kK7xeZXHECfJsOSy9J8CaP6vAf3Et PdQ9tLGFnsg1AZ00gxyWLrGzkmN3kAZrniMfzRIk5SnjGerjaJtojqAY01u20Zdrll5+ 1GR6eiePuriwUN39EGlQRCksIbzEHOiFHV6FN89zuXH8xjKMzh/zfrfMC1FWSU7io6Ij LvaEEd2VDS7NCurNoODmmys6mtaSz4F8jwOvfBUPB+hVj2vT/dn5uKQXhUcB2kAbbFpo pPhg== X-Gm-Message-State: AElRT7HxcGoVt5KCXsGe95rWUzvrnb7J4cTBfPra1WBerknlPceJzt8K py+DMfb9PBtSSNsaVe7PO+349HJP X-Google-Smtp-Source: AG47ELs5SmCFEpQ0g8R1CtE1ptEEjA/eWNm9tTIfgplkNSPrcG+fhHnJkHa4nJLcFD0aW2wGJSGOug== X-Received: by 10.55.87.134 with SMTP id l128mr34245240qkb.162.1521737776925; Thu, 22 Mar 2018 09:56:16 -0700 (PDT) Received: from mbp-eth.home ([177.53.86.172]) by smtp.gmail.com with ESMTPSA id u57sm2456883qtc.8.2018.03.22.09.56.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 09:56:15 -0700 (PDT) Subject: Re: Call for Testing: UEFI Changes To: Kyle Evans , FreeBSD Current References: From: Renato Botelho Message-ID: <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com> Date: Thu, 22 Mar 2018 13:56:11 -0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; 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-US Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 22 Mar 2018 17:24:21 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 16:56:18 -0000 On 21/03/18 21:45, Kyle Evans wrote: > Hello! > > A number of changes have gone in recently pertaining to UEFI booting > and UEFI runtime services. The changes with the most damaging > potential are: > > We now put UEFI runtime services into virtual address mode, fixing > runtime services with U-Boot/UEFI as well as the firmware > implementation in many Lenovos. The previously observed behavior was a > kernel panic upon invocation of efibootmgr/efivar, or a kernel panic > just loading efirt.ko or compiling EFIRT into the kernel. > > Graphics mode selection is now done differently to avoid regression > caused by r327058 while still achieving the same effect. The observed > regression was that the kernel would usually end up drawing > incorrectly at the old resolution on a subset of the screen, due to > incorrect framebuffer information. > > Explicit testing of these changes, the latest of which happened in > r331326, and any feedback from this testing would be greatly > appreciated. Testing should be done with either `options EFIRT` in > your kernel config or efirt.ko loaded along with updated bootloader > bits. > > I otherwise plan to MFC commits involved with the above-mentioned > changes by sometime in the first week of April, likely no earlier than > two (2) weeks from now on April 4th. Just FYI, After upgrade to r331350 on a Thinkpad X230 using drm-next-kmod trackpoint stopped working and touchpad worked but 3 buttons above it didn't. Removing drm-next-kmod and start using i915kms.ko from /boot/kernel fixed it. -- Renato Botelho From owner-freebsd-current@freebsd.org Thu Mar 22 18:06:28 2018 Return-Path: Delivered-To: freebsd-current@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 3CD50F5C839; Thu, 22 Mar 2018 18:06:28 +0000 (UTC) (envelope-from benno@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB16D82A57; Thu, 22 Mar 2018 18:06:27 +0000 (UTC) (envelope-from benno@FreeBSD.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 30719212FC; Thu, 22 Mar 2018 14:06:27 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 22 Mar 2018 14:06:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=Qaut5wpHUXQybnEn2D3nXQE5yxEjffS0cgy6YPt1erU=; b=mSX/Cq4h GbFqzJ9EIHSIqO9+D0uxdZj4l8TwhvGWrA7xC/QaFAphFDLhvHd+74GkjJlteiNp wRIXVoCaNUGPn4Vp7wSYJknvfrcB8zARzdmisgz6kOFmI3UtSMI6ArO4sOASUPOh PDUJaUv5kzqXqjxe6WV5STBqW/NVzs5DXwzNDqLxU28WBZTS4jqUjttEIrqzh5bk CeILK8A0yLbsPY8xYhKXJnftSNYk4WQnBnb+RzUYakona4D+OunwqxEUMvduOIi9 oQ5cLhCLzS2c/JmGJJOVKO8dp1X1lnlEPXsFdPL7bluo1nMpFYcmiGFodRFqm2Iu ceVHKJ92JGJAyQ== X-ME-Sender: Received: from [10.57.105.205] (unknown [209.63.143.172]) by mail.messagingengine.com (Postfix) with ESMTPA id 7563F240DC; Thu, 22 Mar 2018 14:06:26 -0400 (EDT) From: Benno Rice Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Testing requested: Hybrid ISO/USB boot Message-Id: Date: Thu, 22 Mar 2018 11:06:24 -0700 To: FreeBSD Current , freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 18:06:28 -0000 Hello all! I=E2=80=99ve been working on the ability to create hybrid ISO/HDD boot = images for x86, a la what Linux systems do with ISOHYBRID. The general = theory seems to be that ISO images have a 32KB hunk of zeroes at the = front that they generally ignore so we=E2=80=99ll stick something in = there that can handle booting if need be. The cases generally break down = as follows: UEFI with CD: Boots using an EFI system partition embedded in the ISO = image. This loads loader, and so on. UEFI with HDD: Same as above as UEFI doesn=E2=80=99t really care what = the underlying medium is and it sees the ISO image. Legacy BIOS with CD: Boots using El Torrito as always. And now for the new part: Legacy BIOS with HDD: Sees a DOS MBR stuck in the 32KB at the front of = the ISO image. This MBR contains our MBR boot code, which sees an active = BSD slice containing a variant of our BSD boot code that reads from the = ISO filesystem instead of UFS. This finds loader in the ISO filesystem = and loads that. Loader has had support for reading ISO9660 images off = HDDs added. Everything continues normally after that. The review for these changes is here: https://reviews.freebsd.org/D14799 And a version of the standard =E2=80=9Cbootonly=E2=80=9D ISO image built = with these changes is here: https://people.freebsd.org/~benno/hybrid-bootonly.iso.xz = I=E2=80=99ve tested this image under qemu and VMware under all four of = the BIOS/UEFI and CD/HDD combinations. I=E2=80=99ve also booted a system = build around an Asus X399 Prime motherboard with this dd=E2=80=99ed to a = USB stick. I=E2=80=99d love some testing on more systems, especially = things that are more likely to have more customized boot firmwares = (I=E2=80=99m thinking Dell, HP, etc). Many thanks, Benno.= From owner-freebsd-current@freebsd.org Thu Mar 22 20:09:43 2018 Return-Path: Delivered-To: freebsd-current@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 8CAC7F67524 for ; Thu, 22 Mar 2018 20:09:43 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 EEE1D68FF6 for ; Thu, 22 Mar 2018 20:09:42 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id x205-v6so15059391lfa.0 for ; Thu, 22 Mar 2018 13:09:42 -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=Sk58a/O4up+eSCX+himeXM+3mg+KDOH0N64ir+MLF/A=; b=j6wGAsjeoSxI5vWUKYaUgGN0TnqX4yNhhaLDWHL0Rv5cnCEmX9F0D1T1jZ+J3Ce35j s79NzekH8BehuxseXbSsyCtBmUA/l6tn/D0gQBn5uBPjv0kTU9GYXnqUioc26s/jMSe2 sIYRFiEWWri+XuqxfjzZ4CKrjXDGIUiYRWlmnl0xzw6qn2mymGxIa8Cm3ZIc7amA9wKe BYHCJMelyR/nizlQ9hlqDlKrsmgIo/jGpAE775Iv025HxYA7f5HZHOW5tgTG1w6kRB7X T0rtqnGtPpn2AsCEkCrGttgCRy3X8TwNeG4M08TIu2GsCvtj3F89pGTO43698MZKOZeg GW9w== X-Gm-Message-State: AElRT7GRSWx0oGQiwu/8L0dqYy3t5MU6VLORutELqM13Dwxtxl7Mc5FF XA9Dy2bUfAsaj0nUoIrUOxrrz9KXFLo= X-Google-Smtp-Source: AG47ELvVEtcLXcy7ZqsMOT0iJfh/SCS/U5Crda1m+qz1rLK11BgHcjh0u5+aHjEYBtMidXl7MdGwcA== X-Received: by 10.46.128.132 with SMTP id i4mr11508722ljg.51.1521749380714; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com. [209.85.215.46]) by smtp.gmail.com with ESMTPSA id u15sm1533901ljj.9.2018.03.22.13.09.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 13:09:40 -0700 (PDT) Received: by mail-lf0-f46.google.com with SMTP id c78-v6so10367189lfh.1 for ; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) X-Received: by 2002:a19:9e95:: with SMTP id h143-v6mr18556614lfe.129.1521749380282; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 13:09:19 -0700 (PDT) In-Reply-To: <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com> References: <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com> From: Kyle Evans Date: Thu, 22 Mar 2018 15:09:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Renato Botelho Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 20:09:43 -0000 On Thu, Mar 22, 2018 at 11:56 AM, Renato Botelho wrote: > On 21/03/18 21:45, Kyle Evans wrote: >> Hello! >> >> A number of changes have gone in recently pertaining to UEFI booting >> and UEFI runtime services. The changes with the most damaging >> potential are: >> >> We now put UEFI runtime services into virtual address mode, fixing >> runtime services with U-Boot/UEFI as well as the firmware >> implementation in many Lenovos. The previously observed behavior was a >> kernel panic upon invocation of efibootmgr/efivar, or a kernel panic >> just loading efirt.ko or compiling EFIRT into the kernel. >> >> Graphics mode selection is now done differently to avoid regression >> caused by r327058 while still achieving the same effect. The observed >> regression was that the kernel would usually end up drawing >> incorrectly at the old resolution on a subset of the screen, due to >> incorrect framebuffer information. >> >> Explicit testing of these changes, the latest of which happened in >> r331326, and any feedback from this testing would be greatly >> appreciated. Testing should be done with either `options EFIRT` in >> your kernel config or efirt.ko loaded along with updated bootloader >> bits. >> >> I otherwise plan to MFC commits involved with the above-mentioned >> changes by sometime in the first week of April, likely no earlier than >> two (2) weeks from now on April 4th. > > Just FYI, > > After upgrade to r331350 on a Thinkpad X230 using drm-next-kmod > trackpoint stopped working and touchpad worked but 3 buttons above it > didn't. Removing drm-next-kmod and start using i915kms.ko from > /boot/kernel fixed it. > I tend to think that's probably unrelated to the things I've poked- I can't quite imagine how I might have broken it =/. Any chance you can bissect that to the exact commit? Thanks! Kyle Evans From owner-freebsd-current@freebsd.org Thu Mar 22 20:50:40 2018 Return-Path: Delivered-To: freebsd-current@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 410D1F6AA78; Thu, 22 Mar 2018 20:50:40 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FF4B6AEB6; Thu, 22 Mar 2018 20:50:39 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from scdbackup.webframe.org ([91.8.164.220]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MPUFR-1euyIQ298D-004iSk; Thu, 22 Mar 2018 21:50:31 +0100 Date: Thu, 22 Mar 2018 21:48:42 +0100 From: "Thomas Schmitt" To: freebsd-hackers@freebsd.org Subject: Re: Testing requested: Hybrid ISO/USB boot Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org References: In-Reply-To: Message-Id: <3373772881814803857@scdbackup.webframe.org> X-Provags-ID: V03:K0:X2ZuHSvTFNxirIwoIzSyYKMMq5K0YJ4wwI8UKwoxNR1XGIClnvj dhbogVGwnXVFgNJxOMxLHU//hh6Dz1q8AKcmTOXa9EvUCyzTmSsGrPtF6vaWcO5t4fjjz2L 25uxTAMKPE7ofu1IWH/pavoRY1KkpXTfbVOr+gN+bv7cjPHae+tlqEikRUOmHqw3KZXIXG0 s+lzRbF2DR5U3V/eWI60A== X-UI-Out-Filterresults: notjunk:1;V01:K0:6BNIbhrnOSU=:DV0JCJBopVIsUjCu1b1DD6 dtLU5n4ZumsjMr3J4S9H7c0DWnv0GigAHsNEWniN7MOYxG4wOQgVkmLirRHgoT/+xPE5FgVG2 0+0e2ghhxC6XYSUpE/xvCY1Crl6wicmSBtlyPGfcdqn9urTqV+tOBS6QffP93KwOXQrEJj6CA 4KvsQxbPdi6Z8lqazEst2Y8l1iIWQDjaVVWTSJv4kNkkirUns985riIYKy5QV9SU7Ijdn5Cla bXuIxopVBzyolDDOUytftrtV6lkCTNr1obW843VKONpNssX1xwzYn2nzTADTxzp50TPiRxQig dMw41nCiPzg8FAimRvCC5pFTUmeOANSJZ9P/j+vVQIphB/X7VonD+TMAd8og/yD8LOhR+yw8I hiPLqo1Q63MmX3L7TM3fpPDscalhXUyRSfro3+Txchw2Tzlfc9x31qcmGoQxEZn1ouassmxTu Y5qDlPWfwUBN4Z9s/K46CkNPsoZNugoOa76AZo9CR4W/44Gc4GYOQ4w2nckMjbvUoyMz60Jac fuj5u8SEvDwS7IuGu+1oy2Kn8nqGkT1enrUrEdWWIhsTfC6JEw37g6ekwRYHbIYHeIhV3JsfN FeJJelm3Uo/jBV4PUMyF8W/O7HQ6205Ai6JHB6+XAFyfjKoGfqSJjCmBRg+NUHg5Th/HpARaP 4O7jES1cec1iiggLvlvUTAS8k003L2fm3tjl0xQH+N2WdE9VVqiGlKj/Odo0zWbt8WXV1pmXk 4+3fqHEcrFF61RHALtIjFjW+QqrrKVFg9qnWKcdiEdf+Z76Z2O/CROEACSWRk2I3gPTfDeIVy BisfdEakiMFp6qnHMg17DxC5/nXrMretNtHNdLHg1I6CZdpoRE= X-Mailman-Approved-At: Thu, 22 Mar 2018 21:10:47 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 20:50:40 -0000 Hi, Benno Rice wrote: > I’ve been working on the ability to create hybrid ISO/HDD boot images for > x86, a la what Linux systems do with ISOHYBRID. Waving friendly over the fence i feel entitled to give some neighbor's review. > The general theory seems to > be that ISO images have a 32KB hunk of zeroes at the front that they > generally ignore It is called System Area. ECMA-119, 6.2.1: "The System Area shall occupy the Logical Sectors with Logical Sector Numbers 0 to 15. The System Area shall be reserved for system use. Its content is not specified by this Standard." I collected some info about possible stuffings in https://dev.lovelyhq.com/libburnia/libisofs/raw/master/doc/boot_sectors.txt > Legacy BIOS with HDD: Sees a DOS MBR [...] sees an active BSD > slice containing a variant of our BSD boot code that reads from the ISO > [...] This finds loader in the ISO filesystem The isohybrid MBRs of SYSLINUX and GRUB expect to get patched-in the block address of the El Torito no-emulation boot image. To be done by SYSLINUX program "isohybrid", or xorrisofs options -isohybrid-mbr , --grub2-mbr. They try to stay small in order to create room for fancy partition tables GPT and APM. The MBR code even begins by a no-op area where one can put APM magic numbers which happen to be harmless x86 machine code. > https://people.freebsd.org/~benno/hybrid-bootonly.iso.xz This does not look much like it addresses EFI. $ xorriso -indev hybrid-bootonly.iso -report_el_torito plain -report_system_area plain ... El Torito catalog : 19 1 El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 20 El Torito boot img : 2 BIOS y none 0x0000 0x00 1600 24 ... MBR partition table: N Status Type Start Blocks MBR partition : 1 0x80 0xa5 1 16 UEFI 2.4, 12.3.2.1, says about El Torito: "A Platform Id of 0xEF indicates an EFI System Partition." But entry 2 of this catalog is in a section with Platform Id 0x00 (x86 BIOS). If byte 38977 (decimal) was 0xef rather than 0x00, then it would be marked as an El Torito boot image for EFI. Further: This section begins at byte address 38976 by a byte value 0x90. According to El Torito specs this means that another section follows. Correct would be value 0x91, which announces the end of the catalog. (El Torito 1.0, Figure 4, Offset 0) On HDD, EFI looks for specially marked partitions in GPT or MBR partition table. In MBR partiton table it looks for a partition of type 0xEF. (UEFI 2.4, 5.2.2) In GPT it looks for Type GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B. (UEFI 2.4, Table 19) So to mark the EFI partition, hybrid-bootonly.iso should have a MBR partition number 2 with type 0xEF, start at 512-byte block 24*2048/512 = 96, size 1600 blocks. (Strangely El Torito addresses by 2048-byte blocks but counts by 512-byte blocks. Size limit is 65535 blocks. But counts 0 and 1 mean to EFI "up to end of medium".) > I’ve tested this image under qemu OVMF/SDK-II/Tianocore is too tolerant with the EFI specs and with silently using BIOS boot equipment. Real iron EFIs insist much more in compliance. Have a nice day :) Thomas From owner-freebsd-current@freebsd.org Fri Mar 23 07:51:09 2018 Return-Path: Delivered-To: freebsd-current@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 9C030F4FF94; Fri, 23 Mar 2018 07:51:09 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (host64.shmhost.net [IPv6:2a01:4f8:a0:51d7::103:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CB85856EB; Fri, 23 Mar 2018 07:51:08 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from [IPv6:2001:470:25:233:ad60:93d2:9211:833] (unknown [IPv6:2001:470:25:233:ad60:93d2:9211:833]) by host64.shmhost.net (Postfix) with ESMTPSA id A3E3B1653D9; Fri, 23 Mar 2018 08:50:59 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Testing requested: Hybrid ISO/USB boot From: Franco Fichtner In-Reply-To: Date: Fri, 23 Mar 2018 08:50:57 +0100 Cc: FreeBSD Current , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Benno Rice X-Mailer: Apple Mail (2.3445.5.20) X-Virus-Scanned: clamav-milter 0.99.4 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 07:51:09 -0000 Hi Benno, > On 22. Mar 2018, at 7:06 PM, Benno Rice wrote: >=20 > I=E2=80=99ve been working on the ability to create hybrid ISO/HDD boot = images for x86, a la what Linux systems do with ISOHYBRID. The general = theory seems to be that ISO images have a 32KB hunk of zeroes at the = front that they generally ignore so we=E2=80=99ll stick something in = there that can handle booting if need be. The cases generally break down = as follows: Very cool! I ported the patch to 11.1-RELEASE and built an OPNsense image[1] based on the commands enclosed. (I'm not entirely sure if the porting was ok as there were quite a few challenges... but for the sake of testing...) Bhyve boot: ok VirtualBox boot: ok (when using extension .iso) APU1C boot: aborts with "Invalid partition" 3x, then "No /boot/loader" and then escapes to "FreeBSD/x86 boot" etc. It's an UEFI style ISO[2] so not sure if this is problematic. I have other hardware to try and your image, but that's for later. Cheers, Franco -- [1] = https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/OPNsense-18.1.5-OpenSS= L-dvd-amd64.iso.bz2 [2] https://github.com/opnsense/tools/blob/master/build/dvd.sh From owner-freebsd-current@freebsd.org Fri Mar 23 08:01:53 2018 Return-Path: Delivered-To: freebsd-current@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 55D58F50F4D; Fri, 23 Mar 2018 08:01:53 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (host64.shmhost.net [IPv6:2a01:4f8:a0:51d7::103:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0EBF85ED0; Fri, 23 Mar 2018 08:01:52 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from [IPv6:2001:470:25:233:ad60:93d2:9211:833] (unknown [IPv6:2001:470:25:233:ad60:93d2:9211:833]) by host64.shmhost.net (Postfix) with ESMTPSA id E1F6F1654AB; Fri, 23 Mar 2018 09:01:51 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Testing requested: Hybrid ISO/USB boot From: Franco Fichtner In-Reply-To: Date: Fri, 23 Mar 2018 09:01:50 +0100 Cc: FreeBSD Current , freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <6CA7676E-D558-4F9D-9613-C08D54D4C791@lastsummer.de> References: To: Benno Rice X-Mailer: Apple Mail (2.3445.5.20) X-Virus-Scanned: clamav-milter 0.99.4 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 08:01:53 -0000 Hi Benno, > On 23. Mar 2018, at 8:50 AM, Franco Fichtner wrote: > > APU1C boot: aborts with "Invalid partition" 3x, then "No /boot/loader" > and then escapes to "FreeBSD/x86 boot" etc. Small follow-up: the hybrid-bootonly.iso goes blank on this one due to no dual boot / serial settings. Cannot conform nor deny at this point. Cheers, Franco From owner-freebsd-current@freebsd.org Fri Mar 23 10:31:03 2018 Return-Path: Delivered-To: freebsd-current@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 370AFF5D285 for ; Fri, 23 Mar 2018 10:31:03 +0000 (UTC) (envelope-from 482254ac@razorfever.net) Received: from pmta21.teksavvy.com (pmta21.teksavvy.com [76.10.157.36]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "*.teksavvy.com", Issuer "DigiCert SHA2 High Assurance Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFC3A6BF9C for ; Fri, 23 Mar 2018 10:31:02 +0000 (UTC) (envelope-from 482254ac@razorfever.net) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2G6BQDV1rRa/0StpUVdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYIIgTVkbSiDXIhejDABRAYGgSMxAV+SSoIGC4UFAoNlIjUXAQI?= =?us-ascii?q?BAQEBAQECA2gohSYBAQEBAgEjDwEFHiMFCwsYAgImAgI5HgYNBgIBAReEZgUIq?= =?us-ascii?q?QCCIIRYg2mCGhN1hCeDHYEIgS6CMDSEXYMXglQDkEiGcwcBAo4ngTWDVoIqD4R?= =?us-ascii?q?5hyWIQgyBJR0BN4FSH1yDB5BrIzCQVQEB?= X-IPAS-Result: =?us-ascii?q?A2G6BQDV1rRa/0StpUVdGQEBAQEBAQEBAQEBAQcBAQEBAYI?= =?us-ascii?q?IgTVkbSiDXIhejDABRAYGgSMxAV+SSoIGC4UFAoNlIjUXAQIBAQEBAQECA2goh?= =?us-ascii?q?SYBAQEBAgEjDwEFHiMFCwsYAgImAgI5HgYNBgIBAReEZgUIqQCCIIRYg2mCGhN?= =?us-ascii?q?1hCeDHYEIgS6CMDSEXYMXglQDkEiGcwcBAo4ngTWDVoIqD4R5hyWIQgyBJR0BN?= =?us-ascii?q?4FSH1yDB5BrIzCQVQEB?= X-IronPort-AV: E=Sophos;i="5.48,349,1517893200"; d="scan'208";a="25058287" Received: from 69-165-173-68.dsl.teksavvy.com (HELO mail.razorfever.net) ([69.165.173.68]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Mar 2018 06:30:55 -0400 Received: from [127.0.0.1] (mail.razorfever.net [192.168.0.4]) by mail.razorfever.net (8.15.2/8.14.9) with ESMTP id w2NAUsG7034325; Fri, 23 Mar 2018 06:30:54 -0400 (EDT) (envelope-from 482254ac@razorfever.net) X-Authentication-Warning: mail.razorfever.net: Host mail.razorfever.net [192.168.0.4] claimed to be [127.0.0.1] Subject: Re: freebsd-update: to a specific patch level - help please? [PATCH] To: Rainer Duffner Cc: FreeBSD Current References: From: "Derek (freebsd lists)" <482254ac@razorfever.net> Message-ID: Date: Fri, 23 Mar 2018 06:30:54 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, FROM_STARTS_WITH_NUMS,RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.razorfever.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 10:31:03 -0000 On 18-03-21 05:24 PM, Rainer Duffner wrote: >> Am 21.03.2018 um 22:12 schrieb Derek (freebsd lists) <482254ac@razorfever.net>: >> >> Hi! >> >> I was surprised when using freebsd-update, that there was no way to specify a patch level. > > AFAIK, the usual answer to these kinds of requests is: „Run your own freebsd-update server“. > > Mirroring one of the existing ones is AFAIK neither guaranteed to work nor desired by the current „administration“. > Thanks for your thoughts. To be clear, *I've included a link to a patch to freebsd-update in my initial post, and the help I'm looking for: is to get this functionality added as a feature so others can benefit.* It works for me already, and I've already benefited. (I'm happy to flesh it out, and document it properly, but I'm very hesitant to spend the time doing it in detail and submitting a PR if I'm doing this in isolation, and nobody wants it. Perhaps the silence on the thread is already a good indicator of the appetite, although I fear it's my ability to sell it or myself properly.) Structurally, "run your own freebsd-update server" is a wasteful solution for a single (or much larger set of) default install(s). It makes a lot of sense for custom installations. For what should be the default approach: repeatable - version controlled - installations with the support of the FreeBSD project, it would seem that having freebsd-update support patch levels would be a far more efficient net use of people's time than the alternatives. (I was debating both running an update server, or running "behind" a hacked up mirror as well, and in fact, I feel patching freebsd-update was a great investment, for n=1.) > It’s also a somewhat transient problem now because - AFAIK - FreeBSD will see packaged base and you can probably mirror those packages and snapshot the directory at any point in time. > And/Or it’s just easier to create these base-packages yourselves vs. running your own freebsd-update server. > This is a good point, and perhaps why it's not worth putting more time into this. I appreciate your feedback. Thanks! Derek From owner-freebsd-current@freebsd.org Fri Mar 23 10:44:39 2018 Return-Path: Delivered-To: freebsd-current@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 323A7F5E4B4 for ; Fri, 23 Mar 2018 10:44:39 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 BAD6B6CAB8 for ; Fri, 23 Mar 2018 10:44:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1ezKBZ-0006ck-Jj; Fri, 23 Mar 2018 11:44:37 +0100 Date: Fri, 23 Mar 2018 11:44:37 +0100 From: Kurt Jaeger To: "Derek (freebsd lists)" <482254ac@razorfever.net> Cc: FreeBSD Current Subject: Re: freebsd-update: to a specific patch level - help please? [PATCH] Message-ID: <20180323104437.GB21001@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 10:44:39 -0000 Hi! > To be clear, *I've included a link to a patch to freebsd-update > in my initial post, and the help I'm looking for: is to get this > functionality added as a feature so others can benefit.* It > works for me already, and I've already benefited. > > (I'm happy to flesh it out, and document it properly, but I'm > very hesitant to spend the time doing it in detail and submitting > a PR if I'm doing this in isolation, and nobody wants it. Please submit this in a PR, and post the PR number here, I'll work to get this in the tree. -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Fri Mar 23 12:53:46 2018 Return-Path: Delivered-To: freebsd-current@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 1587AF69B29; Fri, 23 Mar 2018 12:53:46 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pl0-x22e.google.com (mail-pl0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C894726BA; Fri, 23 Mar 2018 12:53:45 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pl0-x22e.google.com with SMTP id f23-v6so7360863plr.10; Fri, 23 Mar 2018 05:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Oqaad+Y/+sibLL9MTEBOrhG5wHbJ8FLVT+AOViTC994=; b=NZ3kN92YfWVtHzp92cY9xPMU0LG1YiCXbztO4+syTxjHeMMoXy9jZCc2oq21tLGl+n DmlxkYz6Wyw4qj0W1WFC7mzJMNFywGgFmILsyY/mVLTcnsla3y7FBpJ9+2lub4Lb/COT QJA1O1jwXL7Anf4gQA2KKiZF/Vo8bSXy252WHz9PNvPdir03BYTc/rKWjR8/PEP22zgP bC9yRy6M6PIUwAF3LpGbBKpIt6oBxybWP8/k1JUWU1RkFJtfK0tTIZP4Vs9KKJeeIRZ0 8+ire+qlmGIH1RCm9PmiqayT962LFtmxIuSGWO4SyTpZz303+pQkdX6Awk0LLXxZayEC ol5A== 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=Oqaad+Y/+sibLL9MTEBOrhG5wHbJ8FLVT+AOViTC994=; b=p9phs/cfVKPuGNLvlfK4tU/3hlziZ33Zschsop4Sdeh8MWyOhwPh7KS5uTeUaezKe6 t0IbYFzyvZ5dlsH5rrShQA9nydx6i0YsxWB8nS+F3vFecCXVzk0H1IFqMe4uw1l/JDsv uHiEyl2cautpcyUo/9fM3ipixU9BAMLREdV0r98abf9iyopH2/XpxyyJHeDKjZoIxuV6 V2T6/8NtcebhSPh3ZdPX2LUDgmv46FsVWsmQzJE3UJUMeZY1lAsZ/7iSNjEXl4oMAcgc MWQdXwuej7rPrmi8zijmtlH/AM0dwOMZsVPdknG2jI+q/M4STVO21AwEn1LCq8oEaY9f sEgg== X-Gm-Message-State: AElRT7Hbr9DwgS1Qrb7QEUDsX8/G6j2z/ZURCkhghA5i+AafqPutUFk+ E1Sob5GI5RhQh2kKr3KFoAVKUbN3QfU4pXtbuzs= X-Google-Smtp-Source: AG47ELtSicgn7dBziwK6ITsZdNRW+ZTN2C4997WRiZbsCQlGGrDUqy0MM0pA3lzo1ouLbswWVVaoRq/cRbIsHcAdRa0= X-Received: by 2002:a17:902:51ad:: with SMTP id y42-v6mr26335968plh.314.1521809624411; Fri, 23 Mar 2018 05:53:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.241.196 with HTTP; Fri, 23 Mar 2018 05:53:43 -0700 (PDT) In-Reply-To: References: From: Maurizio Vairani Date: Fri, 23 Mar 2018 13:53:43 +0100 Message-ID: Subject: Re: Testing requested: Hybrid ISO/USB boot To: Benno Rice Cc: FreeBSD Current , freebsd-hackers@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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 12:53:46 -0000 2018-03-22 19:06 GMT+01:00 Benno Rice : > Hello all! > > I=E2=80=99ve been working on the ability to create hybrid ISO/HDD boot im= ages for > x86, a la what Linux systems do with ISOHYBRID. The general theory seems = to > be that ISO images have a 32KB hunk of zeroes at the front that they > generally ignore so we=E2=80=99ll stick something in there that can handl= e booting > if need be. The cases generally break down as follows: > > UEFI with CD: Boots using an EFI system partition embedded in the ISO > image. This loads loader, and so on. > UEFI with HDD: Same as above as UEFI doesn=E2=80=99t really care what the > underlying medium is and it sees the ISO image. > Legacy BIOS with CD: Boots using El Torrito as always. > > And now for the new part: > > Legacy BIOS with HDD: Sees a DOS MBR stuck in the 32KB at the front of th= e > ISO image. This MBR contains our MBR boot code, which sees an active BSD > slice containing a variant of our BSD boot code that reads from the ISO > filesystem instead of UFS. This finds loader in the ISO filesystem and > loads that. Loader has had support for reading ISO9660 images off HDDs > added. Everything continues normally after that. > > The review for these changes is here: > > https://reviews.freebsd.org/D14799 > > And a version of the standard =E2=80=9Cbootonly=E2=80=9D ISO image built = with these > changes is here: > > https://people.freebsd.org/~benno/hybrid-bootonly.iso.xz < > https://people.freebsd.org/~benno/hybrid-bootonly.iso.xz> > > I=E2=80=99ve tested this image under qemu and VMware under all four of th= e > BIOS/UEFI and CD/HDD combinations. I=E2=80=99ve also booted a system buil= d around > an Asus X399 Prime motherboard with this dd=E2=80=99ed to a USB stick. I= =E2=80=99d love > some testing on more systems, especially things that are more likely to > have more customized boot firmwares (I=E2=80=99m thinking Dell, HP, etc). > > Many thanks, > Benno. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Hi Benno, thank you for your work. On a Mac mini "Core i5" 2.3 (Mid-2011), booting via USB, it hangs very early, after writing: FreeBSD/x86 bootstrap loader, version 1.1 (Wed Mar 21 10:27:48 PDT 2018 benno@bobthe) Regards, Maurizio From owner-freebsd-current@freebsd.org Fri Mar 23 12:50:04 2018 Return-Path: Delivered-To: freebsd-current@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 702A7F694AA for ; Fri, 23 Mar 2018 12:50:04 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DAB6172280 for ; Fri, 23 Mar 2018 12:50:03 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 98791 invoked from network); 23 Mar 2018 12:50:01 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 12:50:01 -0000 To: freebsd-stable-request@freebsd.o, freebsd-current@freebsd.org From: Joerg Surmann Subject: two NIC's in a jail Message-ID: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> Date: Fri, 23 Mar 2018 13:49:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5qRRAuPezem2k4WrQxyBfqeveiyeg572F" X-Mailman-Approved-At: Fri, 23 Mar 2018 14:04:32 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 12:50:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5qRRAuPezem2k4WrQxyBfqeveiyeg572F Content-Type: multipart/mixed; boundary="Z6IwXXvgzv6zmBTAYHdbugxcEAhaygVxP"; protected-headers="v1" From: Joerg Surmann To: freebsd-stable-request@freebsd.o, freebsd-current@freebsd.org Message-ID: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> Subject: two NIC's in a jail --Z6IwXXvgzv6zmBTAYHdbugxcEAhaygVxP Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, I have a Problem to understund how to manage 2 Networks inside a Jail. i have create a jail (using ezjail) with a alias IP. in rc.conf (on Host): ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0 <= - this is the jail ip Inside the jail running apachhe24. Now i add a new NIC to the System. in rc.conf (on Host): ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" in /usr/local/etc/ezjail/myjail.conf: i add the new ip export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" Restart the jail and ifconfig looks fine. vmx0 -> inet 192.168.100.2 em0=C2=A0 -> inet 213.70.80.92 Apache Listen on all NIC's () But i can see my Website only via 192.168.100.2 from intern Network. The Host is behind a Firewall. The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. When i give the Hostname in a Browser i become "connection Timeout". What is to do that the Host is accessable from Inet? Thanks Holm =C2=A0 =C2=A0 --Z6IwXXvgzv6zmBTAYHdbugxcEAhaygVxP-- --5qRRAuPezem2k4WrQxyBfqeveiyeg572F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq09/UACgkQGHz25TAa 4su8ehAAgVkUlFnnFNzCrLFtz3TyYa5EjV9wenerzj2yXGaHSeDMmLotSuTLxrHt zM/726jTrEX1EC9nOm/Hu/x9vp9S9O1Lg5a52JM8vRI9ukolB8DJXZ0E7VEa6/Za wzCF42ufjmHw/B+tWk/TUGvWsoENNoMqEr/bMFsHXP2HqsEanMJUsPYD4Ch0qVsL F9akNhe2Y3Ry45dGudxYm7nVf2TOAP6mZu1/JyBRs2xliwLZUZHsmZ4BXBHYSgPR 1m6oeedL0BuKFszzIScVi04fAkfufDY7L+Qf58+ChDS8MmPMb/FmISp0lnV1It3j h6XAZ1ipQZWMmhkd2+06X70MgqqNVRyR9bVBe6QxpMpsIdTrOL/wKiwKQk77LuA0 ekkrAq375rm0Hfem6AeCH/3i2Wi+XqGNjyYbco5CepTvC7mB/bjKhfn1MpuyOnNM JaPu+v2z4TGpoX6102qz3ui1JnyYz9aWwtCGj5iogsfSpLxt5NOFcnK3+40Qb06M v4o773HqzxV0gefc+1dx5yyZex8IYEvrlDfloGUAM6U3TYqR4EdcQrhXZlGUhMa7 jKO0ZJNcHrHUOWXAlXWH7kIcOm/It9wgLgxyBGBl6S/TMLf2qJeNV6sl5P4LJ/Tf Nwhdb3DigxfjVrEAmRQZaiW/tYX8DD2vcXIWSD9B+rS8cMeIENY= =Qod6 -----END PGP SIGNATURE----- --5qRRAuPezem2k4WrQxyBfqeveiyeg572F-- From owner-freebsd-current@freebsd.org Fri Mar 23 15:07:30 2018 Return-Path: Delivered-To: freebsd-current@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 9AA6CF4F869 for ; Fri, 23 Mar 2018 15:07:30 +0000 (UTC) (envelope-from SRS0=pJyN=GN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E634789A5 for ; Fri, 23 Mar 2018 15:07:30 +0000 (UTC) (envelope-from SRS0=pJyN=GN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 05FAF28460; Fri, 23 Mar 2018 16:07:28 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 353BB28411; Fri, 23 Mar 2018 16:07:27 +0100 (CET) Subject: Re: two NIC's in a jail To: Joerg Surmann , freebsd-current@freebsd.org References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> Date: Fri, 23 Mar 2018 16:07:26 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:07:30 -0000 Joerg Surmann wrote on 2018/03/23 13:49: > Hi all, > > I have a Problem to understund how to manage 2 Networks inside a Jail. > > i have create a jail (using ezjail) with a alias IP. > in rc.conf (on Host): > > ifconfig_vmx0="inet 192.168.100.1 netmask 255.255.255.0" > ifconfig_vmx0_alias0="inet 192.168.100.2 netmask 255.255.255.0"  <- this > is the jail ip > > Inside the jail running apachhe24. > > Now i add a new NIC to the System. > in rc.conf (on Host): > ifconfig_em0="inet 213.70.80.92 netmask 255.255.255.0" > > in /usr/local/etc/ezjail/myjail.conf: > i add the new ip > export jail_myjail_ip="192.168.100.2,213.70.80.92" > > Restart the jail and ifconfig looks fine. > vmx0 -> inet 192.168.100.2 > em0  -> inet 213.70.80.92 > > Apache Listen on all NIC's () > But i can see my Website only via 192.168.100.2 from intern Network. > > The Host is behind a Firewall. > The IP  213.70.80.92 is enabled for incomming Traffic. > > When i give the Hostname in a Browser i become "connection Timeout". > > What is to do that the Host is accessable from Inet? Are you sure Apache is listening on both IPs? What netstat says? # netstat -an | egrep 'tcp4.*80 .*LISTEN' Also check what you have in httpd.conf for Listen directive # grep -i Listen /usr/local/etc/apache24/httpd.conf I am not using ezjail, I am using jail.conf costa { host.hostname = "costa.example.com"; ip4.addr = AA.BB.CCC.DDD; ip4.addr += 192.168.222.57; } Real IP was replaced with AA.BB.CCC.DDD And it works. Services inside jail must be listening on both IPs or wildcard * (0.0.0.0) And be sure to disable hosts services to listen on IPs and ports you want to be served from jail. Miroslav Lachman From owner-freebsd-current@freebsd.org Fri Mar 23 15:53:35 2018 Return-Path: Delivered-To: freebsd-current@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 AEFC0F53ACF for ; Fri, 23 Mar 2018 15:53:34 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF787B384 for ; Fri, 23 Mar 2018 15:53:33 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 45909 invoked from network); 23 Mar 2018 15:53:32 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 15:53:32 -0000 Subject: Re: two NIC's in a jail To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> From: Joerg Surmann Message-ID: <19503390-6434-e7cf-f5ce-d0170afc9f91@elektropost.org> Date: Fri, 23 Mar 2018 16:53:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Hqna5AstfTS2BWBKJp35swR5ANdBZUdoB" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:53:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Hqna5AstfTS2BWBKJp35swR5ANdBZUdoB Content-Type: multipart/mixed; boundary="aLl1wpDFygpiy5YthSu6RaP8cxP79lqxd"; protected-headers="v1" From: Joerg Surmann To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org Message-ID: <19503390-6434-e7cf-f5ce-d0170afc9f91@elektropost.org> Subject: Re: two NIC's in a jail References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> --aLl1wpDFygpiy5YthSu6RaP8cxP79lqxd Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Thanks for replay. netstat -an | egrep 'tcp4.*80 .*LISTEN' say: netstat: kvm not available: /dev/mem No such file or directory <- is inside a jail. tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0 *.80=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 = LISTEN grep -i Listen /usr/local/etc/apache24/httpd.conf Listen 80 Listen 443 =46rom the internal IP is no Problem. You are right. I'm not sure on wich IP's Apache is listening. I have change the Listen directive to the external IP in httpd.conf Listen 213.70.80.92:80 netstat -an | egrep 'tcp4.*80 .*LISTEN' now say: tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0=C2=A0 213= =2E70.80.92:80=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 LISTEN But apache is not availble from Internet. =46rom Intranet... no Problem. When i use tcpdump on Host i can see Traffic. Whats wrong? Am 23.03.2018 um 16:07 schrieb Miroslav Lachman: > Joerg Surmann wrote on 2018/03/23 13:49: >> Hi all, >> >> I have a Problem to understund how to manage 2 Networks inside a Jail.= >> >> i have create a jail (using ezjail) with a alias IP. >> in rc.conf (on Host): >> >> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0= <- this >> is the jail ip >> >> Inside the jail running apachhe24. >> >> Now i add a new NIC to the System. >> in rc.conf (on Host): >> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >> >> in /usr/local/etc/ezjail/myjail.conf: >> i add the new ip >> export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >> >> Restart the jail and ifconfig looks fine. >> vmx0 -> inet 192.168.100.2 >> em0=C2=A0 -> inet 213.70.80.92 >> >> Apache Listen on all NIC's () >> But i can see my Website only via 192.168.100.2 from intern Network. >> >> The Host is behind a Firewall. >> The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. >> >> When i give the Hostname in a Browser i become "connection Timeout". >> >> What is to do that the Host is accessable from Inet? > > Are you sure Apache is listening on both IPs? > > What netstat says? > > # netstat -an | egrep 'tcp4.*80 .*LISTEN' > > Also check what you have in httpd.conf for Listen directive > > # grep -i Listen /usr/local/etc/apache24/httpd.conf > > I am not using ezjail, I am using jail.conf > > costa { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 host.hostname=C2=A0=C2=A0 =3D= "costa.example.com"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 =3D AA.BB.CCC.DDD; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 +=3D 192.168.222.57; > } > > Real IP was replaced with AA.BB.CCC.DDD > > And it works. Services inside jail must be listening on both IPs or > wildcard * (0.0.0.0) > > And be sure to disable hosts services to listen on IPs and ports you > want to be served from jail. > > Miroslav Lachman --aLl1wpDFygpiy5YthSu6RaP8cxP79lqxd-- --Hqna5AstfTS2BWBKJp35swR5ANdBZUdoB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1IvgACgkQGHz25TAa 4suQPhAAyO26l+KjQ2BZzmcE8envE3aWvl67nmjJ+d2Gum8D7JA9WlrnQc69gL1y KUrY8PgWjZQty37njONp+EhgRAwGQxrv28HFXmwEUbSp69SHYrV4k78Y1uBvo3Mw +OhfaRGNSFK6tKbuxIaZ9I99i7yzZzZhVU0WmyA0H+DoHcoq+9NPDqj6cOzhEhrH YOiv7MYqP62T3bpay7FmXMyH+kjtie+HDuhhiCDAbTLvlvUQdNn5VXBGHwfGa2RI jQzL5GJ1g1aoCCRkxC99OmKEyetv6omQaZlbB8/a324OF6j8tIRJXHfwdJDF3c38 xKTagm5LbMzJvFuaCGT8CW7aGx4ImIfzLg0o6GbKg89cDpAQwb5ap1UYQYS0nfpo OC7cluy1I4z5Qsl8pUwg6SytjqM1Z2JVfCcIg78yzy1cGI7TPZUWFiB9XwteYbZZ N12/MYBqeay1dNYeZXZJZbnKwxizAWIHpFdMVvw3+vRnE2rZ8PRCRMtpr+quP+zG VYwMteG3EuBYu+Y0rFR2pHVhuf5DJ9tjZIIDvrBvK9z9GdrZkvA45Zvh7W/E8zXp 8uvXvFzpV3ZFlihm7JOEjDdg+IvzPLcjHdLF3b0ED8XXS0fELpDLVq5ETbLo03AD BpKJXOF+rIdvN/j2FyKgM4egjcti724PloSJCpgrqY1sQxMWJL8= =si/n -----END PGP SIGNATURE----- --Hqna5AstfTS2BWBKJp35swR5ANdBZUdoB-- From owner-freebsd-current@freebsd.org Fri Mar 23 15:58:29 2018 Return-Path: Delivered-To: freebsd-current@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 4A6E7F5417A; Fri, 23 Mar 2018 15:58:29 +0000 (UTC) (envelope-from SRS0=pJyN=GN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7BD27B703; Fri, 23 Mar 2018 15:58:25 +0000 (UTC) (envelope-from SRS0=pJyN=GN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0C59728469; Fri, 23 Mar 2018 16:58:24 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id EEA8928462; Fri, 23 Mar 2018 16:58:22 +0100 (CET) Subject: Re: two NIC's in a jail To: Joerg Surmann , FreeBSD-Jail References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-current@freebsd.org Message-ID: <5decebc0-0a77-69fd-4547-8a1665300890@quip.cz> Date: Fri, 23 Mar 2018 16:58:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:58:29 -0000 Joerg Surmann wrote on 2018/03/23 16:45: > Thanks for replay. > > netstat -an | egrep 'tcp4.*80 .*LISTEN' > say: > netstat: kvm not available: /dev/mem No such file or directory <- is > inside a jail. > tcp4    0        0 *.80        *.*        LISTEN > > grep -i Listen /usr/local/etc/apache24/httpd.conf > > Listen 80 > Listen 443 > > From the internal IP is no Problem. > You are right. I'm not sure on wich IP's Apache is listening. > > I have change the Listen directive to the external IP in httpd.conf > Listen 213.70.80.92:80 > > netstat -an | egrep 'tcp4.*80 .*LISTEN' > now say: > tcp4    0        0  213.70.80.92:80        *.*        LISTEN > > But apache is not availble from Internet. > From Intranet... no Problem. > > When i use tcpdump on Host i can see Traffic. > > Whats wrong? That's strange. Listen 80 and Listen 443 is OK, it is the same as Listen *:80 Listen *:443 and as you see with netstat, Apache was listening on both IPs: *.80 *.* LISTEN Do you have something listening on port 80 in the Host? What netstat shows in the host? Also check Apache log files. If you didn't configure virtual host, then you have just these two log files: /var/log/httpd-access.log /var/log/httpd-error.log Use tail and then try to access your website from the internet # tail -f /var/log/httpd-*.log Please send what "jls -v" in the Host will show you. (there should be 2 IPs for your jail) or "jls -s" (replace any sensitive informations if you want) And move this discussion to proper mailing list: freebsd-jail@FreeBSD.org Miroslav Lachman > Am 23.03.2018 um 16:07 schrieb Miroslav Lachman: >> Joerg Surmann wrote on 2018/03/23 13:49: >>> Hi all, >>> >>> I have a Problem to understund how to manage 2 Networks inside a Jail. >>> >>> i have create a jail (using ezjail) with a alias IP. >>> in rc.conf (on Host): >>> >>> ifconfig_vmx0="inet 192.168.100.1 netmask 255.255.255.0" >>> ifconfig_vmx0_alias0="inet 192.168.100.2 netmask 255.255.255.0"  <- this >>> is the jail ip >>> >>> Inside the jail running apachhe24. >>> >>> Now i add a new NIC to the System. >>> in rc.conf (on Host): >>> ifconfig_em0="inet 213.70.80.92 netmask 255.255.255.0" >>> >>> in /usr/local/etc/ezjail/myjail.conf: >>> i add the new ip >>> export jail_myjail_ip="192.168.100.2,213.70.80.92" >>> >>> Restart the jail and ifconfig looks fine. >>> vmx0 -> inet 192.168.100.2 >>> em0  -> inet 213.70.80.92 >>> >>> Apache Listen on all NIC's () >>> But i can see my Website only via 192.168.100.2 from intern Network. >>> >>> The Host is behind a Firewall. >>> The IP  213.70.80.92 is enabled for incomming Traffic. >>> >>> When i give the Hostname in a Browser i become "connection Timeout". >>> >>> What is to do that the Host is accessable from Inet? >> >> Are you sure Apache is listening on both IPs? >> >> What netstat says? >> >> # netstat -an | egrep 'tcp4.*80 .*LISTEN' >> >> Also check what you have in httpd.conf for Listen directive >> >> # grep -i Listen /usr/local/etc/apache24/httpd.conf >> >> I am not using ezjail, I am using jail.conf >> >> costa { >>         host.hostname   = "costa.example.com"; >>         ip4.addr        = AA.BB.CCC.DDD; >>         ip4.addr       += 192.168.222.57; >> } >> >> Real IP was replaced with AA.BB.CCC.DDD >> >> And it works. Services inside jail must be listening on both IPs or >> wildcard * (0.0.0.0) >> >> And be sure to disable hosts services to listen on IPs and ports you >> want to be served from jail. From owner-freebsd-current@freebsd.org Fri Mar 23 16:14:21 2018 Return-Path: Delivered-To: freebsd-current@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 B626CF55A5D for ; Fri, 23 Mar 2018 16:14:20 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 283CD7C3B0 for ; Fri, 23 Mar 2018 16:14:19 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 51047 invoked from network); 23 Mar 2018 16:14:17 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 16:14:17 -0000 Subject: Re: two NIC's in a jail To: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Jail Cc: freebsd-current@freebsd.org References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> <5decebc0-0a77-69fd-4547-8a1665300890@quip.cz> From: Joerg Surmann Message-ID: <78112343-662e-7890-f5ee-668fda23b834@elektropost.org> Date: Fri, 23 Mar 2018 17:14:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5decebc0-0a77-69fd-4547-8a1665300890@quip.cz> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DUWhYKd617V0IXTgdZAOgU0sVtB7v3vTP" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 16:14:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DUWhYKd617V0IXTgdZAOgU0sVtB7v3vTP Content-Type: multipart/mixed; boundary="FDsEC3PGqsJupiwJ9aOKqMKe0THZ1IeZp"; protected-headers="v1" From: Joerg Surmann To: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-Jail Cc: freebsd-current@freebsd.org Message-ID: <78112343-662e-7890-f5ee-668fda23b834@elektropost.org> Subject: Re: two NIC's in a jail References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> <5decebc0-0a77-69fd-4547-8a1665300890@quip.cz> In-Reply-To: <5decebc0-0a77-69fd-4547-8a1665300890@quip.cz> --FDsEC3PGqsJupiwJ9aOKqMKe0THZ1IeZp Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable tail -f /var/log/httpd-access.log 192.168.100.2 - - [23/Mar/2018:13:12:10 +0000] "OPTIONS * HTTP/1.0" 200 -= 192.168.100.2 - - [23/Mar/2018:15:12:02 +0000] "OPTIONS * HTTP/1.0" 200 -= 213.70.80.92 - - [23/Mar/2018:15:33:07 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:33:08 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:33:09 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:35:37 +0000] "GET / HTTP/1.1" 302 209 213.70.80.92 - - [23/Mar/2018:15:35:44 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:35:45 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:35:46 +0000] "OPTIONS * HTTP/1.0" 200 - 213.70.80.92 - - [23/Mar/2018:15:58:05 +0000] "GET / HTTP/1.1" 302 209 tail -f /var/log/httpd-error.log [Fri Mar 23 12:08:18.142835 2018] [mpm_prefork:notice] [pid 18904] AH00163: Apache/2.4.29 (FreeBSD) OpenSSL/1.0.2k-freebsd PHP/7.1.15 configured -- resuming normal operations [Fri Mar 23 12:08:18.142925 2018] [core:notice] [pid 18904] AH00094: Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' [Fri Mar 23 12:30:19.005654 2018] [mpm_prefork:notice] [pid 18904] AH00169: caught SIGTERM, shutting down [Fri Mar 23 12:31:11.111900 2018] [ssl:warn] [pid 2542] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache] [Fri Mar 23 12:31:11.847515 2018] [mpm_prefork:notice] [pid 2542] AH00163: Apache/2.4.29 (FreeBSD) OpenSSL/1.0.2k-freebsd PHP/7.1.15 configured -- resuming normal operations [Fri Mar 23 12:31:11.847589 2018] [core:notice] [pid 2542] AH00094: Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' [Fri Mar 23 15:32:08.238227 2018] [mpm_prefork:notice] [pid 2542] AH00169: caught SIGTERM, shutting down [Fri Mar 23 15:32:08.414689 2018] [ssl:warn] [pid 40920] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache] [Fri Mar 23 15:32:08.716943 2018] [mpm_prefork:notice] [pid 40920] AH00163: Apache/2.4.29 (FreeBSD) OpenSSL/1.0.2k-freebsd PHP/7.1.15 configured -- resuming normal operations [Fri Mar 23 15:32:08.717018 2018] [core:notice] [pid 40920] AH00094: Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT jls -v =C2=A0=C2=A0 JID=C2=A0 Hostname=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 Path =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Name=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 State =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 CPUSetID =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 IP Address(es) =C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0 apache24=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 /usr/jails/apache24 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 apache24=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 ACTIVE =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 192.168.100.2 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 213.70.80.92 jls -s devfs_ruleset=3D0 enforce_statfs=3D2 host=3Dnew ip4=3Ddisable ip6=3Ddisab= le jid=3D2 name=3Dapache24 osreldate=3D1101001 osrelease=3D11.1-RELEASE path=3D/usr/jails/apache24 nopersist securelevel=3D-1 sysvmsg=3Ddisable sysvsem=3Ddisable sysvshm=3Ddisable allow.nochflags allow.mount allow.mount.nodevfs allow.mount.nofdescfs allow.mount.nolinprocfs allow.mount.nolinsysfs allow.mount.nonullfs allow.mount.noprocfs allow.mount.notmpfs allow.mount.nozfs allow.noquotas allow.raw_sockets allow.noset_hostname allow.nosocket_af allow.nosysvipc children.max=3D0 host.domainname=3D"" host.hostid=3D0 host.hostname=3Dapache24 host.hostuuid=3D00000000-0000-0000-0000-000000000000 Am 23.03.2018 um 16:58 schrieb Miroslav Lachman: > Joerg Surmann wrote on 2018/03/23 16:45: >> Thanks for replay. >> >> netstat -an | egrep 'tcp4.*80 .*LISTEN' >> say: >> netstat: kvm not available: /dev/mem No such file or directory <- is >> inside a jail. >> tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0 *.80=C2= =A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0= LISTEN >> >> grep -i Listen /usr/local/etc/apache24/httpd.conf >> >> Listen 80 >> Listen 443 >> >> =C2=A0From the internal IP is no Problem. >> You are right. I'm not sure on wich IP's Apache is listening. >> >> I have change the Listen directive to the external IP in httpd.conf >> Listen 213.70.80.92:80 >> >> netstat -an | egrep 'tcp4.*80 .*LISTEN' >> now say: >> tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0=C2=A0 = 213.70.80.92:80=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 LISTEN >> >> But apache is not availble from Internet. >> =C2=A0From Intranet... no Problem. >> >> When i use tcpdump on Host i can see Traffic. >> >> Whats wrong? > > That's strange. > > Listen 80 and Listen 443 is OK, it is the same as > =C2=A0 Listen *:80 > =C2=A0 Listen *:443 > and as you see with netstat, Apache was listening on both IPs: > =C2=A0*.80=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 LISTEN > > Do you have something listening on port 80 in the Host? > > What netstat shows in the host? > > Also check Apache log files. If you didn't configure virtual host, > then you have just these two log files: > /var/log/httpd-access.log > /var/log/httpd-error.log > > Use tail and then try to access your website from the internet > > # tail -f /var/log/httpd-*.log > > Please send what "jls -v" in the Host will show you. (there should be > 2 IPs for your jail) or "jls -s"=C2=A0 (replace any sensitive informati= ons > if you want) > > And move this discussion to proper mailing list: > =C2=A0freebsd-jail@FreeBSD.org > > Miroslav Lachman > > >> Am 23.03.2018 um 16:07 schrieb Miroslav Lachman: >>> Joerg Surmann wrote on 2018/03/23 13:49: >>>> Hi all, >>>> >>>> I have a Problem to understund how to manage 2 Networks inside a Jai= l. >>>> >>>> i have create a jail (using ezjail) with a alias IP. >>>> in rc.conf (on Host): >>>> >>>> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >>>> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2= =A0 <- >>>> this >>>> is the jail ip >>>> >>>> Inside the jail running apachhe24. >>>> >>>> Now i add a new NIC to the System. >>>> in rc.conf (on Host): >>>> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >>>> >>>> in /usr/local/etc/ezjail/myjail.conf: >>>> i add the new ip >>>> export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >>>> >>>> Restart the jail and ifconfig looks fine. >>>> vmx0 -> inet 192.168.100.2 >>>> em0=C2=A0 -> inet 213.70.80.92 >>>> >>>> Apache Listen on all NIC's () >>>> But i can see my Website only via 192.168.100.2 from intern Network.= >>>> >>>> The Host is behind a Firewall. >>>> The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. >>>> >>>> When i give the Hostname in a Browser i become "connection Timeout".= >>>> >>>> What is to do that the Host is accessable from Inet? >>> >>> Are you sure Apache is listening on both IPs? >>> >>> What netstat says? >>> >>> # netstat -an | egrep 'tcp4.*80 .*LISTEN' >>> >>> Also check what you have in httpd.conf for Listen directive >>> >>> # grep -i Listen /usr/local/etc/apache24/httpd.conf >>> >>> I am not using ezjail, I am using jail.conf >>> >>> costa { >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 host.hostname=C2=A0=C2= =A0 =3D "costa.example.com"; >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D AA.BB.CCC.DDD; >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 +=3D 192.168.222.57; >>> } >>> >>> Real IP was replaced with AA.BB.CCC.DDD >>> >>> And it works. Services inside jail must be listening on both IPs or >>> wildcard * (0.0.0.0) >>> >>> And be sure to disable hosts services to listen on IPs and ports you >>> want to be served from jail. --FDsEC3PGqsJupiwJ9aOKqMKe0THZ1IeZp-- --DUWhYKd617V0IXTgdZAOgU0sVtB7v3vTP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1J9YACgkQGHz25TAa 4suq3Q//WS/az9y5SEcMrPW/UNVQg5azDu8VnFWG/2imKX1blBUsybedo6SQWvuc eOyAy23ppyS0gFFtn0rStYl49Y5K/ZnZqgQEf4U9gvQCjUl5Ei3i4E1hAKac4v83 mwY9DUSdbgL+vZsvCfdEkUovGNzQRWuppq/h5Ieek96gF1kD3tkDTZTLAP/aYsH3 wzMGFy0UlUoboLHCdkgFbIpspfFjvqjlOqArCkKvt/wA196UARKpdLe1LGxvT+BM /Gl31CSubsgJHCXUHPlwKjWEfSEzOjOPp7KtKxlcLUauvqjO1ppVTNz1nrLJzKY/ N6DdkzQOWtm0gNSivfphMtviygJ90HIR+B1frOeJtHRp1z4HmVEbGgmKYe1SfVk4 BHYz0VDrTeqyd0DY8oRiR0gtHxsCVxCelrHJGK/jh2ZSH+jA5LUj5F4+kvEDpxZC PdwKdCfXIzQSOXoGzUFy7OOq3zrnNvdZertxT9Y2Rc74fBLLmym/WqqC/ZpCVy6m +SrGoiG0jqnkYb2taagE3+fgRlWm3b/HP/47xAMi3FDgxhC6m6yVahCMS1+9ZxO1 rs6f6G5R2Bnsjmhtgyqi0ULbkCH81MnOLf7aK6cBtmZ/OkkNpHhBF0OFki+XzOFB 9NCEHg7TWTWNP00YFMeRlZLqKvVj42Cn9cffQz+wsVDAO4Cb2lc= =iJnj -----END PGP SIGNATURE----- --DUWhYKd617V0IXTgdZAOgU0sVtB7v3vTP-- From owner-freebsd-current@freebsd.org Fri Mar 23 15:45:39 2018 Return-Path: Delivered-To: freebsd-current@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 267A8F52DE7 for ; Fri, 23 Mar 2018 15:45:39 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 964EC7AB05 for ; Fri, 23 Mar 2018 15:45:38 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 44569 invoked from network); 23 Mar 2018 15:45:36 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 15:45:36 -0000 Subject: Re: two NIC's in a jail To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> From: Joerg Surmann Message-ID: Date: Fri, 23 Mar 2018 16:45:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0TTFhAyFe7E7t1E11gehlgrHG5X8TURKe" X-Mailman-Approved-At: Fri, 23 Mar 2018 16:29:39 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:45:39 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0TTFhAyFe7E7t1E11gehlgrHG5X8TURKe Content-Type: multipart/mixed; boundary="oDk8OBSzAxwFs8fcs1DAhjILq0X6gqRZy"; protected-headers="v1" From: Joerg Surmann To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org Message-ID: Subject: Re: two NIC's in a jail References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> --oDk8OBSzAxwFs8fcs1DAhjILq0X6gqRZy Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Thanks for replay. netstat -an | egrep 'tcp4.*80 .*LISTEN' say: netstat: kvm not available: /dev/mem No such file or directory <- is inside a jail. tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0 *.80=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 = LISTEN grep -i Listen /usr/local/etc/apache24/httpd.conf Listen 80 Listen 443 =46rom the internal IP is no Problem. You are right. I'm not sure on wich IP's Apache is listening. I have change the Listen directive to the external IP in httpd.conf Listen 213.70.80.92:80 netstat -an | egrep 'tcp4.*80 .*LISTEN' now say: tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0=C2=A0 213= =2E70.80.92:80=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 LISTEN But apache is not availble from Internet. =46rom Intranet... no Problem. When i use tcpdump on Host i can see Traffic. Whats wrong? Am 23.03.2018 um 16:07 schrieb Miroslav Lachman: > Joerg Surmann wrote on 2018/03/23 13:49: >> Hi all, >> >> I have a Problem to understund how to manage 2 Networks inside a Jail.= >> >> i have create a jail (using ezjail) with a alias IP. >> in rc.conf (on Host): >> >> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0= <- this >> is the jail ip >> >> Inside the jail running apachhe24. >> >> Now i add a new NIC to the System. >> in rc.conf (on Host): >> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >> >> in /usr/local/etc/ezjail/myjail.conf: >> i add the new ip >> export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >> >> Restart the jail and ifconfig looks fine. >> vmx0 -> inet 192.168.100.2 >> em0=C2=A0 -> inet 213.70.80.92 >> >> Apache Listen on all NIC's () >> But i can see my Website only via 192.168.100.2 from intern Network. >> >> The Host is behind a Firewall. >> The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. >> >> When i give the Hostname in a Browser i become "connection Timeout". >> >> What is to do that the Host is accessable from Inet? > > Are you sure Apache is listening on both IPs? > > What netstat says? > > # netstat -an | egrep 'tcp4.*80 .*LISTEN' > > Also check what you have in httpd.conf for Listen directive > > # grep -i Listen /usr/local/etc/apache24/httpd.conf > > I am not using ezjail, I am using jail.conf > > costa { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 host.hostname=C2=A0=C2=A0 =3D= "costa.example.com"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 =3D AA.BB.CCC.DDD; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 +=3D 192.168.222.57; > } > > Real IP was replaced with AA.BB.CCC.DDD > > And it works. Services inside jail must be listening on both IPs or > wildcard * (0.0.0.0) > > And be sure to disable hosts services to listen on IPs and ports you > want to be served from jail. > > Miroslav Lachman --oDk8OBSzAxwFs8fcs1DAhjILq0X6gqRZy-- --0TTFhAyFe7E7t1E11gehlgrHG5X8TURKe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1IRwACgkQGHz25TAa 4sts4hAAvWyhtPHyBtKVPm93x8N5Qkx1GP0rd4IJb/kZWdPkCF4dnFpOawxLDCC0 gmc1U9oBEUUnf+/dA0Yrf/iWgFX9nFJ1TBT9pyy4Ia8Kc/6hP1X3vz4WYVfScA93 IEHY9D//UGLct0ytx+7LJZQ03MMWgai59yJsrXIhSpnJ/NLad5cZJjU278HEkMuN 5u5N62jrP3ijRsUlOEOxib4WYMlojXbej9a/YnzAFZqOPOadQwq5wJY3UryeqpKY CwlkyzlYJp+o+Hnr2gOlW3zBj+1pTF52lTP3w8I1f2ham4Qq+BnabDaOsKq77B5d br1buzJCCNXVCSX0EoOc16G07nwmreT9tA8eSaJ5zjo14POsc5J4yeJP1xTSYvIg GJSpqVDF8RKHdmRHz/tWq7FWIYpKkitInXovTHgMsTSZ/UmdX8714tSfN6++cFM1 E3LIMlfMKh8fLr8WEiw9tYEhiF1bmtRraOgcm91qGGOF+42EZsaweewS9c+/hS4e D/SNMKWCe2v6VEEn8oEhMFLd9aNJ1ghBWJHfz+9JNuJHPiiXsKMdfjJzbaQUylJg d2B0PEL2bKuiyMm8so15SxpNidcS9L2IwwnzyKXr4YGlWvKVnoJGRMM/cynqU5R+ N5VVtiaxAHk7eAXtjGr7ygCRo9GAUDh3/rvdCo3P7bwLkSf14jo= =8xoF -----END PGP SIGNATURE----- --0TTFhAyFe7E7t1E11gehlgrHG5X8TURKe-- From owner-freebsd-current@freebsd.org Fri Mar 23 15:51:27 2018 Return-Path: Delivered-To: freebsd-current@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 2BCB7F53812 for ; Fri, 23 Mar 2018 15:51:27 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CB1D7B11C for ; Fri, 23 Mar 2018 15:51:26 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 45745 invoked from network); 23 Mar 2018 15:51:24 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 15:51:24 -0000 Subject: Re: two NIC's in a jail To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> From: Joerg Surmann Message-ID: <0960a59d-ec5d-5ad1-9132-cc8a68f92adf@elektropost.org> Date: Fri, 23 Mar 2018 16:51:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zmmwBEkKXzk6kuAHYuUzm1fJVmreVyC39" X-Mailman-Approved-At: Fri, 23 Mar 2018 18:05:43 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 15:51:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --zmmwBEkKXzk6kuAHYuUzm1fJVmreVyC39 Content-Type: multipart/mixed; boundary="4Fr0elwfgQHi4FW7XDd7AUlnpEnQ0p2m4"; protected-headers="v1" From: Joerg Surmann To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@freebsd.org Message-ID: <0960a59d-ec5d-5ad1-9132-cc8a68f92adf@elektropost.org> Subject: Re: two NIC's in a jail References: <63ecbccc-48e2-4c67-fbf5-0a73094f29be@elektropost.org> <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> In-Reply-To: <31fe7e04-4373-2454-aff5-0bd74b3f4b4e@quip.cz> --4Fr0elwfgQHi4FW7XDd7AUlnpEnQ0p2m4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Thanks for replay. netstat -an | egrep 'tcp4.*80 .*LISTEN' say: netstat: kvm not available: /dev/mem No such file or directory <- is inside a jail. tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0 *.80=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 = LISTEN grep -i Listen /usr/local/etc/apache24/httpd.conf Listen 80 Listen 443 =46rom the internal IP is no Problem. You are right. I'm not sure on wich IP's Apache is listening. I have change the Listen directive to the external IP in httpd.conf Listen 213.70.80.92:80 netstat -an | egrep 'tcp4.*80 .*LISTEN' now say: tcp4=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 0=C2=A0 213= =2E70.80.92:80=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 *.*=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 LISTEN But apache is not availble from Internet. =46rom Intranet... no Problem. When i use tcpdump on Host i can see Traffic. Whats wrong? Am 23.03.2018 um 16:07 schrieb Miroslav Lachman: > Joerg Surmann wrote on 2018/03/23 13:49: >> Hi all, >> >> I have a Problem to understund how to manage 2 Networks inside a Jail.= >> >> i have create a jail (using ezjail) with a alias IP. >> in rc.conf (on Host): >> >> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0= <- this >> is the jail ip >> >> Inside the jail running apachhe24. >> >> Now i add a new NIC to the System. >> in rc.conf (on Host): >> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >> >> in /usr/local/etc/ezjail/myjail.conf: >> i add the new ip >> export jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >> >> Restart the jail and ifconfig looks fine. >> vmx0 -> inet 192.168.100.2 >> em0=C2=A0 -> inet 213.70.80.92 >> >> Apache Listen on all NIC's () >> But i can see my Website only via 192.168.100.2 from intern Network. >> >> The Host is behind a Firewall. >> The IP=C2=A0 213.70.80.92 is enabled for incomming Traffic. >> >> When i give the Hostname in a Browser i become "connection Timeout". >> >> What is to do that the Host is accessable from Inet? > > Are you sure Apache is listening on both IPs? > > What netstat says? > > # netstat -an | egrep 'tcp4.*80 .*LISTEN' > > Also check what you have in httpd.conf for Listen directive > > # grep -i Listen /usr/local/etc/apache24/httpd.conf > > I am not using ezjail, I am using jail.conf > > costa { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 host.hostname=C2=A0=C2=A0 =3D= "costa.example.com"; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 =3D AA.BB.CCC.DDD; > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ip4.addr=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 +=3D 192.168.222.57; > } > > Real IP was replaced with AA.BB.CCC.DDD > > And it works. Services inside jail must be listening on both IPs or > wildcard * (0.0.0.0) > > And be sure to disable hosts services to listen on IPs and ports you > want to be served from jail. > > Miroslav Lachman --4Fr0elwfgQHi4FW7XDd7AUlnpEnQ0p2m4-- --zmmwBEkKXzk6kuAHYuUzm1fJVmreVyC39 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1InkACgkQGHz25TAa 4suLjA//csxgRHoYochsJbpkcMpXhf5vnBOXHMzOu822oxk4nzenPie2Hv3T2UFf HaLILUP22fEvF8v1ZoddOkZmZek3C/dGjEgKY3LzRT2qIhyedwpeiLuuw4hOO6xX IQ1nCtBBywXhZfiu6fEH3MLUogZByQ1JkmKA5HdW1/NUBL9eotNJj63VTkBkK7cD b9TwuiKcJCFF8vfmle/5J/gw64DLX8/HrnZvwKZVQRpiz3LzqKwJ1VEBWfS5ebij 0OxQ4cPsAV+dSokbCrHY7IUqq2fajFxkcZ/VkvlJESg+ATUV0spdaTNVAi5ZkVak jk/bX/x7NyojEL3yBf1sfQvhVwuE2o8UDC8/hzx/MgsqVekQR/FL62hpRW6nrNLI iTN3yge+QGXwH30zwLTXCqOpYQB2QmAIqIaCfT+j3/mJMCVh0xicmnAEE0FUOsvt cVeBq44D6zvs2kD1uWUabbnMztA8U50Csm0AZjI4Nxc1q7F5cyqtliRn/4DL9cT0 YhkY317EYPN3W1hupry8+O/OgGQ+v+9qX8uLaBc/FTL34uN88LA3IFvCLey2x44B pEuQjzyQKhc3wC0jdDIkOT3ReU9aZjE5d8Q0ceGu8w73u4+wHgo6roSPpkHnwHZS HgKoJuU3lnQHo37pROB9ztQafQBDVlqz+9UW9kBrYmt1b+HamKA= =jQIg -----END PGP SIGNATURE----- --zmmwBEkKXzk6kuAHYuUzm1fJVmreVyC39-- From owner-freebsd-current@freebsd.org Fri Mar 23 19:11:48 2018 Return-Path: Delivered-To: freebsd-current@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 BE684F65A64 for ; Fri, 23 Mar 2018 19:11:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72E9387022; Fri, 23 Mar 2018 19:11:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 22C7D10A7DB; Fri, 23 Mar 2018 15:11:47 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: AN , "markj@FreeBSD.org" , "" Subject: Re: problem with [intr{swi4: clock (0)}] Date: Fri, 23 Mar 2018 12:11:03 -0700 Message-ID: <1901802.BMbLzLVd8F@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 23 Mar 2018 15:11:47 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 19:11:49 -0000 On Wednesday, March 21, 2018 11:36:48 AM AN wrote: > Hi: > > I would appreciate any help with this issue, this is a new machine built > in the last week and if it is a hardware issue I want to return it. The > problem seems to have started in the last 24 hours or so. I am seeing a > really high cpu utilization for [intr{swi4: clock (0)}]. I have tried a > couple things to troubleshoot: I would try using dtrace to figure out which functions are running in the callout thread. I've cc'd a couple of folks in case they already have dtrace scripts to do this. You would probably want a script that watched callout_execute::callout-start and callout_execute::callout-end events. You would want to save the start time in callout-start and then report a delta along with the values of 'c->c_func' (the last argument to these probes is 'c'). You might be able to just store the time delta in an aggregate that is keyed on the function. Actually, I've gone ahead and written a little script: ---- callout_execute:::callout-start { self->start = timestamp; self->func = args[0]->c_func; @funcs[self->func] = count(); } callout_execute:::callout-end { @functimes[self->func] = sum(timestamp - self->start); } END { printf("\n\nCallout function counts:\n"); printa("%@8u %a\n", @funcs); printf("\nCallout function runtime:\n"); printa("%@d %a\n", @functimes); } ---- Store this in a file named 'callout.d' and then run 'dtrace -s callout.d'. Let it run for a second or two and then use Ctrl-C to stop it. The first table it will output is a histogram showing how many times different functions were invoked. The second table will count how much total time was spent in each function: CPU ID FUNCTION:NAME 4 2 :END Callout function counts: 2 kernel`kbdmux_kbd_intr_timo 2 kernel`usb_power_wdog 2 kernel`ipport_tick 2 kernel`tcp_timer_delack 2 kernel`nd6_timer 2 kernel`key_timehandler 2 dtrace.ko`dtrace_state_deadman 4 kernel`newnfs_timer 4 kernel`pfslowtimo 10 kernel`logtimeout 10 kernel`pffasttimo 18 kernel`lim_cb 32 kernel`iflib_timer 84 kernel`sleepq_timeout 224 dtrace.ko`dtrace_state_clean Callout function runtime: 2080 kernel`logtimeout 2198 kernel`kbdmux_kbd_intr_timo 2890 kernel`ipport_tick 3550 kernel`iflib_timer 3672 kernel`lim_cb 3936 kernel`pffasttimo 4023 dtrace.ko`dtrace_state_clean 4224 kernel`newnfs_timer 4751 kernel`key_timehandler 5286 kernel`nd6_timer 6700 kernel`usb_power_wdog 7341 kernel`pfslowtimo 19607 kernel`tcp_timer_delack 20273 dtrace.ko`dtrace_state_deadman 32262 kernel`sleepq_timeout You can use this to figure out which timer events are using CPU in the softclock thread/process. -- John Baldwin From owner-freebsd-current@freebsd.org Fri Mar 23 19:17:30 2018 Return-Path: Delivered-To: freebsd-current@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 E86DFF66266 for ; Fri, 23 Mar 2018 19:17:29 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F833874B0 for ; Fri, 23 Mar 2018 19:17:29 +0000 (UTC) (envelope-from joerg_surmann@elektropost.org) Received: (qmail 93349 invoked from network); 23 Mar 2018 19:17:28 -0000 Received: from elektropost.org (HELO elektropost.org) (joerg?surmann) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 23 Mar 2018 19:17:28 -0000 Subject: Re: Two NIC's inside a Jail To: Marek Zarychta Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> From: joerg_surmann Message-ID: Date: Fri, 23 Mar 2018 20:17:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180323172504.GA55971@plan-b.pwste.edu.pl> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 19:17:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv Content-Type: multipart/mixed; boundary="XLdbuKE7TcH5190G2OxcWomUP464lUdtA"; protected-headers="v1" From: joerg_surmann To: Marek Zarychta Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Message-ID: Subject: Re: Two NIC's inside a Jail References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> In-Reply-To: <20180323172504.GA55971@plan-b.pwste.edu.pl> --XLdbuKE7TcH5190G2OxcWomUP464lUdtA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: de-DE Hi, thanks for yor help. I can't find a solution. But i have find a starnge ip config. in rc.conf on Host(not jail) ifconfig_vmx0_alias1=3D"inet 192.168.100.2=C2=A0 netmask 255.255.255.0" ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" ifconfig on host say: inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 inet 192.168.100.2=C2=A0 netmask 0xffffffff broadcast 192.168.100.2 ifconfig say to both ip's /32. Maby that's the reason for unavailable the apache. ifconfig iside the jail say the same. I'm a little bit confused. Am 23.03.2018 um 18:25 schrieb Marek Zarychta: > On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote: >> Hi all, >> >> I have a Problem to understund how to manage 2 Networks inside a Jail.= >> >> i have create a jail (using ezjail) with a alias IP. in rc.conf (on >> Host): >> >> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0"=C2=A0= <- >> this is the jail ip >> >> Inside the jail running apachhe24. >> >> Now i add a new NIC to the System. in rc.conf (on Host): >> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >> >> in /usr/local/etc/ezjail/myjail.conf: i add the new ip export >> jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >> >> Restart the jail and ifconfig looks fine. vmx0 -> inet 192.168.100.2 >> em0=C2=A0 -> inet 213.70.80.92 >> >> Apache Listen on all NIC's () But i can see my >> Website only via 192.168.100.2 from intern Network. >> >> The Host is behind a Firewall. The IP=C2=A0 213.70.80.92 is enabled f= or >> incomming Traffic. >> >> When i give the Hostname in a Browser i become "connection Timeout". >> >> What is to do that the Host is accessable from Inet? >> > Hi Joerg,=20 > > I guess your host has default gw reachable via vmx0 and second interfac= e > em0 is connected and was reachable at least from firewall protecting > address 213.70.80.92? If it is true then you should add:=20 > > to /usr/local/etc/ezjail/myjail.conf=20 > export jail_myjail_ip=3D"lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80= =2E92" > export jail_myjail_fib=3D"1" > > to /etc/rc.conf > static_routes=3D"net_jails" > route_net_jails=3D"default 213.70.80.x -fib 1" > > to /boot/loader.conf > net.fibs=3D"2" > > Eventually take a look at setfib(1) and also consider migrating em > adapter to second vmx which shuld be faster and more flexible. > > IMHO this questions should be asked rather on freebsd-net list than > here. --XLdbuKE7TcH5190G2OxcWomUP464lUdtA-- --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEEKgIE1afOeXZNzpBEGHz25TAa4ssFAlq1UscACgkQGHz25TAa 4stliw//U8XD9nn0MOnrgTW3nROyAaYIcLn1S8VMMT9iTMILIh8nM4RDpU3wMZ9l TjjFQihgihJzOI2GLGBIpyCV3iwaG1PWjkTRT9ed+weI+8drhFx1IXlbFtWKxIt3 8dYYfH/30RRrudzJSdB+bOgwkPvRM+AXpB4ydIzZPvtG/WKRZqG7J/H4l31udLfh i2oBqjV6jeaq/z8LU0gJ8H0BlZUVnEzRtUojKXmGeyOsffKB5DAU89iCGl5rikuJ /z8ob6o0+OiRkpoDq0wKIwqw4ZWLXNINMn7bYbhtXay3p+ItVagPBO5ih2bX9ZLi Xdv3YK7xx+qmg7qzWLUBMWyivF5MeYKn7PNT+vVpNwNm9A/ANjQ9uuR6sL7XjVM5 a9xC2vpRf/DCHaExUBbRwD1KbkbUtSrkiEriOqJVXUv5D9HHRpSQ2IplV1WevbQg 8cA4+0PfV2+pbDf1sMzKIxYLrZEdRlS0IKu1qpsq5YJvEjV11+NDYgdFfN6F4xbK DnXlxL39sFhTX1d0J4q3iBTt9UZaP9fsx1INDVqwa/WDOblutFcgzdcINi/cWOOW z0iEsb+MPCGHh1Iu6/xLgWw9QqldRdQYOuPay2R3oxzCQMiLDicQRBAGf3HVuG2o fm22wRoEMABnX6+NfznofRY5wPfxGCnWYpSK0KPa0NHCVq5apvY= =yYf7 -----END PGP SIGNATURE----- --QabuUyHbzzRJWlhPrBEMbgUkV38HLlAPv-- From owner-freebsd-current@freebsd.org Fri Mar 23 19:48:27 2018 Return-Path: Delivered-To: freebsd-current@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 97C9EF68E44 for ; Fri, 23 Mar 2018 19:48:27 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::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 0C1E888F56 for ; Fri, 23 Mar 2018 19:48:27 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22d.google.com with SMTP id c24so13244857wrc.6 for ; Fri, 23 Mar 2018 12:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bEDEUYK8wmYoj1Vg/ciPVvLTSvWgpB3fJhM3HO92TCY=; b=nqF1icOIW9DovJBZnyghjEgkK7hYydZkuausCWgLDtuMcd+9kOXhUuxD4Xbwm2mSeL RrN9ywJMgEeQd4ueleRMueqUifuTxHAMzOzO9Sj4DoSCIBlPD6wrFEPD52l4zl8lL4C+ qqQxHGQodJkW21l3C/I+UQnMjw/QpCQ4m8X7UPMv2dyzOWlE2bDuYS/ydIY0sgmZ6dNE SkHVZ7+3W7q7oSqV3bO991SpdIn7tnReKuHKzdXSJ1zgcdRZQil2xbg3ESFqagb36lOo Dvv6f3OWkj99Mp6L6RWkVlAOSMrt6zHxL0X+8iykeGkkgMU1PM7mWXuMManjFuP0JXEM LHzQ== 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=bEDEUYK8wmYoj1Vg/ciPVvLTSvWgpB3fJhM3HO92TCY=; b=aD5hPYsYNxabdEoZ4c7ZsQAH63Bi5GH0aS9PykCU8MEHKQzy28NhRufNQi3Uthl6IS S9ro+vMoyCkp8C1QZOsnsl3hH9AxD6tCwiw2eiQG90dKslsoZ7QnvUhXqADcwNdpi5Sm 4E8Z34IpUdZL3A1qHr6VrHH8YrknkAgvI82J0gcmo1vk+1g1mYDKZKUOS3RYMvJfBe8X U5Ovj3kcOm5jtZurtXVPbNvbTon+YFgfG3eCx3238R7ZROk/RMaHn2gQ33+2HLhDX1re LaoqLGb9OavkJxqMZDKkEhtsn3kTdyJLGo+hqUDhgxks3nmfcHUxYHGbLW3MabQ/3Kdj XJ1g== X-Gm-Message-State: AElRT7HP0FLOo1I9xrbsIfv/42OQdAjRybfSPVsZqD1bt/4lKZKJLLJK 4Fy5dbS/I1V3kIM83BCqS7jreBLPp67tAaSFXZM= X-Google-Smtp-Source: AG47ELvFiEiN1qj6WVau51yAqXWt+44qDm4w+sJwfkbwC/ZVu7rK4xJNti8qFDNzOoDQUHxcosu7SRQGdll/npg/bKs= X-Received: by 10.223.170.66 with SMTP id q2mr9365066wrd.140.1521834505384; Fri, 23 Mar 2018 12:48:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Fri, 23 Mar 2018 19:48:15 +0000 Message-ID: Subject: Re: problem with [intr{swi4: clock (0)}] To: AN Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 19:48:27 -0000 On Wed, Mar 21, 2018 at 15:38 AN wrote: > Hi: > > I would appreciate any help with this issue, this is a new machine built > in the last week and if it is a hardware issue I want to return it. The > problem seems to have started in the last 24 hours or so. I am seeing a > really high cpu utilization for [intr{swi4: clock (0)}]. I have tried a > couple things to troubleshoot: > > rebuilt world and kernel > turned off Virtualbox ( did not load kernel module) > turned off in BIOS network, audio > installed disk from another similar machine, booted and it shows the exac= t > same problem. > > Here is what I see in top: > last pid: 56553; load averages: 0.09, 0.44, 0.26 > up 0+00:04:38 11:25:24 > 472 processes: 14 running, 418 sleeping, 40 waiting > CPU 0: 0.0% user, 0.0% nice, 0.0% system, 27.5% interrupt, 72.5% idle > CPU 1: 0.7% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.3% idle > CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 3: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 4: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 5: 0.0% user, 0.0% nice, 0.7% system, 0.0% interrupt, 99.3% idle > CPU 6: 0.8% user, 0.0% nice, 0.8% system, 0.0% interrupt, 98.5% idle > CPU 7: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 8: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 9: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 10: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > CPU 11: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle > Mem: 1096M Active, 53M Inact, 300K Laundry, 568M Wired, 290M Buf, 14G Fre= e > Swap: 21G Total, 21G Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root 155 ki31 0K 192K CPU1 1 4:32 100.00% > [idle{idle: cpu1}] > 11 root 155 ki31 0K 192K CPU8 8 4:31 100.00% > [idle{idle: cpu8}] > 11 root 155 ki31 0K 192K CPU9 9 4:30 100.00% > [idle{idle: cpu9}] > 11 root 155 ki31 0K 192K CPU2 2 4:30 100.00% > [idle{idle: cpu2}] > 11 root 155 ki31 0K 192K CPU10 10 4:30 100.00% > [idle{idle: cpu10}] > 11 root 155 ki31 0K 192K CPU5 5 4:27 100.00% > [idle{idle: cpu5}] > 11 root 155 ki31 0K 192K RUN 11 4:25 99.82% > [idle{idle: cpu11}] > 11 root 155 ki31 0K 192K CPU6 6 4:30 98.93% > [idle{idle: cpu6}] > 11 root 155 ki31 0K 192K CPU7 7 4:31 96.83% > [idle{idle: cpu7}] > 11 root 155 ki31 0K 192K CPU3 3 4:27 94.94% > [idle{idle: cpu3}] > 11 root 155 ki31 0K 192K CPU4 4 4:29 94.11% > [idle{idle: cpu4}] > 11 root 155 ki31 0K 192K RUN 0 3:45 71.60% > [idle{idle: cpu0}] > 12 root -60 - 0K 656K CPU0 0 0:53 28.43% > [intr{swi4: clock (0)}] > > > 28.20% [intr{swi4: clock (0)}] - the process is using close to 30% cpu > time. > > I have no idea what could be causing this, any advice would be > appreciated. Thanks in advance. > > 12 root -60 - 0K 656K WAIT 0 1:27 28.80% [intr{swi4: > clock (0)}] > > systat shows: > > 1 users Load 0.20 0.16 0.18 Mar 21 11:35 > Mem usage: 11%Phy 1%Kmem > Mem: KB REAL VIRTUAL VN PAGER SWAP > PAGER > Tot Share Tot Share Free in out in > out > Act 1357104 111928 4267688 193328 14176K count > All 1357984 112656 4285556 211028 pages > Proc: > Interrupts > r p d s w Csw Trp Sys Int Sof Flt 8 ioflt 996k > total > 1 314 2.0 296 2213 133 1.0 155 cow > atkbd0 1 > 8 zfod 996k > cpu0:timer > 0.1%Sys 1.9%Intr 0.1%User 0.0%Nice 98.0%Idle ozfod 68 > xhci0 259 > | | | | | | | | | | %ozfod > ahci0 260 > + daefr 5 re0 > 261 > 4 dtbuf prcfr > hdac0 262 > Namei Name-cache Dir-cache 349771 desvn 21 totfr > hdac1 280 > Calls hits % hits % 3740 numvn react 4 > cpu6:timer > 474 474 100 958 frevn pdwak 5 > cpu10:time > 456 pdpgs 11 > cpu7:timer > Disks ada0 pass0 intrn 10 > cpu11:time > KB/t 0.00 0.00 469596 wire 3 > cpu1:timer > tps 0 0 1121780 act 2 > cpu8:timer > MB/s 0.00 0.00 170492 inact 8 > cpu9:timer > %busy 0 0 300 laund 5 > cpu4:timer > 14516016 free 2 > cpu2:timer > 183472 buf 7 > cpu5:timer > 7 > cpu3:timer > > FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #18 r331138: Sun Mar 18 > 16:08:31 EDT 2018 > root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1200060 > > FreeBSD 12.0-CURRENT #18 r331138: Sun Mar 18 16:08:31 EDT 2018 > root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 > FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLV= M > 6.0.0) > VT(vga): resolution 640x480 > CPU: AMD Ryzen 5 1600X Six-Core Processor (3600.10-MHz K8-clas= s > CPU) > Origin=3D"AuthenticAMD" Id=3D0x800f11 Family=3D0x17 Model=3D0x1 St= epping=3D1 > > > Features=3D0x178bfbff > > > Features2=3D0x7ed8320b > AMD Features=3D0x2e500800 > AMD > > Features2=3D0x35c233ff > Structured Extended > > Features=3D0x209c01a9 > XSAVE Features=3D0xf > AMD Extended Feature Extensions ID EBX=3D0x7 > SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 > TSC: P-state invariant, performance statistics > real memory =3D 17179869184 (16384 MB) > avail memory =3D 16596353024 (15827 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs > FreeBSD/SMP: 1 package(s) x 2 cache groups x 3 core(s) x 2 hardware > threads > random: unblocking device. > Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid > Length but zero Address: 0x0000000000000000/0x1 (20180313/tbfadt-796) > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-55 on motherboard > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff809e79e0, 0) error 19 > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > nexus0 > vtvga0: on motherboard > cryptosoft0: on motherboard > acpi0: on motherboard > Hi! I had a similar problem caused by interrupt storm from the GPU on a MacBook. The problem is described here: https://bugs.freedesktop.org/show_bug.cgi?id=3D98501 I disabled that IRQ by using a custom acpi config. I know it=E2=80=99s not = the same hardware but might give I can share more details tomorrow when I=E2=80=99m at my computer if you th= ink this might be related. > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Fri Mar 23 20:23:32 2018 Return-Path: Delivered-To: freebsd-current@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 7D955F6B815; Fri, 23 Mar 2018 20:23:32 +0000 (UTC) (envelope-from chris@tellme3times.com) Received: from mail.tellme3times.com (j90z.x.rootbsd.net [208.86.227.78]) (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 1F5BB8A7DD; Fri, 23 Mar 2018 20:23:31 +0000 (UTC) (envelope-from chris@tellme3times.com) Received: from gatekeeper.tellme3times.com (modemcable074.25-70-69.static.videotron.ca [69.70.25.74]) by mail.tellme3times.com (Postfix) with ESMTP id 947C394104B; Fri, 23 Mar 2018 16:15:17 -0400 (EDT) Received: from [192.168.7.61] (unknown [192.168.7.61]) by gatekeeper.tellme3times.com (Postfix) with ESMTP id 35E8D3727C; Fri, 23 Mar 2018 16:15:17 -0400 (EDT) From: Chris Kiakas Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Two NIC's inside a Jail Date: Fri, 23 Mar 2018 16:14:27 -0400 In-Reply-To: Cc: Marek Zarychta , freebsd-stable@freebsd.org, freebsd-current@freebsd.org To: joerg_surmann References: <785ce70f-3f2d-3422-0e95-146b05f7f768@elektropost.org> <20180323172504.GA55971@plan-b.pwste.edu.pl> X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 20:23:32 -0000 --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Sorry that I am coming to the conversation a little late. I have several = systems Which run with multiple IP connections where the jail responds = to multiple IPs I set /etc/rc.conf to just control the ips of the host. as an example; ifconfig_igb1=3D"inet AAA.AAA.AAA.1 netmask 255.255.255.0" defaultrouter=3D=E2=80=9CAAA.AAA.AAA.1=E2=80=9D ifconfig_igb2=3D"inet 192.168.10.1 netmask 255.255.255.0" ifconfig_igb4=3D"UP" ifconfig_igb5=3D"UP" ifconfig_igb6=3D"UP" ifconfig_igb7=3D"UP" cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"laggproto lacp laggport igb4 laggport igb5 laggport = igb6 laggport igb7 192.168.12.14/24=E2=80=9D The jail is then set with it=E2=80=99s jail.conf file as such; jailname { host.hostname =3D =E2=80=9Cjailname"; ip4.addr =3D =E2=80=9Cigb1|AAA.AAA.AAA.2/24=E2=80=9D; ip4.addr +=3D =E2=80=9Cigb2|192.168.10.21/24=E2=80=9D; ip4.addr +=3D "lagg0|192.168.12.32/24"; path =3D "/usr/jail/jailname"; exec.start =3D "/bin/sh /etc/rc"; exec.stop =3D "/bin/sh /etc/rc.shutdown"; exec.consolelog =3D "/var/log/jail.jailname.console.log"; mount.devfs; } My interfaces are igb# your's are em0 Apache is set to listen to; Listen :80 If the Apache setup is not complex it should just work on all IP. If you = are running vhosts you will need to specify ServerName and/or = ServerAliases in apache. If the jail requires a different gateway than the defaultrouter then you = will need to setup fibs. Chris > On Mar 23, 2018, at 3:17 PM, joerg_surmann = wrote: >=20 > Hi, >=20 > thanks for yor help. >=20 > I can't find a solution. >=20 > But i have find a starnge ip config. >=20 > in rc.conf on Host(not jail) >=20 > ifconfig_vmx0_alias1=3D"inet 192.168.100.2 netmask 255.255.255.0" > ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >=20 > ifconfig on host say: > inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 > inet 192.168.100.2 netmask 0xffffffff broadcast 192.168.100.2 >=20 > ifconfig say to both ip's /32. >=20 > Maby that's the reason for unavailable the apache. >=20 > ifconfig iside the jail say the same. >=20 > I'm a little bit confused. >=20 >=20 >=20 > Am 23.03.2018 um 18:25 schrieb Marek Zarychta: >> On Fri, Mar 23, 2018 at 04:01:30PM +0100, Joerg Surmann wrote: >>> Hi all, >>>=20 >>> I have a Problem to understund how to manage 2 Networks inside a = Jail. >>>=20 >>> i have create a jail (using ezjail) with a alias IP. in rc.conf (on >>> Host): >>>=20 >>> ifconfig_vmx0=3D"inet 192.168.100.1 netmask 255.255.255.0" >>> ifconfig_vmx0_alias0=3D"inet 192.168.100.2 netmask 255.255.255.0" = <- >>> this is the jail ip >>>=20 >>> Inside the jail running apachhe24. >>>=20 >>> Now i add a new NIC to the System. in rc.conf (on Host): >>> ifconfig_em0=3D"inet 213.70.80.92 netmask 255.255.255.0" >>>=20 >>> in /usr/local/etc/ezjail/myjail.conf: i add the new ip export >>> jail_myjail_ip=3D"192.168.100.2,213.70.80.92" >>>=20 >>> Restart the jail and ifconfig looks fine. vmx0 -> inet = 192.168.100.2 >>> em0 -> inet 213.70.80.92 >>>=20 >>> Apache Listen on all NIC's () But i can see my >>> Website only via 192.168.100.2 from intern Network. >>>=20 >>> The Host is behind a Firewall. The IP 213.70.80.92 is enabled for >>> incomming Traffic. >>>=20 >>> When i give the Hostname in a Browser i become "connection Timeout". >>>=20 >>> What is to do that the Host is accessable from Inet? >>>=20 >> Hi Joerg, >>=20 >> I guess your host has default gw reachable via vmx0 and second = interface >> em0 is connected and was reachable at least from firewall protecting >> address 213.70.80.92? If it is true then you should add: >>=20 >> to /usr/local/etc/ezjail/myjail.conf >> export = jail_myjail_ip=3D"lo1|127.0.1.1,vmx0|192.168.100.2,em0|213.70.80.92" >> export jail_myjail_fib=3D"1" >>=20 >> to /etc/rc.conf >> static_routes=3D"net_jails" >> route_net_jails=3D"default 213.70.80.x -fib 1" >>=20 >> to /boot/loader.conf >> net.fibs=3D"2" >>=20 >> Eventually take a look at setfib(1) and also consider migrating em >> adapter to second vmx which shuld be faster and more flexible. >>=20 >> IMHO this questions should be asked rather on freebsd-net list than >> here. >=20 >=20 --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC 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----- iQIzBAEBCgAdFiEEi+l+WvjUMve3CBUQ0McJ9XNZ9LEFAlq1YCMACgkQ0McJ9XNZ 9LEplxAAiSrcOP0KVLb1TFuR3NximPUObOk7OPk0ueX4ZW6RaLOMZ/7D1m/tnIl/ TUjLlflzyUeAtXHVj9rYbqXMwpL6ftCtd6U/YAz6kqX5nq3k6vkqE2NjJcFd8Jh0 V0svjA4xMOVai3+M2eBf8CWnYFQT62ekbqK1wTon5vL8us/4VHXIjY81vGugMI6J f3m+94xVE9HHTX79Nrc39cQ/4IAcskdCjF5SgWFSc5GBo/2yh2Sgl3NYUsysPPdV M+/oUqg8ZDKO2PGrHUr02+oPnoRdFoh/1DpT0i0jNjgKlqDiysYy2qI9n+6u9TOL T5OmMmaAoPaVg+0N+2JaH8jvPYv8PCZPcaIhl4YaZlm10liLEXN23riDxv3Wgf6a A52nMJZOjqt+2QLs4eS5i5xhZqLay6SiqRuG9vcvc46WU5x9UyoxjixwYVP0wfyc WmlQEHTsrG6D8is2AphPEYfyc6c+f0ksSFYU7x3VvzoQiAU3QdgOW7DUbAbzpFC/ Du3VTLcy6skYl1qSI02b9V3olP6Ly3GtNVGVfZMEUc/wlmE8IyN4i5JZHj++tY6q amTRisEZQmfLJyyRrtxZKyCPOjmMRD4f9o/K2UUd+F1wmZqp0lklOlQFAu8hDch6 ew6LZgLIILE/MOFsG6b7swq+42AzFVsC9UzZt9su/b9VirbHZ6I= =vV0a -----END PGP SIGNATURE----- --Apple-Mail=_4E2C9BD6-B7A9-4D60-96EC-D0A8852A43FC-- From owner-freebsd-current@freebsd.org Fri Mar 23 21:01:42 2018 Return-Path: Delivered-To: freebsd-current@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 89187F6E59A; Fri, 23 Mar 2018 21:01:42 +0000 (UTC) (envelope-from benno@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AE2A8C67A; Fri, 23 Mar 2018 21:01:42 +0000 (UTC) (envelope-from benno@FreeBSD.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A2D7420DFB; Fri, 23 Mar 2018 17:01:41 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 23 Mar 2018 17:01:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=GSoh2J2M2IH1AKrh2UBc1L8P1PIDd 6o2uE3DJRO/dVY=; b=kaMQC3uTBEtrtk0k3v027Qza48d74SIoVlVX26AO8jFKy RQ6fUY5hZTCBkiQ7aIbV6MNX1uU3NnTiYdJQEod/10QPrO7z8Ew2yhV0LVp8jv5Y GFtFoYSbdVDkrkNtNokOhkxjbIE1KFSDdnIsUy8BJvPq/fSkhWgCVIhV5uNX8Ddw p9siOPfgcmh+KnKm4tk/7HBvvHZaP2sdp2UVwQc5d/g/DoDkbvmGDRAWlEf91UYa djQkAfdTpjKJzt9Ty0V8295WnO4/pasGIUeekvg83waAm1VBw29S9LZKEVD9cui/ GL6/AiLpPFyzP5MnkAfhC8tdkr6pPEivfQ/PPtPCw== X-ME-Sender: Received: from [10.57.111.169] (unknown [209.63.143.172]) by mail.messagingengine.com (Postfix) with ESMTPA id 0838B7E183; Fri, 23 Mar 2018 17:01:40 -0400 (EDT) From: Benno Rice Message-Id: <35FF5A67-B8CA-43C8-B39E-6797066CBD7E@FreeBSD.org> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Testing requested: Hybrid ISO/USB boot Date: Fri, 23 Mar 2018 14:01:39 -0700 In-Reply-To: <3373772881814803857@scdbackup.webframe.org> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org To: Thomas Schmitt References: <3373772881814803857@scdbackup.webframe.org> X-Mailer: Apple Mail (2.3445.5.20) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 21:01:42 -0000 > On Mar 22, 2018, at 1:48 PM, Thomas Schmitt wrote: >=20 > Hi, >=20 > Benno Rice wrote: >> I=E2=80=99ve been working on the ability to create hybrid ISO/HDD = boot images for >> x86, a la what Linux systems do with ISOHYBRID. >=20 > Waving friendly over the fence i feel entitled to give some neighbor's > review. Hello! Thanks for your response. [snip] >> https://people.freebsd.org/~benno/hybrid-bootonly.iso.xz >=20 > This does not look much like it addresses EFI. >=20 > $ xorriso -indev hybrid-bootonly.iso -report_el_torito plain = -report_system_area plain > ... > El Torito catalog : 19 1 > El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz = LBA > El Torito boot img : 1 BIOS y none 0x0000 0x00 4 = 20 > El Torito boot img : 2 BIOS y none 0x0000 0x00 1600 = 24 > ... > MBR partition table: N Status Type Start Blocks > MBR partition : 1 0x80 0xa5 1 16 >=20 > UEFI 2.4, 12.3.2.1, says about El Torito: > "A Platform Id of 0xEF indicates an EFI System Partition." > But entry 2 of this catalog is in a section with Platform Id 0x00 (x86 = BIOS). >=20 > If byte 38977 (decimal) was 0xef rather than 0x00, then it would be = marked > as an El Torito boot image for EFI. I think I=E2=80=99ve addressed this in this revision: https://svnweb.freebsd.org/changeset/base/331463 = And I=E2=80=99ve regenerated the image here: https://people.freebsd.org/~benno/hybrid-bootonly-20180323-00.iso.xz = > Further: This section begins at byte address 38976 by a byte value = 0x90. > According to El Torito specs this means that another section follows. > Correct would be value 0x91, which announces the end of the catalog. > (El Torito 1.0, Figure 4, Offset 0) I=E2=80=99ll look into this too. > On HDD, EFI looks for specially marked partitions in GPT or MBR = partition > table. > In MBR partiton table it looks for a partition of type 0xEF. > (UEFI 2.4, 5.2.2) > In GPT it looks for Type GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B. > (UEFI 2.4, Table 19) >=20 > So to mark the EFI partition, hybrid-bootonly.iso should have a MBR > partition number 2 with type 0xEF, start at 512-byte block 24*2048/512 = =3D 96, > size 1600 blocks. > (Strangely El Torito addresses by 2048-byte blocks but counts by = 512-byte > blocks. Size limit is 65535 blocks. But counts 0 and 1 mean to EFI > "up to end of medium=E2=80=9D.) I=E2=80=99ll look in to this one too. >> I=E2=80=99ve tested this image under qemu=20 >=20 > OVMF/SDK-II/Tianocore is too tolerant with the EFI specs and with = silently > using BIOS boot equipment. Real iron EFIs insist much more in = compliance. So it appears. Thanks again for looking at this! Thanks, Benno.= From owner-freebsd-current@freebsd.org Fri Mar 23 21:16:35 2018 Return-Path: Delivered-To: freebsd-current@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 5348EF6F933; Fri, 23 Mar 2018 21:16:35 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B0C188D371; Fri, 23 Mar 2018 21:16:34 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from scdbackup.webframe.org ([91.8.164.220]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MUHbK-1f8jBx149i-00R2pY; Fri, 23 Mar 2018 22:16:27 +0100 Date: Fri, 23 Mar 2018 22:14:41 +0100 From: "Thomas Schmitt" To: freebsd-hackers@freebsd.org Subject: Re: Testing requested: Hybrid ISO/USB boot Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org References: <35FF5A67-B8CA-43C8-B39E-6797066CBD7E@FreeBSD.org> In-Reply-To: <35FF5A67-B8CA-43C8-B39E-6797066CBD7E@FreeBSD.org> Message-Id: <31624772818301324998@scdbackup.webframe.org> X-Provags-ID: V03:K0:FKSV0wJv7Yo7JeIYvEDPbUaOlh0fjx4L9dbywZ75rhrs9PuQbiS UO7HxVCdWmyKJC5JDFT8xngvKzhZIrLUD42Xq+uGA0rnZROsNzZAb6ePqfZP8bLCKADsvar vm9x4kgewl++9E9nxTeP0fOZpyH7UywJHF0o0f5cFxeHiLHsGzqM2A8iVK3UkeDKuREC7EX dhB47EnO6CyAxswiADtBQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:sSR5wYRwZVI=:Q/jIOPJMJCNQRLudrf2T9I mGhvfxwIgxuARuLjR3cbI3THhhCA3FSCeIiDeD414skteEKvjP5MaW8/lGgr3nPQw0ffdwL/l I6EpvFTDThwC9caSVUy8OlrAzOObiUn3wO95Tm5rDJbLbMsrJmHBfPUCkTKNR3wuwTpXkOi7Q O1nH1yNkZR74xfdKQzZfzow6R29jWLN/qYfVCvfTGJzYL3Jns8OGWTHxjXf1hpGVgQ2QS8R9+ qa/ds1Fq2pIH4Xvm2liEwc7Qa0WyNqnYjN1pLbh/mb57pQANikwjHf6ZWTxmo99VPXSHq4Yij +NrIlNYrZTdG4I/QWWYPOL20w+bkuCx/agdh1hDyQIoM2hJ4lFZqiLh7k7PhdClQOR3nset7K 0ENrIbZEDN766aFe9g7HZaUVOhFFTfuwtxfydl/S87jknsWDZkGoT1FV2hONCCA0g5cs723Oi Ho3EQA3HrnMc09b0l3bsiRvYKV8HUJgAY8LmPfnoIIHT9Wb2u29RGXBkj2QIbMMJShmPzJwFc 8H7neUrxyWygnUF3E3/GhhgOJ/JOZ3KkzruXQGTRpoN2cr0+E7sTQ2QIsaJTKtZdKS6xbh5Ib kHKq3So7thO8IxytvcaoUmMa5xDveNHMuhtLLlf+lRsn7C5gDcGuNjRtJgP07l+YblWiPAk1T VJqibNRs2ZHWbl4OzuwI4EQiou22L63qQEx8oE4U7xZxXp7bKEgnSc0v6EI/NoAQbpKlV83Hm TCI/5NHGZGNHbkl8C8rjxsiaSApm6EZuPHKPKYMZVHnu52WgRN0PRN2WHvPkElS4fgwa0BzT6 efn5AypAUfuSqJ3dNIJ9hgqwj5FYJ8MPlK+X7FDTCDSz79e0Hg= X-Mailman-Approved-At: Fri, 23 Mar 2018 22:49:56 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 21:16:35 -0000 Hi, i wrote: > > If byte 38977 (decimal) was 0xef rather than 0x00, then it would be marked > > as an El Torito boot image for EFI. Benno Rice wrote: > I’ve regenerated the image here: > https://people.freebsd.org/~benno/hybrid-bootonly-20180323-00.iso.xz Looks better now: El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 20 El Torito boot img : 2 UEFI y none 0x0000 0x00 1600 24 Have a nice day :) Thomas From owner-freebsd-current@freebsd.org Fri Mar 23 23:19:19 2018 Return-Path: Delivered-To: freebsd-current@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 49F54F54BB4 for ; Fri, 23 Mar 2018 23:19:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B92016A608; Fri, 23 Mar 2018 23:19:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w2NNJ2Vg007096 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 01:19:06 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w2NNJ2Vg007096 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w2NNJ2ai007092; Sat, 24 Mar 2018 01:19:02 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 24 Mar 2018 01:19:02 +0200 From: Konstantin Belousov To: Mark Peek Cc: Peter Lei , freebsd-current@freebsd.org, huanghwh@163.com, "Jonathan T. Looney" Subject: Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts Message-ID: <20180323231902.GM76926@kib.kiev.ua> References: <8b8f1352-aa5c-716c-ef6c-3b3cd630043f@ieee.org> <20180316095627.GW76926@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 23:19:19 -0000 On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > I ran into the original issue with r330539 on a Fusion VM. Trying this > patch causes a different panic: > > https://people.freebsd.org/~mp/r330539-patched.png > > Thoughts? r331290 should fixed this issue. What is your kernel sources version ? From owner-freebsd-current@freebsd.org Fri Mar 23 23:21:39 2018 Return-Path: Delivered-To: freebsd-current@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 C577CF54FE5 for ; Fri, 23 Mar 2018 23:21:39 +0000 (UTC) (envelope-from bdrewery@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 6AEBC6AA29; Fri, 23 Mar 2018 23:21:39 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (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 3D0C7D974; Fri, 23 Mar 2018 23:21:39 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 285D7FC7; Fri, 23 Mar 2018 23:21:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id kR2SU8CXP9YB; Fri, 23 Mar 2018 23:21:35 +0000 (UTC) Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 8969CFC1 To: Peter Jeremy , Jeff Roberson Cc: FreeBSD current , Andriy Gapon References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> <20180320070745.GA12880@server.rulingia.com> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <2b3db2af-03c7-65ff-25e7-425cfd8815b6@FreeBSD.org> Date: Fri, 23 Mar 2018 16:21:32 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180320070745.GA12880@server.rulingia.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="peWEmISJWwMj6HfJfKeabFgfjpj5pPoKJ" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 23:21:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --peWEmISJWwMj6HfJfKeabFgfjpj5pPoKJ Content-Type: multipart/mixed; boundary="5GZut2mJLg1mrfnwTYoP0tu2JTHyJjIKx"; protected-headers="v1" From: Bryan Drewery To: Peter Jeremy , Jeff Roberson Cc: FreeBSD current , Andriy Gapon Message-ID: <2b3db2af-03c7-65ff-25e7-425cfd8815b6@FreeBSD.org> Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT References: <20180306173455.oacyqlbib4sbafqd@ler-imac.lerctr.org> <201803061816.w26IGaW5050053@pdx.rh.CN85.dnsmgr.net> <20180306193645.vv3ogqrhauivf2tr@ler-imac.lerctr.org> <20180306221554.uyshbzbboai62rdf@dx240.localdomain> <20180307103911.GA72239@kloomba> <20180311004737.3441dbf9@thor.intern.walstatt.dynvpn.de> <20180320070745.GA12880@server.rulingia.com> In-Reply-To: <20180320070745.GA12880@server.rulingia.com> --5GZut2mJLg1mrfnwTYoP0tu2JTHyJjIKx Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 3/20/2018 12:07 AM, Peter Jeremy wrote: >=20 > On 2018-Mar-11 10:43:58 -1000, Jeff Roberson = wrote: >> Also, if you could try going back to r328953 or r326346 and let me kno= w if=20 >> the problem exists in either. That would be very helpful. If anyone = is=20 >> willing to debug this with me contact me directly and I will send some= =20 >> test patches or debugging info after you have done the above steps. >=20 > I ran into this on 11-stable and tracked it to r326619 (MFC of r325851)= =2E > I initially got around the problem by reverting that commit but either > it or something very similar is still present in 11-stable r331053. >=20 > I've seen it in my main server (32GB RAM) but haven't managed to reprod= uce > it in smaller VBox guests - one difficulty I faced was artificially fil= ling > ARC. >=20 Looking at the ARC change you referred to from r325851 https://reviews.freebsd.org/D12163, I am convinced that ARC backpressure is completely broken. On my 78GB RAM system with ARC limited to 40GB and doing a poudriere build of all LLVM and GCC packages at once in tmpfs I can get swap up near 50GB and yet the ARC remains at 40GB through it all. It's always been slow to give up memory for package builds but it really seems broken right now. --=20 Regards, Bryan Drewery --5GZut2mJLg1mrfnwTYoP0tu2JTHyJjIKx-- --peWEmISJWwMj6HfJfKeabFgfjpj5pPoKJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJatYwAAAoJEDXXcbtuRpfPYtUIAJUKx7TLrDXkpSTY1l/FNHz7 CMgOFqck5sYz3x5M4vklwc3yCvCKofI2EPlHg4NEvkOzgYHDOdidaMrbZMDFC4L0 8vm5gWdXtPstMH+IP8QSENgBfh2nUAWxLKSFtKYLTBoQKCdig3HYc/Saf5rcfbrO t7f6Kesz/1B+beS/IWBicuWxuwAw86Ex+uIYE1b10O0/jwY3WOWM3THOT28rAixL 7c7kgXFXEzJw+7qYmuxguE7P0C0kwPd2zxDhaKNzIbyggTu+8QRpPhy5oVW3TDWP mmlvUfZAd9GRD41fv3ZtXMwURQV6fx5ApONwaf31EJi/mJVqHSPR3A5JdRWW76c= =VjMH -----END PGP SIGNATURE----- --peWEmISJWwMj6HfJfKeabFgfjpj5pPoKJ-- From owner-freebsd-current@freebsd.org Sat Mar 24 00:03:50 2018 Return-Path: Delivered-To: freebsd-current@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 A6C1EF58808 for ; Sat, 24 Mar 2018 00:03:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 150226C5C3; Sat, 24 Mar 2018 00:03:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w2O03ZNx017170 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 02:03:39 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w2O03ZNx017170 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w2O03ZAr017169; Sat, 24 Mar 2018 02:03:35 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 24 Mar 2018 02:03:35 +0200 From: Konstantin Belousov To: Mark Peek Cc: Peter Lei , freebsd-current@freebsd.org, huanghwh@163.com, "Jonathan T. Looney" Subject: Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts Message-ID: <20180324000335.GN76926@kib.kiev.ua> References: <8b8f1352-aa5c-716c-ef6c-3b3cd630043f@ieee.org> <20180316095627.GW76926@kib.kiev.ua> <20180323231902.GM76926@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 00:03:50 -0000 On Fri, Mar 23, 2018 at 04:44:36PM -0700, Mark Peek wrote: > On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov > wrote: > > > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > > patch causes a different panic: > > > > > > https://people.freebsd.org/~mp/r330539-patched.png > > > > > > Thoughts? > > > > r331290 should fixed this issue. What is your kernel sources version ? > > > > Thank you for the pointer to r331290. I missed it and thought your patch to > -current was the intended fix. It is, but there is more than one issue. The posted patch fixed code patching, committed as r331258 and r331253. Then there was the fix for sysinit sort in r331290. > > Updated my kernel to r331469 and it is booting on Fusion now. Ok. From owner-freebsd-current@freebsd.org Fri Mar 23 23:06:25 2018 Return-Path: Delivered-To: freebsd-current@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 604CBF53E23 for ; Fri, 23 Mar 2018 23:06:25 +0000 (UTC) (envelope-from mark@peek.org) Received: from mail-yb0-x244.google.com (mail-yb0-x244.google.com [IPv6:2607:f8b0:4002:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF38569FB2 for ; Fri, 23 Mar 2018 23:06:24 +0000 (UTC) (envelope-from mark@peek.org) Received: by mail-yb0-x244.google.com with SMTP id o197-v6so3315478ybg.5 for ; Fri, 23 Mar 2018 16:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peek-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kpMqnDcrFBRkrhtq8uLHDx2cZI61/5HE0eQCKBW8C3g=; b=mZ/OYyCNtq+q4eUS653L16UpCToHOzi5Y1gM8J4GM2RCBRWhquc4fu9YB6SjQGvWA/ twnjeiGMwQaUUuePU/EnP9xRgIohZF1Sc7PbaqhaAWUmKSbJ6LjJ2JK+hLStDECjPz/y g0lnWaqHUs01hSbjTiz+z+twZDsS9qe4ldBa0u1JSs/JnmeaYa0nwd61NDOOaa0BfDA4 WhUT6ekpGdFP7q5T4RYabD9u1Fc7Sped9mh2zPwZ88CNHoJqO3taKFxv+G3l30saFzEX Sv/wvpI9oirMpmXw6nfoNnCSyIrw95hQrlenNsUDN9gSlokpDhFqWbOdDD4iBu6WjFOV kadg== 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=kpMqnDcrFBRkrhtq8uLHDx2cZI61/5HE0eQCKBW8C3g=; b=aTgoiItPm9btTim//0crAf/r0st2s7/IFnWrjhX/rVrybaFiPjF/ZDlug9qhyhVrLW 0q/7OJwYoZYXsuL4ZSskQ1SUzTGN/900aQvk+zYlicbREd2rlQxzJQJrHfOyh3DWrWhy rP7niYAeSwwQR3t360qfPJrrZvIzDc8Py9JLoGnBg4PsMcSpXwZL8qeKqAtaWIhogImm iWzJyCDhNuELOBL9G+EppeCXazCK/vC0r7FDgInw4gdZm1ArY9aomn6IuPnk4QwJb/n/ TASexjm3JKoNz8wmIVkiJhT2Sew1Yoz7eKE4h6ngAqjNIQjY3XW4XKoE4gyD2phb/YID IJBg== X-Gm-Message-State: AElRT7EbUv2VGKcmlu7ffLVVraLmSR+GvJHSv10v4y7htXJQp/12zXDA UICwZhm+if5Fo0ij9EgK1g5snMG4PEXkL9jC5uDUyA== X-Google-Smtp-Source: AG47ELvFLesj28kHM1PNN4F8sojOLulyvxdCPZYWkibPZ8MU3x0LSxUVwRVK5vZ9C/e+Ll1Y/4Bm5P66ByCvMbgNXCU= X-Received: by 2002:a25:5e41:: with SMTP id s62-v6mr18190314ybb.115.1521846384084; Fri, 23 Mar 2018 16:06:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:1057:0:0:0:0:0 with HTTP; Fri, 23 Mar 2018 16:06:23 -0700 (PDT) X-Originating-IP: [2601:646:c700:35ed:b42e:d398:1bb6:3336] In-Reply-To: <20180316095627.GW76926@kib.kiev.ua> References: <8b8f1352-aa5c-716c-ef6c-3b3cd630043f@ieee.org> <20180316095627.GW76926@kib.kiev.ua> From: Mark Peek Date: Fri, 23 Mar 2018 16:06:23 -0700 Message-ID: Subject: Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts To: Konstantin Belousov Cc: Peter Lei , freebsd-current@freebsd.org, huanghwh@163.com, "Jonathan T. Looney" X-Mailman-Approved-At: Sat, 24 Mar 2018 00:35:57 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 23:06:25 -0000 On Fri, Mar 16, 2018 at 2:56 AM, Konstantin Belousov wrote: > On Thu, Mar 15, 2018 at 09:38:56PM -0500, Peter Lei wrote: > > Some recent UEFI implementations have begun to leave the CPU with page > > write protection enabled in CR0. > > > > With r330539 which enables kernel page protections, interesting things > > happen during boot (aka panic) when protection is already enabled, > > including a write protection fault from an explicit .text fixup write > > from xsave->xsaveopt by fpuinit(). > > > > I see this so far booting -CURRENT under virtual environments: > > > > - QEMU with recent OVMF EDK2 builds: this is certainly due to UEFI > > enabling paging and page protections. > > > > - VMWare Fusion 10.1.x on Mac: no specific insight on what's going > > inside the implementation, but CR0_WP is definitely left enabled before > > the kernel is booted. > > > > I have patched my kernel build to explicitly clear CR0_WP (e.g. in > > initializecpu) prior to creating the page tables to get around this, but > > someone might have a cleaner/better solution... > > Try this. > > diff --git a/sys/amd64/amd64/db_interface.c b/sys/amd64/amd64/db_ > interface.c > index 9dfd44cf82c..1ecec02835c 100644 > --- a/sys/amd64/amd64/db_interface.c > +++ b/sys/amd64/amd64/db_interface.c > I ran into the original issue with r330539 on a Fusion VM. Trying this patch causes a different panic: https://people.freebsd.org/~mp/r330539-patched.png Thoughts? Mark From owner-freebsd-current@freebsd.org Sat Mar 24 05:59:21 2018 Return-Path: Delivered-To: freebsd-current@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 80980F6F8CF for ; Sat, 24 Mar 2018 05:59:21 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0BA3E7AB58 for ; Sat, 24 Mar 2018 05:59:21 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id C3F39F6F8C4; Sat, 24 Mar 2018 05:59:20 +0000 (UTC) Delivered-To: current@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 7710AF6F8C3 for ; Sat, 24 Mar 2018 05:59:20 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta03p.bpe.bigpond.com (nsstlmta03p.bpe.bigpond.com [203.38.21.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 576407AB56 for ; Sat, 24 Mar 2018 05:59:18 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep33p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180324035659.LQXL1063.nsstlfep33p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com> for ; Sat, 24 Mar 2018 14:56:59 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtgedrvddvgdejiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvfftteenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtuggfsehmtderredtredvnecuhfhrohhmpeetnhgurhgvficutfgvihhllhihuceorghrvghilhhlhiessghighhpohhnugdrnhgvthdrrghuqeenucffohhmrghinheprggtqdhrrdhnuhenucfkphepuddvgedrudeltddrgedtrddukedvnecurfgrrhgrmhephhgvlhhopegkvghnrdgrtgdqrhdrnhhupdhinhgvthepuddvgedrudeltddrgedtrddukedvpdhmrghilhhfrhhomhepoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgruheqnecu X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from Zen.ac-r.nu (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A614436175617AC for current@freebsd.org; Sat, 24 Mar 2018 14:56:59 +1100 Date: Sat, 24 Mar 2018 14:56:53 +1100 From: Andrew Reilly To: current@freebsd.org Subject: 12-Current panics on boot (didn't a week ago.) Message-ID: <20180324035653.GA3411@Zen.ac-r.nu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 05:59:21 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, For reasons that still escape me, I haven't been able to get a kernel dump to debug, sorry. Just thought that I'd generate a fairly low-quality report, to see if anyone has some ideas. The last kernel that I have that booted OK (and I'm now running) is: FreeBSD Zen.ac-r.nu 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r331064M: Sat Mar 17 07:54:51 AEDT 2018 root@Zen:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 The machine is a: CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Features=0x178bfbff Kernels built from head as of a couple of hours ago get through launching the other CPUs and then stops somewhere in random, apparently: SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 1497223020 Hz quality 1000 random: entpanic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/subr_bus.c:617 cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00004507a0 vpanic() at vpanic+0x18d/frame 0xfffffe0000450800 doadump () at doadump/frame 0xfffffe0000450880 __mtx_lock_flags() at __mtx_lock_flags+0x163/frame 0xfffffe00004508d0 devctl_queue_data_f() at devctl_queue_data_f+0x6a/frame 0xfffffe0000450900 g_dev_taste() at g_dev_taste+0x370/frame 0xfffffe0000450a10 g_new_provider_event() at g_new_provider_event+0xfa/frame 0xfffffe0000450a30 g_run_events() at g_run_events+0x151/frame 0xfffffe0000450a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000450ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000450ab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 14 tid 100052 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> dump Cannot dump: no dump device specified. db> Now dumping worked fine the last time the kernel panicked: I have dumpdev=AUTO in rc.conf and I have swap on nvd0p3 (first) and /dev/zvol/root/swap (second, larger than the first.) Root on the nvd0p2 is ZFS, and ther's a four-drive raidZ with user directories and what-not on them, and another ZFS on an external USB drive that I use for backups, unmounted. In the new kernels, we clearly aren't even getting as far as finding the hubs and controllers, let alone the drives. I've attached dmesg.boot from the last boot from last week's good kernel. (While briefly in yoyo mode I turned the SMT back on, so now there are 16 cores instead of the eight mentioned in the crash dump. Didn't help, but I haven't turned it back off yet.) Cheers, Andrew --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #1 r331064M: Sat Mar 17 07:54:51 AEDT 2018 root@Zen:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x7 SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33272578048 (31731 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs FreeBSD/SMP: 1 package(s) x 2 cache groups x 4 core(s) x 2 hardware threads random: unblocking device. Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180313/tbfadt-796) ioapic0: Changing APIC ID to 17 ioapic1: Changing APIC ID to 18 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard SMP: AP CPU #12 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #11 Launched! Timecounter "TSC-low" frequency 1497228045 Hz quality 1000 random: entropy device external interface [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0xffffffff8101f5c0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 vtvga0: on motherboard cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 cpu8: on acpi0 cpu9: on acpi0 cpu10: on acpi0 cpu11: on acpi0 cpu12: on acpi0 cpu13: on acpi0 cpu14: on acpi0 cpu15: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 350 Event timer "HPET1" frequency 14318180 Hz quality 350 Event timer "HPET2" frequency 14318180 Hz quality 350 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 amdsmn0: on hostb0 amdtemp0: on hostb0 pci0: at device 0.2 (no driver attached) pcib1: at device 1.1 on pci0 pci1: on pcib1 nvme0: mem 0xfe900000-0xfe903fff irq 24 at device 0.0 on pci1 pcib2: at device 1.3 on pci0 pci2: on pcib2 xhci0: mem 0xfe6a0000-0xfe6a7fff irq 32 at device 0.0 on pci2 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ahci0: mem 0xfe680000-0xfe69ffff irq 33 at device 0.1 on pci2 ahci0: AHCI v1.31 with 8 6Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 pcib3: irq 34 at device 0.2 on pci2 pci3: on pcib3 pcib4: irq 32 at device 0.0 on pci3 pci4: on pcib4 pcib5: irq 33 at device 1.0 on pci3 pci5: on pcib5 pcib6: irq 32 at device 4.0 on pci3 pci6: on pcib6 pcib7: irq 33 at device 5.0 on pci3 pci7: on pcib7 pcib8: irq 34 at device 6.0 on pci3 pci8: on pcib8 pci8: at device 0.0 (no driver attached) pcib9: irq 35 at device 7.0 on pci3 pci9: on pcib9 igb0: port 0xf000-0xf01f mem 0xfe400000-0xfe41ffff,0xfe420000-0xfe423fff irq 32 at device 0.0 on pci9 igb0: attach_pre capping queues at 2 igb0: using 1024 tx descriptors and 1024 rx descriptors igb0: msix_init qsets capped at 2 igb0: pxm cpus: 8 queue msgs: 4 admincnt: 1 igb0: using 2 rx queues 2 tx queues igb0: Using MSIX interrupts with 3 vectors igb0: allocated for 2 tx_queues igb0: allocated for 2 rx_queues igb0: Ethernet address: 70:85:c2:59:38:4e igb0: netmap queues/slots: TX 2/1024, RX 2/1024 pcib10: at device 3.1 on pci0 pci10: on pcib10 vgapci0: port 0xe000-0xe0ff mem 0xe0000000-0xefffffff,0xfe800000-0xfe83ffff irq 54 at device 0.0 on pci10 vgapci0: Boot video device hdac0: mem 0xfe860000-0xfe863fff irq 55 at device 0.1 on pci10 hdac0: hdac_get_capabilities: Invalid corb size (0) device_attach: hdac0 attach returned 6 pcib11: at device 7.1 on pci0 pci11: on pcib11 pci11: at device 0.0 (no driver attached) ccp0: mem 0xfe200000-0xfe2fffff,0xfe300000-0xfe301fff irq 36 at device 0.2 on pci11 random: registering fast source AMD CCP TRNG xhci1: mem 0xfe100000-0xfe1fffff irq 37 at device 0.3 on pci11 xhci1: 64 bytes context size, 64-bit DMA usbus1 on xhci1 usbus1: 5.0Gbps Super Speed USB v3.0 pcib12: at device 8.1 on pci0 pci12: on pcib12 pci12: at device 0.0 (no driver attached) ahci1: mem 0xfe708000-0xfe708fff irq 42 at device 0.2 on pci12 ahci1: AHCI v1.31 with 1 6Gbps ports, Port Multiplier supported with FBS ahcich8: at channel 0 on ahci1 hdac0: mem 0xfe700000-0xfe707fff irq 43 at device 0.3 on pci12 isab0: at device 20.3 on pci0 isa0: on isab0 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0 hwpstate0: on cpu0 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec ugen0.1: <0x1022 XHCI root HUB> at usbus0 ugen1.1: <0x1022 XHCI root HUB> at usbus1 uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 nvd0: NVMe namespace nvd0: 228936MB (468862128 512 byte sectors) hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 20,22,21 and 24,26 on hdaa0 pcm1: at nid 27 and 25 on hdaa0 pcm2: at nid 30 on hdaa0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA8-ACS SATA 3.x device ada0: Serial Number PK1334PEHWZT7S ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 3815447MB (7814037168 512 byte sectors) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA8-ACS SATA 3.x device ada1: Serial Number PK1334PEHZBWXS ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 3815447MB (7814037168 512 byte sectors) ada2 at ahcich4 bus 0 scbus2 target 0 lun 0 ada2: ATA8-ACS SATA 3.x device ada2: Serial Number PK1334PEHYSZ6S ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 3815447MB (7814037168 512 byte sectors) ada3 at ahcich5 bus 0 scbus3 target 0 lun 0 ada3: ATA8-ACS SATA 3.x device ada3: Serial Number PK1334PEHZDA1S ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 3815447MB (7814037168 512 byte sectors) WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from zfs:root [rw]... Root mount waiting for: usbus1 usbus0 uhub1: 8 ports with 8 removable, self powered uhub0: 22 ports with 22 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 ubt0 on uhub0 ubt0: on usbus0 ugen1.2: at usbus1 umass0 on uhub1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:5:0: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 1153000117AD da0: 400.000MB/s transfers da0: 5723166MB (1465130646 4096 byte sectors) da0: quirks=0x2 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Link state changed to up igb0: link state changed to UP --sm4nu43k4a2Rpi4c-- From owner-freebsd-current@freebsd.org Sat Mar 24 09:36:30 2018 Return-Path: Delivered-To: freebsd-current@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 532C7F5A628 for ; Sat, 24 Mar 2018 09:36:30 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A839582FA0 for ; Sat, 24 Mar 2018 09:36:29 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.178.113.82]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LmeGF-1eQL2s3PsZ-00aB5e for ; Sat, 24 Mar 2018 10:36:21 +0100 Date: Sat, 24 Mar 2018 10:35:48 +0100 From: "O. Hartmann" To: FreeBSD CURRENT Subject: g_handleattr: md0 bio_length 24 len 31 -> EFAULT Message-ID: <20180324103615.7b88c33f@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Zk_qe+0i5ZWx3e98P.Vz4CJ"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:v8JhJsID8PM2u1vTWqwkmJGF2I+ObvOiPVb5L+t08H7sma0Us+z S7Yig3UHrtK3H+4aoXGUP/nGV6UpoZVV9GaFAHUSvkUG7zGzJnNEmZ793aoVHuav/t3PZ3s PGONOQI3waVQsgl1IJHQ+Qqi8ic1J6ieS00omhn1YLjLG2bvdRWlPeppjSI6om2VZsl7X/o GmBhJnip/Neey2nuWc4iA== X-UI-Out-Filterresults: notjunk:1;V01:K0:3dGcm7OE+J0=:/9+LwFzCmqBZ2gWBmaWClV zgPDIUYf9prQn3A0zsSpJuyVGrgQA2yL93egF5ie8/1RcHbbOxFELq9botSbNY/A7tirJ14dT o9Rf+vqoGcosHW1ZfjeBuX4lgp7G1W6zESxlk9HOpdCPaGI6LSyjRVjbQtiBR4/lIvX7Trf2W T7XsejRGz6bVciHXThOa9D1jnWuF+1zj3uCAYXCQJd5/ibQRM+dKdGaIf/yUPJ4pU8Jk6+vog PdWLjQ3/WKSievQJ2omp5YTelUw9SLKMo1Kmn5mabqntWKeAq7eGgR61pDBAsqDXBDEGIy0iM jxIJKSXlQ7p9jvzKctjyxnedDW5jITPThvnEbFYphqyxmMatnzqM9Vp01gDPQMIobfwCgBSu0 gkZzPcuFQoMQ9GB/AcGwzgB7wgjYanisp+S7F0RcIdvHiRUa8wvVsuSNLRwZZiKnkqI1LvZjA PYZB8ncHJu0UD43ZG4lc+wdsg4RPAWGmU4Y0O2ruIcdt2ZwcbtePgg/a0xg7sceNjMjMJA6rL W62n9n7t1szSXVj4XfixfglcB8e3W7vLHRm1qDMBhd65dnUshRktaw050rV0DAQEtrsErNFx7 zJF8HZ4sdpo00UBD1LVYL0jtBITlnGxOv8dfWs45Nw2SdvN+6FGGVY826DX1Lougq44lMSqNP s3nNU91bkVSjBL/anfMgmTUeWlcFY/cHFk+uCOGJ2/lZwz0pGLPbMKfYm+k+HbwnZEA10j6rw qz+pYMJ1L2npbgEhaRRmA3769e3o2XzRzP/FCudXz+NEdRYvIBjj21VgSuxuEGkURYywaGP7+ ZFqGBQekb/3hrkdkLexRuoK9LI6lw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 09:36:30 -0000 --Sig_/Zk_qe+0i5ZWx3e98P.Vz4CJ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Writing out memory (md) backed images of UFS2 filesystems (NanoBSD images, = created via the classical manual way, no makefs), my recent CURRENT system dumps the console full of these error messages: g_handleattr: md0 bio_length 24 len 31 -> EFAULT I do not know what they are supposed to mean and I'd like to ask whether so= meone could shed some light on this. Thanks, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/Zk_qe+0i5ZWx3e98P.Vz4CJ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWrYcDwAKCRDS528fyFhY lPqgAgChhDSlabMLFjtLZEUSESoO73LDlR/r0s3TT/uo/ICvbCxvS3BWoPAfMqcz VaaDePFFSz5pjks0VAATdr3WWw4lAf43ruPwrytrRdhlGDNOZMnSOm/ycbCvfaZJ Ppx1KohDix8jJo3lGmrqfTcjX9zUKjnl33l2CmVJvXdHC+dSMyVo =BiP+ -----END PGP SIGNATURE----- --Sig_/Zk_qe+0i5ZWx3e98P.Vz4CJ-- From owner-freebsd-current@freebsd.org Fri Mar 23 23:44:38 2018 Return-Path: Delivered-To: freebsd-current@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 1C603F56DC5 for ; Fri, 23 Mar 2018 23:44:38 +0000 (UTC) (envelope-from mark@peek.org) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB3326B8B4 for ; Fri, 23 Mar 2018 23:44:37 +0000 (UTC) (envelope-from mark@peek.org) Received: by mail-yw0-x232.google.com with SMTP id y23so4505136ywy.4 for ; Fri, 23 Mar 2018 16:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peek-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9yvYlQhSowqunfwbsmkZz86GpDdfqMp+2BfqbTFRDZ8=; b=ZQn4bM7i16FixN8rsXLlrUKJpvdhP5FUZyID4ocScXDiBoQ7zDjYHgWvgLV9gqVIT2 W2hwZwmdKvUCRvqE36dZuRXIILMoAGuJZIuRBzMShWtH26XBzAj4mi+dysrCVXYKyzT+ lTPlBJNr+wH376u3FP2uriA5KUV2RhcnKI3ogm8gQ+zrvFCeNpJntl8MGMTjGaasLOBO RQKHhe6KDoW2/94Zvkbqv7P2UGJFnnMVf3LTJF2p6kUEu6Po/aOijuhzYDh650n81Vkw K33p65bHHqCNwqh//+YdFFB8xngahKI8VurVf55lQcRnf6TXghjze/v81VeKS99NwMPZ XLng== 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=9yvYlQhSowqunfwbsmkZz86GpDdfqMp+2BfqbTFRDZ8=; b=OS6HRsplmdCzvDvyyRh1IckpqLX/OENQyb3CQcczylbC9AJ6h6pLKUMVCWYbmA4n7d uqMKyVT/k9EUe+a3HIiY0PVqFr/70nRdFZnI9PEr1Es2HdPKeaC9uQ5imSmgbbUb4Q3E j/PN0HCgGIguMc3ZLJ5/r2IVMWhv0spmbaTakXp1vljVLISID8m/SRpXjLeWQULII+co 0KoiK+ks+xMZVpV+oQgmIVOh0qLWkdkZvB8YeUg0J80bLXKAQ5RIvsiQabCNTBogDeaG 56Yfs0CMkK/P1FAzU86Y0zI0CshRm24zEl6aJV1R3srExK9hbj0a4Z7io7mHvLTZEIvr woEQ== X-Gm-Message-State: AElRT7E2b6UMOe8S+1pNxMJhfDIgvei4phu1oPH/JCFVrU2/+QaPYmyI SMZMTFPr/8wEWarQ6JaJ87BVGBYF/vRLp38yno1cIA== X-Google-Smtp-Source: AG47ELuv3O6mP1RH8iYpqCnjeo89c1KV8DlZcOe8HNgXFcgBkQGooH5Kn5CEycwRiYeLoiO6xeIOrTbSCU9D3fXmUa4= X-Received: by 10.13.196.131 with SMTP id g125mr17980902ywd.442.1521848676860; Fri, 23 Mar 2018 16:44:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:1057:0:0:0:0:0 with HTTP; Fri, 23 Mar 2018 16:44:36 -0700 (PDT) X-Originating-IP: [2601:646:c700:35ed:b42e:d398:1bb6:3336] In-Reply-To: <20180323231902.GM76926@kib.kiev.ua> References: <8b8f1352-aa5c-716c-ef6c-3b3cd630043f@ieee.org> <20180316095627.GW76926@kib.kiev.ua> <20180323231902.GM76926@kib.kiev.ua> From: Mark Peek Date: Fri, 23 Mar 2018 16:44:36 -0700 Message-ID: Subject: Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts To: Konstantin Belousov Cc: Peter Lei , freebsd-current@freebsd.org, huanghwh@163.com, "Jonathan T. Looney" X-Mailman-Approved-At: Sat, 24 Mar 2018 10:28:04 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 23:44:38 -0000 On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov wrote: > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > patch causes a different panic: > > > > https://people.freebsd.org/~mp/r330539-patched.png > > > > Thoughts? > > r331290 should fixed this issue. What is your kernel sources version ? > Thank you for the pointer to r331290. I missed it and thought your patch to -current was the intended fix. Updated my kernel to r331469 and it is booting on Fusion now. Thanks! Mark From owner-freebsd-current@freebsd.org Sat Mar 24 13:09:41 2018 Return-Path: Delivered-To: freebsd-current@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 8564DF6C3B6 for ; Sat, 24 Mar 2018 13:09:41 +0000 (UTC) (envelope-from james.wright@jigsawdezign.com) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA7176AFEF for ; Sat, 24 Mar 2018 13:09:40 +0000 (UTC) (envelope-from james.wright@jigsawdezign.com) Received: from [192.168.0.15] ([82.18.193.38]) by mrelayeu.kundenserver.de (mreue003 [212.227.15.163]) with ESMTPSA (Nemesis) id 0MTtH3-1f8lO10EHB-00QlrQ for ; Sat, 24 Mar 2018 14:04:28 +0100 To: freebsd-current@freebsd.org From: James Wright Subject: installkernel error WITHOUT_BLUETOOTH Message-ID: Date: Sat, 24 Mar 2018 13:04:28 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Provags-ID: V03:K0:VmaEEr7tTYUd6mlOGs1JwHv6sRJjYtW6ck4xTiK/56T+vCc4GBA A/EQWIgEIohiXFoG8L0gV/NwMBZd6GJSevpQF9WsQYB09mPSI02fLYJjOJNrqdxF6Lh3pt7 ZOwobpCdRy8/k8AIBq9gtNC34UV0oWODSxFTpM8rivGTsQe58/RdCtFllrLzkonGVkJPa2Y ey3FmS5rCqtECa2tbhIjQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:igFhL6YGRqk=:K+X1sL6eeaf7eFOOXmu/Fz Sf+ThpOrtNxPRKFMnLBeueHby7ndKF1wVsDBB8WQ0rndrQ6WwYMP5wZqE4Uj8q70kv8n2Dxvn XtZVwXjckuFTRBEx1sgfeI5meKR3OxHbspj+nOL+sNzIqX9ozYZGnyMlXpqAJFOa4CPOrKvGt wgC9L+eam9GPhuEfWIXERMGB92LektUGGQN6GbtHK7I9GaxRjgG5PecUOZCn/ECwVx+lZzRod Pac2w9i4OGy364C95GVpr2WToN3piJZA5DNZFssc0RizfMRWVv5rYKQ+pJK9u7gxGGXxDYJbB zHD5OX2EiG/gqCTkypk11kSGqEPyfEi9QGSfG5oeduOnQff73iT89Kc+Upmsf2dyQXiMH41lO XrGSD39YdYDat3BMYM916dUbKsK6okNCQEP0EgcMPkMqPcHObDHDN/dsOoGXrWMhcpoBVgn7P sY1Q/fDdK9Ubf1scM68yMMdOJX/05fKH+tpq5Qe8EObaYueco7cMF053pROihb8YJPTc+PgZu tODcJsiviioB23Qnjt8raW5jVwFgzLjQlt8NEIFlrp3kOXiACSXtlyJjuJTONXLc5i5qAh+rE HbIQvsNUP1CV63ABOjUrYpt0wyq94gQNq9M31uLbngQ5FdNpM2RpPP7nsKA4h+5K2wqXZR+cT VVyBWjEqLvYamsREs6qXN9Mh0n2Q35JOzHYbN/fb/U83L0rKIxBLyldxiaozUMKHbwAFli+/f npAiyosO/w8RliaEa1ctiIIcz4cZDVdRqz2hVcasJAG88IjiOUw/1gRyHdI= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 13:09:41 -0000 Hi,    Just ran into this issue when trying to "make installkernel" after adding the "WITHOUT_BLUETOOTH" flag to my "/etc/src.conf" (see snippet below). Is this expected behaviour? Do I need to add "WITHOUT_NETGRAPH" also? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> install -T release -o root -g wheel -m 555   ng_atmllc.ko /boot/kernel/ install -T debug -o root -g wheel -m 555   ng_atmllc.ko.debug /usr/lib/debug/boot/kernel/ ===> netgraph/bluetooth (install) ===> netgraph/bluetooth/bluetooth (install) install -T release -o root -g wheel -m 555   ng_bluetooth.ko /boot/kernel/ install: ng_bluetooth.ko: No such file or directory *** Error code 71 Stop. make[6]: stopped in /usr/src/sys/modules/netgraph/bluetooth/bluetooth *** Error code 1 Stop. make[5]: stopped in /usr/src/sys/modules/netgraph/bluetooth *** Error code 1 Stop. make[4]: stopped in /usr/src/sys/modules/netgraph *** Error code 1 Stop. make[3]: stopped in /usr/src/sys/modules *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Thanks, James From owner-freebsd-current@freebsd.org Sat Mar 24 14:11:16 2018 Return-Path: Delivered-To: freebsd-current@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 CB2A9F4C6A5 for ; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7E96DEA7 for ; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1716EF4C6A4; Sat, 24 Mar 2018 14:11:16 +0000 (UTC) Delivered-To: current@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 E74CBF4C6A1 for ; Sat, 24 Mar 2018 14:11:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 855196DEA2 for ; Sat, 24 Mar 2018 14:11:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x244.google.com with SMTP id r18so18325388ioa.1 for ; Sat, 24 Mar 2018 07:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r3l+MLFkpDQGUJ1dpCGInJjOIn4k1Wj6OMFVOuStju4=; b=kZ5ZVHfUEcGOsM674xmp9+YJsTLTKqtYKPxGu6RqOY7MugkGNmqbPv3iCMYUr8faXy 0UDHqmCvFCXndiYsg/SUqmKrNm5zLyTMHuYmRwI7FbzrgCE9MhgshjDPLj0fhrIDHUye uI79Z5qjPv2Trx+bUAj2K/pXVlbszc68UgoQH6P54MPXSg9tIpnq4Fsuis3Mu/PVCrJc iu3L+iCTaKSRniDo3DfQhVtGAUkJj6ZkPohiSTTpxN0trNVDdDutl4nXxwWlee4ERJN0 u52H48aVUvxpTnjMfkAf+DWF4iWsENX2ct/prMIEeuzAsiP+XLe224YHLJa8BoZOl7FJ IdVQ== 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=r3l+MLFkpDQGUJ1dpCGInJjOIn4k1Wj6OMFVOuStju4=; b=NyK4Ie8RFhF0Rf9z8U1q68BhX5ayXPQNxAP9xUBNMNDhtgnk/1ESOE3OB6CI/+gQoH MbrVn3FZbgpIZ7gC52lzlC+JPKVaYVc01qHaU68LlzCCkyZD80x4u2yaMdCEMnNkAZ97 FpSEDeyv3v6q/ALaoo9bjMyO1VglcjAWVbJyM/Qpz0p/zG2mPYXTAuRf13FGf2mBzPG3 KC7jPrMBABptQixqMwO1MqPBWL45ZcBme+cl8HBFUaL1TyAKF+EKLj72r9dukrkkuZFC ttvRTqwR7H+8zOOmtzqrinsZVTpRl9YmmVv2zVmib+CWCc72LoKKKKJuptWdQQ2Kttip ZnEw== X-Gm-Message-State: AElRT7ET8UloTUFejGAcw9TpR029vnYQmlgbX2vV8qOVOo5x3kjyHdBh SO5Df/lCAAaGugsLaJn5Hz2faYtpPazjA1JT9LFmqw== X-Google-Smtp-Source: AG47ELtOOpnClnfp+DNPBOj5fgdXYQs/0y9ynbKhl1MgfVhuwD7vxl5GNbszFfNVe3dUwiea7DPYb6uvbGmMZANs8ag= X-Received: by 10.107.144.11 with SMTP id s11mr34165866iod.37.1521900674658; Sat, 24 Mar 2018 07:11:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sat, 24 Mar 2018 07:11:13 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180324035653.GA3411@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> From: Warner Losh Date: Sat, 24 Mar 2018 08:11:13 -0600 X-Google-Sender-Auth: -tuyySFsQ25ud7xCpEVX1ZTR__M Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 14:11:17 -0000 That lock has been there for a long, long time (like 5 or 6 major releases)... It's surprising that it's causing issues now. Can you bisect versions to find when this starts happening? Warner On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly wrote: > Hi all, > > For reasons that still escape me, I haven't been able to get a kernel dump > to debug, sorry. > > Just thought that I'd generate a fairly low-quality report, to see if > anyone has some ideas. > > The last kernel that I have that booted OK (and I'm now running) is: > FreeBSD Zen.ac-r.nu 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r331064M: Sat > Mar 17 07:54:51 AEDT 2018 root@Zen:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > The machine is a: > CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class > CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > Features=0x178bfbff APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > Kernels built from head as of a couple of hours ago get through launching > the other CPUs and then stops somewhere in random, apparently: > > SMP: AP CPU #2 Launched! > Timecounter "TSC-low" frequency 1497223020 Hz quality 1000 > random: entpanic: mtx_lock() of spin mutex (null) @ > /usr/src/sys/kern/subr_bus.c:617 > cpuid = 0 > time = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00004507a0 > vpanic() at vpanic+0x18d/frame 0xfffffe0000450800 > doadump () at doadump/frame 0xfffffe0000450880 > __mtx_lock_flags() at __mtx_lock_flags+0x163/frame 0xfffffe00004508d0 > devctl_queue_data_f() at devctl_queue_data_f+0x6a/frame 0xfffffe0000450900 > g_dev_taste() at g_dev_taste+0x370/frame 0xfffffe0000450a10 > g_new_provider_event() at g_new_provider_event+0xfa/frame > 0xfffffe0000450a30 > g_run_events() at g_run_events+0x151/frame 0xfffffe0000450a70 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000450ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000450ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 14 tid 100052 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> dump > Cannot dump: no dump device specified. > db> > > Now dumping worked fine the last time the kernel panicked: I have > dumpdev=AUTO in rc.conf and I have swap on nvd0p3 (first) and > /dev/zvol/root/swap > (second, larger than the first.) > > Root on the nvd0p2 is ZFS, and ther's a four-drive raidZ with user > directories and what-not on them, and another ZFS on an external USB drive > that I use > for backups, unmounted. > > In the new kernels, we clearly aren't even getting as far as finding the > hubs and controllers, let alone the drives. > > I've attached dmesg.boot from the last boot from last week's good kernel. > (While briefly in yoyo mode I turned the SMT back on, so now there are 16 > cores > instead of the eight mentioned in the crash dump. Didn't help, but I > haven't turned it back off yet.) > > Cheers, > > Andrew > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Sat Mar 24 14:14:43 2018 Return-Path: Delivered-To: freebsd-current@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 2A4B2F4CF94 for ; Sat, 24 Mar 2018 14:14:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B05966E33A for ; Sat, 24 Mar 2018 14:14:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6F7CCF4CF8D; Sat, 24 Mar 2018 14:14:42 +0000 (UTC) Delivered-To: current@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 4AFD3F4CF8C for ; Sat, 24 Mar 2018 14:14:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D28406E339 for ; Sat, 24 Mar 2018 14:14:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x243.google.com with SMTP id b20so18352544iof.5 for ; Sat, 24 Mar 2018 07:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Bz2h61k7tuDSdkOc1VKbS602GqCOBj+oc769xKJuyk4=; b=XYId9j2hZozF4IgKi+mvq8XzZTWPRU8LTyQL7CoNVoOsam5rTHV9DNgX9SniH85yBI OseFmuqRzWWE/ZYGajZ7IibEqbZH5i46QxEtAGJa+ODlw56OcDDBV8NMWJQ1Dyc0HuWl 2qWzLsJ4Ep3ncOdkGz/RVOQIrioeZMrt15U+x8hyOV1kyRXFd021GKyXBY5+GpwGcS2S awdgOhW7ZLQIdJRfiysbhYQcNfDfEj5Vlh40QFDxbiWcc/Yq8JdZt40eg4WqiXxjKoc1 efyxobtnKe44D8xtVUVnOdPXYYnk5uRfzBxbbLykgUYKaYUm8gPM31/aphvSzZnKxeba PNoA== 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=Bz2h61k7tuDSdkOc1VKbS602GqCOBj+oc769xKJuyk4=; b=W6o3uD27kdBl9082DN1o2VQZrskC4xZl/Xg13Vlmk5EGaEK/3zJUX41fnaW0zIdi1H BQmnbdMaMVED98tXGbdw6Fqj9BjvtyUC3YYJsL5i92efW4zp0fnNj10xPwBnVZHWj3bj dwwaa7gPWaq55LXBimsijDdudSjQexW3KhiCJrm6jT/tmi9dJAduBKuFPMK1z70SXaOS NH+jhT5Ll1nHO1eO5FizMK7r9AKMwwsiq90etFUtsXrSWFeJjJnvQ5axBPtsQAx5LB9X vkVJoKvfF04Q/FoDdrBWIh+y86BfHms6ycfU8BSB1ioXXvnD8WI3HiEaTNkaA7KS699l 9U3A== X-Gm-Message-State: AElRT7EoW5THdj5Uzc0/SzvHqZ+uBXy7a//4Sn5oOdm1aBVEPgj0jBfF gjHdVVdCDRz1QCB3b30F4ZS28iZyARIJ0z6vn738pI9T X-Google-Smtp-Source: AG47ELtmOlD7FUol4fdmPD3TiVNOykfyHVwi9deWEM7qSo3JHNwWDaCKxzea6Pn8HzckxCx7dyYJqPrkYbiTUFGaGRo= X-Received: by 10.107.162.146 with SMTP id l140mr29248166ioe.39.1521900881129; Sat, 24 Mar 2018 07:14:41 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sat, 24 Mar 2018 07:14:40 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180324035653.GA3411@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> From: Warner Losh Date: Sat, 24 Mar 2018 08:14:40 -0600 X-Google-Sender-Auth: FqisToBzv3gYCMmyr49-8JPJGHA Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 14:14:43 -0000 Also, what rev failed? I booted r331464 last night w/o issue. Warner On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly wrote: > Hi all, > > For reasons that still escape me, I haven't been able to get a kernel dump > to debug, sorry. > > Just thought that I'd generate a fairly low-quality report, to see if > anyone has some ideas. > > The last kernel that I have that booted OK (and I'm now running) is: > FreeBSD Zen.ac-r.nu 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r331064M: Sat > Mar 17 07:54:51 AEDT 2018 root@Zen:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > The machine is a: > CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class > CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > Features=0x178bfbff APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > Kernels built from head as of a couple of hours ago get through launching > the other CPUs and then stops somewhere in random, apparently: > > SMP: AP CPU #2 Launched! > Timecounter "TSC-low" frequency 1497223020 Hz quality 1000 > random: entpanic: mtx_lock() of spin mutex (null) @ > /usr/src/sys/kern/subr_bus.c:617 > cpuid = 0 > time = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00004507a0 > vpanic() at vpanic+0x18d/frame 0xfffffe0000450800 > doadump () at doadump/frame 0xfffffe0000450880 > __mtx_lock_flags() at __mtx_lock_flags+0x163/frame 0xfffffe00004508d0 > devctl_queue_data_f() at devctl_queue_data_f+0x6a/frame 0xfffffe0000450900 > g_dev_taste() at g_dev_taste+0x370/frame 0xfffffe0000450a10 > g_new_provider_event() at g_new_provider_event+0xfa/frame > 0xfffffe0000450a30 > g_run_events() at g_run_events+0x151/frame 0xfffffe0000450a70 > fork_exit() at fork_exit+0x84/frame 0xfffffe0000450ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000450ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 14 tid 100052 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> dump > Cannot dump: no dump device specified. > db> > > Now dumping worked fine the last time the kernel panicked: I have > dumpdev=AUTO in rc.conf and I have swap on nvd0p3 (first) and > /dev/zvol/root/swap > (second, larger than the first.) > > Root on the nvd0p2 is ZFS, and ther's a four-drive raidZ with user > directories and what-not on them, and another ZFS on an external USB drive > that I use > for backups, unmounted. > > In the new kernels, we clearly aren't even getting as far as finding the > hubs and controllers, let alone the drives. > > I've attached dmesg.boot from the last boot from last week's good kernel. > (While briefly in yoyo mode I turned the SMT back on, so now there are 16 > cores > instead of the eight mentioned in the crash dump. Didn't help, but I > haven't turned it back off yet.) > > Cheers, > > Andrew > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Sat Mar 24 14:27:01 2018 Return-Path: Delivered-To: freebsd-current@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 8B6B7F4E52E for ; Sat, 24 Mar 2018 14:27:01 +0000 (UTC) (envelope-from derek@chezmarcotte.ca) Received: from pmta31.teksavvy.com (pmta31.teksavvy.com [76.10.157.38]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "*.teksavvy.com", Issuer "DigiCert SHA2 High Assurance Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DC2E6EDDE for ; Sat, 24 Mar 2018 14:27:00 +0000 (UTC) (envelope-from derek@chezmarcotte.ca) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2HMCQDRX7Za/0StpUVdGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBZG2EBIhfjC8BgUopMQFflFcLhQUCg28iOBQBAgEBAQEBAQI?= =?us-ascii?q?DaCiFJwEFIxUeMwsYAgImAgI5HhMIAQGFCql3giCEWINoghoTdYQng21BgS6CZ?= =?us-ascii?q?YU/gjWCVAOXPwiCL4t8gSgOgRKCRYIqD4R5hyaIRAyBJTMigVJNOIJ+kGojkDU?= =?us-ascii?q?BAQ?= X-IPAS-Result: =?us-ascii?q?A2HMCQDRX7Za/0StpUVdGQEBAQEBAQEBAQEBAQcBAQEBAYN?= =?us-ascii?q?BZG2EBIhfjC8BgUopMQFflFcLhQUCg28iOBQBAgEBAQEBAQIDaCiFJwEFIxUeM?= =?us-ascii?q?wsYAgImAgI5HhMIAQGFCql3giCEWINoghoTdYQng21BgS6CZYU/gjWCVAOXPwi?= =?us-ascii?q?CL4t8gSgOgRKCRYIqD4R5hyaIRAyBJTMigVJNOIJ+kGojkDUBAQ?= X-IronPort-AV: E=Sophos;i="5.48,355,1517893200"; d="scan'208";a="25115373" Received: from 69-165-173-68.dsl.teksavvy.com (HELO mail.razorfever.net) ([69.165.173.68]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Mar 2018 10:26:54 -0400 Received: from [127.0.0.1] (mail.razorfever.net [192.168.0.4]) by mail.razorfever.net (8.15.2/8.14.9) with ESMTP id w2OEQr5S052055 for ; Sat, 24 Mar 2018 10:26:53 -0400 (EDT) (envelope-from derek@chezmarcotte.ca) X-Authentication-Warning: mail.razorfever.net: Host mail.razorfever.net [192.168.0.4] claimed to be [127.0.0.1] Subject: Re: freebsd-update: to a specific patch level - help please? [PATCH] To: freebsd-current@freebsd.org References: <20180323104437.GB21001@home.opsec.eu> From: Derek Message-ID: <8b80e639-b5a5-111e-aaf3-07952b2d57d1@chezmarcotte.ca> Date: Sat, 24 Mar 2018 10:26:53 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180323104437.GB21001@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.razorfever.net X-Mailman-Approved-At: Sat, 24 Mar 2018 14:47:43 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 14:27:01 -0000 On 18-03-23 06:44 AM, Kurt Jaeger wrote: > Hi! > >> To be clear, *I've included a link to a patch to freebsd-update >> in my initial post, and the help I'm looking for: is to get this >> functionality added as a feature so others can benefit.* It >> works for me already, and I've already benefited. >> >> (I'm happy to flesh it out, and document it properly, but I'm >> very hesitant to spend the time doing it in detail and submitting >> a PR if I'm doing this in isolation, and nobody wants it. > > Please submit this in a PR, and post the PR number here, I'll work to > get this in the tree. > PR is 226893 Thanks! Derek From owner-freebsd-current@freebsd.org Sat Mar 24 17:39:17 2018 Return-Path: Delivered-To: freebsd-current@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 C1E5CF5EA42; Sat, 24 Mar 2018 17:39:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 165D57674C; Sat, 24 Mar 2018 17:39:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2OHdDJr025216 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 10:39:14 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2OHdCkc025215; Sat, 24 Mar 2018 10:39:12 -0700 (PDT) (envelope-from fbsd) Date: Sat, 24 Mar 2018 10:39:12 -0700 From: bob prohaska To: "Hartmann, O." Cc: FreeBSD CURRENT , freebsd-arm@freebsd.org, bob prohaska Subject: Re: CURRENT r331284: crashing with USB Message-ID: <20180324173912.GA25188@www.zefox.net> References: <20180321120710.4eb3b944@hermann> <20180322044934.GA13553@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20180322044934.GA13553@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 17:39:17 -0000 On Wed, Mar 21, 2018 at 09:49:34PM -0700, bob prohaska wrote: > On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote: > >=20 > > not the ZFS. I can plugin the USB and then unplug it and after two or > > three times doing this, the box goes down. > >=20 > >=20 > > Does anyone else observe this bug? > >=20 >=20 > An RPI2 running r331179 didn't crash, but it did complain about setting > addresses. The same error crops up from time to time when pl2303 serial An RPI3 running r331146 reacted more drastically to the insertion of a USB 3.0 flash drive additional to the one holding /usr and /var; the console began to emit a flood of gibberish: =02=02=02=1A=EF=BF=BD`=06!=EF=BF=BD=EF=BF=BD=EF=BF=BDQsb"J=EF=BF=BD =EF=BF= =BD=EF=BF=BDB=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDdevices... =EF=BF=BD=EF=BF= =BDm=EF=BF=BDo=EF=BF=BDT=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDH=EF=BF=BD=EF= =BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF= =BDHU=EF=BF=BDm=EF=BF=BD=EF=BF=BD** First descriptor=EF=BF=BD=EF=BF=BD=EF= =BF=BDOo]=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF= =BF=BD=EF=BF=BDsc=EF=BF=BD=EF=BF=BDy=EF=BF=BD=EF=BF=BD=EF=BF=BDRRj=EF=BF=BD= 1 Storage Device(s) found s=EF=BF=BD0=EF=BF=BDH=EF=BF=BD=EF=BF=BD *=1C "=EF=BF=BDR =EF=BF=BD=EF=BF=BD=EF=BF=BDX=EF=BF=BDt Dev=EF= =BF=BD=EF=BF=BD=D6=B9.. 1 Ethernet Device(s) found Hit any key=EF=BF=BD}/=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD/_K=EF=BF=BD}?=EF= =BF=BD=EF=BF=BD=EF=BF=BD which persisted across shutdown -r and momentary power cutoff. Removing pow= er=20 for a minute or two seems to have restored normal operation. Note the snipp= ets of clear text; the serial link isn't the culprit, it's working fine. The flash drive had been used as swap on a Raspbian system successfully, and had a vestigal partitioning scheme from a previous FreeBSD-current installation. However, it wasn't mounted in any way, just plugged in, to cause the upset seen above. I wanted to try using the flash drive as extra swap, per advice given elsewhere. Clearly that isn't going to work. Thanks for reading, and any ideas. bob prohaska From owner-freebsd-current@freebsd.org Sat Mar 24 17:52:26 2018 Return-Path: Delivered-To: freebsd-current@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 BC502F600AB for ; Sat, 24 Mar 2018 17:52:26 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 483F0773E2 for ; Sat, 24 Mar 2018 17:52:26 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: f13eaf8e-2f8b-11e8-b951-f99fef315fd9 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 outbound2.ore.mailhop.org (Halon) with ESMTPSA id f13eaf8e-2f8b-11e8-b951-f99fef315fd9; Sat, 24 Mar 2018 17:51:13 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2OHqH2A052577; Sat, 24 Mar 2018 11:52:17 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1521913937.51564.20.camel@freebsd.org> Subject: Re: CURRENT r331284: crashing with USB From: Ian Lepore To: bob prohaska , "Hartmann, O." Cc: FreeBSD CURRENT , freebsd-arm@freebsd.org Date: Sat, 24 Mar 2018 11:52:17 -0600 In-Reply-To: <20180324173912.GA25188@www.zefox.net> References: <20180321120710.4eb3b944@hermann> <20180322044934.GA13553@www.zefox.net> <20180324173912.GA25188@www.zefox.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 17:52:26 -0000 On Sat, 2018-03-24 at 10:39 -0700, bob prohaska wrote: > On Wed, Mar 21, 2018 at 09:49:34PM -0700, bob prohaska wrote: > > > > On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote: > > > > > > > > > not the ZFS. I can plugin the USB and then unplug it and after > > > two or > > > three times doing this, the box goes down. > > > > > > > > > Does anyone else observe this bug? > > > > > An RPI2 running r331179 didn't crash, but it did complain about > > setting > > addresses. The same error crops up from time to time when pl2303 > > serial > An RPI3 running r331146 reacted more drastically to the insertion of > a > USB 3.0 flash drive additional to the one holding /usr and /var; the > console began to emit a flood of gibberish: > > �`!���Qsb"J� ��B����devices... ��m�o�T����H����������HU�m��** > First descriptor���Oo]���������sc��y���RRj�1 Storage Device(s) found >        s�0�H�� * >                  "�R ���X�t Dev��ֹ.. 1 Ethernet Device(s) found > Hit any key�}/����/_K�}?��� > > which persisted across shutdown -r and momentary power cutoff. > Removing power  > for a minute or two seems to have restored normal operation. Note the > snippets > of clear text; the serial link isn't the culprit, it's working fine. > > The flash drive had been used as swap on a Raspbian system > successfully, > and had a vestigal partitioning scheme from a previous FreeBSD- > current > installation. However, it wasn't mounted in any way, just plugged in, > to > cause the upset seen above. I wanted to try using the flash drive as > extra > swap, per advice given elsewhere. Clearly that isn't going to work. > > Thanks for reading, and any ideas. > > bob prohaska Those snippets are some of the first things uboot says when it starts. -- Ian From owner-freebsd-current@freebsd.org Sat Mar 24 18:15:47 2018 Return-Path: Delivered-To: freebsd-current@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 0155AF6239D; Sat, 24 Mar 2018 18:15:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9D3782D4; Sat, 24 Mar 2018 18:15:46 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2OIFmhw025320 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 11:15:49 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2OIFleb025319; Sat, 24 Mar 2018 11:15:47 -0700 (PDT) (envelope-from fbsd) Date: Sat, 24 Mar 2018 11:15:47 -0700 From: bob prohaska To: Ian Lepore Cc: bob prohaska , FreeBSD CURRENT , freebsd-arm@freebsd.org Subject: Re: CURRENT r331284: crashing with USB Message-ID: <20180324181547.GB25188@www.zefox.net> References: <20180321120710.4eb3b944@hermann> <20180322044934.GA13553@www.zefox.net> <20180324173912.GA25188@www.zefox.net> <1521913937.51564.20.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1521913937.51564.20.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 18:15:47 -0000 On Sat, Mar 24, 2018 at 11:52:17AM -0600, Ian Lepore wrote: > > Those snippets are some of the first things uboot says when it starts. > > -- Ian Yes, understood. The initial console text flooded off the terminal scrollback, so it couldn't be captured. The portion selected was meant mostly to relieve suspicions it was a serial malfunction of some kind, copied after several attempts to reboot. It was quite surprising to see the flood of nonsense persist after a shutdown -r now had been issued, and apparently acted upon (the controlling shell exited, but the console flood continued). The console flood came back after a quick power disconnect/reconnect, but finally stopped when the power was left off for a minute or so. Then all returned to normal. Thanks for reading! bob prohaska From owner-freebsd-current@freebsd.org Sat Mar 24 21:56:38 2018 Return-Path: Delivered-To: freebsd-current@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 1D788F4E5F6 for ; Sat, 24 Mar 2018 21:56:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A8D2181D5F for ; Sat, 24 Mar 2018 21:56:37 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id 67476F4E5F5; Sat, 24 Mar 2018 21:56:37 +0000 (UTC) Delivered-To: current@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 430F4F4E5F4 for ; Sat, 24 Mar 2018 21:56:37 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta09p.bpe.bigpond.com (nsstlmta09p.bpe.bigpond.com [203.38.21.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F1C6881D5B for ; Sat, 24 Mar 2018 21:56:34 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep07p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180324205121.DELH24132.nsstlfep07p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com>; Sun, 25 Mar 2018 07:51:21 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtgedrvdefgddugeegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuffpveftpgfvgffnuffvtfetnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefffggjfhggtgfguffvhffksegrjehmredtreejnecuhfhrohhmpeetnhgurhgvficutfgvihhllhihuceorghrvghilhhlhiessghighhpohhnugdrnhgvthdrrghuqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghdprggtqdhrrdhnuhenucfkphepuddvgedrudeltddrgedtrddukedvnecurfgrrhgrmhephhgvlhhopegluddtrddtrddtrdeingdpihhnvghtpeduvdegrdduledtrdegtddrudekvddpmhgr X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from [10.0.0.6] (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A61443617890073; Sun, 25 Mar 2018 07:51:21 +1100 Date: Sun, 25 Mar 2018 07:49:17 +1100 User-Agent: K-9 Mail for Android In-Reply-To: References: <20180324035653.GA3411@Zen.ac-r.nu> MIME-Version: 1.0 Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Warner Losh CC: FreeBSD Current From: Andrew Reilly Message-ID: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 21:56:38 -0000 Hi Warner, The breakage was in 331470, and at least one version earlier, that I upda= ted past when it panicked=2E I'm guessing that kdb's inability to dump would be down to it not having f= ound any disk devices yet, right? So yes, bisecting to narrow down the iss= ue is probably the best bet=2E I'll try your r331464: if that works that l= eaves only four or five revisions=2E Of course the breakage could be hardw= are specific=2E Cheers, --=20 Andrew On 25 March 2018 1:14:40 am AEDT, Warner Losh wrote: >Also, what rev failed? I booted r331464 last night w/o issue=2E > >Warner > >On Fri, Mar 23, 2018 at 9:56 PM, Andrew Reilly >wrote: > >> Hi all, >> >> For reasons that still escape me, I haven't been able to get a kernel >dump >> to debug, sorry=2E >> >> Just thought that I'd generate a fairly low-quality report, to see if >> anyone has some ideas=2E >> >> The last kernel that I have that booted OK (and I'm now running) is: >> FreeBSD Zen=2Eac-r=2Enu 12=2E0-CURRENT FreeBSD 12=2E0-CURRENT #1 r33106= 4M: >Sat >> Mar 17 07:54:51 AEDT 2018 =20 >root@Zen:/usr/obj/usr/src/amd64=2Eamd64/sys/GENERIC >> amd64 >> >> The machine is a: >> CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994=2E46-MHz >K8-class >> CPU) >> Origin=3D"AuthenticAMD" Id=3D0x800f11 Family=3D0x17 Model=3D0x1=20 >Stepping=3D1 >> Features=3D0x178bfbff> APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> >> >> Kernels built from head as of a couple of hours ago get through >launching >> the other CPUs and then stops somewhere in random, apparently: >> >> SMP: AP CPU #2 Launched! >> Timecounter "TSC-low" frequency 1497223020 Hz quality 1000 >> random: entpanic: mtx_lock() of spin mutex (null) @ >> /usr/src/sys/kern/subr_bus=2Ec:617 >> cpuid =3D 0 >> time =3D 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> 0xfffffe00004507a0 >> vpanic() at vpanic+0x18d/frame 0xfffffe0000450800 >> doadump () at doadump/frame 0xfffffe0000450880 >> __mtx_lock_flags() at __mtx_lock_flags+0x163/frame 0xfffffe00004508d0 >> devctl_queue_data_f() at devctl_queue_data_f+0x6a/frame >0xfffffe0000450900 >> g_dev_taste() at g_dev_taste+0x370/frame 0xfffffe0000450a10 >> g_new_provider_event() at g_new_provider_event+0xfa/frame >> 0xfffffe0000450a30 >> g_run_events() at g_run_events+0x151/frame 0xfffffe0000450a70 >> fork_exit() at fork_exit+0x84/frame 0xfffffe0000450ab0 >> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000450ab0 >> --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- >> KDB: enter: panic >> [ thread pid 14 tid 100052 ] >> Stopped at kdb_enter+0x3b: movq $0,kdb_why >> db> dump >> Cannot dump: no dump device specified=2E >> db> >> >> Now dumping worked fine the last time the kernel panicked: I have >> dumpdev=3DAUTO in rc=2Econf and I have swap on nvd0p3 (first) and >> /dev/zvol/root/swap >> (second, larger than the first=2E) >> >> Root on the nvd0p2 is ZFS, and ther's a four-drive raidZ with user >> directories and what-not on them, and another ZFS on an external USB >drive >> that I use >> for backups, unmounted=2E >> >> In the new kernels, we clearly aren't even getting as far as finding >the >> hubs and controllers, let alone the drives=2E >> >> I've attached dmesg=2Eboot from the last boot from last week's good >kernel=2E >> (While briefly in yoyo mode I turned the SMT back on, so now there >are 16 >> cores >> instead of the eight mentioned in the crash dump=2E Didn't help, but I >> haven't turned it back off yet=2E) >> >> Cheers, >> >> Andrew >> >> >> _______________________________________________ >> freebsd-current@freebsd=2Eorg mailing list >> https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" >> >> From owner-freebsd-current@freebsd.org Sat Mar 24 23:23:22 2018 Return-Path: Delivered-To: freebsd-current@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 207ABF55711 for ; Sat, 24 Mar 2018 23:23:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 98BDE858D4 for ; Sat, 24 Mar 2018 23:23:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 595F6F55705; Sat, 24 Mar 2018 23:23:21 +0000 (UTC) Delivered-To: current@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 34CC9F55704 for ; Sat, 24 Mar 2018 23:23:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C14F8858D3 for ; Sat, 24 Mar 2018 23:23:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id d13-v6so6633280itf.0 for ; Sat, 24 Mar 2018 16:23:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=8B7KOsrojjIOCQl7a9eOhJb5uJtynV4tZJrwYscYYzY=; b=uELplQ+kT4/zQYxLMlfX5uG52e+YPmUdkoY0JT2ipqf/U1WNhrvQza6ptWe2sshi4y rYDgWktObtrTTV6CkYeI78nkqOyJ41cTNohffbL5nsfo4WcOfSuC4X2VO7efZX8LIVir OMOB2UsDWmdoPAASDK+KZudwxgXGwgNPjd4pUW6oB97AHvgps6Xk/DhDcc5lQUvePrPd FOUdlx1U3HVwQ7Dr+18ZljDeCoW1rQclgVS8YdXcoR+MVj1nyj4aDQWI2lT+qhWwi7Ic RP/uNdo/Ol564GnOYwpbquVraBO/gpu3qAYdDm0XtN8inIMYxFNeBWX4BKVp38gT3Z/k Kn6w== 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=8B7KOsrojjIOCQl7a9eOhJb5uJtynV4tZJrwYscYYzY=; b=g/EMGN37KNgg8fGFtOeAsaXDWbmb0imdsvCx23JvRBPJjlYl4K7944DF4bbIQpbl6q ReGe/DdsQisJe5bmcyhaKS6IxmfXbw2u/7GnkZ8GDrGBryZVDO+oS7z2znqUeKQzZyqS VPp7/9WL1Cd0TuJnq9NmePU8pnC7OyXKVWejoVgt7CEag9ubozcYq+/IqHiLSuu3HccN BKAreUL+ecfe8pXkWhAv8YxIC/1qD93SsHCg/64mER1Zf3P65SLegqp6Ry8kDOOvX2au bYWTPqAa5/uOQgKu5DTQP9YUQcBqtbDuwpPG0SrSQBAslLEgUqzumov2KImLc3XmSnKh GZSg== X-Gm-Message-State: AElRT7E464/0gl7mIn025wYyeltb6dRS7U5dNqTqMcfl/BJXAEWtn3Dq Et0BdcdexX+Yfwnk+0TvFXbywpAhxEh4oRWPmLdMpQ== X-Google-Smtp-Source: AG47ELun+TN6g8j031lB/dOu0ViIZUA5lXORVwWkb3wAqXdgk3GgOBQXwCqjQhwT9D9j2M5azzsVa6PmEIbGtVa7FtU= X-Received: by 2002:a24:fa83:: with SMTP id v125-v6mr18297134ith.36.1521933799640; Sat, 24 Mar 2018 16:23:19 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sat, 24 Mar 2018 16:23:18 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180324232206.GA2457@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> <20180324232206.GA2457@Zen.ac-r.nu> From: Warner Losh Date: Sat, 24 Mar 2018 17:23:18 -0600 X-Google-Sender-Auth: n-cIsZoM-k7GfbeycYhnJ3UYzyg Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 23:23:22 -0000 Thanks Andrew... I can't recreate this on my VM nor my real hardware. Warner On Sat, Mar 24, 2018 at 5:22 PM, Andrew Reilly wrote: > So, r331464 crashes in the same place, on my system. r331064 still boots > OK. I'll keep searching. > > One week ago there was a change to randomdev to poll for signals every so > often, as a defence against very large reads. That wouldn't have > introduced a race somewhere, > or left things in an unexpected state, perhaps? That change (r331070) by > cem@ is just a few revisions after the one that is working for me. I'll > start looking there... > > Cheers, > > Andrew > > On Sun, Mar 25, 2018 at 07:49:17AM +1100, Andrew Reilly wrote: > > Hi Warner, > > > > The breakage was in 331470, and at least one version earlier, that I > updated past when it panicked. > > > > I'm guessing that kdb's inability to dump would be down to it not having > found any disk devices yet, right? So yes, bisecting to narrow down the > issue is probably the best bet. I'll try your r331464: if that works that > leaves only four or five revisions. Of course the breakage could be > hardware specific. > > > > Cheers, > > -- > > Andrew > From owner-freebsd-current@freebsd.org Sat Mar 24 23:29:33 2018 Return-Path: Delivered-To: freebsd-current@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 5EB2EF55F74 for ; Sat, 24 Mar 2018 23:29:33 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E2F6C85E7F for ; Sat, 24 Mar 2018 23:29:32 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id 98854F55F6F; Sat, 24 Mar 2018 23:29:32 +0000 (UTC) Delivered-To: current@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 83159F55F6E for ; Sat, 24 Mar 2018 23:29:32 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta07p.bpe.bigpond.com (nsstlmta07p.bpe.bigpond.com [203.38.21.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F2DE85E7D for ; Sat, 24 Mar 2018 23:29:29 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep13p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180324232212.HEVL18817.nsstlfep13p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com>; Sun, 25 Mar 2018 10:22:12 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtgedrvdefgddujeehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuffpveftpgfvgffnuffvtfetnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpeetnhgurhgvficutfgvihhllhihuceorghrvghilhhlhiessghighhpohhnugdrnhgvthdrrghuqeenucfkphepuddvgedrudeltddrgedtrddukedvnecurfgrrhgrmhephhgvlhhopegkvghnrdgrtgdqrhdrnhhupdhinhgvthepuddvgedrudeltddrgedtrddukedvpdhmrghilhhfrhhomhepoegrrhgvihhllhihsegsihhgphhonhgurdhnvght X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from Zen.ac-r.nu (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A204A962862D550; Sun, 25 Mar 2018 10:22:12 +1100 Date: Sun, 25 Mar 2018 10:22:06 +1100 From: Andrew Reilly To: Warner Losh Cc: FreeBSD Current Subject: Re: 12-Current panics on boot (didn't a week ago.) Message-ID: <20180324232206.GA2457@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 23:29:33 -0000 So, r331464 crashes in the same place, on my system. r331064 still boots OK. I'll keep searching. One week ago there was a change to randomdev to poll for signals every so often, as a defence against very large reads. That wouldn't have introduced a race somewhere, or left things in an unexpected state, perhaps? That change (r331070) by cem@ is just a few revisions after the one that is working for me. I'll start looking there... Cheers, Andrew On Sun, Mar 25, 2018 at 07:49:17AM +1100, Andrew Reilly wrote: > Hi Warner, > > The breakage was in 331470, and at least one version earlier, that I updated past when it panicked. > > I'm guessing that kdb's inability to dump would be down to it not having found any disk devices yet, right? So yes, bisecting to narrow down the issue is probably the best bet. I'll try your r331464: if that works that leaves only four or five revisions. Of course the breakage could be hardware specific. > > Cheers, > -- > Andrew