Date: Thu, 12 Feb 2009 01:51:47 +0900 From: Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp> To: Hans Petter Selasky <hselasky@c2i.net> Cc: pyunyh@gmail.com, freebsd-usb@freebsd.org Subject: Re: USB2: [was: umass not detected correctly, axe not transmitting] AXE problems Message-ID: <sa6vdrgkjbw.wl%tamaru@myn.rcast.u-tokyo.ac.jp> In-Reply-To: <200902111657.38129.hselasky@c2i.net> References: <sa64oz1lacr.wl%tamaru@myn.rcast.u-tokyo.ac.jp> <200902110954.37659.hselasky@c2i.net> <sa6y6wdjbts.wl%tamaru@myn.rcast.u-tokyo.ac.jp> <200902111657.38129.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > ugen3.3: <ASIX Electronics> at usbus3 > > > > axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 3> on usbus3 > > > > axe0: PHYADDR 0xe0:0x18 > > > > miibus0: <MII bus> on axe0 > > > > ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus0 > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > ue0: link state changed to DOWN > > > > ue0: link state changed to UP > > > > > > > > > > > Turn on debugging: > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > And repeat test. > > > > with hw.usb2.axe.debug=15, I have: > > > > ugen3.3: <ASIX Electronics> at usbus3 (disconnected) > > pid 3244 (dhclient), uid 65: exited on signal 11 > > ugen3.3: <ASIX Electronics> at usbus3 > > axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 3> on usbus3 > > axe0: PHYADDR 0xe0:0x18 > > miibus0: <MII bus> on axe0 > > ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus0 > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > ue0: link state changed to DOWN > > ue0: link state changed to UP > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > > > What can I do now? > > Does netstat indicate any receive errors on the AXE interface? > > netstat -i Nope. Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ... ue0 1500 <Link#4> 00:90:cc:f7:bc:2e 52 0 12 0 0 ue0 1500 192.168.1.0 192.168.1.3 0 - 4 - - The latter line is the result of statically asigning an address, and then 'ping -n 192.168.1.1'ing for four seconds. > Maybe "Pyun YongHyeon" should have a look at this. > > And you are running the latest current? I updated to -current as of about an hour or two ago. > --HPS Hiroharu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?sa6vdrgkjbw.wl%tamaru>