From owner-freebsd-current@FreeBSD.ORG Sat Mar 28 08:10:52 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 1A7AD106566C for ; Sat, 28 Mar 2009 08:10:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.186]) by mx1.freebsd.org (Postfix) with ESMTP id A36728FC13 for ; Sat, 28 Mar 2009 08:10:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id u5so1017828tia.3 for ; Sat, 28 Mar 2009 01:10: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=ahsVBpFADPD26fodtd36oFbamZHi3+3WckLhZYUECGY=; b=YCiseLET5ureSwtYV4SaVChBeHpUgoBVcVtsSk/YqdHjtuYXqiwBtNTomGgqtkVCEp QXx2x3uWSo8lbhIouG2JVMU10h2IlDMDOJx8yteT8L8MeUf4XVAN9TR2PP46fDSbcQ6x L5XzwGq2WEV71/QoqftSJucQI9lb42RuKWehA= 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=VYNcneUWeeJ6YCVsu1OFDm6BjKRXEHftcQ8myKgyG2nu2nDCNpvaI3YkkSmMLGUTtO 5+ROIirwRsIfV7lVYhQiE2lODEef9PULLhZFCj1gCCXmn58tIvdTAjbAehnDFShNqK+9 6KzvwfUvQTDgsCG+RuBYjVvZ4x3avQHiTedvU= Received: by 10.110.42.17 with SMTP id p17mr4317801tip.36.1238227850257; Sat, 28 Mar 2009 01:10:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id u8sm4047830tia.30.2009.03.28.01.10.48 (version=SSLv3 cipher=RC4-MD5); Sat, 28 Mar 2009 01:10:49 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Sat, 28 Mar 2009 17:09:25 +0900 From: Pyun YongHyeon Date: Sat, 28 Mar 2009 17:09:24 +0900 To: Nikolay Denev Message-ID: <20090328080924.GD99923@michelle.cdnetworks.co.kr> References: <75656435-49E2-457A-9CFE-8706CD44916E@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <75656435-49E2-457A-9CFE-8706CD44916E@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: 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: Sat, 28 Mar 2009 08:10:52 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --cWoXeonUoKmBZSoM Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="mii.ET110C.patch" Index: sys/dev/mii/truephy.c =================================================================== --- sys/dev/mii/truephy.c (revision 190500) +++ sys/dev/mii/truephy.c (working copy) @@ -76,6 +76,7 @@ }; static const struct mii_phydesc truephys[] = { + MII_PHY_DESC(AGERE, ET1011C_1), MII_PHY_DESC(AGERE, ET1011C), MII_PHY_END }; Index: sys/dev/mii/miidevs =================================================================== --- sys/dev/mii/miidevs (revision 190500) +++ sys/dev/mii/miidevs (working copy) @@ -108,6 +108,7 @@ */ /* Agere Systems PHYs */ +model AGERE ET1011C_1 0x0001 ET1011C 10/100/1000baseT PHY model AGERE ET1011C 0x0004 ET1011C 10/100/1000baseT PHY /* Altima Communications PHYs */ --cWoXeonUoKmBZSoM--