workqueue restart seem to cause another crash
https://pastebin.com/pyVYMfNF
Maybe smth should be cleared beforehand?
edit: Sorry @hnyman for wrong thread again
No problem. Good that somebody is active 
Ps. I just noticed that https://github.com/lede-project/source/commit/c03d4317a6bc891cb4a5e89cbdd77f37c23aff86 has broken the qcom tsens thermal driver in 17.01. Backports of Broadcom-specific stuff by @rmilecki is polluting all Linux targets and R7800 build for 17.01 now fails (all ipq806x builds now fail in buildbot, too: http://release-builds.lede-project.org/17.01/images/builders/ipq806x%2Fgeneric )
Yeah, I've noticed that build fails. The fix is part of
As for tsens - I suppose it's because of inconsistent https://github.com/dissent1/r7800/blob/sta49/target/linux/ipq806x/patches-4.9/0063-2-tsens-support-configurable-interrupts.patch
But last time I checked it was ok, not sure if it was before or after the upstream changes.
No, the 17.01 breakage (with kernel 4.4) is due to backporting a Broadcom thermal driver to global Linux generic patches instead of Broadcom targets. Respective ipq806x patches are in linux/ipq806x and patch the same files.
Ah, so patch applications fails and not the driver itself in k4.4?
Yes.
And funnily enough, mtd patches from the same author seem to now break ipq806x builds in master... 
http://phase1.builds.lede-project.org/builders/ipq806x%2Fgeneric
EDIT: should be fixed in master (the kernel bump commit included the fix)
Hi @hnyman differences between r3437 and r3439?. The otp wifi patch?
I'm running the r3437 release with the MTD mod .... should i rebuild and upgrade?
Thx!
See for yourself:
lede1701-r3437-a6b5ddfd9b-20170611
lede1701-r3439-c16326cfed-20170619
https://git.lede-project.org/?p=source.git;a=shortlog;h=refs/heads/lede-17.01
one dropbear fix (c16326cfed) plus possible changes in packages & LuCI feeds.
I see, thx! 
Well, move it then.
I recently built LEDE for the r7800 using LEDE master/head.
The wired aspect of the router was very solid. I have a gigabit connection (fiber) and wsa able to really push the wired WAN-to-LAN and was getting nearly 900mbps throughput.
I know people won't necessarily have a gigabit connection like me so it could be potentially difficult to stress the wifi like I am. But if there is any advice as to what build is recommended as stable in terms of wifi (i can sacrifice a few mbps as long as stability is there), I would really appreciate it.I happen to have AC wifi cards which connect to the router at around 800mbps+ and then when I run speedtests through the wifi device (laptop or phone both are capable of 800+mbps connections), i could notice a certain throttle and as soon as I noticed it, looking in the logs there were some stack trace and kernal warnings realating to ath10k. and within a few seconds the 5GHz wifi would just disappear. 2.4GHz was still available. There was no way to bring back the 5ghz network back without rebooting the router.
Another thing I realized was that dropbear was not able to authenticate my public key through ssh. I assume from the recent discussion this was fixed.
Anyhow, if there is anyone out there that is using LEDE on the r7800 and doesn't have any major complaints regarding the wifi, please let me know, I'll either try out your build or try to rebuild it and see if it works for me. if the lede 17.01 final release is fairly stable in this sense, also please let me know and I'll give that a shot as well.
Thanks,
cchhat01
I had the same issue with master, however 17.01 is rock solid.
I've tried these builds recently on my R7800; thanks @hnyman for building and sharing! Everything works great for about a day or so, but eventually the ath10k driver will crash and wi-fi goes down until I reboot. Both 2.4G and 5G can crash, but not necessarily at the same time.
I increased the log daemon's buffer, so I think I captured almost everything from booting until a crash occurred. See https://gist.github.com/cjberg/32bd22ed87581c4e7278cecbec507259 for complete kernel and system logs. After the firmware crash log messages, the message "failed to send pdev bss chan info request" is repeated over and over again until reboot.
These logs were captured while running the r4409-19ac879954 build. I've since tried running r4467-6da4f03f02 and 2.4G crashed after about a day (roughly), but 5G kept going for a few more days until I needed rebooting. The same "pdeb bss chan" error was logged.
My /etc/config/wireless: https://gist.github.com/cjberg/0e0f8b6bfc4e6aef8f47ebbfa957ccc2
Is this a familiar crash? Any known work-around? Can I collect more diagnostic information to better aid in hunting down this bug somehow?
I also tried running Voxel's build of the stock firmware over the weekend and wi-fi was rock solid, so at least the hardware looks to be in good shape.
I have not experienced that crash myself.
I have a hunch that the "failed to send pdev bss chan info request" is just the end result of multiple wifi driver & firmware crashes, not the core error.
The errors start with the "firmware crashed" error that suggests that something may be going wrong inside the closed-source firmware blob.
Your wifi config looks otherwise rather vanilla, except the "auto" channel setting. I have always used pre-defined channel.
I built my own LEDE v17.01.2 images using the same config i had used for LEDE master.
WiFi and wired are both rock solid.
I have found a keeper.
seeing nearly 550mbps throughput on wifi and around 900mbps on wired wan-to-lan
no crash so far.
Thanks, setting a fixed channel is worth testing. The wifi space is very crowded where I live, so ‘auto’ did perhaps select a somehow problematic (DFS?) channel.
Sounds great! Is it the same build config as hnyman is using, or did you change something noteworthy?
I have my own config.
I take a standard config, add some filesystem related package (ntfs3g, usb-uhci, etc) and some telephony package (asterisk11, yate), LuCI with SSL
i have ipv6, ddns, luci stats, miniupnpd, wget, curl, nathelper, ipsec, wake-on-lan
i have openvpn packages and luci openvpn config page (
I don't have anything else that was added by hnyman.
I am at work, but I can provide my config once I'm home (and if I can remember to upload it)
After trying master twice and failing in terms of stability, I built 17.01.2 and everything just works (with some minor kinks)
kinks:
upnp: ssdp keeps on complaining about packets coming in from an unknown ip (not in the lan) and ignoring
wifi is solid and has not crashed so far. AC wifi works in 80MHz mode, but not in 160MHz mode. (EDIT: maybe because Im using channel 149, I haven't tried with channel 36 and 160Mhz combo yet)
wired is rock solid and has not crashed so far.
Can you kindly share your build, so that I could use it to flash my router ? I'm coming from ddwrt, which is causing my 5 Ghz radio to crash due to a firmware bug, while the 2.4 GHz radio is fine(Pretty similar to the issue that others reported). I'm looking for stability too. I get good wireless through-puts on ddwrt (around 600M down) but frustrated with the stability. I have already set my router to restart every morning, but still see the 5 Ghz crash during the day.
I don't think I can do my own build as I'm fairly new. Any help is appreciated.
You can also download the 17.01.2 builds from the first post in this thread. OP has builds posted. The WiFi crashes occur on the master build not 17.0.1.2.