Hi All,

 

I have a small issue and I'm struggling to figure it out. I think it may be the USB drive giving up but I'm not certain.

 

The GUI started lagging when in use (accessing via chrome), the main tab takes a while to load up before showing info, same with the dashboard, tools, plugins etc.

Dockers and VM's are running fine but the pages take a while to load.

 

Looking in the live log I get a lot of

 

May  1 20:22:22 Alice kernel: usb usb2-port2: unable to enumerate USB device
May  1 20:22:28 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  1 20:22:34 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  1 20:22:34 Alice kernel: usb 2-2: device not accepting address 33, error -62
May  1 20:22:39 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  1 20:22:45 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  1 20:22:45 Alice kernel: usb 2-2: device not accepting address 34, error -62
May  1 20:22:45 Alice kernel: usb usb2-port2: attempt power cycle
May  1 20:22:51 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  1 20:22:57 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

 

The only USB device I have plugged in is the USB boot drive

 

I have attached a diagnostic pull if any one is able to offer any advice it would be appreciated.

 

Thanks in advance. 

 

alice-diagnostics-20250501-2010.zip

I would expect more direct flash drive errors, if that really was the flash drive, post the output from

 

lsusb -vt

 

Results from lsub:

 

root@Alice:~# lsusb -vt
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1462:7e01 Micro Star International 
    |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0610 Genesys Logic, Inc. Hub
    |__ Port 005: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    |__ Port 011: Dev 007, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0608 Genesys Logic, Inc. Hub
    |__ Port 014: Dev 008, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0033 Intel Corp. 
    |__ Port 014: Dev 008, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0033 Intel Corp. 
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
root@Alice:~# 

55 minutes ago, CoolDude01 said:

Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Looks like this is the problem, appears to be a keyboard or mouse.

Ok, so this whole line is the issue:

 

    |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1462:7e01 Micro Star International 

 

Or as shown in Unarid GUI:

 

"Bus 001 Device 002 Port 1-2        ID 1462:7e01 Micro Star International MYSTIC LIGHT"

 

Strange as nothing new has been plugged in but if its "1462:7e01 Micro Star International " then it points to something called mystic lights on the mother board. 

I wonder if it's decided to just give up!

Probably the RGB control.

Amazing, thank you @JorgeB  appreciate your help, I just couldnt see it.

I will try and disable the feature in the bios if that's possible, it's not used.

I'm having exactly the same problem. GUI suddenly started taking a long time to load information, but everything else runs fine. Logs show the same thing:

 

May  2 09:49:55 MultiServ kernel: usb 2-2: device not accepting address 2, error -62
May  2 09:50:01 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:06 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:07 MultiServ kernel: usb 2-2: device not accepting address 2, error -62
May  2 09:50:07 MultiServ kernel: usb 2-2: USB disconnect, device number 2
May  2 09:50:12 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:18 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:18 MultiServ kernel: usb 2-2: device not accepting address 3, error -62
May  2 09:50:23 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:29 MultiServ kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 09:50:29 MultiServ kernel: usb 2-2: device not accepting address 4, error -62
May  2 09:50:29 MultiServ kernel: usb usb2-port2: attempt power cycle

 

lsusb shows the same (and takes a while to populate):

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1462:7d42 Micro Star International MYSTIC LIGHT 
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
Bus 001 Device 005: ID 154b:0076 PNY USB 2.0 FD
Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 008: ID 8087:0033 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

 

I tried going into the BIOS and disabling USB2 Port 2 but that just prevented Unraid from booting and would kick me back into the BIOS. There's also an RGB Light Setting in the BIOS EZ Mode that I toggled off, but that didn't help either. Apparently some MSI motherboards also have a physical switch for LED control, but mine doesn't. I'll keep poking around. @CoolDude01, if you find anything or manage to resolve it please let me know!

Planning on taking a look when I get back from work tonight so will update.

 

