Hello, I'm confused, there are two mails in this bug log, senders differ, but they are still the same person? If not, replying to the bug someone else opened is only usefull if you're quite sure you see the exact same bug.
On Mon, Jul 20, 2026 at 02:28:01AM +0100, Nana K Gyasi wrote:
> Re: Bug#1142440: amdgpu Mullins: intermittent hibernation resume hang with
> page fault in drm_sched_job_arm
>
> Hello,
>
> I have now tested the immediately preceding Debian kernel on the same
> machine:
>
> 6.12.94+deb13-amd64
>
> The hardware and configuration were unchanged:
>
> AMD A8-6410 Mullins Radeon R4/R5
> PCI ID 1002:9851, subsystem 103c:2268
>
> radeon.cik_support=0
> amdgpu.cik_support=1
> amdgpu.dpm=1
>
> resume=/dev/mapper/sda8_crypt
> resume_offset=8278889
>
> The 16 GiB Btrfs hibernation swapfile was active and the 6.12.94
> initramfs contained the Dracut resume module.
>
> Results with 6.12.94:
>
> - graphical rendering was normal;
> - an ordinary suspend/resume succeeded;
> - two hibernation/resume cycles succeeded;
> - the restored desktop remained usable;
> - no page fault in drm_sched_job_arm was observed during these tests.
>
> However, 6.12.94 still produced the same underlying AMDGPU recovery
> errors seen with 6.12.95:
>
> WARNING at amdgpu_irq_put
> dce_v8_0_hw_fini
> dce_v8_0_suspend
>
> amdgpu_ring_test_helper:
> ring comp_1.0.0 through comp_1.0.3 test failed (-110)
>
> amdgpu: SRBM_SOFT_RESET=0x00100040
>
> [drm] scheduler comp_1.0.x is not ready, skipping
>
> The scheduler-not-ready messages continued repeatedly after the
> successful resume.
>
> The observed difference so far is:
>
> - 6.12.94: the AMDGPU compute-ring recovery failure occurred, but the
> system remained usable in the tests performed;
> - 6.12.95: the same failure sequence was followed by repeated kernel
> page faults in drm_sched_job_arm and an unusable system requiring a
> forced power-off.
>
> This suggests that the underlying AMDGPU hibernation/resume problem
> predates 6.12.95, although 6.12.95 may be more likely to progress into
> the fatal GPU scheduler fault.
>
> I have attached the filtered 6.12.94 kernel journal from the successful
> suspend and hibernation tests.
These bugs are hard for us (= Debian kernel team) to handle. It would be
best if you (two?) could retest with the latest 6.12 kernel from stable
and the latest kernel from testing/unstable. If the problem still
happens there, it't probably best to report that upstream.
> *Disclaimer*
> This message is intended only for the use of the person(s) ("Intended
> Recipient") to whom it is addressed. It may contain information, which is
> privileged and confidential. Accordingly any dissemination, distribution,
> copying or other use of this message or any of its content by any person
> other than the Intended Recipient may constitute a breach of civil or
> criminal law and is strictly prohibited. If you are not the Intended
> Recipient, please contact the sender as soon as possible.
This kind of trailer doesn't really make sense when sending a Debian bug
report that is publically archived.
Best regards
Uwe
signature.asc
Description: PGP signature
