From owner-freebsd-stable@FreeBSD.ORG Tue Dec 24 08:30:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AAF78F7F for ; Tue, 24 Dec 2013 08:30:55 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8BA4B1A23 for ; Tue, 24 Dec 2013 08:30:55 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VvNOA-0008Bt-33 for freebsd-stable@freebsd.org; Tue, 24 Dec 2013 00:30:54 -0800 Date: Tue, 24 Dec 2013 00:30:54 -0800 (PST) From: Beeblebrox To: freebsd-stable@freebsd.org Message-ID: <1387873854076-5871132.post@n5.nabble.com> In-Reply-To: <1382106225174-5852917.post@n5.nabble.com> References: <1382080515404-5852849.post@n5.nabble.com> <1382106225174-5852917.post@n5.nabble.com> Subject: Re: if_re NIC ping responds only after manual re-create or dhclient 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.17 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 Dec 2013 08:30:55 -0000 This error had been fixed in an update some time ago. The error is unfortunately back. Same description as previous posts - I can ping to NIC after I delete IP and manually re-assign. During the previous error, I had come across a separate thread on the forums with very similar problem description and had concluded that the problem was with the if_re driver. This time around I have also noticed considerable networking problems: slow or dropped connections, jails unable to keep consistent forwarding traffic between each other, and just a whole slew of annoyances. As posted before, hardware is: re0: port 0xd800-0xd8ff mem re1: port 0xe800-0xe8ff mem Please advise maintainer. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/if-re-NIC-ping-responds-only-after-manual-re-create-or-dhclient-tp5852849p5871132.html Sent from the freebsd-stable mailing list archive at Nabble.com.