Summary: | [KBL] igt/gem_userptr_blits/sync-unmap is fail | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Olivier Berthier <olivierx.berthier> | ||||
Component: | DRM/Intel | Assignee: | Olivier Berthier <olivierx.berthier> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | DRI git | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | KBL | i915 features: | |||||
Attachments: |
|
Description
Olivier Berthier
2016-02-12 16:18:36 UTC
commit ca3d355846c0b9746d2d6892bd0a4c1413b2abab Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Feb 12 16:38:04 2016 +0000 igt/gem_userptr_blits: Flip sign on error check Following conversion to __gem_execbuf() we need to consider that it returns -errno when checking the result. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94117 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Assigned to Olivier to check Last version of IGT should fix it: https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/?id=ca3d355846c0b9746d2d6892bd0a4c1413b2abab Confirmed: Test is successful with following configuration: Linux distribution: Ubuntu 15.10 64 bits Kernel drm-intel-nightly 4.5.0-rc5_1a139ea from http://cgit.freedesktop.org/drm-intel/ 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 drm: tag libdrm-2.4.66 9b77443 from http://cgit.freedesktop.org/mesa/drm/ mesa: tag mesa-11.1.1 330aa44from http://cgit.freedesktop.org/mesa/mesa/ cairo: tag 1.15.2 db8a7f1 from http://cgit.freedesktop.org/cairo waffle: master bb29b2a from https://github.com/waffle-gl/waffle xorg-server-macros: master d7acec2 from git://git.freedesktop.org/git/xorg/util/macros libva: tag libva-1.6.1 1f026de from http://cgit.freedesktop.org/libva/ vaapi-intel-driver: tag 1.6.1 f6fe842 from http://cgit.freedesktop.org/vaapi/intel-driverFirmware Firmware (APL)DMC 1.06 from https://01.org/linuxgraphics/downloads/broxton-dmc-1.06 Output Aperture size is 268435456 MiB Total RAM is 7 824 MiB Not enough RAM to run test, reducing buffer count. Testing unsynchronized mappings... Testing synchronized mappings... Subtest sync-unmap: SUCCESS (0.005s) Still Pass with 4.7.0 #6f87e85 So closed Platform: KABY LAKE-U CPU : Intel(R) Core(TM) @ 2.60GHz MCP : KBL-U G0 2+2 QDF : QYQ8 Chipset PCH: SPT-LP C1 CRB : KABY LAKE U DDR3L RVP7 CRB FAB1 Software BIOS: 38_07 KBLSE2R1.R00.X038.P07.1606200632 from https://ubit-artifactory-ba.intel.com/artifactory/simple/one-windows-local/Submissions/ifwi/KBL_PURPLE_IFWI_2016_WW26_1_00_HR'16/IFWI-KBL_PURPLE_IFWI_2016_WW26_1_00_HR'16-R.7z ME FW: 11.5.0.1058 EC FW: 1.19 Ksc (EC FW): 1.20 Linux distribution: Ubuntu 16.04 64 bits Kernel: 4.7.0 6f87e85 from http://cgit.freedesktop.org/drm-intel/ commit 6f87e85fa302ffdb4cb9f4cd712691165923c7a2 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Aug 1 15:53:41 2016 +0100 drm-intel-nightly: 2016y-08m-01d-14h-53m-17s UTC integration manifest drm: libdrm-2.4.70 f19cd3a from git://anongit.freedesktop.org/mesa/drm mesa: mesa-11.2.2 3a9f628from git://anongit.freedesktop.org/mesa/mesa cairo: 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo xserver: xorg-server-1.18.0-502 c833c08 from git://git.freedesktop.org/git/xorg/xserver xf86-video-intel: 2.99.917-688 49daf5d from git://git.freedesktop.org/git/xorg/driver/xf86-video-intel libva: libva-1.7.0-40 f7e2263 from git://git.freedesktop.org/git/vaapi/libva vaapi-intel-driver: 1.7.0-64 1cd6795 from git://git.freedesktop.org/git/vaapi/intel-driverGuC 9.14 from http://rdvivi-hillsboro.jf.intel.com/firmware/kbl_guc_ver9_14.tar.bz2 DMC 1.01 from: https://01.org/linuxgraphics/downloads/kabylake-dmc-1.01 Intel-Gpu-Tools 1.15-188 53b4dfdfrom http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git |
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.