Is there a way to collect information after an Asuswrt-Merlin crash?

[HyperCris]

I have a RT-AC86U with an Asuswrt-Merlin 384.13 and I'm happy with it the only problem I have is that the
router crash and reboot itself more or less once a week.
My configuration is nothing fancy: basic configuration as main router after a fiber modem/router, parental control, traffic analyzer and a SMB share on the USB 3.
Up to now I didn't see any specific problem on the system log for example last crash was like:

ov 9 23:36:54 smbd[9867]: [2019/11/09 23:36:54.559869, 0] smbd/negprot.c:706(reply_negprot)
Nov 9 23:36:54 smbd[9867]: No protocol supported !
Nov 9 23:36:54 smbd[9870]: [2019/11/09 23:36:54.710327, 0] smbd/negprot.c:706(reply_negprot)
Nov 9 23:36:54 smbd[9870]: No protocol supported !
May 5 07:05:07 kernel: nand: Could not find valid ONFI parameter page; aborting
May 5 07:05:07 kernel: brcmboard registered
May 5 07:05:07 kernel: genirq: Flags mismatch irq 36. 00000000 (brcm_36) vs. 00000000 (brcm_36)
May 5 07:05:07 kernel: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:07 kernel: pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:07 kernel: pci 0001:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:07 kernel: pci 0001:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:07 kernel: broadcomThermalDrv brcm-therm: init (CPU count 2 2 2 2)
May 5 07:05:07 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
May 5 07:05:07 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
May 5 07:05:07 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 07:05:07 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
May 5 07:05:07 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 07:05:12 acsd: selected channel spec: 0x100a (10)
May 5 07:05:12 acsd: Adjusted channel spec: 0x100a (10)
May 5 07:05:12 acsd: selected channel spec: 0x100a (10)
May 5 07:05:13 wsdd2[889]: error: wsdd-mcast-v4: wsd_send_soap_msg: send

Is there any way to dig deeper to see what's happening?

Thanks

Cris

 

[CaptainSTX]

I have had some of the same issues with my AC86. It is my understanding that what you see with the May 5 dates is the router after it has begun the re-initializing cycle and the cause is prior to that.

I found by trying 384.14 alpha and now 384.14 beta that my AC86 became more stable. Give it a try.

 

[HyperCris]

Thanks for sharing.
Since, except that problem, the software is working very well I was waiting for the stable release of 384.14.
I was used to the Netgear software and Asuswrt-Merlin is another planet no matter what!