-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to flush queue #11
Comments
Your kernel version..? And also the output of these commands:
|
4.2.8 (-300.fc23)
|
Confirming this bug causes connection failure and the inability to reconnect(or send any tx frames probably) until the mt7630e module is removed and inserted again.
dmesg:
uname -srv: lspci -vv |grep -i -A 9 wireless:
lsusb | grep -i mediatek: I installed the latest 2.0.3a-1 github version using dkms. |
@J08nY Thanks for testing it. Though I don't recommend using the alpha branches for normal uses, those are only for testing. For normal uses, always use the release branch.:D |
I used the release branch, same bug, I only installed the alpha version to try to fix it. |
It appears that the frequency of this issue is somehow related to signal strength, If I have a really good signal I might go hours without being disconnected, however if I have poor signal it might be minutes. |
I also have this error many times, but my wifi never disconnect. A workaround could be try to disable the power managment: |
@J08nY I wouldn't say so, I have my laptop like 3 metres far from a wifi router, so the signal strength is really high, but the connection is lost anyway very quickly.
@echo-devim Tried this with no success at all. Reloading the module mt7630e on the other hand happens to work a bit more. Also, since my first comment, I've upgraded kernel to 4.4.4-301.fc23 and tried both 2.0.3a-1 and master branches. When I look into log using journalctl on the line when NetworkManager disconnects, it says:
According to NetworkManager.h this means Then it tries to reconnect:
|
I get the same issue. I have tried both master and 2.0.3a-1, on both Debian and Ubuntu. Below are the details for my Ubuntu laptop.
|
Still getting the same issue with v2.0.6. Cheers, |
I also have roughly this problem, only at office but not home. I can get it working by turning off wifi, and using rmmod/modprobe, but if I try that two times it brings down the system. |
Yep, same for me. I have a script that disconnects using NetworkManager, 2016-09-21 14:47 GMT+02:00 John Vandenberg notifications@github.com:
|
Just upgraded kernel to 4.7.0 and driver to 2.0.8 (commit d5023e7) and I seem to get far less errors. It might be just freak coincidence since I had the driver error after upgrading but currently been on wifi for hours and no error, no disconnect (note that this is indeed very unusual, before upgrade I could get maybe half an hour of basic usage until disconnect). I recommend updating (both kernel and driver) and trying it out. |
@J08nY , is it still working well for you? |
@jayvdb Hmm, tested it some more and seems I was just lucky that day. Issue is not solved on 4.7.0 kernel and 2.0.8 driver. |
I have the same problem, uname -r Kernel: 4.4.0-59-generic sudo lspci -vv |grep -i -A 9 wireless: 03:00.0 Network controller: MEDIATEK Corp. MT7630e 802.11bgn Wireless Network Adapter Subsystem: Foxconn International, Inc. MT7630e 802.11bgn Wireless Network Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mt7630e Kernel modules: mt7630e lsusb |grep -i mediatek: Bus 002 Device 006: ID 0e8d:763f MediaTek Inc. |
There is a similar issue here with a kickstarter campaign to resolve it. Maybe this will help. |
There seems to be some progress on the issue linked by @horacekmi: lede-project/source@9eacb9d |
Hi, after installing this driver, everything looked working well, but after few hours, the wifi disconnected and dmesg is full of these errors:
ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
And since the first lost connection I can't get it to connect again. Restarting system works just for few minutes, then it gets again into these errors. I don't even know where to look for further information about this.
The text was updated successfully, but these errors were encountered: