Release Asuswrt-Merlin 3006.102.6 is now available
- Thread starter RMerlin
- Start date
-
- Tags
- asuswrt-merlin firmware
.
Ok thanks again. Interesting. Then I find the names of those options very peculiar, unless I’ve misunderstood preamble and modulation scheme.
128bit
Senior Member
frankly, it would be preferred by me if for no other reason than consolidation. there may have been some talk that the mesh code is "sealed" and as a result safer. i just may take that dive.
bbunge
Part of the Furniture
While it is not necessary to run Asus or Merlin on an AiMesh node one advantage is that Merlin has SMB2. OK, so I have a 2TB drive on my node to use as a backup for my videos. And yes, I do have Merlin on the node with SMB1 disabled.
I decided to give Merlin a try again and discovered the issues with the IoT clients was the block list I was using on Diversion. Checking the Diversion log I was able to whitelist the needed web sites.
But, one funny today was my wife was blocked from a web site she needed to do some Christmas shopping. Sorry honey... let me fix that...happy wife!
Since a dirty upgrade from 102.5 to 102.6, I've had multiple spontaneous router reboots. I grabbed a log and I'm seeing unusual crond behavior:
This is all from a time range of a couple of minutes. Note the "time disparity" warnings and the resultant time changes. It's almost as though it's contacting pool.ntp.org and getting bogus responses.
But I changed the ntp server to an internal one, but the router rebooted again a few minutes later (same message in the log). So it's not pool.ntp.org that's the culprit.
If there are no other obvious clues, I'll probably do a full reset/reinstall this afternoon. I just have to painstakingly copy out all the settings. I haven't done that in a while (naughty, I know) so maybe I'm just due.
Code:
Dec 31 19:00:36 kernel: skb_free_task created successfully with start budget 32, period 10ms
Dec 31 19:00:36 kernel: bcm_tcp_task created successfully with budget 256 ,cpumask:0x6
Dec 31 19:00:36 kernel: enet_kthread_init:L637 ENET system contructed and configured enet-kthrd thread
Dec 31 19:00:36 kernel: enet_kthread_handler:L595 Instantiating ENET thread
Dec 31 19:00:38 kernel: eth1 (Int switch port: 5) (Logical Port: 5) (phyId: 6) Link Up at 10000 mbps full duplex AN: Off
Dec 31 19:00:46 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 9) Link Up at 100 mbps full duplex AN: On
Nov 27 16:46:58 crond[4259]: time disparity of 1003545 minutes detected
Dec 31 19:00:37 kernel: skb_free_task created successfully with start budget 32, period 10ms
Dec 31 19:00:37 kernel: bcm_tcp_task created successfully with budget 256 ,cpumask:0x6
Dec 31 19:00:37 kernel: enet_kthread_init:L637 ENET system contructed and configured enet-kthrd thread
Dec 31 19:00:37 kernel: enet_kthread_handler:L595 Instantiating ENET thread
Dec 31 19:00:39 kernel: eth1 (Int switch port: 5) (Logical Port: 5) (phyId: 6) Link Up at 10000 mbps full duplex AN: Off
Dec 31 19:00:47 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 9) Link Up at 100 mbps full duplex AN: On
Nov 27 17:26:29 crond[4257]: time disparity of 1003585 minutes detected
May 3 20:23:22 crond[4257]: time disparity of 15005317 minutes detected
May 3 20:23:22 kernel: rcu: INFO: rcu_sched self-detected stall on CPU
May 3 20:23:22 kernel: rcu: 1-...!: (213 ticks this GP) idle=95e/0/0x1 softirq=532151/532426 fqs=0
May 3 20:23:22 kernel: rcu: (t=900318639124 jiffies g=140121 q=170)
May 3 20:23:22 kernel: rcu: rcu_sched kthread starved for 900318639128 jiffies! g140121 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=2
May 3 20:23:22 kernel: rcu: RCU grace-period kthread stack dump:
May 3 21:12:14 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
May 3 21:12:14 kernel: rcu: 2-...!: (1 GPs behind) idle=132/1/0x4000000000000002 softirq=2356225/2356226 fqs=1
May 3 21:12:14 kernel: rcu: (t=974954 jiffies g=4153833 q=61)
Nov 15 12:02:41 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Nov 15 12:02:41 kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Nov 15 12:02:41 kernel: rcu: 1-....: (1 GPs behind) idle=50a/0/0x1 softirq=2171837/2171838 fqs=6
Nov 15 12:02:41 kernel: rcu: 1-...!: (333 ticks this GP) idle=50a/0/0x1 softirq=2171342/2171838 fqs=0
Nov 15 12:02:41 kernel: rcu: (t=900514227672 jiffies g=4153833 q=123857)
Nov 15 12:02:41 kernel: rcu: (detected by 3, t=900513252722 jiffies, g=257969, q=5)
Nov 15 12:02:41 kernel: rcu: rcu_preempt kthread starved for 900513252730 jiffies! g4153833 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
Nov 15 12:02:41 kernel: rcu: RCU grace-period kthread stack dump:
Nov 15 12:02:41 crond[4257]: time disparity of 15008570 minutes detected
May 30 03:58:44 crond[4257]: time disparity of 15008571 minutes detected
May 30 03:58:44 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
May 30 03:58:44 kernel: rcu: 2-...!: (1 ticks this GP) idle=98e/1/0x4000000000000002 softirq=2548583/2548583 fqs=0
May 30 03:58:44 kernel: rcu: (t=974854 jiffies g=4496261 q=165)
May 30 03:58:44 kernel: rcu: rcu_preempt kthread starved for 974854 jiffies! g4496261 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
May 30 03:58:44 kernel: rcu: RCU grace-period kthread stack dump:
May 30 03:58:44 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
May 30 03:58:44 kernel: rcu: 1-...!: (1 ticks this GP) idle=0e6/0/0x1 softirq=2355609/2355609 fqs=0
May 30 03:58:44 kernel: rcu: (t=900514227567 jiffies g=4496261 q=54154)
May 30 03:58:44 kernel: rcu: rcu_preempt kthread starved for 900514227567 jiffies! g4496261 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
May 30 03:58:44 kernel: rcu: RCU grace-period kthread stack dump:
May 30 04:59:54 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
May 30 04:59:54 kernel: rcu: 3-...!: (1 GPs behind) idle=61e/1/0x4000000000000002 softirq=4677231/4677232 fqs=0
May 30 04:59:54 kernel: rcu: (t=974956 jiffies g=8212437 q=513)
May 30 04:59:54 kernel: rcu: rcu_preempt kthread starved for 974956 jiffies! g8212437 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
May 30 04:59:54 kernel: rcu: RCU grace-period kthread stack dump:
Dec 11 18:50:22 crond[4257]: time disparity of 15008570 minutes detected
Dec 11 18:50:22 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Dec 11 18:50:22 kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Dec 11 18:50:22 kernel: rcu: (detected by 3, t=900514227661 jiffies, g=8212437, q=53942)
Dec 11 18:50:22 kernel: rcu: 1-...!: (5 ticks this GP) idle=7c2/1/0x4000000000000000 softirq=3962119/3962119 fqs=0
Dec 11 18:50:22 kernel: rcu: All QSes seen, last rcu_preempt kthread activity 900514227661 (3606166315200-2705652087539), jiffies_till_next_fqs=3, root ->qsmask 0x0
Dec 11 18:50:22 kernel: rcu: (detected by 0, t=900513252705 jiffies, g=422449, q=245)
Dec 11 18:50:22 kernel: rcu: rcu_sched kthread starved for 900513252705 jiffies! g422449 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=3
Dec 11 18:50:22 kernel: rcu: RCU grace-period kthread stack dump:
Dec 11 19:01:37 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Dec 11 19:01:37 kernel: rcu: (detected by 2, t=974958 jiffies, g=8886189, q=44)
Dec 11 19:01:37 kernel: rcu: All QSes seen, last rcu_preempt kthread activity 974958 (3606167965543-3606166990585), jiffies_till_next_fqs=3, root ->qsmask 0x0
Dec 11 19:01:37 kernel: rcu: rcu_preempt kthread starved for 974958 jiffies! g8886189 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=1
Dec 11 19:01:37 kernel: rcu: RCU grace-period kthread stack dump:
Jun 24 10:52:05 crond[4257]: time disparity of 15008570 minutes detected
Jun 24 10:52:05 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Jun 24 10:52:05 kernel: rcu: (detected by 1, t=900514227665 jiffies, g=8886189, q=49557)
Jun 24 10:52:05 kernel: rcu: All QSes seen, last rcu_preempt kthread activity 900514227671 (4506681218256-3606166990585), jiffies_till_next_fqs=3, root ->qsmask 0x0
Jun 24 10:52:05 kernel: rcu: rcu_preempt kthread starved for 900514227741 jiffies! g8886189 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
Jun 24 10:52:05 kernel: rcu: RCU grace-period kthread stack dump:
Dec 31 19:00:37 kernel: skb_free_task created successfully with start budget 32, period 10ms
Dec 31 19:00:37 kernel: bcm_tcp_task created successfully with budget 256 ,cpumask:0x6
Dec 31 19:00:37 kernel: enet_kthread_init:L637 ENET system contructed and configured enet-kthrd thread
Dec 31 19:00:37 kernel: enet_kthread_handler:L595 Instantiating ENET thread
Dec 31 19:00:39 kernel: eth1 (Int switch port: 5) (Logical Port: 5) (phyId: 6) Link Up at 10000 mbps full duplex AN: Off
Dec 31 19:00:47 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 9) Link Up at 100 mbps full duplex AN: On
Nov 27 20:51:57 crond[4256]: time disparity of 1003790 minutes detected
Dec 31 19:00:37 kernel: skb_free_task created successfully with start budget 32, period 10ms
Dec 31 19:00:37 kernel: bcm_tcp_task created successfully with budget 256 ,cpumask:0x6
Dec 31 19:00:37 kernel: enet_kthread_init:L637 ENET system contructed and configured enet-kthrd thread
Dec 31 19:00:37 kernel: enet_kthread_handler:L595 Instantiating ENET thread
Dec 31 19:00:39 kernel: eth1 (Int switch port: 5) (Logical Port: 5) (phyId: 6) Link Up at 10000 mbps full duplex AN: Off
Dec 31 19:00:47 kernel: eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 9) Link Up at 100 mbps full duplex AN: OnThis is all from a time range of a couple of minutes. Note the "time disparity" warnings and the resultant time changes. It's almost as though it's contacting pool.ntp.org and getting bogus responses.
But I changed the ntp server to an internal one, but the router rebooted again a few minutes later (same message in the log). So it's not pool.ntp.org that's the culprit.
If there are no other obvious clues, I'll probably do a full reset/reinstall this afternoon. I just have to painstakingly copy out all the settings. I haven't done that in a while (naughty, I know) so maybe I'm just due.
Ripshod
Part of the Furniture
The only thing I can think of is another ntp server running on your network.
If you still see ntp errors after the reset take a look at ntpMerlin in the addons forum.
That's probably for the best anyway with the broadcom drivers being involved.
If you still see ntp errors after the reset take a look at ntpMerlin in the addons forum.
nothing like beating a dead horse.
Zirescu
Very Senior Member
@bpsmicro - I'm assuming this is happening on the RT-BE92U as I've seen the same thing ever since buying the router. I ended up having to write a script to check that the year reported by the clock was not less than 1969 and if it was, force a restart of the router as the ntpd isn't able to update the clock when it ends up back in the 1918s. My best guess is that something in the broadcom driver ends up overwriting memory where it shouldn't and clobbers the system time.
GWTechTalk
Regular Contributor
Still having issues with some devices not showing in the main dashboard client's sections. Interestingly enough the devices that DONT show up there also do not get the static DHCP reservations I have set. Since this was a dirty flash, I'm going to do a clean reset and reconfigure to see if it's just a byproduct of dirty flashing. Still, posting here for awareness for others on what to look out for.
heysoundude
Part of the Furniture
usually a good idea to clear browser cache every so often...Having issues with my AX86U Pro.
After updating from 3006.102.6, the routers web interface is slow, laggy and will sometimes crash and reload.
I've restarted the router, but it's still doing this.
**edit** oddly, rebooting the pc that I was using to view the interface seems to have resolved the issue.
Tim Storey
Occasional Visitor
Factory reset from beta 2, rebuilt network. Everything appears to be working fine after 2 1/2 days.
It is indeed the BE92U. And I did a complete factory reset, staying at 102.6, and it's still rebooting randomly.
Unfortunately, a script that reboots the router isn't all that much better than it self-rebooting.
I think I'll have to go back to 102.4 (102.5 gave random WiFi problems, but not rebooting).
22Vanquish22
New Around Here
Unable to login into the router after the update despite multiple reboots, login attempts on different devices, filling password manually, clearing cache and cookies.
Just keeps stating invalid username or password.
side note, I switch from Asuswrt to merlin 3006.102.5 than updated to current.
Device: GT-AX6000
Any assistance will be appreciated.
Just keeps stating invalid username or password.
side note, I switch from Asuswrt to merlin 3006.102.5 than updated to current.
Device: GT-AX6000
Any assistance will be appreciated.
Updated from beta2. No problems other than the same minor issue reported during the beta test: client will not bind to AiMesh node - remains connected to main router due to "optimization". This is a change in behavior from 3006.102.5. I assume this is due to a change in one of the closed source modules supplied by Asus and not related to the Merlin code updates.
Downgraded to 102.4, factory reset and painstaking reapplication of my basic settings. Still reboots and the syslog still shows bogus timestamps. Unfortunately, since syslog doesn't include the year, I can't tell if your theory about that is correct. But I surmise it's not the broadcom driver unless this has been around since 102.4. But then I'd expect to see more complaints.
The only block that seems to indicate trouble brewing is this:
Code:
May 6 22:01:54 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
May 6 22:01:54 kernel: rcu: 0-...!: (1 GPs behind) idle=372/1/0x4000000000000002 softirq=743644/743645 fqs=0
May 6 22:01:54 kernel: rcu: (t=979249 jiffies g=916005 q=32)
May 6 22:01:54 kernel: rcu: rcu_preempt kthread starved for 979249 jiffies! g916005 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
May 6 22:01:54 kernel: rcu: RCU grace-period kthread stack dump:
May 6 22:01:54 kernel: Call trace:
May 6 22:01:54 kernel: __switch_to+0xe8/0x170
May 6 22:01:54 kernel: __schedule+0x214/0x5a0
May 6 22:01:54 kernel: schedule+0x38/0xa0
May 6 22:01:54 kernel: schedule_timeout+0x15c/0x2a0
May 6 22:01:54 kernel: rcu_gp_kthread+0x488/0x900
May 6 22:01:54 kernel: kthread+0x118/0x150
May 6 22:01:54 kernel: ret_from_fork+0x10/0x24
May 6 22:01:54 kernel: Call trace:
May 6 22:01:54 kernel: dump_backtrace+0x0/0x150
May 6 22:01:54 kernel: show_stack+0x14/0x20
May 6 22:01:54 kernel: sched_show_task+0x100/0x120
May 6 22:01:54 kernel: dump_cpu_task+0x40/0x4c
May 6 22:01:54 kernel: rcu_dump_cpu_stacks+0x90/0xcc
May 6 22:01:54 kernel: rcu_check_callbacks+0x67c/0x810
May 6 22:01:54 kernel: update_process_times+0x2c/0x70
May 6 22:01:54 kernel: tick_sched_timer+0x54/0xd0
May 6 22:01:54 kernel: __hrtimer_run_queues+0x13c/0x1d0
May 6 22:01:54 kernel: hrtimer_interrupt+0xe4/0x2b0
May 6 22:01:54 kernel: arch_timer_handler_phys+0x30/0x40
May 6 22:01:54 kernel: handle_percpu_devid_irq+0x80/0x140
May 6 22:01:54 kernel: __handle_domain_irq+0x70/0xd0
May 6 22:01:54 kernel: gic_handle_irq+0x5c/0xc0
May 6 22:01:54 kernel: el0_irq_naked+0x4c/0x54
May 6 22:01:54 kernel: Call trace:
May 6 22:01:54 kernel: __switch_to+0xe8/0x170
May 6 22:01:54 kernel: tick_nohz_restart_sched_tick+0x3c/0xd0
May 6 22:01:54 kernel: tick_nohz_idle_exit+0x90/0xe0
May 6 22:01:54 kernel: do_idle+0x14c/0x260
May 6 22:01:54 kernel: cpu_startup_entry+0x24/0x40
May 6 22:01:54 kernel: secondary_start_kernel+0x13c/0x170Not sure what "rcu" is.
Zirescu
Very Senior Member
Yeah, I've seen it on mine from the very first release. Near as I can tell it is somehow related to some network setting that messes things up. I was able to eventually get things more or less stable by setting the main network to just the 5 & 6 GHz radios and only one Guest Network on the 2.4 GHz radio.
If you SSH to the router when it's in the bad state, you can run `date` on the command line to get it to report the time.
Here's the script that I created to log the data to syslog and reboot when it glitches and call it via services-start.
#!/bin/sh
while true; do
YEAR=$(date +%Y)
UPTIME=$(uptime)
echo "Current year is $YEAR, Router uptime: $UPTIME"
logger "Clock check: Current year is $YEAR, Router uptime: $UPTIME"
if [ "$YEAR" -lt 1969 ]; then
echo "Year is $YEAR (less than 1969) – restarting router"
logger "Year is $YEAR (less than 1969) – restarting router"
reboot
fi
sleep 300
done
Okay, yeah, I can see that now. I SSH'ed in and just checked date every now and then, and it changed from correct to Wed May 8 04:54:27 EDT 1918.
I'd imagine it'll try to correct that via ntp, fail, and self-reboot at some point soon.
My network settings aren't particularly elaborate. Wifi 6 & 7 turned off, separate 2.4 & 5 SSIDs, plus one 2.4-only IOT. I do have a fair number of manual IP settings under DHCP. I changed nothing under the WiFi Professional settings from the last factory reset.
I broke down and ordered a RT-BE88U, catching a Black Friday sale. If I don't get this solved by Sunday when the new one arrives, I'll relegate the 92U to a stock firmware doing AIMesh duties.
Similar threads
Similar threads
Similar threads
-
-
Does minidlna get installed by default (asuswrt-merlin 3006.102.5)
- Started by chrisisbd
- Replies: 2
-
-
-
-
-
Homekit help request on Asuswrt-Merlin 3006.102.4 Beta 2
- Started by Alfie J
- Replies: 2
-
-
Release Asuswrt-Merlin 3006.102.3 is now available for WIfi 7 devices
- Started by RMerlin
- Replies: 120
-
Beta Asuswrt-Merlin 3006.102.3 beta is now available for Wifi 7 devices
- Started by RMerlin
- Replies: 53