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
FS#2018 - Wifi stops working until reboot #6981
Comments
psyborg: Which device revision, what error messages in log do you get. Post kernel logs and more info if you expect bug to get solved! |
misterti: Attached is a kernel log copied from luci. It should also contain all data of the device. |
y.salnikov: Same problem with same dmesg output on d-link dir-620 D1. |
psyborg: try solution from comment in sub-task |
misterti: @Psyborg |
psyborg: obviously, the ones linked on patchwork are not. for your device you need first one only, 2nd patch is for mt7620 devices. patches to remove (with prefixed numbers) are integrated |
y.salnikov: So, just suppressing printk is enough to fix bug? |
misterti: how does that work then? When will this patch be integrated into dev build? |
psyborg: it is enough to fix interface hang. a bug itself is most likely insignificant. improper bug printout caused more problems than bug itself. i can't tell whether the wifi still freezes when printout is moved to rt2x00_dbg context and debugging features enabled, but printing it from within rt2x00_err context is wrong. as a reference, when porting several RT6352 calibration routines i did something similar in one of these and got malformed rf register values, calibration failure, perhaps even a crash but who would remember exactly... |
misterti: I think it's time for a new router, i'm getting too old for this |
y.salnikov: Built image with mentioned patch, not a single hang for now. |
misterti: Great, can you share rt2x00lib.ko? |
psyborg: did you also remove patches 701-705? if not try without these too since they cause throughput regression |
y.salnikov: There is no 701-705 patches in tree. I don't think module will be helpfull but here it is. |
misterti: Thanks, As much as i read about the overlay filesystem in openwrt, it should be possible to replace a file from /rom |
y.salnikov: Maybe so, but kernel version in prebuild image differ from my 4.14.93. |
misterti: Yea, it didn't work, kernel panicked. Can you please send me the image instead? I had to unbrick it, so i'm starting from scratch anyway. Maybe a link if it's too big for attachment? Thanks |
y.salnikov: You know that we have different routers with different SoCs, right? |
misterti: So that's the reason why kernel panicked :))) This fact completely slipped past me. Anyways, your built image for my router is working. Let's see if wifi holds, i'll report back. |
y.salnikov: Well, bad news. Interface just hangs with exactly same messages. Maybe i need change printk level? root@OpenWrt:~# cat /proc/sys/kernel/printk |
misterti: Same for me, i see the same messages in kernel log when wifi drops, it happens in a few minutes of high speed download. Are you sure that the patch was integrated correctly into the build? |
y.salnikov: Looks like it use kernel that was built first time. Strange, i am sure i ran make distclean command before build every time. |
y.salnikov: Redownload all build system. I slightly change message string in the patch to make sure that the patch is applying. In source code all ok, but when i grep rt2x00lib.ko it show original string. |
misterti: I decided to give it a try and i succeeded. I am now at 4.14.95. You need to copy the patch to "package/kernel/mac80211/patches/rt2x00/", then it works. You'll also find patches 701-705 to remove in that folder. Name the patch 777-.patch. After the build is done, the .ko file should not contain the string anymore, because release version removes the dbg prints. |
y.salnikov: Thanks. |
misterti: This is still not fixed on my router. The patch to remove the error message did not fix the issue. It still happens, but not as often as it did before the error message patch. There must be an unattended race condition in the driver, which causes the issue, and this race condition was even more prone to happen when additional time was lost by printing the error message. |
misterti: ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x010c, type=4 There are multiple lines of this message, some with different signal, like signal=0x010a,signal=0x010b After this, no more wifi. It is still connected, but no more data. And a reconnect is not possible |
misterti:
Asus RT-N56U, old, known, still unresolved problem with wifi drop, because of the rt2x00 driver. Wifi will drop with this driver at high speed download. Queue full and friends condition will occur in driver.
Reproduce:
try a large file download over wifi, when speed reaches 5Mb/s or over, driver will eventually fail in a very short time until reboot, every time.
The text was updated successfully, but these errors were encountered: