From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 22:02:52 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 CB85C106566C for ; Fri, 19 Nov 2010 22:02:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 78FC88FC14 for ; Fri, 19 Nov 2010 22:02:52 +0000 (UTC) Received: by gyg13 with SMTP id 13so3155140gyg.13 for ; Fri, 19 Nov 2010 14:02:51 -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=0IjQ/7OqYAboje2b24aega+kyJ7rVQGgbL/nM5Wd2tA=; b=VRZ4kQNDbdN/m9KmVKTi6F6gaRAuzeyjdPeGl0EMosSB9MOcN0cB3ThP8HbL7G874K aKvYiOexbqQnslrsHcrBO+qPH7Qvb/wOv02jL0SgecJqmmeuTMVXE7hubo/VlqcGR9IM v3r+4IOW+0pOPj6IEE29khTq0ksZi5V+d4AjE= 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=VhJNiqHI7GIleYvwOJbpR5OQMwoD5bjRMHzZItRw85xXGB7mx9HLGhPwfEnTQrsaeQ qvL6B8Ky4gd2wdzN317rtP7paFyy+YuwHNqc7ZXrtv1bNEDGvRCOJ2bXWme4T7CKmb5R RiB3ZQFQgjV7/RSz7L9B9iySAzx3HnsJnEAsI= Received: by 10.150.230.7 with SMTP id c7mr4349376ybh.446.1290204170909; Fri, 19 Nov 2010 14:02:50 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id j9sm308591yha.45.2010.11.19.14.02.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 14:02:49 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 14:02:48 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 14:02:48 -0800 To: Nenhum_de_Nos Message-ID: <20101119220248.GG13317@michelle.cdnetworks.com> References: <20101119000618.GC8512@michelle.cdnetworks.com> <32aed4c0a483f26c662dd513ea718a78.squirrel@eternamente.info> <20101119013857.GE8512@michelle.cdnetworks.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Fri, 19 Nov 2010 22:02:52 -0000 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. > thanks, > > matheus