[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1086604: marked as done (linux-image-6.11.4-amd64: amdgpu is unable to resume from suspend)

Your message dated Sat, 22 Mar 2025 14:45:05 +0100 (CET)
with message-id <20250322134505.E1385BE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1086604,
regarding linux-image-6.11.4-amd64: amdgpu is unable to resume from suspend
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1086604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086604
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 6.11.4-1
Severity: important


Dear Maintainer,
After an update to 6.11.4, I am observing the following single line in the TTY after resume from S3: 

```
amdgpu 0000:75:00.0: drm *ERROR* dc_dmub_srv_log_diagnostic_data dmcub error - collecting diagnostic data 
```

The problem is not present when booting 6.10.X and earlier kernels.

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself without
resolution. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are closing
older bugs were they look sensible to be closed. For an overview see:
https://bugs.debian.org/src:linux .

If you can reproduce your issue with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debuging on your side as the owner of the
hardware.

Regards,
Salvatore

--- End Message ---
Reply to: