All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: asix usb network driver: nfg
Date: Wed, 26 Oct 2011 19:36:18 -0400	[thread overview]
Message-ID: <4EA89972.5060101@teksavvy.com> (raw)

For the longest time, the asix driver was _the_ usb network device of choice.
But for kernels of the last year or two, it simply has not been working
reliably here with a variety of 10, 100, and 1000 mbit USB devices.

When it fails, one just sees it sitting there trying to do DHCP,
but it's outbound packets never arrive at the DHCP server.
It can listen just fine, though (wireshark), so I suspect some
sort of blockage in the transmit path.

With some devices, it sometimes works when unplugged (USB) and replugged,
but usually that doesn't help at all here.

And even when it does manage to transmit and negotiate DHCP,
a suspend/resume cycle is enough to kill it again.

Google reveals that this is also the case for at least a few others,
and some distro forums have been directing troubled users to download
the vendor's latest open source driver to get things working again.

     http://www.asix.com.tw/download.php?sub=searchresult&PItemID=84&download=driver

The driver there does indeed work better with some of my devices,
and oddly enough when I uncomment the "// #define DEBUG" line
it then works perfectly for me here.  Just like the old days,
except noisier in the syslog.  :)

Even suspend/resume work again.

So, the in-kernel asix driver seems badly broken for a lot of hardware,
and the vendor driver also has a slight race somewhere that is cured
by enabling debug logging.

Is there an asix driver maintainer, or anyone else with the time
to step up and try to fix these issues?

Thanks
Mark



             reply	other threads:[~2011-10-26 23:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 23:36 Mark Lord [this message]
2011-10-26 23:40 ` asix usb network driver: nfg David Miller
2011-10-27  1:23   ` Mark Lord
2011-10-27  2:17     ` David Miller
2011-10-27 18:48       ` Mark Lord
2011-11-02 19:36       ` [PATCH] drivers/net/usb/asix: resync from vendor's copy Mark Lord
2011-11-02 19:48         ` Mark Lord
2011-11-02 20:42         ` Ben Hutchings
2011-11-02 22:44           ` Mark Lord
2011-11-09 16:25           ` Mark Lord
2011-11-09 16:34             ` Ben Hutchings
2011-11-09 16:47               ` Mark Lord
2011-11-09 16:57                 ` Mark Lord
2011-11-09 17:20                   ` Mark Lord
2011-11-09 17:31                     ` Ben Hutchings
2011-11-09 17:40                       ` Mark Lord
2011-11-09 17:48                         ` Ben Hutchings
2011-11-09 18:22                           ` Mark Lord
2011-12-05 14:41                           ` Mark Lord
2011-12-05 15:18                             ` Ben Hutchings
2011-12-06 12:44                               ` Mark Lord
2011-12-06 17:45                                 ` Ben Hutchings
2011-12-07 16:21                                   ` Mark Lord
2011-12-07 16:27                                     ` Ben Hutchings
2011-12-07 16:59                                       ` Mark Lord
2011-12-07 17:03                                         ` Ben Hutchings
2011-11-07 16:09         ` Michal Marek
2011-11-09 17:31         ` [PATCH v2] " Mark Lord
2011-11-09 17:41           ` Mark Lord
2011-11-09 17:43           ` Mark Lord
2011-11-09 17:47           ` Ben Hutchings
2011-11-09 18:27             ` Mark Lord
2011-11-09 17:49           ` [PATCH v3] " Mark Lord
2011-11-10 14:01           ` [PATCH v2] " Mark Lord
2011-11-10 16:54             ` Grant Grundler
2011-11-10 20:17               ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EA89972.5060101@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.