Two more updates: another confirmed occurrence of the GPU-reset-during- hibernate-resume signature, plus a distinct new failure mode (silently orphaned desktop session, no suspend ever logged) — and frequency data showing this class of bug is a regular, recurring problem rather than an occasional edge case. ## Update 1 (2026-09-03): another GPU reset during hibernation resume, kernel 7.0.0-27-generic Same signature as the 2026-08-19 update above: amdgpu 0000:04:00.0: ring sdma0 timeout, signaled seq=296951, emitted seq=296953 amdgpu 0000:04:00.0: GPU reset begin!. Source: 1 amdgpu 0000:04:00.0: [drm] *ERROR* dpcd_set_link_settings:1122/1127/1155: core_link_write_dpcd (...) failed amdgpu 0000:04:00.0: GPU pre asic reset failed with err, -22 amdgpu 0000:04:00.0: MODE2 reset amdgpu 0000:04:00.0: GPU reset succeeded, trying to resume amdgpu 0000:04:00.0: VRAM is lost due to GPU reset! amdgpu 0000:04:00.0: [drm] *ERROR* DPM disable vcn failed, ret = -62. This happened immediately on hibernation exit (image had frozen successfully, plenty of free-page margin, so not the ENOMEM case below). The machine kept running afterward in a degraded graphics state but became fully unresponsive roughly an hour later, with no orderly shutdown logged — required a hard power-off. ## Update 2 (2026-09-08): new failure mode — desktop session silently lost, suspend request never reaches logind, machine runs hot for hours, battery drained This is different from the amdgpu ring-timeout pattern above. Timeline: - ~19:00 — user triggers "Suspend" from the Plasma menu. No corresponding "The system will suspend now!" line from systemd-logind, no "PM: suspend entry" — the request never reached logind at all. No error of any kind logged either. - 1-2 hours later — laptop found running hot (fans presumably active, not asleep). A second suspend attempt is made; again nothing logged. - ~21:48 — an explicit, orderly shutdown finally happens (clean systemd-poweroff sequence). Right as this shutdown starts, kwin_wayland logs: kwin_core: Failed to open /dev/dri/renderD128 device (Unknown object '/org/freedesktop/login1/session/_33'.) kwin_core: Failed to open /dev/input/event5 device (Unknown object '/org/freedesktop/login1/session/_33'.) i.e. logind no longer recognized the Plasma session's own session object as valid — consistent with the interactive session having silently detached/orphaned itself well before the shutdown, explaining why neither suspend attempt could have worked: the session invoking them was already broken. - Next morning: lid-open did not wake anything (machine was genuinely off by then, from the 21:48 shutdown), and the battery was found drained — consistent with several hours of full operation (screen/fans active) between the first failed suspend (~19:00) and the eventual shutdown (~21:48), rather than genuine low-power suspend. No amdgpu errors, no OOM, no crash of any kind logged around the failed suspend attempts — the session simply stopped being able to act on sleep requests, silently. ## Frequency data (last 3 weeks, 2026-08-19 to 2026-09-09) Grepping this machine's journal for each known failure signature: - GPU reset during suspend/hibernate (ring timeout + MODE2 reset): 3 separate days (Aug 19, Sep 1, Sep 3) - Orphaned/lost logind session (this update's new pattern): 4 separate days (Aug 20, Aug 28, Sep 1, Sep 8) - Hibernation aborting cleanly with ENOMEM ("PM: hibernation: Error -12 creating image", safe failure, no data loss): 8 separate days (Aug 22, 25, 28, 29, 30, 31 [x2], Sep 3, Sep 6) Combined, some form of sleep/hibernate failure has occurred on the large majority of weeks since this was first reported, across multiple distinct failure modes (GPU driver hang, orphaned session, memory pressure) and across both kernel builds tested (7.0.0-27 and 7.0.0-28). This no longer looks like an occasional edge case — power-state transitions are broadly unreliable on this AMD Barcelo iGPU (amdgpu) platform under current Ubuntu 25.10 kernels. ## Hardware/software (unchanged) Dell Inspiron 14 5425, AMD Ryzen 7 5825U, AMD Barcelo iGPU (amdgpu), Ubuntu 25.10, KDE Plasma 6.5, Wayland. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161312 Title: System hangs on suspend (s2idle) with kernel 7.0.0-28-generic, works fine on 7.0.0-27 Status in linux package in Ubuntu: New Bug description: Hello Here is a bug occurring on my laptop. The analysis is from claude code. I hope it is relevant & complete. Thanks for your help. Summary System hangs permanently when entering suspend (s2idle) on kernel 7.0.0-28-generic; requires a hard power-off to recover. The exact same hardware suspended and resumed reliably dozens of times over 8 days on kernel 7.0.0-27-generic. The regression appeared immediately after the machine booted 7.0.0-28 for the first time — first suspend attempt on the new kernel already failed, and it failed again on the next boot. Hardware Machine: Dell Inspiron 14 5425 CPU: AMD Ryzen 7 5825U with Radeon Graphics GPU: AMD/ATI Barcelo iGPU (integrated, PCI 04:00.0) BIOS: 1.19.0 (2024-09-10) Sleep mode: only s2idle is offered by the platform (/sys/power/mem_sleep → [s2idle], no deep/S3 option available) Software Ubuntu 25.10 (Questing Quokka), KDE Plasma 6.5, Wayland session (kwin_wayland) Working kernel: linux-image-7.0.0-27-generic (7.0.0-27.27) Broken kernel: linux-image-7.0.0-28-generic (7.0.0-28.28) Steps to reproduce Boot into 7.0.0-28-generic. Trigger suspend (via systemd Suspend action / closing lid / GUI power menu). System freezes during or immediately after suspend entry: keyboard backlight stays lit, no reaction to any key or the power button short-press, screen never turns back on. Only recovery is holding the power button for a hard shutdown. Expected behavior System suspends and resumes normally, as it did consistently on 7.0.0-27-generic. Actual behavior System never comes back from suspend. journalctl shows the boot ending abruptly right after suspend entry, with no PM: suspend exit line and no orderly shutdown sequence — consistent with a full system hang, not a clean poweroff. Evidence from journalctl Working kernel (7.0.0-27), representative sample out of ~40 successful cycles between 2026-07-09 and 2026-07-17: juil. 16 19:31:46 kernel: PM: suspend entry (s2idle) juil. 17 14:48:21 kernel: PM: suspend exit Failing kernel (7.0.0-28), first attempt, boot ends here with no further log lines at all: juil. 20 10:42:38 root[18433]: Dell wakeup sources disabled - ALL including dock disconnect juil. 20 10:42:38 systemd-sleep[18388]: Performing sleep operation 'suspend'... juil. 20 10:42:38 kernel: PM: suspend entry (s2idle) [-- nothing further; next boot is a cold boot, not a resume --] Failing kernel (7.0.0-28), second attempt on a fresh boot, same pattern: juil. 20 12:32:59 systemd-sleep[26074]: Performing sleep operation 'suspend'... juil. 20 12:32:59 kernel: PM: suspend entry (s2idle) [-- nothing further --] Both failing boots are followed by a fresh cold boot (new boot ID in journalctl --list-boots), confirming the machine was hard power-cycled rather than resuming. Workaround Pinning the system to linux-image-7.0.0-27-generic (apt-mark hold) restores reliable suspend/resume. Additional notes A local dell-suspend-fix.service (disables PCI/USB/BT/WMI wakeup sources before sleep, standard workaround for this laptop's dock/eSATA wake-on-disconnect quirk) is present and unchanged across both the working and failing kernel — ruling it out as the cause. Not the known 7.0.0-28.28 AMDGPU/HMM ROCm performance regression (that one is a slowdown in compute workloads, not a hang) — this appears to be a separate, undocumented issue in the same kernel build. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 20 14:19:25 2026 InstallationDate: Installed on 2025-07-09 (376 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) IwDevWlp3s0Link: Not connected. MachineType: Dell Inc. Inspiron 14 5425 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=b239c123-a9a4-4924-bfc7-38c39f92e79b ro quiet splash acpi_backlight=native resume=UUID=871f8b5f-e842-4660-9c64-7661287c3695 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-09 (11 days ago) dmi.bios.date: 09/10/2024 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0J9C2M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.19.0 dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/10/2024:br1.19:svnDellInc.:pnInspiron145425:pvr1.19.0:rvnDellInc.:rn0J9C2M:rvrA00:cvnDellInc.:ct10:cvr1.19.0:sku0B46:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5425 dmi.product.sku: 0B46 dmi.product.version: 1.19.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161312/+subscriptions
Комментариев нет:
Отправить комментарий