Bug 219048 - System doesn't wake up properly from S3 sleep
Summary: System doesn't wake up properly from S3 sleep
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-16 18:36 UTC by dellamorte
Modified: 2024-09-30 08:33 UTC (History)
1 user (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
kernel log (98.12 KB, text/plain)
2024-07-18 21:14 UTC, dellamorte
Details

Description dellamorte 2024-07-16 18:36:28 UTC
Hello,

my system doesn't boot properly with linux LTS 6.6 including 6.6.40. After going to sleep it will wakeup frozen to blank screen. Reboot doesn't help as motherboard doesn't start. I need to do (often several) cold power down/up to make it work again. After successful boot reading journalctl -b -1 will show last message that system went to sleep. 

When switched to stable kernel 6.9.9 i got slightly different behavior: system went up but most of peripherales were unresponsive, including mouse and keyboard. Kernel log shows:

Jul 16 19:17:51 home-pc kernel: ACPI: PM: Waking up from system sleep state S3
Jul 16 19:17:51 home-pc kernel: pcieport 0000:00:01.2: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:09.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:01.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:0a.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:05.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:04.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: ahci 0000:0a:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:03.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pcieport 0000:03:08.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: nvme 0000:04:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: ahci 0000:09:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: mt7921e 0000:07:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: r8169 0000:06:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: pci 0000:08:00.0: Unable to change power state from D0 to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: Unable to change power state from D3hot to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: Controller not ready at resume -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: PCI post-resume error -19!
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: HC died; cleaning up
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:05:00.0: PM: failed to resume async: error -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: Unable to change power state from D3cold to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: Controller not ready at resume -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: Controller not ready at resume -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: PCI post-resume error -19!
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: PCI post-resume error -19!
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: HC died; cleaning up
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: HC died; cleaning up
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.3: PM: failed to resume async: error -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -19
Jul 16 19:17:51 home-pc kernel: xhci_hcd 0000:08:00.1: PM: failed to resume async: error -19
Jul 16 19:17:51 home-pc kernel: nvme 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jul 16 19:17:51 home-pc kernel: nvme nvme1: Disabling device after reset failure: -19

Several times this happened on LTS kernel as well, but usually it is a blank screen.

Used hardware: x570s Aorus Elite AX with Ryzen 9 3900X processor. I also tried different MBO and GPU but without success.
Comment 1 Artem S. Tashkinov 2024-07-17 08:23:03 UTC
Could you please provide `lspci` and *full* `dmesg` output (including boot and a failure to resume)?
Comment 2 dellamorte 2024-07-18 20:57:17 UTC
lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E: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] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
04:00.0 Non-Volatile memory controller: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 
lspci out:

Plus NVMe PCIe SSD (DRAM-less) (rev 01)
05:00.0 USB controller: ASMedia Technology Inc. ASM3241 USB 3.2 Gen 2 Host Controller
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
07:00.0 Network controller: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz
08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
08:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
08:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] (rev f1)
0b:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tonga HDMI Audio [Radeon R9 285/380]
0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
0d:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0d:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
Comment 3 dellamorte 2024-07-18 21:14:41 UTC
Created attachment 306579 [details]
kernel log

Kernel log is attached.
Comment 4 dellamorte 2024-07-19 09:48:43 UTC
This is also from last night. I disabled sleep but still there was some trouble in communication with GPU:

Jul 19 03:36:46 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:36:51 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:36:57 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:05 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:13 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:19 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:27 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:35 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:43 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:52 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:37:57 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:02 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:11 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:19 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:24 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:33 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 03:38:41 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:03:25 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:03:33 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:03:39 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:03:44 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:03:53 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:04:01 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:04:06 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:04:14 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:04:23 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:05:31 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:05:39 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:05:45 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:05:50 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:05:58 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:07 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:12 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:20 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:29 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:37 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:45 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:50 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:06:56 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:07:04 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:07:12 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:07:18 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:07:26 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 10:07:34 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Jul 19 11:09:19 home-pc kernel: amdgpu 0000:0b:00.0: amdgpu: 
                                last message was failed ret is 0
Comment 5 Artem S. Tashkinov 2024-07-19 11:23:41 UTC
Please try the following:

* Update BIOS to the latest version
* Reset BIOS settings
Comment 6 Artem S. Tashkinov 2024-07-19 11:32:48 UTC
Stanislaw Gruszka,

Do you have any ideas what could be wrong with this system?
Comment 7 dellamorte 2024-07-19 15:22:17 UTC
Bios is updated to latest release, default settings. No changes in behavior.
Comment 8 dellamorte 2024-09-30 08:33:11 UTC
This is connected to this bug:

https://bugzilla.kernel.org/show_bug.cgi?id=217415

I realized it after my wifi card died out (or new kernel release is completely screwed up), it doesn't start properly anymore so I removed it from the motherboard, and i will replace it with different one. However i still can get this issue to happen but now it is 1 out of 10 times when i send it to sleep.

Note You need to log in before you can comment on or make changes to this bug.