I'm running a "MAG B760M MORTAR WIFI (MS-7E01) , Version 4.0" motherboard in case you have something similar.

 

Looking at my logs, it all starts to go wrong when I log in, while i'm not everything seems to run smoothly:

 

May  2 11:33:37 Alice emhttpd: spinning down /dev/sdf
May  2 16:01:31 Alice webgui: Successful login user root
May  2 16:01:38 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 16:01:44 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 16:01:44 Alice kernel: usb 2-2: device not accepting address 31, error -62
May  2 16:01:49 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 16:01:55 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 16:01:55 Alice kernel: usb 2-2: device not accepting address 32, error -62

 

 

It's almost like something is being triggered, but why? It's strange and only started happening the other day with 0 changes in that time.

 

I have tried to goolge around and see if it's possible to disable the device in unraid it's self but I haven't found anything yet.

I've been looking around too but nothing I've found works. Well, kinda. 

 

I found this: https://askubuntu.com/questions/741760/is-it-possible-to-turn-off-a-specific-usb-port-so-it-doesnt-accept-any-device and this: https://stackoverflow.com/questions/1163824/linux-usb-turning-the-power-on-and-off/7943636#7943636 so far.

 

What's interesting is that I found that running just "echo on | sudo tee /sys/bus/usb/devices/usb2/power/level" (without the prior commands listed in the first link) seems to stop the error from happening, even despite the fact that I get a message saying power/level is depreciated. And so far the GUI seems to be snappier and load quickly like I'm used to. This, however, does not persist through reboots, so it's just a temp fix (if it's a fix at all).

 

I think you might be onto something, but I wonder if it's the opposite - something isn't getting triggered, but running that command does something to trigger it and stop the error.

 

Edit: Or perhaps something is getting triggered like you said, and running the command "un"triggers it. Who knows.

Edited May 2, 20251 yr by zerohunter

Ok, So I can not disable Mystic lights in the bios or via a physical switch.

 

I bodged in Power top now nerdtools is no longer supported and I can see its doing something, what this means though I'm not sure at the moment.

The bodge:

"wget https://slackware.uk/slackware/slackware64-current/slackware64/ap/powertop-2.15-x86_64-2.txz"

"installpkg powertop-2.15-x86_64-2.txz"

 

The Info:

Device Status

Doing nothing
0.0%        USB device: MYSTIC LIGHT  (MSI)

Jumping between GUI pages:
24.6%        USB device: MYSTIC LIGHT  (MSI)

Then down to:
0.6%        USB device: MYSTIC LIGHT  (MSI)

 

I have also tried Settings - Power Mode and changing between the two (Best power and Best performance) but nothing changed.

 

Running the command you posted has also made my GUI snappier for me and stopped the error spamming the live log:

 

May  2 20:25:45 Alice kernel: WARNING! power/level is deprecated; use power/control instead
May  2 20:25:47 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 20:25:47 Alice kernel: usb 2-2: device not accepting address 49, error -62
May  2 20:25:53 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 20:25:58 Alice kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  2 20:25:58 Alice kernel: usb 2-2: device not accepting address 50, error -62
May  2 20:25:58 Alice kernel: usb usb2-port2: unable to enumerate USB device
May  2 20:25:58 Alice sudo: pam_unix(sudo:session): session closed for user root

 

 

Powertop still shows it doing something though:

 

Device Status
Jumping between GUI pages:
32.6%        USB device: MYSTIC LIGHT  (MSI)

 

I may be barking up the wrong tree with the above. I'm not sure what the next move is either but would it be possible to pass it through to a windows VM and see if the software can be installed and used?

 

 

It may be worth a try

I tried out a couple of things, no luck yet though.

 

