Created attachment 118764 [details] hsw-kern.log.bz2 HSW-ULT (STP Fab3) Hardware Platform: Shark Bay ULT CPU : Intel® Core ™ i7-4550 @ 1.5GHz (family: 6, model: 69, stepping: 1) SoC: Haswell ULT 2+3 C3 Chipset PCH: LynxPoint B1 CRB: SawTooth Peak Fab3 Reworks : F06 (Audio), F10 (DevSleep), F22 (NFC) Software Linux distribution: Ubuntu 14.04 LTS 64 bits BDW-U (WTM1 Fab3) Hardware Platform: Crescent Bay ULT CPU: Intel® Core™ i5 5300-U @ 2.30 GHz (family: 6, model: 61 stepping: 4 ) SoC : Broadwell U 2+2 F0 Chipset PCH: Wildcat Point B2 CRB: White Tip Mountain 1 Fab3 Software BIOS : BDW-E1R1.86C.0114.R00.1502042131 ME FW : 10.0.38.1000 Ksc : 1.18 Linux kernel drm-intel-nightly 4.3.0-rc4 3f7a6e1 from anongit.freedesktop.org/drm-intel commit 3f7a6e15f853963cba68fcde99fb5d2bea057d65 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Tue Oct 6 15:03:42 2015 +0200 drm-intel-nightly: 2015y-10m-06d-13h-03m-02s UTC integration manifest Reproduced with: Linux kernel drm-intel-nightly 4.3.0-rc4 9e89df3 from anongit.freedesktop.org/drm-intel commit 9e89df3714be34218fd1af734ed34f944ba0f304 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Wed Oct 7 16:39:03 2015 +0200 drm-intel-nightly: 2015y-10m-07d-14h-38m-18s UTC integration manifest Steps: ------- Execute command: ./kms_pipe_crc_basic Actual result: --------------- Test result is fail for 12 subcases: igt@kms_pipe_crc_basic@hang-read-crc-pipe-a Fail igt@kms_pipe_crc_basic@hang-read-crc-pipe-b Fail igt@kms_pipe_crc_basic@hang-read-crc-pipe-c Fail igt@kms_pipe_crc_basic@read-crc-pipe-a Fail igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence Fail igt@kms_pipe_crc_basic@read-crc-pipe-b Fail igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence Fail igt@kms_pipe_crc_basic@read-crc-pipe-c Fail igt@kms_pipe_crc_basic@read-crc-pipe-c-frame-sequence Fail igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a Fail igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b Fail igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c Fail Expected result: ---------------- Tests are Pass Info: ----- From result.json: "igt@kms_pipe_crc_basic@hang-read-crc-pipe-a": { "environment": "PIGLIT_SOURCE_DIR=\"/usr/local/src/piglit\" PIGLIT_PLATFORM=\"mixed_glx_egl\"", "exception": null, "returncode": 99, "command": "/usr/local/src/intel-gpu-tools/tests/kms_pipe_crc_basic --run-subtest hang-read-crc-pipe-A", "result": "fail", "err": "Subtest hang-read-crc-pipe-A failed.\n**** DEBUG ****\nTest requirement passed: !(pipe >= data->display.n_pipes)\nhang-read-crc-pipe-A: Testing connector DP-1 using pipe A\ndisplay: DP-1: set_pipe(A)\nClearing the fb with color (0.00,1.00,0.00)\nigt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258 [bpp=32], tiling=0x0, size=0\nigt_create_fb_with_bo_size(handle=1, pitch=4096)\ndisplay: A.0: plane_set_fb(36)\ndisplay: commit {\ndisplay: DP-1: Selecting pipe A\ndisplay: DP-1: SetCrtc pipe A, fb 36, panning (0, 0), mode 1024x768\ndisplay: }\nCRC for this fb: a7eebc96 00000000 00000000 00000000 00000000\ndisplay: A.0: plane_set_fb(0)\ndisplay: DP-1: set_pipe(any)\ndisplay: DP-1: set_pipe(A)\nClearing the fb with color (0.00,1.00,1.00)\nigt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258 [bpp=32], tiling=0x0, size=0\nigt_create_fb_with_bo_size(handle=1, pitch=4096)\ndisplay: A.0: plane_set_fb(36)\ndisplay: commit {\ndisplay: }\nTimed out: CRC reading\n**** END ****\n", "time": 27.3630850315094, "subtests": { "__type__": "Subtests" }, "__type__": "TestResult", "out": "IGT-Version: 1.12-NOT-GIT (x86_64) (Linux: 3.17.3 x86_64)\nhang-read-crc-pipe-A: Testing connector DP-1 using pipe A\nTimed out: CRC reading\nSubtest hang-read-crc-pipe-A: FAIL (11.549s)\n" },
Created attachment 118765 [details] hsw-results.json.bz2
Created attachment 118766 [details] BDW-kern.log.bz2
Created attachment 118767 [details] BDW-results.json.bz2
Bug scrub: Kimmo, can someone have a look to it?
We found an error in the test procedure. Not reproduced with kernel drm-intel-nightly 7c5adfc1da122fb3cf8fae4b7b638e85ec6ddbae anongit.freedesktop.org/drm-intel
So closed as invalid
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.