AX88U strange log entries - help needed

Sabbath81

Occasional Visitor
Hello guys,

im running latest stable Merlin WRT on my AX88U and i need some advice here.

i would like to ask for some assistance on strange log entries, some of which cause the device to stuck, and needs rebooting:

1. Which entries are problems from the ones below?
2. These started to occur recently , how can i fix them? Most likely they are the reason for the device to hung.
May 17 17:10:06 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x8
May 17 17:10:06 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
May 17 17:21:57 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 17 17:21:57 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
May 17 17:57:42 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 17 17:57:42 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
May 17 17:59:56 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
May 17 17:59:56 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
May 17 18:15:03 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 17 18:15:03 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
May 17 19:33:36 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 17 19:33:36 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
3. What are these:
May 5 08:05:08 wsdd2[1252]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 08:05:08 wsdd2[1252]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 08:05:12 wsdd2[1252]: Terminated received.
4. After boot i notice transmission reports errors, although there are such dirs and there is some mount:
May 17 20:23:53 transmission-daemon[3307]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:97)
May 17 20:23:53 transmission-daemon[3307]: watchdir:inotify Failed to setup watchdir "/mnt/WDHDD/Torrents/Watch": No such file or directory (2) (watchdir-inotify.c:171)
May 17 20:23:53 transmission-daemon[3307]: watchdir Failed to open directory "/mnt/WDHDD/Torrents/Watch" (2): No such file or directory (watchdir.c:358)

Thank you!
 

JGrana

Very Senior Member
I would hazard a guess that your routers NAND flash chip is borderline defective. This memory contains the /jffs directory and other critical areas used by the firmware.

Another user of a similar class router had similar timeouts/failures and pinged the Linux kernel developers for some help:

On Sun, Feb 06, 2022 at 09:57:15AM -0500, MP wrote:
>
> Hello all,
>
> Just looking for a bit of guidance here and a suggestion on proper next
> steps. I think there may be an issue within the below broadcom nand driver
> implementation.
>
> I have an Asus GTE-AX11000 and it reboots\crashes multiple times a week,
> upon inspection of snmp logging you can see the below entries, when the
> kernel panic occurs the entire router locks up, and sometimes reboots.
> Sometimes it doesn't reboot and the router hangs completely and drops all
> network devices, and removes wireless SSIDs and all of your devices lose
> their connection.
>
> Not sure who to turn to but Asus support has not grasped the gravity of this
> problem and I am thinking this can only really be resolved with a
> firmware\driver\linux update, so just hoping for some additional help or
> guidance from this group.

This is a very old, obsolete, and known buggy kernel version running any
number of unknown closed source kernel modules. Only the manufacturer
can help you here, there is nothing the community can do at all, sorry.

Best of luck!

greg k-h

For starters, you might want to try and re-format the NAND flash. Go to the Administration->System tab in the GUI and select “Format JFFS partition at next boot” Yes.
Reboot and hope it’s maybe a bad block that needs to be marked during format.
Note - you will lose anything you have put in /jffs - Entware, Addons etc.
So, be prepared to setup the router again from scratch.
If this fixes things - great. If you continue to get bcm63xx_nand errors, time to RMA the router…
 

Sabbath81

Occasional Visitor
I would hazard a guess that your routers NAND flash chip is borderline defective. This memory contains the /jffs directory and other critical areas used by the firmware.

Another user of a similar class router had similar timeouts/failures and pinged the Linux kernel developers for some help:



For starters, you might want to try and re-format the NAND flash. Go to the Administration->System tab in the GUI and select “Format JFFS partition at next boot” Yes.
Reboot and hope it’s maybe a bad block that needs to be marked during format.
Note - you will lose anything you have put in /jffs - Entware, Addons etc.
So, be prepared to setup the router again from scratch.
If this fixes things - great. If you continue to get bcm63xx_nand errors, time to RMA the router…
Hello,

thank you. The device is 12months old, it used to work flawlessly until last 2 weeks, when this happened.

Is it possible the problem to be caused by the following: my SSD flash drive which was used to run entware and add-ons failed, so i replaced it with a new one, installed everything again but without formatting JFFS?

As for the transmission - problem solved.
 

L&LD

Part of the Furniture
Anything is possible. With such an easy way to check, just do it.

Safely remove the new drive from the router and format it on a PC with NTFS file format. Save any files you want to save, but do not restore them for testing purposes below until after you are satisfied the hardware is working properly first.

Format the JFFS partition (click the button to format on next boot, be sure you hit 'Apply' at the bottom of that GUI page, then reboot the router 3 times in the next 15 minutes, making sure to allow the router to idle 5 to 10 minutes between reboots.

Now, insert the drive you formatted above, ssh into the router, and via the amtm menu, format it to Ext4 with journaling, add a 5 or 10GB swap file, and then re-install the scripts you want, from scratch.

Monitor the router/network to see if the above log entries return.
 

Sabbath81

Occasional Visitor
I will do the suggested actions if this happens again. After the last reboot, 3 days ago, log is empty.
 

Similar threads

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