cancel
Showing results for 
Search instead for 
Did you mean: 

GT-AXE11000 - can someone please explain to me what's going on with this?

superdeleted
Level 7
I have hit my limit. Been over 2 weeks troubleshooting with Asus Support and they either can't or they won't explain to me what these log files mean and ultimately why they are happening. I attached what anmounts to the smallest of slivers to what my router has been spitting out over the last couple weeks. I mean I have books and books of this stuff now.

Every search I turn up only a couple threads with people experiencing the same thing but none of reach an answer or if they did it wasn't posted. Asus support won't even address the lines with me. happy to just send me constant faqs to follow that I told them I had already tried them all before I reached out to them because I know thats step one with any support but alas they just keep wanting me to reset like my time means nothing and I could reconnect 120+ devices on the regular. They used to always just reconnect (when I had the AX-86U) but now every reset seems to mean stumbling through 50% of my IoT devices trying to get them to reconnect which is why I would like to understand what is going on in the logs. Some of it I know what it is saying but I don't understand why it would be happening and other parts I just plain am clueless as to what the heck is happening. The main culprits in the log file are as follows:

May 13 00:20:14 wlceventd: wlceventd_proc_event(508): eth6: Disassoc 34:20:03:5C:27:4E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

or

May 13 00:20:17 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 34:20:03:7A:FE:AD, status: 0, reason: Unspecified reason (1), rssi:0

or

May 13 00:20:25 kernel: 7C:78:B2:A8:91:C0 not mesh client, can't update it's ip

or

May 13 00:22:24 kernel: 7E:78:B2:2C:975 not mesh client, can't delete it

and last but not least the one that seems obvious in meaning but reasoning why I dont get:

May 13 00:02:52 kernel: 192.168.50.231 is used by someone else, can't use it


I am happy to share data anyone wants if they can give even the slightest insight. Support finally has given me a RMA number but is it even worth it? I mean I really hope its just a bad unit, if not it'll hit down to my soul spending 600 bucks to get what I thought would be top of the line. As it stands now I am about to switch back to one of my AC86U nodes because at least there I was stable with my devices.

Couple quick things to note about my notes. The router literally never stops until it forces me to reboot because my LAN wont even connect. Otherwise these lines are on constant write. I have also tried tracking the MACs being called out each time but after a couple days of skimming and checking there is no rhyme or reason that I can tell. It's a random group out of all my IoT devices, never the same ones so not sure I can rule out anything as being "the trouble spot" plus like I mentioned I had all the same devices on my AX-86U without much problems. The GT-11000 originally seemed to work fine too I don't know what even happened just one day I would wake up with some device not responding or whatever. The MACs don't seem to pinpoint a singular device or even device grouping.

