From owner-freebsd-net@freebsd.org Thu Feb 1 14:17:56 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 D41BEED0EE9 for ; Thu, 1 Feb 2018 14:17:55 +0000 (UTC) (envelope-from marius.h@lden.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 84A2A6CC42 for ; Thu, 1 Feb 2018 14:17:54 +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 3DC8520F33 for ; Thu, 1 Feb 2018 09:17:54 -0500 (EST) Received: from web1 ([10.202.2.211]) by compute7.internal (MEProxy); Thu, 01 Feb 2018 09:17:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lden.org; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=C2XwfhHOjEnFpHZezfcEw6hrex2B0kZ+JCN0NM9ZlaI=; b=gH/rJDod RshdhCL57uaNleTG/jy5rpN774L+mvIlXCjY0uCo0t+JxOWSOHk13Y1K0lEMuOiY B8dhx1Kmjd7D7UD0F73YTE256jp+4F+Z73NDHcqg4EMGaFydJCdv5sJLh+yEtm8J acSrhOvYai8+1XyNI9Oe0E4CNRI4kLbJpmy7aJSWb0xcQSiPi1Mc2WUUk6gw7Dib MqKbW3zilrEaWd0wA3OSUjlRQxn+FhjYzLm/RJMCCDGafckyHXOAVa5uJBhFoHos L4kylErsjm0VA9XGtQMlJ6YXAvZkTZRmMgKj8N5H5n74ky6Gcl25YU9/TrBUHi5Y OKQ/m113Z5+X/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=C2XwfhHOjEnFpHZezfcEw6hrex2B0 kZ+JCN0NM9ZlaI=; b=NrJ0Kb6AHMmu2JEe5FTfTwrE9ZuYzsddudcZwUYi0F29w XT6DSvuUr7ElBRPgA0QniOHjxKMxIQ6Ar+bWRK/YYRPYEGnp9B/8vYFpNjwZ2hEW MN/qSbxNvkZ4PNI0QTbNuHwNLHx+BDhbw8gkokaAwCkDNQCw3Zm5ODUofyJ6Sn7I 1Crkr9OgbZaKv4//PfEwa5fJ7w5hpnQZYXop85BrFmL9ojpC57fwQuUsA/yffAUH eGN41o7FGDQGYKkYu/i4KmNBjqL64c0kBFDdipjY9wjBlLKPadB+vY7qCp0CQDV3 Tc8ePGzTfdU9k/xkGS1Tbb5cIscKhxuIawLDkNEuw== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 1CD8E940F1; Thu, 1 Feb 2018 09:17:54 -0500 (EST) Message-Id: <1517494674.4068747.1255940744.6E4465CF@webmail.messagingengine.com> From: Marius Halden To: 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-fde26eb3 Date: Thu, 01 Feb 2018 15:17:54 +0100 Subject: Issues with bxe NIC X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 14:17:56 -0000 Hi, We have two routers running FreeBSD r320487 (BSDRP) with bxe NICs, they are connected together with a twinax cable and to our ISP with 1Gbit fiber. The NICs in question are Broadcom BCM57840S (Supermicro AOC-STG-B4S). The link between the routers will go down on one side not long after it's brought up while staying up on the other side. I am not able to bring the link back up without either unplugging the cable or powering the routers off and on again, if I try to bring them up by taking them down and up with ifconfig they will stay down no matter what the state was before. After the routers have been up some time the console will be flooded with messages like this: bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) bxe0: ERROR: resource (0x0) in use (status 0xffffffff bit 0x1) bxe0: ELINK EVENT LOG (3) bxe0: ELINK EVENT LOG (3) This is not always limited to just one interface, but can include all interfaces which are in use. -- Marius Halden