From owner-freebsd-usb@FreeBSD.ORG Mon Nov 30 20:15:07 2009 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 EFBB2106566B for ; Mon, 30 Nov 2009 20:15:07 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-vw0-f188.google.com (mail-vw0-f188.google.com [209.85.212.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3838FC12 for ; Mon, 30 Nov 2009 20:15:07 +0000 (UTC) Received: by vws26 with SMTP id 26so1221656vws.7 for ; Mon, 30 Nov 2009 12:15:06 -0800 (PST) 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=gqpCss89tgQviavG9EWyA9w1WAd1wzJeJPbLNbBfl9U=; b=m6HInvzD+WDINJsFmUnz9cLX5MnECldtMKcnKS0+1H4KRdDriz22EzB795aCTgB8pY pwm2Umdf6abBOkMnXoU/92emIYWrV/eVjOYqf4KyGbqiVIc0N1kVHAeGksO/FNHqG++u G8NFvux2YR64lvewA7W43+Waa+HrMXwtZ9lCw= 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=JF8RRBD9+zNgG9YSbXAWnFBMLuEUib+U4OVir5SK8k41w0ghvIoWGITBt33FHW5Cwm nnaOMMGKyey7GD7n1riZaUYOVzgUrnKXT+vf6fXb+IEHnbCdn5kiZFO3s/Mih5/vXR2V XfpNSujkd9YbnRL8g1V/ejQLp8fe9lvjR0ggI= Received: by 10.220.122.212 with SMTP id m20mr5799627vcr.32.1259612106692; Mon, 30 Nov 2009 12:15:06 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 22sm7751473vws.14.2009.11.30.12.15.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 30 Nov 2009 12:15:05 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 30 Nov 2009 12:13:54 -0800 From: Pyun YongHyeon Date: Mon, 30 Nov 2009 12:13:54 -0800 To: Jason Edwards Message-ID: <20091130201354.GD1172@michelle.cdnetworks.com> References: <200911260840.nAQ8e4c7030168@freefall.freebsd.org> <20091129015142.GB1355@michelle.cdnetworks.com> <883b2dc50911291942n618bcaax2bb76e3e246be25f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <883b2dc50911291942n618bcaax2bb76e3e246be25f@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic 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: Mon, 30 Nov 2009 20:15:08 -0000 On Mon, Nov 30, 2009 at 04:42:28AM +0100, Jason Edwards wrote: > [root@mesa /]# devinfo -rv | grep phy > (..) > ukphy1 pnpinfo oui=0x606e model=0xc rev=0x0 at phyno=0 > (..) > > I understand my device may have the same name, but different PHY thus > is actually a different product. > This looks strange. According to the output above, the OUI indicates the PHY vendor is Davicom and its model number is 0x0c. However, the vendor's site has no mention of gigabit PHY and also their current product line does not seem to have model C of PHY. Are you sure your axe(4) controller has gigabit PHY? Or by chance did you capture the output of udav(4)? > In order to debug this problem i need physical access to change the > ethernet cables (and replug the device once its stuck). Probably might > get the chance tomorrow. > > Aside from enabling debug and trying to get it to the point it fails, > what else could i try to identify the problem or is there any other > information you require to diagnose this issue? > > Thanks for looking into it! > Kind regards, > sub > > On 11/29/09, Pyun YongHyeon wrote: > > On Thu, Nov 26, 2009 at 08:40:04AM +0000, Hans Petter Selasky wrote: > >> The following reply was made to PR usb/140883; it has been noted by GNATS. > >> > >> From: Hans Petter Selasky > >> To: freebsd-usb@freebsd.org > >> Cc: sub mesa , > >> freebsd-gnats-submit@freebsd.org > >> Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short > >> period of traffic > >> Date: Thu, 26 Nov 2009 09:32:43 +0100 > >> > >> On Thursday 26 November 2009 03:59:55 sub mesa wrote: > >> > >Number: 140883 > >> > >Category: usb > >> > >Synopsis: axe(4) USB gigabit ethernet hangs after short period > >> of > >> > > traffic Confidential: no > >> > >Severity: serious > >> > >Priority: medium > >> > >Responsible: freebsd-usb > >> > >State: open > >> > >Quarter: > >> > >Keywords: > >> > >Date-Required: > >> > >Class: sw-bug > >> > >Submitter-Id: current-users > >> > >Arrival-Date: Thu Nov 26 03:00:11 UTC 2009 > >> > >Closed-Date: > >> > >Last-Modified: > >> > >Originator: sub mesa > >> > >Release: FreeBSD 8.0-RELEASE i386 > >> > >Organization: > >> > >Environment: > >> > > >> > FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET > >> > 2009 xor@xor:/usr/obj/usr/src/sys/XOR i386 > >> > > >> > >Description: > >> > > >> > I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip > >> > supported by the axe(4) driver in FreeBSD 8.0. It works, but it > >> 'freezes' > >> > or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 > >> minutes > >> > will cause the device to freeze. This has been happening since a long > >> time > >> > on 8.0, ever since i bought the device and was running one of the early > >> > beta's. Upgrading to the final release of 8.0 did not resolve the > >> issue. > >> > > >> > Googling on the problem i found this mailinglist thread: > >> > > >> http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html > >> > > >> > However, there doesn't seem to be a single conclusion. Even though my > >> > product ("Belkin F5D5055") seems to be supported according to the > >> axe(4) > >> > manpage, it doesn't get detected as such, rather with a vendor id. > >> Quoting > >> > dmesg output: > >> > > >> > axe0: on usbus4 > >> > axe0: PHYADDR 0xe0:0x01 > >> > miibus1: on axe0 > >> > ue0: on axe0 > >> > > >> > May i suggest removing the Belkin F5D5055 from the supported devices > >> list > >> > in the axe(4) manpage, until a fix has been committed? I specifically > >> > bought the device believing it would work since it was explicitly > >> listed in > >> > the manpage. As of 8.0, it doesn't even get detected by name. It is of > >> > course possible my device is of a different revision. > > > > I frequently see some vendors do not change their model name even > > though the controller's internal chipset/PHY was changed. I guess > > the original FD5055 have used different PHY so it might have worked > > at that time. > > > >> > > >> > I would be happy to try any patches. > >> > > >> > Also see: > >> > http://forums.freebsd.org/showthread.php?t=8661 > >> > > >> > >How-To-Repeat: > >> > > >> > Connect axe(4) gigabit ethernet device > >> > Send/receive packets using the ueX ethernet device > >> > Device will stop receiving/transmitting packets after a short while > >> > > > > > I remember some user also reported instability of axe(4) on Belkin > > F5D5055. I'm not sure what PHY driver was attached to your > > controller but it could also be a variant of LSI TruePHY. > > Would you show me the output of "devinfo -rv | grep phy"? > >