› UKTH forums › ๐ Wireless Routers & Modems › ASUS & Wireless › ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above.ย Has anyone used this and does it...
- This topic has 1,410 replies, 25 voices, and was last updated 2 months, 4 weeks ago by
UK Sentinel.
- AuthorPosts
- April 12, 2023 at 9:39 pm #23717
Interestingly enough this new version is not showing on the Asus website, at least when I check. Last posted on website is still 22525.
You need to login in order to vote
April 12, 2023 at 10:05 pm #23718April 12, 2023 at 10:44 pm #23720Possible bug in the V1 firmware.ย After setting up with full pin and WPS reset, the 5GHz-2 network is setup as open.ย During setup with the app there was no option to set password for 5GHz-2.ย Seems like the 160MHz ‘bug’ is still also present for me.
You need to login in order to vote
April 13, 2023 at 12:07 am #23721I had a number of devices bound (bind) to some nodes and after the upgrade they showed as greyed out and not connected. Also, they didn’t show on the routers client list, even though they were accessible from the network. I had to un-bind them from their nods before they would appear on the client list.
I know the client list as always been a bit flaky, but on this build devices (both hard wired and WiFi) are dropping on and off the list quite regularly, but they do remain accessible.
I’m also getting these errors in the system log:-
Apr 12 16:30:08 kernel: CPU: 1 PID: 8719 Comm: ping Tainted: P B O 4.1.52 #2
Apr 12 16:30:08 kernel: Hardware name: Generic DT based system
Apr 12 16:30:08 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 12 16:30:08 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 12 16:30:08 kernel: [<c04c76bc>] (dump_stack) from [<c0093188>] (bad_page+0xcc/0x11c)
Apr 12 16:30:08 kernel: [<c0093188>] (bad_page) from [<c00933f4>] (free_pages_prepare+0x21c/0x264)
Apr 12 16:30:08 kernel: [<c00933f4>] (free_pages_prepare) from [<c0093f68>] (free_hot_cold_page+0x30/0x158)
Apr 12 16:30:08 kernel: [<c0093f68>] (free_hot_cold_page) from [<c00940bc>] (free_hot_cold_page_list+0x2c/0x48)
Apr 12 16:30:08 kernel: [<c00940bc>] (free_hot_cold_page_list) from [<c009a368>] (release_pages+0x204/0x20c)
Apr 12 16:30:08 kernel: [<c009a368>] (release_pages) from [<c00b3760>] (exit_mmap+0x120/0x1dc)
Apr 12 16:30:08 kernel: [<c00b3760>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 12 16:30:08 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 12 16:30:08 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 12 16:30:08 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 12 16:30:08 kernel: BUG: Bad rss-counter state mm:ccf18900 idx:0 val:-1Apr 12 19:33:26 kernel: BUG: Bad page map in process dhcpc_lease pte:00000001 pmd:13ef6831
Apr 12 19:33:26 kernel: page:dfbf8000 count:0 mapcount:-1 mapping: (null) index:0x0
Apr 12 19:33:26 kernel: flags: 0x400(reserved)
Apr 12 19:33:26 kernel: page dumped because: bad pte
Apr 12 19:33:26 kernel: addr:b6d30000 vm_flags:00000075 anon_vma: (null) mapping:df04f8cc index:15f
Apr 12 19:33:26 kernel: file:libcrypto.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Apr 12 19:33:26 kernel: CPU: 0 PID: 16830 Comm: dhcpc_lease Tainted: P B O 4.1.52 #2
Apr 12 19:33:26 kernel: Hardware name: Generic DT based system
Apr 12 19:33:26 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 12 19:33:26 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 12 19:33:26 kernel: [<c04c76bc>] (dump_stack) from [<c00ab4b0>] (print_bad_pte+0x138/0x1a0)
Apr 12 19:33:26 kernel: [<c00ab4b0>] (print_bad_pte) from [<c00acb50>] (unmap_single_vma+0x474/0x520)
Apr 12 19:33:26 kernel: [<c00acb50>] (unmap_single_vma) from [<c00ad9b4>] (unmap_vmas+0x54/0x68)
Apr 12 19:33:26 kernel: [<c00ad9b4>] (unmap_vmas) from [<c00b371c>] (exit_mmap+0xdc/0x1dc)
Apr 12 19:33:26 kernel: [<c00b371c>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 12 19:33:26 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 12 19:33:26 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 12 19:33:26 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 12 19:33:26 kernel: BUG: Bad rss-counter state mm:c71f8040 idx:0 val:-1You need to login in order to vote
April 13, 2023 at 6:59 am #23722Interestingly enough this new version is not showing on the Asus website, at least when I check. Last posted on website is still 22525.
3.0.0.4.388.23012 is showing for myself now, when @Dodgydrains posted the update firmware link for the XT8, I did check and also could only see 22525.
As you are in US, could take a while for firmware’s to replicate around the world.
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
April 13, 2023 at 7:08 am #23725Apr 12 19:33:26 kernel: BUG: Bad page map in process dhcpc_lease pte:00000001 pmd:13ef6831
This is interesting, are these messages after latest firmware update, if so did you manage to reboot all the nodes after firmware was updated, ?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
April 13, 2023 at 7:15 am #23727They where after the latest firmware update and I did a a system reboot (as I always do after an update) via the system setting tab.
You need to login in order to vote
April 13, 2023 at 7:20 am #23728Hopefully after 24 hours your AiMesh system will settle down, but will be interesting if the above log keeps repeating itself .
Good news is that you are no longer getting the Firewall Restart log message like you did previously

In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
April 13, 2023 at 7:21 am #23729Interestingly enough this new version is not showing on the Asus website, at least when I check. Last posted on website is still 22525.
same here (asus asian region), not posted yet
but i still downloaded and also did a dirty install.
so far no obvious bugs have come up yet. Will observe for now.
You need to login in order to vote
April 13, 2023 at 8:04 am #23734Possible bug in the V1 firmware. After setting up with full pin and WPS reset, the 5GHz-2 network is setup as open. During setup with the app there was no option to set password for 5GHz-2. Seems like the 160MHz โbugโ is still also present for me.
@UK Sentinel, will you be able able to ask ASUS if this is a new ‘feature’ or a known bug?ย Or is it just me doing things wrong?ย Thanks
You need to login in order to vote
April 13, 2023 at 8:08 am #23735not posted yet but i still downloaded and also did a dirty install. so far no obvious bugs have come up yet. Will observe for now.
I also dirty flashed initially and it all seemed ok too.ย I then decided to do a full factory reset to see if my issue with 160MHz backhaul was resolved.
You need to login in order to vote
April 13, 2023 at 8:47 am #23737@UK Sentinel, will you be able able to ask ASUS if this is a new โfeatureโ or a known bug?ย Or is it just me doing things wrong?ย Thanks
I have dropped ASUS a message and asked

In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
April 14, 2023 at 8:05 am #23748Everything seems to be stable, but I’m still getting these entries in the system log:
Apr 14 02:38:50 kernel: swap_free: Bad swap file entry 100133cb
Apr 14 02:38:50 kernel: BUG: Bad page map in process asusdiscovery pte:0099e5a0 pmd:13ef6831
Apr 14 02:38:50 kernel: addr:b6b30000 vm_flags:00000075 anon_vma: (null) mapping:df04f74c index:0
Apr 14 02:38:50 kernel: file:libssl.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Apr 14 02:38:50 kernel: CPU: 1 PID: 24433 Comm: asusdiscovery Tainted: P B O 4.1.52 #2
Apr 14 02:38:50 kernel: Hardware name: Generic DT based system
Apr 14 02:38:50 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 14 02:38:50 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 14 02:38:50 kernel: [<c04c76bc>] (dump_stack) from [<c00ab4b0>] (print_bad_pte+0x138/0x1a0)
Apr 14 02:38:50 kernel: [<c00ab4b0>] (print_bad_pte) from [<c00acb0c>] (unmap_single_vma+0x430/0x520)
Apr 14 02:38:50 kernel: [<c00acb0c>] (unmap_single_vma) from [<c00ad9b4>] (unmap_vmas+0x54/0x68)
Apr 14 02:38:50 kernel: [<c00ad9b4>] (unmap_vmas) from [<c00b371c>] (exit_mmap+0xdc/0x1dc)
Apr 14 02:38:50 kernel: [<c00b371c>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 14 02:38:50 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 14 02:38:50 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 14 02:38:50 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 14 02:38:50 kernel: BUG: Bad rss-counter state mm:c732e3c0 idx:0 val:1
Apr 14 02:38:50 kernel: BUG: Bad rss-counter state mm:c732e3c0 idx:2 val:-1You need to login in order to vote
April 14, 2023 at 10:47 am #23755So does look like the “asusdiscovery” process, maybe a buffer overflow issue, but nothing to over-worry about.
If you could, send a fedback form to ASUS and put in message box that you are seeing “Bad page map in process asusdiscovery” messages and thought they “ASUS” should know.
One of the services (I think) using the asusdiscovery process/service is to periodically sends packets out across the network, scanning for other ASUS routers. When another ASUS router sees this discover packet, it responds with it’s information and the discovery service parses it.
Have you noticed say the network map or client list not updating ?
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
April 14, 2023 at 1:22 pm #23757I’ll send them feedback straight away.
Yes I am seeing the client list not updating on both the main router and the three nodes (hardwired) and as previously mentioned, I know the client list has always been a bit flaky, but on this build, devices (both hardwired and Wi-Fi) are dropping on and off the list quite regularly, but they do remain accessible.
You need to login in order to vote
- AuthorPosts
- You must be logged in to reply to this topic.

