On 11/28/2022 5:08 AM, Ville Syrjälä wrote:
On Mon, Nov 28, 2022 at 01:10:58AM -0800, Ceraolo Spurio, Daniele wrote:
On 11/25/2022 5:54 AM, Ville Syrjälä wrote:
On Thu, Nov 10, 2022 at 04:56:51PM -0800, Daniele Ceraolo Spurio wrote:
The fence is always initialized in huc_init_early, but the cleanup in
huc_fini is only being run if HuC is enabled. This causes a leaking of
the debug object when HuC is disabled/not supported, which can in turn
trigger a warning if we try to register a new debug offset at the same
address on driver reload.
To fix the issue, make sure to always run the cleanup code.
This oopsing in ci now. Somehow the patchwork run did not
hit that oops.
Can you point me to the oops log? I opened a few recent runs at random
but I wasn't able to find it.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12425/fi-blb-e6850/igt@core_hotunplug@xxxxxxxxxxxxxxxxxx
Thanks, it's indeed the same issue (and I've just confirmed that the
pre-merge result for the fix do mention that this test is moving from
incomplete to pass). From just a visual inspection I thought the problem
would only affect MTL, which does have HuC but only on one of the 2 GTs,
but it looks like this impacts also platforms without HuC at all (as
long as they also have no VCS engines). I'll try to get the fix reviewed
and merged ASAP.
Thanks,
Daniele
