Created attachment 121991 [details] dmesg.log ==Regresion== -------------------------------------------------- I'm not sure, i think that this is a new test case ==Description== -------------------------------------------------- gem_softpin/evict-active never ends ==Attachments== -------------------------------------------------- dmesg.log ==Steps to reproduce== -------------------------------------------------- run the following test ./gem_softpin --run-subtest evict-active ==Actual results== -------------------------------------------------- gem_softpin/evict-active never ends ==Expected results== -------------------------------------------------- the test must be run and finish without any issues ==Hardware configuration== -------------------------------------------------- Kernel version : 4.5.0-rc5-nightly+ Linux distribution : Ubuntu 15.10 Architecture : 64-bit Mesa version : 11.1.1 (git-330aa44 xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.1 DRM version : 2.4.66 VAAPI version : Intel i965 driver for Intel(R) Broxton - 1.6.3.pre1 (1.6.1-92-gf6fe842) Cairo version : 1.15.2 Bios revision : 119.10 KSC revision : 1.6 Motherboard model : Broxton P Motherboard type : NOTEBOOK Hand Held Motherboard manufacturer : Intel Corp. CPU family : Other CPU information : 06/5c GPU Card : Intel Corporation Device 5a84 (rev 03) (prog-if 00 [VGA controller]) IGT 1.13 ========= Commit : babcf40f29d9e9cce5d0739b1784eb94fe91bd26 kernel ======= commit 1a139ead792d8e912aa13d413b9cf59811fde676 Author: Jani Nikula <jani.nikula@intel.com> Date: Mon Feb 22 10:48:46 2016 +0200 drm-intel-nightly: 2016y-02m-22d-08h-48m-06s UTC integration manifest
Do you not have hard-lockup and soft-lockup detection enabled in your CI kernel builds?
commit 172ae5b4c8c104af56804bf2406014849ed6fa37 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Dec 5 14:29:37 2016 +0000 drm/i915: Fix i915_gem_evict_for_vma (soft-pinning)
Closing as re-test on QA side confirmed it is pass
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.