What's new

Release Asuswrt-Merlin 386.7 is now available for all models

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
AX86U + 386.7


Is that a problem?

Jun 25 12:56:07 kernel: psmdebug 0x00000024 pc 0x01ff000e phydebug 0x0 macctl 0x84160403 maccmd 0x4
Jun 25 12:56:07 kernel: psm_brc 0x0180 psm_brc_1 0x0000 M_UCODE_DBGST 0x2
Jun 25 12:56:07 kernel: brwk_0 0x058b brwk_1 0x0014 brwk_2 0x22a2 brwk_3 0x0ff0 brwk_4 0x0006
Jun 25 12:56:07 kernel: ifsstat 0xaf ifsstat1 0xf0 txectl 0x481a txestat 0x5
Jun 25 12:56:07 kernel: rxestat1 0x1 rxestat2 0x500 rcv_frmcnt 0x0 rxe_rxcnt 0xe
Jun 25 12:56:07 kernel: wepctl 0x0
Jun 25 12:56:07 kernel: aqmf_ready0 0x0 aqmf_ready1 0x4 aqmf_ready2 0x0 aqmf_ready3 0x0
Jun 25 12:56:07 kernel: aqmf_ready4 0x0 wepstat 0x8000 wep_ivloc 0x1a wep_psdulen 0x0
Jun 25 12:56:07 kernel: rxe_errval 0x80 rxe_errmask 0x20f rxe_status3 0x20a txe_status2 0x5
Jun 25 12:56:07 kernel: dbg_bmc_status 0x0 psm_chk0_err 0x0 psm_chk1_err 0x0
Jun 25 12:56:07 kernel: PC :
Jun 25 12:56:07 kernel: R0: 0x24 0x24 0x24 0x24
Jun 25 12:56:07 kernel: psm stack_status : 0x8000
Jun 25 12:56:07 kernel: psm stack_entries:
Jun 25 12:56:07 kernel: 0x0024
Jun 25 12:56:07 kernel: 0x02ac
Jun 25 12:56:07 kernel: 0x01dc
Jun 25 12:56:07 kernel: 0x0683
Jun 25 12:56:07 kernel: 0x307f
Jun 25 12:56:07 kernel: 0x2627
Jun 25 12:56:07 kernel: 0x3f94
Jun 25 12:56:07 kernel: 0x10e2
Jun 25 12:56:07 kernel: wl0: fatal error, reinitializing, total count of reinit's[4]
Jun 25 12:56:07 kernel: CSIMON: CSIMON[1.1.0] Initialization
Jun 25 12:56:07 kernel: CSIMON: M2M usr already registered
1656151502981.png
 
dirty flash over the beta version
everything working fine so far
thxs Merlin !
 
Last edited:
Anyone else having issues with sourceforge not letting you download? tried on 3 devices and mirrors from sourceforge.

Edit: >_> Skynet was geo blocking the country it was coming from changed mirror to country I allow.
Tried whitelisting the domain?
 
Hi all,
Am I the only one with fstab not being read?

It seems to me that when using "mount -a", it is

/rom/etc/fstab

and not

/etc/fstab

which is loaded.

Therefore, any entry put into /jffs/configs/fstab, copied at boot in /etc/fstab, is not used when using the mount command.

@RMerlin, is that possibly a bug?

I'm on RT-AX86U if that matters.
@papypaprika and @RMerlin : having the same issue on my AX58U.
 
I uninstalled Diversion a few days prior to installing 386.7 - since I learned that it was causing the dcd / trendmicro crash.

I do have ipv6 enabled (native, ppp, dhcp-pd enabled). ipv6 works just fine though - devices get ipv6 and are connecting to ipv6 sites with no problems.



I did not manually add/edit the dnsmasq.postconf file, but I do have manual ip assignments via the dhcp server web ui - didn’t change anything. Devices receive their manual ip assignments normally.

Prior to the crash, it was giving an IP address assignment to my work laptop which has a domain - dnsmasq was ignoring said domain. 7 seconds later, it crashed.

15 seconds before that, it was normal dnsmasq startup chatter
Are you using yazfi dhcp script as well?
 
One thing I found, don't know if this is 38.6.7 related.

When I go to the Web page the items on the left show the sub menus, no idea how this came about.
 
Hi Merlin, thanks for the latest release 386.7. After upgrading from 386.5_2 directly, I saw in the log:

Code:
Jun 23 17:49:09 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 23 17:49:09 RT-AX86U-1F70 kernel: CPU: 1 PID: 5116 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 23 17:49:09 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 23 17:49:09 RT-AX86U-1F70 kernel: Call trace:
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18
Jun 23 17:49:09 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 23 17:49:09 RT-AX86U-1F70 kernel: CPU: 1 PID: 5116 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 23 17:49:09 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 23 17:49:09 RT-AX86U-1F70 kernel: Call trace:
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 23 17:49:09 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18
Jun 23 17:49:10 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 23 17:49:10 RT-AX86U-1F70 kernel: CPU: 2 PID: 5116 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 23 17:49:10 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 23 17:49:10 RT-AX86U-1F70 kernel: Call trace:
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 23 17:49:10 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18
Jun 23 17:49:31 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 23 17:49:31 RT-AX86U-1F70 kernel: CPU: 2 PID: 5116 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 23 17:49:31 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 23 17:49:31 RT-AX86U-1F70 kernel: Call trace:
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 23 17:49:31 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18

