| Summary: | [CI][DRMTIP]igt@perf_pmu@busy-no-semaphores-vcs0 - dmesg-warn- IRQs not enabled as expected | ||
|---|---|---|---|
| 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: | normal | ||
| Priority: | medium | CC: | chris, intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BXT, BYT | i915 features: | Perf/PMU |
|
Description
Lakshmi
2019-08-12 11:00:29 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT: igt@perf_pmu@busy-no-semaphores-vcs0 - dmesg-warn- IRQs not enabled as expected (No new failures associated) The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT: igt@runner@aborted - fail - Previous test: perf_pmu (busy-no-semaphores-vcs0) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_340/fi-byt-j1900/igt@runner@aborted.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_340/fi-byt-n2820/igt@runner@aborted.html commit a79ca656b648e6851dd2f1eb0dcef86b278a8908 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Aug 13 20:07:05 2019 +0100 drm/i915: Push the wakeref->count deferral to the backend If the backend wishes to defer the wakeref parking, make it responsible for unlocking the wakeref (i.e. bumping the counter). This allows it to time the unlock much more carefully in case it happens to needs the wakeref to be active during its deferral. For instance, during engine parking we may choose to emit an idle barrier (a request). To do so, we borrow the engine->kernel_context timeline and to ensure exclusive access we keep the engine->wakeref.count as 0. However, to submit that request to HW may require a intel_engine_pm_get() (e.g. to keep the submission tasklet alive) and before we allow that we have to rewake our wakeref to avoid a recursive deadlock. A CI Bug Log filter associated to this bug has been updated:
{- BYT: igt@perf_pmu@busy-no-semaphores-vcs0 - dmesg-warn- IRQs not enabled as expected -}
{+ APL BYT: igt@perf_pmu@busy-* - dmesg-warn- IRQs not enabled as expected +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6706/shard-apl4/igt@perf_pmu@busy-idle-no-semaphores-vecs0.html
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_343/fi-byt-n2820/igt@perf_pmu@busy-hang-rcs0.html
A CI Bug Log filter associated to this bug has been updated:
{- BYT: igt@runner@aborted - fail - Previous test: perf_pmu (busy-no-semaphores-vcs0) -}
{+ BYT: igt@runner@aborted - fail - Previous test: perf_pmu ((busy-no-semaphores-vcs0)|(busy-idle-no-semaphores-vecs0)|(busy-hang-rcs0)) +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6706/shard-apl4/igt@runner@aborted.html
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_343/fi-byt-n2820/igt@runner@aborted.html
(In reply to CI Bug Log from comment #6) > A CI Bug Log filter associated to this bug has been updated: > > {- BYT: igt@runner@aborted - fail - Previous test: perf_pmu > (busy-no-semaphores-vcs0) -} > {+ BYT: igt@runner@aborted - fail - Previous test: perf_pmu > ((busy-no-semaphores-vcs0)|(busy-idle-no-semaphores-vecs0)|(busy-hang-rcs0)) > +} > > New failures caught by the filter: > > * > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6706/shard-apl4/ > igt@runner@aborted.html > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_343/fi-byt-n2820/ > igt@runner@aborted.html Also on APL. commit 62520e3361d2d9e2e41d3958dcc34faee79a3c1a (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Aug 15 05:20:30 2019 +0100 drm/i915: Move tasklet kicking to __i915_request_queue caller Since __i915_request_queue() may be called from hardirq (timer) context, we cannot use local_bh_disable/enable at the lower level. As we do want to kick the tasklet to speed up initial submission or preemption for normal client submission, lift it to the normal process context callpath. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190815042031.27750-1-chris@chris-wilson.co.uk A CI Bug Log filter associated to this bug has been updated:
{- APL BYT: igt@perf_pmu@busy-* - dmesg-warn- IRQs not enabled as expected -}
{+ APL BYT: igt@perf_pmu@busy-* - dmesg-warn- IRQs not enabled as expected +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_344/fi-byt-j1900/igt@perf_pmu@most-busy-idle-check-all-bcs0.html
A CI Bug Log filter associated to this bug has been updated:
{- BYT: igt@runner@aborted - fail - Previous test: perf_pmu ((busy-no-semaphores-vcs0)|(busy-idle-no-semaphores-vecs0)|(busy-hang-rcs0)) -}
{+ BYT: igt@runner@aborted - fail - Previous test: perf_pmu ((busy-no-semaphores-vcs0)|(busy-idle-no-semaphores-vecs0)|(busy-hang-rcs0)) +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_344/fi-byt-j1900/igt@runner@aborted.html
|
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.