[RESOLVED] Faulty USB device prevents sleep

Demon · 2018-12-13 21:27:23

My inbuilt card reader become faulty suddenly:

[  525.146928] dpm_run_callback(): usb_dev_freeze+0x0/0x10 returns -16
[  525.146930] PM: Device usb1 failed to freeze async: error -16
...
[  526.233634] usb 1-8: device descriptor read/64, error -71
[  526.463357] usb 1-8: new low-speed USB device number 92 using xhci_hcd
[  526.590346] usb 1-8: device descriptor read/64, error -71
[  526.820506] usb 1-8: device descriptor read/64, error -71
[  526.926996] usb usb1-port8: attempt power cycle
[  527.570298] usb 1-8: new low-speed USB device number 93 using xhci_hcd
[  527.572012] usb 1-8: Device not responding to setup address.
[  527.777660] usb 1-8: Device not responding to setup address.
[  527.983456] usb 1-8: device not accepting address 93, error -71
[  528.106703] usb 1-8: new low-speed USB device number 94 using xhci_hcd
[  528.108098] usb 1-8: Device not responding to setup address.
[  528.314693] usb 1-8: Device not responding to setup address.
[  528.520192] usb 1-8: device not accepting address 94, error -71
[  528.520273] usb usb1-port8: unable to enumerate USB device

so laptop now won't sleep/suspend/hibernate:

