RT-AC86U both CPU on 100%

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

NGI

Regular Contributor
Recently I started to experience a problem where bot CPUs get 100% utilization and I'm pretty certain it is related to my external USB drive. It appears to me that the CPU is mainly used by /usr/sbin/smbd -D -s /etc/smb.conf (see attached) and I have constant logs like Dec 7 11:01:40 RT-AC86U-4AB0 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0 (see attached). I have done the health-check and reformatting the USB drive and disable and enable SAMBA (or any changes related to R/W permissions to the USB on that page) and whiles this fixes the problem initially for few days the problem seems to come back after few days. The drive is less than 2 months old Patriot Memory Supersonic Rage Elite USB 3.1 Gen. 1, 128GB Flash Drive plugged into the USB 2 slot configured with 2GB SWAP on one partition with Ext4 and Journaling. Any ideas what may cause this problem?
 

Attachments

  • CPU Log.png
    CPU Log.png
    161.6 KB · Views: 107
  • CPU.png
    CPU.png
    121.7 KB · Views: 108
  • SYS Log.png
    SYS Log.png
    266 KB · Views: 104

john9527

Part of the Furniture
This is a pure guess....
I see that drive is one of the super fast USBs (400MB/s) which means it probably implements UASP. It's been my experience that linux doesn't play well with UASP, and in most cases sets a usb.quirk to make sure it's disabled if it recognizes the controller. Maybe in this case the drive isn't recognized. Does anything mentioning 'quirk' show up in the syslog as the drive is attached?
 

NGI

Regular Contributor
This is a pure guess....
I see that drive is one of the super fast USBs (400MB/s) which means it probably implements UASP. It's been my experience that linux doesn't play well with UASP, and in most cases sets a usb.quirk to make sure it's disabled if it recognizes the controller. Maybe in this case the drive isn't recognized. Does anything mentioning 'quirk' show up in the syslog as the drive is attached?

I have the below message appearing 3 times in my Syslog:

May 5 06:05:11 kernel: xhci-hcd xhci-hcd.0: hcc params 0x0250f17c hci version 0x100 quirks 0x00010010

A bit of an odd time stamp I have May 5 then Dec 3, 4 and then again May 5. Is this to do with a Reboot?
 

NGI

Regular Contributor
See if this helps


Thanks, did you manage to get to the bottom of what actually caused the problem in your case? Was it Diversion or AiProtection since I use both of them as well as spdMerlin which was mentioned but I saw you don't use it.
 
Last edited:

john9527

Part of the Furniture
May 5 06:05:11 kernel: xhci-hcd xhci-hcd.0: hcc params 0x0250f17c hci version 0x100 quirks 0x00010010
That's basically saying it reports it's capacity wrong and the kernel needs to adjust it. Does the syslog mention a pid and vid value? If not, what is the output of running
lsusb
via ssh
A bit of an odd time stamp I have May 5 then Dec 3, 4 and then again May 5. Is this to do with a Reboot?
Yes, that's because the system clock hasn't been set yet.
 
  • Like
Reactions: NGI

NGI

Regular Contributor
That's basically saying it reports it's capacity wrong and the kernel needs to adjust it. Does the syslog mention a pid and vid value?

Thank you very much for the explanation. Below are all the PID references in the Sys log.

Code:
May  5 06:05:11 kernel: PID hash table entries: 2048 (order: 2, 16384 bytes)
May  5 06:05:11 kernel: ubi0: background thread "ubi_bgt0d" started, PID 60
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 320
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 384
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 870
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 930
May  5 06:05:11 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 947
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 987
May  5 06:05:11 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1047
May  5 06:05:11 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1062
May  5 06:05:18 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1518
May  5 06:05:21 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2311
May  5 06:05:24 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2420
May  5 06:05:27 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2499
May  5 06:05:30 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2823
May  5 06:05:12 kernel: PID hash table entries: 2048 (order: 2, 16384 bytes)
May  5 06:05:12 kernel: ubi0: background thread "ubi_bgt0d" started, PID 60
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 320
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 382
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 866
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 928
May  5 06:05:12 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 947
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 987
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1047
May  5 06:05:12 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1062
May  5 06:05:18 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1518
May  5 06:05:21 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2327
May  5 06:05:24 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2466
May  5 06:05:27 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2576
May  5 06:05:30 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2905
Dec  3 23:31:57 RT-AC86U-4AB0 kernel: ubi1: background thread "ubi_bgt1d" started, PID 10365
May  5 06:05:12 kernel: PID hash table entries: 2048 (order: 2, 16384 bytes)
May  5 06:05:12 kernel: ubi0: background thread "ubi_bgt0d" started, PID 60
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 320
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 382
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 866
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 928
May  5 06:05:12 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 947
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 985
May  5 06:05:12 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1047
May  5 06:05:12 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1062
May  5 06:05:19 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1506
May  5 06:05:22 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2305
May  5 06:05:26 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2421
May  5 06:05:28 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2522
May  5 06:05:31 kernel: ubi1: background thread "ubi_bgt1d" started, PID 2754

