From owner-freebsd-current@FreeBSD.ORG Fri Oct 9 19:41:52 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FA631065695 for ; Fri, 9 Oct 2009 19:41:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 0DE4E8FC18 for ; Fri, 9 Oct 2009 19:41:51 +0000 (UTC) Received: by ewy18 with SMTP id 18so1366746ewy.43 for ; Fri, 09 Oct 2009 12:41:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=/q7ZEoBqAjXHtQ6lycVAyZ1BGhQ0KiFECYEWpYHaV10=; b=dxm60SXkvQ7lIalJugzQ5A2mRE0Xr7CpP5hGKyhBGsGoYPQZlEqW8x+/YtxqbAomMV 82L6h6CoOIFu2QC67eTAYx+eGuzWtpsN8nPDoGrG5G9PoK8spj0XxS91UCpwEU0S/sDB MKC/5GnzUfuHI3YWGj8wNmUOGEdBjnD9K77SI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=I6nQe+ZDafY0tL+bljSOYvnSyw3cslbOSbL+uFvzfce2ByD1N+54m5J7GoE5z05nBk IQutPDJDufy0t5QL5z/jMc9h5mPihPIjBNtVDMVoB3H6pq4OEhbfSKO+yh6Mm/I7nArj T3QIAd+LRYnXmYQIZ/u/IjYWK44+cfL8WDHQU= Received: by 10.216.90.203 with SMTP id e53mr1025589wef.28.1255117310798; Fri, 09 Oct 2009 12:41:50 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id m5sm203772gve.26.2009.10.09.12.41.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 09 Oct 2009 12:41:47 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 9 Oct 2009 12:40:37 -0700 From: Pyun YongHyeon Date: Fri, 9 Oct 2009 12:40:37 -0700 To: Ian FREISLICH Message-ID: <20091009194037.GI3843@michelle.cdnetworks.com> References: <20091008170458.GC3843@michelle.cdnetworks.com> <20091007180257.GA3843@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: alc(4) link autoselect problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Oct 2009 19:41:52 -0000 On Fri, Oct 09, 2009 at 07:29:08AM +0200, Ian FREISLICH wrote: > Pyun YongHyeon wrote: > > On Thu, Oct 08, 2009 at 12:38:45PM +0200, Ian FREISLICH wrote: > > > wgsw-24010# sh interfaces status ethernet g14 > > > Flow Link Back Mdix > > > Port Type Duplex Speed Neg ctrl State Pressure Mode > > > -------- ------------ ------ ----- -------- ---- ----------- -------- ---- > --- > > > g14 1G-Copper Full 100 Enabled Off Up Disabled Off > > > > > > > Hmm, does your switch have an option to enable/disable downshifting > > feature? If so, how about toggling the option? > > I'm not sure exactly what you mean. There's no configuration options > that obviously match. > Modern PHYs have ability to correct several cabling problems, for example, - pair swaps - pair skews - pair polarity - automatic MDI/MDIX - downshift to enable 10/100Mps link establishment with two pairs by downgrading the link speed to 10/100Mbps during auto-negotiation process when it can't establish 1000Mbps link. Existing cables used to connect 10/100Mbps link partners may have only two pairs. With two pairs PHYs can announce 1000Mbps capability to link partner but it can't establish the link as 1000Mbps link requires 4 pairs. Since F1 PHY seems to have above capability I just wanted to see whether disabling downshifting on link partner makes any difference. > > > > How about checking MIB statistics of controller? > > > > (sysctl dev.alc.0.stats) > > > > > > This is after a reboot, but the link was up for a short while to > > > do the above testing. rx.good_frames looks a bit high for "up 21 > > > mins". > > > > > > dev.alc.0.stats.rx.good_frames: 3348588249 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > dev.alc.0.stats.rx.good_octets: 0 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > Yeah, that looks odd, it seemed controller received a lot of good > > frames but none were meaningful packets so I guess there are link > > establishment issues. I still have no clue but if I manage to find > > more test case I will let you know. > > That number is bogus. It's currently incrementing by approximately > 33435108 per second without a cable plugged in. > Hmm, I have to test this case. Thanks. > Ian > > -- > Ian Freislich