System freezes on suspend

chapelierfou · 2023-02-05 00:08:41

Hello,

When I attempt to suspend my desktop computer with Arch Linux, the display freezes, including the mouse cursor (the screens do not blank nor go to standby). The fans and power LED stay on. The system appears irrecoverable from that state as the USB keyboard seems disabled (backlight turns off) and the power button has no effect. I'm running Arch Linux with KDE Plasma under X11, the motherboard is a Gigabyte B450 Aorus Pro Wifi with the last BIOS update (F63c) and the video card is an AMD Radeon RX 5700 (Navi 10).

Sadly I can't see anything weird in the log before the freeze happen:

$ journalctl -b -1 | tail -20
févr. 05 00:19:10 zeus systemd[1120]: app-org.kde.konsole-66eb3e8f636949759499bc499b5279ae.scope: Consumed 2.538s CPU time.
févr. 05 00:19:11 zeus kernel: usb 3-3.3: reset high-speed USB device number 6 using xhci_hcd
févr. 05 00:19:12 zeus systemd[1120]: app-org.kde.dolphin-414b1ace26b94bd5a392be051dede70b.scope: Consumed 13.290s CPU time.
févr. 05 00:19:14 zeus kernel: usb 3-3.3: reset high-speed USB device number 6 using xhci_hcd
févr. 05 00:19:17 zeus systemd-logind[693]: The system will suspend now!
févr. 05 00:19:17 zeus NetworkManager[720]: <info>  [1675552757.1512] manager: sleep: sleep requested (sleeping: no  enabled: yes)
févr. 05 00:19:17 zeus NetworkManager[720]: <info>  [1675552757.1514] device (wlan0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
févr. 05 00:19:17 zeus NetworkManager[720]: <info>  [1675552757.1521] device (wlan0): set-hw-addr: reset MAC address to 0C:DD:24:32:EC:3B (unmanage)
févr. 05 00:19:17 zeus NetworkManager[720]: <info>  [1675552757.1530] device (C0:EE:FB:33:90:C9): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
févr. 05 00:19:17 zeus NetworkManager[720]: <info>  [1675552757.1532] manager: NetworkManager state is now ASLEEP
févr. 05 00:19:17 zeus kscreenlocker_greet[23805]: Qt: Session management error: networkIdsList argument is NULL
févr. 05 00:19:17 zeus kscreenlocker_greet[23805]: kf.kirigami: Failed to find a Kirigami platform plugin
févr. 05 00:19:17 zeus kscreenlocker_greet[23805]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
févr. 05 00:19:17 zeus kscreenlocker_greet[23805]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
févr. 05 00:19:17 zeus systemd[1]: Reached target Sleep.
févr. 05 00:19:17 zeus plasmashell[1234]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
févr. 05 00:19:17 zeus plasmashell[1234]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
févr. 05 00:19:17 zeus systemd[1]: Starting System Suspend...
févr. 05 00:19:17 zeus systemd-sleep[23847]: Entering sleep state 'suspend'...
févr. 05 00:19:17 zeus kernel: PM: suspend entry (deep)

Here is some other system info:

$ 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.3 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 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller (rev 01)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
06:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
09:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c4)
0a:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4)
0b:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
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

$ uname -r
6.1.8-arch1-1
$ pacman -Q xf86-video-amdgpu
xf86-video-amdgpu 22.0.0-1

I tried playing with boot parameters like `acpi=linux`, to no avail.

Could someone please give me some pointers about where to investigate?

seth · 2023-02-05 08:55:41

https://01.org/blogs/rzhang/2015/best-p … ate-issues

cat /sys/power/mem_sleep

journalctl -b -1 | tail -20

That's not gonna work as the journal can't be synced to disk after the kernel halts.
Boot the multi-user.target (2nd link below), try to suspend from there and hope for some console messages.

boot parameters like `acpi=linux`, to no avail.

"acpi_osi" and if anything you'd probably want to fake windows,

acpi_osi=! acpi_osi='Windows 2015'

Also please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

If there're relevant warnings reg. the ACPI, they'll happen much earlier (don't freak out: there will be *some* ACPI warnings for sure. Doesn't mean they're meningful)

dcy3rka · 2023-02-05 09:24:27

Same problem here since some days. When I get the time I will check the logs too.

dcy3rka · 2023-02-05 11:32:30

Strange beaviour. Boot from a Snapshot from a week ago had no problem with suspend. If I updated to the latest available packages the problem came back. Then I decided to update packages step by step with power- und graphics related packages at last. Now I'm on the latest version again without any reproducible suspend problems and I don't know why.

Therefor: maybe a reinstall of acpi_call, upower, etc. maybe helps? Sorry, I don't have the time to go into deeper...

chapelierfou · 2023-02-08 12:11:39

seth wrote:

https://01.org/blogs/rzhang/2015/best-p … ate-issues

Thank you for your help!

$ cat /sys/power/mem_sleep
s2idle [deep]

Boot the multi-user.target (2nd link below), try to suspend from there and hope for some console messages.

Indeed, I get console messages about a suspend error:

[ 52.735683] Freezing user space processes... (elapsed 0.001 seconds) done.
[ 52.736910] OOM killer disabled.
[ 52.736926] Freezing remaining freezable tasks... (elapsed 0.001 seconds) done.
[ 53.012160] sd 5:0:0:0: [sdc] Stopping disk
[ 53.010948] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
[ 53.847639] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[ 53.848398] sd 4:0:0:0: [sdb] Stopping disk
[ 54.027620] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 54.028558] sd 1:0:0:0: [sda] Stopping disk
[ 55.640655] xhci_hcd 0000:0d:00.3: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 55.640722] xhci_hcd 0000:0d:00.3: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 55.640755] xhci_hcd 0000:0d:00.3: PM: failed to suspend: error -16
[ 55.640781] PM: Some devices failed to suspend, or early wake event detected
[ 55.646898] sd 1:0:0:0: [sda] Starting disk
[ 55.957540] ata1: SATA link down (SStatus SControl 300)
[ 56.117536] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 56.117596] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 56.117638] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 56.119207] ata2.00: configured for UDMA/133
[ 56.119548] ata6.00: configured for UDMA/133
[ 56.124772] ata5.00: configured for UDMA/133

"acpi_osi" and if anything you'd probably want to fake windows,
acpi_osi=! acpi_osi='Windows 2015'

I meant "acpi_osi=Linux", sorry. "acpi_osi=! acpi_osi='Windows 2015'" prevents the kernel from booting, the last thing printed is the following error:

[ 1.446374) clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc-early' as unstable because the skew is too large:
[ 1.446734] clocksource:     'hpet' wd_nsec: 0 wd_now: ffffffff wd_last: ffffffff mask: ffffffff 
[ 1.446912] clocksource:     'tsc-early' cs_nsec: 506680032 cs_now: 5596ce3c64 cs_last: 552443c5aa mask: ffffffffffffffff
[ 1.447265] clocksource:     'tsc-early' is current clocksource.
[ 1.447447] tsc: Marking TSC unstable due to clocksource watchdog
[ 1.447631] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc-unstable'.
[ 1.447818] sched_clock: Marking unstable (1130431544, 317199026)<-(1450657268, -3026671)
[ 1.448093] clocksource: Switched to clocksource hpet

Sadly adding the kernel parameter "tsc=unstable" as suggested prevents from booting even earlier, it gets stuck at "Loading initial ramdisk..."

Also please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
If there're relevant warnings reg. the ACPI, they'll happen much earlier (don't freak out: there will be *some* ACPI warnings for sure. Doesn't mean they're meningful)

Here is the log.

Last edited by chapelierfou (2023-02-08 13:56:10)

chapelierfou · 2023-02-08 14:36:17

So from the error message on suspend it looks like the USB 3 controller prevents suspending:

[ 55.640655] xhci_hcd 0000:0d:00.3: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 55.640722] xhci_hcd 0000:0d:00.3: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 55.640755] xhci_hcd 0000:0d:00.3: PM: failed to suspend: error -16
[ 55.640781] PM: Some devices failed to suspend, or early wake event detected

$ lspci|grep "0d:00.3"
0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

The issue looks a bit similar to the one reported here. Disabling the USB controller allows to suspend, however the machine wakes up in the same frozen state as before: power LED on, fan on, display on but seemingly stuck on a frozen frame (taking into account that the USB keyboard is disabled), the kernel answers pings but I'm unable to SSH into the system.

echo -n "0000:0d:00.3" > /sys/bus/pci/drivers/xhci_hcd/unbind && systemctl suspend

seth · 2023-02-08 14:58:20

You can try "Windows 2012" and "Windows 2009" instead

[ 55.640655] xhci_hcd 0000:0d:00.3: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 55.640722] xhci_hcd 0000:0d:00.3: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 55.640755] xhci_hcd 0000:0d:00.3: PM: failed to suspend: error -16
[ 55.640781] PM: Some devices failed to suspend, or early wake event detected

0. https://bbs.archlinux.org/viewtopic.php?id=277229

1. Disable https://wiki.archlinux.org/title/Power_ … utosuspend , "usbcore.autosuspend=-1"
2. remove/replace all external usb devices

3. Disable https://wiki.archlinux.org/title/Power_ … Management for the device

cat /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control
echo on | sudo tee /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control
cat /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control

Should allow a runtime test, maybe you also need to alter /sys/class/pci_bus/0000:0d/power/control, notably if the device is already on "on"

chapelierfou · 2023-02-09 10:25:23

seth wrote:

You can try "Windows 2012" and "Windows 2009" instead

Both boot but they don't seem to have any impact on the freezing issue.

seth wrote:

0. https://bbs.archlinux.org/viewtopic.php?id=277229
1. Disable https://wiki.archlinux.org/title/Power_ … utosuspend , "usbcore.autosuspend=-1"

The bluetooth workaround and the "usbcore.autosuspend=-1" parameter have no effect.

seth wrote:

2. remove/replace all external usb devices

OK, the only externally-connected devices were the keyboard, mouse, and UPS (Eaton 3S). Disconnecting the UPS allows suspending for some reason. I can even wake up from keyboard. However, the system is still frozen when waking up.

seth wrote:

3. Disable https://wiki.archlinux.org/title/Power_ … Management for the device
cat /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control
echo on | sudo tee /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control
cat /sys/class/pci_bus/0000:0d/device/0000:0d:00.3/power/control
Should allow a runtime test, maybe you also need to alter /sys/class/pci_bus/0000:0d/power/control, notably if the device is already on "on"

It looks like this has no effect either, only disconnecting the UPS, unbinding the device, or removing the xhci_pci module does, which is good enough I guess.

Anyway, USB preventing suspend does not look like the core issue here, as the system still freezes afterwards in any case. If I suspend from graphical target then wake up, the display is frozen (for instance the lock screen animation is stuck half way). If I suspend from multi-user target then wake up, it's not (I can see the cursor blinking), but nothing happens. In both cases, the system is not recoverable, USB devices are inactive (even the keyboard and even after unplugging-replugging), the kernel answers pings but the SSH server does not answer connections.

From multi-user target, it prints:

[ 42.699116] ACPI: PM: Low-level resume complete
[ 42.699142] ACPI: PM: Restoring platform NVS memory
[ 42.699307] LVT offset 0 assigned for vector 0x400
[ 42.699739] Enabling non-boot CPUs
[ 42.699817] x86: Booting SMP configuration:
[ 42.699819] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 42.699956] microcode: CPU1: patch_level=0x08701021
[ 42.702508] ACPI: \_PR_.C002: Found 2 idle states
[ 42.705326] CPU1 is up
[ 42.705354] smpboot: Booting Node Processor 2 APIC 0x4
[ 42.705491] microcode: CPUZ: patch_level=0x08701021
[ 42.707705] ACPI: \_PR_.C004: Found 2 idle states
[ 42.708670] CPU2 is up
[ 42.708697] smpboot: Booting Node Processor 3 APIC 0x8
[ 42.708835) microcode: CPU3: patch_level=0x08701021
[ 42.711073] ACPI: \_PR_.C006: Found 2 idle states
[ 42.712421] CPU3 is up
[ 42.712454] smpboot: Booting Node Processor 4 APIC 0xa
[ 42.712611] microcode: CPU4: patch_level=0x08701021
[ 42.714847] ACPI: \_PR_.C008: Found 2 idle states
[ 42.715755] CPU4 is up
[ 42.715787] smpboot: Booting Node Processor 5 APIC 0xc
[ 42.715940) microcode: CPU5: patch_level=0x08701021
[ 42.718179] ACPI: \_PR_.C00A: Found 2 idle states
[ 42.718872] CPU5 is up
[ 42.718902] smpboot: Booting Mode Processor 6 APIC 0x1
[ 42.719070] microcode: CPU6: patch_level=0x08701021
[ 42.721318] ACPI: \_PR_.C001: Found 2 idle states
[ 42.722240] Spectre V2: Update user space SMT mitigation: STIBF always-on
[ 42.722257] CPU6 is up
[ 42.722296] smpboot: Booting Mode 0 Processor 7 APIC 0x3
[ 42.722421] microcode: CPU7: patch_level=0x08701021
[ 42.724669] ACPI: \_PR_.C003: Found 2 idle states
[ 42.725709] CPU7 is up
[ 42.725740] smpboot: Booting Mode Processor 8 APIC 0x5
[ 42.725883] microcode: CPU8: patch_level=0x08701021
[ 45.921747] sd 1:0:0:0: [sda] Starting diskng jpeg_dec uses VM inv eng 5 on hub 1 00low Control: RX/TX
[ 46.232554] ata1: SATA link down (SStatus 0 SControl 300)
[ 46.392397] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 46.397387] ata5.00: configured for UDMA/133
[ 48.262133] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 48.269508) ata6.00: configured for UDMA/133
[ 50.412084] ata2: SATA link up 6.0 Gbps (3Status 133 SControl 300)
[ 50.441600] ata2.00: configured for UDMA/133