The first was trying to see if there was a driver or something that could help. I installed the OpenRGB docker container and associated patch plugin from community apps, but it didn't seem to make a difference. I did try re-enabling that EZ RGB Lighting setting in the BIOS to see if that affected it, still nothing. Interestingly, the OpenRGB docker couldn't detect any RGB devices or services when I scanned for them. I did see that many versions of Mystic Light were supported, but perhaps the version I have isn't or it needs something plugged in before it populates. I'm not sure.

 

Next I tried the User Scripts plugin, added a script for that one line above and set it to run when the array starts. However I'm having the same issue where those errors only start after logon, so the script doesn't really help. I know you can set a custom schedule, but I'm not savvy enough to find out if you can set it for user logon.

 

I did find this: https://unix.stackexchange.com/questions/56083/how-to-write-a-shell-script-that-gets-executed-on-login, and I tried to add a script to /etc/profile.d and I edited /etc/profile, however those changes get reverted after a reboot, I imagine since those changes would need to be applied on the USB boot drive. I did see that you could add scripts to the root/config/go folder on the flash drive, but I didn't see the go folder on mine. The posts were from a few years ago so maybe it got removed. I haven't tested adding it (and personally I'm a little wary of making changes on the boot drive).

 

So yeah, no luck yet. I think for now I'm just going to keep that script in the User Scripts plugin and just run it whenever I log in on a fresh boot. A little bit of a pain but at least it's a relatively quick fix.

I am also having this problem. I am on the same motherboard mentioned here as well. I do not believe I've done any recent hardware changes. I've tried removing my USB 3 header cable entirely. I do not have any lights that are not stock on the motherboard. I have tried disabling a variety of plugins, and running with docker and VMs disabled. The error persists.

 

The command that zerohunter mentions ( echo on | sudo tee /sys/bus/usb/devices/usb2/power/level ) does work for me as well after taking a moment to run. I still do not know of a permanent fix.

 

My BIOS IS dated 26 Oct 2023 and is out of date. This will be my next troubleshooting step - a BIOS update. But I am weary of doing this. And not very confident it will resolve the issue.

 

 

 

 

Board: MAG B760M MORTAR WIFI (MS-7E01) , Version 4.0

 

Errors:

May  3 03:07:08 Alfred kernel: usb usb2-port2: attempt power cycle
May  3 03:07:14 Alfred kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  3 03:07:19 Alfred kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  3 03:07:20 Alfred kernel: usb 2-2: device not accepting address 119, error -62
May  3 03:07:25 Alfred kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  3 03:07:31 Alfred kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  3 03:07:31 Alfred kernel: usb 2-2: device not accepting address 120, error -62
May  3 03:07:31 Alfred kernel: usb usb2-port2: unable to enumerate USB device

 

 

 

So, I did updated to the lates BIOS version - 7E01vME and it has made no change. I was originally running 7E01vMA.

 

Nothing has got worse and the command zerohunter mentions still works thankfully. 

Here having a same issue, came from this ticket:

 

I just wanted to share info about my motherboard is also "MSI MAG B760M MORTAR MAX WIFI (MS-7E01) Version 3.0".

There's "MAX" on mine but the model numbers are same.

Unraid logs and the results of "lsusb -vt" are same as well.

 

May  7 20:21:08 Unraid kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  7 20:21:14 Unraid kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  7 20:21:14 Unraid kernel: usb 2-2: device not accepting address 49, error -62
May  7 20:21:20 Unraid kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  7 20:21:25 Unraid kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
May  7 20:21:25 Unraid kernel: usb 2-2: device not accepting address 50, error -62

 

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1462:7e01 Micro Star International

 

Bus 001 Device 002 Port 1-2		ID 1462:7e01 Micro Star International MYSTIC LIGHT

 

So it looks like MSI Mystic Light + Unraid Connect makes a problem indeed.

I'm currently avoiding this issue by uninstalling Unraid Connect.

 

Looks like this has now been raised as an issue and updates will follow over on this thread: 

 

 

I have something similar but it stops when checking SDA1 .. says it wont accept command  etc..  just locks there and asks for reboot