Summary: | [BSW]igt/gem_workarounds/reset fails | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | lu hua <huax.lu> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | christophe.prigent, intel-gfx-bugs | ||||
Version: | unspecified | ||||||
Hardware: | All | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | SKL | i915 features: | GEM/Other | ||||
Attachments: |
|
Description
lu hua
2015-02-05 08:06:25 UTC
kernel commit: 2a579576e4c01799ec67264c9169e5adeadcc3ff ./gem_workarounds --run-subtest reset IGT-Version: 1.9-g9846e7f (x86_64) (Linux: 3.19.0_drm-intel-nightly_2a5795_20150212+ x86_64) (gem_workarounds:4792) WARNING: 0x0E4F0 0x01200120 0x00000120 0xFFFF0000 FAIL (gem_workarounds:4792) WARNING: 0x07300 0x08100810 0x00000810 0x00000000 FAIL (gem_workarounds:4792) WARNING: 0x07000 0x00040000 0x00000004 0x00000004 FAIL (gem_workarounds:4792) WARNING: 0x07004 0x00400040 0x00000040 0x00000180 FAIL (gem_workarounds:4792) WARNING: 0x07018 0x80008000 0x00008000 0x00000000 FAIL (gem_workarounds:4792) WARNING: 0x07008 0x02800200 0x00000280 0x00000000 FAIL (gem_workarounds:4792) CRITICAL: Test assertion failure function check_workarounds, file gem_workarounds.c:160: (gem_workarounds:4792) CRITICAL: Failed assertion: workaround_fail_count() == 0 Subtest reset: FAIL (0.003s) Created attachment 113389 [details]
dmesg
still happen on SKL-Y with the latest kernel : Kernel commit log: commit b4c4542ba1abfb0d3d6913504502573bf2c62b12 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Aug 28 15:51:30 2015 +0200 drm-intel-nightly: 2015y-08m-28d-13h-50m-34s UTC integration manifest Reproduced on BSW with 4.3.0-rc2-drm-intel-nightly+ Hardware: ========= Platform: Braswell M CPU : Intel(R) Celeron N3060 1.60GHz @ 1.6 GHz (family: 6, model: 76 stepping: 4) SoC : BSW D0 QDF : K6XC CRB : BRASWELL RVP Fab2 Mandatory Reworks : All Feature Reworks: F28, F32,F33 & F37 Optional reworks : O-01a Software : Linux distribution: Ubuntu 14.04 LTS 64 bits BIOS : BRAS.X64.B084.R00.1508310642 TXE FW : 2.0.0.2073 Ksc : 1.08 kernel 4.3.0-rc2-drm-intel-nightly+ commit 794e1cdfb84be003dbd287c69501c98ec280a89b Author: Jani Nikula <jani.nikula@intel.com> Date: Mon Sep 28 17:28:29 2015 +0300 drm-intel-nightly: 2015y-09m-28d-14h-28m-11s UTC integration manifest cairo: (HEAD, tag: 1.14.2) 93422b3cb5e0ef8104b8194c8873124ce2f5ea2d from git://git.freedesktop.org/git/cairo drm: (HEAD, tag: libdrm-2.4.64, tag: 2.4.64) ab2fadabde3829b1ec56bd4756165dd9bd281488 from git://git.freedesktop.org/git/mesa/drm intel-driver: (HEAD, origin/master, origin/HEAD, master) 2a72f99d24714f2a58f400ef63b913d4cf9080b3 from git://git.freedesktop.org/git/vaapi/intel-driver libva: (HEAD, tag: libva-1.6.1, origin/v1.6-branch) 613eb962b45fbbd1526d751e88e0d8897af6c0e0 from git://git.freedesktop.org/git/vaapi/libva mesa: (HEAD, tag: mesa-10.6.7) 32efdc87cbf89cfe08ad9571cd756e27c803caa8 from git://git.freedesktop.org/git/mesa/mesa xf86-video-intel: (HEAD, origin/master, origin/HEAD, master) f0fd4d500de03c30c7ce19915f85acadd1ca4e5d from git://git.freedesktop.org/git/xorg/driver/xf86-video-intel xserver: (HEAD, tag: xorg-server-1.17.2) 2123f7682d522619f101b05fb75efa75dabbe371 from git://git.freedesktop.org/git/xorg/xserver intel-gpu-tools: (HEAD, tag: intel-gpu-tools-1.12) 1f9e0550455be4b219954a026407dd23ec21b299 from git://git.freedesktop.org/git/xorg/app/intel-gpu-tools This test is passing on both BSW & SKL with kernel: commit 8f02d2103390e48e9e76c9e75d16dbb4396484c8 Author: Jani Nikula <jani.nikula@intel.com> Date: Mon Nov 28 14:38:48 2016 +0200 drm-tip: 2016y-11m-28d-12h-38m-14s UTC integration manifest intel-gpu-tools tag : intel-gpu-tools-1.16-164-g7797517 commit : 7797517 author : Chris Wilson <chris@chris-wilson.co.uk> age : 2 days ago comment : igt/kms_setmode: Skip unconnected connectors |
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.