zerohunter

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'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.

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!