Open ec1oud opened 10 years ago
Due to the lack of activity, I may be wasting my breath, but...
Confirmed on Arch Linux. Kernel 3.13.6-1 x86_64. Asus Zenbook UX32-VD laptop. Even compiled, installed, and insmod'd Asix kernel driver 1.9.0 (dmesg follows).
[ 8747.778169] usb 4-2: new SuperSpeed USB device number 5 using xhci_hcd
[ 8748.116072] ASIX USB Ethernet Adapter:v1.9.0 23:25:29 Mar 8 2014
http://www.asix.com.tw
[ 8748.116085] ax88179_178a 4-2:1.0 (unregistered net_device): mtu 1500
[ 8748.116346] ax88179_178a 4-2:1.0 eth0: register 'ax88179_178a' at usb-0000:00:14.0-2, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0a:cd:21:48:e5
[ 8709.983432] systemd-udevd[4183]: renamed network interface eth0 to enp0s20u2
[ 8748.151512] systemd-udevd[4372]: renamed network interface eth0 to enp0s20u2
[ 8748.472860] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2: link is not ready
[ 8748.513108] ax88179_178a 4-2:1.0 enp0s20u2: ax88179_178a - Link status is: 1
[ 8748.513170] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u2: link becomes ready
[ 8748.641151] ax88179_178a 4-2:1.0 enp0s20u2: ax88179_178a - Link status is: 0
[ 8751.587653] ax88179_178a 4-2:1.0 enp0s20u2: ax88179_178a - Link status is: 1
[ 8751.589717] ax88179_178a 4-2:1.0 enp0s20u2: Write medium type: 0x013b
[ 8751.591312] ax88179_178a 4-2:1.0 enp0s20u2: link up, 1000Mbps, full-duplex, lpa 0xC1E1
[ 8753.202721] usb 4-2: USB disconnect, device number 5
[ 8753.203125] ax88179_178a 4-2:1.0 enp0s20u2: unregister 'ax88179_178a' usb-0000:00:14.0-2, ASIX AX88179 USB 3.0 Gigabit Ethernet
[ 8753.203147] ax88179_178a 4-2:1.0 enp0s20u2: Failed to read reg index 0x0002: -19
[ 8753.203166] ax88179_178a 4-2:1.0 enp0s20u2: Failed to write reg index 0x0002: -19
[ 8753.224547] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19
[ 8753.224551] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0001: -19
[ 8753.224553] ax88179_178a 4-2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19
On ArchLinux, with kernel 3.14.2, I'm still encountering the issue. I decided to report the bug upstream. Maybe this will help to have a fix more rapidly. https://bugzilla.kernel.org/show_bug.cgi?id=75381
The device I use is a Digitus DN-3023 http://goo.gl/r8ugR6
The Ethernet USB adapter is completely unstable and even unusable; therefore, we should consider such a bug as blocking.
Btw, even if not much activity has been made on that file in the kernel tree, maybe you could rebase your git on that version. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/net/usb/ax88179_178a.c
Had exactly this problem with the same device, on Ubuntu 14.04.1 LTS, with stock kernel 3.13.0-34 on a Lenovo Yoga 13 laptop.
The problem was when I connected it to the USB 3.0 port of the laptop.
I worked it around by connecting the Ethernet USB adapter through a USB 2.0 hub, which was in turn connected to either the USB 2.0 or USB 3.0 port of the laptop. This works like a charm, allowing me to plug and unplug it again with no issues at all.
I don't have an USB 3.0 hub, so I can't tell if this is a USB 3.0 issue, or if any hub in the middle would do the job.
The hub I used was a Terminus Technology 4-port hub, 1a40:0101. This is the chip's name -- the hub is sold as a no-name piece of junk at Ebay.
I've also hit the same problem. Can confirm that it works in a USB2 port, but not USB3.
Hello. Problem reported on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269883?comments=all on 2014-01-16. To put it short: adapter unusable on USB3 port, works fine on USB2 port (with reduced performance depending on network speed and activity).
@fidergo-stephane-gourichon There are some new posts on the kernel.org bugzilla report I made, but nothing really interesting. Except maybe that since a recent NetworkManager version, the problem seems to be reduced as the device reconnects by himself. And also a guy succeeded to write a Python script mitigating issues by forcing reconnections.
Thanks wget for your comment/update. I've added this after comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269883/comments/21 . Reading activity here and following your link, what I experienced seems different. For example, problem starts immediately, not on receiving heavy traffic. Also, machine feels a little sluggish but no crash observed. Might be a different bug?
Not really. (at least I'm not an expert in driver dev nor in RX-TX values, etc. so I cannot say). What I can say, is that the same driver seems to be the cause of our issues. But yes I remember that from 3.9 to 3.14, my machine becomes sluggish as if all I/O were used. And after some times this leads to kernel panics. Since recent kernel/network stack updates, all seems to be working but I've sometimes disconnections, which could confirm what the guy said regarding NetworkManager (I'm using KDE Plasma and the latter is using underlying NetworkManager). And the adapter disconnected sometimes even after light traffic. I experienced the issue explicitly with torrent clients. As the latter uses a bunch of TCP connections for DHT (so not really huge traffic), the problem often arose when such a client was active. Also, when backuping a bunch of linux iso from my laptop, the transfer went well, but disconnections occurred during the transfer: either leading to kernel panic or not. Had the same problem when reading (loading) webpages, so not really under heavy load then. I remembered having discussed with Ubuntu kernel developers and according to what I saw, their version had more code (maybe to apply a fix for specific devices) in the file than the version made available on kernel.org.
Great (#irony). No more kernel panic, but I was unable to sync my backups with my server using that adapter. Had to continue in Wi-Fi despite lower bitrate, but at least it was stable. https://gist.github.com/wget/11ef48eba07b31adc15b Kernel 4.1.6.
I can confirm this issue on Ubuntu 16.04. Usb 2.0 port works fine, but usb 3.0 will get this error message.
It has been mentioned on the aforementioned bug report (upstream) https://bugzilla.kernel.org/show_bug.cgi?id=75381 that using a more up to date version of the driver provided by the company ASIX itself could potentially solve the problem.
I do have the latest version from ASIX website. It is still the same.
Debian, proxmox 4.4.16-1, same problem.
Arch Linux with 4.8 kernel, with or without latest version from AUR, same problem. I couldn't find a gigabit Ethernet adapter without this chipset. They all seem to use Asix. Bummer...
@mattpepin Hello there. I'm an Arch Linux user with 4.8 kernel too. When you have installed aur/asix-ax88179-dkms
make sure you specify in /etc/modules-load.d/ax88179_178a-dkms.conf
the mention ax88179_178a-dkms
, otherwise the module won't be used and the one from the kernel will be used instead.
Using the dkms version which uses more up to date source directly from ASIX (have a look at the PKGBUILD) solved most of the problems I had.
@wget Thanks, wget. It seems the official driver readme does not mention this step. They only mentioned using modprobe
, insmod
. Do you know why?
@gladiacxtylish No idea, but I think this is just because the driver was not available in the linux kernel tree at the time ASIX wrote the driver: so no risk of driver conflict at that time. The driver has been uploaded in the git repo on March 3rd, 2013 while the driver dates back from 2002 (even if USB 3.0 was not available yet at that time) if I can rely on the copyright statement:
* ASIX AX88179 based USB 3.0 Ethernet Devices
* Copyright (C) 2003-2005 David Hollis <dhollis@davehollis.com>
* Copyright (C) 2005 Phil Chang <pchang23@sbcglobal.net>
* Copyright (c) 2002-2003 TiVo Inc.
I'm also having this problem with a Buffalo lua4-u3-agt, uses the ax88179_178a driver. Works if I force USB2 via a USB2 hub, otherwise USB3 won't even pull an IP.
I have three noname usb-ethernet adapters based on ASIX88179. I didn't pay much attention to "write reg" error in dmesg because adapters always appeared to be working. But then I started to use Transmissioin and discovered that adapter can't sustain such a heavy load for a long time. After some time it begin to looks like working but does not actually transmit or receive anything. I tried in-kernel driver and driver from ASIX. I tried different kernels and did tests on ARM boards and x86 laptop. ASIX 88179 stops working under heavy network load, produced by Transmission-daemon. Interestingly enough - it works fine under iperf load... It also works without any problem under any load on a Windows system.
I filed a bug report to upstream but no one cares.
Aug 21 17:40:00 laptop kernel: [ 2566.781695] usb 2-1: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
Aug 21 17:40:00 laptop kernel: [ 2566.808337] usb 2-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 0.50
Aug 21 17:40:00 laptop kernel: [ 2566.808347] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 21 17:40:00 laptop kernel: [ 2566.808351] usb 2-1: Product: USB3.0 Hub
Aug 21 17:40:00 laptop kernel: [ 2566.808354] usb 2-1: Manufacturer: VIA Labs, Inc.
Aug 21 17:40:00 laptop kernel: [ 2566.831130] hub 2-1:1.0: USB hub found
Aug 21 17:40:00 laptop kernel: [ 2566.831329] hub 2-1:1.0: 4 ports detected
Aug 21 17:40:00 laptop kernel: [ 2566.933455] usb 1-1: new high-speed USB device number 8 using xhci_hcd
Aug 21 17:40:00 laptop kernel: [ 2567.085918] usb 1-1: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 0.50
Aug 21 17:40:00 laptop kernel: [ 2567.085925] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 21 17:40:00 laptop kernel: [ 2567.085928] usb 1-1: Product: USB2.0 Hub
Aug 21 17:40:00 laptop kernel: [ 2567.085930] usb 1-1: Manufacturer: VIA Labs, Inc.
Aug 21 17:40:00 laptop kernel: [ 2567.150832] hub 1-1:1.0: USB hub found
Aug 21 17:40:00 laptop kernel: [ 2567.151141] hub 1-1:1.0: 4 ports detected
Aug 21 17:40:02 laptop kernel: [ 2568.628584] usb 2-1.3: new SuperSpeed Gen 1 USB device number 7 using xhci_hcd
Aug 21 17:40:02 laptop kernel: [ 2568.656390] usb 2-1.3: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 2.00
Aug 21 17:40:02 laptop kernel: [ 2568.656398] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 21 17:40:02 laptop kernel: [ 2568.656401] usb 2-1.3: Product: AX88179A
Aug 21 17:40:02 laptop kernel: [ 2568.656403] usb 2-1.3: Manufacturer: ASIX
Aug 21 17:40:02 laptop kernel: [ 2568.656405] usb 2-1.3: SerialNumber: 00000001
Aug 21 17:40:02 laptop kernel: [ 2569.060022] ax88179_178a 2-1.3:2.0 eth0: register 'ax88179_178a' at usb-0000:03:00.3-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:00:00:00:00:01
Aug 21 17:40:03 laptop kernel: [ 2569.386978] ax88179_178a 2-1.3:2.1 (unnamed net_device) (uninitialized): Failed to read reg index 0x0040: -32
Aug 21 17:40:03 laptop kernel: [ 2569.394157] ax88179_178a 2-1.3:2.1 eth1: register 'ax88179_178a' at usb-0000:03:00.3-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:00:00:00:00:01
Aug 21 17:40:03 laptop kernel: [ 2569.419375] ax88179_178a 2-1.3:2.0 enx000000000001: renamed from eth0
Aug 21 17:40:03 laptop kernel: [ 2569.769635] ax88179_178a 2-1.3:2.1 eth1: Failed to read reg index 0x0040: -32
Aug 21 17:40:03 laptop kernel: [ 2570.108053] ax88179_178a 2-1.3:2.0 enx000000000001: Failed to read reg index 0x0040: -32
Same problem. Any idea?
I did more tests and as far as I can say my adapter works fine on x86 laptop with a driver from ASIX website. At least it sustained a few hours of torture by Transmission.
The same adapter quickly disconnects under Transmission load on x86 laptop when using in-kernel driver. Also the same adapter disconnects on Allwinner A10 device with any driver.
Same problem here:
[Ср янв 5 16:08:58 2022] usb 6-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[Ср янв 5 16:08:58 2022] usb 6-1: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 1.00
[Ср янв 5 16:08:58 2022] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Ср янв 5 16:08:58 2022] usb 6-1: Product: AX88179
[Ср янв 5 16:08:58 2022] usb 6-1: Manufacturer: ASIX Elec. Corp.
[Ср янв 5 16:08:58 2022] usb 6-1: SerialNumber: 0028EE52015CF8
[Ср янв 5 16:08:58 2022] ax88179_178a 6-1:1.0 eth0: register 'ax88179_178a' at usb-0000:02:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 28:ee:52:01:5c:f8
[Ср янв 5 16:08:58 2022] usbcore: registered new interface driver ax88179_178a
[Ср янв 5 16:08:58 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: renamed from eth0
[Ср янв 5 16:09:35 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: Failed to write reg index 0x000d: -110
[Ср янв 5 16:09:40 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: Failed to write reg index 0x000e: -110
[Ср янв 5 16:09:45 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: Failed to write reg index 0x000d: -110
[Ср янв 5 16:09:50 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: Failed to write reg index 0x000e: -110
[Ср янв 5 16:09:55 2022] ax88179_178a 6-1:1.0 enx28ee52015cf8: Failed to read reg index 0x0000: -110
uname -a
Linux powerman 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux
Well i solved it by plug adapter to USB2 instead USB3 In USB2 it works.
I have just discovered that on Linux Mint 20.3 with 5.15 kernel, i can fix the problem until the next reboot as follows:
sudo rmmod ax88179_178a
,After more investigation, the problem seems to be in the module loading order: ax88179_178a
has to be loaded after cdc_mbim
.
The following commands fix the problem until reboot:
# rmmod ax88179_178a
# modprobe cdc_mbim
# modprobe ax88179_178a # optional
To fix this, you can create the file /etc/modprobe.d/ax88179_178a-fix.conf
with contents softdep ax88179_178a pre: cdc_mbim
, which will ensure that cdc_mbim
is loaded before ax88179_178a
is inserted.
@lights0123, could you maybe add your workaround as an answer here?
I have 3 identical UGREEN dongles. 2 of them affected by this issue, 1 not. The dmesg shows that they differ in USB product: AX88179A (affected) vs AX88179 (good).
Having a similar issue here on Debian with a PCIe card that uses the ASIX chip. The card has 3 USB 3.0 ports and an ethernet port. I get the following errors and then the card stops working:
2023-10-06T22:38:03.886498-05:00 node1 kernel: [ 39.652066] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to read reg index 0x0001: -19 2023-10-06T22:38:03.886499-05:00 node1 kernel: [ 39.652082] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to read reg index 0x0006: -19 2023-10-06T22:38:03.886501-05:00 node1 kernel: [ 39.652094] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0006: -19 2023-10-06T22:38:03.886508-05:00 node1 kernel: [ 39.652098] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0005: -19 2023-10-06T22:38:03.886511-05:00 node1 kernel: [ 39.652102] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886512-05:00 node1 kernel: [ 39.652106] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886513-05:00 node1 kernel: [ 39.652110] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886513-05:00 node1 kernel: [ 39.652114] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886514-05:00 node1 kernel: [ 39.652118] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0002: -19 2023-10-06T22:38:03.886515-05:00 node1 kernel: [ 39.652122] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886523-05:00 node1 kernel: [ 39.652126] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0002: -19 2023-10-06T22:38:03.886525-05:00 node1 kernel: [ 39.652134] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to read reg index 0x0001: -19 2023-10-06T22:38:03.886526-05:00 node1 kernel: [ 39.652141] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to read reg index 0x0001: -19 2023-10-06T22:38:03.886526-05:00 node1 kernel: [ 39.652146] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0001: -19 2023-10-06T22:38:03.886527-05:00 node1 kernel: [ 39.652150] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x001f: -19 2023-10-06T22:38:03.886528-05:00 node1 kernel: [ 39.652154] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x0019: -19 2023-10-06T22:38:03.886536-05:00 node1 kernel: [ 39.652158] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x001f: -19 2023-10-06T22:38:03.886538-05:00 node1 kernel: [ 39.652162] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000d: -19 2023-10-06T22:38:03.886539-05:00 node1 kernel: [ 39.652166] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000e: -19 2023-10-06T22:38:03.886540-05:00 node1 kernel: [ 39.652170] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000d: -19 2023-10-06T22:38:03.886540-05:00 node1 kernel: [ 39.652178] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to read reg index 0x000e: -19 2023-10-06T22:38:03.886541-05:00 node1 kernel: [ 39.652182] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000d: -19 2023-10-06T22:38:03.886548-05:00 node1 kernel: [ 39.652186] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000e: -19 2023-10-06T22:38:03.886550-05:00 node1 kernel: [ 39.652190] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000d: -19 2023-10-06T22:38:03.886551-05:00 node1 kernel: [ 39.652193] ax88179_178a 9-1:1.0 enx00133bab605e: Failed to write reg index 0x000e: -19
Try: modprobe kmod-usb-net-cdc-mbim (or whatever the module is called on your distro) in addition to kmod-usb-net-asix-ax88179. I use a Raspberry Pi 4 with OpenWrt.
same problem
uname -a
dmesg
[ 315.674083] ax88179_178a 2-1:1.0 enx00051bc1296c: unregister 'ax88179_178a' usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet [ 315.727492] ax88179_178a 2-1:1.0 enx00051bc1296c (unregistered): Failed to write reg index 0x0002: -19 [ 315.727518] ax88179_178a 2-1:1.0 enx00051bc1296c (unregistered): Failed to write reg index 0x0001: -19 [ 315.727530] ax88179_178a 2-1:1.0 enx00051bc1296c (unregistered): Failed to write reg index 0x0002: -19
same problem
You have the problem after installing the module?
Do you use OpenWrt?
Do lsusb -t
What hardware?
Is it a USB-C to ethernet adapter or regular USB?
I've tried various versions of the driver including 1.9.0, and when I plug in the adapter I get errors like this
[34688.799667] usb 3-2.2: new SuperSpeed USB device number 11 using xhci_hcd [34689.131320] ASIX USB Ethernet Adapter:v1.9.0 07:44:41 Jan 10 2014 http://www.asix.com.tw [34689.131337] ax88179_178a 3-2.2:1.0 (unregistered net_device): mtu 1500 [34689.131900] ax88179_178a 3-2.2:1.0 eth0: register 'ax88179_178a' at usb-0000:00:14.0-2.2, ASIX AX88179 USB 3.0 Gigabit Ethernet, 80:3f:5d:09:95:9f [34689.174196] systemd-udevd[16550]: renamed network interface eth0 to enp0s20u2u2 [34690.123136] usb 3-2.2: USB disconnect, device number 11 [34690.277039] ax88179_178a 3-2.2:1.0 enp0s20u2u2: unregister 'ax88179_178a' usb-0000:00:14.0-2.2, ASIX AX88179 USB 3.0 Gigabit Ethernet [34690.293753] ax88179_178a 3-2.2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19 [34690.293770] ax88179_178a 3-2.2:1.0 (unregistered net_device): Failed to write reg index 0x0001: -19 [34690.293774] ax88179_178a 3-2.2:1.0 (unregistered net_device): Failed to write reg index 0x0002: -19
It repeats over and over.
Sometimes I get lucky when the adapter is plugged in for the first time after booting, but not the next time.
This is on a Thinkpad Helix, Arch Linux 64-bit, kernel currently 3.12.6-1
I wonder if it could be a USB 3 problem instead, since I don't see others reporting such messages? It's the only USB 3 device I have so far, but a USB 2.0 network adapter works fine. (And a really old 3Com HED1045USB is also kindof flaky.)
The adapter is this one
http://dx.com/p/usb-3-0-gigabit-lan-ethernet-adapter-black-213357