All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Saarinen, Jani" <jani.saarinen@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Srinivas, Vidya" <vidya.srinivas@intel.com>
Subject: Re: ✓ Fi.CI.BAT: success for Adding NV12 support (rev5)
Date: Mon, 15 Jan 2018 10:39:42 +0000	[thread overview]
Message-ID: <43D4F724E12AB6478FC1572B3FBE89D075D4BA17@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <20180115084707.16750.20972@emeril.freedesktop.org>

Hi. 
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
> Of Patchwork
> Sent: maanantai 15. tammikuuta 2018 10.47
> To: Srinivas, Vidya <vidya.srinivas@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for Adding NV12 support (rev5)
> 
> == Series Details ==
> 
> Series: Adding NV12 support (rev5)
> URL   : https://patchwork.freedesktop.org/series/28103/
> State : success
> 
> == Summary ==
> 
> Series 28103v5 Adding NV12 support
> https://patchwork.freedesktop.org/api/1.0/series/28103/revisions/5/mbox/
> 
> Test debugfs_test:
>         Subgroup read_all_entries:
>                 dmesg-warn -> DMESG-FAIL (fi-elk-e7500) fdo#103989 Test
> gem_ringfill:
>         Subgroup basic-default:
>                 skip       -> PASS       (fi-bsw-n3050)
> 
> fdo#103989 https://bugs.freedesktop.org/show_bug.cgi?id=103989
> 
> fi-bdw-5557u     total:288  pass:267  dwarn:0   dfail:0   fail:0   skip:21
> time:421s
> fi-bdw-gvtdvm    total:288  pass:264  dwarn:0   dfail:0   fail:0   skip:24
> time:428s
> fi-blb-e6850     total:288  pass:223  dwarn:1   dfail:0   fail:0   skip:64
> time:371s
> fi-bsw-n3050     total:288  pass:242  dwarn:0   dfail:0   fail:0   skip:46
> time:484s
> fi-bwr-2160      total:288  pass:183  dwarn:0   dfail:0   fail:0   skip:105
> time:280s
> fi-byt-j1900     total:288  pass:253  dwarn:0   dfail:0   fail:0   skip:35  time:468s
> fi-byt-n2820     total:288  pass:249  dwarn:0   dfail:0   fail:0   skip:39
> time:459s
> fi-elk-e7500     total:224  pass:168  dwarn:9   dfail:1   fail:0   skip:45
> fi-hsw-4770      total:288  pass:261  dwarn:0   dfail:0   fail:0   skip:27
> time:390s
> fi-hsw-4770r     total:288  pass:261  dwarn:0   dfail:0   fail:0   skip:27
> time:401s
> fi-ilk-650       total:288  pass:228  dwarn:0   dfail:0   fail:0   skip:60  time:417s
> fi-ivb-3520m     total:288  pass:259  dwarn:0   dfail:0   fail:0   skip:29
> time:449s
> fi-ivb-3770      total:288  pass:255  dwarn:0   dfail:0   fail:0   skip:33  time:412s
> fi-pnv-d510      total:288  pass:222  dwarn:1   dfail:0   fail:0   skip:65
> time:579s
> fi-snb-2520m     total:288  pass:248  dwarn:0   dfail:0   fail:0   skip:40
> time:522s
> fi-snb-2600      total:288  pass:248  dwarn:0   dfail:0   fail:0   skip:40
> time:397s
> fi-bxt-dsi failed to collect. IGT log at Patchwork_7664/fi-bxt-dsi/igt.log
> fi-bxt-j4205 failed to connect after reboot
> fi-cfl-s2 failed to collect. IGT log at Patchwork_7664/fi-cfl-s2/igt.log
> fi-gdg-551 failed to collect. IGT log at Patchwork_7664/fi-gdg-551/igt.log
> fi-glk-1 failed to collect. IGT log at Patchwork_7664/fi-glk-1/igt.log fi-glk-dsi
> failed to collect. IGT log at Patchwork_7664/fi-glk-dsi/igt.log fi-kbl-7500u
> failed to collect. IGT log at Patchwork_7664/fi-kbl-7500u/igt.log
> fi-kbl-7560u failed to collect. IGT log at Patchwork_7664/fi-kbl-7560u/igt.log
> fi-kbl-7567u failed to collect. IGT log at Patchwork_7664/fi-kbl-7567u/igt.log
> fi-kbl-r failed to collect. IGT log at Patchwork_7664/fi-kbl-r/igt.log fi-skl-
> 6260u failed to collect. IGT log at Patchwork_7664/fi-skl-6260u/igt.log
> fi-skl-6600u failed to collect. IGT log at Patchwork_7664/fi-skl-6600u/igt.log
> fi-skl-6700hq failed to collect. IGT log at Patchwork_7664/fi-skl-
> 6700hq/igt.log
> fi-skl-6700k2 failed to collect. IGT log at Patchwork_7664/fi-skl-
> 6700k2/igt.log
> fi-skl-6770hq failed to collect. IGT log at Patchwork_7664/fi-skl-
> 6770hq/igt.log
> fi-skl-gvtdvm failed to collect. IGT log at Patchwork_7664/fi-skl-
> gvtdvm/igt.log

