On 2025-05-22 13:06 +03:00, Ozgur Karatas wrote:
> Alper Nebi Yasak <alpernebiya...@gmail.com>, 22 May 2025 Per, 12:57
> tarihinde şunu yazdı:
>>
>> Package: src:linux
>> Version: 6.12.29-1
>> Severity: important
>> Tags: upstream
>> Forwarded: https://gitlab.freedesktop.org/drm/amd/-/issues/4238
>
> Hello,
>
> this is a hardware or firmware error for the GPU so driver
> incompatibility and kernel not responding errors and resulting in a
> crash.
> is this latest Debian version? did you also install an AMD driver?
This is on Debian unstable with linux-image-6.12.29-amd64 and
firmware-amd-graphics (=20250410-2) packages from Debian, without
proprietary drivers from AMD. I'm using a Radeon 6800 XT in case knowing
that helps.
>> My PC consistently freezes with Linux v6.12.29 in a few minutes after
>> boot, but it works fine on v6.12.27 and v6.14.6. I've seen new errors
>> from the amdgpu module in the kernel dmesg.
>>
>> [ 3249.244690] amdgpu 0000:0d:00.0: amdgpu: [drm] amdgpu: AUX partially
>> written
>> [ 3249.244692] amdgpu 0000:0d:00.0: amdgpu: [drm] amdgpu: AUX reply command
>> not ACK: 0x01.
>> [ 3249.246142] amdgpu 0000:0d:00.0: amdgpu: [drm] amdgpu: AUX partially
>> written
>> [ 3249.246144] amdgpu 0000:0d:00.0: amdgpu: [drm] amdgpu: AUX reply command
>> not ACK: 0x01.
>> [ 3273.453141] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3273.453163] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3310.955288] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3310.959676] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3311.183514] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3311.407523] amdgpu 0000:0d:00.0: [drm] *ERROR*
>> dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
>> [ 3314.373183] clocksource: Long readout interval, skipping watchdog check:
>> cs_nsec: 2302686514 wd_nsec: 2302685676
>> [ 3315.677400] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your
>> previous command: SMN_C2PMSG_66:0x00000028 SMN_C2PMSG_82:0x00000000
>> [ 3315.677407] amdgpu 0000:0d:00.0: amdgpu: Failed to enable gfxoff!
>> [ 3320.662787] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your
>> previous command: SMN_C2PMSG_66:0x00000028 SMN_C2PMSG_82:0x00000000
>> [ 3320.662794] amdgpu 0000:0d:00.0: amdgpu: Failed to enable gfxoff!
>> [ 3320.806277] amdgpu 0000:0d:00.0: amdgpu: Dumping IP State
>> [ 3325.715100] amdgpu 0000:0d:00.0: amdgpu: SMU: I'm not done with your
>> previous command: SMN_C2PMSG_66:0x00000028 SMN_C2PMSG_82:0x00000000
>> [ 3325.715107] amdgpu 0000:0d:00.0: amdgpu: Failed to enable gfxoff!
>> [ 3325.720230] amdgpu 0000:0d:00.0: amdgpu: Dumping IP State Completed
>> [ 3325.720283] amdgpu 0000:0d:00.0: amdgpu: ring vcn_dec_0 timeout, signaled
>> seq=367410, emitted seq=367411
>> [ 3325.720287] amdgpu 0000:0d:00.0: amdgpu: Process information: process RDD
>> Process pid 4872 thread firefox:cs0 pid 5309
>> [ 3325.720290] amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
>> [...]
>> [ 3335.748049] watchdog: Watchdog detected hard LOCKUP on cpu 23
>>
>> Apparently there are already upstream reports for those about it, where
>> people tracked it to commit cfb2d41831ee ("drm/amd/display: more liberal
>> vmin/vmax update for freesync"). Setting my display to a fixed 60Hz
>> appears to help, the messages above are shortly after switching back to
>> 144Hz (which would enable freesync) after running about an hour at 60Hz.
>>
>> Apparently the commit is in v6.15-rc6/7 as well, in case you're thinking
>> of an experimental upload any time soon.
>>
>> [...]
