From owner-freebsd-usb@FreeBSD.ORG Sat Mar 27 02:20:20 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D56C0106564A for ; Sat, 27 Mar 2010 02:20:20 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-iw0-f183.google.com (mail-iw0-f183.google.com [209.85.223.183]) by mx1.freebsd.org (Postfix) with ESMTP id 8EFE98FC14 for ; Sat, 27 Mar 2010 02:20:17 +0000 (UTC) Received: by iwn13 with SMTP id 13so7221979iwn.14 for ; Fri, 26 Mar 2010 19:20:17 -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=yWkhxpXFZ618rPeiT5xXNlodEUY25f0fafEwUUlSZbg=; b=ajX7uF9Mpiocb3Qi5HzsPZYZLQIxCjkC/01rtx9u8yXFcRTXS6Y3pu9JLd3Zv2RHUF 2aIfLPHj8iVENIWj+9f42u1vx8ryIFEGDJsyfgLZ7RRlFlX8z1UTjwpKjblRm90x1IRB unHrHiNvcPstV5JnC3YJxGFDmvX61rrJk02XA= 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=m42ktcEwf4uCsFJ8uS2/yJCLXZZwNGPtsaIjcFTJhU/vjfRf0qZJmDvByqcMbVTTAc FOIM8Bp3XOWfz6vVjrOP6zqNeR04OTcTlXttWAIBUgyoPTUL94hrDxmTJTH17f4OyHRT Bh5QDEC0fjG2a2S6LFWWgymuGsAe1YJmSV2LY= Received: by 10.231.182.206 with SMTP id cd14mr886865ibb.39.1269656417329; Fri, 26 Mar 2010 19:20:17 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id a1sm1346885ibs.18.2010.03.26.19.20.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 26 Mar 2010 19:20:16 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 26 Mar 2010 19:19:54 -0700 From: Pyun YongHyeon Date: Fri, 26 Mar 2010 19:19:54 -0700 To: Nenhum_de_Nos Message-ID: <20100327021954.GY1278@michelle.cdnetworks.com> References: <20100324214230.GT1278@michelle.cdnetworks.com> <20100324215827.GU1278@michelle.cdnetworks.com> <20100324231833.GX1278@michelle.cdnetworks.com> <35a626b67a1556071f4c76498214581d.squirrel@cygnus.homeunix.com> <20100325173556.GA1278@michelle.cdnetworks.com> <20100326003150.GI1278@michelle.cdnetworks.com> <20100326195012.GS1278@michelle.cdnetworks.com> <6672a5444e755931f93f58f7b2df28c4.squirrel@cygnus.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6672a5444e755931f93f58f7b2df28c4.squirrel@cygnus.homeunix.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: 10Mbps+ throughput usb based ethernet recommendation X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2010 02:20:20 -0000 On Fri, Mar 26, 2010 at 11:03:50PM -0300, Nenhum_de_Nos wrote: > > On Fri, March 26, 2010 16:50, Pyun YongHyeon wrote: > > On Thu, Mar 25, 2010 at 09:57:22PM -0300, Nenhum_de_Nos wrote: > > > > [...] > > > >> >> miibus1: on axe0 > >> >> ukphy0: PHY 1 on miibus1 > >> >> ukphy0: XXX ID1 = 0x7949, ID2 = 0x7949 > >> > > >> > This value looks garbage. > >> > >> :( > >> > >> >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseSX, > >> >> 1000baseT, 1000baseT-FDX, auto > >> > > >> > And this time, ukphy(4) also thinks your PHY supports 1000baseSX. > >> > Of course it's wrong because PHY is copper type. > >> > By chance, are you using Belkin F5D5055 USB controller? I remember > >> > another user also reported similar issue. > >> > >> yes. I have two of them. > >> > > > > Ok, would you try attached patch and check whether the patch prints > > some error messages on your console? I guess some commands are > > timed out here. > > ugen1.3: at usbus1 > axe0: on usbus1 > axe0: PHYADDR 0xe0:0x01 > miibus1: on axe0 > ukphy0: PHY 1 on miibus1 > ukphy0: XXX ID1 = 0x0282, ID2 = 0xf012 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: xx.xx.xx.xx.xx.xx > ue0: link state changed to DOWN > ue0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > wlan0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > vboxnet0: Ethernet address: 0a:00:27:00:00:00 > nfe0: promiscuous mode enabled > wlan0: link state changed to DOWN > wlan0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > ue0: link state changed to DOWN > ue0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > nfe0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > nfe0: link state changed to DOWN > ue0: link state changed to DOWN > nfe0: link state changed to UP > ue0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > nfe0: tx v2 error 0x6100 ^^^^^^^^^^^^^^^^^^^^^^^^ It seems you have nfe(4) Tx issues here. You may want to check negotiated speed/duplex is correct against switch. If you have manual media configuration instead of auto, nuke that configuration. nfe(4) has a long standing issue when manual media configuration is used. > arp: xx:xx:xx:xx:xx:xx:xx is using my IP address 10.1.1.1 on ue0! > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > > so far, just this after plugging the usb nic. tested iperf and the > behavior was the same, but nothing in logs. > > just noticed this: > > ukphy0: XXX ID1 = 0x0282, ID2 = 0xf012 > > this is not the same as the other mail. I think is the same adapter (as I > have two), but this should change with the nic change ? > > I changed and got this: > > miibus1: on axe0 > ukphy0: PHY 1 on miibus1 > ukphy0: XXX ID1 = 0x0282, ID2 = 0xf012 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is *NOT* bogus value. It's Agere Systems' ET1011 gigabit PHY. FreeBSD has truephy(4) for Agere Systems' PHY but it does not have support code for the model yet. > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: xxxxxxxxxxxxxx > ue0: link state changed to DOWN > > so it didn't now. other thing is that not every time it works: > Yeah, that is real issue here. I guess there should be some magic to wakeup the PHY from deep sleep state. I'll see what can be done.