axe(4) woes

[Roy Marples]

Hi List

I recently got hold of an axe(4) device. I have tried it on netbsd-6
amd64 and i386 -current.
Both have the same issue - any traffic results in this

axe0: usb watchdog timeout
axe0: usb error on tx: IN_PROGRESS
axe0: usb error on tx: TIMEOUT

It can see incomming traffic fine, it just can't send out. I've verified
this with tcpdump at either end.
However, on netbsd-6 amd64 the kernel things it sent the traffic
according to tcpdump, but on -current i386 tcpdump doesn't record
anything sent.

Any ideas to debug and ideally this? I'm using this device to try and
add more physical interfaces to my one interface server to better manage
wired, wireless.
As a metric, does anyone have a working axe(4)?

dmesg:
axe0 at uhub4 port 3
axe0: ASIX Electronics AX88178 USB 2.0 gigabit ethernet controller, rev
2.00/0.01, addr 2
axe0: Ethernet address 8c:ae:4c:ff:4c:03
rgephy0 at axe0 phy 2: RTL8169S/8110S/8211 1000BASE-T media interface,
rev. 2
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto

Thanks

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Petri Laakso]

Post by Roy Marples
Hi List

Hi

Post by Roy Marples
As a metric, does anyone have a working axe(4)?

For me, on evbarm/imx23_olinuxino it has been great. I haven't noticed single
failure on my network connection because of it.

from dmesg:
axe0 at uhub0 port 1
axe0: vendor 0x2001 product 0x1a02, rev 2.00/0.01, addr 2
axe0: Ethernet address bc:f6:85:d7:4e:f6
ukphy0 at axe0 phy 16: OUI 0x007063, model 0x0008, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Takahiro HAYASHI]

On Thu, 7 Nov 2013 08:24:00 +0200 (EET)

Post by Roy Marples
Hi List

Hi

Hi,

Post by Roy Marples
As a metric, does anyone have a working axe(4)?

tried 4 axes on NetBSD/amd64 6.99.25, all work fine.

axe0 at uhub5 port 2
axe0: ASIX Electronics AX88178 USB 2.0 gigabit ethernet controller, rev 2.00/0.01, addr 2
axe0: Ethernet address 00:22:xx:xx:xx:xx
ukphy0 at axe0 phy 24: OUI 0x00c08f, model 0x000b, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
# ifconfig axe0 inet6 fe80::1:69
# ping6 -n fe80::66%axe0
PING6(56=40+8+8 bytes) fe80::1:69%axe0 --> fe80::66%axe0
16 bytes from fe80::66%axe0, icmp_seq=0 hlim=64 time=13.320 ms
16 bytes from fe80::66%axe0, icmp_seq=1 hlim=64 time=0.348 ms
16 bytes from fe80::66%axe0, icmp_seq=2 hlim=64 time=0.245 ms
16 bytes from fe80::66%axe0, icmp_seq=3 hlim=64 time=0.339 ms
^C
--- fe80::66%axe0 ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.245/3.563/13.320/6.505 ms

axe0 at uhub5 port 2
axe0: BayNETGEAR USB 2.0 Fast Ethernet Adapter, rev 2.00/0.01, addr 2
axe0: Ethernet address 00:09:xx:xx:xx:xx
rlphy1 at axe0 phy 3: RTL8201L 10/100 media interface, rev. 1
rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
# ifconfig axe0 inet6 fe80::1:69
# ping6 -n fe80::66%axe0
PING6(56=40+8+8 bytes) fe80::1:69%axe0 --> fe80::66%axe0
16 bytes from fe80::66%axe0, icmp_seq=0 hlim=64 time=0.692 ms
16 bytes from fe80::66%axe0, icmp_seq=1 hlim=64 time=0.318 ms
16 bytes from fe80::66%axe0, icmp_seq=2 hlim=64 time=0.206 ms
^C
--- fe80::66%axe0 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.206/0.405/0.692/0.254 ms

axe0 at uhub5 port 2
axe0: ASIX Electronics AX88772 USB 2.0 10/100 ethernet controller, rev 2.00/0.01, addr 2
axe0: Ethernet address 00:90:xx:xx:xx:xx
ukphy0 at axe0 phy 16: OUI 0x007063, model 0x0001, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
# ifconfig axe0 inet6 fe80::1:69
# ping6 -n fe80::66%axe0
PING6(56=40+8+8 bytes) fe80::1:69%axe0 --> fe80::66%axe0
16 bytes from fe80::66%axe0, icmp_seq=0 hlim=64 time=0.629 ms
16 bytes from fe80::66%axe0, icmp_seq=1 hlim=64 time=0.291 ms
^C
--- fe80::66%axe0 ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.291/0.460/0.629/0.239 ms

axe0 at uhub5 port 2
axe0: Melco LUA-U2-KTX Ethernet, rev 2.00/0.01, addr 2
axe0: Ethernet address 00:07:xx:xx:xx:xx
rlphy1 at axe0 phy 3: RTL8201L 10/100 media interface, rev. 1
rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
# ifconfig axe0 inet6 fe80::1:69
# ping6 -n fe80::66%axe0
PING6(56=40+8+8 bytes) fe80::1:69%axe0 --> fe80::66%axe0
16 bytes from fe80::66%axe0, icmp_seq=0 hlim=64 time=0.580 ms
^C
--- fe80::66%axe0 ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.580/0.580/0.580/0.000 ms

--
t-hash


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

Hi

Post by Takahiro HAYASHI
tried 4 axes on NetBSD/amd64 6.99.25, all work fine.

Myself and nick@ have been working on a patch [1] to add GPIO
programming for more PHY hardware based on the FreeBSD axe(4) driver.
This makes my axe(4) work very nicely on i386 current, will test on my
amd64 NetBSD-6 shortly.

Can you test the patch [1] and check that it does not break your axes
please?

Thanks

Roy

[1] http://www.netbsd.org/~roy/if_axe.diff

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Takahiro HAYASHI]

Hi,

On Thu, 07 Nov 2013 15:08:37 +0000

Hi

Post by Takahiro HAYASHI
tried 4 axes on NetBSD/amd64 6.99.25, all work fine.

This makes my axe(4) work very nicely on i386 current, will test on my amd64 NetBSD-6 shortly.
Can you test the patch [1] and check that it does not break your axes please?

My axes work fine as much as before patch.

I assign unique local ipv6 unicast address to axe under test
and confirm ping6 replies from remote host.


Thanks,
--
t-hash


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de