Summary: | [CI][BAT]igt@i915_selftest@live_client - dmesg-warn - INFO: trying to register non-static key, the code is fine but needs lockdep annotation. | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | not set | ||
Priority: | not set | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | PNV | i915 features: | GEM/Other |
Description
Lakshmi
2019-10-25 05:53:32 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * PNV: igt@i915_selftest@live_client - dmesg-warn - INFO: trying to register non-static key, the code is fine but needs lockdep annotation. - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7175/fi-pnv-d510/igt@i915_selftest@live_client.html Oh, register raced with the ongoing GT work! https://patchwork.freedesktop.org/series/68576/ commit c442292a661bec3a32cf2a351c53c5f07da20e21 (HEAD -> drm-intel-next-queued, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Oct 25 17:54:42 2019 +0100 drm/i915/pmu: Initialise the spinlock before registering As the GT may be running in parallel with the module initialisation code, we may enter i915_pmu_gt_parked() as we are executing i915_pmu_register(). We have to init the spinlock before we mark pmu.event_init so that it is available for use by i915_pmu_gt_parked() (which may run as soon as event_init is set). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112127 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20191025165442.23356-1-chris@chris-wilson.co.uk |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.