From owner-freebsd-usb@FreeBSD.ORG Fri Nov 19 21:23:35 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 5E107106566B for ; Fri, 19 Nov 2010 21:23:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 25FA08FC18 for ; Fri, 19 Nov 2010 21:23:35 +0000 (UTC) Received: by pxi1 with SMTP id 1so1201562pxi.13 for ; Fri, 19 Nov 2010 13:23:34 -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=SB0xbqPAlSb67ugqdQvOCSTNCZgPIXerXLvSjt5sYA4=; b=EHBKkLhElyjmLE/FctU2wF9QnaW1+nE/coE1O5Pm8ZP5T5W80z7lELF0zcwQRlAOin qG0R1Fh01FB1c/+0gAZnFwEpi9EqzlqM1soU36RXtJZ5iA0bCxD37ustWeHPjML3QoIq jnPUMxnSO9U7rEkXxRDQTpumXQNYFQzYdNocM= 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=vwLKNGQYC52LXACSSYf9kG+jXGUhO/tfyBzeHfTQRpX7ne6ySm8E5CpaIYEd+3CVS3 DwhSrwbS8efRIisDTTpPk61J7xIH8kW87sYARFziThNpEGUsR9bMyzIH1x/3y9bC7Jyg kmmuE1T6OaTEG7d8lSbqIZpgIlVL68MrtQkNs= Received: by 10.142.49.21 with SMTP id w21mr2258078wfw.157.1290201814467; Fri, 19 Nov 2010 13:23:34 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id y42sm2347705wfd.22.2010.11.19.13.23.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Nov 2010 13:23:33 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 19 Nov 2010 13:23:33 -0800 From: Pyun YongHyeon Date: Fri, 19 Nov 2010 13:23:33 -0800 To: Nenhum_de_Nos Message-ID: <20101119212333.GD13317@michelle.cdnetworks.com> References: <20101118202426.GB8512@michelle.cdnetworks.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9ecdf40489022c754096ac1f388a605f.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: Fri, 19 Nov 2010 21:23:35 -0000 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. > > 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 it is gigabit controller. So it should print the message I mentioned in previous mail. Are you sure you rebuild/reboot your kernel? 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.