There are some pid references but they are all related to FlexQoS e.g.

Code:
Dec  4 09:20:06 RT-AC86U-4AB0 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=4548) called in unattended mode with 1 args: -start
Dec  4 09:20:06 RT-AC86U-4AB0 FlexQoS: [*] Killing Delayed Process (pid=4349)

Regarding VID references I have the below message appearing 37 times in the sys log.

May 5 06:05:11 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096

Happy to PM the whole Syslog if this would be helpful.

I have also run the lsusb via ssh and the result is below but please bare in mind that when I run that I did not experience the problem since I changed the R/W permissions for the USB under SAMBA settings in the router and that fixes the problem for few days.
Code:
Bus 003 Device 002: ID 13fe:6000
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0001

Many thanks in advance for your help.

UPDATE: The problem happened again and attached is the output of the top command.

Also the output of lsusb is the same as above.
 

Attachments

  • top.png
    top.png
    327.8 KB · Views: 44
Last edited:

Rassal

Regular Contributor
Are you using the Android Asus App to connect to the router?
 

NGI

Regular Contributor
Are you using the Android Asus App to connect to the router?
Yes, I have it installed on my phone but rarely login to the router from there.
 

john9527

Part of the Furniture
@NGI
Thanks for the syslogs....learned a couple of things from them.
- the quirks entry is actually being applied to the USB3 port, not your device
- more important, the code doesn't recognize the USB stick as USB3 capable....it's running it in USB2 mode on the USB3 port. That sometimes can be flakey.

Easiest thing to try would be another USB stick or move the current one to the USB2 port and see what happensc (it looks like that is your only USB device, so I think if you move it everything should still work)..
 
  • Like
Reactions: NGI

NGI

Regular Contributor
@NGI
Thanks for the syslogs....learned a couple of things from them.
- the quirks entry is actually being applied to the USB3 port, not your device
- more important, the code doesn't recognize the USB stick as USB3 capable....it's running it in USB2 mode on the USB3 port. That sometimes can be flakey.

Easiest thing to try would be another USB stick or move the current one to the USB2 port and see what happensc (it looks like that is your only USB device, so I think if you move it everything should still work)..

Thanks for that @john9527. Actually the Patriot USB stick is connected to the USB2 port. I have a 1TB connected to the USB3 port but it is currently switched off (it has a on/off switch) since we only use it for files sharing on demand at home.

To me it would be interesting to see if removing Diversion or Skynet contributed to fixing the issue?

For info after the problem occurred today I have disabled AiProtection and uninstalled Diversion, uiDivStats, Skynet and SpdMerlin and the CPUs were still at 100%. Subsequently I enabled AiProtection and installed SpdMerlin and after an hour or so now the CPUs are back to normal :rolleyes:. I hope they stay that way.
 

john9527

Part of the Furniture
Actually the Patriot USB stick is connected to the USB2 port.
I had to double check.....confirmed. I misread the order of some syslog output....it does show as connected to the USB2 port.
 

Rassal

Regular Contributor
Yes, I have it installed on my phone but rarely login to the router from there.

Ok... then check it out... on my AC87U, each and everytime i was USING the Asus Router APP, the CPU would go to 100% like 1-2 min after, to a point where my only work around was to reboot the router... took me a while to figure it out...

I stopped using the Asus Router App, and the problem stopped...

Might give it a try...
 
  • Like
Reactions: NGI

NGI

Regular Contributor
Ok... then check it out... on my AC87U, each and everytime i was USING the Asus Router APP, the CPU would go to 100% like 1-2 min after, to a point where my only work around was to reboot the router... took me a while to figure it out...

I stopped using the Asus Router App, and the problem stopped...

Might give it a try...

Thanks you for your suggestion. I tried using the Android App but that doesn't cause any substantial CPU % increase in my setup.
 

NGI

Regular Contributor
you can Disable all usb applications, such as upnp and samba.
UPnP is disabled but I use Samba for file sharing so disabling that is not an option. It use to work with samba enabled for 2 month without any issues.
 

wizin

Regular Contributor
Thanks, did you manage to get to the bottom of what actually caused the problem in your case? Was it Diversion or AiProtection since I use both of them as well as spdMerlin which was mentioned but I saw you don't use it.

Diversion
 

wizin

Regular Contributor
I had this issue again, pulled out the USB and it stopped - so I have come to the conclusion that after a while, have to format USB and reset diversion skynet etc
 

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