From owner-freebsd-stable@freebsd.org Mon Jan 23 06:57:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B1F8CBD13F for ; Mon, 23 Jan 2017 06:57:48 +0000 (UTC) (envelope-from walterp@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::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 B60DCB8A for ; Mon, 23 Jan 2017 06:57:47 +0000 (UTC) (envelope-from walterp@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id k15so108508507qtg.3 for ; Sun, 22 Jan 2017 22:57:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=g7oQ1JkEgFtLZDo+T8LMr6aKauSkxk62CgnEXrdKPtY=; b=aE7Yod0d3uOjduHlXDxbWk6odO9BUslCHLf9ApLV7VVhbajGhkc9iDDklaGxFucqqR C/0qBuRrgF0pT4DJdBTjDd7Baw2AqityW134yDA/T0gl+KYtWzdYVnzGhel5S1SLZMeS WxQy9lfF/WLd01TGwc0f6Q0XKJpLntB0BeaOWIy3JLKObdq/FPRttoyEaWhZOzjDTF7f DP0BPzscvq78zhRGU2px0btN97q+d21X3jQcHc+m72cIZ69GvXlI21+uj5yNeNPiqwi1 oUL1s12iy2qRCEA9JDtKy0RIveaJdQ9FVMSBlRt7IZN58m5AoLYtMuM25oIHS5/vuyW0 GW2A== 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=g7oQ1JkEgFtLZDo+T8LMr6aKauSkxk62CgnEXrdKPtY=; b=Sp9AQCOG56A7qsFPFnsiCuiWfyKTgqVzIl7BIJwEim2Wx+mMwxxVrfuoVK6nWFhRxl +2/cTln0Hx9Nu9u0h9WMohiWXtkHoR8JZtIjR9oMKTVoQl0yHqR87L729yQuiLZDbfTa Orsm68stvo1nMYiEIPbMsJcjxuUskPyq918O+Nmi7vdUkqcyfpXFsWmiNUCzelg0zlaA M38wq3znzcD3Fzzi4xExdz01mPVGio+vwykKHQiqKIa2gGfNKueZ+hhnhruKhLAu6FfG tC6cLjbu64rnPzUGZwLUWZxdpz8xi2+FjNFJeWPLBlmhTDZrclIRI5G/BZAz44oiMrgP +LMA== X-Gm-Message-State: AIkVDXJQR7A1bMPi36XBt3XFHFD2T1czE2vC95bUf0ryB40+q1WtnIw0tbs6CSVc/7b5D7yGx3IRAuvm8mcEmw== X-Received: by 10.55.210.135 with SMTP id f129mr22473061qkj.184.1485154666815; Sun, 22 Jan 2017 22:57:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.162.33 with HTTP; Sun, 22 Jan 2017 22:57:46 -0800 (PST) From: Walter Parker Date: Sun, 22 Jan 2017 22:57:46 -0800 Message-ID: Subject: Building Kernel and World with -j To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 06:57:48 -0000 Hi, For decades there has always been a warning not to do parallel builds of the kernel or the world (Linux kernel builds also suggest not to do this). Every once in a while, I see people post about 5 minutes. This only way I can see this happening is by doing a parallel build (-j 16 on a Xeon Monster box). Are parallel builds safe? If not, what are actual risk factors and can they be mitigated? Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis From owner-freebsd-stable@freebsd.org Mon Jan 23 07:25:07 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81AAECBD96C for ; Mon, 23 Jan 2017 07:25:07 +0000 (UTC) (envelope-from sakhmatd@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 588621A90 for ; Mon, 23 Jan 2017 07:25:06 +0000 (UTC) (envelope-from sakhmatd@riseup.net) Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 395FF1A1FDE for ; Mon, 23 Jan 2017 07:25:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1485156300; bh=v5lxWijSOl2CHTf90FUwh4hxy7kNqvNMW1Q2BM+BvuQ=; h=Date:From:To:Subject:In-Reply-To:References:From; b=WNTYT2O83ZPNt7HW1gkceeO+yYGcCBVWlCFTy0I1C9WFdf4MzBIRZWCr/t19/CU4q APOZIo4ud+7ZhHslFv1/lRi9faaAFQzTmHdk5YiszKyJsTrdmw/SQ4dJHQd6ffGNbw VDMEd+Y5A5hBRG/r77u5+D+S/MQp0pFCbPJGdmw4= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: sakhmatd) with ESMTPSA id 97024402C0 Date: Mon, 23 Jan 2017 02:24:57 -0500 From: Sergei Akhmatdinov To: freebsd-stable@freebsd.org Subject: Re: Building Kernel and World with -j Message-ID: <20170123022457.606a0d8e@riseup.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/IdMhN4t3V.fvQqn/KOhu_BE"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 07:25:07 -0000 --Sig_/IdMhN4t3V.fvQqn/KOhu_BE Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 22 Jan 2017 22:57:46 -0800 Walter Parker wrote: > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). >=20 > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). >=20 > Are parallel builds safe? If not, what are actual risk factors and can th= ey > be mitigated? Not only do I use -j, I also use ccache. Another option is to use WITH_META_MODE=3DYES, that's where most of the 5-m= inute reports come from, I imagine. I haven't used it myself. My kernel takes 10 minutes with world taking about two hours. I generally j= ust leave them building overnight. The risks of parallel builds are mostly in the past, concurrency was still = just coming out and there were chances that something would get compiled before = it's dependency, breaking your compile and wasting all of those hours. Cheers, --=20 Sergei Akhmatdinov My GPG public key: gpg --keyserver pgp.mit.edu --recv-keys AD800D99 --Sig_/IdMhN4t3V.fvQqn/KOhu_BE Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEFByDSlcPK9lAgiNNxKRHP62ADZkFAliFr8kACgkQxKRHP62A DZloCQ//bdpk8xRxqIYD8JegqNnrpxQFysipHQQXXlfFl+lOpXOQfY/0b941nqAA cLq5fN7lA6tzfNUpoZ0enDydgYnnqccD1JBjUFZgf2V68H2C4sFIx5E2iGRfPwHg ZRhh3/v/CsZ9ED3L+aZ+oBNuJCEk/luW1Mi1OxRBXXN7r4H4kMIb48i5fV2BDped y0QdCvrvsZBq+yzDZy12An7ZBtFEQyHUW1htZHRQX1jF4Q+dM8D57OYskXc75756 tlliEkwN1ieqs1fAMSNkkFtBCVhPfHPmgvfw07LTdKkaz08vh52MKSwYZXpxZH9Z b1cpFQbysuNMh2gtAYKmPjhSXpqRvvwGaDMD7PKPvDKRQ1GDSg6/4gypaJNR3tqq 6kdK0VcOgJZj8h1DrJemncoG59y9rzy1uP3HlmhKaKCVVaiTQW+MJ8Nk7Fy3aOH3 LrJjrcSfnLFsyj6f4+U5CtWw7cvmg3vzBHJknZ8ORuZEfdlKZvoxvn5jhFoqcwQA UVyxEeEbKmFhQeJ0aYyo8ER5zrWWoqgVhilIv7pjlXO29ByDeFXQqDCZquK3bmp0 izmRvAldQ7v6heNLoz3LOHVNSDg78DqtoaEhUDmH5xMekYBySRzIwnu6HbDyIe8R cPRXLgXeaYmLD2BAmoE83j5fSDvMwGWQC2nGSW646uyt/NV5u7M= =+vbQ -----END PGP SIGNATURE----- --Sig_/IdMhN4t3V.fvQqn/KOhu_BE-- From owner-freebsd-stable@freebsd.org Mon Jan 23 09:53:27 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB5EACBC2AE for ; Mon, 23 Jan 2017 09:53:27 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67538ABF for ; Mon, 23 Jan 2017 09:53:27 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x229.google.com with SMTP id r126so124046813wmr.0 for ; Mon, 23 Jan 2017 01:53:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=eth/CCZ/Vpj3bATG4McR2RQZjKP0qtPeAA+Z7cZquTk=; b=q6y2Plg1VIIrHA75XHME5okYRWQ+qNqjzP9MXsC6ayyZ+Dpd12KbeqCQREe/2opXSG xIBMg83z09TJCJCebykUjdheZo/TKjD53t9p4OQnXal8BZGL08t6isNVco75zIL5W+k5 D5x2VmsONWT678RPKEEKNkjrT5J+mWIMbPWysQg+0hI9FvzhH4j9mJqt3BVtzShldN9X gSFvqsxkq4Ttyk4qT+RknIWSGasCjAtfRyLi++WCRQxfw4v34fUgvqiRfdW8vuaDq75N WjyrVZksNxSKpN4xIMFsoCcQNHm0+Q8Y+T2B/jlIirynlwxDShH3fr0o1CnRJYXqrmeC Eb/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=eth/CCZ/Vpj3bATG4McR2RQZjKP0qtPeAA+Z7cZquTk=; b=ZhycAJeRibisPGOLRpg5YfrPVZbsQS4BWXi+IGKLD9Nmal5/m4cCTy6xHE6X5NvzwU hhxCi/X17E1FpFiIuX26ROeV2o7jE2a2TD8UzJxc+mZe8b+8F/D9G8R1bnQOAvJWtZ+t nFU0xbBNPPzYqN0p3MdK5QcznsYoSU4jkeE/0fJBNi+c6NglWMeBqJ/DbgClm/PtUZUU I+YdgBXSZBIqgbvCSd2Kr+Z/qasVLYLXA3kQpdZkmyuJPVus+8R5Gs9kkzSA1xy6JUaW z6N+8bNoIFjvCtCffzwOVngY94n1dH6/nYs975u2P6bNkIUHDlrLU1utT45V/XGd1Nhk UUXA== X-Gm-Message-State: AIkVDXJMPnXG/cfX2yPLY6Yy1sWYe/cJtxYxgWyIa8A1ipWUKIP1uiNgI8X+NdIu0NfX1a9W X-Received: by 10.223.163.154 with SMTP id l26mr27274121wrb.35.1485165204872; Mon, 23 Jan 2017 01:53:24 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id s17sm13750487wrc.6.2017.01.23.01.53.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Jan 2017 01:53:24 -0800 (PST) Subject: Re: Building Kernel and World with -j To: freebsd-stable@freebsd.org References: <20170123022457.606a0d8e@riseup.net> From: Steven Hartland Message-ID: <0ac0789a-35db-bed6-b01d-2d817c2e5933@multiplay.co.uk> Date: Mon, 23 Jan 2017 09:53:24 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170123022457.606a0d8e@riseup.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 09:53:27 -0000 On 23/01/2017 07:24, Sergei Akhmatdinov wrote: > On Sun, 22 Jan 2017 22:57:46 -0800 > Walter Parker wrote: >> For decades there has always been a warning not to do parallel builds of >> the kernel or the world (Linux kernel builds also suggest not to do this). >> >> Every once in a while, I see people post about 5 minutes. This only way I >> can see this happening is by doing a parallel build (-j 16 on a Xeon >> Monster box). >> >> Are parallel builds safe? If not, what are actual risk factors and can they >> be mitigated? > Not only do I use -j, I also use ccache. > > Another option is to use WITH_META_MODE=YES, that's where most of the 5-minute > reports come from, I imagine. I haven't used it myself. > > My kernel takes 10 minutes with world taking about two hours. I generally just > leave them building overnight. > > The risks of parallel builds are mostly in the past, concurrency was still just > coming out and there were chances that something would get compiled before it's > dependency, breaking your compile and wasting all of those hours. > > Cheers, We always use -j for both kernel and world for years. While there's been a few niggles if the clock is out and its a rebuild they have been few and far between. Current cut down kernel build time is 1m and world build time is 22m here for FreeBSD 11.0-RELEASE on a dual E5-2640. Regards Steve From owner-freebsd-stable@freebsd.org Mon Jan 23 11:07:47 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08049CBD907 for ; Mon, 23 Jan 2017 11:07:47 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D140CF7B for ; Mon, 23 Jan 2017 11:07:46 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A05812047A for ; Mon, 23 Jan 2017 06:07:45 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 23 Jan 2017 06:07:45 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=7oy4nJZ+yR9f48D Wv6a/So/0Cdg=; b=BfXxs+6KqxgthDG1d397NFWyn1EtDDqOfZOxaNaR3IYyxim wSw8mo2r1KGkskUzyu9e0lzInBCsKh1QblcFuGDiqdDuJhD6UtuL1w6EP0zuBcp3 yOMnCcZ2cTHslrq6l/uqc8djOw7paIKscpGjWEmN/aRA2VHQgxLdRxsb+mx0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=7oy4nJZ+yR9f48DWv6a/So/0Cdg=; b=kR4L8u4bfoUbCc8HfaSk 3pKrzc3YPoIWgbk5kvD4TXB30rWjoIXaJRvWgko/W3nzuytpqjT70C2Z3Mnsisr6 MphZ/Q4M4+z9QgwKYjxl+4qQpPJNd3PibxdyfXHS/G+voxEra+M+/EyjkmumGgVU kbmVpiGYVnMpht66f0qM8GQ= X-ME-Sender: X-Sasl-enc: 6ld40yUfu55aKVilr7105ilOP46rQNBvMq1H/R8+v+LA 1485169665 Received: from pumpkin.growveg.org (pumpkin.growveg.org [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 4304E7E404 for ; Mon, 23 Jan 2017 06:07:45 -0500 (EST) Subject: Re: Building Kernel and World with -j To: freebsd-stable@freebsd.org References: From: tech-lists Message-ID: <693bfe80-fb44-4a3f-c0c3-6fd79a0055b3@zyxst.net> Date: Mon, 23 Jan 2017 11:07:37 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 11:07:47 -0000 On 23/01/2017 06:57, Walter Parker wrote: > Hi, > > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). > > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). > > Are parallel builds safe? If not, what are actual risk factors and can they > be mitigated? I remember warnings to the effect that while buildworld and buildkernel was safe, installworld and installkernel were not. I use -j32 on i7 monster boxes. -- J. From owner-freebsd-stable@freebsd.org Mon Jan 23 14:11:13 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2E64CB8D29 for ; Mon, 23 Jan 2017 14:11:13 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 958063DF for ; Mon, 23 Jan 2017 14:11:13 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id C51D233C1E; Mon, 23 Jan 2017 09:10:59 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 278133981A; Mon, 23 Jan 2017 09:10:57 -0500 (EST) From: Lowell Gilbert To: Walter Parker Cc: freebsd-stable@freebsd.org Subject: Re: Building Kernel and World with -j References: Reply-To: freebsd-stable@freebsd.org Date: Mon, 23 Jan 2017 09:10:57 -0500 In-Reply-To: (Walter Parker's message of "Sun, 22 Jan 2017 22:57:46 -0800") Message-ID: <44k29l27f2.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 14:11:13 -0000 Walter Parker writes: > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). > > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). > > Are parallel builds safe? If not, what are actual risk factors and can they > be mitigated? As a general rule, it's safe. But don't report failures from a parallel build. This is not so much an issue of parallel builds being unsupported as of the logs being harder to read. From owner-freebsd-stable@freebsd.org Mon Jan 23 15:13:33 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77A62CBE48C for ; Mon, 23 Jan 2017 15:13:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) 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 65279149C for ; Mon, 23 Jan 2017 15:13:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 61940CBE48B; Mon, 23 Jan 2017 15:13:33 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 613CACBE48A for ; Mon, 23 Jan 2017 15:13:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (ingresso-1-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:411::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 32D1B149B for ; Mon, 23 Jan 2017 15:13:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cVgJH-0002y5-MP for stable@freebsd.org; Mon, 23 Jan 2017 15:13:31 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87_1 (FreeBSD)) (envelope-from ) id 1cVgJH-0004aA-Kk for stable@freebsd.org; Mon, 23 Jan 2017 15:13:31 +0000 To: stable@freebsd.org Subject: Horrible zpool resilver perormance on local hast Message-Id: From: Pete French Date: Mon, 23 Jan 2017 15:13:31 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 15:13:33 -0000 I have a pair of machines running hast cross two pairs of drives - i.e. 4 drives total, two in each box, and hence two hast resources, cbert0 and cebrt1. Its been running mysql fir a long time, but there only 6 gig of data actually in use in the pool. I rebuilt the secondary machine, and wanted to resync the hast devices, but that would involve copying 450 gig for only 6 gig of actual data. "easy" I though, "just rebuild each has device in the pool so it only has the current data dirty" seems reasonbale enough ? so I disconnected one bit of the mirror, did a 'hast create' to zero it, and reattached it to the mirror. (note that the secondary side is entirely disconnected, this is local to one machine). what I am seeing is that the zpool is resilvering at a rate of 170K/s - currently it says this: 622M scanned out of 6.53G at 170K/s, 10h9m to go But the hastctl status outout says this: status: degraded workerpid: 950 dirty: 136363114496 (127GB) statistics: I onyl expect dirty blocks when the ZFS has ritten something -0 127 gig dirty seems excessive for 622 meg written! anyone got any idea what might be happening ? -pete. From owner-freebsd-stable@freebsd.org Mon Jan 23 15:37:33 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 212F6CBEA94 for ; Mon, 23 Jan 2017 15:37:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0EB06831 for ; Mon, 23 Jan 2017 15:37:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 0E156CBEA93; Mon, 23 Jan 2017 15:37:33 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DCA1CBEA92 for ; Mon, 23 Jan 2017 15:37:33 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (ingresso-1-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:411::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3710830 for ; Mon, 23 Jan 2017 15:37:32 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cVggV-0003Iw-Hv; Mon, 23 Jan 2017 15:37:31 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87_1 (FreeBSD)) (envelope-from ) id 1cVggV-0004e0-GK; Mon, 23 Jan 2017 15:37:31 +0000 To: petefrench@ingresso.co.uk, stable@freebsd.org Subject: Re: Horrible zpool resilver perormance on local hast In-Reply-To: Message-Id: From: Pete French Date: Mon, 23 Jan 2017 15:37:31 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 15:37:33 -0000 Partially answering my own question here, as it occured to me that the zpool is scattering writes across the disc in 4k blocks, but hast has a minimum extent size of 2meg by default. Thats eems like a likely culprit for the 'dirty blocks' multiplcation I am seeing. I shrunk down the extent size to 16k to see if that helped, and I now see a far smaller dirty block to written block ration, but also the write speed has now shrunk down even more to around 50k/s :-( Any advice on tuning this properly ? -pete. From owner-freebsd-stable@freebsd.org Mon Jan 23 18:09:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE56ECBE1F5 for ; Mon, 23 Jan 2017 18:09:29 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 71F707A8 for ; Mon, 23 Jan 2017 18:09:29 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id c85so145273218wmi.1 for ; Mon, 23 Jan 2017 10:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=MTu++kI0qaBu/y7kwKFiwk0i3hOtAdNUnYte3OAKY2c=; b=fmn3gtnXl0l6N4IH/Sm/xb14LQyYHM27APnz/xz2TGLkZzN3R7wisyzfcxMKKMIGsA 9kT6ZOiKH4qYODOzh6urFPBOuDrZwzpfG5sw9G0/CGgzb67AdSq3wJ8K1h+J/Wx71ASN JZ9ZNPhZNxAx3NG0vQcy1XCbeUNyKP3Gxx1khRUjSMmfquYtG32lA3feNu93lATubxgF g3Ca/fRE8O734A2PUa5i/XrI0IIagdVPBYL/K3BHvt6LWcabXwL/te4jIZtvuNj0+rbK HU74ZMxrhQD+u2RINzZawYBszeRKfQ9tCo10NQQakFJzLsUad2YMSCts6FwqB3h+fkOW KsCw== 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=MTu++kI0qaBu/y7kwKFiwk0i3hOtAdNUnYte3OAKY2c=; b=kH96/85idLcwkiOUliMODJ1FpYtpS2tdFOu3PMRt1U+WLQCLkxfGhDrJKSY+6Ht81V BAF8T8lahMruP8+L1wUn9YDDvlmKOaC+i30Va9IThe1FoMferkNah44uq61NXcFb8TX/ F/D/yl623PVVlglTTWxVYRGgV9LTM5hRZLHkKdm+3yaY2GI0irl/B5TLqS5BdB6lZqHd IgHp5Rc5DKDe315tIKpGJJ9jFUwmC3uTh4IcWYiQkfrUZtXu2YRg5ac4g+iwjDqqtiUm hmwNHvA4IkeEHdmy/5/G255BOnWtMjQ3UpUXlpKF9GvbMz2bYispPe7JY3mhq7RaAM3D RDsw== X-Gm-Message-State: AIkVDXL3SS7sRKY74C4uUjNLfzeHQZZJ+91DYElf6ef/bEk9M5JJSPIQ+uxr2Y0TOFYQJhT56Kuy8ApaWEaCBg== X-Received: by 10.28.147.72 with SMTP id v69mr15363496wmd.51.1485194967686; Mon, 23 Jan 2017 10:09:27 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.41.194 with HTTP; Mon, 23 Jan 2017 10:09:27 -0800 (PST) In-Reply-To: <44k29l27f2.fsf@lowell-desk.lan> References: <44k29l27f2.fsf@lowell-desk.lan> From: Kevin Oberman Date: Mon, 23 Jan 2017 10:09:27 -0800 X-Google-Sender-Auth: 1-jywwsfBAaLuYXHI56yfmv5y2w Message-ID: Subject: Re: Building Kernel and World with -j To: FreeBSD-STABLE Mailing List Cc: Walter Parker Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2017 18:09:30 -0000 On Mon, Jan 23, 2017 at 6:10 AM, Lowell Gilbert < freebsd-stable-local@be-well.ilk.org> wrote: > Walter Parker writes: > > > For decades there has always been a warning not to do parallel builds of > > the kernel or the world (Linux kernel builds also suggest not to do > this). > > > > Every once in a while, I see people post about 5 minutes. This only way I > > can see this happening is by doing a parallel build (-j 16 on a Xeon > > Monster box). > > > > Are parallel builds safe? If not, what are actual risk factors and can > they > > be mitigated? > > As a general rule, it's safe. But don't report failures from a > parallel build. > > This is not so much an issue of parallel builds being unsupported > as of the logs being harder to read. Use of parallel builds of world and kernel are and have been supported since at least 10.0. If a parallel build fails, the first step is usually to do a single-job build. If it succeeds, there is a bug in the make scripts that should be reported. If the single-job build also fails, a bug should be reported with any errors included from the non-parallel build as the parallel build makes the error context very difficult or even impossible to determine from the log. Generally, I think the number of jobs should be slightly greater than the number of available CPU threads. Back in 10.0 days I ran some tests that showed the for 4 and 8 thread systems the improvements for large numbers of jobs peaked at about CPU thread count + 2 and significantly larger numbers of jobs caused a slight deterioration in performance. This was not true on early hyper-threaded CPUs which did not effectively optimize hyper-threading and things may have changed in the 6 or 7 years since I tested and may be very different for systems with large numbers of threads seen in servers today. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Tue Jan 24 10:59:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD529CBF64F for ; Tue, 24 Jan 2017 10:59:48 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (mail1.mimar.rs [193.53.106.128]) (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 9872E18AC for ; Tue, 24 Jan 2017 10:59:47 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail1.mimar.rs (localhost [127.0.1.128]) by mail.mimar.rs (Postfix) with ESMTP id 1BA659FA8968 for ; Tue, 24 Jan 2017 11:59:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:message-id:subject:subject:from:from:date :date:received:received; s=mimar-0901; t=1485255576; x= 1487069977; bh=joMg21qysiDRmrYQaVuXhkigrYonlRJ6JC9THldWVKM=; b=S Yd4r2q6HdLPwPQVNGBuY3MB2VDiKvc/ZhZwSwFPMDCK9HC9KwmtdDuwUhlLA3CVA CvWPfoePV2BWatAZmsmpPg6TQMM4n2BOE9r9r3D0xuTPjnxw8eAWzlDFx+XAVpfe s/annwMaXWu5Y1e6jnJYEHLiizlJnR7krvXS09FOVs= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.1.128]) by mail1.mimar.rs (amavis.mimar.rs [127.0.1.128]) (amavisd-new, port 10026) with LMTP id pgA-onlZXcfh for ; Tue, 24 Jan 2017 11:59:36 +0100 (CET) Received: from mephala.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id 473DB9FA891B for ; Tue, 24 Jan 2017 11:59:36 +0100 (CET) Date: Tue, 24 Jan 2017 11:58:11 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-stable@freebsd.org Subject: network after resume Message-ID: <20170124115811.52f83662@mephala.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 10:59:49 -0000 Hi, I am running 11.0-RELEASE-p6 amd64, and I'm having a strange problem on my ThinkPad T440: after resuming from suspend, wifi resumes operation and I can ping around, play music from NFS share etc., but I can't open websites in chromium, pidgin won't reconnect to xmpp server, ownclound client won't connect etc. Restarting network with `service netif restart` tears wifi connection apart and re-establishes it again, but those applications just won't connect. Any idea why those applications won't work when underlying OS has network connectivity? Could it have something to do with those applications connecting via SSL/TLS? Thank you in advance, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-stable@freebsd.org Tue Jan 24 18:02:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6455CC0CF4 for ; Tue, 24 Jan 2017 18:02:48 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-ot0-f179.google.com (mail-ot0-f179.google.com [74.125.82.179]) (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 B37873B3 for ; Tue, 24 Jan 2017 18:02:48 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-ot0-f179.google.com with SMTP id 73so133382257otj.0 for ; Tue, 24 Jan 2017 10:02:48 -0800 (PST) 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; bh=eUGofXp0v6ZOVcNnHywWUCuQOFoe+xr0RyAlZ3dURYI=; b=MFPefgGYoc/ZYzgXZS2mOdiJpyjZqO/bHkaHNxPqFCeRcZGJIP2xbUYrEolUMC8YKa UhCI+NTSMqmhuKla1LI1sE5cVPzwQBGWQcKFT8H7kgLwQkcL739o8cgtjBIgN1pmpWlP SI8aezNMjVN7E2YRSYpu2rHTdHjgHTp4IBQNl+2qEzhBzdVmo+nJS2sh3lw0ZwAMcxyD kP+bPMzZLc6zh9q5PXWGSzVsAhmXr14Fjj+y1ON+/0R2M2zUifTZsqceBaI9+Li5XomD JByGD1PYeFd6z7PBV6f4AgBXlylPMt6I/5q1SkW+ZkrXlMFy9z+QvrTjc//xwgRGKsCn TxvA== X-Gm-Message-State: AIkVDXKU1YWV/HhvJvDRsiVkcAb3IPpadKTWUZLQ6wvnwaqBzYStnpA0pH4Na6iUPrFhAw== X-Received: by 10.157.33.230 with SMTP id s93mr17022105otb.106.1485280638123; Tue, 24 Jan 2017 09:57:18 -0800 (PST) Received: from mail-ot0-f171.google.com (mail-ot0-f171.google.com. [74.125.82.171]) by smtp.gmail.com with ESMTPSA id t53sm10837452otd.6.2017.01.24.09.57.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Jan 2017 09:57:17 -0800 (PST) Received: by mail-ot0-f171.google.com with SMTP id 73so133255565otj.0 for ; Tue, 24 Jan 2017 09:57:17 -0800 (PST) X-Received: by 10.157.24.92 with SMTP id t28mr18740323ott.238.1485280637235; Tue, 24 Jan 2017 09:57:17 -0800 (PST) MIME-Version: 1.0 References: <11f0e9e6-cfe7-1cc7-49a0-4bc42fd0f99a@gmx.de> In-Reply-To: <11f0e9e6-cfe7-1cc7-49a0-4bc42fd0f99a@gmx.de> From: Eric Joyner Date: Tue, 24 Jan 2017 17:57:06 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: intel 10gbe nic bug in 10.3 - no carrier To: Daniel Genis , freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 18:02:49 -0000 On Tue, Jan 10, 2017 at 2:38 AM Daniel Genis wrote: > Hello everyone, > > we're trying to tackle a rare bug that is very hard to debug. > > Our 10.3-RELEASE servers can panic boot and subsequently can come up > without network (2x - no carrier). We've seen this on 10.3-RELEASE-p0 we > have never seen this before. > > root@storage ~ # pciconf -lv | grep -B3 network > ix0@pci0:2:0:0: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' > class = network > -- > ix1@pci0:2:0:1: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' > class = network > > Our network is configured as active/passive using lagg. (/etc/rc.conf): > > ifconfig_ix0="up" > ifconfig_ix1="up" > cloned_interfaces="lagg0" > ifconfig_lagg0="laggproto failover laggport ix0 laggport ix1 10.1.2.31/16" > > After panic boot the network show up like this: > > ix0: flags=8843 metric 0 mtu 1500 > > options=8407bb > ether 60:08:10:d0:4e:9f > nd6 options=29 > media: (autoselect) > status: no carrier > ix1: flags=8843 metric 0 mtu 1500 > > options=8407bb > ether 60:08:10:d0:4e:9f > nd6 options=29 > media: (autoselect) > status: no carrier > > The network switch sees the connection as online. The LED's of the nic's > suggest the same, they see the network as online (led's are on like in > normal operation). Unplugging/replugging the network cable will get the > network online. Shutting the port on the switch and reenabling it wil > also get the network online. However another reboot will return the > machine into the no-carrier state. > > I've built various kernels trying to find where the regression is > without success. I tried porting the 10.2 nic driver (2.8.3) to 10.3 and > subsequently the lagg code as well. I ported nic driver 3.1.14 from > pfsense into 10.3-STABLE (2 december kernel) to no avail, also porting > lagg code from 10.2 did not make any difference. Rebooting with those > kernels the server remains in the no carrier state. > > We install our systems using mfsbsd for PXE boot. If I boot a machine > which has the "no carrier" state using the 10.3 PXE boot, both nic's > come online. If I then boot from disk again the machine returns into the > "no carrier" state. > > Recently we got some new machines, so we can shuffle more around and > also to try to debug this. We baseinstalled it using mfsbsd 10.3 pxe and > configured it like always. Here interestingly one of the two nic's > entered the "no carrier" state, the other nic remained operational. This > remained persistent across reboots. > > The issue disappears after many reboots but it's not conclusive. I've > had 2 machines with which I could experiment with. > > On one the problem it disappeared on it's own after a reboot (kernel > 10.3-STABLE git hash d99ba5c aka r299900(?)). > > On the other one I pxe booted 10.1 live environment and then > subsequently I booted into kernel 10.3-STABLE git hash 3673260fc9 aka > r308456(?)). But I don't think anything can be concluded from that. That > was the machine which had both nic's online after booting into the 10.3 > pxe environment but subsequently returned into no carrier state when > booting 10.3 from disk. > > We also tried many sysctl flags (and many reboots), but without success. > For example: hw.ix.enable_msix=0 and hw.ix.enable_msi=0 > > At the moment I have no spare/empty machine in this state, we will empty > one machine though which currently has this state (but is in production > right now). > I don't know how to trigger this state manually, which doesn't help for > debugging. > > I could link reference where others report similar issues, for example > https://www.reddit.com/r/PFSENSE/comments/45bcuq/10_gig_woes/ > Here they suggest that the new intel nic driver 3.1.14 fixes it. Though > I was not able to resolve the state by booting into a kernel with this > driver. > > If I can provide any additional information please do not hesitate to ask. > > Any tips and suggestions for debugging are most welcome! > > With kind regards, > > Daniel > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > This is a late follow-up, but could you file this as a bug on bugs.freebsd.org? - Eric From owner-freebsd-stable@freebsd.org Tue Jan 24 19:04:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F898CBF0B5 for ; Tue, 24 Jan 2017 19:04:48 +0000 (UTC) (envelope-from lrizzo@med.edu.ky) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0084.outbound.protection.outlook.com [104.47.38.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF63816; Tue, 24 Jan 2017 19:04:46 +0000 (UTC) (envelope-from lrizzo@med.edu.ky) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mededu.onmicrosoft.com; s=selector1-med-edu-ky; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SC4Rgz4aevYwiCB8mvr/d5r5PoajoCv1RuQ7nEj0hXs=; b=aF6psymK/yvw/q6fy6WPIp8XugunixsEdzhb5Ynp0V8wsBo7TCYMHdIsSfhJi6Ge0B6oKJzp5QW8kSMwJMcBb6E2KdYq3wZZq4RPkM0efiFghwuphPS9a8b91I0PaKVP9lsKM76VcqrxtgdgjK8Izzn9apN3bWfPCPHLcuoOBZU= Received: from SN2PR18CA0033.namprd18.prod.outlook.com (10.169.189.43) by DM3PR18MB0700.namprd18.prod.outlook.com (10.164.248.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.860.13; Tue, 24 Jan 2017 19:04:42 +0000 Received: from DM3NAM03FT046.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e49::200) by SN2PR18CA0033.outlook.office365.com (2603:10b6:804:1b::43) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.860.13 via Frontend Transport; Tue, 24 Jan 2017 19:04:42 +0000 Authentication-Results: spf=pass (sender IP is 172.81.179.3) smtp.mailfrom=med.edu.ky; freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=pass action=none header.from=med.edu.ky; Received-SPF: Pass (protection.outlook.com: domain of med.edu.ky designates 172.81.179.3 as permitted sender) receiver=protection.outlook.com; client-ip=172.81.179.3; helo=med.edu.ky; Received: from med.edu.ky (172.81.179.3) by DM3NAM03FT046.mail.protection.outlook.com (10.152.83.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.2 via Frontend Transport; Tue, 24 Jan 2017 19:04:42 +0000 Received: from med.edu.ky (localhost [127.0.0.1]) by med.edu.ky (8.15.2/8.15.2/Secured_Mail_Gateway) with ESMTPS id v0OJ4eL3003656 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 24 Jan 2017 11:04:40 -0800 Received: (from lrizzo@localhost) by med.edu.ky (8.15.2/8.15.2/Submit) id v0OJ4dfr003655; Tue, 24 Jan 2017 11:04:39 -0800 Date: Tue, 24 Jan 2017 11:04:39 -0800 From: Lucius Rizzo To: CC: Subject: FreeBSD 11.0, sendmail from ports PRE-INSTALL script failed Message-ID: <20170124190439.GA1132@med.edu.ky> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:172.81.179.3; IPV:CAL; CTRY:; EFV:NLI; SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(2980300002)(438002)(189002)(199003)(50986999)(2351001)(106466001)(450100001)(6916009)(40036005)(5660300001)(50466002)(42882006)(626004)(110136003)(38730400001)(74826001)(83506001)(54356999)(7596002)(26826002)(305945005)(356003)(97756001)(36756003)(8676002)(2906002)(189998001)(46406003)(47776003)(8936002)(33656002)(42186005)(1076002)(4326007)(4001350100001)(246002)(88552002)(74482002)(92566002)(23726003)(18370500001)(87636001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM3PR18MB0700; H:med.edu.ky; FPR:; SPF:Pass; PTR:med.edu.ky; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; DM3NAM03FT046; 1:EKE2svHFG65EQ3hZU3YypvtwNOJ/vPZ4hmAU3FaYm33rFxyRpou/EWzAF9+D8fDQEAaeOQwWBsHxAFeJ+f5XxNgh0Ux+64wdZYmb8gUMckwfhI05r85ssLMz4qSulVFqQef+05Uk1CmxKN40xXIRvN+WdusozjXOnwALJHPrfwdAx835xJmWG7BjUnPJJC2m79ocl3I3qxNQinxohPpCEHsTbu7+P1hfEiQqpCrN2ISJZp7p67MZICm1T9XM6l352vo7GsHClDXnE2ous3lobcLYOHWcgH/ZcWnFEo1MOda6AeVAz+niZECGL7I3FmhxilFmbUwzgtDYKWn4vQVql1MxzTgmFKZ3qMqJTCrGn61Fdef4mCe7A0lg0sZqUspnjAHIxiUidiqXAUvGcAPzp6zsRNCxaqiNuEzlEf8m9t/qyXLqYF4pkvRd2h4P3CO8wYpgpqy8n3cvZMfkDPBk24l+hl/Ekwrl3h2bwVj6C6s= X-MS-Office365-Filtering-Correlation-Id: f273f525-5d50-4489-9e10-08d4448bda7b X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(8251501002); SRVR:DM3PR18MB0700; X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 3:YqtAq0vkFrRNGL48dmT3y04acNAHKwE51oF9nZhZv3KWGjBOH0UIF+YN0RypMO75W5ks3YMpjPXW2ihOEJDNwcP6akgbQOXkidBl2YSak5GtObodtTgWfHEy+dX/sGy+8axCdljGombB72h9rDz83rV8MjkF5+lQSIGQ524K5bwbdOEHFbmBkKk2K4NmLYvfV7JcVDYo1vTpC7iPOhXMG3mL2Zz8fA9siba+Vz2Uiufp3Mc/R/1oKtK4S+o7c1He4lzrZBbrpSeM+xC1EIZJtFlC32XBzCRY/GwPCKxRoWC3y2BYxLUQA/IZm3NhHrq28281fKkDdl5PKBU18A3kMD2ffZ02h0q8vrW4QiMQj8VXhqqSdQpkTWcpRqvUOzae X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 25:LeI9TDMCEGXxptOUjH68pWR0FZHfytUPBNbqPRkQGJf+6gle7UUYQ13AZPRb3VCEtIEudlablFFy0JsLGabJzpj3lHMOh5rBXNGbLxofUvXKOIwf9UASF8DEBEg0mQSpgmXK/g++X5fdMBy6m4D7vu/jPkDuI8gk1th06rWthpF4MdqqTcfCrNCaxZG2igHQlQnujqr7IeuwW/gnCYIu21CZCG2sLwb5GG6IYx4caWg80Lpcl0DTMVTNOGHHzW3nqt0w4G7FEsRvpaS8QmqpIFFOPhC3Y2A+1Nf06oE6vAZ9PKHYAy12A0EuR4wcPjpdxLsMVBqBGTWRH/LNJMSJzdF1cxQzVQa0RTd30gkkRQtGkFCS/471a1xqWYvIaYjtThHIQfrz32jV+Ngz6lF1+qYaWDgIxFYiGzD/PeZhwjyFhx/BDMmop4BjkI2J2aY7a5vtcFgx59mKjLo7Nl1j97FXmZiinbIov1jownnhQuqjO+XoDdMqBTJgNtVVe9T+kzRaRjYPZGSV8eHo6N+F1txP5xPaQOkWbzItb17axt8yyd5J4zAop96oJG14pp3TmrXd7MQVMCYfd/80vUe7vmfW4//NMYInrvC3k2etlVnjnOVXFf3dCqk/yqWJH3FcEbbJeXs0MUjFNLi5pp0KfHbSP4moT2yCmcJFuH0EGN/qJM+3z1M58FCNJjom9AP5vaOOSoCYf2VfrDTV35Di+cRWiA8jwhhfvocye4yq5wtySY4olDrOS6jWeVSpxyCdFiJ2IzxZgxhStN+m8hjAO86UBLps3Dd1tp/O8SjHeUrv9ryr6DBieWihqDAxmrQ25JxxVz1NZWoPE+mBK7Cyng== X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 31:F976Tc3VCYu+LaI1HS1+5/Npw6PANdpBbw9xAqogLA933YPvvJTwj4AtvPCKA73xFszGudyhUDaMsXDVSvueWI1bxdvIJpXl5qqNRbzPxEHDfC/lWnFzEJ2GJPp1Vf/LTNqdwNhYfSjaSjDiqAjUPyMVxuN2NIOgZnkDquumGF2yaupGbxkXwU9h6Mpa3e9kCiNZbplAaGJRrnBzs6bx//yxa2lu2Z0RqSlXKrfFvhIG7uLVrUUS990l7nhxkJOLk3WnGXN/aZ4ZOcoP+cA/ug== X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(13023025)(13013025)(13021025)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(2016111802025)(6072148)(6043046); SRVR:DM3PR18MB0700; BCL:0; PCL:0; RULEID:; SRVR:DM3PR18MB0700; X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 4:In1ZAbFNqnBLcgs2frxY9Q6FSAQGFcQYZlR3ko9CgAGpSN/S/2gpUNmoS+DS56UP7cpXyssOHe3acIdbP6Uk8XHL60m/HDIFp5InaBbNDwDNI2td3Hk8R0WwEP4XGCHvlMQhvJUQrK6J54mbxwfw6mrrsDR2WJOXVs8JUwzznXKoQgFcO3rI7vFPoS3uWu0JT9qvvTZz+rcj7Ag7+0YAysFXgoojuqTIdWtEaUnGt2vy73LLd9w3kbJ4R61IWHrFEaB2I43l9u5VA6M1BwyRZfuwUmBUMZESd3/OAA71KnOmaHCdonTizZvI88I0n4cnCEy0XDeFv18uKLNrZzCOVTl7X2JROAscYv45IPBlGjXh/t2D05vn0hRQK8JNIRJXTao3CCXkrtDV+lXZq5faP+YG2m37GndaAB99aBp8Y3mlzkhinYmIsMmsCiR/oy6MNCRt16DvHmqLY4QnTOhf9CVzeIdvgRg7Yg2z4//Ik3ezxW95QUGEz4WepNp4N7fdBJnzrmCx3ipng02/rIQrkdjUT87Ri1OWgCscov7CfgqazIYzaD7ac63JNQOiBEUteTD6vlA5ZdspvNycCt58A3E0xluy2ObVJmMWYSxNUg147GHz84g+lFNTMTsxqpB82ZirUJy5wsTM2MZrxE25ktRhtYK3U1FhB1lazyVLV2aIEiagGRtYjKtslzrtMXsn X-Forefront-PRVS: 0197AFBD92 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM3PR18MB0700; 23:FpkQIkjKn6mOyMmuQg84Lxxo57BjN+10b3itV0R+D?= =?us-ascii?Q?tGKB2Ixmea0vR0apWB5ID7jncYvB5Vu5tBLazIQnFe5N3l12ynshFHpaSR3D?= =?us-ascii?Q?DiZ8GgrTCMn2yWTCGVotywlCP4J7P01zGYwrN36u1PA9yyMEWegP77XU0+NB?= =?us-ascii?Q?1BTy1v2Z/uYsCjhR3GRBz4be0xSbpfo/PtSS987WLBZhH7SSHxAWrX/JgcMJ?= =?us-ascii?Q?V/oTfYDNCxKfNWQks6/es0Lj0dY9gF0TaWVwLjy3+21gb64iOokZas1rEXSR?= =?us-ascii?Q?rLUareDzqV37aPlPef/s8YEJROu9mNF3QP6aXxIREMPilauB3D/Cq2ar+SlJ?= =?us-ascii?Q?X794c0kmdr/c0A0SkN6aLOKenR/am5sFOOTzr0SljefX+cFEciRNPniXw5MT?= =?us-ascii?Q?m3PYH2HPoB8g9rYWk66LVjwlOZ9zjbdGeNLnGJ/p+LBIdQH+pGIxkIrSu/rQ?= =?us-ascii?Q?7UX4apLLAVpig+qazRh6zY+02T54x1RKZ74tqZB2ImJNb9yb25AQ+6ANe7bG?= =?us-ascii?Q?xaaD8JPCvEccgbVOvjqfPbm4PILLkn/KzgtSOBY5NZMpZSOobeCHJWkoHwMh?= =?us-ascii?Q?biNd+fWStRjWP8Ja9Br9+VudAzyYwtH6D77LGaYe/adHeg8F9B5S9f4ZxSMy?= =?us-ascii?Q?exoV5NKiK8jf+HC0Gt2Wg8J3geg3QFgxXHBQOSXWjKtVIomPKFDbYUsY5zYc?= =?us-ascii?Q?ze/QjPlVRAmL3RK0sGrkARRMOUCT66Di8f+H91XsdeVdYU/w68MyOp0Z8I4t?= =?us-ascii?Q?/+059885K1AEhfK+LyFAB9dGlzrnCV0y8LpJFeeWNrPEpEoCGpzdubQILl+T?= =?us-ascii?Q?PUAnEM4m9Ce2dGmW73TnAj9ny9deN0fuR6/mPYagGc8a7ZQ8yClWztpHnVqM?= =?us-ascii?Q?D7nrHQDYWGoqjAif5dMptuCbYpYqjmeJF2dbCJiD2JUIvKXr1XoZ8RvEFEOl?= =?us-ascii?Q?PX1dCuKmDNz7fFwFv3IVe8grhacr5TnTgsCn/A+JxPElv4e4SlyJnHwP+EMW?= =?us-ascii?Q?zLjIfYsNOBQMtFkeso2H71Myfh/8jJxVBa3iCYcyJgp0lrJET1s5qbLah3Hg?= =?us-ascii?Q?7QQR1DADY061ty4C56eNDWxBfNnWFoOQ6JqQ0z7HfM4CkmtUw=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 6:kSuCjrLd7EmfoPRwiReV9Ig+sbmtRmEHQNTsrbcn7W2nWvFoSGDbIOzyrrdrbayprYuM76ujUmflPjfvbJcusyk0UGVv7uKYjvHA1hkMyXT2t6ql11PF+PimigntAmSJvDIukWiH8E9ITxkTq0miIP4bUD85gUmJGmlhghb22DHPTNaayEHH/HSJ6LSHue0kz+aoVsLgYnRBAv/RSqVG0Co6MSPr01Dftqq8khO/iohzONaXJGZ/YXvLi7KUue6+WsvYeDACjQikpzRdQnJ8bimATqknTeLjcfcbobdLnxVZuPwjM2iHxgh+dt8UFxUljQ6HMWABEhddL2B5MRewrx/l7KNQJYVWOe7TFnfKDb8ymfgUM3KGipPvvikE4WmlnDlw+YBTCxLof7TQOWFHEaG852TX1VyBoIsk5O47Op8o1yt+ZpA6uXDk0B7hWLQE; 5:Sok2TU6oTGX2f60v+MUpae4Ilgz5rMb3CDyavpvDKCOr42CMxtCGfcz5/1oJ41ap2ynW+cPQfffNlVWWfuYr2Pb8KU8w6G6hLS96Hj3Xg5u+xE50IGZZ9q5Srx8plddo8mgMGMPhBPPuaVcxNRWqcqFYdYWxWzqawZHasGkby9k=; 24:lKOmoyknt2T0fI+hotA8NvpgDPVNtT2S44BdAmtyUCLXddxm3TbGBQyTMpM/o1c9w6NmmGGLa933Mp+SDCX7D7IaLhQbVVoGUKG+Ubgu1DQ= SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-Microsoft-Exchange-Diagnostics: 1; DM3PR18MB0700; 7:m+6J2GB+Y8gLZeWahFYrA1M8tBHol7GtHEhFuDbK5LS7VuWKsot7qm/qEp2wQFL6SVRvZ3dGerta2S1h1wK5JBTUCthoscqIbliNdiPgzZPiKBtBLCIJ6/wH7ggS8Y5zOWegYQfQl0o2CaLDlUfg0bfOkFEA3l35iv/kI8bm3a5M5AFaDDwADoMAT+2cdH0DNPE/ARbLOBbsFOzC3gR4QPp7fvuzLP//2aeIH+e0ZdksbOx58dZlUXYAmd3cwjFpuPLy9U+7Q0nYix//IWzPT6u7qI1TORqge2rPLN29TeIf9pUbjrcKMJyQMaBMqlL4WO7Xt7lzfRpwAVPm5/OKj4jiiebbf3MeTCZVyOt2GzznQTQ1DOjChq9NjI+sjV+TojlcM85lRxfDDv1fzFoQNqHUBG/Y9s6Y4L4y03oOE1y7bdRdsnx0hpDyycNOWlQ7tQuGFeeR0I+r0U6CkR3URQ== X-OriginatorOrg: med.edu.ky X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jan 2017 19:04:42.0259 (UTC) X-MS-Exchange-CrossTenant-Id: 802a5422-9e9b-45c2-a586-6f87b7ccf7f1 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=802a5422-9e9b-45c2-a586-6f87b7ccf7f1; Ip=[172.81.179.3]; Helo=[med.edu.ky] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM3PR18MB0700 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 19:04:48 -0000 Hello, I am installing sendmail from ports on a FreeBSD 11.0 box. During the compile (from ports), the install fails: ===> Registering installation for sendmail+tls+sasl2+ldap+db5-8.15.2_3 pkg-static: Warning: @exec is deprecated, please use @[pre|post][un]exec Installing sendmail+tls+sasl2+ldap+db5-8.15.2_3... ===> Creating groups. Using existing group 'smmsp'. ===> Creating users Using existing user 'smmsp'. install: option requires an argument -- g usage: install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner] [-M log] [-D dest] [-h hash] [-T tags] [-B suffix] [-l linkflags] [-N dbdir] file1 file2 install [-bCcpSsUv] [-f flags] [-g group] [-m mode] [-o owner] [-M log] [-D dest] [-h hash] [-T tags] [-B suffix] [-l linkflags] [-N dbdir] file1 ... fileN directory install -dU [-vU] [-g group] [-m mode] [-N dbdir] [-o owner] [-M log] [-D dest] [-h hash] [-T tags] directory ... /bin/sh: smmsp: not found pkg-static: PRE-INSTALL script failed --------------------------------------------------- From owner-freebsd-stable@freebsd.org Wed Jan 25 09:52:22 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F6F4CB5057 for ; Wed, 25 Jan 2017 09:52:22 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C79E9CB4 for ; Wed, 25 Jan 2017 09:52:21 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. ([IPv6:fd00::7af]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v0P9qF8l065946 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 25 Jan 2017 14:52:16 +0500 (YEKT) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1485337936; bh=wcesSxf6tMaBFN0429Qwkcp/UvZ4estdZBGCsdS9opA=; h=To:From:Subject:Date; b=rEewuL+RfQKOth/Gx4uQ+PlNN+Wls5QqnBAkemULOscN75AhVtb2ZHG5RdAygKu1V qiiG/1abhnm3LU19Z6TknsWt1iSUdn/gkHn0vBeptCtnWI4SXWNlUvW658rMrrxyVv ED3e0NHOARLbFp5shhn6C0W7GcZn7jOd1Cg/IGtw= To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Subject: reset not working like 70% of the time Message-ID: <5888754F.2040901@norma.perm.ru> Date: Wed, 25 Jan 2017 14:52:15 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 09:52:22 -0000 Hi, does anyone suffer from this too ? Right now (and for several last years) a 100% decent way to reset a terminal session (for instance, after a connection reset, after acidentally displaying a binary file with symbols that are treated as terminal control sequence, after breaking a cu session, etc) is to launch midnight commander and then quit from it. And the reset is working like in 30% of cases only. Unlike in Linux, where it's 100% functional. Am I the only person seeing this ? Eugene. From owner-freebsd-stable@freebsd.org Wed Jan 25 10:15:17 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39322CB5D0A for ; Wed, 25 Jan 2017 10:15:17 +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 F39DE1068 for ; Wed, 25 Jan 2017 10:15:16 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cWKbl-0007iC-2n; Wed, 25 Jan 2017 11:15:17 +0100 Date: Wed, 25 Jan 2017 11:15:17 +0100 From: Kurt Jaeger To: "Eugene M. Zheganin" Cc: freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125101517.GW13006@home.opsec.eu> References: <5888754F.2040901@norma.perm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5888754F.2040901@norma.perm.ru> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 10:15:17 -0000 Hi! > does anyone suffer from this too ? Right now (and for several last > years) a 100% decent way to reset a terminal session (for instance, > after a connection reset, after acidentally displaying a binary file > with symbols that are treated as terminal control sequence, after > breaking a cu session, etc) is to launch midnight commander and then > quit from it. And the reset is working like in 30% of cases only. [...] > Am I the only person seeing this ? I had some cases in the past where xterm was hanging, too -- but not with *that* high rate of problems. Most of the times, xterm's Full Reset options works fine. The question is: how to debug that... ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Wed Jan 25 10:24:59 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6749CBF181 for ; Wed, 25 Jan 2017 10:24:59 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4732B17B3 for ; Wed, 25 Jan 2017 10:24:58 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. ([IPv6:fd00::7af]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v0PAOtBl067650 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 25 Jan 2017 15:24:55 +0500 (YEKT) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1485339895; bh=2Bv3cQxh5XHmzSKBFrpqKUP8ctpg9+nA/anX5d2KW2I=; h=Subject:References:To:From:Date:In-Reply-To; b=t4lUsRnoqnxN+gvCA5F5rOAH7SbVBnBagpgY2t/IQTUPQ0QbDgQqsJHhOg2m4yTg8 yGagcWyvL40vB5FX4hoNouNo6xne5uuU2lpn6Hnoe/f6I7rEt+OR8RJFHFYcI8phy6 FMHpfIBMr3ZQkb/q/D3oiGvupgVbS3y7tD7jR9MA= Subject: Re: reset not working like 70% of the time References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Message-ID: <58887CF7.1010908@norma.perm.ru> Date: Wed, 25 Jan 2017 15:24:55 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <20170125101517.GW13006@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 10:25:00 -0000 Hi. On 25.01.2017 15:15, Kurt Jaeger wrote: > Hi! > >> does anyone suffer from this too ? Right now (and for several last >> years) a 100% decent way to reset a terminal session (for instance, >> after a connection reset, after acidentally displaying a binary file >> with symbols that are treated as terminal control sequence, after >> breaking a cu session, etc) is to launch midnight commander and then >> quit from it. And the reset is working like in 30% of cases only. > [...] >> Am I the only person seeing this ? > I had some cases in the past where xterm was hanging, too -- but > not with *that* high rate of problems. > > Most of the times, xterm's Full Reset options works fine. > > The question is: how to debug that... ? > A typical cases are: - newlines aren't working properly, current line just got cleaned and that's all (no scrolling up one line happens) - mouse clicking produces some input symbols in the terminal line - Ctrl-C stops working (just nothing happens) I'm seeing all of these in my konsole terminal window while working with local and remote hosts (mostly with remotes), an typing 'reset' usually just does nothing. God bless the Midnight Commander ! Eugene. From owner-freebsd-stable@freebsd.org Wed Jan 25 10:26:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D1B7CBF30D for ; Wed, 25 Jan 2017 10:26:25 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D57EC1AD1 for ; Wed, 25 Jan 2017 10:26:23 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from hephaistos.local ([79.208.137.127]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MC8iq-1cf6Di3npQ-008ql6; Wed, 25 Jan 2017 11:26:11 +0100 Received: by hephaistos.local (Postfix, from userid 1000) id BB0F9297CDF7; Wed, 25 Jan 2017 11:26:09 +0100 (CET) Date: Wed, 25 Jan 2017 11:26:09 +0100 From: "Martin S. Weber" To: Kurt Jaeger Cc: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125102609.GA1359@hephaistos.local> Mail-Followup-To: Kurt Jaeger , "Eugene M. Zheganin" , freebsd-stable@freebsd.org References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170125101517.GW13006@home.opsec.eu> User-Agent: Mutt/1.7.2 (2016-11-26) X-Provags-ID: V03:K0:p2su1w70nIm0HFLVYwFqNnpDHORTQUorG7uKOaI8Qb185AbVKyi 5QiyEId/PDPfYalOv8bEAdqm1EoBZDDKrPUCHT7o3is8AQci7BZa9ZKTED9kM+MjlC0cWQ6 1zLoqbhodEE/br8n2RcdDbkuQKEEdCup3Eiaza4k1nNn8LDU7R6nhxHG0P1AiYEXWrlcomH xNgwwBmluZTs3NlcoeEeg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qZxT0pT8EOI=:TjefYQC6lcXE4FQVKJcjVu QdPY7e+xU24md0ODqIPtZ0PuDj+g0ybAIMOM4Gxn3I9W6TzB8VCUOeQrgo7IKHjna0TGOf6gH VjDHRWT5WE/hdEmkky2vmA5GM/BvtJ5BFqS2y7K/B7sj8wAeONwEtldd/yfYiefCS90XVgx7b 605vzRLQC9llyAJjFFZWUlQyCA3uIOOvQDT2cpF8t5YGJ7feH5L/Oukvbgg5V02Yf1FRtjkQt GHSdHW6/tv63PnEU9b1ihYbUpYL06ecpebcywr+71nQLS1G750bELZ58ejOGMv5HLkXXPEmbm ly/OyBHr3k8qjal5Xh+viMa/Gi1/47OhkmfVKcI2n+j5yinTKcwObbCgAiFbOXBtCLa5pNu+z iShrtU0w0A7vuVuy7Nvx1HntcZMwEUs+mY4ECmTM8wclQsbuWlfY9yw9HGWUz2YwG4h7cYMs2 CH7pdTwxS4laYznflHOUJfHdzbgdHPlz3x1wx29dw8R42mzw4YxSmqB0Gf6pTYb9ZPpl3GsZP zW1SNIdJO11+7YStxD1RqISCIMmOTEepTVqWI+Lp5QKbHMsNWWR39JpVCeq+3vcGubkXI4uyC J+1LDB7kywALnIFL/1LdlxtBH/YxJIDadrvF1/yfju9Ez2ecjhNYhEfK+n2gfPH1O+gCIyayH G7JSyuJXroDNRWoPUU8hbT8ePkRLBCA1HNIbrMzJjQUSgEXYQno+m9afTfiI6KoVQiyIAo2m9 /QAElQrfhcXz3lUchRk3tOGIhrhLPIPIq1rvqa6sx1W2I+3UsdnMnxiZwEj4p5eVH+LF9tFrr 3/JbVLxSyu/vUPaeu94cGHGzOSF9Lngh63Im+UTurmorWe4vE7gSraKKXp7ec311SD6O272Eq ET+ppFUIqx5QtTaD+GxgdS+AgsFXgSmNKjqLAzVP0T/qE9MVLzITkvehoWzkAa+cdMOW/lGzp sh0xl9MJuHjkxR5jT1FoNAgtSwPLEfuKEHW+VdWcdiuVYKV6kaIQ5arLWk/LogUD+6T/NpqLI nA== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 10:26:25 -0000 On 2017-01-25 11:15:17, Kurt Jaeger wrote: > Hi! > > > does anyone suffer from this too ? Right now (and for several last > > years) a 100% decent way to reset a terminal session (for instance, > > after a connection reset, after acidentally displaying a binary file > > with symbols that are treated as terminal control sequence, after > > breaking a cu session, etc) is to launch midnight commander and then > > quit from it. And the reset is working like in 30% of cases only. > [...] > > Am I the only person seeing this ? > > I had some cases in the past where xterm was hanging, too -- but > not with *that* high rate of problems. > > Most of the times, xterm's Full Reset options works fine. > > The question is: how to debug that... ? Use script(1) to record an offending session, including the reset. Then replay with script or cat or ... Regards, -Martin From owner-freebsd-stable@freebsd.org Wed Jan 25 12:07:38 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 065DCCC016A for ; Wed, 25 Jan 2017 12:07:38 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (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 BCD28F9E for ; Wed, 25 Jan 2017 12:07:36 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.36] (unknown [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPA id 99FEB9DC716; Wed, 25 Jan 2017 13:07:27 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: reset not working like 70% of the time From: Borja Marcos In-Reply-To: <20170125101517.GW13006@home.opsec.eu> Date: Wed, 25 Jan 2017 13:07:26 +0100 Cc: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 12:07:38 -0000 > On 25 Jan 2017, at 11:15, Kurt Jaeger wrote: >=20 > I had some cases in the past where xterm was hanging, too -- but > not with *that* high rate of problems. Hmm that doesn=E2=80=99t sound too good. Potentially exploitable bug?=20 Borja. From owner-freebsd-stable@freebsd.org Wed Jan 25 12:16:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E162CC04DB for ; Wed, 25 Jan 2017 12:16:29 +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 641F115B8 for ; Wed, 25 Jan 2017 12:16:29 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cWMUy-0007xp-Iu; Wed, 25 Jan 2017 13:16:24 +0100 Date: Wed, 25 Jan 2017 13:16:24 +0100 From: Kurt Jaeger To: Borja Marcos Cc: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125121624.GX13006@home.opsec.eu> References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 12:16:29 -0000 Hi! > > I had some cases in the past where xterm was hanging, too -- but > > not with *that* high rate of problems. > > Hmm that doesn???t sound too good. Potentially exploitable bug? I assume so, yes. Needs more fuzzying 8-} -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Wed Jan 25 12:58:07 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72C98CBE06D for ; Wed, 25 Jan 2017 12:58:07 +0000 (UTC) (envelope-from bounce@ims8.isendservice.com.br) Received: from ims8.isendservice.com.br (ims8.isendservice.com.br [177.71.248.1]) by mx1.freebsd.org (Postfix) with ESMTP id DCC28978 for ; Wed, 25 Jan 2017 12:58:06 +0000 (UTC) (envelope-from bounce@ims8.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims8.isendservice.com.br (Postfix) with ESMTP id 775C042480 for ; Wed, 25 Jan 2017 10:28:33 -0200 (BRST) Date: Wed, 25 Jan 2017 10:28:33 -0200 (BRST) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: joel.ferreira@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <886845377.517623.1485347313444.JavaMail.root@ims8> Subject: =?ISO-8859-1?Q?O_Que_Voc=EA_Quer_ser_Amanh=E3=3F_Curso?= =?ISO-8859-1?Q?s_T=E9cnicos_2017_na_Faculdade_SENAI?= bounce-key: <2420-22522874-1604684> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 12:58:07 -0000 From owner-freebsd-stable@freebsd.org Wed Jan 25 16:54:49 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 085E3CC10E3 for ; Wed, 25 Jan 2017 16:54:49 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (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 C893D7F8 for ; Wed, 25 Jan 2017 16:54:48 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cWQqG-0006at-3Q for freebsd-stable@freebsd.org; Wed, 25 Jan 2017 17:54:40 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: network after resume References: <20170124115811.52f83662@mephala.kappastar.com> Date: Wed, 25 Jan 2017 17:54:38 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: <20170124115811.52f83662@mephala.kappastar.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 9090f8a1960d7f777b94d17b6f36e747 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 16:54:49 -0000 On Tue, 24 Jan 2017 11:58:11 +0100, Marko Cupa=C4=87 = wrote: > Hi, > > I am running 11.0-RELEASE-p6 amd64, and I'm having a strange problem o= n > my ThinkPad T440: after resuming from suspend, wifi resumes operation > and I can ping around, play music from NFS share etc., but I can't ope= n > websites in chromium, pidgin won't reconnect to xmpp server, ownclound= > client won't connect etc. > > Restarting network with `service netif restart` tears wifi connection > apart and re-establishes it again, but those applications just won't > connect. > > Any idea why those applications won't work when underlying OS has > network connectivity? Could it have something to do with those > applications connecting via SSL/TLS? > > Thank you in advance, What error do those applications give? Some applications do their own DN= S = caching. That cache might be stale, but the real error message would = provide more hints than me guessing. Regards, Ronald. From owner-freebsd-stable@freebsd.org Wed Jan 25 17:59:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BB95CC12B7 for ; Wed, 25 Jan 2017 17:59:29 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C085192D for ; Wed, 25 Jan 2017 17:59:29 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id c7so113746171itd.1 for ; Wed, 25 Jan 2017 09:59:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BghmCxzwWWla6TiZ4D27xGlKPP+UqtvbwiU8Fk7hTxc=; b=EXBP+cCNCBcRECVQbIQTF552J15xT/bwwwPc5xOVF8e/S7VKgf1SrrcpDeeHBNVVIb SKQfv1WIsXlO2T7j0AICwUnV/Y7pYgMttiQY21HuVvrvSaZN8ugggyj4majXmGjHDaiK rUPvoAvgqILyQ9FiAyEk+PpKUWOJRhFMByy+yNA4He0Eeuba0iQoWlYVgVXA0kSzR5NK BieBICW4IQS9UNmIaJ/a/wjPe4PzVTr9E8QhfYeCT34fXdZZJaThEKjuI+1UxW5G/bvg IkCQkMgz+gYcqpElP5QW8Y1F3iYpa4xAs64bzLK+mpvltWNmE9qrDSY43qD/3wPcKQvK eeIw== 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=BghmCxzwWWla6TiZ4D27xGlKPP+UqtvbwiU8Fk7hTxc=; b=lVx0sYSOjsTQrOmCyGPAfYqfdb/RF7ti+6IyD6MBddKYN8hGFDE+H9kszmtK8H+ioG 8z5bSCmIf8uWuvGqYtKuk38Wwbzr6ooUdrwiNaBnyJUUr7szU34gQmPK9LDKNsiDU1y/ M6zZWaehfBHA/fYI21YnEcXvBcQFlZ8i48ztZAI5dj6unn60TxR7N1Cpjfz/YQQk+IdD 7T3Z326UhPMvGrHcYmWr92QSujOtCzJx1D8WwlC//3eAdU8bYCtpxLexX4AZTuDZh35G 0d+5qoW+JGJt75f2IXafmqM6WMmQuceNY2AFmJYn7YsrSoMM50+/E8c9UJhnxV+hIak1 FRlg== X-Gm-Message-State: AIkVDXLsUuh3IDR9ePa13qFYomRO1vQkFocQfN6c7rYUxUT3rx5uv0XJtyemlwz69G+5wSbXplTtQLtvpXQUKg== X-Received: by 10.36.102.195 with SMTP id k186mr26862276itc.75.1485367168414; Wed, 25 Jan 2017 09:59:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.18.197 with HTTP; Wed, 25 Jan 2017 09:59:27 -0800 (PST) In-Reply-To: <5888754F.2040901@norma.perm.ru> References: <5888754F.2040901@norma.perm.ru> From: Brandon Allbery Date: Wed, 25 Jan 2017 12:59:27 -0500 Message-ID: Subject: Re: reset not working like 70% of the time To: "Eugene M. Zheganin" Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 17:59:29 -0000 On Wed, Jan 25, 2017 at 4:52 AM, Eugene M. Zheganin wrote: > does anyone suffer from this too ? Right now (and for several last > years) a 100% decent way to reset a terminal session (for instance, > after a connection reset, after acidentally displaying a binary file > with symbols that are treated as terminal control sequence, after > breaking a cu session, etc) is to launch midnight commander and then > quit from it. And the reset is working like in 30% of cases only. Unlike > in Linux, where it's 100% functional. > Using an application like that to reset the terminal is dubious at best. You are at the mercy of how exactly it does terminal conditioning, and nobody makes any promises about its actual behavior. In fact it could be argued that, if it does not put the terminal back exactly the way it found it, the application is broken. But this is actually impossible to do correctly as the application can't know the terminal's full ANSI X3.64 state. Additionally there's a bit of a "religious issue" around whether full screen applications use xterm's alternate screen (and whether xterm even has that enabled) which will save and restore more of the X3.64 state around the application. "tput reset; stty sane" (or just "reset") should usually put the terminal into a sensible state. If it doesn't, figure out whether the part that isn't happening is a termios or a terminfo setting and focus on that part. Check if xterm has "Enable alternate screen switching" checked on the control-middle button menu. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Wed Jan 25 18:25:26 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9776CC1E19 for ; Wed, 25 Jan 2017 18:25:26 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22D34E2 for ; Wed, 25 Jan 2017 18:25:25 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from hephaistos.local ([79.208.137.127]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Ljqgb-1bvBUj0iBl-00bsTl; Wed, 25 Jan 2017 19:25:16 +0100 Received: by hephaistos.local (Postfix, from userid 1000) id A007C297CDF6; Wed, 25 Jan 2017 19:25:14 +0100 (CET) Date: Wed, 25 Jan 2017 19:25:14 +0100 From: "Martin S. Weber" To: Brandon Allbery Cc: "Eugene M. Zheganin" , freebsd-stable Subject: Re: reset not working like 70% of the time Message-ID: <20170125182514.GB1359@hephaistos.local> Mail-Followup-To: Brandon Allbery , "Eugene M. Zheganin" , freebsd-stable References: <5888754F.2040901@norma.perm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-Provags-ID: V03:K0:vBtPaIKAzxs2/UEOHY75gNVPIbPKgO13SqzxtpnjSlE1RriAT/r YQCUhg5WfbskhRYBRgkABrD9695tNaSeGFRh1Mutt6psG7GNJ/VgtMYm9oWikk9eribIe6N q5F939bCin2aNjUFnXwZiCV8cLVMPJybNU1/VkRAmNWJ7EoJybi3orxLzCE3a8QXicAg108 QNk3FJv54AGrV/CXLStUg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qUFyV3YChyY=:1Py340kD2e+s2PC08uHh45 T1RTXN8jJJy3FJQfUgR/HhMmvkRmg/V1Zo+4U89ze4l4elufmePgrtC/B66wgXU5Ob6Wrxq5v 5fyiNQWRmGvmP86YuT9VOwQ1lTOhaeXIkTZlgriYhY2+jYkqhi/or7blqDBEpOraddbHPratq pL7XDt5xxHy5mXtR5xwBMnzgzaqqrIQRka4sXNfJwf1k6djSUAd87LdwBLDd8ILaKO18vlF4T PaPa1uxby9XMVCtpDYhOc4PwDiGTUCfUfGTb0xH6IBXps1WAPcIN/bpIbGK+Y4/ZWe4nP6DmQ Xyv3Jpgp9VUi+goVuM98eePfwly82ImNPtbo1/MBr3nXuGq6mk4rnPHFF97JqTahaZeuecOBi LIjn4RdNj6AbzdxtuJ2JgZ4cGjeOqmcT2bMcCGTUbxV9JyvciDMQpg0+NjZhefovNvJg1faFp +d7C+qwdUlgvRKm9OmMr5x0trxTt/0GeDxu99uKymRe+Pa/0m5ztRWeC9LjBZmJ9DHJ9b3km1 XkP1ls+RV1aX4lXn+n4oR0022gMBp5SdUjqIrvxf3j1EPskxdo3ZJuZxougHfquHRx0hTIl2h eVJ/9cEpMhfsuEKts4JmLQn3mQ62ldmLG33Zt8ThNbKUtIOdf7RPS06ub+fzwm5B0uzVYkX42 N/Qv7PrJIDmNhsedBJ8ZrXTEFfOCMjayrV0srXHZ9KLsYDUtA25de/wcHy7T84XTeuccyxsgO ekFUjgpl5CerJ0l99DnnlSlAT85EOKeYGymdjp5WUnSO0AEwzc3oVST3xBU= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 18:25:26 -0000 On 2017-01-25 12:59:27, Brandon Allbery wrote: > On Wed, Jan 25, 2017 at 4:52 AM, Eugene M. Zheganin > wrote: > > > does anyone suffer from this too ? Right now (and for several last > > years) a 100% decent way to reset a terminal session (for instance, > > after a connection reset, after acidentally displaying a binary file > > with symbols that are treated as terminal control sequence, after > > breaking a cu session, etc) is to launch midnight commander and then > > quit from it. And the reset is working like in 30% of cases only. Unlike > > in Linux, where it's 100% functional. > > > > Using an application like that to reset the terminal is dubious at best. > You are at the mercy of how exactly it does terminal conditioning, and > nobody makes any promises about its actual behavior. In fact it could be > argued that, if it does not put the terminal back exactly the way it found > it, the application is broken. But this is actually impossible to do > correctly as the application can't know the terminal's full ANSI X3.64 > state. Additionally there's a bit of a "religious issue" around whether > full screen applications use xterm's alternate screen (and whether xterm > even has that enabled) which will save and restore more of the X3.64 state > around the application. > > "tput reset; stty sane" (or just "reset") should usually put the terminal > into a sensible state. If it doesn't, figure out whether the part that > isn't happening is a termios or a terminfo setting and focus on that part. > Check if xterm has "Enable alternate screen switching" checked on the > control-middle button menu. OP stated he's using konsole (KDE wannabe xterm). OP, try and create a minimal file with script that doesn't clean up your terminal on reset(1). Make sure it doesn't contain confidential information. Publish your environment (env | grep TERM) and this script file somewhere. Let others know the URL. Then we can actually begin to answer your original question, whether or not we see this as well. You could also try to reproduce your problems with different terminal emulators (xterm, freebsd console) Regards, -Martin From owner-freebsd-stable@freebsd.org Wed Jan 25 18:28:53 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28BCBCC1F23 for ; Wed, 25 Jan 2017 18:28:53 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCAE5324 for ; Wed, 25 Jan 2017 18:28:52 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by mail-it0-x231.google.com with SMTP id r185so18566650ita.0 for ; Wed, 25 Jan 2017 10:28:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=wSThuU00q2e+gV6Fu+9Ze5tDyZoWUUnvwPQv7WoUjbM=; b=CfWYo27gNHN6xB2vOdmXNAGe8Gxgo9n5rmvC0MHrQgOJVipPw1+Odzqn8yRA1j66YY GsmCoIfQmZsZ+rf3MbSZIg+S5+ZwvRhW0Yvx9P3On5lqwoT+W77+cegC5EmgZtKlydSI ZX5gR9RE9kLqr72SoEnyRZ7pxCx5WNOFX5ibeDvPq6kAzuWvqp7phJz6NLsW9y3wpigl 7ihuT8CsDV1wpKDMApZCquJEtJT/h+hTeCHeBvWoRMdAa6MuH75IryKKJSJYF+8XWDer XGI4d+VchW2wooLh0sosiXW7vjc3qLAT8b7dUmf7d2t9gcG7Zmz3aQLvF15nk38dkBDn 79mw== 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; bh=wSThuU00q2e+gV6Fu+9Ze5tDyZoWUUnvwPQv7WoUjbM=; b=Xo9pi2J75pOU9RTbroal/F0XWX/FDaUgZ80LoPi5g1ugMLeTPlSbkBS0DCocLkhTQD 4XNwKDrLqq5HmSnVLc26BZxEQVBdjs3AsvZ0c4jE1FsuB64IHGfivkYsoZM2RMt3DGFa NSEKgE+htCXhD78ONTNUF82rdD35I8GUp659tncXpUvmj+DTQtVZk2K+i/hCyym39iLB hp8XyYfbGvtwB8FYYqlfa5HKGqkgZ/JhPJ3IPEDnafgRSMLzyR7KpbFnZIF4kjLFiDZ0 H5q4l5J/D8xdtKLQ6TW1tPDlnZeE5x5s0axLqmtSBNtVq7MTeZqTRBnku7hqZYrN/TgF +Drw== X-Gm-Message-State: AIkVDXJTwJGRFku8wVw28WUMzCgcgQPV9YrTstQp6GR9S03jre9IwEtP1Zys4npBH4Ru9fmoWfqvymL8Slp2Gg== X-Received: by 10.36.111.82 with SMTP id x79mr24533222itb.1.1485368932227; Wed, 25 Jan 2017 10:28:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.18.197 with HTTP; Wed, 25 Jan 2017 10:28:51 -0800 (PST) In-Reply-To: <20170125182514.GB1359@hephaistos.local> References: <5888754F.2040901@norma.perm.ru> <20170125182514.GB1359@hephaistos.local> From: Brandon Allbery Date: Wed, 25 Jan 2017 13:28:51 -0500 Message-ID: Subject: Re: reset not working like 70% of the time To: Brandon Allbery , "Eugene M. Zheganin" , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 18:28:53 -0000 On Wed, Jan 25, 2017 at 1:25 PM, Martin S. Weber wrote: > OP, try and create a minimal file with script that doesn't clean up your > terminal > on reset(1). Make sure it doesn't contain confidential information. > Publish your > environment (env | grep TERM) and this script file somewhere. Let others > know the > Also include output of "stty -a" ideally both before and after the terminal ends up in a weird state. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Thu Jan 26 16:36:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DC45CC31E8 for ; Thu, 26 Jan 2017 16:36:25 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3975F4A for ; Thu, 26 Jan 2017 16:36:24 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-vk0-x22a.google.com with SMTP id x75so158077433vke.2 for ; Thu, 26 Jan 2017 08:36:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1P5MK419CiPsslmLTmG5fBWqfS0HB9ZOwXuACeSc74Y=; b=LIRau2/WaNbbXPfKUrJT6/FowbdiWSnUS+05g3XRfyYO088d5tu+VQALMQtbN7I2O0 ChAKroVLpbuTNHUcnz8bsi3wq4kmmTYATMgFaYCjMAflPeT64Z7U2Qkpr4MPh/ECvwU0 29gwQJjxPi5Xw4lw+cxN19e0QM/hjaNxwdtzP3hKdOsSRi5m4kw+xcdwDSq8Qa1uuAIU Z9oqxbQ+xV+V1jGVD4/DrkqF85JHyTrEr0zAFJk6LLM/0c8oStbx6UfMUh/d2QXbAd0Z +MCbKwA7GAzFUeBYp2aTFyehVQPf0bvl+DxH2zE3AjU9wABUJ6VK98XU0KkrsBfTx9XR zYVQ== 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=1P5MK419CiPsslmLTmG5fBWqfS0HB9ZOwXuACeSc74Y=; b=KBbifQBLn3fXVNmdTB12NZWi1zyybkJsPu9rPNNFUbbb/bwAfATPtv4vylyEpjTc/G eG/oO7yMadfe2zmkUeOJS9pYYdxLdssL0WfzTvMhKI5lmqKOjHALvStCqjJnMgDEPnD1 sQHeZWc4Bwew3ItBtMXMvzEOYF6E4dOD6RGgM49zZagwR6EKgxf1EKB2ju566khJCZ00 Pd4K60qnb4UphiHemUy6b2b/60MhycL9wMDnzuTq1LTfd88mtZcjyrohX8sB+qWdgtHb TObFbejWesns7vg+ThqksPdbHBmlq1bpE6XeEEty0H68hqrUxOqZF86RUbcrnbbqC3Ci 4wAA== X-Gm-Message-State: AIkVDXKJAYT1GxP235DX8CekG+wLniFrl+LSQqNiMUJ28A9GXQYe17foLSEAWQfmkKQHnOkAWHzcR55ielQEPQ== X-Received: by 10.55.192.137 with SMTP id v9mr3541245qkv.305.1485448583965; Thu, 26 Jan 2017 08:36:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.173.40 with HTTP; Thu, 26 Jan 2017 08:36:23 -0800 (PST) In-Reply-To: References: <44k29l27f2.fsf@lowell-desk.lan> From: krad Date: Thu, 26 Jan 2017 16:36:23 +0000 Message-ID: Subject: Re: Building Kernel and World with -j To: Kevin Oberman Cc: FreeBSD-STABLE Mailing List , Walter Parker Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 16:36:25 -0000 I use these options in my src.conf WITH_FAST_DEPEND=yes WITH_CCACHE_BUILD=yes I can often get build times of about 9 min but can got upto about 30 mins in jenkins depending on how much has changed. This is on a i5-3570K. It does have 32GB and ssd l2arc. Those times are for a buildworld, buildkernel packages for pkgbase. and j is set to 5 On 23 January 2017 at 18:09, Kevin Oberman wrote: > On Mon, Jan 23, 2017 at 6:10 AM, Lowell Gilbert < > freebsd-stable-local@be-well.ilk.org> wrote: > > > Walter Parker writes: > > > > > For decades there has always been a warning not to do parallel builds > of > > > the kernel or the world (Linux kernel builds also suggest not to do > > this). > > > > > > Every once in a while, I see people post about 5 minutes. This only > way I > > > can see this happening is by doing a parallel build (-j 16 on a Xeon > > > Monster box). > > > > > > Are parallel builds safe? If not, what are actual risk factors and can > > they > > > be mitigated? > > > > As a general rule, it's safe. But don't report failures from a > > parallel build. > > > > This is not so much an issue of parallel builds being unsupported > > as of the logs being harder to read. > > > Use of parallel builds of world and kernel are and have been supported > since at least 10.0. If a parallel build fails, the first step is usually > to do a single-job build. If it succeeds, there is a bug in the make > scripts that should be reported. If the single-job build also fails, a bug > should be reported with any errors included from the non-parallel build as > the parallel build makes the error context very difficult or even > impossible to determine from the log. > > Generally, I think the number of jobs should be slightly greater than the > number of available CPU threads. Back in 10.0 days I ran some tests that > showed the for 4 and 8 thread systems the improvements for large numbers of > jobs peaked at about CPU thread count + 2 and significantly larger numbers > of jobs caused a slight deterioration in performance. This was not true on > early hyper-threaded CPUs which did not effectively optimize > hyper-threading and things may have changed in the 6 or 7 years since I > tested and may be very different for systems with large numbers of threads > seen in servers today. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Thu Jan 26 16:51:10 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 345EECC3607 for ; Thu, 26 Jan 2017 16:51:10 +0000 (UTC) (envelope-from daniel.genis@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C1051AC3; Thu, 26 Jan 2017 16:51:09 +0000 (UTC) (envelope-from daniel.genis@gmx.de) Received: from [192.168.101.182] ([80.113.31.106]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LaWlT-1c57em2VcF-00mHLC; Thu, 26 Jan 2017 17:45:47 +0100 Subject: Re: intel 10gbe nic bug in 10.3 - no carrier To: Eric Joyner , freebsd-stable@freebsd.org, s.munaut@whatever-company.com References: <11f0e9e6-cfe7-1cc7-49a0-4bc42fd0f99a@gmx.de> From: Daniel Genis Message-ID: Date: Thu, 26 Jan 2017 17:45:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:XuNhraaRCZF40zeeUQPGDPkIfV+d9AvqQ7MJr3tjPS6MZ1b5Lte n6mWBP0RiYJx5bJ5L+7Kc7DXjavLR7gl6sHPlj/DgJy2ZOjnSAB3wyyDPhtl6kw9JsnBoI9 zCf0C+gQS/+P+Bj1/VaZHpfFiqDe9GGiAV00D0BZswAszObBQj6pOLDp9RmoBRNgrT+hqGp a/v0fbtXRfoZmLQNqv0Ng== X-UI-Out-Filterresults: notjunk:1;V01:K0:rUoj9PlCqZg=:DZZvHokQuTMk/cpEBU6M7W 7DfUQkAdP0iPGklmQ4Yz84bRai4hCKdRmrsfg/pm06Tq9Aj0gVhk4QR9FpJpmAbVvbGs6gpRI fEiJC5ucUJHd5DD0iWpi3Bn1QuBmDp3vKEwo9RVvcrKbfnGOfduiyOhpGTdOy6ILRKvF9Ks7o G/u4DxkeGGtr2agJo01bZzZi4aaDciuseeQiY4IzfgTh37fBxsFJ6mMhmL6Gd4KTlk2hIH8C2 DGw4CHza3poyKO3wvvClbR1RnMd5IF5DbgChgpC8p2VR44P1tQieFw9cD9Y7iU/DYnw+V5Ebb TadouaUnx5gzL/SAmRD/TlPcEMwmLIPgvxL/VKNQZptYK4eYN/ihMGSwm+MSu1PUBAv/Rm4/V bvY6G6U9L6TqarMSNWOvjU0VZW6OTTjpVZArgjZfaonPkTAxegfV5RCdLb3N5gdVVvWaX+ik8 fQgt/+J/qcT2w+sSNy3o5O7w2/SpLaGQFKHcycyj/kZyvhyZe2dQ0bQ3yvOnEY148PaC0uLKc cpW0i9cuHUU3iNLgCgIJHpz1RzPsqu0dr3g9Y0Z4ufAGcCX7hcXTIZKYiyIQuW38EJchSY2SF KxL5gRe1uw3C4CbI5fLQFeCgVWob+XJfOoOK7mvnZy4rFj7xXRihotKMAApZ6U2oLp39oqjDq dzTggf8Lx5ix6C6GH8tYFZQnuqtzBu1znBZumQ9BvZAOuMOPe0cV4qN0Zpjv66L7uePwO4O3c WoRb6cfelswzxkMHx4fgJ8DL3Kik4KHK8bIKK7tqp/mffJiv8KHn9SNMNPMakrSgE4236cmXh sW8Yk3S X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 16:51:10 -0000 Hi Eric and Todd, Thanks for your answers. I will try the linux boot, that's an excellent suggestion! I will file a bugreport once I have a bit more info. The issue sounds very similar compared to the Re: [E1000-devel] X550EM_X_SFP "lockup" / link issues in this thread. The problem is not always present and I'm unable to trigger it manually. Which makes it tough to debug :-) Slowly but surely I'm getting closer to triaging the bug. It sounds ooh so erily similar to the "lockup" issue Sylvain is describing. Next week we'll empty a machine which is in this "state", then I have another test machine to play with. For the record, we have multiple link partners (2 juniper models, and one Huawei model). I've seen this issue with all link partners. Maybe never had this issue on 10.1/10.2-STABLE because those kernels never panicked on us. With kind regards, Daniel On 01/24/2017 06:57 PM, Eric Joyner wrote: > On Tue, Jan 10, 2017 at 2:38 AM Daniel Genis wrote: > >> Hello everyone, >> >> we're trying to tackle a rare bug that is very hard to debug. >> >> Our 10.3-RELEASE servers can panic boot and subsequently can come up >> without network (2x - no carrier). We've seen this on 10.3-RELEASE-p0 we >> have never seen this before. >> >> root@storage ~ # pciconf -lv | grep -B3 network >> ix0@pci0:2:0:0: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' >> class = network >> -- >> ix1@pci0:2:0:1: class=0x020000 card=0xd10f19e5 chip=0x10fb8086 >> rev=0x01 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82599ES 10-Gigabit SFI/SFP+ Network Connection' >> class = network >> >> Our network is configured as active/passive using lagg. (/etc/rc.conf): >> >> ifconfig_ix0="up" >> ifconfig_ix1="up" >> cloned_interfaces="lagg0" >> ifconfig_lagg0="laggproto failover laggport ix0 laggport ix1 10.1.2.31/16" >> >> After panic boot the network show up like this: >> >> ix0: flags=8843 metric 0 mtu 1500 >> >> options=8407bb >> ether 60:08:10:d0:4e:9f >> nd6 options=29 >> media: (autoselect) >> status: no carrier >> ix1: flags=8843 metric 0 mtu 1500 >> >> options=8407bb >> ether 60:08:10:d0:4e:9f >> nd6 options=29 >> media: (autoselect) >> status: no carrier >> >> The network switch sees the connection as online. The LED's of the nic's >> suggest the same, they see the network as online (led's are on like in >> normal operation). Unplugging/replugging the network cable will get the >> network online. Shutting the port on the switch and reenabling it wil >> also get the network online. However another reboot will return the >> machine into the no-carrier state. >> >> I've built various kernels trying to find where the regression is >> without success. I tried porting the 10.2 nic driver (2.8.3) to 10.3 and >> subsequently the lagg code as well. I ported nic driver 3.1.14 from >> pfsense into 10.3-STABLE (2 december kernel) to no avail, also porting >> lagg code from 10.2 did not make any difference. Rebooting with those >> kernels the server remains in the no carrier state. >> >> We install our systems using mfsbsd for PXE boot. If I boot a machine >> which has the "no carrier" state using the 10.3 PXE boot, both nic's >> come online. If I then boot from disk again the machine returns into the >> "no carrier" state. >> >> Recently we got some new machines, so we can shuffle more around and >> also to try to debug this. We baseinstalled it using mfsbsd 10.3 pxe and >> configured it like always. Here interestingly one of the two nic's >> entered the "no carrier" state, the other nic remained operational. This >> remained persistent across reboots. >> >> The issue disappears after many reboots but it's not conclusive. I've >> had 2 machines with which I could experiment with. >> >> On one the problem it disappeared on it's own after a reboot (kernel >> 10.3-STABLE git hash d99ba5c aka r299900(?)). >> >> On the other one I pxe booted 10.1 live environment and then >> subsequently I booted into kernel 10.3-STABLE git hash 3673260fc9 aka >> r308456(?)). But I don't think anything can be concluded from that. That >> was the machine which had both nic's online after booting into the 10.3 >> pxe environment but subsequently returned into no carrier state when >> booting 10.3 from disk. >> >> We also tried many sysctl flags (and many reboots), but without success. >> For example: hw.ix.enable_msix=0 and hw.ix.enable_msi=0 >> >> At the moment I have no spare/empty machine in this state, we will empty >> one machine though which currently has this state (but is in production >> right now). >> I don't know how to trigger this state manually, which doesn't help for >> debugging. >> >> I could link reference where others report similar issues, for example >> https://www.reddit.com/r/PFSENSE/comments/45bcuq/10_gig_woes/ >> Here they suggest that the new intel nic driver 3.1.14 fixes it. Though >> I was not able to resolve the state by booting into a kernel with this >> driver. >> >> If I can provide any additional information please do not hesitate to ask. >> >> Any tips and suggestions for debugging are most welcome! >> >> With kind regards, >> >> Daniel >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > This is a late follow-up, but could you file this as a bug on > bugs.freebsd.org? > > - Eric > From owner-freebsd-stable@freebsd.org Thu Jan 26 17:38:23 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B829BCC221E for ; Thu, 26 Jan 2017 17:38:23 +0000 (UTC) (envelope-from bounce@ims7.isendservice.com.br) Received: from ims7.isendservice.com.br (ims7.isendservice.com.br [54.232.187.223]) by mx1.freebsd.org (Postfix) with ESMTP id 333DBC10 for ; Thu, 26 Jan 2017 17:38:23 +0000 (UTC) (envelope-from bounce@ims7.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims7.isendservice.com.br (Postfix) with ESMTP id 0F92D43785 for ; Thu, 26 Jan 2017 15:04:46 -0200 (BRST) Date: Thu, 26 Jan 2017 15:04:46 -0200 (BRST) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: faculdadesenai@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <2068063897.199913.1485450286016.JavaMail.root@ims7> Subject: =?ISO-8859-1?Q?Vestibular_SENAI_2017/1_-_Oportunidade_de_50%_de?= =?ISO-8859-1?Q?_desconto_no_1=BA_semestre_para_alunos_tranferidos?= bounce-key: <2420-22522874-1612456> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 17:38:23 -0000 From owner-freebsd-stable@freebsd.org Thu Jan 26 22:50:20 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAB93CC3EFC; Thu, 26 Jan 2017 22:50:20 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv72.fwdcdn.com (frv72.fwdcdn.com [212.42.77.72]) by mx1.freebsd.org (Postfix) with ESMTP id 76857233; Thu, 26 Jan 2017 22:50:20 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from [10.10.17.71] (helo=frv156.fwdcdn.com) by frv72.fwdcdn.com QID:1cWsbd-000K3l-SH/RC:2; Fri, 27 Jan 2017 00:33:26 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; 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=K2rwyOMecf+QpAdX2Bg7kQ223Fu005zT9Y/gh5M8g7g=; b=kfo62mQs9e3UQfR116L3lPG9H6 ayLUWdC1Au27+2jrUoYoC+ezFsv1SB7VonpnsGJ6TPueurxjNh9Z5dnrhC4e93Ka8w1LaMvN7Cscj nLlP2I1RcfgnPaqYOkoLSKTKCgd6nX82UO7jVRZG8C2HoAcOi6O6KJYNZ03EHngHfCAY=; Received: from [46.119.57.93] (helo=nonamehost) by frv156.fwdcdn.com with esmtpsa ID 1cWsbO-0005hs-Md ; Fri, 27 Jan 2017 00:33:10 +0200 Date: Fri, 27 Jan 2017 00:33:10 +0200 From: Ivan Klymenko To: hiren panchasara Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127003310.15c5a828@nonamehost> In-Reply-To: <20161228175729.GC17818@strugglingcoder.info> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 22:50:20 -0000 On Wed, 28 Dec 2016 09:57:29 -0800 hiren panchasara wrote: > On 12/28/16 at 07:53P, Ivan Klymenko wrote: > > On Wed, 28 Dec 2016 09:41:42 -0800 > > hiren panchasara wrote: > > > > > Can you open a bug report at https://bugs.freebsd.org/bugzilla/ > > > with necessary details? Looks like virtualbox is involved here? > > > > I can not, because that does not make sense. > > PR are not considered for months and years. > > It was the last hope for the mail lists. > > Probably i must to change the operating system. > > Apologies for that. As you know people get busy in such opensource > projects. > > The panic appears in tcp land so if you provide enough information, > I'll try to look at it. Again, I cannot promise anything more than an > honest attempt. > > Cheers, > Hiren The reason most panics served as tuning Netisr: net.isr.numthreads=4 net.isr.maxthreads=4 net.isr.bindthreads=1 Apparently, this subsystem at some moment had been broken. Best regards, From owner-freebsd-stable@freebsd.org Fri Jan 27 05:38:01 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38D7ECC3252 for ; Fri, 27 Jan 2017 05:38:01 +0000 (UTC) (envelope-from mail@fbsd.e4m.org) Received: from mail.g66.org (mail.g66.org [85.10.206.112]) by mx1.freebsd.org (Postfix) with ESMTP id D292C134A for ; Fri, 27 Jan 2017 05:37:59 +0000 (UTC) (envelope-from mail@fbsd.e4m.org) Received: from x55b58e4e.dyn.telefonica.de (x55b58e4e.dyn.telefonica.de [85.181.142.78]) (authenticated bits=128) by mail.g66.org (8.15.2/8.15.2) with ESMTPA id v0R5bouQ010947 for ; Fri, 27 Jan 2017 06:37:51 +0100 (CET) (envelope-from mail@fbsd.e4m.org) Received: from submit.client ([127.0.0.1]) by gate.local (8.15.2/8.15.2) with ESMTP id v0R5boi3010043; Fri, 27 Jan 2017 06:37:50 +0100 (CET) (envelope-from mail@fbsd.e4m.org) Received: (from user@localhost) by gate.local (8.15.2/8.15.2/Submit) id v0R5borJ010042; Fri, 27 Jan 2017 06:37:50 +0100 (CET) (envelope-from mail@fbsd.e4m.org) Date: Fri, 27 Jan 2017 06:37:50 +0100 From: Andre Albsmeier To: freebsd-stable@freebsd.org Cc: mail@fbsd.e4m.org Subject: kernel build error on STABLE-11 with bktr Message-ID: <20170127053750.GA9908@gate> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) X-Virus-Scanned: clamav-milter 0.99.2 at colo X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 05:38:01 -0000 Is it just me seeing this or does nobody else use bktr compiled into the kernel anymore: ... cc -target i386-unknown-freebsd11.0 --sysroot=/usr/obj/src/src-11/tmp -B/usr/obj/src/src-11/tmp/usr/bin -c -O -pipe -march=pentium3 -g -nostdinc -I. -I/src/src-11/sys -I/src/src-11/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -march=core2 -fno-ident -MD -MF.depend.msp34xx.o -MTmsp34xx.o -mno-mmx -mno-sse -msoft-float -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -mno-aes -mno-avx -std=iso9899:1999 -Werror /src/src-11/sys/dev/bktr/msp34xx.c /src/src-11/sys/dev/bktr/msp34xx.c:112:18: error: unused variable 'bl_dfp' [-Werror,-Wunused-const-variable] static const int bl_dfp[] = { ^ Removing the bl_dfp definition fixes it... -Andre From owner-freebsd-stable@freebsd.org Fri Jan 27 10:47:41 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0B6DCC4A16; Fri, 27 Jan 2017 10:47:41 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward2m.cmail.yandex.net (forward2m.cmail.yandex.net [5.255.216.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6FB82FAD; Fri, 27 Jan 2017 10:47:41 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [95.108.130.59]) by forward2m.cmail.yandex.net (Yandex) with ESMTP id 27839218B5; Fri, 27 Jan 2017 13:47:37 +0300 (MSK) Received: from smtp1j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1j.mail.yandex.net (Yandex) with ESMTP id F39A53C81415; Fri, 27 Jan 2017 13:47:34 +0300 (MSK) Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id CV6ORWtxRJ-lXq4toUg; Fri, 27 Jan 2017 13:47:33 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1485514054; bh=W1RxltENrwvul06MuI+Z3Yw4vIcV4GdgTH9Rnp2RrB0=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=Q7m/mCSGla0Grmazeta/GW62E4w5HjFQJEh1AiJjVPWy30rmswa3LqHlpv0awNale U+G1qTZ9HJfqfbgMHXHrovG62LcdzpiwCy8F+Mu4gFIK4IBr+osoBYaEf7nHGneFyY L3rYnPx6NmDGQVD5W6WXAulrlo4i6U5i/G6lpSxo= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE To: Ivan Klymenko , hiren panchasara References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org From: "Andrey V. Elsukov" Message-ID: <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> Date: Fri, 27 Jan 2017 13:46:30 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170127003310.15c5a828@nonamehost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 10:47:41 -0000 On 27.01.2017 01:33, Ivan Klymenko wrote: > The reason most panics served as tuning Netisr: > net.isr.numthreads=4 > net.isr.maxthreads=4 > net.isr.bindthreads=1 > > Apparently, this subsystem at some moment had been broken. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836 -- WBR, Andrey V. Elsukov From owner-freebsd-stable@freebsd.org Fri Jan 27 11:59:20 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06F34CC2121; Fri, 27 Jan 2017 11:59:20 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv72.fwdcdn.com (frv72.fwdcdn.com [212.42.77.72]) by mx1.freebsd.org (Postfix) with ESMTP id A997E33A; Fri, 27 Jan 2017 11:59:18 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from [10.10.17.73] (helo=frv158.fwdcdn.com) by frv72.fwdcdn.com QID:1cX5BU-0005hv-Sk/RC:2; Fri, 27 Jan 2017 13:59:16 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; 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=FiMAszI8fz99LT9iO/CRGfwLoIvZIVjDYm904CVX0oU=; b=YxG9nYfMxnVKjeQXsKtZmKdrSu SsflZ7To9R7WvydOY8mjfwUGvughQAgi0RvxXuaW/4SaUSzfSqiwE4biFufjn2j2nvXpjXryp/5oe K+UC5BmNfAv+kkxckRbLuQs9yk8Zq4AzEPgjJWZ6jwUgroFtzr9Chncdg7l9qag3fIbQ=; Received: from [46.119.57.93] (helo=nonamehost) by frv158.fwdcdn.com with esmtpsa ID 1cX5BD-000Fr0-Nz ; Fri, 27 Jan 2017 13:58:59 +0200 Date: Fri, 27 Jan 2017 13:58:59 +0200 From: Ivan Klymenko To: "Andrey V. Elsukov" Cc: hiren panchasara , freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127135859.30628eb7@nonamehost> In-Reply-To: <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 11:59:20 -0000 On Fri, 27 Jan 2017 13:46:30 +0300 "Andrey V. Elsukov" wrote: > On 27.01.2017 01:33, Ivan Klymenko wrote: > > The reason most panics served as tuning Netisr: > > net.isr.numthreads=4 > > net.isr.maxthreads=4 > > net.isr.bindthreads=1 > > > > Apparently, this subsystem at some moment had been broken. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836 > Yes you are right. But the problem still remains unsolved. I just removed these settings. From owner-freebsd-stable@freebsd.org Fri Jan 27 12:02:23 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 985EDCC2E17; Fri, 27 Jan 2017 12:02:23 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 12A44E0B; Fri, 27 Jan 2017 12:02:21 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE To: Ivan Klymenko References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> <20170127135859.30628eb7@nonamehost> Cc: hiren panchasara , freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, Adrian Chadd From: "Andrey V. Elsukov" Message-ID: <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> Date: Fri, 27 Jan 2017 15:01:18 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170127135859.30628eb7@nonamehost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 12:02:23 -0000 On 27.01.2017 14:58, Ivan Klymenko wrote: > On Fri, 27 Jan 2017 13:46:30 +0300 > "Andrey V. Elsukov" wrote: > >> On 27.01.2017 01:33, Ivan Klymenko wrote: >>> The reason most panics served as tuning Netisr: >>> net.isr.numthreads=4 >>> net.isr.maxthreads=4 >>> net.isr.bindthreads=1 >>> >>> Apparently, this subsystem at some moment had been broken. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836 >> > > Yes you are right. > But the problem still remains unsolved. > > I just removed these settings. I didn't done the merge of the patch into stable/11 and releng/11.0, because Adrian said it is not good enough and he will rework it better :) -- WBR, Andrey V. Elsukov From owner-freebsd-stable@freebsd.org Fri Jan 27 12:11:01 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9730CC1126; Fri, 27 Jan 2017 12:11:01 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv156.fwdcdn.com (frv156.fwdcdn.com [212.42.77.156]) (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 90593146; Fri, 27 Jan 2017 12:11:01 +0000 (UTC) (envelope-from fidaj@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; 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=4YuDUPn4Rs8SLDAJhO6Ia/F6tPcBdNoCkCMcMcZDPZg=; b=OppOJ52f5Pg+C98vNtHMTSHzWo iUnGZTzhzu8oLb6oOpCuhhEV1mMzfgjfHbt7b0DMOVshAu5bqEFFx5GF18vcZsADScedLbDvlBMRy jqzvJttybo6HP0izp8RF6eU1r8tb/t8OBH+lzxufytzM2fZqahJ8q+ocfr6yEm0S1+nY=; Received: from [46.119.57.93] (helo=nonamehost) by frv156.fwdcdn.com with esmtpsa ID 1cX5Mp-000GNh-05 ; Fri, 27 Jan 2017 14:10:59 +0200 Date: Fri, 27 Jan 2017 14:10:58 +0200 From: Ivan Klymenko To: "Andrey V. Elsukov" Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, hiren panchasara , Adrian Chadd Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127141058.5afd80c5@nonamehost> In-Reply-To: <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> <20170127135859.30628eb7@nonamehost> <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 12:11:02 -0000 On Fri, 27 Jan 2017 15:01:18 +0300 "Andrey V. Elsukov" wrote: > On 27.01.2017 14:58, Ivan Klymenko wrote: > > On Fri, 27 Jan 2017 13:46:30 +0300 > > "Andrey V. Elsukov" wrote: > > > >> On 27.01.2017 01:33, Ivan Klymenko wrote: > >>> The reason most panics served as tuning Netisr: > >>> net.isr.numthreads=4 > >>> net.isr.maxthreads=4 > >>> net.isr.bindthreads=1 > >>> > >>> Apparently, this subsystem at some moment had been broken. > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836 > >> > > > > Yes you are right. > > But the problem still remains unsolved. > > > > I just removed these settings. > > I didn't done the merge of the patch into stable/11 and releng/11.0, > because Adrian said it is not good enough and he will rework it > better :) > Thank you for your hard work and efforts. From owner-freebsd-stable@freebsd.org Fri Jan 27 12:26:42 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F5ADCC1918 for ; Fri, 27 Jan 2017 12:26:42 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from lamora.getmail.no (lamora.getmail.no [84.210.184.7]) by mx1.freebsd.org (Postfix) with ESMTP id 10B03BD2 for ; Fri, 27 Jan 2017 12:26:41 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id 35A9A108F76 for ; Fri, 27 Jan 2017 13:20:13 +0100 (CET) Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id XEkpnfIhbqDB for ; Fri, 27 Jan 2017 13:20:12 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id B4F27106E8E for ; Fri, 27 Jan 2017 13:20:12 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.9.2 lamora.getmail.no B4F27106E8E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1485519612; bh=2OMoprVNi4qY/MwOR30HcpP3s/pIwLwKQZo/zu+UFHQ=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=3Cz64WtTQDD1mCtN3mXYMh+J0IqyoGjbCWt8Y2ibEVKJRARv/hxwm6IawIhGuDSG7 Xkjw9ligtGNc6OMVWQpq1pZEDs7pLDw+Ht4mjL4cOKm3oYR0X29d79/5FZS5+Mc86D x4dkeiANEi9QYdpf1Xu8PFb/vF1DL3nE8d02cjPU= X-Virus-Scanned: amavisd-new at lamora.get.c.bitbit.net Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YvKRJ3nG87da for ; Fri, 27 Jan 2017 13:20:12 +0100 (CET) Received: from kg-core1.kg4.no (cm-84.209.39.108.getinternet.no [84.209.39.108]) by lamora.getmail.no (Postfix) with ESMTPSA id 698F110907A for ; Fri, 27 Jan 2017 13:20:12 +0100 (CET) Date: Fri, 27 Jan 2017 13:20:10 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-Id: <20170127132010.57598b5780d071688c42f656@getmail.no> In-Reply-To: <58887CF7.1010908@norma.perm.ru> References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> <58887CF7.1010908@norma.perm.ru> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 12:26:42 -0000 On Wed, 25 Jan 2017 15:24:55 +0500 "Eugene M. Zheganin" wrote: > I'm seeing all of these in my konsole terminal window while working with Does it also happen if you use another terminal emulator insted of konsole? -- Torfinn Ingolfsen From owner-freebsd-stable@freebsd.org Fri Jan 27 14:42:06 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F40ECC3E28; Fri, 27 Jan 2017 14:42:06 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv158.fwdcdn.com (frv158.fwdcdn.com [212.42.77.158]) (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 077F01CAE; Fri, 27 Jan 2017 14:42:05 +0000 (UTC) (envelope-from fidaj@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; 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=J/10wKDYeXAIn8KbyGvfkSlYWPmBSoF43+J7hhl7C+0=; b=Z81R6xLUOJjS9G0n1LDWpAWXff nROF7YzZd03xBtJ4UiqcCbbDCtrfZEhoqVUpUcFrRBsmLei0J6rI853VUJYcUzcn+DBJhv5PHZiM+ kWmX29OiKdh8bACicEmBtAedMHHlvNN5cEx2P6Ok5oZ1tu/DHLQNn3KHJQOMGv0C63ro=; Received: from [46.119.57.93] (helo=nonamehost) by frv158.fwdcdn.com with esmtpsa ID 1cX7iy-000BqX-Rs ; Fri, 27 Jan 2017 16:42:00 +0200 Date: Fri, 27 Jan 2017 16:41:59 +0200 From: Ivan Klymenko To: "Andrey V. Elsukov" Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, hiren panchasara , Adrian Chadd Subject: Re: panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127164159.772de4f2@nonamehost> In-Reply-To: <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> <20170127135859.30628eb7@nonamehost> <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 14:42:06 -0000 On Fri, 27 Jan 2017 15:01:18 +0300 "Andrey V. Elsukov" wrote: > On 27.01.2017 14:58, Ivan Klymenko wrote: > > On Fri, 27 Jan 2017 13:46:30 +0300 > > "Andrey V. Elsukov" wrote: > > > >> On 27.01.2017 01:33, Ivan Klymenko wrote: > >>> The reason most panics served as tuning Netisr: > >>> net.isr.numthreads=4 > >>> net.isr.maxthreads=4 > >>> net.isr.bindthreads=1 > >>> > >>> Apparently, this subsystem at some moment had been broken. > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836 > >> > > > > Yes you are right. > > But the problem still remains unsolved. > > > > I just removed these settings. > > I didn't done the merge of the patch into stable/11 and releng/11.0, > because Adrian said it is not good enough and he will rework it > better :) > Jan 27 16:17:07 ns kernel: Fatal trap 12: page fault while in kernel mode Jan 27 16:17:07 ns kernel: cpuid = 2; apic id = 02 Jan 27 16:17:07 ns kernel: fault virtual address = 0x8 Jan 27 16:17:07 ns kernel: fault code = supervisor read data, page not present Jan 27 16:17:07 ns kernel: instruction pointer = 0x20:0xffffffff80b8e170 Jan 27 16:17:07 ns kernel: stack pointer = 0x28:0xfffffe083b7fc550 Jan 27 16:17:07 ns kernel: frame pointer = 0x28:0xfffffe083b7fc580 Jan 27 16:17:07 ns kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jan 27 16:17:07 ns kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Jan 27 16:17:07 ns kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jan 27 16:17:07 ns kernel: current process = 12 (swi5: fast taskq) Jan 27 16:17:07 ns kernel: trap number = 12 Jan 27 16:17:07 ns kernel: panic: page fault Jan 27 16:17:07 ns kernel: cpuid = 2 Jan 27 16:17:07 ns kernel: KDB: stack backtrace: Jan 27 16:17:07 ns kernel: #0 0xffffffff80b3ec47 at kdb_backtrace+0x67 Jan 27 16:17:07 ns kernel: #1 0xffffffff80af3a46 at vpanic+0x186 Jan 27 16:17:07 ns kernel: #2 0xffffffff80af38b3 at panic+0x43 Jan 27 16:17:07 ns kernel: #3 0xffffffff8102de30 at trap_fatal+0x320 Jan 27 16:17:07 ns kernel: #4 0xffffffff8102dffc at trap_pfault+0x1bc Jan 27 16:17:07 ns kernel: #5 0xffffffff8102d6ab at trap+0x27b Jan 27 16:17:07 ns kernel: #6 0xffffffff8100fd81 at calltrap+0x8 Jan 27 16:17:07 ns kernel: #7 0xffffffff80d2ec9e at tcp_do_segment+0x12ae Jan 27 16:17:07 ns kernel: #8 0xffffffff80d2d282 at tcp_input+0x14d2 Jan 27 16:17:07 ns kernel: #9 0xffffffff80c94402 at ip_input+0x192 Jan 27 16:17:07 ns kernel: #10 0xffffffff80c2a58d at netisr_dispatch_src+0xad Jan 27 16:17:07 ns kernel: #11 0xffffffff80c12589 at ether_demux+0x149 Jan 27 16:17:07 ns kernel: #12 0xffffffff82b6971c at vboxNetFltFreeBSDinput+0x27c Jan 27 16:17:07 ns kernel: #13 0xffffffff80b520da at taskqueue_run_locked+0x14a Jan 27 16:17:07 ns kernel: #14 0xffffffff80b51ecf at taskqueue_run+0xbf Jan 27 16:17:07 ns kernel: #15 0xffffffff80aad3cf at intr_event_execute_handlers+0x20f Jan 27 16:17:07 ns kernel: #16 0xffffffff80aad636 at ithread_loop+0xc6 Jan 27 16:17:07 ns kernel: #17 0xffffffff80aa9e75 at fork_exit+0x85 Jan 27 16:17:07 ns kernel: Uptime: 16h19m23s Jan 27 16:17:07 ns kernel: Dumping 7744 out of 32688 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Alas - I was wrong. The problem remains urgent. The panic occurs when a network owncloud service activity in a jail. I will write again: this problem appears while using jails and VirtualBox. With switched off the jails - the problem is not reproduced. I am looking forward the merge of the patch into stable/11 and releng/11.0. This is a critical issue for me. From owner-freebsd-stable@freebsd.org Fri Jan 27 16:17:09 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4CF0CC494C; Fri, 27 Jan 2017 16:17:09 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 39E43BBA; Fri, 27 Jan 2017 16:17:07 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE To: Ivan Klymenko References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> <20170127135859.30628eb7@nonamehost> <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> <20170127164159.772de4f2@nonamehost> Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, hiren panchasara , Adrian Chadd From: "Andrey V. Elsukov" Message-ID: <3be020a7-b68e-ad69-78b2-e16c3d6286ae@FreeBSD.org> Date: Fri, 27 Jan 2017 19:16:04 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170127164159.772de4f2@nonamehost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 16:17:10 -0000 On 27.01.2017 17:41, Ivan Klymenko wrote: >> I didn't done the merge of the patch into stable/11 and releng/11.0, >> because Adrian said it is not good enough and he will rework it >> better :) >> > > > Jan 27 16:17:07 ns kernel: Fatal trap 12: page fault while in kernel mode > Jan 27 16:17:07 ns kernel: cpuid = 2; apic id = 02 > Jan 27 16:17:07 ns kernel: fault virtual address = 0x8 > Jan 27 16:17:07 ns kernel: fault code = supervisor read data, page not present > Jan 27 16:17:07 ns kernel: instruction pointer = 0x20:0xffffffff80b8e170 > Jan 27 16:17:07 ns kernel: stack pointer = 0x28:0xfffffe083b7fc550 > Jan 27 16:17:07 ns kernel: frame pointer = 0x28:0xfffffe083b7fc580 > Jan 27 16:17:07 ns kernel: code segment = base 0x0, limit 0xfffff, type 0x1b > Jan 27 16:17:07 ns kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > Jan 27 16:17:07 ns kernel: processor eflags = interrupt enabled, resume, IOPL = 0 > Jan 27 16:17:07 ns kernel: current process = 12 (swi5: fast taskq) > Jan 27 16:17:07 ns kernel: trap number = 12 > Jan 27 16:17:07 ns kernel: panic: page fault > Jan 27 16:17:07 ns kernel: cpuid = 2 > Jan 27 16:17:07 ns kernel: KDB: stack backtrace: > Jan 27 16:17:07 ns kernel: #0 0xffffffff80b3ec47 at kdb_backtrace+0x67 > Jan 27 16:17:07 ns kernel: #1 0xffffffff80af3a46 at vpanic+0x186 > Jan 27 16:17:07 ns kernel: #2 0xffffffff80af38b3 at panic+0x43 > Jan 27 16:17:07 ns kernel: #3 0xffffffff8102de30 at trap_fatal+0x320 > Jan 27 16:17:07 ns kernel: #4 0xffffffff8102dffc at trap_pfault+0x1bc > Jan 27 16:17:07 ns kernel: #5 0xffffffff8102d6ab at trap+0x27b > Jan 27 16:17:07 ns kernel: #6 0xffffffff8100fd81 at calltrap+0x8 > Jan 27 16:17:07 ns kernel: #7 0xffffffff80d2ec9e at tcp_do_segment+0x12ae > Jan 27 16:17:07 ns kernel: #8 0xffffffff80d2d282 at tcp_input+0x14d2 > Jan 27 16:17:07 ns kernel: #9 0xffffffff80c94402 at ip_input+0x192 > Jan 27 16:17:07 ns kernel: #10 0xffffffff80c2a58d at netisr_dispatch_src+0xad > Jan 27 16:17:07 ns kernel: #11 0xffffffff80c12589 at ether_demux+0x149 > Jan 27 16:17:07 ns kernel: #12 0xffffffff82b6971c at vboxNetFltFreeBSDinput+0x27c > Jan 27 16:17:07 ns kernel: #13 0xffffffff80b520da at taskqueue_run_locked+0x14a > Jan 27 16:17:07 ns kernel: #14 0xffffffff80b51ecf at taskqueue_run+0xbf > Jan 27 16:17:07 ns kernel: #15 0xffffffff80aad3cf at intr_event_execute_handlers+0x20f > Jan 27 16:17:07 ns kernel: #16 0xffffffff80aad636 at ithread_loop+0xc6 > Jan 27 16:17:07 ns kernel: #17 0xffffffff80aa9e75 at fork_exit+0x85 > Jan 27 16:17:07 ns kernel: Uptime: 16h19m23s > Jan 27 16:17:07 ns kernel: Dumping 7744 out of 32688 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > > Alas - I was wrong. > The problem remains urgent. > > The panic occurs when a network owncloud service activity in a jail. > I will write again: this problem appears while using jails and VirtualBox. > With switched off the jails - the problem is not reproduced. > > I am looking forward the merge of the patch into stable/11 and releng/11.0. > > This is a critical issue for me. The panic in PR 211836 is in the netisr code, and they are depend from the number of configured netisr threads. Your panics looks different and it seems unrelated. It would be good if you fill the PR with the details (backtraces from core.txt.N, how your kernel differs from the GENERIC, what kernel modules you have loaded, etc). -- WBR, Andrey V. Elsukov From owner-freebsd-stable@freebsd.org Fri Jan 27 16:40:39 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6C6ACC4E17; Fri, 27 Jan 2017 16:40:39 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv72.fwdcdn.com (frv72.fwdcdn.com [212.42.77.72]) by mx1.freebsd.org (Postfix) with ESMTP id 7F6DB878; Fri, 27 Jan 2017 16:40:38 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv157.fwdcdn.com ([212.42.77.157]) by frv72.fwdcdn.com QID:1cX9Zl-000K81-15/RC:4; Fri, 27 Jan 2017 18:40:37 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; 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=gB52JZYPjIY5bPJz4K0j9O8Xc/dSxwBUBz+aPdFdkqA=; b=FtbnjgVLzJjIN/MSoldPm+aGJj KBYJRMiAuQ+RGFKCUly1d2GxK07mtj4hrY1XF1aYKtb0Fqy0jSa3H3VIGPJMks194NvQWhv4BqVcv 1f8XHGZ/on9Q23bwaZJspAOTUNMgZ4TvrqtJovrz0yMYI2Zzph6EaEqgVVpoFWI4FMPE=; Received: from [46.119.57.93] (helo=nonamehost) by frv157.fwdcdn.com with esmtpsa ID 1cX9ZU-000IkO-Rb ; Fri, 27 Jan 2017 18:40:20 +0200 Date: Fri, 27 Jan 2017 18:40:20 +0200 From: Ivan Klymenko To: "Andrey V. Elsukov" Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, hiren panchasara , Adrian Chadd Subject: Re: panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127184020.6c730b8e@nonamehost> In-Reply-To: <3be020a7-b68e-ad69-78b2-e16c3d6286ae@FreeBSD.org> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> <478d912c-b9ed-44e0-6afb-c3f30cefec6b@yandex.ru> <20170127135859.30628eb7@nonamehost> <1e7898cf-a746-4289-74a2-fd9571387ca0@FreeBSD.org> <20170127164159.772de4f2@nonamehost> <3be020a7-b68e-ad69-78b2-e16c3d6286ae@FreeBSD.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2017 16:40:39 -0000 On Fri, 27 Jan 2017 19:16:04 +0300 "Andrey V. Elsukov" wrote: > On 27.01.2017 17:41, Ivan Klymenko wrote: > >> I didn't done the merge of the patch into stable/11 and > >> releng/11.0, because Adrian said it is not good enough and he will > >> rework it better :) > >> > > > > > > Jan 27 16:17:07 ns kernel: Fatal trap 12: page fault while in > > kernel mode Jan 27 16:17:07 ns kernel: cpuid = 2; apic id = 02 > > Jan 27 16:17:07 ns kernel: fault virtual address = 0x8 > > Jan 27 16:17:07 ns kernel: fault code = supervisor read > > data, page not present Jan 27 16:17:07 ns kernel: instruction > > pointer = 0x20:0xffffffff80b8e170 Jan 27 16:17:07 ns kernel: stack > > pointer = 0x28:0xfffffe083b7fc550 Jan 27 16:17:07 ns > > kernel: frame pointer = 0x28:0xfffffe083b7fc580 Jan > > 27 16:17:07 ns kernel: code segment = base 0x0, limit > > 0xfffff, type 0x1b Jan 27 16:17:07 ns kernel: = DPL 0, pres 1, long > > 1, def32 0, gran 1 Jan 27 16:17:07 ns kernel: processor eflags > > = interrupt enabled, resume, IOPL = 0 Jan 27 16:17:07 ns kernel: > > current process = 12 (swi5: fast taskq) Jan 27 > > 16:17:07 ns kernel: trap number = 12 Jan 27 16:17:07 ns > > kernel: panic: page fault Jan 27 16:17:07 ns kernel: cpuid = 2 Jan > > 27 16:17:07 ns kernel: KDB: stack backtrace: Jan 27 16:17:07 ns > > kernel: #0 0xffffffff80b3ec47 at kdb_backtrace+0x67 Jan 27 16:17:07 > > ns kernel: #1 0xffffffff80af3a46 at vpanic+0x186 Jan 27 16:17:07 ns > > kernel: #2 0xffffffff80af38b3 at panic+0x43 Jan 27 16:17:07 ns > > kernel: #3 0xffffffff8102de30 at trap_fatal+0x320 Jan 27 16:17:07 > > ns kernel: #4 0xffffffff8102dffc at trap_pfault+0x1bc Jan 27 > > 16:17:07 ns kernel: #5 0xffffffff8102d6ab at trap+0x27b Jan 27 > > 16:17:07 ns kernel: #6 0xffffffff8100fd81 at calltrap+0x8 Jan 27 > > 16:17:07 ns kernel: #7 0xffffffff80d2ec9e at tcp_do_segment+0x12ae > > Jan 27 16:17:07 ns kernel: #8 0xffffffff80d2d282 at > > tcp_input+0x14d2 Jan 27 16:17:07 ns kernel: #9 0xffffffff80c94402 > > at ip_input+0x192 Jan 27 16:17:07 ns kernel: #10 0xffffffff80c2a58d > > at netisr_dispatch_src+0xad Jan 27 16:17:07 ns kernel: #11 > > 0xffffffff80c12589 at ether_demux+0x149 Jan 27 16:17:07 ns kernel: > > #12 0xffffffff82b6971c at vboxNetFltFreeBSDinput+0x27c Jan 27 > > 16:17:07 ns kernel: #13 0xffffffff80b520da at > > taskqueue_run_locked+0x14a Jan 27 16:17:07 ns kernel: #14 > > 0xffffffff80b51ecf at taskqueue_run+0xbf Jan 27 16:17:07 ns kernel: > > #15 0xffffffff80aad3cf at intr_event_execute_handlers+0x20f Jan 27 > > 16:17:07 ns kernel: #16 0xffffffff80aad636 at ithread_loop+0xc6 Jan > > 27 16:17:07 ns kernel: #17 0xffffffff80aa9e75 at fork_exit+0x85 Jan > > 27 16:17:07 ns kernel: Uptime: 16h19m23s Jan 27 16:17:07 ns kernel: > > Dumping 7744 out of 32688 > > MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > > > > > Alas - I was wrong. > > The problem remains urgent. > > > > The panic occurs when a network owncloud service activity in a jail. > > I will write again: this problem appears while using jails and > > VirtualBox. With switched off the jails - the problem is not > > reproduced. > > > > I am looking forward the merge of the patch into stable/11 and > > releng/11.0. > > > > This is a critical issue for me. > > The panic in PR 211836 is in the netisr code, and they are depend > from the number of configured netisr threads. Your panics looks > different and it seems unrelated. It would be good if you fill the PR > with the details (backtraces from core.txt.N, how your kernel differs > from the GENERIC, what kernel modules you have loaded, etc). > For some time my operating system now is not write core.txt.N files after panics. Now I do not know how to make it do so. Previously, these files are created, but I have not changed anything after that. It is difficult to draw detailed PR. From owner-freebsd-stable@freebsd.org Sat Jan 28 11:58:13 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D90BCC5CEF for ; Sat, 28 Jan 2017 11:58:13 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id 365A21AE4 for ; Sat, 28 Jan 2017 11:58:12 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 19846929A4FF for ; Sat, 28 Jan 2017 12:58:06 +0100 (CET) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id hBPgKNz0xCEL for ; Sat, 28 Jan 2017 12:58:04 +0100 (CET) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 1B7DB929A4FA for ; Sat, 28 Jan 2017 12:58:04 +0100 (CET) Received: by beast.freibergnet.de (Postfix, from userid 201) id 130EA4B783D; Sat, 28 Jan 2017 12:58:04 +0100 (CET) Date: Sat, 28 Jan 2017 12:58:04 +0100 From: Holm Tiffe To: freebsd-stable@freebsd.org Subject: problems with KiCad (pcbnew) on 11-stable with boost-libs Message-ID: <20170128115804.GA68571@beast.freibergnet.de> Mail-Followup-To: Holm Tiffe , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2017 11:58:13 -0000 Hi all, in the last days I've updated my PC from 10.3-stable to 11.0-stable and recompiled almost all installed ports. I have had kicad-devel installed and now I have problems to get that port working again. I've bootstrapped the kicad-devel port (look at the Makefile) and build the last git version. The problem is, that the pcb-editor pcbnew ist segfaulting at startup. /libexec/ld-elf.so.1.debug...done. done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000818cdd711 in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface [New Thread 817816000 (LWP 101268/)] (gdb) bt #0 0x0000000818cdd711 in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface #1 0x0000000818cdda33 in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface #2 0x0000000818cdd96d in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface #3 0x0000000818cdd8fc in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface #4 0x00000008029ff76f in make_fcontext () from /usr/local/lib/libboost_context.so.1.63.0 #5 0x00000000001e8480 in ?? () #6 0x00000000001e8000 in ?? () #7 0x00000008183ef000 in ?? () #8 0x0000000818cdd700 in PNS::TOOL_BASE::Router () from /usr/local/bin/_pcbnew.kiface Previous frame inner to this frame (corrupt stack?) (gdb) I can reproduce it on a 2nd test machine that's newly installed. Some investigations had the result that the system wide boost-libs in the version 1.63 are the problem. I've checked out an old 1.55 version and pcbnew ist running on one machine without segfaulting. Michal (mr@freebsd.org) the port-maintainer informed me that the problem is already known with Windows on amd64: http://kicad-pcb.org/help/known-system-related-issues/ Suggeest there is installing the old boost-libs (1.56) which would'nt work that easy on FreeBSD. I don't have the skills to fix this for me and so my question here is how I can temporarly fix that w/o clobbering the entire system with the old boost_libs? Is someone here using Kicad too? regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 info@tsht.de Fax +49 3731 74200 Tel +49 3731 74222 Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Sat Jan 28 18:21:27 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B8BACC5DE3; Sat, 28 Jan 2017 18:21:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3F808E5; Sat, 28 Jan 2017 18:21:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cXXck-0009YM-7f; Sat, 28 Jan 2017 21:21:18 +0300 Date: Sat, 28 Jan 2017 21:21:18 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Subject: LACP: Fatal trap 18: integer divide fault while in kernel mode Message-ID: <20170128182118.GH58505@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2017 18:21:27 -0000 I am got panic on recent stable: Fatal trap 18: integer divide fault while in kernel mode cpuid = 3; apic id = 06 instruction pointer = 0x20:0xffffffff81453230 stack pointer = 0x28:0xfffffe3e56f46480 frame pointer = 0x28:0xfffffe3e56f464a0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock (3)) trap number = 18 panic: integer divide fault cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff8032b3eb = db_trace_self_wrapper+0x2b/frame 0xfffffe3e56f460c0 vpanic() at 0xffffffff804e33a6 = vpanic+0x186/frame 0xfffffe3e56f46140 panic() at 0xffffffff804e3213 = panic+0x43/frame 0xfffffe3e56f461a0 trap_fatal() at 0xffffffff807b07c2 = trap_fatal+0x322/frame 0xfffffe3e56f461f0 trap() at 0xffffffff807b0475 = trap+0x6b5/frame 0xfffffe3e56f463b0 calltrap() at 0xffffffff807946b1 = calltrap+0x8/frame 0xfffffe3e56f463b0 --- trap 0x12, rip = 0xffffffff81453230, rsp = 0xfffffe3e56f46480, rbp = 0xfffffe3e56f464a0 --- lacp_select_tx_port() at 0xffffffff81453230 = lacp_select_tx_port+0x70/frame 0xfffffe3e56f464a0 lagg_lacp_start() at 0xffffffff814504ae = lagg_lacp_start+0xe/frame 0xfffffe3e56f464c0 lagg_transmit() at 0xffffffff8144e73f = lagg_transmit+0xbf/frame 0xfffffe3e56f46530 ether_output() at 0xffffffff805f30bc = ether_output+0x71c/frame 0xfffffe3e56f465d0 ip_output() at 0xffffffff80629935 = ip_output+0x1585/frame 0xfffffe3e56f46720 tcp_output() at 0xffffffff806b9e16 = tcp_output+0x1876/frame 0xfffffe3e56f468c0 tcp_timer_rexmt() at 0xffffffff806c572f = tcp_timer_rexmt+0x4df/frame 0xfffffe3e56f46900 softclock_call_cc() at 0xffffffff804fd1b6 = softclock_call_cc+0x156/frame 0xfffffe3e56f469b0 softclock() at 0xffffffff804fd754 = softclock+0x94/frame 0xfffffe3e56f469e0 intr_event_execute_handlers() at 0xffffffff8049d15f = intr_event_execute_handlers+0x20f/frame 0xfffffe3e56f46a20 ithread_loop() at 0xffffffff8049d766 = ithread_loop+0xc6/frame 0xfffffe3e56f46a70 fork_exit() at 0xffffffff80499e25 = fork_exit+0x85/frame 0xfffffe3e56f46ab0 fork_trampoline() at 0xffffffff80794bee = fork_trampoline+0xe/frame 0xfffffe3e56f46ab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- (kgdb) info line *0xffffffff81453230 Line 848 of "/usr/src/sys/modules/if_lagg/../../net/ieee8023ad_lacp.c" starts at address 0xffffffff8145322e and ends at 0xffffffff81453233 . Do I need to create PR? From owner-freebsd-stable@freebsd.org Sat Jan 28 19:20:52 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8EFDCC621A; Sat, 28 Jan 2017 19:20:52 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 A9A7BBB9; Sat, 28 Jan 2017 19:20:52 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yw0-x230.google.com with SMTP id v200so35720076ywc.3; Sat, 28 Jan 2017 11:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=tDe24Zp1+IeZN0I+xnz+v2hQx/zOM+DGcNjVjWzl0uI=; b=sPQfP6oH3Nh/AU8fnenOfK5uU4yLN6bLSP3zRUPK+eRGyMegvvzh8JfgrXxDwOKGrv SO9+3g4uyVwiFlK6p5aDuOwno2js9GUVUMDkhhX2vX5AHvkkbAgLaPhT836YGA8WT4Pi 0KItNe6+RCKl5EVjxs9GZDKNNWt4eJWKgEsrVbUGFBXR31s3UF6tT97alThTZBanb6zN DpA7rWnX5+dmUv4xioMXY0nF6XNzmbnOByzIewYyrL9ayWKUAW2JL/2YgBo07DOaqqDL MydS9XYIoIrh2wShuP94lckBPfo8s1U3lC3juQBTrbo7PrheKJ60+wJZE/WC3oSdQx4m X8Lw== 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=tDe24Zp1+IeZN0I+xnz+v2hQx/zOM+DGcNjVjWzl0uI=; b=aDAmaIGR1xQlpdw6EqrkhIznmBv9m0Yq6dJpPyxcxjhFUPdrHL+TOBUYxiuhJqaSIG 6Q8MJBzB5NqpmSk/3OC9x7roGVNAUeyIDCMBx7Yvvg7C7LrBCI7sCmCo2PEQBBLGdW+k fyGVZxKMRMr0bRqSZ28evPX83gk9Jg24c2JHchkl0ASRL/aG6Ks/fpukHsw7yvN4vmSF rPL8NVyvwyf/tJghRFugzZoqSPGL+Rb7XEs20IBYBhEKYNFIETSIdKRXE04L5ySyGODf i1RYMqKkGLmF54P+s4HdKM2xvAqU0rsqnrRvXCErqeSkpjlk7R0YKKKItpO6e43BuUP9 tWXw== X-Gm-Message-State: AIkVDXLnYw5IJKmjmu7Uy+Oux2RkSJGD8P5hV7ql60FWg4IUyF2itpV2DGHvpggx5DRGiEf3xP44T2Z1oejyoQ== X-Received: by 10.13.230.135 with SMTP id p129mr9790080ywe.253.1485631251709; Sat, 28 Jan 2017 11:20:51 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.129.38.133 with HTTP; Sat, 28 Jan 2017 11:20:51 -0800 (PST) In-Reply-To: <20170128182118.GH58505@zxy.spb.ru> References: <20170128182118.GH58505@zxy.spb.ru> From: Alan Somers Date: Sat, 28 Jan 2017 12:20:51 -0700 X-Google-Sender-Auth: XNL9emNSC1BVN9eImOCfHut4YpA Message-ID: Subject: Re: LACP: Fatal trap 18: integer divide fault while in kernel mode To: Slawa Olhovchenkov Cc: FreeBSD , FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2017 19:20:53 -0000 Please do open a PR and CC me. As well as the stack trace, post your lagg configuration, and, if you can determine it, the ports' state at the time of the crash. -Alan On Sat, Jan 28, 2017 at 11:21 AM, Slawa Olhovchenkov wrote: > I am got panic on recent stable: > > Fatal trap 18: integer divide fault while in kernel mode > cpuid = 3; apic id = 06 > instruction pointer = 0x20:0xffffffff81453230 > stack pointer = 0x28:0xfffffe3e56f46480 > frame pointer = 0x28:0xfffffe3e56f464a0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi4: clock (3)) > trap number = 18 > panic: integer divide fault > cpuid = 3 > KDB: stack backtrace: > db_trace_self_wrapper() at 0xffffffff8032b3eb = db_trace_self_wrapper+0x2b/frame 0xfffffe3e56f460c0 > vpanic() at 0xffffffff804e33a6 = vpanic+0x186/frame 0xfffffe3e56f46140 > panic() at 0xffffffff804e3213 = panic+0x43/frame 0xfffffe3e56f461a0 > trap_fatal() at 0xffffffff807b07c2 = trap_fatal+0x322/frame 0xfffffe3e56f461f0 > trap() at 0xffffffff807b0475 = trap+0x6b5/frame 0xfffffe3e56f463b0 > calltrap() at 0xffffffff807946b1 = calltrap+0x8/frame 0xfffffe3e56f463b0 > --- trap 0x12, rip = 0xffffffff81453230, rsp = 0xfffffe3e56f46480, rbp = 0xfffffe3e56f464a0 --- > lacp_select_tx_port() at 0xffffffff81453230 = lacp_select_tx_port+0x70/frame 0xfffffe3e56f464a0 > lagg_lacp_start() at 0xffffffff814504ae = lagg_lacp_start+0xe/frame 0xfffffe3e56f464c0 > lagg_transmit() at 0xffffffff8144e73f = lagg_transmit+0xbf/frame 0xfffffe3e56f46530 > ether_output() at 0xffffffff805f30bc = ether_output+0x71c/frame 0xfffffe3e56f465d0 > ip_output() at 0xffffffff80629935 = ip_output+0x1585/frame 0xfffffe3e56f46720 > tcp_output() at 0xffffffff806b9e16 = tcp_output+0x1876/frame 0xfffffe3e56f468c0 > tcp_timer_rexmt() at 0xffffffff806c572f = tcp_timer_rexmt+0x4df/frame 0xfffffe3e56f46900 > softclock_call_cc() at 0xffffffff804fd1b6 = softclock_call_cc+0x156/frame 0xfffffe3e56f469b0 > softclock() at 0xffffffff804fd754 = softclock+0x94/frame 0xfffffe3e56f469e0 > intr_event_execute_handlers() at 0xffffffff8049d15f = intr_event_execute_handlers+0x20f/frame 0xfffffe3e56f46a20 > ithread_loop() at 0xffffffff8049d766 = ithread_loop+0xc6/frame 0xfffffe3e56f46a70 > fork_exit() at 0xffffffff80499e25 = fork_exit+0x85/frame 0xfffffe3e56f46ab0 > fork_trampoline() at 0xffffffff80794bee = fork_trampoline+0xe/frame 0xfffffe3e56f46ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > (kgdb) info line *0xffffffff81453230 > Line 848 of "/usr/src/sys/modules/if_lagg/../../net/ieee8023ad_lacp.c" starts at address 0xffffffff8145322e and ends at 0xffffffff81453233 . > > Do I need to create PR? > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"