public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Akash Goel <akash.goel@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: failure for Support for sustained capturing of GuC firmware logs (rev9)
Date: Fri, 19 Aug 2016 09:01:31 -0000	[thread overview]
Message-ID: <20160819090131.22209.4967@emeril.freedesktop.org> (raw)
In-Reply-To: <1471596198-30748-1-git-send-email-akash.goel@intel.com>

== Series Details ==

Series: Support for sustained capturing of GuC firmware logs (rev9)
URL   : https://patchwork.freedesktop.org/series/7910/
State : failure

== Summary ==

Series 7910v9 Support for sustained capturing of GuC firmware logs
http://patchwork.freedesktop.org/api/1.0/series/7910/revisions/9/mbox

Test drv_module_reload_basic:
                pass       -> SKIP       (ro-skl3-i5-6260u)
Test gem_exec_suspend:
        Subgroup basic-s3:
                incomplete -> PASS       (fi-hsw-i7-4770k)
Test kms_cursor_legacy:
        Subgroup basic-cursor-vs-flip-varying-size:
                pass       -> FAIL       (ro-bdw-i5-5250u)
        Subgroup basic-flip-vs-cursor-legacy:
                fail       -> PASS       (ro-skl3-i5-6260u)
                fail       -> PASS       (ro-bdw-i5-5250u)
        Subgroup basic-flip-vs-cursor-varying-size:
                pass       -> FAIL       (ro-bdw-i5-5250u)
Test kms_pipe_crc_basic:
        Subgroup suspend-read-crc-pipe-a:
                skip       -> DMESG-WARN (ro-bdw-i7-5557U)
        Subgroup suspend-read-crc-pipe-b:
                pass       -> DMESG-WARN (ro-bdw-i7-5600u)
                dmesg-warn -> SKIP       (ro-bdw-i7-5557U)
                skip       -> DMESG-WARN (ro-bdw-i5-5250u)
        Subgroup suspend-read-crc-pipe-c:
                pass       -> DMESG-WARN (ro-bdw-i7-5600u)

fi-hsw-i7-4770k  total:244  pass:222  dwarn:0   dfail:0   fail:0   skip:22 
fi-kbl-qkkr      total:244  pass:186  dwarn:28  dfail:0   fail:3   skip:27 
fi-skl-i7-6700k  total:244  pass:208  dwarn:4   dfail:2   fail:2   skip:28 
fi-snb-i7-2600   total:244  pass:202  dwarn:0   dfail:0   fail:0   skip:42 
ro-bdw-i5-5250u  total:240  pass:218  dwarn:3   dfail:0   fail:2   skip:17 
ro-bdw-i7-5557U  total:240  pass:220  dwarn:2   dfail:0   fail:0   skip:18 
ro-bdw-i7-5600u  total:240  pass:204  dwarn:2   dfail:0   fail:2   skip:32 
ro-bsw-n3050     total:240  pass:194  dwarn:0   dfail:0   fail:4   skip:42 
ro-byt-n2820     total:240  pass:196  dwarn:0   dfail:0   fail:4   skip:40 
ro-hsw-i3-4010u  total:240  pass:213  dwarn:0   dfail:0   fail:1   skip:26 
ro-hsw-i7-4770r  total:240  pass:185  dwarn:0   dfail:0   fail:0   skip:55 
ro-ilk1-i5-650   total:235  pass:174  dwarn:0   dfail:0   fail:2   skip:59 
ro-ivb-i7-3770   total:240  pass:204  dwarn:0   dfail:0   fail:1   skip:35 
ro-ivb2-i7-3770  total:240  pass:208  dwarn:0   dfail:0   fail:1   skip:31 
ro-skl3-i5-6260u total:240  pass:222  dwarn:0   dfail:0   fail:3   skip:15 

Results at /archive/results/CI_IGT_test/RO_Patchwork_1938/

