Here's a patch that inserts a few trace events.
https://pastebin.com/dpLnVSbu

Could you try to reproduce the hang again while recording these trace events?
Using trace-cmd (with stack trace enabled '-T'):

I think Michele said that the timeout issue would be masked by drm.debug due to overhead?


     trace-cmd record -e amdgpu_dm_event_arm -e drm_vblank_dbg* -T
     trace-cmd report trace.dat

The timeout can be found by searching 'remaining_wait_ms=0'.

Regarding the deferred vblank patchset, if the issue is indeed racing writes of
amdgpu_crtc->event, then I don't imagine that patchset would help. It's
intended to solve a different race.

Thanks,
Leo



fixed [email protected] cc


Attachment: OpenPGP_0xE3520CC91929C8E7.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to