Date: Fri, 26 Mar 2010 23:31:50 -0300 (BRT) From: "Nenhum_de_Nos" <matheus@eternamente.info> To: pyunyh@gmail.com Cc: freebsd-usb@freebsd.org Subject: Re: 10Mbps+ throughput usb based ethernet recommendation Message-ID: <4f4516c4a748aacfbd62cad9691afb90.squirrel@cygnus.homeunix.com> In-Reply-To: <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> <b5b7224dd079150dcb9c932ef6603e08.squirrel@cygnus.homeunix.com> <20100326003150.GI1278@michelle.cdnetworks.com> <e15b32df866e9001a9f0971b2393bce2.squirrel@cygnus.homeunix.com> <20100326195012.GS1278@michelle.cdnetworks.com> <6672a5444e755931f93f58f7b2df28c4.squirrel@cygnus.homeunix.com> <20100327021954.GY1278@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, March 26, 2010 23:19, Pyun YongHyeon wrote: > 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: <MII bus> on axe0 >> >> >> ukphy0: <Generic IEEE 802.3u media interface> 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: <vendor 0x050d> at usbus1 >> axe0: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 3> on usbus1 >> axe0: PHYADDR 0xe0:0x01 >> miibus1: <MII bus> on axe0 >> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1 >> ukphy0: XXX ID1 = 0x0282, ID2 = 0xf012 >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> ue0: <USB Ethernet> 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. I'm linking my nfe0 from notebook, bridged in a vbox freebsd machine, and the usb nic. the media is auto (not manually changed since boot) on both ue0 (native freebsd), nfe0 native and em0 (guest freebsd). >> 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: <MII bus> on axe0 >> ukphy0: <Generic IEEE 802.3u media interface> 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. so I can think that's the issue, right ? >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> ue0: <USB Ethernet> 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. ok, great it was found :) let me know if I can help in anything :) matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f4516c4a748aacfbd62cad9691afb90.squirrel>