From owner-freebsd-current@FreeBSD.ORG Mon Mar 30 02:17:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99E02106566B for ; Mon, 30 Mar 2009 02:17:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 5BDD78FC0A for ; Mon, 30 Mar 2009 02:17:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so2505339rvb.43 for ; Sun, 29 Mar 2009 19:17: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=8H9N+8fxM9oJowSmuAX2V75kvhlar/1CXu9jccWUEU4=; b=Ing66kDPFltFEEGSUlcgDTle96FeOZLqu1FOu+zZQWRF6l7kwjP0PVtV8mr7IXf15X uKdY2f3hL0tUucwmLRrpARbiFI0hr4ktLyIOtqDTEvLs9UvnSFFzg/uGaIo2fc14olH+ 4AfaEnbB8sFRViAsnjyG3R6uL4vIhAQiYCasE= 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=pmhtaNzY+KCNOH/8iTy760LfXYyiHbtALhsq0Tua1zoEyinhsYywZxAaOEyQk33SpD fJiLx7zQQK/oG2chSkVcylvEVTtJWjXEcqTqHWZLB/nqe2thKFN+hyIGEZWLsYvI+oah JvLfmrFg9XrC7ixyqPZSQI2n2bDF//4ElKcok= Received: by 10.140.248.15 with SMTP id v15mr2522791rvh.165.1238379470766; Sun, 29 Mar 2009 19:17:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id g14sm11780206rvb.29.2009.03.29.19.17.49 (version=SSLv3 cipher=RC4-MD5); Sun, 29 Mar 2009 19:17:50 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Mon, 30 Mar 2009 11:16:48 +0900 From: Pyun YongHyeon Date: Mon, 30 Mar 2009 11:16:48 +0900 To: Niki Denev Message-ID: <20090330021648.GE7076@michelle.cdnetworks.co.kr> References: <75656435-49E2-457A-9CFE-8706CD44916E@gmail.com> <20090328080924.GD99923@michelle.cdnetworks.co.kr> <2e77fc10903280259s5a761cacs398b88649a2367fe@mail.gmail.com> <20090328102735.GE99923@michelle.cdnetworks.co.kr> <2e77fc10903280942u7c934aa4w80176680e9dff6d7@mail.gmail.com> <2e77fc10903281539h7b713711w116a90fd2bfadbcf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2e77fc10903281539h7b713711w116a90fd2bfadbcf@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: Sepherosa Ziehau , freebsd-current@freebsd.org Subject: Re: axe(4) (Belkin F5D5055) problems 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: Mon, 30 Mar 2009 02:17:51 -0000 On Sun, Mar 29, 2009 at 12:39:22AM +0200, Niki Denev wrote: > On Sat, Mar 28, 2009 at 6:42 PM, Niki Denev wrote: > > On Sat, Mar 28, 2009 at 12:27 PM, Pyun YongHyeon wrote: > >> On Sat, Mar 28, 2009 at 11:59:13AM +0200, Niki Denev wrote: > >>> 2009/3/28 Pyun YongHyeon : > >>> > On Fri, Mar 27, 2009 at 09:14:06PM +0200, Nikolay Denev wrote: > >>> >> -----BEGIN PGP SIGNED MESSAGE----- > >>> >> Hash: SHA1 > >>> >> > >>> >> Hello, > >>> >> > >>> >> I'm running -current from 23.03.09 and I'm experiencing some axe(4) > >>> >> problems. > >>> >> Basically the network connection works but when some more serious > >>> >> traffic hits the > >>> >> interface (i.e. torrent download) it then dies, ifconfig down/up > >>> >> does not help, only replugging of the adapter. > >>> >> > >>> >> I've tried running with hw.usb2.axe.debug=15 and the output was many > >>> >> lines of: > >>> >> > >>> >> ? ?axe_bulk_write_callback:853: transfer complete > >>> >> > >>> >> then a pause of several seconds and the kernel begins to print : > >>> >> > >>> >> ? ?axe_bulk_write_callback:925: transfer error, USB_ERR_TIMEOUT > >>> >> > >>> >> Another strange thing that I noticed is that, while the interface > >>> >> seems to be > >>> >> connected and working, if I type many times ifconfig ue0 consecutively > >>> >> most of the time it would show different settings for the auto > >>> >> negotiated link. > >>> >> I.e. it would cycle between 100baseTX-FDX, 1000baseT-FDX, no carrier, > >>> >> 100BaseT-FDX hw-loopback and 1000BaseT-FDX hw-loopback. > >>> >> > >>> >> The switch does not seem to register link flaps. > >>> >> > >>> > > >>> > axe(4) requires exact link state/speed information from mii(4) to > >>> > reprogram controller to resolved speed/duplex. In this case > >>> > ukphy(4) seems to report fake link state/speed to axe(4). > >>> > > >>> >> The kernel messages for the interface are : > >>> >> > >>> >> ? ?ugen2.5: at usbus2 > >>> >> ? ?axe0: on usbus2 > >>> >> ? ?axe0: PHYADDR 0xe0:0x01 > >>> >> ? ?miibus0: on axe0 > >>> >> ? ?ukphy0: PHY 1 on miibus0 > >>> >> ? ?ukphy0: ?10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >>> >> 1000baseT, 1000baseT-FDX, auto > >>> >> ? ?ue0: on axe0 > >>> >> ? ?ue0: Ethernet address: 00:11:50:xx:xx:xx > >>> >> > >>> >> devinfo -vr | grep phy > >>> >> ukphy0 pnpinfo oui=0xa0bc model=0x1 rev=0x2 at phyno=1 > >>> >> > >>> > > >>> > This looks like Agere systems ET110C TruePHY. Would you try > >>> > attached patch? Because truephy(4) pokes some undocumented PHY > >>> > registers on PHY reset I'm not sure this model also requires that > >>> > magic to make it work though. > >>> > > >>> > >>> Hi Pyun, > >>> > >>> Thanks for the patch. > >>> > >>> With it the PHY is now detected as truephy. > >>> The only thing that i notice is that if the media status changes displayed with > >>> ifconfig are less frequent, and I mostly see 1000baseT-FDX and 100baseT-HDX > >>> The packet loss is still there, and the interface again stops to work > >>> after some time. > >>> > >> > >> Ok, revert previous patch and try attached one. This one does not > >> try to load ET1011C dsp codes. If this does not work next thing > >> would be try to load dsp code for ET1011C revision 1 model. > >> Not sure where I can find required dsp code. > >> > > > > There don't seem to be any improvement with the new patch. > > The packetloss and media status changes are still here. > > Maybe check Linux/Solaris/OtherBSD driver? > > > > -- > > Niki > > > > LSI seem to have several documents about this phy chip, including > datasheet (which you probably have) and errata : > http://www.lsi.com/DistributionSystem/AssetDocument/documentation/networking/ethernet/et1011c/DS06-161GPHY_ET1011C_09-28-2007.pdf > http://www.lsi.com/DistributionSystem/AssetDocument/documentation/networking/ethernet/et1011c/ET1011C_Errata_08June2007.pdf > Yes, but unfortunately it is for model 3 or model 4. Yours is model 1. In fact I have no idea whether model 1 is ET1011C. It seems that there are ET1011A or ET1011B PHYs. Sepherosa, do you have more information on ET1011A/ET1011B PHY?