From owner-freebsd-net@freebsd.org Tue Aug 28 20:13:14 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71C9F1097370 for ; Tue, 28 Aug 2018 20:13:14 +0000 (UTC) (envelope-from marius.h@lden.org) 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 1CAA394F95; Tue, 28 Aug 2018 20:13:14 +0000 (UTC) (envelope-from marius.h@lden.org) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9FD63211E5; Tue, 28 Aug 2018 16:13:13 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute7.internal (MEProxy); Tue, 28 Aug 2018 16:13:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lden.org; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=t/eTB07VGIUojfxwhDxT36dO3EZ+u EZAjwTKLFJkytg=; b=MVMtGTRZFKN8ID/ULgEFmQ/At0HlNWd+FDfIZrQtdWkpg jqW+Z+mSzwQFystmE+Odv0MZfyQCtYAoFrpljGV2yvON7r04zHqcDBcNq/dur1gf 9sLyJPKERjJFksfRp1jKyFO/040DUuEbPdW6s5Fi1FDR9JPGhy0l0kqY1Wb9cLfB YA9WDHP8t0sTYpvdoil0WdHl2XySwCClL+zuYDNrAapGcAQ/SN5SbItHrk49nS0z zuh2vmr5E8mVSlcYP8c4YKffMXXqgC5Vx8bgnpVVDzi0QL7cfOFoEhCbQuEEt7rY j8prvRxRCbcIctSqKNlBWD4EeAgrrZPZwKpfg8iyQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=t/eTB0 7VGIUojfxwhDxT36dO3EZ+uEZAjwTKLFJkytg=; b=UJMK5YRJjlgu54cfKS0lPO UAURx8SWmpYURIQ0oBfcPDUC/8QybfBXt8ma+sI6YzlfNqtRkH5kOZN8MKMRuTR4 BeGcqr4gHqKujBrJv51dZSQ2S0DOXo2PA7u+5jHyoV/3zFxGroOp5u/f5o6rR453 lhrs3Ns/nxfhp4/fmJz1/zUnR8r+Wip3+jvQ9QxQjbnS8bjo87oqN7c3ceAHIO5A mV5Zhq2hyw2Vy/o8IAzAvlgke6/UBU5QrSZPfV2S7Hzp68dgRZSP1nOkrAJVzu7t qidVbWlDY/3v169zGznIAajtMlOznROdu98U6g48Uagb6vEu/IGsde7YykfNxcAQ == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DEAF49E48A; Tue, 28 Aug 2018 16:13:12 -0400 (EDT) Message-Id: <1535487192.1547312.1489227960.14DA5D07@webmail.messagingengine.com> From: Marius Halden To: Navdeep Parhar Cc: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-7b72137a Subject: Re: cxl nic not working after reboot Date: Tue, 28 Aug 2018 22:13:12 +0200 References: <1535379569.2132387.1487489784.45227861@webmail.messagingengine.com> <20180827151302.GA10167@ox> <1535395530.234212.1487804896.64257978@webmail.messagingengine.com> <1535448912.3229649.1488521184.1EE83C33@webmail.messagingengine.com> <3bdfa15a-1b9f-e8cd-00a5-f5fdaaa5d15e@FreeBSD.org> <1535480853.1508751.1489107768.35E0F6F1@webmail.messagingengine.com> <72e8b5b8-631b-35b3-b378-804e69dd3250@FreeBSD.org> <1535484638.1530345.1489178328.3374515B@webmail.messagingengine.com> <32fc6737-87f8-7156-17f0-8e17b65a0812@FreeBSD.org> In-Reply-To: <32fc6737-87f8-7156-17f0-8e17b65a0812@FreeBSD.org> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 20:13:14 -0000 On Tue, Aug 28, 2018, at 21:34, Navdeep Parhar wrote: > On 8/28/18 12:30 PM, Marius Halden wrote: > > tx_frames does move, rx_frames is stuck at zero. The following counters are non-zero and does increase when traffic is sent through the interface, all other are stuck at zero: > > > > dev.cxl.0.stats.tx_frames_65_127: 26083 > > dev.cxl.0.stats.tx_frames_64: 4084 > > dev.cxl.0.stats.tx_mcast_frames: 26083 > > dev.cxl.0.stats.tx_bcast_frames: 4084 > > dev.cxl.0.stats.tx_frames: 30167 > > dev.cxl.0.stats.tx_octets: 2608846 > > > > Anything else I should look at? > > > > What is on the other side of the link? Look at the peer's rx stats and > see if it received the frames that cxl0 claims it has transmitted or not. Our ISPs router is connected to the other side. Unfortunately I don't have access to any of the counters, but from what I understood when originally debugging this with our ISP they did not see any traffic. If needed I can ask them to check the rx counters tomorrow. -- Marius Halden