You're totally right that there is a problem when memory pressure is high that the suspend sequence can't evict the RAM.
This is upstream https://gitlab.freedesktop.org/drm/amd/-/issues/2362 A bunch of changes are going into 6.7 that will move the parts that allocate memory into the prepare() pmops sequence. This will "fix" the immediate problem in that the suspend itself will "return" an error code. There is a secondary problem though that the PM core disables swap "too soon", so if memory is low it can't be moved into swap. This secondary problem can either be fixed by PM core either moving the timing of the swap disable or evicting some other usage (userspace?) into swap before letting the prepare()/suspend() sequence start. ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - Desktop cannot resume after suspend: screen not detected + dGPU suspend fails under memory pressure ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2362 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Assignee: Mario Limonciello (superm1) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: dGPU suspend fails under memory pressure Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F.... pulseaudio /dev/snd/controlC1: pieq 2262 F.... pulseaudio /dev/snd/controlC0: pieq 2262 F.... pulseaudio /dev/snd/controlC2: pieq 2262 F.... pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lo no wireless extensions. enp3s0 no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
