Posted: Wed Apr 07, 2021 13:18 Post subject: New Build - 04/07/2021 - r46301
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues:
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Router setup:
WRT1900ACS V2
Config retained from previous build
Configuration
Build 46301
OpenVPN - tap mode bridged (Disabled)
Wireguard - 11 clients
Wifi 5GHZ AC-Only WHT80
Wifi 2.4GHZ - Auto Channel NG-Mixed
Security WP2+AES on both radios
Port forwarding utilized for SMTP, IMAP, HTTP and HTTPS (IMAP on non-standard port)
Error Descriptions:
After, flash => boot and on first attempt to call GUI, it does not respond. DMESG enclosed. I keep reverting to 45993 which is the latest build I tried, that doesn't crash either immediately or within 12H or so on my router.
After reboot - it takes literally seconds before the build crashes again. Reverting back again.
Update
I did reset the router, flashed 46301 with full manual config. Came as far as configuring my WG-tunnels - when it crashed the same way again. Back to 45993 and stability. The weirdest thing.....
Did try to revert to 46069. Also stable. Is it a possible explanation that my problems are Kernel-related? Kernel 4.9.261 seems to run fine, and 46069 is the last build with that kernel. All builds with kernel 4.9.264 crash on my setup.
Last edited by Fonzi on Thu Apr 08, 2021 20:04; edited 2 times in total
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r46301 std (04/07/21) (prev. DD-WRT v3.0-r46259 std (04/03/21))
Kernel: Linux 4.9.264 #2536 SMP Wed Apr 7 02:06:22 +07 2021 armv7l
Mode: Gateway, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G, Keep Alive reboot 6:02 in the morning
Reset: No
Status: 2h:38 up, ok. load average 0.00, 0.00, 0.00, Temperatures CPU 73.6 °C / WL0 46.5 °C / WL1 48.1 °C. Webif working on my end. Nothing similar to above can be seen in my dmesg, sorry .
As also stated in BDCM Thread, one minor cosmectic thing: mixed figures in NAT/QoS --> Port Range Forwarding.
Nothing similar to above can be seen in my dmesg, sorry
I don't get it. We have the same router. How can it be, that mine consistently has been unstable and failing on last builds, and yours not? Would assume its something in the config then, and my is just a couple of weeks old, and all config entered manually....hm..
Not me, but might just be different environments (wireless and/or power line), hardware tolerances, or some combination. Even with nearly identical configurations, we had some otherwise unexplained glitches on our ACSv2, for example, while our ACSv1 was fine. Simply plugging it into a UPS seems to have unexpectedly resolved that difference.
I think I remember reading and/or watching somewhere online about someone upgrading an on-board power conditioning capacitor in one of these Linksys/Marvell units (while complaining that it was shoddy). I'll see if I can find the link. With the Marvel driver support issues, though, I think we'll be upgrading to something else before I open either of these up again. But for now, even my better half is content including home/office/Apple use. I'll post our latest build results shortly. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Last edited by o2bad455 on Wed Apr 07, 2021 20:48; edited 1 time in total
Make sure you allow the updates to fully complete. There will be a progress bar then another with a "Continue" button. Don't press the continue button, wait until the GUI pops back up by itself. Some browsers will interfere with the updates finale moments so use a browser that finishes by itself with the GUI popping up without your input. Different OS's seem to make a diff in which browser is best for you. A partial update can be really buggy with the false appearance of working.
Make sure all security browser apps are "Trusted" or off for your router IP address. I've had issues where it was appearing to be a successful update but would fail due to security apps blocking the changes. NoScript especially can be a problem unless your IP address is "Trusted".
Since your router is fairly new have you rebooted both the router and modem since you put DD-WRT on the router? Depending on the modem it may need to renegotiate with the router after a firmware change from the stock firmware. Reboot of both can sometimes work wonders.
Make sure you allow the updates to fully complete. There will be a progress bar then another with a "Continue" button. Don't press the continue button, wait until the GUI pops back up by itself. Some browsers will interfere with the updates finale moments so use a browser that finishes by itself with the GUI popping up without your input. Different OS's seem to make a diff in which browser is best for you. A partial update can be really buggy with the false appearance of working.
Make sure all security browser apps are "Trusted" or off for your router IP address. I've had issues where it was appearing to be a successful update but would fail due to security apps blocking the changes. NoScript especially can be a problem unless your IP address is "Trusted".
Since your router is fairly new have you rebooted both the router and modem since you put DD-WRT on the router? Depending on the modem it may need to renegotiate with the router after a firmware change from the stock firmware. Reboot of both can sometimes work wonders.
If none of the above apply just ignore me. =)
These points would have made sense for me, if it weren't for the fact that reverting to build 45993 makes it stable as a rock - in the same configuration (Been going back to that build 6-7 times now). It would be odd if it was stable on 45993, if there was something messing with the flashing. The Fiber-moden is OK. Again, no issues on speed or anything with the older build. What I actually haven't tried is a "cold boot" - turn off switch on the router for each new build I have tried - so I'll try that next. We'll see. Not hopeful.
Router/Version: Linksys WRT1900ACSv1 / DD-WRT v3.0-r46301 std (04/07/21)
File/Kernel: webflash / Linux 4.9.264 #2536 SMP Wed Apr 7 02:06:22 +07 2021 armv7l
Previous/Reset: r46259 / No
Mode/Status: Gateway, OpenVPN Client, FreeRadius Server / Uptime 3:08, Load Average
0% 0.00, 0.00, 0.00 , Temperatures CPU 72.7 °C / WL0 45.1 °C / WL1 46.7 °C
Issues/Errors: None / This ACSv1 is running well, thanks!
Router/Version: Linksys WRT1900ACSv2 / DD-WRT v3.0-r46301 std (04/07/21)
File/Kernel: webflash / Linux 4.9.264 #2536 SMP Wed Apr 7 02:06:22 +07 2021 armv7l
Previous/Reset: r46259 / No
Mode/Status: Gateway, OpenVPN Client, FreeRadius Server / Uptime 2:58 , Load Average 0% 0.00, 0.02, 0.00, Temperatures CPU 71.7 °C / WL0 45.3 °C / WL1 47.5 °C
Issues/Errors: None / This ACSv2 is running well, thanks!
Note: I don't have any actual errors in dmesg, but do have this taint reported by both routers (right after apparently successful Bluetooth initialization - what's that about?):
ACSv1:
[ 7.281654] lzma_compress: module license 'unspecified' taints kernel.
[ 7.289479] Disabling lock debugging due to kernel taint
ACSv2:
[ 8.120154] lzma_compress: module license 'unspecified' taints kernel.
[ 8.127857] Disabling lock debugging due to kernel taint
Is my understanding correct that this taint means wifi compression is not working (where I have both QAM256 and LDPC enabled), or is this taint related to openvpn (where I have compression disabled on client)? _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Last edited by o2bad455 on Thu Apr 08, 2021 0:49; edited 1 time in total
Upgraded my 1900ACSv1 via Safari from 44048. I did a reset via CLI and manually re-entered the configuration, rebooting several times. No issues with the upgrade.
Problems with Apple devices: I didn't see any wifi hangs (like I have with every release since 44048) but I didn't get a chance to test very long because something started crashing within a few minutes of uptime. This made the GUI unusable. Existing wifi connections seemed ok but new clients did not connect to the WAP after this process crashed. I tried stop/startservice on httpd but it just went into a zombie state (Z in ps). See dmesg output below. (This same crash/dmesg also happened with the 46239 release too.)
Syslog: I couldn't access syslog via GUI. See dmesg below.
44048 is the last good release if you have Apple devices in your environment. Something broke with 44085 and 44112.
Linksys WRT1900ACSv1: router mode, hardwired ethernet lan to a WRT3200ACM. WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel 11, WPA2-CCMP-128. 5ghz: AC/N mixed, 80mhz channel width, channel 36+upper, WPA2-CCMP-128.
Clients: Apple MACOS x 4, IOS x 4, Apple TV, Chromecast Audio x 2, Eufy doorbells, Lutron Caseta, Axis Camera, Samsung TV, Nest thermostat, EtekCity outlets (Espressif)..
Dmesg:
[ 183.161062] ieee80211 phy0: Mac80211 start BA 0e:02:25:xx:xx:62
[ 197.504666] ieee80211 phy0: Mac80211 start BA 0e:02:25:xx:xx:62
[ 482.716626] Unable to handle kernel NULL pointer dereference at virtual address 00000004
[ 482.725089] pgd = dc8cc000
[ 482.729195] [00000004] *pgd=1c869831, *pte=00000000, *ppte=00000000
[ 482.741094] Internal error: Oops: 17 [#1] SMP ARM
[ 482.747201] Modules linked in: ip6_tables btmrvl_sdio btmrvl bluetooth mwifiex_sdio mvsdio sdhci_pxav3 sdhci_pltfm sdhci mmc_block mmc_core mwifiex mwlwifi mac80211 compat mii tmp421 pwm_fan leds_pca963x leds_tlc591xx orion_wdt
[ 482.767675] CPU: 0 PID: 2362 Comm: httpd Not tainted 4.9.264 #2536
[ 482.773879] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 482.779821] task: df74f9c0 task.stack: de784000
[ 482.784430] PC is at sta_set_sinfo+0x9d4/0x1304 [mac80211]
[ 482.789936] LR is at 0x0
[ 482.792477] pc : [<bf02db30>] lr : [<00000000>] psr: 80000013
[ 482.798768] sp : de785b78 ip : de1c0c20 fp : ddd124c0
[ 482.804011] r10: 00000002 r9 : 00000000 r8 : 00000000
[ 482.809256] r7 : 00000000 r6 : dc8b8150 r5 : dc8b8000 r4 : de785c08
[ 482.815809] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000
[ 482.822362] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 482.829526] Control: 10c5387d Table: 1c8cc04a DAC: 00000055
[ 482.835294] Process httpd (pid: 2362, stack limit = 0xde784210)
[ 482.841236] Stack: (0xde785b78 to 0xde786000)
[ 482.845609] 5b60: bf0c949c 00000003
[ 482.853821] 5b80: 00000000 de1c0c20 dc8b8150 0000475f 00000001 dc8b86b8 dc8b8150 de785bf8
---I truncated the stack trace---
[ 483.141207] 5fe0: b6b29600 b6b295ec b6f26848 b6f25d10 60000010 00000007 00000000 00000000
[ 483.149474] [<bf02db30>] (sta_set_sinfo [mac80211]) from [<bf04998c>] (ieee80211_dump_station+0x60/0x78 [mac80211])
[ 483.160002] [<bf04998c>] (ieee80211_dump_station [mac80211]) from [<bf0b2b6c>] (nl80211_dump_station+0x8c/0x110 [mac80211])
[ 483.171207] [<bf0b2b6c>] (nl80211_dump_station [mac80211]) from [<c0516234>] (netlink_dump+0x160/0x330)
[ 483.180641] [<c0516234>] (netlink_dump) from [<c0517538>] (__netlink_dump_start+0x134/0x1cc)
[ 483.189115] [<c0517538>] (__netlink_dump_start) from [<c051a8bc>] (genl_rcv_msg+0x22c/0x3c8)
[ 483.197588] [<c051a8bc>] (genl_rcv_msg) from [<c05173a0>] (netlink_rcv_skb+0x5c/0xc0)
[ 483.205451] [<c05173a0>] (netlink_rcv_skb) from [<c05197e8>] (genl_rcv+0x24/0x34)
[ 483.212964] [<c05197e8>] (genl_rcv) from [<c0516ed0>] (netlink_unicast+0x20c/0x4f0)
[ 483.220652] [<c0516ed0>] (netlink_unicast) from [<c0517f54>] (netlink_sendmsg+0x324/0x36c)
[ 483.228953] [<c0517f54>] (netlink_sendmsg) from [<c049c524>] (___sys_sendmsg+0x238/0x290)
[ 483.237165] [<c049c524>] (___sys_sendmsg) from [<c049cdec>] (SyS_sendmsg+0x68/0xa0)
[ 483.244856] [<c049cdec>] (SyS_sendmsg) from [<c010b9c0>] (ret_fast_syscall+0x0/0x40)
[ 483.252633] Code: e7e31251 e203300f e0822101 e59228cc (e5922004)
[ 483.258869] ---[ end trace 454cf89cf1efa7f2 ]---
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Apr 08, 2021 7:50 Post subject:
Zyxx wrote:
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r46301 std (04/07/21) (prev. DD-WRT v3.0-r46259 std (04/03/21))
Kernel: Linux 4.9.264 #2536 SMP Wed Apr 7 02:06:22 +07 2021 armv7l
Mode: Gateway, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G, Keep Alive reboot 6:02 in the morning
Reset: No
Status: 2h:38 up, ok. load average 0.00, 0.00, 0.00, Temperatures CPU 73.6 °C / WL0 46.5 °C / WL1 48.1 °C. Webif working on my end. Nothing similar to above can be seen in my dmesg, sorry .
As also stated in BDCM Thread, one minor cosmectic thing: mixed figures in NAT/QoS --> Port Range Forwarding.
Upgraded WRT1200AC v1's from r46294 to r46301 using Brave 1.10.91 (64-bit) running on Linux Mint 20.1 OS hardwired via Cat6.
Successful update and reboot. No reset, nothing disabled prior to update, uptime approx 15 hrs, wired/wireless connected, vpn up immediately (Expressvpn). I do not use NAS. SFE, QoS and IPv6 are always disabled. OpenVPN client/DNSMasq and radios always enabled. I do not have any Apple devices.
Kernel Version Linux 4.9.264 #2536 SMP Wed Apr 7 02:06:22 +07 2021 armv7l
.
