You need to provide the full kernel log and device information (from
lspci).
Kernel log can't be acquired as the system isn't accessible after the
bug is triggered. Other TTYs are unresponsive as well. lspci below:
```
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14d8
00:
Control: tag -1 moreinfo
On Sat, 2024-11-02 at 11:17 +1030, and...@lists.savchenko.net wrote:
> 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:
>
> ``
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 :75:00.0: drm *ERROR* dc_dmub_srv_log_diagnostic_data dmcub
error - collecting diagnostic data
```
3 matches
Mail list logo
