From owner-freebsd-usb@FreeBSD.ORG Sat Nov 20 05:37:53 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 9C8C41065672 for ; Sat, 20 Nov 2010 05:37:53 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from phoenix.eternamente.info (phoenix.eternamente.info [109.169.62.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4D2168FC18 for ; Sat, 20 Nov 2010 05:37:52 +0000 (UTC) Received: by phoenix.eternamente.info (Postfix, from userid 80) id 90D3A1CC3E; Sat, 20 Nov 2010 02:37:48 -0300 (BRT) Received: from 187.114.192.104 (SquirrelMail authenticated user matheus) by eternamente.info with HTTP; Sat, 20 Nov 2010 03:37:48 -0200 Message-ID: <2e6af51d55d458ce6ab55e921741a2de.squirrel@eternamente.info> In-Reply-To: <20101120012455.GK13317@michelle.cdnetworks.com> References: <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> <20101120005222.GJ13317@michelle.cdnetworks.com> <4a747b33d267e46f379607979ad57158.squirrel@eternamente.info> <20101120012455.GK13317@michelle.cdnetworks.com> Date: Sat, 20 Nov 2010 03:37:48 -0200 From: "Nenhum_de_Nos" To: pyunyh@gmail.com User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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 List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2010 05:37:53 -0000 On Fri, November 19, 2010 23:24, Pyun YongHyeon wrote: > On Fri, Nov 19, 2010 at 11:20:25PM -0200, Nenhum_de_Nos wrote: >> >> On Fri, November 19, 2010 22:52, Pyun YongHyeon wrote: >> > 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. >> >> need to recompile kernel, or just if_axe ? >> > > If you used if_axe module without "device axe" in kernel > configuration(i.e. kernel does not include axe(4) driver), > rebuilding/reloading if_axe should be enough. Otherwise, you have > to rebuild kernel and reboot. axe0: on usbus1 axe0: EEPROM data : 0x0a82, phymode : 02 axe0: attaching PHYs failed 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 axe0: attaching PHYs failed wlan0: link state changed to UP [matheus@darkside /usr/home/matheus]$ tried it twice, tried both adapters. just got this. thanks, matheus >> will do this asap. >> >> matheus >> >> >> 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, > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style