Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

USB error message: Failed to suspend device

Featured Replies

I'm on 7.0.1. Was looking at shares on the GUI when it slowed to essentially a halt. In the log I saw lots of messages like this:

 

May  5 00:42:44 T2 kernel: usb 3-1: Failed to suspend device, error -110
May  5 00:42:49 T2 kernel: hub 3-1:1.0: hub_ext_port_status failed (err = -110)
May  5 00:42:51 T2 kernel: usb 3-1-port1: cannot disable (err = -110)
May  5 00:42:51 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:51:00 T2 root: Fix Common Problems Version 2025.03.12
May  5 00:54:51 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:54:52 T2 root: Fix Common Problems Version 2025.03.12
May  5 00:55:12 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:55:25 T2 kernel: x86/split lock detection: #AC: CPU 0/KVM/21420 took a split_lock trap at address: 0xfffff805bf6c218c
May  5 00:55:32 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 00:56:53 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:57:26 T2 root: Fix Common Problems Version 2025.03.12
May  5 00:57:28 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 00:57:37 T2 kernel: block nvme0n1: the capability attribute has been deprecated.
May  5 00:57:48 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:58:23 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 00:58:43 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 00:59:18 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 00:59:38 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 01:00:12 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 01:00:33 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 01:01:08 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 01:01:28 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 01:02:02 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 01:02:23 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 01:02:57 T2 kernel: usb 4-1: Failed to suspend device, error -110
May  5 01:03:17 T2 kernel: usb 3-1-port1: device 3-1.1 not suspended yet
May  5 01:03:52 T2 kernel: usb 4-1: Failed to suspend device, error -110

 

It took a few tries to get to the Diagnostics page and then it hung on downloading diagnostics

 

So I restarted the server, which now seems OK, but I'm getting the same messages (see timestamps above). I do have a USB add-on card in the server, but there's nothing attached to it. Diagnostics after reboot are attached.

 

Is this something to be worried about?

t2-diagnostics-20250505-0057.zip

Solved by JorgeB

  • Community Expert

Post the output from:

 

lsusb -vt

 

  • Author

Here's the output:

 

root@T2:~# 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 004: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M
        ID 0665:5161 Cypress Semiconductor USB to Serial
    |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
        |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 480M
            ID 0781:5591 SanDisk Corp. Ultra Flair
    |__ Port 013: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 26ce:01a2  
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:3431 VIA Labs, Inc. Hub
        |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 045b:0209 Hitachi, Ltd 
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 045b:0210 Hitachi, Ltd 

 

  • Community Expert
14 minutes ago, sonofdbn said:
 ID 045b:0209 Hitachi, Ltd 

 

14 minutes ago, sonofdbn said:
ID 045b:0210 Hitachi, Ltd 

Do you know what these two devices are?

  • Author

Hmm... the only Hitachi devices I have are these HGST (Hitachi Global Storage Technologies) drives. But they're connected to SATA ports on the motherboard.

 

HGST.png.882d76d7b78c4ddabb8c3a261554db71.png

 

(If the USB add-on card is an issue, I can remove it. It's not being used for anything.)

 

  • Community Expert
  • Solution
15 minutes ago, sonofdbn said:

I can remove it. It's not being used for anything.

Worth a try, and see if those devices no longer show.

  • Author

And now they're gone!

 

root@T2:~# 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 004: Dev 002, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M
        ID 0665:5161 Cypress Semiconductor USB to Serial
    |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
        |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 480M
            ID 0781:5591 SanDisk Corp. Ultra Flair
    |__ Port 013: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 26ce:01a2  
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub

 

And so far none of those error messages in the logs.

 

So I'm considering this solved. But in case it's needed for any future issue, I've attached the current diagnostics.

t2-diagnostics-20250505-2318.zip

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.