Unable to suspend with XHC enabled

tigerjack · 2022-04-14 09:04:41

I am not able to suspend my laptop anymore after latest updates. Indeed, every time I do a systemctl suspend, my laptop wakes up again after a few seconds.

Digging around, I tried to overcome the problem by disabling, one at at a time, the devices listed in /proc/acpi/wakeup. Disabling the device called XHC, indeed, fixed the problem. However, I don't know if it's safe. Also, in order to be able to suspend, I should disable it anytime I reboot my laptop. Does anyone have the same problem? Is there a better workaround or fix?

Last edited by tigerjack (2022-04-14 09:06:59)

seth · 2022-04-14 13:03:38

XHC is some usb hub - most likely some™ device respsonds badly to the powerdown and triggers an event.
There's a good chance that this shows up in dmesg/the system journal, if not "lsusb" might still reveal a suspect.

Ceterum ceseo: 3rd link below.

tigerjack · 2022-04-19 09:36:25

Hey @seth, thank you and sorry for the delay. I uploaded the journalctl logs here http://0x0.st/ocRf.txt. Honestly, I didn't find any line signaling an error, but of course I am not an expert.

seth · 2022-04-19 13:17:15

That event would not be logged because it occurs to the BIOS.

lsusb -tv

If there's no parallel windows (again: 3rd link below) you'd remove all removable USB devices and see whether the issue remains.
From the context, there's a chance that it's the BT controller (which you might be able to deactivate in the BIOS)

tigerjack · 2022-04-19 14:39:55

seth wrote:

That event would not be logged because it occurs to the BIOS.
lsusb -tv
If there's no parallel windows (again: 3rd link below) you'd remove all removable USB devices and see whether the issue remains.
From the context, there's a chance that it's the BT controller (which you might be able to deactivate in the BIOS)

Yeah disabling fast boot is the first thing I do when I install linux in parallel with windows.
For the usb part, the problem was there even when no USB device was connected. So yeah, it can be a problem related to bluetooth, but I use it a lot so I cannot simply disable it from BIOS.

Here the output from the previous command (there is a keyboard and a mouse attached now)

$>lsusb -tv
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 145f:02b0 Trust
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 145f:02b0 Trust
    |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 1bcf:08a0 Sunplus Innovation Technology Inc. Gaming mouse [Philips SPK9304]
    |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
        ID 13d3:56cb IMC Networks
    |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
        ID 13d3:56cb IMC Networks
    |__ Port 5: Dev 3, If 2, Class=Video, Driver=uvcvideo, 480M
        ID 13d3:56cb IMC Networks
    |__ Port 5: Dev 3, If 3, Class=Video, Driver=uvcvideo, 480M
        ID 13d3:56cb IMC Networks
    |__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0026 Intel Corp. AX201 Bluetooth
    |__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0026 Intel Corp. AX201 Bluetooth

seth · 2022-04-19 17:26:31

but I use it a lot so I cannot simply disable it from BIOS

The idea would be to disable it for testing purposes to pin down the offender (or rule out BT) and then look on from there.

tigerjack · 2022-04-20 19:24:11

seth wrote:

but I use it a lot so I cannot simply disable it from BIOS
The idea would be to disable it for testing purposes to pin down the offender (or rule out BT) and then look on from there.

I did it indeed, and it seems to work now, but I cannot tell if it is because of the latest upgrade or because turning electronic things off and on is the oldest and most reliable bug fix of the world

seth · 2022-04-21 13:16:18

Does re-enabling BT re-instate the original problem?
Is there a parallel windows installation at all?
https://wiki.archlinux.org/title/Blueto … ot_pairing - the device might be uneasy about this. If BT now works fine (doesn't trigger an S3 wake) but flares up in the future, try to remove the battery (or otherwise turn it on and off) w/o altering or rebooting the host (archlinux system) at all.

tigerjack · 2022-04-24 14:19:44

seth wrote:

Does re-enabling BT re-instate the original problem?
Is there a parallel windows installation at all?
https://wiki.archlinux.org/title/Blueto … ot_pairing - the device might be uneasy about this. If BT now works fine (doesn't trigger an S3 wake) but flares up in the future, try to remove the battery (or otherwise turn it on and off) w/o altering or rebooting the host (archlinux system) at all.

Indeed, the problem is still here, and I don't know if it's because of the new upgrade (iirc acpi was just upgraded again).
Yes, I have a dual boot btw, but I didn't change the configuration at all nor start windows in a couple of months now. And since I rarely uses Windows (and when I do, it's for a few weeks in a row in which I don't use Arch) I did not bother to setup dual boot pairing.
From what I can tell, btw, bluetooth works just fine with my headphones and mouse. However, I have a few lines in the journal logs that keeps repeating (those with the asterisks). I don't know if they can be incriminated.