daimonion-lap systemd[1]: Reached target Sleep.
daimonion-lap systemd[1]: Starting Hybrid Suspend+Hibernate...
daimonion-lap kernel: PM: Image not found (code -22)
daimonion-lap systemd-sleep[1183]: Suspending system...
daimonion-lap kernel: PM: hibernation entry
daimonion-lap kernel: PM: Syncing filesystems ... 
daimonion-lap kernel: usb 1-8: Device not responding to setup address.
daimonion-lap kernel: PM: done.
daimonion-lap kernel: Freezing user space processes ... (elapsed 0.005 seconds) done.
daimonion-lap kernel: OOM killer disabled.
daimonion-lap kernel: PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
daimonion-lap kernel: PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
daimonion-lap kernel: PM: Marking nosave pages: [mem 0x7aa6e000-0xffffffff]
daimonion-lap kernel: PM: Basic memory bitmaps created
daimonion-lap kernel: PM: Preallocating image memory... 
daimonion-lap kernel: usb 1-8: device not accepting address 11, error -71
daimonion-lap kernel: done (allocated 468150 pages)
daimonion-lap kernel: PM: Allocated 1872600 kbytes in 0.28 seconds (6687.85 MB/s)
daimonion-lap kernel: Freezing remaining freezable tasks ... 
daimonion-lap kernel: usb 1-8: new low-speed USB device number 12 using xhci_hcd
daimonion-lap kernel: usb 1-8: Device not responding to setup address.
daimonion-lap kernel: usb 1-8: Device not responding to setup address.
daimonion-lap kernel: usb 1-8: device not accepting address 12, error -71
daimonion-lap kernel: usb usb1-port8: unable to enumerate USB device
daimonion-lap kernel: (elapsed 0.452 seconds) done.
daimonion-lap kernel: Suspending console(s) (use no_console_suspend to debug)
daimonion-lap kernel: wlp1s0: deauthenticating from 8c:04:ff:b9:04:6e by local choice (Reason: 3=DEAUTH_LEAVING)
daimonion-lap kernel: dpm_run_callback(): usb_dev_freeze+0x0/0x10 returns -16
daimonion-lap kernel: PM: Device usb1 failed to freeze async: error -16
daimonion-lap kernel: sd 0:0:0:0: [sda] Starting disk
daimonion-lap kernel: PM: Basic memory bitmaps freed
daimonion-lap kernel: OOM killer enabled.
daimonion-lap kernel: Restarting tasks ... done.
daimonion-lap wpa_supplicant[444]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=8c:04:ff:b9:04:6e reason=3 locally_generated=1
daimonion-lap NetworkManager[423]: <warn>  [1544724792.4025] sup-iface[0x55cf39fda8d0,wlp1s0]: connection disconnected (reason -3)
daimonion-lap NetworkManager[423]: <info>  [1544724792.4073] device (wlp1s0): supplicant interface state: completed -> disconnected
daimonion-lap NetworkManager[423]: <info>  [1544724792.5055] device (wlp1s0): supplicant interface state: disconnected -> scanning
daimonion-lap kernel: usb 1-8: new low-speed USB device number 13 using xhci_hcd
daimonion-lap systemd-sleep[1183]: Failed to suspend system. System resumed again: Device or resource busy
daimonion-lap kernel: PM: hibernation exit
daimonion-lap systemd[1]: systemd-hybrid-sleep.service: Main process exited, code=exited, status=1/FAILURE
daimonion-lap systemd[1]: systemd-hybrid-sleep.service: Failed with result 'exit-code'.
daimonion-lap systemd[1]: Failed to start Hybrid Suspend+Hibernate.
daimonion-lap systemd[1]: Dependency failed for Hybrid Suspend+Hibernate.
daimonion-lap systemd[1]: hybrid-sleep.target: Job hybrid-sleep.target/start failed with result 'dependency'.
daimonion-lap audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
daimonion-lap kernel: audit: type=1130 audit(1544724792.568:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hybrid-sleep comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
daimonion-lap systemd[1]: Stopped target Sleep.
daimonion-lap systemd-logind[407]: Operation 'sleep' finished.

The card reader is actually on a small board next to two USBs and a headphone jack, all work without problems. But I do not actually need the card reader, I only care about been able to suspend my laptop. Is there any workaround for this issue?

Last edited by Demon (2018-12-15 19:29:13)

loqs · 2018-12-13 22:00:16

Can you prevent the device being used with https://www.kernel.org/doc/Documentatio … zation.txt ?

tpfkanep · 2018-12-14 06:56:30

Also cannot suspend my PC with systemctl suspend after poweroff of USB HDD with udisksctl power-off -b /dev/sdx

journalctl

Dec 14 08:47:19 arch64 systemd-sleep[3437]: Failed to suspend system. System resumed again: Device or resource busy
Dec 14 08:47:19 arch64 systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 08:47:19 arch64 systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Dec 14 08:47:19 arch64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dec 14 08:47:19 arch64 systemd[1]: Failed to start Suspend.
Dec 14 08:47:19 arch64 systemd[1]: Dependency failed for Suspend.
Dec 14 08:47:19 arch64 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.

Edit:
Only way to get suspend working is by physically unplugging device and running systemctl suspend.

Last edited by tpfkanep (2018-12-14 06:57:28)

seth · 2018-12-14 08:23:39

echo "1-8" > /sys/bus/usb/drivers/usb/unbind
echo "1-8" > /sys/bus/usb/drivers/usb/bind

In some sleep hooks? https://wiki.archlinux.org/index.php/Po … leep_hooks
(Adjust the bus id, in doubt search it by vendor/product id)

Demon · 2018-12-15 16:07:19

@loqs Thanks, but I do not know what to do with this.

@seth Thanks, I get this:

# echo "1-8" >! /sys/bus/usb/drivers/usb/unbind
echo: write error: no such device

seth · 2018-12-15 16:44:09

How many exclamation points do you see in my post?
To be sure:

stat /sys/bus/usb/drivers/usb/unbind

Demon · 2018-12-15 17:08:42

seth wrote:

How many exclamation points do you see in my post?

I am using zsh, it requires the exclamation.

To be sure:

stat /sys/bus/usb/drivers/usb/unbind

% stat /sys/bus/usb/drivers/usb/unbind
  File: /sys/bus/usb/drivers/usb/unbind
  Size: 4096            Blocks: 0          IO Block: 4096   regular file
Device: 14h/20d Inode: 7661        Links: 1
Access: (0200/--w-------)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-12-15 17:05:21.783708290 +0100
Modify: 2018-12-15 17:05:21.780060164 +0100
Change: 2018-12-15 17:05:21.780060164 +0100
 Birth: -

seth · 2018-12-15 17:20:05

No it doesn't.
But the message is actually from the unbind, try so to be sure: you try to unbind the device *before* it gets faulty and still shows up in "lsusb -t" (with this bus/port)?

Demon · 2018-12-15 18:43:59

seth wrote:

No it doesn't.
But the message is actually from the unbind, try so to be sure: you try to unbind the device *before* it gets faulty and still shows up in "lsusb -t" (with this bus/port)?

I honestly don't understand what you want me to do here.

I can sleep the same laptop on other distros (they display the same "usb 1-8: Device not responding to setup address." error), but not on Arch. So there's gotta be a way to enable sleep/hibernate on Arch has well.

Demon · 2018-12-15 19:28:40

I have created a following file:

% cat /usr/lib/systemd/system-sleep/10-xhcihcd.sh 
#!/bin/bash

case $1/$2 in
  pre/*)
    # echo "Going to $2..."
    echo "0000:00:14.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
    ;;
  post/*)
    # echo "Waking up from $2..."
    echo "0000:00:14.0" > /sys/bus/pci/drivers/xhci_hcd/bind
    ;;
esac

Suspend/hibernate now works.

Arch Linux

#1 2018-12-13 21:27:23

[RESOLVED] Faulty USB device prevents sleep

#2 2018-12-13 22:00:16

Re: [RESOLVED] Faulty USB device prevents sleep

#3 2018-12-14 06:56:30

Re: [RESOLVED] Faulty USB device prevents sleep

#4 2018-12-14 08:23:39

Re: [RESOLVED] Faulty USB device prevents sleep

#5 2018-12-15 16:07:19

Re: [RESOLVED] Faulty USB device prevents sleep

#6 2018-12-15 16:44:09

Re: [RESOLVED] Faulty USB device prevents sleep

#7 2018-12-15 17:08:42

Re: [RESOLVED] Faulty USB device prevents sleep

#8 2018-12-15 17:20:05

Re: [RESOLVED] Faulty USB device prevents sleep

#9 2018-12-15 18:43:59

Re: [RESOLVED] Faulty USB device prevents sleep

#10 2018-12-15 19:28:40

Re: [RESOLVED] Faulty USB device prevents sleep

Board footer