Setup used to work fine, but recently the netgear EX6200 (broadcom chip) with DD-WRT v3.0-r55179 mini (02/24/24) just stopped broadcasting wifi signals on both 5g and 2.5g. After a reboot, i can see on a wifi analyzer app on my smartphone that it broadcasts for a minute, then appears to turn off. 0 clients are connected in Status > Wireless menu. Anyone else have this happen, or have an idea?
config is mostly default, recommended settings, /24 subnet, some static IPs assigned. I set the DNS to my pihole, and turned off dnsmasq recently so that the router would pass all the client names to the pihole, so I could visualize more stats there about what & who is getting blocked. With dnsmasq on, all I could ever see on the pihole were ddwrt router queries.
Anwyays, today, after another simple restart, no settings changed, the radio went back to working, and stayed on all day afaik.
Build is 3 years old, because up until now my router has been working fine. It's also an odd router, actually extender, Netgear EX6200, repurposed into a router, because evidently all the hardware was the same. Netgear just installed different firmware to make an extender vs a router? Not 100% on that, but I got it free, and it works. Using a mini build because I think it's got less memory than most newer routers, so I don't want glitches from too little memory leftover.
No logs, sorry, didn't want to overrun the memory.
...turned on syslogd for a few minutes while thinking about this post. It's empty :/
got a syslog from immediately after a reboot where the router dropped the radio almost immediately... saw this entry:
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.000000] Hit pending asynchronous external abort (FSR=0x00001c06) during first unmask, this is most likely caused by a firmware/bootloader bug.
...so, reinstall?
...edit...
there are more orange and red "error" entries:
Dec 31 18:00:09 DD-WRT kern.err kernel: [ 0.000153] smp_twd: clock not found -2
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.198545] Found a ST compatible (Marconix) serial flash with 256 64KB blocks; total size 16MB
Dec 31 18:00:09 DD-WRT kern.emerg kernel: [ 0.322388] Netgear AC1450/R6250/R6300v2/EX6200 init
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.322683] PCI: no core
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.322693] PCI: no core
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.328583] PCI: Fixing up bus 0 domain 0
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.696752] PCIE1 link=1
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.697307] PCI host bridge to bus 0001:00
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.697334] pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.697347] pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 0.697396] pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 0.697485] pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.697702] PCI: Fixing up bus 0 domain 1
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.697723] PCI: bus0: Fast back to back transfers disabled
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 0.697905] pci 0001:01:00.0: [14e4:a8db] type 00 class 0x028000
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 0.697967] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 0.698081] pci 0001:01:00.0: supports D1 D2
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 0.698278] PCI: Fixing up bus 1 domain 1
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 0.698298] PCI: bus1: Fast back to back transfers disabled
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 1.397803] pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 1.397817] pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 1.397860] pci 0002:00:00.0: [14e4:8011] type 01 class 0x060400
Dec 31 18:00:09 DD-WRT kern.debug kernel: [ 1.397947] pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 1.398156] PCI: Fixing up bus 0 domain 2
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 1.398174] PCI: bus0: Fast back to back transfers disabled
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.705157] Creating 6 MTD partitions on "bcmsflash":
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.710254] 0x000000000000-0x000000040000 : "boot"
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.716472] 0x000000040000-0x000000ff0000 : "linux"
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.722425] 0x0000001c0000-0x0000006e0000 : "rootfs"
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.728520] 0x0000006e0000-0x0000007f0000 : "ddwrt"
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.734494] 0x0000007e0000-0x0000007f0000 : "board_data"
Dec 31 18:00:09 DD-WRT kern.notice kernel: [ 2.740965] 0x0000007f0000-0x000000800000 : "nvram"
Dec 31 18:00:09 DD-WRT kern.err kernel: [ 2.746991] nflash: found no supported devices
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 2.908345] Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
Dec 31 18:00:09 DD-WRT kern.err kernel: [ 2.917033] brcmnand: found no supported devices Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 6.373337] eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.692724] wl: module license 'Proprietary' taints kernel.
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.698328] Disabling lock debugging due to kernel taint
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.734171] wl_module_init: passivemode set to 0x0
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.738997] wl_module_init: txworkq set to 0x0
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.743529] PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 7.780498] _ctf_attach:attach wl0
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.787922] eth1: Broadcom BCM43227 802.11 Wireless Controller 7.14.164.18 (r692288)
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 7.821461] _ctf_attach:attach wl1
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.828922] eth2: Broadcom BCM4360 802.11 Wireless Controller 7.14.164.18 (r692288)
Dec 31 18:00:09 DD-WRT kern.warn kernel: [ 7.990141] eth0: mixed HW and IP checksum settings.
Dec 31 18:00:09 DD-WRT kern.info kernel: [ 9.707388] device br0 entered promiscuous mode
Dec 31 18:00:10 DD-WRT user.info : [bridge] : interface vlan1 successfully added to bridge br0
Dec 31 18:00:10 DD-WRT kern.info kernel: [ 10.083054] device vlan1 entered promiscuous mode
Dec 31 18:00:10 DD-WRT kern.info kernel: [ 10.087959] device eth0 entered promiscuous mode
Dec 31 18:00:10 DD-WRT kern.info kernel: [ 10.093206] br0: port 1(vlan1) entered forwarding state
...promiscuous doesn't sound good %) ...
then more kernel stuff, then about 10 minutes strait of DHCPPACK, OFFER, REQUEST from the same 3 devices over and over again every few seconds.
Sep 22 21:26:09 DD-WRT kern.info kernel: [ 2659.562397] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Sep 22 21:49:59 DD-WRT kern.warn kernel: [ 152.588995] br0: received packet on eth1 with own address as source address
...
Last edited by ghent96 on Wed Sep 23, 2026 2:52; edited 1 time in total
ok, I get it, upgrade... but the build hasn't changed, as a variable in this "equation", to start causing this radio bug. The only config or settings I've changed recently is disabling dnsmasq so I can see all the individual devices in my pihole logs, and adding static IPs for most of my devices. These don't seem related at all to the radio just randomly getting set to "inactive"
on status, and wireless tabs, I can in fact see that the radio is "inactive".
Joined: 08 May 2018 Posts: 17403 Location: Texas, USA
Posted: Tue Sep 29, 2026 16:21 Post subject:
Those highlighted entries are "normal", but not sure about the asynchronous external abort. I replied in the other thread also. The Broadcom drivers are seemingly painful to try and work around or fix, and it'd be nice to have a smoking gun configuration that just works IMHO. I personally haven't seen issues, but I'm sure these issues require hours / days to reproduce, and my Broadcom devices are not in use 24/7. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... RSS feed for DD-WRT releases (2025) RSS feed for DD-WRT releases (2024) RSS feed for DD-WRT releases (2023)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
ty for trying, and lending your eyes & experience to this at least, will upgrade and report back... still , for now, the radio is still going off at least once every few days, usually once daily. Will schedule a daily reboot to attempt to band-aid the problem.
but the build hasn't changed, as a variable in this "equation", to start causing this radio bug. The only config or settings I've changed recently is disabling dnsmasq so I can see all the individual devices in my pihole logs, and adding static IPs for most of my devices. These don't seem related at all to the radio just randomly getting set to "inactive"