#>sudo journalctl -u bluetooth -b -2
Apr 22 10:32:30 azenb systemd[1]: Starting Bluetooth service...
Apr 22 10:32:30 azenb bluetoothd[705]: Bluetooth daemon 5.64
Apr 22 10:32:30 azenb systemd[1]: Started Bluetooth service.
Apr 22 10:32:30 azenb bluetoothd[705]: Starting SDP server
Apr 22 10:32:30 azenb bluetoothd[705]: Bluetooth management interface 1.21 initialized
Apr 22 10:32:56 azenb bluetoothd[705]: Player registered: sender=:1.28 path=/media_player0
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/ldac
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSink/aptx
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aac
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSink/sbc
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/sbc
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/faststream
Apr 22 10:32:56 azenb bluetoothd[705]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource/faststream_duplex
*Apr 22 10:33:38 azenb bluetoothd[705]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 04:CB:88:C3:1C:76: Connection refused (111)
*Apr 22 10:33:38 azenb bluetoothd[705]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Connection timed out
*Apr 22 10:34:21 azenb bluetoothd[705]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 04:CB:88:C3:1C:76: Connection refused (111)
Apr 22 11:14:31 azenb bluetoothd[705]: Terminating
Apr 22 11:14:31 azenb systemd[1]: Stopping Bluetooth service...
*Apr 22 11:14:31 azenb bluetoothd[705]: Failed to set mode: Not Connected (0x02)
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/ldac
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink/aptx
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aac
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink/sbc
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/sbc
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/faststream
Apr 22 11:14:31 azenb bluetoothd[705]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 22 11:14:31 azenb bluetoothd[705]: Player unregistered: sender=:1.28 path=/media_player0
Apr 22 11:14:32 azenb bluetoothd[705]: Disconnected from D-Bus. Exiting.
Apr 22 11:14:32 azenb bluetoothd[705]: Stopping SDP server
Apr 22 11:14:32 azenb bluetoothd[705]: Exit
Apr 22 11:14:32 azenb systemd[1]: bluetooth.service: Deactivated successfully.
Apr 22 11:14:32 azenb systemd[1]: Stopped Bluetooth service.

seth · 2022-04-24 14:22:51

Yes, I have a dual boot btw

1st step: 3rd link below. Mandatory.
Sorry, we already had that. Maybe still check whether it's still deactivated as windows updates occasionally re-enable it.

Edit #2: What is the device w/ the MAC 04:CB:88:C3:1C:76 ?
Does it still exist/get found?
If so, what if you disable just its pairing and try to suspend?

Edit #3: vendor is https://uic.io/en/mac/address/04cb88/ (if that helps you identifying the device)

Last edited by seth (2022-04-24 14:30:39)

tigerjack · 2022-04-29 08:44:07

seth wrote:

Yes, I have a dual boot btw
1st step: 3rd link below. Mandatory.
Sorry, we already had that. Maybe still check whether it's still deactivated as windows updates occasionally re-enable it.

Still didn't have time to do that, but I didn't boot Windows in weeks/months. I also want to point out that another upgrade fixed the problem. I think it's somehow related to acpi packages upgrades.

seth wrote:

Edit #2: What is the device w/ the MAC 04:CB:88:C3:1C:76 ?
Does it still exist/get found?
If so, what if you disable just its pairing and try to suspend?
Edit #3: vendor is https://uic.io/en/mac/address/04cb88/ (if that helps you identifying the device)

It's a JBL Flip Essential speaker. I may try to remove it for now since I'm not using it too much. But I honestly don't know why it tries to connect to that every time.

Thanks for the effort you're putting

Arch Linux

#1 2022-04-14 09:04:41

Unable to suspend with XHC enabled

#2 2022-04-14 13:03:38

Re: Unable to suspend with XHC enabled

#3 2022-04-19 09:36:25

Re: Unable to suspend with XHC enabled

#4 2022-04-19 13:17:15

Re: Unable to suspend with XHC enabled

#5 2022-04-19 14:39:55

Re: Unable to suspend with XHC enabled

#6 2022-04-19 17:26:31

Re: Unable to suspend with XHC enabled

#7 2022-04-20 19:24:11

Re: Unable to suspend with XHC enabled

#8 2022-04-21 13:16:18

Re: Unable to suspend with XHC enabled

#9 2022-04-24 14:19:44

Re: Unable to suspend with XHC enabled

#10 2022-04-24 14:22:51

Re: Unable to suspend with XHC enabled

#11 2022-04-29 08:44:07

Re: Unable to suspend with XHC enabled

Board footer