From owner-freebsd-stable@FreeBSD.ORG Fri Feb 8 19:27:57 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30E4464E for ; Fri, 8 Feb 2013 19:27:57 +0000 (UTC) (envelope-from olli@grabthar.secnetix.de) Received: from grabthar.secnetix.de (grabthar.secnetix.de [212.17.241.225]) by mx1.freebsd.org (Postfix) with ESMTP id 9DD5EA65 for ; Fri, 8 Feb 2013 19:27:56 +0000 (UTC) Received: from grabthar.secnetix.de (localhost [127.0.0.1]) by grabthar.secnetix.de (8.14.5/8.14.5) with ESMTP id r18JRtEx017320; Fri, 8 Feb 2013 20:27:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by grabthar.secnetix.de (8.14.5/8.14.5/Submit) id r18JRtYk017319; Fri, 8 Feb 2013 20:27:55 +0100 (CET) (envelope-from olli) Date: Fri, 8 Feb 2013 20:27:55 +0100 (CET) Message-Id: <201302081927.r18JRtYk017319@grabthar.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, pyunyh@gmail.com Subject: Re: re(4) problems with GA-H77N-WIFI In-Reply-To: <20130206055322.GA1442@michelle.cdnetworks.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (FreeBSD/9.1-PRERELEASE-20120811 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 08 Feb 2013 19:27:57 -0000 I'm sorry for the late reply. I didn't have much time this week to investigate this issue. At the moment I implemented a work-around with an additional switch using VLANs, but I'd really like to get the second NIC working. YongHyeon PYUN wrote: > On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver Fromme wrote: > > Recently I got a new mainboard for a router, it's a > > Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. > > > > The problem is that re0 works fine and re1 doesn't: > > It doesn't receive any packets. Tcpdump displays all > > outgoing packets, but no incoming ones on re1. > > Can you see the packets sent from re1 on other box? No. I can only see them locally in tcpdump, but they never hit the wire. > If not, it probably indicates GMAC is in weird state which in turn > indicates initialization was not complete for the controller. > > > Ifconfig shows the link correctly (100 or 1000 Mbit, > > depending on where I plug the cable in). > > I also swapped cables just to be sure, but it made no > > difference. > > If you cold-boot the box with UTP cable plugged in to re1 does it > make any difference? No, it doesn't. > > I'm running a recent stable/9 (about 14 days old). > > What's the best way to debug this problem? At the > > I would check whether GMAC is active when driver detects a valid > link. Add a code like the following to re_miibus_statchg() to get > the status of RL_COMMAND register. You would get the status > whenever a link is established with link partner. re0: CMD 0x0c re0: link state changed to UP re0: link state changed to DOWN re1: link state changed to UP re1: link state changed to DOWN re1: CMD 0x0c re1: link state changed to UP re0: CMD 0x0c re0: link state changed to UP re1: link state changed to DOWN I always seem to get 0x0c for both re0 and re1. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman