usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic

[Pyun YongHyeon]

On Thu, Nov 26, 2009 at 08:40:04AM +0000, Hans Petter Selasky wrote:
> The following reply was made to PR usb/140883; it has been noted by GNATS.
> 
> From: Hans Petter Selasky <hselasky at c2i.net>
> To: freebsd-usb at freebsd.org
> Cc: sub mesa <sub.mesa at gmail.com>,
>  freebsd-gnats-submit at freebsd.org
> Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic
> Date: Thu, 26 Nov 2009 09:32:43 +0100
> 
>  On Thursday 26 November 2009 03:59:55 sub mesa wrote:
>  > >Number:         140883
>  > >Category:       usb
>  > >Synopsis:       axe(4) USB gigabit ethernet hangs after short period of
>  > > traffic Confidential:   no
>  > >Severity:       serious
>  > >Priority:       medium
>  > >Responsible:    freebsd-usb
>  > >State:          open
>  > >Quarter:
>  > >Keywords:
>  > >Date-Required:
>  > >Class:          sw-bug
>  > >Submitter-Id:   current-users
>  > >Arrival-Date:   Thu Nov 26 03:00:11 UTC 2009
>  > >Closed-Date:
>  > >Last-Modified:
>  > >Originator:     sub mesa
>  > >Release:        FreeBSD 8.0-RELEASE i386
>  > >Organization:
>  > >Environment:
>  >
>  > FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET
>  > 2009     xor at xor:/usr/obj/usr/src/sys/XOR  i386
>  >
>  > >Description:
>  >
>  > I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip
>  > supported by the axe(4) driver in FreeBSD 8.0. It works, but it 'freezes'
>  > or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 minutes
>  > will cause the device to freeze. This has been happening since a long time
>  > on 8.0, ever since i bought the device and was running one of the early
>  > beta's. Upgrading to the final release of 8.0 did not resolve the issue.
>  >
>  > Googling on the problem i found this mailinglist thread:
>  > http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html
>  >
>  > However, there doesn't seem to be a single conclusion. Even though my
>  > product ("Belkin F5D5055") seems to be supported according to the axe(4)
>  > manpage, it doesn't get detected as such, rather with a vendor id. Quoting
>  > dmesg output:
>  >
>  > axe0: <vendor 0x050d product 0x5055, rev 2.00/0.01, addr 2> on usbus4
>  > axe0: PHYADDR 0xe0:0x01
>  > miibus1: <MII bus> on axe0
>  > ue0: <USB Ethernet> on axe0
>  >
>  > May i suggest removing the Belkin F5D5055 from the supported devices list
>  > in the axe(4) manpage, until a fix has been committed? I specifically
>  > bought the device believing it would work since it was explicitly listed in
>  > the manpage. As of 8.0, it doesn't even get detected by name. It is of
>  > course possible my device is of a different revision.

I frequently see some vendors do not change their model name even
though the controller's internal chipset/PHY was changed. I guess
the original FD5055 have used different PHY so it might have worked
at that time.

>  >
>  > I would be happy to try any patches.
>  >
>  > Also see:
>  > http://forums.freebsd.org/showthread.php?t=8661
>  >
>  > >How-To-Repeat:
>  >
>  > Connect axe(4) gigabit ethernet device
>  > Send/receive packets using the ueX ethernet device
>  > Device will stop receiving/transmitting packets after a short while
>  >

I remember some user also reported instability of axe(4) on Belkin
F5D5055. I'm not sure what PHY driver was attached to your
controller but it could also be a variant of LSI TruePHY.
Would you show me the output of "devinfo -rv | grep phy"?