-
Notifications
You must be signed in to change notification settings - Fork 41
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
Firmware crash on TP-Link Archer C7 v2 (QCA988x) #123
Comments
This bug is similar to what 'stintel' reported some time back. The tx-callback code in the firmware has a null-pointer for one of the callback objects. I did get a bit of useful debug out of this crash (bad address is 0x0), but still no idea why it is happening. For now, I'm going to ignore this bug and see if anyone manages to reproduce it. Please let me know if you see more crashes, possibly you have a system that can reproduce this and then I might can make some more progress. |
Hello @greearb, It happened again with latest firmware and driver updates:
|
And again (x3):
|
Still happening on latest firmware:
|
Here is a new image with more debugging in this area. |
Crash log with new firmware:
|
@greearb and another crash with the firmware you provided:
EDIT: another one:
|
For now I've just noticed these crashes in the logs. Last week (same FW) I had some issues connecting with some devices, while others were still able to connect. I rebooted before I downloaded the logs however. Edit: In the log excerpt at 469359, the firmware crashes, restarts and then crashes again 5s later
|
More crashes on latest firmware (.022):
|
Hi @greearb, at this point, would more people posting their kernel logs help at all? I'm also seeing the same crashes using the ct-htt firmware. |
sure, please attach some. I'll dig through these sometime soon. |
Should I use the firmware you posted here? I was using the one that came with openwrt 19.07.5 (2020-07-02-1) |
Either is fine with me, does one firmware work obviously different than the other for you? |
I haven't tested the one you posted here. But comparing the openwrt
supplied ones, the ct-htt firmware gives me these errors, whereas the
regular ct one does not (or at least I haven't encountered it). I don't
think it matters, but I have 802.11w set to optional and am running a WPA3
and a WPA2 multi-SSID network on the 5GHz network.
…On Wed, Dec 16, 2020 at 1:35 PM Ben Greear ***@***.***> wrote:
Either is fine with me, does one firmware work obviously different than
the other for you?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHWYSHBPNZ5HDICSRXHKCDSVD4WNANCNFSM4LRU25AQ>
.
|
TP-Link Archer C7 v2 using OpenWrt master (4.19.108) and ath10k-ct 8df0a7f with HTT firmware.
The text was updated successfully, but these errors were encountered: