Package: linux-image-6.1.0-6-amd64 Severity: normal When I suspend on my Gigabyte B660 GAMING X DDR4 motherboard, the following can be observed:
root@xxx:~# echo -n "mem" > /sys/power/state [ 56.895232] PM: suspend entry (deep) [ 56.906889] Filesystems sync: 0.008 seconds [ 57.112498] (NULL device *): firmware: direct-loading firmware i915/dg2_dmc_ver2_07.bin [ 57.112634] (NULL device *): firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin [ 57.112648] (NULL device *): firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin [ 57.112753] (NULL device *): firmware: direct-loading firmware i915/dg2_guc_70.bin [ 57.147342] Freezing user space processes [ 57.152920] Freezing user space processes completed (elapsed 0.001 seconds) [ 57.160054] OOM killer disabled. [ 57.163312] Freezing remaining freezable tasks [ 57.169022] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 57.788864] r8169 0000:06:00.0 eth0: Link is Down [ 57.980226] ACPI: PM: Preparing to enter system sleep state S3 [ 57.994907] ACPI: PM: Saving platform NVS memory [ 57.999917] Disabling non-boot CPUs ... [ 58.006843] smpboot: CPU 1 is now offline [ 58.012789] smpboot: CPU 2 is now offline [ 58.018614] smpboot: CPU 3 is now offline [ 58.024417] smpboot: CPU 4 is now offline [ 58.030298] smpboot: CPU 5 is now offline [ 58.036142] smpboot: CPU 6 is now offline [ 58.042138] smpboot: CPU 7 is now offline [ 58.049025] smpboot: CPU 8 is now offline [ 58.054802] smpboot: CPU 9 is now offline [ 58.060547] smpboot: CPU 10 is now offline [ 58.066398] smpboot: CPU 11 is now offline [ 58.072397] smpboot: CPU 12 is now offline [ 58.078247] smpboot: CPU 13 is now offline [ 58.084137] smpboot: CPU 14 is now offline [ 58.090204] smpboot: CPU 15 is now offline [ 58.095982] smpboot: CPU 16 is now offline [ 58.101833] smpboot: CPU 17 is now offline [ 58.107586] smpboot: CPU 18 is now offline [ 58.113414] smpboot: CPU 19 is now offline !!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!! ExceptionData - 0000000000000002 I:0 R:0 U:0 W:1 P:0 PK:0 SS:0 SGX:0 RIP - 000000003FA6760E, CS - 0000000000000038, RFLAGS - 0000000000010007 RAX - 000000000091E204, RCX - 00000000FFFFFF00, RDX - 000000000091E000 RBX - 000000003FA7D018, RSP - 000000003FCADB50, RBP - 000000003FCADB90 RSI - 000000003FB031C0, RDI - 000000003FA65E20 R8 - 0000000000000000, R9 - 000000003FCADBE8, R10 - 0000000000000001 R11 - 000000003FCADC30, R12 - 000000003FA7D020, R13 - 000000003FA7D020 R14 - 0000000000000001, R15 - 0000000000000001 DS - 0000000000000020, ES - 0000000000000020, FS - 0000000000000020 GS - 0000000000000020, SS - 0000000000000020 CR0 - 0000000080010033, CR2 - 000000000091E204, CR3 - 000000003FC80000 CR4 - 0000000000000668, CR8 - 0000000000000001 DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000 DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400 GDTR - 000000003FC7F000 000000000000004F, LDTR - 0000000000000000 IDTR - 000000003FC8B000 00000000000001FF, TR - 0000000000000040 FXSAVE_STATE - 000000003FC8CC60 I'm quite sure the problem is either in the upstream kernel or the vendor BIOS, however Gigabyte claims they have no reports of this behaviour on this board with Windows. I probably need some guidance to pinpoint the problem and properly report it to kernel maintainer, if it's not the BIOS (or a Debian kernel patch). -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)