From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 00:52:24 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 7E751106564A for ; Sat, 20 Nov 2010 00:52:24 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 450368FC1C for ; Sat, 20 Nov 2010 00:52:23 +0000 (UTC) Received: by pzk1 with SMTP id 1so1055050pzk.13 for ; Fri, 19 Nov 2010 16:52:23 -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=bfmbbOIFmSnK1gNcsqp+cdOHj2jMBALdkL1BSr768pA=; b=dq8ErpWFMi/XxtJ0KDqDGHZdL0HZyjLeBYsHM5yJHnEZeOtqB1ZGKaWMEmQ/7acrlk /aIk+N4rr1gGgKiclWoJZdQ5AKZBpP58xcmNLT1s+7oBCXgO7BCrGhxYaHtd3bXie2cf ypJD4pGFFAxp3Lo3yAZ5LJ0wiVdYE9ZnF1vTU= 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=BF0Dypk8AULcXqa8AjkhIANPY1NW+gSW8IAj2BikQMYjFUgbRiWGsjkCzqk5jDAJgI Evfj0RxdEP/iMiLSKlPTJmEDhTnnO9ox9gAu359SnOqsvgk3U+2eCDtgTL7s/GNOCuWW 47l7Brp1qTe6alZGdCudO7LCY9MrgrWAj/qdo= Received: by 10.142.11.4 with SMTP id 4mr2437683wfk.181.1290214343629; Fri, 19 Nov 2010 16:52:23 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id w14sm2544672wfd.6.2010.11.19.16.52.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 16:52:22 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 16:52:22 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 16:52:22 -0800 To: Nenhum_de_Nos Message-ID: <20101120005222.GJ13317@michelle.cdnetworks.com> References: <8ca59ffdfef13423f8a34d81cfdefc49.squirrel@eternamente.info> <20101119171324.GA13317@michelle.cdnetworks.com> <603efbe44ab6deefcd86905280566f32.squirrel@eternamente.info> <20101119192731.GB13317@michelle.cdnetworks.com> <9ecdf40489022c754096ac1f388a605f.squirrel@eternamente.info> <20101119212333.GD13317@michelle.cdnetworks.com> <20101119220248.GG13317@michelle.cdnetworks.com> <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94fe065ccecdaf0f391e17fc07af245a.squirrel@eternamente.info> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: usb/140883: [axe] [usb8] 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: Sat, 20 Nov 2010 00:52:24 -0000 On Fri, Nov 19, 2010 at 08:30:54PM -0200, Nenhum_de_Nos wrote: > > On Fri, November 19, 2010 20:07, Nenhum_de_Nos wrote: > > > > On Fri, November 19, 2010 20:02, Pyun YongHyeon wrote: > >> On Fri, Nov 19, 2010 at 07:49:57PM -0200, Nenhum_de_Nos wrote: > >>> > >>> On Fri, November 19, 2010 19:23, Pyun YongHyeon wrote: > >>> > On Fri, Nov 19, 2010 at 06:23:50PM -0200, Nenhum_de_Nos wrote: > >>> > > >>> > [...] > >>> > > >>> >> > Ok, try again after downloading new if_axe.c and let me know > >>> >> > the output "EEPROM data : 0xXX, phymode : 0xXX" shown on your > >>> >> > console. > >>> >> > >>> >> never got to see that message. I saw the diff to previous version, > >>> and > >>> >> did > >>> >> boot into verbose mode (dmesg attached). there were just the belkin > >>> >> gigabit nic on boot. after, the linksys USB200M: > >>> >> > >>> >> axe1: on > >>> usbus2 > >>> >> axe1: PHYADDR 0xe0:0x10 > >>> >> miibus2: on axe1 > >>> >> ukphy1: PHY 16 on miibus2 > >>> >> ukphy1: OUI 0x000ec6, model 0x0001, rev. 1 > >>> >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >>> >> ue1: on axe1 > >>> >> ue1: bpf attached > >>> >> invalid media SR 0x700 > >>> >> invalid media SR 0x700 > >>> >> > >>> > > >>> > This is normal, the message I said will show up when you use > >>> > gigabit controller, AX88178. This controller is fast ethernet > >>> > controller, AX88772A. > >>> > >>> yes, I just tried to show that message with other nic. > >>> > >>> >> > >>> >> and the other gigabit: > >>> >> > >>> >> ugen2.4: at usbus2 > >>> >> axe2: on > >>> usbus2 > >>> >> axe2: PHYADDR 0xe0:0x01 > >>> >> miibus3: on axe2 > >>> >> truephy1: PHY 1 on miibus3 > >>> >> truephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > >>> >> 1000baseT-FDX, > >>> >> auto > >>> >> ue2: on axe2 > >>> >> ue2: bpf attached > >>> >> ue2: Ethernet address: my mac here > >>> >> ue2: link state changed to DOWN > >>> >> > >>> >> and never got to see the EEPROM message. > >>> >> > >>> > > >>> > Two odd things here. This controller looks like Belkin F5D5055 and > >>> > >>> yes, it's this one. > >>> > >>> > it is gigabit controller. So it should print the message I > >>> > mentioned in previous mail. Are you sure you rebuild/reboot your > >>> > kernel? > >>> > >>> as usual, just rebuilt the axe module ... so I'm going to rebuild now. > >>> this is a slow box, and might take a couple of hours. Will try to do it > >>> also in a notebook running stable to speedup the process. > >>> > >>> > The second odd thing is now truephy(4) PHY driver is attached to > >>> > your controller. Previously it was ukphy(4) generic PHY driver. > >>> > This means accessing GMII is not reliable such that reading OUI of > >>> > PHY changed its value. Maybe this could the reason why you see lots > >>> > of link UP/DOWN messages since mii(4) periodically polls a register > >>> > through GMII. If the register value read through GMII constantly > >>> > changes it will cause all sorts of problems. > >>> > I'm not sure whether this is axe(4) issue or USB stack issue. I > >>> > also have Belkin F5D5055 controller and has no such problems so I > >>> > guess it could be related with other parts of USB stack. > >>> > > >>> > To easily identify issues for a controller, it would be better to > >>> > remove all other axe(4) controllers except one you want to test. > >>> > >>> ok, I was also testing that other issue. Will separate things from now > >>> on. > >>> no problem using stable from October 7, right ? > >>> > >> > >> Hmm, that depends on your environments. To test USB issues it would > >> be better to use stable/8. > > > > both are 8-stable from the beginning of October. As the faster is already > > compiling things, and it takes 1h max, I'll try this way and can after > > update to today 8-stable. > > > > if anything, just say :) > > > > thanks, > > > > matheus > > > >>> thanks, > >>> > >>> matheus > > here: > > ugen0.2: at usbus0 > wlan0: Ethernet address: a mac here > fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > ugen1.3: at usbus1 > axe0: on usbus1 > axe0: EEPROM data : 0x0a82, phymode : 02 > axe0: MII without any PHY > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > ugen1.3: at usbus1 (disconnected) > axe0: at uhub1, port 3, addr 3 (disconnected) > ugen1.3: at usbus1 > axe0: on usbus1 > axe0: EEPROM data : 0x0a82, phymode : 02 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Thanks. It's big hint. I uploaded updated if_axe.c Let me know it makes any difference. > miibus1: on axe0 > ukphy0: PHY 1 on miibus1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > ue0: on axe0 > ue0: Ethernet address: a mac here > ue0: link state changed to DOWN > > both belkin, each one at a time. > > will sync world and kernel and make {kernel,world} > > thanks, > > matheus