From owner-freebsd-stable@freebsd.org Wed Oct 10 22:21:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55A2D10BE3E9 for ; Wed, 10 Oct 2018 22:21:25 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E5386745BE for ; Wed, 10 Oct 2018 22:21:24 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 8617 invoked by uid 1003); 10 Oct 2018 22:14:46 -0000 Received: from unknown (HELO grape.brokenco.de) (tyler@monkeypox.org@50.0.170.232) by mail.geekisp.com with (AES256-SHA encrypted) SMTP; 10 Oct 2018 22:14:45 -0000 Date: Wed, 10 Oct 2018 15:14:38 -0700 From: "R. Tyler Croy" To: freebsd-stable@FreeBSD.org Subject: Peculiar failure of re(4) to active a link after a RAM upgrade Message-ID: <20181010221438.GF28842@grape.brokenco.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f6nK9RR+X1IX2pXa" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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, 10 Oct 2018 22:21:25 -0000 --f6nK9RR+X1IX2pXa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I recently upgraded my 11.2-STABLE machine from 4 to 16GB of memory. Upon reboot the dual-NIC re(4) card which had been previously working failed to either negotiate or activate a link (i.e. lights up :)) with my DSL modem. ifcnofig lists the interface as 'no carrier' I verified that both ports (re0 and re1) were working by plugging network cables into my switch, and found that both were able to activate a link properly. When I plugin the DSL modem's cable into my em(4) based NIC, that activates a link properly. Regardless of which re(4) NIC I stick the cable into, it fails to create a link (ifconfig lists em0 as 'active'), while the same cable works properly in an em(4) NIC. I'm running r339079 right now, and if I remember correctly, had upgraded the world prior to the RAM upgrade, so it _seems_ like the RAM upgrade is the only variable which changed. I'm really clueless as to what would even be happening underneath the covers here, and would appreciate any pointers in the right direction for debugging here :) Cheers, -R Tyler Croy -- GitHub: https://github.com/rtyler Twitter: https://twitter.com/agentdero --f6nK9RR+X1IX2pXa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSQYoZaRujHSSvxiNcUJsfcP1HhbwUCW755zAAKCRAUJsfcP1Hh b270AJ4vRyv4NIjn3zA2n1iWgt8O/dte9gCfUpXTdcz7QyRuHFbw5MBuTRFz74Y= =u0a4 -----END PGP SIGNATURE----- --f6nK9RR+X1IX2pXa--