Failed to suspend

I was able to suspend before the most recent stable update. I'm guessing it may have been a kernel regression. It happens with both 5.1 & 4.19. I came across these posts, but I got a bit lost. I'm not sure if it's PCIe or USB related or both.

Good grief I feel like a n00b. I usually can solve my own problems, but this one eludes me.

Journal from when the laptop lid was closed in my backpack:

Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00000040/00006000
Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7:    [ 6] BadTLP                
Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00001040/00006000
Jun 17 11:11:15 inspirognome kernel: pcieport 0000:00:01.7:    [ 6] BadTLP                
Jun 17 11:11:1
 inspirognome kernel: pcieport 0000:00:01.7:    [12] Timeout               
Jun 17 11:24:26 inspirognome kernel: PM: suspend_common(): xhci_pci_suspend+0x0/0xd0 [xhci_pci] returns -110
Jun 17 11:24:26 inspirognome kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
Jun 17 11:24:26 inspirognome kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x120 returns -110
Jun 17 11:24:26 inspirognome kernel: PM: Device 0000:04:00.4 failed to suspend async: error -110
Jun 17 11:24:26 inspirognome kernel: PM: Some devices failed to suspend, or early wake event detected
Jun 17 11:24:26 inspirognome kernel: hub 3-0:1.0: hub_ext_port_status failed (err = -108)
Jun 17 11:24:26 inspirognome kernel: usb usb3-port2: cannot disable (err = -108)
Jun 17 11:24:46 inspirognome kernel: Freezing of tasks failed after 20.001 seconds (0 tasks refusing to freeze, wq_busy=1):
Jun 17 11:24:46 inspirognome systemd-sleep[22313]: Failed to suspend system. System resumed again: Connection timed out
Jun 17 11:24:47 inspirognome systemd[1]: Failed to start Suspend.

inxi -Fxzc0

System:    Host: inspirognome Kernel: 5.1.8-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.2 
           Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Inspiron 5575 v: 1.3.2 serial: <filter> 
           Mobo: Dell model: 0M0Y6P v: X01 serial: <filter> UEFI: Dell v: 1.3.2 date: 05/10/2019 
Battery:   ID-1: BAT1 charge: 36.0 Wh condition: 39.1/42.0 Wh (93%) model: SDI 0x4D,0x38,0x34,0x49,0x00,0x00,0x0057 
           status: Discharging 
CPU:       Topology: Quad Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen 
           L2 cache: 2048 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31952 
           Speed: 1413 MHz min/max: 1600/2000 MHz Core speeds (MHz): 1: 1503 2: 1506 3: 1500 4: 1366 5: 1367 6: 1368 7: 1369 
           8: 1368 
Graphics:  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Dell driver: amdgpu v: kernel 
           bus ID: 04:00.0 
           Display: x11 server: X.Org 1.20.5 driver: amdgpu resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.30.0 5.1.8-1-MANJARO LLVM 8.0.0) v: 4.5 Mesa 19.0.6 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus ID: 04:00.1 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 04:00.6 
           Sound Server: ALSA v: k5.1.8-1-MANJARO 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 2000 
           bus ID: 02:00.0 
           IF: eth0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel 
           port: 2000 bus ID: 03:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 3-2.4:5 
           IF-ID-1: Mullvad state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 1.14 TiB used: 643.79 GiB (55.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB 
           ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-75Z10T2 size: 931.51 GiB temp: 31 C 
Partition: ID-1: / size: 227.94 GiB used: 82.15 GiB (36.0%) fs: ext4 dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 57.5 C mobo: N/A gpu: amdgpu temp: 57 C 
           Fan Speeds (RPM): fan-1: 2500 
Info:      Processes: 321 Uptime: 8m Memory: 7.50 GiB used: 2.84 GiB (37.9%) Init: systemd Compilers: gcc: 8.3.0 clang: 8.0.0 
           Shell: bash v: 5.0.7 inxi: 3.0.34

lspci

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0]
00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0]
00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4)
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61)

lsusb

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications 
Bus 003 Device 004: ID 2386:3119  
Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It's possible it's a kernel regression involving your network adapter. You've the misfortune of having two network adapters that can cause a lot of problems.

I have two suggestions:

  1. temporarily disable tlp (then restart):
sudo sytemctl mask tlp
  1. run the commands below before you put your computer into suspend.

Please do not cut and paste all the commands together at once.

Enter and run each command separately with a few seconds between each command.

nmcli networking off

sudo systemctl stop NetworkManager

sudo ip link set eth0 down

sudo ip link set wlan0 down

sudo lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs sudo rmmod

sudo modprobe -r r8169

sudo modprobe -r r8168

Try to suspend after you have unloaded your network components.

Afterwards reboot to restore your networking (you may also need to issue):

nmcli networking on

To enable tlp (then restart):

sudo sytemctl unmask tlp
sudo sytemctl enable tlp

Try those suggestions to see if your issue improves.

I don't see how it's possible, but I can't boot now after following those instructions.

Jun 17 18:20:49 inspirognome kernel: usb 3-2.4: device not accepting address 8, error -71

Jun 17 18:20:49 inspirognome kernel: usb 3-2.4: device not accepting address 9, error -71

Jun 17 18:20:49 inspirognome kernel: usb 3-2-port4: unable to enumerate USB device

Are you booting from a USB hard drive?

No, I have no USB devices connected. The only peripheral is my Logitech MX Anywhere 2S mouse connected via Bluetooth.

Well this is very strange. Your errors are referring to USB. I would not expect any of those commands to affect booting in any way. Did you attempt to boot to an older kernel or the fallback kernel?

There have been a lot of bluetooth issues on recent kernels. If your mouse is not detecting properly that may be preventing booting. Swap in an old school mouse with no bluetooth.

I plugged in the Logitech Unifying Receiver and it booted. I can now suspend successfully with tlp enabled. I thought I tried that earlier and it didn't work.

Logitech unifying receivers are not bluetooth. Please clarify, so we can understand what exactly was causing the problem and how you corrected it.

Yes, I'm aware the Unifying Receiver is not Bluetooth. I don't know how I can be more clear. I was connecting via Bluetooth, now I'm connecting via USB.

EDIT: I tried suspending again and got the same error in my journal posted in the OP.

Yes you were being clear, but a lot of users are under the misimpression that the Logitech Unifying Receiver is Bluetooth. That was why I asked for clarification.

So this appears to be another one of many bluetooth related problems. Bluetooth is really problematic of late. Best to steer clear of BT devices till some of these bugs get resolved.

Glad you got things working.

I didn't actually get things working. I got the same errors again trying to suspend. When it fails, most of the time the laptop is completely locked up and doesn't respond to anything. Sometimes the Caps Lock key light will blink as well. I have to hold the power button to turn it off.

Did you try disabling the networking prior to suspend without result?

It turned out networking was still disabled when suspending worked. So this is where I would use your system service you posted somewhere that disables networking before suspending? I'll fiddle with it more tomorrow, thanks for your help.

Here's the latest log while it locked up: https://pastebin.com/7HWDAJLA

1 Like

Here's a couple of different services I wrote you could try:

2 Likes

The network suspend / resume service did not help, but the USB restart service did the trick!

Now to figure out what to do about the internet dropping out randomly on certain Wireless AC networks. Specifically Channel 153 (5.765GHz) at my favorite coffee shop. But that's another issue for another topic.

Some adapters just don't like the higher channels. Not a big deal on your own network where you can change it, but obviously a pain when your roaming.

Glad the service did the job for you.

2 Likes

I just set my regulatory domain to US again, this time more permanently as per the wiki. I haven't had a drop since I set it, so I think that may be helping.

1 Like