From owner-freebsd-usb@FreeBSD.ORG Sat Mar 27 02:04:00 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 9CE0A1065670 for ; Sat, 27 Mar 2010 02:04:00 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from mail-gx0-f211.google.com (mail-gx0-f211.google.com [209.85.217.211]) by mx1.freebsd.org (Postfix) with ESMTP id 446F98FC16 for ; Sat, 27 Mar 2010 02:03:59 +0000 (UTC) Received: by gxk3 with SMTP id 3so466467gxk.13 for ; Fri, 26 Mar 2010 19:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:in-reply-to:references:date:subject:from:to:cc :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; bh=zdgftfJV0wIq4tVltKKsXC+B0H/11/i8iwYmRVTVAzk=; b=c8U2rAWVv6wcQ85zzV5RfCLXkXuI6szNQBBkB1O0IbLorTj06LN72X5+3TmJCwEz1u 5eFBpbERw7EQQrefPbaXGpkWBhHnzYI8nc+SZu6m8xIM6iHsrd8Ov/QTYy1t5TvM+Fq+ wcN7aowzp+Nlfw8BbDV8h+HVJ2lXg4UEG3Sdo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:in-reply-to:references:date:subject:from:to:cc :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; b=EFyMtYJKK3cP8OxwoDmWTsk5WOv+yXzbmj4HA7IV0PI17eAek0SKaxyue9iuiouccv KPAYpkI67d9VOAEdZJSx2bJB8sBiCoH32trJ7t9vsKzr53C75JqQQpe1lS2GyTq7Sy1n 11hzJIIaDbMZeXFRDEruKzmS5pdJlUFOtgJv4= Received: by 10.150.208.12 with SMTP id f12mr2216258ybg.36.1269655439345; Fri, 26 Mar 2010 19:03:59 -0700 (PDT) Received: from cygnus.homeunix.com ([189.71.112.4]) by mx.google.com with ESMTPS id 16sm954860gxk.9.2010.03.26.19.03.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 26 Mar 2010 19:03:57 -0700 (PDT) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id C1DA3B8A1E; Fri, 26 Mar 2010 23:03:50 -0300 (BRT) Received: from 189.71.66.48 (SquirrelMail authenticated user matheus) by cygnus.homeunix.com with HTTP; Fri, 26 Mar 2010 23:03:50 -0300 (BRT) Message-ID: <6672a5444e755931f93f58f7b2df28c4.squirrel@cygnus.homeunix.com> In-Reply-To: <20100326195012.GS1278@michelle.cdnetworks.com> References: <20100324010107.GM1278@michelle.cdnetworks.com> <3e164e2fc77415a67bd7d22e9c51168b.squirrel@cygnus.homeunix.com> <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> Date: Fri, 26 Mar 2010 23:03:50 -0300 (BRT) From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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 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:04:00 -0000 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 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 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: ugen1.3: at usbus1 axe0: on usbus1 axe0: PHYADDR 0xe0:0x01 axe0: MII without any PHY ugen1.3: at usbus1 (disconnected) axe0: at uhub1, port 3, addr 3 (disconnected) ugen1.3: at usbus1 axe0: on usbus1 axe0: PHYADDR 0xe0:0x01 axe0: MII without any PHY ugen1.3: at usbus1 (disconnected) axe0: at uhub1, port 3, addr 3 (disconnected) and in the third time it found the PHY it was looking for above and got what I said above. hope it helps, thanks, matheus >> thanks, >> >> matheus >> >> > Hans, I guess there is not much thing left to do in PHY driver >> > because accessing these MII registers return garbage. What could be >> > done in USB subsystem to get more information to know why >> > controller returns garbage for accessing MII registers? >> > > -- 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