Hi, > On Wed, 04 Nov 2026, Wentao Guan <[email protected]> wrote: > > cancel_async_put_work() also clears async_put_next_delay, so moving it > > ahead of the requeue in intel_display_power_put_async_work() makes the > > requeue always use a zero delay. That discards the delay accumulated by > > concurrent async puts, including the 17 ms DC-state anti-toggle delay > > requested for POWER_DOMAIN_DC_OFF. > > > > Use cancel_delayed_work() directly to cancel the stale instance without > > clearing the delay, and clear the delay only after the requeue has > > consumed it. > > > > Fixes: 30ca6365bb42 ("drm/i915: Fix assert on pending async-put power > > domain work when it requeues itself") > > Cc: <[email protected]> # v6.11+ > > Signed-off-by: Wentao Guan <[email protected]> > > How did you find this? During a stable bugfix backport work, found by github copilot max(gpt-6.1-sol[ReasoningEffort=xhigh]).
> Is there a bug report about this? Just see: https://github.com/deepin-community/kernel/pull/2239#discussion_r4463718883 > How did you test this? Review again, build again, integation by anothor one. It is not the original bug we met, the bug sovled by backport many i915 update commits as them in mainline. BRs Wentao Guan
