RT-AC5300 Kernel Flash Errors

[AndyBlak]

Howdy folks!

Over the past month or so, I've been experiencing intermittent network drops on both hardwired and Wi-Fi devices. During these incidents, neither my ISP modem, nor my router show any signs of distress in terms of the LEDs. At first, I dismissed these incidents as the inevitably expected ISP interrupts, and thought nothing of them. As the frequency of the incidents increased, I began normal network troubleshooting, still believing the issue was ISP based. Restarting the router, the modem, checking cables and power supplies, etc.

After two of the described drops within the short time of coming home after work today, I decided it was time to hop into the system log on my router, and sure enough, I found some interesting errors.

Jun 25 21:29:11 kernel: ACCEPT IN=br0 OUT=eth0 SRC=192.168.XX.XX DST=54.XX.XX.XX LEN=1498 TOS=0x00 PREC=0x00 TTL=63 ID=5087 DF PROTO=UDP SPT=49344 DPT=5001 LEN=1478
Feb 13 18:00:16 kernel: pflash: found no supported devices
Feb 13 18:00:16 kernel: bcmsflash: found no supported devices
Feb 13 18:00:16 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Feb 13 18:00:16 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Feb 13 18:00:23 Mastiff: init
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

The most baffling part of this output, in my opinion, is the strange shift in dates within the logs. I Googled the messages, and I am aware that they appear to be related to flash storage drivers. I immediately reformatted the USB drive attached to the router, but another drop happened after that.

I'd be happy to provide any further information, and any assistance is appreciated!

-Andy

 

[RMerlin]

All those log messages are perfectly normal. This is just the Linux kernel probing the hardware to determine if it supports certain features, and move on if it doesn't.

The date shift is also normal, routers don't have a battery backed up clock. Their clock gets reset every reboot.

 

[AndyBlak]

All those log messages are perfectly normal. This is just the Linux kernel probing the hardware to determine if it supports certain features, and move on if it doesn't.

The date shift is also normal, routers don't have a battery backed up clock. Their clock gets reset every reboot.

Ah, understood, sir. Thank you so much for the clarification!

Do you have any suggestions for what data/tools should use, and/or how I should approach the intermittent drop issue, please?

 

[RMerlin]

Start by determining if it's a LAN-side or WAN-side issue, by trying to ping other LAN devices during the outage.

 

[AndyBlak]

Start by determining if it's a LAN-side or WAN-side issue, by trying to ping other LAN devices during the outage.

Many thanks for your assistance, sir! I've not had any further issues, so I'm inclined to think it really was just ISP drops. Nonetheless, I greatly appreciate the guidance.

Have a good one!

-Andy

 

[AndyBlak]

Merlin,

The issue has unfortunately returned. I've isolated it specifically to the LAN. After a drop last night, I immediately attempted to connect to my router from a browser, and just got a blank page with infinite loading. I quickly swapped my Cat6 from the switch on the back of the ASUS router to direct connection with my ISP modem, and was able to load pages fine. Once I was able to look at the log, I found this:

Feb 13 18:00:16 kernel: pflash: found no supported devices
Feb 13 18:00:16 kernel: bcmsflash: found no supported devices
Feb 13 18:00:16 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Feb 13 18:00:16 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Feb 13 18:00:23 Mastiff: init
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jun 26 04:02:40 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Feb 13 18:00:17 kernel: pflash: found no supported devices
Feb 13 18:00:17 kernel: bcmsflash: found no supported devices
Feb 13 18:00:17 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Feb 13 18:00:17 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Feb 13 18:00:24 Mastiff: init
Jul  3 04:02:54 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul  3 04:02:54 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul  3 04:02:54 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Feb 13 18:00:17 kernel: pflash: found no supported devices
Feb 13 18:00:17 kernel: bcmsflash: found no supported devices
Feb 13 18:00:17 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Feb 13 18:00:17 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Feb 13 18:00:25 Mastiff: init
Jul 10 04:02:59 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 10 04:02:59 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 10 04:02:59 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

Does this give us any more hints? Or is this still normal activity?

Disregard. Just compared it to previous log post.