On Thu, Jan 14, 2016 at 02:20:40PM -0000, Patchwork wrote: > == Summary == > > Built on 8fb2feecca499d11e104264071ac55e273e23af5 drm-intel-nightly: 2016y-01m-14d-13h-06m-44s UTC integration manifest > > Test gem_basic: > Subgroup create-close: > pass -> DMESG-WARN (skl-i7k-2) > Test gem_cpu_reloc: > Subgroup basic: > pass -> DMESG-FAIL (skl-i7k-2) > Test gem_ctx_param_basic: > Subgroup basic: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup invalid-param-set: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup non-root-set-no-zeromap: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup root-set-no-zeromap-disabled: > pass -> DMESG-WARN (skl-i7k-2) > Test gem_mmap: > Subgroup basic: > pass -> DMESG-WARN (skl-i7k-2) > Test gem_mmap_gtt: > Subgroup basic-read: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup basic-write: > pass -> DMESG-WARN (skl-i7k-2) > Test gem_storedw_loop: > Subgroup basic-render: > dmesg-warn -> PASS (skl-i5k-2) UNSTABLE > dmesg-warn -> PASS (bdw-nuci7) > dmesg-warn -> PASS (skl-i7k-2) UNSTABLE > Test kms_addfb_basic: > Subgroup addfb25-modifier-no-flag: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup addfb25-x-tiled-mismatch: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup addfb25-yf-tiled: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup bad-pitch-1024: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup bad-pitch-63: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup bad-pitch-999: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup clobberred-modifier: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup too-high: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup too-wide: > pass -> DMESG-WARN (skl-i7k-2) > Subgroup unused-offsets: > pass -> DMESG-WARN (skl-i7k-2) > Test kms_flip: > Subgroup basic-plain-flip: > pass -> DMESG-FAIL (skl-i7k-2) > Test kms_pipe_crc_basic: > Subgroup nonblocking-crc-pipe-a-frame-sequence: > pass -> DMESG-FAIL (skl-i7k-2) > Subgroup read-crc-pipe-b-frame-sequence: > pass -> DMESG-FAIL (skl-i7k-2) > Test prime_self_import: > Subgroup basic-with_two_bos: > pass -> DMESG-WARN (skl-i7k-2) Looks like the GPU died or something on that skl. Can't imagine it being related to watermark patches. Unfortunately these didn't cure the recent underrun regressions from the ilk-ivb machines. So seems like there's something more busted somewhere. > > bdw-nuci7 total:138 pass:129 dwarn:0 dfail:0 fail:0 skip:9 > bdw-ultra total:138 pass:131 dwarn:1 dfail:0 fail:0 skip:6 > bsw-nuc-2 total:141 pass:115 dwarn:2 dfail:0 fail:0 skip:24 > hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7 > hsw-gt2 total:141 pass:137 dwarn:0 dfail:0 fail:0 skip:4 > ilk-hp8440p total:141 pass:101 dwarn:3 dfail:0 fail:0 skip:37 > ivb-t430s total:135 pass:122 dwarn:3 dfail:4 fail:0 skip:6 > skl-i5k-2 total:141 pass:132 dwarn:1 dfail:0 fail:0 skip:8 > skl-i7k-2 total:141 pass:108 dwarn:20 dfail:4 fail:0 skip:8 > snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14 > snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13 > > Results at /archive/results/CI_IGT_test/Patchwork_1187/ -- Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