bf1752b drm-intel-nightly: 2016y-08m-19d-07h-51m-47s UTC integration manifest
52416c5 drm/i915: Mark the GuC log buffer flush interrupts handling WQ as freezable
9eaf155 drm/i915: Early creation of relay channel for capturing boot time logs
2c2c711 drm/i915: Use SSE4.1 movntdqa based memcpy for sampling GuC log buffer
5e6c954 drm/i915: Use uncached(WC) mapping for acessing the GuC log buffer
6b78dd5 drm/i915: Debugfs support for GuC logging control
0d1a5d0 drm/i915: Forcefully flush GuC log buffer on reset
d72520e drm/i915: Augment i915 error state to include the dump of GuC log buffer
9c4d368 drm/i915: Increase GuC log buffer size to reduce flush interrupts
1278064 drm/i915: Optimization to reduce the sampling time of GuC log buffer
1278d5a drm/i915: Add stats for GuC log buffer flush interrupts
940b84c drm/i915: New lock to serialize the Host2GuC actions
7f8984e drm/i915: Add a relay backed debugfs interface for capturing GuC logs
73a2867 relay: Use per CPU constructs for the relay channel buffer pointers
ad33b7c drm/i915: Handle log buffer flush interrupt event from GuC
9e09494 drm/i915: Support for GuC interrupts
018b214 drm/i915: Add low level set of routines for programming PM IER/IIR/IMR register set
fc17fad drm/i915: New structure to contain GuC logging related fields
ec6dd0f drm/i915: Add GuC ukernel logging related fields to fw interface file
d693aba drm/i915: Decouple GuC log setup from verbosity parameter

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

      parent reply	other threads:[~2016-08-19  9:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  8:42 [PATCH v8 00/19] Support for sustained capturing of GuC firmware logs akash.goel
2016-08-19  8:43 ` [PATCH 01/19] drm/i915: Decouple GuC log setup from verbosity parameter akash.goel
2016-08-19  8:43 ` [PATCH 02/19] drm/i915: Add GuC ukernel logging related fields to fw interface file akash.goel
2016-08-19  8:43 ` [PATCH 03/19] drm/i915: New structure to contain GuC logging related fields akash.goel
2016-08-19  8:43 ` [PATCH 04/19] drm/i915: Add low level set of routines for programming PM IER/IIR/IMR register set akash.goel
2016-08-19  8:43 ` [PATCH 05/19] drm/i915: Support for GuC interrupts akash.goel
2016-08-19  8:43 ` [PATCH 06/19] drm/i915: Handle log buffer flush interrupt event from GuC akash.goel
2016-08-19 10:08   ` Tvrtko Ursulin
2016-08-19  8:43 ` [PATCH 07/19] relay: Use per CPU constructs for the relay channel buffer pointers akash.goel
2016-08-19  8:43 ` [PATCH 08/19] drm/i915: Add a relay backed debugfs interface for capturing GuC logs akash.goel
2016-08-19 18:03   ` Chris Wilson
2016-08-20  6:40     ` Goel, Akash
2016-08-19  8:43 ` [PATCH 09/19] drm/i915: New lock to serialize the Host2GuC actions akash.goel
2016-08-19  8:43 ` [PATCH 10/19] drm/i915: Add stats for GuC log buffer flush interrupts akash.goel
2016-08-19  8:43 ` [PATCH 11/19] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 12/19] drm/i915: Increase GuC log buffer size to reduce flush interrupts akash.goel
2016-08-19  8:43 ` [PATCH 13/19] drm/i915: Augment i915 error state to include the dump of GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 14/19] drm/i915: Forcefully flush GuC log buffer on reset akash.goel
2016-08-19 18:10   ` Chris Wilson
2016-08-20  6:49     ` Goel, Akash
2016-08-19  8:43 ` [PATCH 15/19] drm/i915: Debugfs support for GuC logging control akash.goel
2016-08-19 18:18   ` Chris Wilson
2016-08-20  6:40     ` Goel, Akash
2016-08-19  8:43 ` [PATCH 16/19] drm/i915: Use uncached(WC) mapping for acessing the GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 17/19] drm/i915: Use SSE4.1 movntdqa based memcpy for sampling " akash.goel
2016-08-19 18:19   ` Chris Wilson
2016-08-20  6:44     ` Goel, Akash
2016-08-20  8:40       ` Chris Wilson
2016-08-19  8:43 ` [PATCH 18/19] drm/i915: Early creation of relay channel for capturing boot time logs akash.goel
2016-08-19  8:43 ` [PATCH 19/19] drm/i915: Mark the GuC log buffer flush interrupts handling WQ as freezable akash.goel
2016-08-19 10:19   ` Imre Deak
2016-08-19  9:01 ` Patchwork [this message]

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=20160819090131.22209.4967@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=akash.goel@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox