What's new

RT-AX86U crashing and rebooting few times a day

  • 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!

imisic

New Around Here
Hi,

I have a RT-AX86U (3.0.0.4.388_22525) with two Ai-Mesh nodes RT-AX59U (3.0.0.4.388_31345) and RP-AX56 (3.0.0.4.386_42860).

Last few days I'm having a lot of problems. AX86U would reboot, most often a dozen times in row.
Tried disconnecting everything but for some reason it doesn't help.

Does anyone know what might be the problem?
Full log is attached, small sample following below.

Code:
May  5 07:05:09 crashlog: LOG
May  5 07:05:09 crashlog: <6>pci 0001:01:00.0: BAR 4: assigned [mem 0xd0c00000-0xd0cfffff 64bit pref]
May  5 07:05:09 crashlog: <6>pci 0001:01:00.0: BAR 0: assigned [mem 0xd0800000-0xd080ffff 64bit]
May  5 07:05:09 crashlog: <6>pci 0001:00:00.0: PCI bridge to [bus 01]
May  5 07:05:09 crashlog: <6>pci 0001:00:00.0:   bridge window [mem 0xd0000000-0xd0bfffff]
May  5 07:05:09 crashlog: <6>pci 0001:00:00.0:   bridge window [mem 0xd0c00000-0xd0cfffff 64bit pref]
May  5 07:05:09 crashlog: <6>pcieport 0001:00:00.0: enabling device (0000 -> 0002)
May  5 07:05:09 crashlog: <6>pcieport 0001:00:00.0: Max Payload Size set to  512/ 512 (was  128), Max Read Rq  512
May  5 07:05:09 crashlog: <6>pci 0001:01:00.0: Max Payload Size set to  512/ 512 (was  128), Max Read Rq  512
May  5 07:05:09 crashlog: <4>  bcm963xx-pcie: [2] DT node available: /pcie@80060000
May  5 07:05:09 crashlog: <4>  bcm963xx-pcie: found port [2] GEN2 Core Rev [3.04] with 1 Lanes^M
May  5 07:05:09 crashlog: <4>getrcal for res select 5, int 665, ext 622, ratio 119 ratio1 164, rcal 10
May  5 07:05:09 crashlog: <4>  bcm963xx-pcie: Core [2] setting resistor calibration value to 0xa
May  5 07:05:09 crashlog: <4>  bcm963xx-pcie: core [2] link is DOWN^M
May  5 07:05:09 crashlog: <4>  bcm963xx-pcie: core [2] powered down^M
May  5 07:05:09 crashlog: <4>^[[1m^[[34mWifi Forwarding Driver is initialized!^[[0m
May  5 07:05:09 crashlog: <6>bcmspu: loading driver
May  5 07:05:09 crashlog: <2>broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May  5 07:05:09 crashlog: <4>brcm_otp_init entry
May  5 07:05:09 crashlog: <5>ubi2: attaching mtd10
May  5 07:05:09 crashlog: <5>ubi2: scanning is finished
May  5 07:05:09 crashlog: <5>ubi2: attached mtd10 (name "misc1", size 8 MiB)
May  5 07:05:09 crashlog: <5>ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May  5 07:05:09 crashlog: <5>ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May  5 07:05:09 crashlog: <5>ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
May  5 07:05:09 crashlog: <5>ubi2: good PEBs: 63, bad PEBs: 1, corrupted PEBs: 0
May  5 07:05:09 crashlog: <5>ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
May  5 07:05:09 crashlog: <5>ubi2: max/mean erase counter: 16/6, WL threshold: 4096, image sequence number: 1725884149
May  5 07:05:09 crashlog: <5>ubi2: available PEBs: 0, total reserved PEBs: 63, PEBs reserved for bad PEB handling: 3
May  5 07:05:09 crashlog: <5>ubi2: background thread "ubi_bgt2d" started, PID 379
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 394
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "nvram"
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): reserved for root: 0 bytes (0 KiB)
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 4B2A44DD-417E-46D8-97CE-24D278768884, small LPT model
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): un-mount UBI device 2
May  5 07:05:09 crashlog: <5>UBIFS (ubi2:0): background thread "ubifs_bgt2_0" stops
May  5 07:05:09 crashlog: <5>ubi2: detaching mtd10
May  5 07:05:09 crashlog: <5>ubi2: mtd10 is detached
May  5 07:05:09 crashlog: <5>random: init urandom read with 6 bits of entropy available
May  5 07:05:09 crashlog: <4>jffs2: Empty flash at 0x012d78ac ends at 0x012d8000
May  5 07:05:09 crashlog: <4>jffs2: Empty flash at 0x022aa9dc ends at 0x022ab000
May  5 07:05:09 crashlog: <4>jffs2: Empty flash at 0x022b91a8 ends at 0x022b9800
May  5 07:05:09 crashlog: <4>jffs2: Empty flash at 0x02c2f5e0 ends at 0x02c2f800
May  5 07:05:09 crashlog: <4>Loading HND Module
May  5 07:05:09 crashlog: <4>crossbar[0]: del cb_idx=0 ext_ep=0 SERDES:6

Thanks
 

Attachments

  • syslog.txt
    362.8 KB · Views: 44
Last edited:
Welcome to the forums @imisic.

Three different routers, three different firmware. Ouch.

When you say you tried disconnecting everything, what does that mean exactly?

Do you have any USB devices plugged into the main router and/or nodes? Safely remove them, and do a full system reboot if so.

If you physically power down the nodes and reboot the main router, does the rebooting continue?

If you physically power down the nodes, and all (wired) attached devices, and reboot the main router, does the rebooting continue?

If you do the above, change the SSIDs (temporarily), and reboot the main router, does the rebooting continue?

If after testing the above scenarios and you don't find a specific device/client that is causing these issues, I would be doing a full reset of the network at this point.

After a full reset, do not plug in any USB drives during your testing phase. Do not use any saved backup config files. Do a minimal and manual configuration and only introduce new features/options after you have fully tested (including doing a manual, GUI, reboot) the base configurations first.

Also, more information would be helpful too.

When was the last time you upgraded the firmware? When was the last time you did a full reset to the factory defaults of the nodes, and set them up again? When was the last time you did a full reset of the main router and set it up without using saved backup config files?

The following links may also be of use too.




 
Welcome to the forums @imisic.

Three different routers, three different firmware. Ouch.

When you say you tried disconnecting everything, what does that mean exactly?

Do you have any USB devices plugged into the main router and/or nodes? Safely remove them, and do a full system reboot if so.

If you physically power down the nodes and reboot the main router, does the rebooting continue?

If you physically power down the nodes, and all (wired) attached devices, and reboot the main router, does the rebooting continue?

If you do the above, change the SSIDs (temporarily), and reboot the main router, does the rebooting continue?

If after testing the above scenarios and you don't find a specific device/client that is causing these issues, I would be doing a full reset of the network at this point.

After a full reset, do not plug in any USB drives during your testing phase. Do not use any saved backup config files. Do a minimal and manual configuration and only introduce new features/options after you have fully tested (including doing a manual, GUI, reboot) the base configurations first.

Also, more information would be helpful too.

When was the last time you upgraded the firmware? When was the last time you did a full reset to the factory defaults of the nodes, and set them up again? When was the last time you did a full reset of the main router and set it up without using saved backup config files?

The following links may also be of use too.





Thanks.

Yeah, 3 different I got in different times as need for coverage was growing, Although I could go without RP-AX56

Disconnecting everything = all mesh nodes off and all wired devices disconnected
I don't have any USB devices plugged in.

If you physically power down the nodes, and all (wired) attached devices, and reboot the main router, does the rebooting continue?
Yes, and there is no pattern, sometimes it would do 5 cycles, sometimes that would be 10+, always gets to point where WiFi gets ON for a minute, about to connect PPPoE, then gets in to new reboot.

If you do the above, change the SSIDs (temporarily), and reboot the main router, does the rebooting continue?
Interesting, but as it looks like based on your comments I will have to do full reset. Reason more as for main router I haven't done this at all, nodes where reset as I was setting them up, AX56 some 6 months back, AX59U 2-3 weeks back.

There were no changes for last 2 weeks (last was me adding AX59U), FW update was mid Feb for AX86U. This is what's bothering me as I haven't changed anything when this started to happen.

Thanks for your help, will go trough those links too but as you suggested hard reset would be needed.
 

Latest threads

Sign Up For SNBForums Daily Digest

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