And it hangs there with blinking cursor. Note "ACPI Found 2 idle states / CPU8 is up" is weirdly missing for the last core, maybe that's the actual issue.

Last edited by chapelierfou (2023-02-09 10:30:09)

seth · 2023-02-09 12:58:49

Disconnecting the UPS allows suspending for some reason. I can even wake up from keyboard.

So that's progress.

I assume

[ 55.640655] xhci_hcd 0000:0d:00.3: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 55.640722] xhci_hcd 0000:0d:00.3: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 55.640755] xhci_hcd 0000:0d:00.3: PM: failed to suspend: error -16
[ 55.640781] PM: Some devices failed to suspend, or early wake event detected

is gone w/ that?

If I suspend from multi-user target then wake up, it's not (I can see the cursor blinking), but nothing happens. In both cases, the system is not recoverable

After the CPU restarts, it takes 3s to start sda and then it's hanging out 5s on the ata bus where you've one HDD and two SSDs

1st

Feb 08 12:31:39 zeus kernel: FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
…
Feb 08 12:31:40 zeus ntfs-3g[677]: Mounted /dev/sda2 (Read-Write, label "Windows-storage", NTFS 3.1)

Is there a parallel windows installation? => 3rd link below. Reboot both twice afterwards for voodoo reasons.

2nd, try w/o the SSDs (root FS seems to be on the HDD only?)

chapelierfou · 2023-02-19 21:17:33

seth wrote:

Disconnecting the UPS allows suspending for some reason. I can even wake up from keyboard.
So that's progress.

Yes, thank you for the help!

seth wrote:

I assume

[ 55.640655] xhci_hcd 0000:0d:00.3: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[ 55.640722] xhci_hcd 0000:0d:00.3: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
[ 55.640755] xhci_hcd 0000:0d:00.3: PM: failed to suspend: error -16
[ 55.640781] PM: Some devices failed to suspend, or early wake event detected

is gone w/ that?

Yes it is gone.

seth wrote:

1st
Feb 08 12:31:39 zeus kernel: FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
…
Feb 08 12:31:40 zeus ntfs-3g[677]: Mounted /dev/sda2 (Read-Write, label "Windows-storage", NTFS 3.1)
Is there a parallel windows installation? => 3rd link below. Reboot both twice afterwards for voodoo reasons.

Yes there is. Thanks for the tip, I updated from Windows 7 without knowing about this Fast Start thing, luckily I did not run into an issue until now...

I've disabled it and repaired the EFI partition, the "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." is gone but the problem persists on suspend.

seth wrote:

2nd, try w/o the SSDs (root FS seems to be on the HDD only?)

I need the SSDs to boot with the current setup (one contains Linux, the other Windows and the EFI partition), but I will unplug the HDD to see if it makes a difference (it's only used for storage).

chapelierfou · 2023-08-16 12:25:15

Sorry, I forgot to follow-up on this. I've removed the disks and moved everything to an NVMe disk to increase performance, which also solved this issue. Thank you for your help!

Last edited by chapelierfou (2023-08-16 12:25:49)

Arch Linux

#1 2023-02-05 00:08:41

System freezes on suspend

#2 2023-02-05 08:55:41

Re: System freezes on suspend

#3 2023-02-05 09:24:27

Re: System freezes on suspend

#4 2023-02-05 11:32:30

Re: System freezes on suspend

#5 2023-02-08 12:11:39

Re: System freezes on suspend

#6 2023-02-08 14:36:17

Re: System freezes on suspend

#7 2023-02-08 14:58:20

Re: System freezes on suspend

#8 2023-02-09 10:25:23

Re: System freezes on suspend

#9 2023-02-09 12:58:49

Re: System freezes on suspend

#10 2023-02-19 21:17:33

Re: System freezes on suspend

#11 2023-08-16 12:25:15

Re: System freezes on suspend

Board footer