MT7603 (2.4ghz) - Main Issue #149
Comments
|
For me only these warnings every 3/4 days, connection is stable with ~ 10 devices Thanks |
|
OpenWrt SNAPSHOT r6297 Xiaomi 3G |
|
With build r6297 I have many warnings and router (Xiaomi 3G) it has restarted itself twice in 24 hours |
|
I noticed that the warning "Workqueue: phy0 mt7603_mac_work [mt7603e]" is obtained every time I transfer large files (2.4 GHz) between clients and can also be obtained with iperf... |
|
Router (Xiaomi 3G with r6297) has restarted itself again after 19 hours. |
|
Router: WE3526 Issue: Wifi stays connected but cannot ping router (happens randomly after some usage) Log has nothing relevant. |
|
@barhom Don't use option disassoc_low_ack='0' |
|
@Mafesa - we were, but in our testing it didn't make any difference.
…On Wed, Feb 28, 2018 at 11:16 PM, MaFeSa ***@***.***> wrote:
@barhom <https://github.com/barhom> are you using option
disassoc_low_ack='0' ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TckbCvzXjylsb9wVdNHpG-DympRShks5tZ5IsgaJpZM4SCrz0>
.
|
|
@nbd168 , @Mafesa , @barhom - I am working with @slthomason on our MT7603 issues, and have some additional information. We are testing the throughput on MT7603 & MT7612 - on the ZBT WE1326. We are running on the latest commit. I am using Iperf 3.1 to test this. During my last test, I had two iperf clients running simultaneously against MT7603 - and eventually one of them "locked up". One machine was connected, but unable to communicate with the AP (same issue as described by @barhom) . There were two other devices also connected to this radio, and they were working fine. To be clear, here is what I saw on the machine having issues: Windows shows as connected, but offline. Pings and Tracert failed.
Here is the station dump, with some useful information. The device having issues was: 60:67:20:2a:f2:ec root@ph:/proc# iw wlan0 station dump Station 54:8c:a0:79:52:6b (on wlan0) Station 60:67:20:2a:f2:ec (on wlan0) Here is an important observation: During this behavior, "expected throughput" disappears. Another observation: The txbit rate always returns to "6.5 MBit/s MCS 0" during the issue For comparison, here is the station dump when this device is connected properly: Station 60:67:20:2a:f2:ec (on wlan0) We have been able to "fix" this behavior two ways:
ubus call hostapd.wlan0 del_client '{"addr":"60:67:20:2a:f2:ec", "reason":1, "deauth":true, "ban_time":10}' This command kicks the client, and the client immediately reconnects successfully. However, this fix only seems to last about 5 - 10 minutes, before this same behavior returns. I have wireless logging set to its most verbose setting, and see nothing in logread or dmesg to indicate an issue. EDIT: Forgot to include our wireless config: config wifi-device 'radio0' config wifi-iface 'default_radio0' config wifi-device 'radio1' config wifi-iface 'default_radio1' |
|
r6350 with this (cda627f) for me is very stable, I have transferred more than 40 GB with 2.4GHz and 60GB with 5GHz without any kernel warning. |
|
@Mafesa |
|
No, my config is simple: After 5 days uptime and many data over wireless I have only this warning No more Workqueue: phy0 mt7603_mac_work [mt7603e] warnings. OpenWrt SNAPSHOT r6380-606cea8 / LuCI Master (git-18.062.27847-1e46a67) |
|
I see. I don't have option noscan, will add it now and see how it goes.. My config now looks like: config wifi-device 'radio0' |
|
Try tomorrow snapshot, probabily nbd had fixed these warnings. |
|
With 7603 (Xiaomi 3G) there are no errors but it is not possible to connect to the new virtual wireless network. |
|
I suggest separating and tagging MT7603 and MT7628. |
|
@nbd168 Any ideas on this one? We are able to readily reproduce this behavior. We have written a script which consistently bumps the client and works for a short time, but then the problem occurs again. But it is that readily reproducible - even on the latest build. Any ideas? |
|
@nbd168 is no one else seeing this? |
|
I am seeing this on a daily basis. |
|
If you have php, you can run that script and it will log times that it has
happened. If you don't have php, that script can easily be written to an
ash script. But it will log on the router the times that this happens.
@nbd168 <https://github.com/nbd168> - do you want @CR-Ryan
<https://github.com/cr-ryan> to split this out into a separate issue? I
know this thread has gotten muddy with other issues.
Thanks!
Spencer
…On Tue, Mar 20, 2018 at 2:38 AM, barhom ***@***.***> wrote:
I am seeing this on a daily basis.
My laptop can be connected to wifi but nothing goes through. Unfortunately
I have been unable to run an "iw wlan0 station dump" when this happens as I
dont have a wired computer at this moment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcqMVuQBtLhCG3B2foE9j70bl_hdvks5tgM4LgaJpZM4SCrz0>
.
|
No not anymore, disabled 2.4Ghz because of this problem. :p It is unusable right now for my iPhone7, trying every new commit. (Not tried the new driver of March 19.) The same? bug happens in 5Ghz too, but far less often. |
|
Just compile 2d08440 , against an old kernel same issue as before. I will try with newer kernel and commits that were made just few minutes ago.
|
|
On recent lede version with mt76 e2eedc9 |
|
With latest version it crashes 2-3 times a day. I use hostapd not wpad-mini. My hostapd conf file: |
|
The 2.4Ghz wifi runs now much better with the lastest commits. Thank you nbd, updatete for your endless effort to improve the driver. 😃 Thank you openwrt team for this nice peace of software. |
|
My Xiaomi 3G has eight days of uptime (from this) with no warnings and problems. |
|
@Mafesa can you please give the details of your setup? What commit? What software do you use (hotsapd, wpad-mini)? What configuration file? |
|
@pparent76 2.4 GHz - 10 clients |
|
Hi. I have two Archer C50 v3 and I am using latest snapshots (currently OpenWrt SNAPSHOT r6761-ddb70e7 / LuCI Master (git-18.115.55974-e56d9f4)). Wifi 2.4 is really unstable. Adding the option "disassoc_low_ack 0" increased stability but my two routers need to be restarted at least twice a day. The log shows behaviors similar to the one described by @Mafesa . 2018-04-30T08:52:26+01:00 ap2 hostapd: wlan0: STA 00:08:22:62:55:39 MLME: MLME-DEAUTHENTICATE.indication(00:08:22:62:55:39, 3) My current config is: config wifi-device 'radio0' config wifi-iface 'default_radio0' config wifi-device 'radio1' config wifi-iface 'default_radio1' |
|
@Mafesa just to make sure to understand, where did you get your config file from? The default one from a snapshot firmware is like below which is quite different (for exemple htmode): |
I'm using LuCI for wireless configuration and |
|
I can confirm that even with wpad-mini and your conf file I get the following crash: I'm not sure why you don't have it. In order to make tests I put the router on a public space. So many different kind of devices may access it. You may not have the same kind of devices connected to it. |
@pparent76 |
|
No ZBT wg-3526 |
|
We also are using the ZBT WG3526 and a variant of it - ZBT WE1326. Both
have the 2.4Ghz as mt7603 and 5Ghz as MT7612e. I believe these are the
same as a Xiaomi.
…On Wed, May 9, 2018 at 6:45 AM, Pierre Parent ***@***.***> wrote:
No ZBT wg-3526
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcieYO7WkhHcgsd9NMpH6NH8_mzkXks5twvLugaJpZM4SCrz0>
.
|
|
@pparent76 I see that you are using coova, have you tried to disable it? |
|
We aren't using it, and have still had the problem.
…On Wed, May 9, 2018 at 7:09 AM, MaFeSa ***@***.***> wrote:
@pparent76 <https://github.com/pparent76> I see that you are using coova,
have you tried to disable it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TctERWFZLBQx9qcYXFbO_Ulog3NCyks5twviIgaJpZM4SCrz0>
.
|
|
#167 <-- That thread has not been
resolved. We are still having this issue. Please don't close it. We can
consistently reproduce it. Setting to Legacy is not a resolution - we
would really like to get the speed of HT40. Legacy is extremely slow.
…On Wed, May 9, 2018 at 7:37 AM, MaFeSa ***@***.***> wrote:
With Xiaomi Router 3G I've never had kernel panics.
Can it be a specific problem with ZBT WG3526?
I think, however, that this and this
<#167> issues are to be closed.
It is better to open an issue for every problem and for yours there is
this <#121>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcmspCEwzHKbnqmFtcfZz6Zr5R5W1ks5twv8cgaJpZM4SCrz0>
.
|
Each time i've tested, with wifi disabled no crashes were recorded. |
|
It is not a crash. Please read the original post.
…On Wed, May 9, 2018 at 8:03 AM, Pierre Parent ***@***.***> wrote:
Can it be a specific problem with ZBT WG3526?
Each time i've tested, with wifi disabled no crashes were recorded.
Plus Xiaomi Router 3G seems to have the exact same hardware as 3526
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcqmHFE9Mffh7shPVbQr7gKAjc_Kzks5twwUmgaJpZM4SCrz0>
.
|
|
Others are reporting the same issue with the Xiaomi. You as well said you
could repro if not set to Legacy.
On Wed, May 9, 2018 at 8:05 AM, Spencer Thomason <spencer.thomason@gmail.com
… wrote:
It is not a crash. Please read the original post.
On Wed, May 9, 2018 at 8:03 AM, Pierre Parent ***@***.***>
wrote:
> Can it be a specific problem with ZBT WG3526?
> Each time i've tested, with wifi disabled no crashes were recorded.
> Plus Xiaomi Router 3G seems to have the exact same hardware as 3526
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#149 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AB0TcqmHFE9Mffh7shPVbQr7gKAjc_Kzks5twwUmgaJpZM4SCrz0>
> .
>
|
|
@slthomason you're confusing, it's a different problem than that of @pparent76
I repeat @pparent76 I see that you are using coova, have you tried to disable it? |
|
Ok. Just please don't close #167
then. You said earlier you thought it was closed. This issue (#149) is
resolved for us.
…On Wed, May 9, 2018 at 8:11 AM, MaFeSa ***@***.***> wrote:
@slthomason <https://github.com/slthomason> you're confusing, it's a
different problem than that of @pparent76 <https://github.com/pparent76>
This is why it is better to keep separate issues!
@pparent76 <https://github.com/pparent76> has kernel panic and it's a
different thing.
Each time i've tested, with wifi disabled no crashes were recorded.
I repeat @pparent76 <https://github.com/pparent76> I see that you are
using coova, have you tried to disable it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TckV7dSHGaj1waS4COKMHmzFj-Gzmks5twwcWgaJpZM4SCrz0>
.
|
No but it is not that easily doable. As I'm testing in real world situation, and in a public space (testing manually is way too long as crashes happen on average once per day or two with many users connected). I will see if I can find a way to test without coova-chilli, in the following weeks. Although with coova-chilli used on wired interface and no wifi, there are no crashes. |
|
I'm experiencing these problems, mainly 20% or more packet loss, on VoCore2 with the mt7603e chip. Apparently it also works with a binary driver from the manufacturer, but it's for an older kernel and I'd rather not use it anyway. We're using IBSS and currently have this config: config wifi-device 'radio0' config wifi-iface 'radio0_adhoc' |
|
@laadayush AFAIK the proprietary driver does not support adhoc so it's not a viable alternative for us. Do correct me if I'm wrong. Thanks. |
|
But that proprietary version is vulnerable to KRACK ATTACKS isn't it? |
|
Not sure if it is entirly due to mt76 driver, but I tested latest version. After a while the wifi is not emitted anymore. Hostapd process does not respond and is unkillable even with kill -9 Then any network command like ifconfig or hostapd or /etc/init.d/network restart, ... is freezing the console. (Even ctrl+c does not reply). Although, the network itself is still working. If you want to know more I still have my router in this freezy state and I can try other commands. I've already seen this, but I cannot remember when, and what was the solution. |
|
With commit 792dbe0 (still not happening with wifi disabled) |
|
you should've used mt7602 chipset. is better than 7603 |
|
Haha ... nice, but already invested a lot in this hardware, and it has
7603.
Spencer
…On Sun, Jul 8, 2018 at 3:08 PM psyborg55 ***@***.***> wrote:
you should've used mt7602 chipset. is better than 7603
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB0TcnY72zuW7z3MKqq0iByFn1vq6pewks5uEoLNgaJpZM4SCrz0>
.
|
|
I have massive Wifi disconnection problem with Archer C50 and OpenWrt 18.06 on both 2.4 and 5 GHz. Option |
|
I am closing this issue. I hope that everyone who have issues with MT7603 opens a new issue writes a detailed report on what the issues are. |
|
@CR-Ryan I have the same device ZBT WE1326 and haven't been able to get 5Ghz working. Can you please point me to the last working commit and some sample settings corresponding to it. Thanks. |
Hello,
I thought that maybe we should try to put together all the different issues that everyone is facing with 2.4ghz on MT7603 (specifically this chipset) into this main issue that everyone can easily follow.
I suggest closing the following issues:
#26, #66, #90, #107, #121, #136, #146
And then for anyone that still have issues on MT7603 write us here.
Please always mention which TARGET device you are using and make sure you are on trunk when reporting.
Also mention if you are using disassoc_low_ack='0' or not (default is 1)
The text was updated successfully, but these errors were encountered: