You are not logged in.

Pages: 1

#1 2021-08-22 10:41:05

08d09
Member
Registered: 2020-05-10
Posts: 12

System unresponsive after resuming from sleep

Hello, my system sometimes becomes unresponsive after resuming from sleep. The displays turn on and the system reacts to the power button so it's not completely unresponsive but USB, ethernet or AHCI do not work in this state so I have to shutdown the system via the power button. The kernel logs contain these errors after this occurs:

Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/1/21/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/1/21/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/2/28/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/2/28/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/3/35/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/3/35/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/4/42/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/4/42/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/5/49/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/5/49/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/6/56/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/6/56/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/7/63/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/7/63/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/8/70/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/8/70/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/9/77/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/9/77/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/10/84/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/10/84/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/11/91/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/11/91/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/12/98/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/12/98/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/13/105/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/13/105/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/14/112/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/14/112/0x00000000
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/15/119/0x00000002
Aug 22 11:53:42 ryzen kernel: BUG: scheduling while atomic: cpuhp/15/119/0x00000000
Aug 22 11:53:42 ryzen kernel: pcieport 0000:00:01.2: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:02:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:03:04.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:03:01.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:03:08.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:03:09.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pcieport 0000:03:0a.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: igb 0000:05:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: pci 0000:06:00.0: can't change power state from unknown to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.1: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: nvme 0000:04:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.3: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: igb 0000:05:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.3: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.1: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.3: PCI post-resume error -19!
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.3: HC died; cleaning up
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.1: PCI post-resume error -19!
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.1: HC died; cleaning up
Aug 22 11:53:42 ryzen kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x1c0 returns -19
Aug 22 11:53:42 ryzen kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x1c0 returns -19
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.3: PM: failed to resume async: error -19
Aug 22 11:53:42 ryzen kernel: xhci_hcd 0000:06:00.1: PM: failed to resume async: error -19
Aug 22 11:53:42 ryzen kernel: nvme 0000:04:00.0: can't change power state from D3hot to D0 (config space inaccessible)
Aug 22 11:53:42 ryzen kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x1c0 returns -19
Aug 22 11:53:42 ryzen kernel: igb 0000:05:00.0: PM: failed to resume async: error -19
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: controller reset failed (0xffffffff)
Aug 22 11:53:42 ryzen kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x1c0 returns -5
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: PM: failed to resume async: error -5
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: controller reset failed (0xffffffff)
Aug 22 11:53:42 ryzen kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x1c0 returns -5
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: PM: failed to resume async: error -5
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:42 ryzen kernel: Buffer I/O error on dev nvme1n1p1, logical block 34305, lost sync page write
Aug 22 11:53:42 ryzen kernel: JBD2: Error -5 detected when updating journal superblock for nvme1n1p1-8.
Aug 22 11:53:42 ryzen kernel: Aborting journal on device nvme1n1p1-8.
Aug 22 11:53:42 ryzen kernel: Buffer I/O error on dev nvme1n1p1, logical block 34305, lost sync page write
Aug 22 11:53:42 ryzen kernel: JBD2: Error -5 detected when updating journal superblock for nvme1n1p1-8.
Aug 22 11:53:42 ryzen systemd[1]: Failed unmounting /med/ssd.
Aug 22 11:53:47 ryzen kernel: xhci_hcd 0000:06:00.1: xHCI host controller not responding, assume dead
Aug 22 11:53:47 ryzen kernel: xhci_hcd 0000:06:00.3: xHCI host controller not responding, assume dead
Aug 22 11:53:47 ryzen kernel: xhci_hcd 0000:06:00.3: HC died; cleaning up
Aug 22 11:53:47 ryzen kernel: xhci_hcd 0000:06:00.1: HC died; cleaning up
Aug 22 11:53:48 ryzen kernel: ahci 0000:08:00.0: AHCI controller unavailable!
Aug 22 11:53:48 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!
Aug 22 11:53:48 ryzen kernel: ahci 0000:07:00.0: AHCI controller unavailable!

My system is running 5.13.12-zen1-1-zen, has an X570 Aorus Elite, 3700X and the CPU is mildly undervolted. I doubt the undervolt is the cause as I've had no stability issues with this config for months even when keeping the CPU at 100% for hours. Does anyone know what might be causing this?

Last edited by 08d09 (2021-08-22 11:11:54)

Offline

#2 2021-08-22 16:51:48

seth
Member
Registered: 2012-09-03
Posts: 51,056

Re: System unresponsive after resuming from sleep

pcie_aspm=off

?
https://wiki.archlinux.org/title/Kernel_parameters

I've had no stability issues with this config for months

What changed before it started to happen?
Kernel update? Are other kernels (lts) affected?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2021-08-22 22:14:31

08d09
Member
Registered: 2020-05-10
Posts: 12

Re: System unresponsive after resuming from sleep

seth wrote:
pcie_aspm=off

?

I haven't turned off ASPM, I'll add that to my kernel parameters. These are my current parameters, I don't think they are related but who knows

loglevel=3  amd_iommu=on  mem_encrypt=off iommu=pt audit=0  clearcpuid=514 amdgpu.ppfeaturemask=0xffffffff apparmor=1 lsm=lockdown,yama,apparmor acpi_enforce_resources=lax usbcore.autosuspend=-1 init_on_alloc=1 init_on_free=1 page_alloc.shuffle=1 vsyscall=none"
seth wrote:

What changed before it started to happen??

I should have been more specific, sorry. Honestly I have no idea what might have caused this, I undervolted the CPU a little after getting it and ran it like that some time prior to experiencing this. I don't recall this starting to happen right after a kernel update either, I update the BIOS quite regularly so my initial suspicion was a BIOS update but they probably would have fixed such an issue in a year(This has been occurring intermittently for around a year). I've encountered this issue with both the regular and zen kernels.

Offline

#4 2021-08-23 06:41:00

seth
Member
Registered: 2012-09-03
Posts: 51,056

Re: System unresponsive after resuming from sleep

acpi_enforce_resources=lax # given the errors, this is hyper-fishy
page_alloc.shuffle=1 # could be related if this shuffles into the wrong area…
amd_iommu=on # invalid value anyway?, https://raw.githubusercontent.com/torva … meters.txt
iommu=pt # do you need the pass-through? I'd rather try whether "iommu=soft" stabilizes stuff to see whether it's iommu related

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2021-08-23 11:58:12

08d09
Member
Registered: 2020-05-10
Posts: 12

Re: System unresponsive after resuming from sleep

seth wrote:

acpi_enforce_resources=lax # given the errors, this is hyper-fishy

Wow I you were right, I removed that and could suspend & resume without problems 3 times in a row. I added that some time ago due to an IT sensor chip I couldn't use without it but now it seems to work without it. I had the page shuffle option due for hardening and the other two because I use PCIE passthrough but the ACPI one was probably the cause. I'll add solved to the title if I don't get this error in the next two days or so, thanks a lot!

Offline

Pages: 1

Board footer

Powered by FluxBB