==System Environment== -------------------------- Regression: Yes. Good commit on -next-queued: 648fb42d1e77cf90cddea2b1cf1f4ac4453e65e6 Non-working platforms: BSW ==kernel== -------------------------- origin/drm-intel-nightly: 7101d84020f63f1da7e0c5d021cdd6be4d515de5(fails) drm-intel-nightly: 2014y-09m-25d-15h-14m-02s UTC integration manifest origin/drm-intel-next-queued: 7ca5a41f4da201371e131fc0641033652f76bf30(fails) drm/i915: Avoid re-configure panel on every PSR re-enable. origin/drm-intel-fixes: c84db77010877da6c5da119868ed54c43d59e726(fails) drm/i915/hdmi: fix hdmi audio state readout ==Bug detailed description== ----------------------------- igt/gem_render_copy_redux/flink-interruptible causes system hang unable to get dmesg because system hang. ==Reproduce steps== ---------------------------- 1. ./gem_render_copy_redux --run-subtest flink-interruptible
*** This bug has been marked as a duplicate of bug 84207 ***
This bug still able to reproduce on BDW [root@x-bdw01 tests]# time ./gem_render_copy_redux --run-subtest flink-interruptible IGT-Version: 1.8-gf33fa71 (x86_64) (Linux: 3.17.0-rc7_drm-intel-fixes_91e564_20141006+ x86_64) Subtest flink-interruptible: SUCCESS (0.521s) ^C
The fix commit e9681366ea9e76ab8f75e84351f2f3ca63ee542c Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Sep 26 10:31:02 2014 +0100 drm/i915: Do not store the error pointer for a failed userptr registration is not in -fixes.
It's in drm-intel-next-fixes, queued for v3.18: http://mid.gmane.org/20140929132041.GP4109@phenom.ffwll.local
Verified on latest -nightly(ead7d71357628dc1231535886ec09853e9164d6d) root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./gem_render_copy_redux --run-subtest flink-interruptible IGT-Version: 1.8-gb7d80d1 (x86_64) (Linux: 3.17.0_drm-intel-nightly_ead7d7_20141013+ x86_64) Subtest flink-interruptible: SUCCESS (0.425s) real 0m0.730s user 0m0.074s sys 0m0.270s
Closing (>2 years) old Verified+Fixed.
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.