Re: axe(4) (Belkin F5D5055) problems

On Friday 27 March 2009, Nikolay Denev wrote:
> Hello,
>
> I'm running -current from 23.03.09 and I'm experiencing some axe(4)
> problems.
> Basically the network connection works but when some more serious
> traffic hits the
> interface (i.e. torrent download) it then dies, ifconfig down/up
> does not help, only replugging of the adapter.
>
> I've tried running with hw.usb2.axe.debug=15 and the output was many
> lines of:
>
>     axe_bulk_write_callback:853: transfer complete
>
> then a pause of several seconds and the kernel begins to print :
>
>     axe_bulk_write_callback:925: transfer error, USB_ERR_TIMEOUT

If you start seeing timeouts, then the device has probably died. What happens 
if you try:

usbconfig -u XXX -a YYY reset

where XXX and YYY matches the numbers after "ugen" for your device.

NOTE: The if-net link will be reset.

--HPS

>
> Another strange thing that I noticed is that, while the interface
> seems to be
> connected and working, if I type many times ifconfig ue0 consecutively
> most of the time it would show different settings for the auto
> negotiated link.
> I.e. it would cycle between 100baseTX-FDX, 1000baseT-FDX, no carrier,
> 100BaseT-FDX hw-loopback and 1000BaseT-FDX hw-loopback.
>
> The switch does not seem to register link flaps.
>
> The kernel messages for the interface are :
>
>     ugen2.5: <Belkin Components> at usbus2
>     axe0: <Belkin Components F5D5055, rev 2.00/0.01, addr 5> on usbus2
>     axe0: PHYADDR 0xe0:0x01
>     miibus0: <MII bus> on axe0
>     ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
>     ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
> 1000baseT, 1000baseT-FDX, auto
>     ue0: <USB Ethernet> on axe0
>     ue0: Ethernet address: 00:11:50:xx:xx:xx
>
> devinfo -vr | grep phy
> ukphy0 pnpinfo oui=0xa0bc model=0x1 rev=0x2 at phyno=1