So thank you for letting me rave and vent for a min. I am a big fan of Asus equipment but this one has started [putting a sour taste in my mouth and it is starting to hurt my work from home requirement.

So anything ANYONE can shed line on dealing with this please let me know. I'm happy to pull any data or cfg file settings or follow whatever troubleshooting anybody has gladly.

Also if I am set to DHCP why is it constantly trying/testing the device of it being aimesh node or why does it want to keep changing the ip of the devices or wanting to delete them?

I am in an AImesh system. Veryv large house with all nodes connected via ethernet backhaul



Thanks ROG Forum!
2,627 Views
37 REPLIES 37

MasterC
Community Admin
Community Admin
Around 130... woah... are you running this for a business? Personally I'm at 25+ and that's already slightly OTT. As each band gets populated (and yours must be very populated), just try a different band (AX11000 is tri-band).

Sorry, we don't have guides for logs, not something general users want to study nor would we expect them to. You can send off some feedback and private message me your email, I'll help to push the right people.

Trying to test and optimize networking performance is very technical, far more difficult than a single PC. Every single person has a different scenario, even changing the angle of the antenna can alter the reception or performance. The best thing you can do is follow the guides we have online (YouTUbe), like using an Ethernet backhaul or direct line of sight between the nodes, placing units near windows or staircases if not possible, etc.
_____________________________________________________________
FPS, Racing, and VR Gamer / Tech Enthusiast / ROG Admin

MasterC@ROG wrote:
Around 130... woah... are you running this for a business? Personally I'm at 25+ and that's already slightly OTT. As each band gets populated (and yours must be very populated), just try a different band (AX11000 is tri-band).

Sorry, we don't have guides for logs, not something general users want to study nor would we expect them to. You can send off some feedback and private message me your email, I'll help to push the right people.

Trying to test and optimize networking performance is very technical, far more difficult than a single PC. Every single person has a different scenario, even changing the angle of the antenna can alter the reception or performance. The best thing you can do is follow the guides we have online (YouTUbe), like using an Ethernet backhaul or direct line of sight between the nodes, placing units near windows or staircases if not possible, etc.


Yeah I totally get it and understand. Originally I went to school for this stuff but that was 20 years ago now so much I've missed out on with the features on these things today (god I sound old). I think I just have a hard time letting go when I don't fully understand. Really I'm just trying to learn enough to decide if I really should be RMAing it or not. I am on ethernet backhaul. I run network cables wherever I can so all my nodes were connected via that way, plus then I have two rooms connecting via additional switches that way everything that has the ability to connect with a CAT cable is. The wifi devices are all IoT things, and I have pretty much most things you can think of "smart".

I'm about to remove the AXE and go back to the setup before to see if I get the results I had before this ROG router because when I had just the ACs or the AX and AC I still had the random disconnect but thos eevents were further apart but if I go back and continue with same results it could maybe just point to something external thats changed.

As far as the logs I am pretty sure those first ones I questioned were caused by the AC55 node since removing that from the network I havent seen one since. It was either that or changing the nodes to access points. Not sure why it would cause it with the AXE though and not the AX but I also never checked the logs before my original AX died so for all I know it was hitting the same wall.

And now I'm just droning on. I really do appreciate your input and the time you spent thinking about this. This thread got me to a much better place than where I started it from which I am super grateful for.

Did you update the firmware for that AC55 unit there is/was an updated firmware version?

jzchen wrote:
Did you update the firmware for that AC55 unit there is/was an updated firmware version?


I checked but did not find any updated firmware for it. If you're talking about a beta firmware I cvouldn't find that either.

I just wanted to share that upon looking at my network more recently as I added a new Lyra Voice node that I saw a few devices that were noted as having static IPs. I don't ever recall setting them up as static and my list on the GUI is completely empty, even allowing static IPs is not enabled.

Have things gotten better?....

Saltgrass
Level 13
I have been watching this thread but really did not have must to input except many of the lines in those listings happen all the time.

If you want to pin something down, knowing the eth number and the MAC address will help isolate the exact device. If it is having problems with eth6, change it to eth7 or 8.

If it is one of the Ethernet connections, eth1- eth5 then the same would apply.

Simplifying your system for testing may also help track down problems. You have many AiMesh units so you must have a very large space if you need that many. If those spaces are on different levels, you might try altering the antenna configuration.

Personally, since I don't have ethernet backhaul I just use my routers as media bridges for those devices that have ethernet.
Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Saltgrass wrote:
I have been watching this thread but really did not have must to input except many of the lines in those listings happen all the time.

If you want to pin something down, knowing the eth number and the MAC address will help isolate the exact device. If it is having problems with eth6, change it to eth7 or 8.

If it is one of the Ethernet connections, eth1- eth5 then the same would apply.

Simplifying your system for testing may also help track down problems. You have many AiMesh units so you must have a very large space if you need that many. If those spaces are on different levels, you might try altering the antenna configuration.

Personally, since I don't have ethernet backhaul I just use my routers as media bridges for those devices that have ethernet.


Does ETH6 reference the radio band? If eth1-5 is the ethernet ports does that make eth6 the 2.4Ghz band? I know it couldn't reference the 5 or 6 bands because the devices that keep being listed are smart home devices that are 2.4 only. I have at least worked this to a stable point (for the most part) by removing the AC55 and the AX56 extenders, resetting the remaining routers and setting them in AP mode (no more mesh). Also I set the wifi bands all to the highest channel with the highest bandwidth available per an asus support rep direction. Oh and also disabled some additonal settings but can't think of what they were at the moment. Would have to check from a pc when back on home network.

I still get the Deauth_ind 7C:A6:B0:16:7F:B5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-50 fairly regularly which from what I have been able to gather from other posts and threads is supposedly when something interferes with the signal to the device or the device is moving/roaming and goes out of signal range. I can deduct the latter because the devices never move as most are a smart outlet or switch or light something like that that never changes position. So that leaves signal interference. Only thing that uses signal in my home that moves is my phone or my tablet, or on rare occasion my laptop. Could any of these really cause that much disruption?

I am content at least because it seems most devices work and if disconnected will reconnect on their own. I was at the point of resetting most of my smart home on a daily basis and even then it would be hit or miss controlling it. The deauth events now usually are only a couple different devices at a time and seemed to come every 7-10mins and then last about a 15-30 seconds.

-Aaron

Saltgrass
Level 13
In answer to the question, yes eth 6 is 2.4 7 is 5.1 and 8 is 6 Ghz.

I get the Deauth_ind quite often, not really sure why but my system is very stable. If it is dropping and reconnecting, I don't even notice.

Glad it is working better..
Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Not saure anyone still looking at this thread but if you are I'm now having some new weird issues that I again don't understand.

First off I am noticing that CORE 4 of my router is like locked at 100% usage. I cant get it to change until I reboot the router and even then it only momentarily looks normal but then will shoot back up to 100% and I dont see it change. The other 3 COREs fluctuate like I am used to seeing.

Then I am getting new log lines I I have never seen before. Lots of them so I don't even know where to begin on what to share.

This morning and now all day eventually during my normal work use of this PC I will start getting errors when trying to go to a website where it brings up a splash page saying such and such blocked redir and then telling me to run network diagnostics which can't give me any insight when running. I have to reboot at this point to regain being able to browse.

I am getting log lines where ETH1 is DOWN then UP at 1000 (logical port 😎 or something like that happening multiple times in clumps of 2 mins at a time.

I get an error regarding bcm63xx_nand timing out waiting for a command?

I get lines mentioning A.Q0S rules is less than 22 and something like setup rule fail

I see disk_monitor: Got SIGALRM...

I see my ddns keeps restarting with watchdog calling it

A reference to a zcip client being configured with an IP addy listed.

I see smbd triggered out of memory codition (oom killer not called) followed by a long list that looks like memory pages followed by what looks like a hardware/firmware check to make sure everything is working correctly or something.

rc_service: httpd 1703:notify_rc reboot
Jun 16 10:58:08 pppd[2405]: Connection terminated.
Jun 16 10:58:08 iTunes: daemon is stoped
Jun 16 10:58:08 FTP Server: daemon is stopped
Jun 16 10:58:10 Samba Server: smb daemon is stoped
Jun 16 10:58:10 Timemachine: daemon is stoped
Jun 16 10:58:10 WEBDAV Server: daemon is stoped
Jun 16 10:58:11 BWDPI: force to flush flowcache entries
Jun 16 10:58:11 BWDPI: rollback fc
Jun 16 10:58:11 WEBDAV Server: daemon is stoped
Jun 16 10:58:11 Mastiff: Got SIGTERM
Jun 16 10:58:12 iTunes: daemon is stoped
Jun 16 10:58:12 FTP Server: daemon is stopped
Jun 16 10:58:12 Samba Server: smb daemon is stoped
Jun 16 10:58:12 hour monitor: dpi engine doesn't exist
Jun 16 10:58:12 Timemachine: daemon is stoped
Jun 16 10:58:12 disk_monitor: Finish
Jun 16 10:58:12 miniupnpd[3129]: shutting down MiniUPnPd
Jun 16 10:58:14 ahs: ===Terminate ahs daemon===
Jun 16 10:58:16 kernel: ^[[0;33;41m[ERROR pktrunner] buildFlowKey,210: LAN flow is not supported: Rx 0, Tx 2^[[0m
Jun 16 10:58:16 kernel: port_generic_stop 561 skip turnning off power on eth1 here
Jun 16 10:58:16 kernel: port_generic_stop 561 skip turnning off power on eth2 here
Jun 16 10:58:16 kernel: port_generic_stop 561 skip turnning off power on eth3 here
Jun 16 10:58:16 kernel: port_generic_stop 561 skip turnning off power on eth4 here
Jun 16 10:58:16 kernel: port_generic_stop 561 skip turnning off power on eth5 here
Jun 16 10:58:16 kernel: FPM Pool 1: invalid token 0x226b8000 freed
Jun 16 10:58:17 kernel: ubi2: attaching mtd10
Jun 16 10:58:17 kernel: ubi2: scanning is finished
Jun 16 10:58:17 kernel: ubi2: attached mtd10 (name "misc1", size 8 MiB)
Jun 16 10:58:17 kernel: ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jun 16 10:58:17 kernel: ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jun 16 10:58:17 kernel: ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
Jun 16 10:58:17 kernel: ubi2: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jun 16 10:58:17 kernel: ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
Jun 16 10:58:17 kernel: ubi2: max/mean erase counter: 14/5, WL threshold: 4096, image sequence number: 340828245
Jun 16 10:58:17 kernel: ubi2: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jun 16 10:58:17 kernel: ubi2: background thread "ubi_bgt2d" started, PID 13962
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 13978
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "nvram"
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): reserved for root: 0 bytes (0 KiB)
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID C50EC67E-2752-49C8-8249-D2C960A8A3CC, small LPT model
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): un-mount UBI device 2
Jun 16 10:58:18 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" stops
Jun 16 10:58:18 kernel: ubi2: detaching mtd10
Jun 16 10:58:18 kernel: ubi2: mtd10 is detached
Jun 16 10:58:18 get_ext_phy_id: 0/1/0/1
May 4 22:05:11 kernel: klogd started: BusyBox v1.24.1 (2022-02-17 15:29:22 CST)
May 4 22:05:11 kernel: Upload the firmware into the on-chip memory
May 4 22:05:11 kernel: ^M0%^M1%^M2%^M3%^M4%^M5%^M6%^M7%^M8%^M9%^M10%^M11%^M12%^M13%^M14%^M15%^M16%^M17%^M18%^M19%^M20%^M21%^M22%^M23%^M24%^M25%^M26%^M27%^M28%^M29%^M30%^M31%^M32%^M33%^M34%^M35%^M36%^M37%^M38%^M39%^M40%^M41%^M42%^M43%^M44%^M45%^M46%^M47%^M48%^M49%^M50%^M51%^M52%^M53%^M54%^M55%^M56%^M57%^M58%^M59%^M60%^M61%^M62%^M63%^M64%^M65%^M66%^M67%^M68%^M69%^M70%^M71%^M72%^M73%^M74%^M75%^M76%^M77%^M78%^M79%^M80%^M81%^M82%^M83%^M84%^M85%^M86%^M87%^M88%^M89%^M90%^M91%^M92%^M93%^M94%^M95%^M96%^M97%^M98%^M99%^M100%
May 4 22:05:11 kernel: Reset the processors to start execution of the code in the on-chip memory
May 4 22:05:11 kernel: Verify that the processors are running: OK
May 4 22:05:11 kernel: Verify that the firmware has been loaded with good CRC: OK
May 4 22:05:11 kernel: Firmware loading completed successfully
May 4 22:05:11 kernel: BCMENET: Enabling Software GSO for eth0
May 4 22:05:11 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
May 4 22:05:11 kernel: LAG/Trunking enabled <0x08>
May 4 22:05:11 kernel: getrcal for res select 5, int 664, ext 638, ratio 122 ratio1 152, rcal 9
May 4 22:05:11 kernel: Setting SGMII Calibration value to 0x9
May 4 22:05:11 kernel: PLL_PON(8051): 0x0250; TX_PON(8067): 0x0048; RX_PON(80b2): 0x0980
May 4 22:05:11 kernel: eth0: Down <04:42:1A:4E:A5:10>
May 4 22:05:11 kernel: Chip Port 10, CrossBar Port 1, PHY_ID <0x0007f00c:0x0c: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 4 22:05:11 kernel: eth1: Down <04:42:1A:4E:A5:10> PHY_ID <0x0007f008:0x08: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 4 22:05:11 kernel: eth2: Down <04:42:1A:4E:A5:10> PHY_ID <0x0007f009:0x09: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 4 22:05:11 kernel: eth3: Down <04:42:1A:4E:A5:10> PHY_ID <0x0007f00a:0x0a: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 4 22:05:11 kernel: eth4: Down <04:42:1A:4E:A5:10> PHY_ID <0x0007f00b:0x0b: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 4 22:05:11 kernel: eth5: Down <04:42:1A:4E:A5:10>
May 4 22:05:11 kernel: Chip Port 9, CrossBar Port 0, PHY_ID <0x06180006:0x06:External 2.5G SERDES> Cfg: ANG.2.5G; Down
May 4 22:05:11 kernel: PHY_ID <0x0388001e:0x1e:External Cascaded 10G EXT3> Cfg: ANG.2.5G; Down ===> Activate Deep Green Mode
May 4 22:05:11 kernel: bcmswlpbk0 (Ext switch port: 😎 (Logical Port: 😎 Virtual link DOWN
May 4 22:05:11 kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
May 4 22:05:11 kernel: bcm_enet_init:L2396 ENET system contructed and configured enet-kthrd thread
May 4 22:05:11 kernel: enet_kthread_handler:L295 Instantiating ENET thread
May 4 22:05:11 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:PktRnr[0]:Create Index Pool_Size = 16512^[[0m
May 4 22:05:11 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:L2L3-ucast:Create Index Pool_Size = 16384^[[0m
May 4 22:05:11 kernel: Initialized Runner Host Layer
May 4 22:05:11 kernel: Initialized Runner Unicast Layer
May 4 22:05:11 kernel: Initialized Runner L2 Unicast Layer
May 4 22:05:11 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:mcast:Create Index Pool_Size = 128^[[0m
May 4 22:05:11 kernel: Initialized Runner Multicast Layer
May 4 22:05:11 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:FHW[0]:Create Index Pool_Size = 16512^[[0m
May 4 22:05:11 kernel: Retrieve num_fhw_path=64
May 4 22:05:11 kernel: ^[[0;36;44mPathstats allocated 2048 bytes^[[0m
May 4 22:05:11 kernel: ^[[0;36;44mBroadcom Packet Flow Cache HW acceleration enabled.^[[0m
May 4 22:05:11 kernel: Enabled Runner binding to Flow Cache
May 4 22:05:11 kernel: Initialized Runner Protocol Layer (800)
May 4 22:05:11 kernel: Broadcom Runner Blog Driver Char Driver v0.1 Registered <309>
May 4 22:05:11 kernel: Lservices Loaded - NComm, Inc.
May 4 22:05:11 kernel: exLinuxETH Loaded - NComm, Inc.
May 4 22:05:11 kernel: PCIe HCD (impl1)^M
May 4 22:05:11 kernel: bcm963xx-pcie: [2] DT node available: /pcie@80060000
May 4 22:05:11 kernel: bcm963xx-pcie: found port [2] GEN2 Core Rev [3.04] with 1 Lanes^M
May 4 22:05:11 kernel: getrcal for res select 5, int 664, ext 638, ratio 122 ratio1 152, rcal 9
May 4 22:05:11 kernel: bcm963xx-pcie: Core [2] setting resistor calibration value to 0x9
May 4 22:05:11 kernel: bcm963xx-pcie: core [2] Link UP - [1] lanes, [GEN2] speed^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [2] Enabled PCIE/UBUS Error Interrupts^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [2] UBUS Intr [UBUS_LINKUP]^M
May 4 22:05:11 kernel: bcm963xx-pcie: [1] DT node available: /pcie@80050000
May 4 22:05:11 kernel: bcm963xx-pcie: found port [1] GEN2 Core Rev [3.04] with 1 Lanes^M
May 4 22:05:11 kernel: getrcal for res select 5, int 664, ext 638, ratio 122 ratio1 152, rcal 9
May 4 22:05:11 kernel: bcm963xx-pcie: Core [1] setting resistor calibration value to 0x9
May 4 22:05:11 kernel: bcm963xx-pcie: core [1] Link UP - [1] lanes, [GEN2] speed^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [1] Enabled PCIE/UBUS Error Interrupts^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [1] UBUS Intr [UBUS_LINKUP]^M
May 4 22:05:11 kernel: bcm963xx-pcie: [0] DT node available: /pcie@80040000
May 4 22:05:11 kernel: bcm963xx-pcie: found port [0] GEN2 Core Rev [3.04] with 2 Lanes^M
May 4 22:05:11 kernel: getrcal for res select 5, int 664, ext 638, ratio 122 ratio1 152, rcal 9
May 4 22:05:11 kernel: bcm963xx-pcie: Core [0] setting resistor calibration value to 0x9
May 4 22:05:11 kernel: bcm963xx-pcie: core [0] Link UP - [2] lanes, [GEN2] speed^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [0] Enabled PCIE/UBUS Error Interrupts^M
May 4 22:05:11 kernel: bcm963xx-pcie: Core [0] UBUS Intr [UBUS_LINKUP]^M
May 4 22:05:11 kernel: ^[[1m^[[34mWifi Forwarding Driver is initialized!^[[0m
May 4 22:05:11 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May 4 22:05:11 kernel: brcm_otp_init entry
May 4 22:05:11 kernel: ubi2: attaching mtd10
May 4 22:05:11 kernel: ubi2: scanning is finished
May 4 22:05:11 kernel: ubi2: attached mtd10 (name "misc1", size 8 MiB)
May 4 22:05:11 kernel: ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 4 22:05:11 kernel: ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 4 22:05:11 kernel: ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
May 4 22:05:11 kernel: ubi2: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 4 22:05:11 kernel: ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
May 4 22:05:11 kernel: ubi2: max/mean erase counter: 14/5, WL threshold: 4096, image sequence number: 340828245
May 4 22:05:11 kernel: ubi2: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 4 22:05:11 kernel: ubi2: background thread "ubi_bgt2d" started, PID 376
May 4 22:05:11 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 391
May 4 22:05:11 kernel: UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "nvram"
May 4 22:05:11 kernel: UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 4 22:05:11 kernel: UBIFS (ubi2:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May 4 22:05:11 kernel: UBIFS (ubi2:0): reserved for root: 0 bytes (0 KiB)
May 4 22:05:11 kernel: UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID C50EC67E-2752-49C8-8249-D2C960A8A3CC, small LPT model
May 4 22:05:11 kernel: UBIFS (ubi2:0): un-mount UBI device 2
May 4 22:05:11 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" stops
May 4 22:05:11 kernel: ubi2: detaching mtd10
May 4 22:05:11 kernel: ubi2: mtd10 is detached
May 4 22:05:11 kernel: random: init urandom read with 7 bits of entropy available
May 4 22:05:11 kernel: Loading HND Module
May 4 22:05:11 kernel: igs_module_init:867: IGS 29 create network socket successful
May 4 22:05:11 kernel: dpsta_init: 17.10.157.2802 (r794271) cf953dc Jan 12 2021 15:19:57 msglevel 0x1
May 4 22:05:11 kernel: osl_skb_audit: PASS
May 4 22:05:11 kernel: wl_module_init: passivemode set to 0x1
May 4 22:05:11 kernel: wl_module_init: txworkq set to 0x0
May 4 22:05:11 kernel: ^[[0;32mwl_pktfwd_sys_init: ^[[1m^[[34mWL_PKTFWD[1.1.0]^[[0m Success^[[0m
May 4 22:05:11 kernel: DHD_FKB_POOL size is:1280 and entry size:2816
May 4 22:05:11 kernel: DHD_PKTTAG POOL size is:2592 and entry size:128
May 4 22:05:11 kernel: ^[[0;32mdhd_pktfwd_sys_init: ^[[1m^[[34mdhd_PKTFWD[1.0.0]^[[0m Success^[[0m
May 4 22:05:11 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device AAA4(good PCI location)
May 4 22:05:11 kernel: dor0: runner supported ring format types TxP 0x5, RxP 0x3 TxC 0x3 RxC 0x3^M
May 4 22:05:11 kernel: dhd_runner_attach: Tx Offload - Enabled, Ring Size = 1024
May 4 22:05:11 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 4 22:05:11 kernel: TX wakeup info: reg = <0x82299004>, val = <0x10000000>
May 4 22:05:11 kernel: RX wakeup info: reg = <0x8229a004>, val = <0x28000000>
May 4 22:05:11 kernel: dhd_attach(): thread:dhd_watchdog_thread:304 started
May 4 22:05:11 kernel: ^[[0;31mwfd_bind: wfd0-thrd initialized pktlists: radio 0 nodes 1032 xfer dhd_pktfwd_xfer_callback+0x0/0x798 [dhd]
May 4 22:05:11 kernel: ^[[0m
May 4 22:05:11 kernel: Creating CPU ring for queue number 0 with 1024 packets descriptor=0xffffffbffc5c02c0
May 4 22:05:11 kernel: Creating CPU ring for queue number 1 with 1024 packets descriptor=0xffffffbffc5c0300
May 4 22:05:11 kernel: ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 0 wl_radio_idx 0 Type fkb:sll configured WFD thread wfd0-thrd minQId/maxQId (8/9), status (0) qmask 0x3^[[0m
May 4 22:05:11 kernel: Instantiating WFD 0 thread
May 4 22:05:11 kernel: ^[[0;32mdhd_wfd_bind: wl0 wfd_idx 0 success^[[0m
May 4 22:05:11 kernel: dor0: MSG Ring format set to 1
May 4 22:05:11 kernel: dhd_runner_flowmgr_init: dhd0_rnr bootmem addr size<11534336>
May 4 22:05:11 kernel: dhd_runner_profile_init: profile = 3 1024/0512 2048/1024 1024/0512 0512/0512 0512/0512
May 4 22:05:11 kernel: ^[[0;33;40mRunner DHD PCIE: vendor<0x14e4> device<0xaaa4> bus<1> slot<0>^[[0m
May 4 22:05:11 kernel: Initial configuration
May 4 22:05:11 kernel: =================================
May 4 22:05:11 kernel: rx_post_flow_ring_base_addr : ffffffc02e4dc000
May 4 22:05:11 kernel: tx_post_flow_ring_base_addr : ffffffc00a8d8000
May 4 22:05:11 kernel: rx_complete_flow_ring_base_addr : ffffffc02e500000
May 4 22:05:11 kernel: tx_complete_flow_ring_base_addr : ffffffc02e4de000
May 4 22:05:11 kernel: r2d_wr_arr_base_addr : ffffff80025e9000
May 4 22:05:11 kernel: d2r_rd_arr_base_addr : ffffff80025e9802
May 4 22:05:11 kernel: r2d_rd_arr_base_addr : ffffff80025ea000
May 4 22:05:11 kernel: d2r_wr_arr_base_addr : ffffff80025e9c02
May 4 22:05:11 kernel: tx_post_mgmt_arr_base_addr : ffffff80025ea800
May 4 22:05:11 kernel: tx_post_mgmt_arr_base_phys_addr : 0x2e1d1800
May 4 22:05:11 kernel: r2d_wr_arr_base_phys_addr : 0x2e1d0000
May 4 22:05:11 kernel: d2r_rd_arr_base_phys_addr : 0x2e1d0802
May 4 22:05:11 kernel: r2d_rd_arr_base_phys_addr : 0x2e1d1000
May 4 22:05:11 kernel: d2r_wr_arr_base_phys_addr : 0x2e1d0c02
May 4 22:05:11 kernel: Doorbell Post Wakeup register : phy_addr: 0xe0802160, virt_addr: ffffff80025e2160
May 4 22:05:11 kernel: Doorbell Complete Wakeup register : phy_addr: 0xe0802164, virt_addr: ffffff80025e2164
May 4 22:05:11 kernel: Doorbell ISR : ffffffbffcf40ab0
May 4 22:05:11 kernel: Doorbell CTX : ffffffc02fef2000
May 4 22:05:11 kernel: flow_ring_format : 1
May 4 22:05:11 kernel: idma_active : 1
May 4 22:05:11 kernel: Backup queue configuration:
May 4 22:05:11 kernel: ========================================
May 4 22:05:11 kernel: Base virt address = ffffffc00df00000, physical address = DF00000
May 4 22:05:11 kernel: Index stack virt address = ffffffc00dfe38c0, physical address = DFE38C0
May 4 22:05:11 kernel: Backup queue entries: total = 58250 shared by all radios
May 4 22:05:11 kernel: ========================================
May 4 22:05:11 kernel: Creating CPU ring for queue number 7 with 128 packets descriptor=0xffffffbffc303338, size_of_entry 16
May 4 22:05:11 kernel: Done initializing Ring 7 Base=0xffffff80003e3000 End=0xffffff80003e3800 calculated entries= 128 RDD Base=3e012000K descriptor=0xffffffbffc303338
May 4 22:05:11 kernel: ^[[0;33;40mRunner DHD Offload initialization complete^[[0m
May 4 22:05:11 kernel: CUR_ETHERADDR : 6
May 4 22:05:11 kernel: 04 42 1a 4e a5 10
May 4 22:05:11 kernel: Dongle Host Driver, version 17.10.157.2803 (r795020)
May 4 22:05:11 kernel: Compiled in drivers/net/wireless/bcmdhd
May 4 22:05:11 kernel: wfd_registerdevice Successfully registered dev eth6 ifidx 0 wfd_idx 0
May 4 22:05:11 kernel: Register interface [eth6] MAC: 04:42:1a:4e:a5:10
May 4 22:05:11 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device AAA4(good PCI location)
May 4 22:05:11 kernel: dor1: runner supported ring format types TxP 0x5, RxP 0x3 TxC 0x3 RxC 0x3^M
May 4 22:05:11 kernel: dhd_runner_attach: Tx Offload - Enabled, Ring Size = 1024
May 4 22:05:11 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
May 4 22:05:11 kernel: TX wakeup info: reg = <0x82299004>, val = <0x11000000>
May 4 22:05:11 kernel: RX wakeup info: reg = <0x8229a004>, val = <0x29000000>
May 4 22:05:11 kernel: dhd_attach(): thread:dhd_watchdog_thread:30b started
May 4 22:05:11 kernel: ^[[0;31mwfd_bind: wfd1-thrd initialized pktlists: radio 1 nodes 1032 xfer dhd_pktfwd_xfer_callback+0x0/0x798 [dhd]
May 4 22:05:11 kernel: ^[[0m
May 4 22:05:11 kernel: Creating CPU ring for queue number 2 with 1024 packets descriptor=0xffffffbffc5c0340
May 4 22:05:11 kernel: Creating CPU ring for queue number 3 with 1024 packets descriptor=0xffffffbffc5c0380
May 4 22:05:11 kernel: ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 1 wl_radio_idx 1 Type fkb:sll configured WFD thread wfd1-thrd minQId/maxQId (10/11), status (0) qmask 0xc^[[0m
May 4 22:05:11 kernel: Instantiating WFD 1 thread
May 4 22:05:11 kernel: ^[[0;32mdhd_wfd_bind: wl1 wfd_idx 1 success^[[0m
May 4 22:05:11 kernel: <=== Deactivate Deep Green Mode
May 4 22:05:11 kernel: bcmswlpbk0 (Ext switch port: 😎 (Logical Port: 😎 Virtual link UP
May 4 22:05:11 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link Up at 1000 mbps full duplex
May 4 22:05:11 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex





etc etc etc... 😞 What the heck happened or is happening?