From owner-freebsd-stable@FreeBSD.ORG Wed Feb 13 01:34:48 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 CFCF99C8 for ; Wed, 13 Feb 2013 01:34:48 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-da0-f49.google.com (mail-da0-f49.google.com [209.85.210.49]) by mx1.freebsd.org (Postfix) with ESMTP id A3235135 for ; Wed, 13 Feb 2013 01:34:48 +0000 (UTC) Received: by mail-da0-f49.google.com with SMTP id t11so306980daj.36 for ; Tue, 12 Feb 2013 17:34:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=Yv+WBEk40odReGoYPDlBRh8JQjsztZrXxNByi+Qk+h4=; b=QzNXwtRTO6chrEdhMKpEUDR4fFLltUsNobFjRqy9K4DlhjOKmU2d/V9EC94rjuLnj1 Xk9863kZi09woT4Ed7vwXSkcDPBCWdZ1iY7peGY6pvo01MsYLkNQBGovtf5c3vmolzwQ HTof94nkNFLizffmQozcO6RaQSLwgQmqGn1/6S8n0xB/yc62T5dxHDM/HCvK67siT/XX v71Z82qSIixuSbzLb76C9afpzI6fm0OgoYMpEg79YR8rCrgrhIPzQ7i0rUgIlpzZpS5u uiih9lA2npD5w8Dcu2NBaX/p/qIgI9O38ji8l8i5XwpNpSDZTHlqKAczkoTxMUFhSI2p pfZg== X-Received: by 10.66.81.199 with SMTP id c7mr58051251pay.39.1360719287488; Tue, 12 Feb 2013 17:34:47 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id z10sm79153537pay.7.2013.02.12.17.34.44 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Feb 2013 17:34:46 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 13 Feb 2013 10:34:38 +0900 From: YongHyeon PYUN Date: Wed, 13 Feb 2013 10:34:38 +0900 To: Oliver Fromme Subject: Re: re(4) problems with GA-H77N-WIFI Message-ID: <20130213013438.GA3101@michelle.cdnetworks.com> References: <20130206055322.GA1442@michelle.cdnetworks.com> <201302081927.r18JRtYk017319@grabthar.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302081927.r18JRtYk017319@grabthar.secnetix.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@FreeBSD.ORG X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 01:34:48 -0000 On Fri, Feb 08, 2013 at 08:27:55PM +0100, Oliver Fromme wrote: > 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. Hmm, it seems GMAC is in sane state. Would you show me the output of "devinfo -rv | grep rgephy"? To rule out hardware issues, could you also try other OS like Linux? > > Best regards > Oliver