I see this very alarming that all gen9+ systems eg. has issues booting up. 
This also now 2nd time in a row. So not really considering this as success.
 
> e96cbac0c1751d045065a49bf20ea134739e2dbb drm-tip: 2018y-01m-15d-
> 05h-55m-36s UTC integration manifest d19f9064681f drm/i915: Add NV12
> support to intel_framebuffer_init
> 420b315f2392 drm/i915: Add NV12 as supported format for sprite plane
> 4f54f455147b drm/i915: Add NV12 as supported format for primary plane
> e521e0b5b531 drm/i915: Upscale scaler max scale for NV12
> e8d508d50d81 drm/i915: Update format_is_yuv() to include NV12
> a449444b4453 drm/i915: Set scaler mode for NV12 2c6f947a9b2e
> drm/i915/skl: split skl_compute_ddb function
> 21c70676d051 drm/i915/skl+: nv12 workaround disable WM level 1-7
> 855807a0e29b drm/i915/skl+: make sure higher latency level has higher wm
> value
> f6c1e1570324 drm/i915/skl+: pass skl_wm_level struct to wm compute func
> e7d0a3539737 drm/i915/skl+: NV12 related changes for WM 411196b713cb
> drm/i915/skl+: support verification of DDB HW state for NV12
> d3531892bd0a drm/i915/skl+: add NV12 in skl_format_to_fourcc
> e1790b4eb0a4 drm/i915/skl+: refactor WM calculation for NV12
> 21ece85a2cb6 drm/i915/skl+: rename skl_wm_values struct to
> skl_ddb_values
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-
> tip/Patchwork_7664/issues.html


Jani Saarinen
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-01-15 10:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  3:18 [PATCH 00/15] Adding NV12 support Vidya Srinivas
2018-01-15  3:18 ` [PATCH 02/15] drm/i915/skl+: refactor WM calculation for NV12 Vidya Srinivas
2018-01-20  0:39   ` kbuild test robot
2018-01-15  3:18 ` [PATCH 05/15] drm/i915/skl+: NV12 related changes for WM Vidya Srinivas
2018-01-15  3:18 ` [PATCH 03/15] drm/i915/skl+: add NV12 in skl_format_to_fourcc Vidya Srinivas
2018-01-17 11:43   ` Mika Kahola
2018-01-15  3:18 ` [PATCH 01/15] drm/i915/skl+: rename skl_wm_values struct to skl_ddb_values Vidya Srinivas
2018-01-15  3:18 ` [PATCH 04/15] drm/i915/skl+: support verification of DDB HW state for NV12 Vidya Srinivas
2018-01-15  3:18 ` [PATCH 07/15] drm/i915/skl+: make sure higher latency level has higher wm value Vidya Srinivas
2018-01-15  3:18 ` [PATCH 08/15] drm/i915/skl+: nv12 workaround disable WM level 1-7 Vidya Srinivas
2018-01-15  3:18 ` [PATCH 09/15] drm/i915/skl: split skl_compute_ddb function Vidya Srinivas
2018-01-15  3:18 ` [PATCH 10/15] drm/i915: Set scaler mode for NV12 Vidya Srinivas
2018-01-15  3:18 ` [PATCH 06/15] drm/i915/skl+: pass skl_wm_level struct to wm compute func Vidya Srinivas
2018-01-15  3:18 ` [PATCH 12/15] drm/i915: Upscale scaler max scale for NV12 Vidya Srinivas
2018-01-15  3:18 ` [PATCH 13/15] drm/i915: Add NV12 as supported format for primary plane Vidya Srinivas
2018-01-15  3:18 ` [PATCH 11/15] drm/i915: Update format_is_yuv() to include NV12 Vidya Srinivas
2018-01-15  3:18 ` [PATCH 14/15] drm/i915: Add NV12 as supported format for sprite plane Vidya Srinivas
2018-01-15  3:18 ` [PATCH 15/15] drm/i915: Add NV12 support to intel_framebuffer_init Vidya Srinivas
2018-01-18 14:21   ` Maarten Lankhorst
2018-01-18 14:49     ` Maarten Lankhorst
2018-01-29 11:41   ` Maarten Lankhorst
2018-01-30  4:53     ` Srinivas, Vidya
2018-01-29 17:17   ` Maarten Lankhorst
2018-01-30  4:05     ` Srinivas, Vidya
2018-01-30  6:16       ` Kumar, Mahesh
2018-01-30  9:50         ` Maarten Lankhorst
2018-01-15  3:49 ` ✓ Fi.CI.BAT: success for Adding NV12 support (rev5) Patchwork
2018-01-15  4:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-01-15  8:47 ` ✓ Fi.CI.BAT: " Patchwork
2018-01-15 10:39   ` Saarinen, Jani [this message]
2018-01-15  9:44 ` ✓ Fi.CI.IGT: " Patchwork
2018-01-15 12:35 ` ✗ Fi.CI.BAT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43D4F724E12AB6478FC1572B3FBE89D075D4BA17@IRSMSX106.ger.corp.intel.com \
    --to=jani.saarinen@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vidya.srinivas@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.