Summary: | [CI][BAT]igt@i915_module_load@reload-with-fault-injection - incomplete - DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock)) | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED MOVED | 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: | KBL | i915 features: | display/Other |
Description
Lakshmi
2019-11-15 12:36:03 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * KBL: igt@i915_module_load@reload-with-fault-injection - incomplete - DEBUG_LOCKS_WARN_ON(mutex_is_locked(lock)) (No new failures associated) So the drm_poll_helper_fini() is a little too early. commit 448aa9117cfa6591c4e18cb32a0329a66b9cd3b7 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Nov 28 11:01:47 2017 +0000 drm/i915: Enable hotplug polling after registering the outputs I'd like to split drm_kms_helper_probe_enable/disable so that we can use it in register/unregister and so move the init/fini back to their original locations. Chris, are you saying this already fixed? (In reply to Jani Saarinen from comment #3) > Chris, are you saying this already fixed? Just reminding myself of the conversation with Daniel about the likely cause here. No, it's not yet fixed. OK, this is only DP_MST setup in CI. Setup is Dell XPS (KBL) and TB16 dock connected to port and from dock mini-DP to DP-MST (4K) Dell monitor (DP In) and from that DP out to normal Dell Monitor -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/609. |
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.