Is this any cause for concern? It happened 4 times after the upgrade reboot, and it didn't show again (for now)
I'm also have this on my log Asus AX86U. Is there anything I should be worried about?
 
One thing I found, don't know if this is 38.6.7 related.

When I go to the Web page the items on the left show the sub menus, no idea how this came about.
That's the scMerlin script, I believe.
 
Had to roll back to 386.5_2 due to wifi weirdness. Not sure what was the issue but a lot of my IoT devices just would not remain connected reliably. Back on 386.5_2 and everything is once again stable. Who knows what was going one….
same issue on an ax86u, I tried factory and still same. previous version works well.
 
RT-AC5300

2.4 and 5G#2 works fine
5G#1 connects but these no upload data when doing a speed test. Internet doesn't work very well if at all.

I've done 2 clean factory defaults but same problem.

Any suggestions, I'm going back versions at the moment but still the same thing.

I have a RT-AC5300 and did 386.5_2 -> 387 dirty upgrade and don't have this issue (or any issues that I have found so far).
 
anyone had issues when trying to add a new AIMESH node? I get to 1% adding the node after reseting the factory default on the node and then it fails? I'm trying to connect a RT-AC68U to a RT-AC68U which worked fine until the upgrade. I've had issues since this update and had to factory reset the node, and now can't get it to add back.
 

Attachments

  • Screenshot 2022-06-25 at 17.20.46.png
    Screenshot 2022-06-25 at 17.20.46.png
    734.1 KB · Views: 65
Last edited:
anyone had issues when trying to add a new AIMESH node? I get to 1% adding the node after reseting the factory default on the node and then it fails? I'm trying to connect a RT-AC68U to a RT-AC68U which worked fine until the upgrade. I've had issues since this update and had to factory reset the node, and now can't get it to add back.
Are you trying to connect via wifi? My experience is that this fails when adding node 95% of the time. Either way, temporarily move AiMesh node adjacent to primary router. Connect Ethernet cable from LAN port of primary router to WAN port of node. Try again, and it should add the node. Disconnect cable and move node back to original location. It should now connect via Ethernet OR wifi without issue.
 
Update from 386.5_2 went well. Had issues with some iot devices reconnecting, but reboots solved them. Up and running for about a day with no issues. With 386.5_2, the wireless would randomly die. Sometimes within a few hours, other times - weeks or more. Interested to see how this version goes. I’ve tested aimesh with beta 2 and there were no issues using my 68u’s as nodes with wireless backhaul.

many thanks Merlin!
 
Last edited:
anyone had issues when trying to add a new AIMESH node? I get to 1% adding the node after reseting the factory default on the node and then it fails? I'm trying to connect a RT-AC68U to a RT-AC68U which worked fine until the upgrade. I've had issues since this update and had to factory reset the node, and now can't get it to add back.
Yes, for setup, I had to connect the node via lan to wan for it to work. Once it was added, I moved the node to its place…
 
I don't see anyone else reporting this oddity with dnsmasq, perhaps is something specific client side as the OP indicated the behavior present on a work laptop.
I actually sent him a test build with the fix reverted, and dnsmasq was still crashing. So, unrelated to that backport.
 
It seems to me that when using "mount -a", it is

/rom/etc/fstab

and not

/etc/fstab

which is loaded.
This is by design. On HND Busybox will use /rom/etc/fstab, and on other platforms it will use /etc/fstab. You'd have to ask Broadcom why it's designed that way, I don't know.

Therefore, any entry put into /jffs/configs/fstab, copied at boot in /etc/fstab, is not used when using the mount command.
That is correct. Since I do not know the reason behind that design decision, I don't want to risk changing it back to /etc/fstab and running the risk of breaking something else. So for the time being, HND models cannot use /jffs/configs/fstab.

The reason the bahaviour changed in 386.7 is because I updated busybox to apply a few missing Broadcom patches to it, which includes the switch to use /rom/etc/fstab.
 
Are you trying to connect via wifi? My experience is that this fails when adding node 95% of the time. Either way, temporarily move AiMesh node adjacent to primary router. Connect Ethernet cable from LAN port of primary router to WAN port of node. Try again, and it should add the node. Disconnect cable and move node back to original location. It should now connect via Ethernet OR wifi without issue.
Thank you for this, connected via Ethernet, configured and then moved back to how originally set up and all now up and running again.
 
I had a couple streaming sticks act funny after getting 386.7 up and running with a full reset. This didn’t happen with the latest stock firmware. But I rebooted the router and the devices and no issues since.
 
Anyhow, my ISP provide me a 48 bit length IPv6 range of addresses; what I'm doing wrong right now? Why I stepped down from 48 to 64 bit?
You’re probably being delegated a /48 (check /tmp/wan0_bound6.env for PREFIXES=). But the firmware is hardcoding a /64 when assigning a prefix length to br0.

Hardcoded /64 into ipv6_prefix_length:

Adding IPv6 address with ipv6_prefix_length:
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top