Mario,

I completed further read-only investigation of the suspend/resume failure
on my Dell Inspiron 15 3525 and preserved the evidence in a local
SHA256-verified checkpoint.
System information

   -

   Laptop: Dell Inspiron 15 3525
   -

   Processor: AMD Ryzen 7 5825U (Barcelo)
   -

   Integrated graphics: AMD Barcelo [1002:15e7]
   -

   Graphics driver: amdgpu
   -

   Operating system: Ubuntu 26.04.1 LTS
   -

   Kernel: 7.0.0-43-generic
   -

   Suspend mode: s2idle
   -

   DMUB firmware: 0x0101002B
   -

   Display Core: v3.2.369 (DCN 2.1)

Three historical suspend attempts

I identified three historical suspend attempts in which an AMD DMCUB
diagnostic error occurred immediately before the recorded suspend entry.

*November 7, 2026 — 18:18:03*

DMCUB error:
18:18:03.475285

Suspend entry:
18:18:03.778973

Difference: 0.304 seconds.

*November 7, 2026 — 21:58:06*

Last DMCUB error:
21:58:05.588042

Suspend entry:
21:58:06.367973

Difference: 0.780 seconds.

*November 8, 2026 — 00:15:54*

Last DMCUB error:
00:15:53.840258

Suspend entry:
00:15:54.546242

Difference: 0.706 seconds.

The recurring kernel diagnostic message is:

amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB
error - collecting diagnostic data

Each attempt was followed by an absence of successful resume messages in
the available boot journal.

This does not establish precisely where suspension or resumption failed.
Additional findings

Across 12 examined historical boots running kernel 7.0.0-43-generic, I
identified 110 DMCUB diagnostic error messages.

These messages also occur during normal operation, so their proximity to
suspend entry does not establish causation.

Additional observations:

   -

   DMUB firmware initialization was recorded as successful.
   -

   Historical journal timestamps include some clock irregularities.
   -

   A TPM communication timeout was observed during an investigated boot,
   but its relevance remains unknown.
   -

   I inspected the amd-debug-tools source without running its active
   suspend test.
   -

   No CPU C6, GPU power-management, BIOS, firmware, or suspend-guard
   changes were made during this investigation.
   -

   BIOS storage-password configuration has not yet been verified.

Preserved diagnostic evidence

The historical journals, event extracts, graphics information, boot index,
findings, and SHA256 manifest have been preserved in:

~/SCOUT/checkpoints/suspend-recovery/amd-diagnostics-v0.1/

The checkpoint was verified and frozen read-only on November 11, 2026.

I can provide selected logs if they would assist further investigation.
Request for guidance

Given these findings, which additional read-only diagnostics would be most
useful?

I would prefer to avoid another suspend attempt until there is a clear and
justified testing plan, since the laptop has previously failed to resume
and required restarting.

Thank you for your continued assistance with this issue.


On Wed, Nov 11, 2026 at 12:04 PM Joseph Simons <[email protected]> wrote:

> Thank you for the guidance.
>
> The affected system is a Dell Inspiron 15 3525 with an AMD Ryzen 7 5825U,
> running Ubuntu 26.04.1 LTS, kernel 7.0.0-43-generic at the time of the
> report, with Dell BIOS 1.36.0.
>
> Regarding your questions:
>
>    1.
>
>    *SATA storage:* Yes. The laptop has a PNY 1 TB SATA SSD containing the
>    Ubuntu installation, as well as an Intel 670p 512 GB NVMe drive containing
>    Windows. I have not removed the SATA SSD because it contains the affected
>    Ubuntu installation, so I cannot yet report whether removal changes the
>    suspend behavior.
>    2.
>
>    *Storage password:* I have not yet confirmed whether a storage
>    password is configured in firmware. I will check without changing the
>    configuration.
>    3.
>
>    *AMD debug tools:* I will investigate amd-debug-tools and collect the
>    requested diagnostic information. I have not run another suspend test
>    because the machine has previously failed to resume, and I want to avoid
>    another uncontrolled shutdown. I will attach any relevant failure report
>    that can be collected safely.
>
> The suspend guard remains enabled pending a verified fix and controlled
> recovery plan.
>
> Thank you for helping investigate this issue.
>
>
> On Tue, Nov 10, 2026 at 11:55 AM Mario Limonciello <
> [email protected]> wrote:
>
>> ** Changed in: linux (Ubuntu)
>>        Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2173670
>>
>> Title:
>>   Dell Inspiron 15 3525 AMD Barcelo fails to resume from s2idle
>>
>> Status in linux package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   **System information**
>>
>>   - Laptop: Dell Inspiron 15 3525
>>   - Processor: AMD Ryzen 7 5825U
>>   - Graphics: AMD Barcelo [1002:15e7], amdgpu driver
>>   - Operating system: Ubuntu 26.04.1 LTS
>>   - Kernel: 7.0.0-43-generic
>>   - BIOS: Dell 1.36.0
>>   - Available sleep mode: s2idle only
>>
>>   **Problem**
>>
>>   The laptop fails to resume reliably from system suspension.
>>
>>   Both manually selecting Suspend and closing the laptop lid have caused
>>   black-screen failures. Normal wake attempts do not reliably restore
>>   the desktop, and recovery has required restarting the computer.
>>
>>   Ordinary display blanking after five minutes works correctly,
>>   including waking the display and entering the login password.
>>
>>   **Expected behavior**
>>
>>   The computer should enter s2idle and resume normally when the power
>>   button is briefly pressed.
>>
>>   **Actual behavior**
>>
>>   The laptop becomes unresponsive during suspension or fails to restore
>>   the display and desktop afterward.
>>
>>   **Relevant kernel messages — November 8, 2026**
>>
>>   At 00:15:53, the AMD graphics driver logged two DMCUB diagnostic
>>   errors:
>>
>>   `amdgpu: dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting
>>   diagnostic data`
>>
>>   At 00:15:54, the final recorded kernel message was:
>>
>>   `PM: suspend entry (s2idle)`
>>
>>   No successful suspend exit or resume completion was recorded
>>   afterward.
>>
>>   A TPM communication timeout was also logged earlier during startup,
>>   but its relationship to the suspend failure is unknown.
>>
>>   **Troubleshooting performed**
>>
>>   - Updated Dell BIOS from 1.3.0 to 1.36.0; the problem persisted.
>>   - Verified the amdgpu and amd_pmc drivers are loaded.
>>   - Verified the installed Ubuntu kernel and firmware packages match the
>> available repository candidate versions.
>>   - Preserved the original failed-boot kernel journal.
>>   - Temporarily disabled system suspension to prevent further hangs.
>>
>>   Further suspend tests are being avoided because recovery has been
>>   unreliable.
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173670/+subscriptions
>>
>>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2173670

Title:
  Dell Inspiron 15 3525 AMD Barcelo fails to resume from s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173670/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to