public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kamble, Sagar A" <sagar.a.kamble@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: warning for series starting with [1/1] drm/i915: Never fully mask the the EI up rps interrupt on SNB/IVB
Date: Wed, 1 Jun 2016 13:42:34 +0530	[thread overview]
Message-ID: <574E98F2.6060700@intel.com> (raw)
In-Reply-To: <20160531110506.14194.51269@emeril.freedesktop.org>

These warnings are too not related to the patch.
Kindly push this patch.

On 5/31/2016 4:35 PM, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/1] drm/i915: Never fully mask the the EI up rps interrupt on SNB/IVB
> URL   : https://patchwork.freedesktop.org/series/7990/
> State : warning
>
> == Summary ==
>
> Series 7990v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/7990/revisions/1/mbox
>
> Test gem_busy:
>          Subgroup basic-parallel-render:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
>          Subgroup basic-render:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
> Test gem_close_race:
>          Subgroup basic-process:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
> Test gem_cs_tlb:
>          Subgroup basic-default:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
> Test gem_exec_basic:
>          Subgroup readonly-render:
>                  dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_exec_flush:
>          Subgroup basic-uc-prw-default:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>          Subgroup basic-uc-ro-default:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
> Test gem_exec_parallel:
>          Subgroup basic:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
> Test gem_exec_store:
>          Subgroup basic-all:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
>          Subgroup basic-blt:
>                  dmesg-warn -> PASS       (ro-ivb2-i7-3770)
>          Subgroup basic-default:
>                  dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_flink_basic:
>          Subgroup bad-flink:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
> Test gem_mmap_gtt:
>          Subgroup basic-short:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>          Subgroup basic-small-copy:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
> Test gem_storedw_loop:
>          Subgroup basic-bsd:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
> Test gem_tiled_pread_basic:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
> Test kms_addfb_basic:
>          Subgroup addfb25-framebuffer-vs-set-tiling:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup addfb25-x-tiled:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup addfb25-y-tiled-small:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup bad-pitch-1024:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup bad-pitch-63:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup basic-x-tiled:
>                  pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>          Subgroup too-high:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>          Subgroup too-wide:
>                  dmesg-warn -> PASS       (ro-skl-i7-6700hq)
> Test kms_force_connector_basic:
>          Subgroup force-edid:
>                  pass       -> DMESG-WARN (ro-ivb2-i7-3770)
>
> fi-bdw-i7-5557u  total:102  pass:93   dwarn:0   dfail:0   fail:0   skip:8
> fi-byt-n2820     total:209  pass:168  dwarn:0   dfail:0   fail:3   skip:38
> fi-hsw-i7-4770k  total:209  pass:190  dwarn:0   dfail:0   fail:0   skip:19
> fi-hsw-i7-4770r  total:209  pass:186  dwarn:0   dfail:0   fail:0   skip:23
> fi-skl-i7-6700k  total:209  pass:184  dwarn:0   dfail:0   fail:0   skip:25
> fi-snb-i7-2600   total:209  pass:170  dwarn:0   dfail:0   fail:0   skip:39
> ro-bdw-i5-5250u  total:102  pass:93   dwarn:0   dfail:0   fail:0   skip:8
> ro-bdw-i7-5600u  total:102  pass:75   dwarn:0   dfail:0   fail:0   skip:26
> ro-bsw-n3050     total:209  pass:168  dwarn:0   dfail:0   fail:2   skip:39
> ro-byt-n2820     total:209  pass:169  dwarn:0   dfail:0   fail:3   skip:37
> ro-hsw-i3-4010u  total:209  pass:186  dwarn:0   dfail:0   fail:0   skip:23
> ro-hsw-i7-4770r  total:102  pass:82   dwarn:0   dfail:0   fail:0   skip:19
> ro-ilk-i7-620lm  total:1    pass:0    dwarn:0   dfail:0   fail:0   skip:0
> ro-ilk1-i5-650   total:204  pass:146  dwarn:0   dfail:0   fail:1   skip:57
> ro-ivb-i7-3770   total:102  pass:75   dwarn:0   dfail:0   fail:0   skip:26
> ro-ivb2-i7-3770  total:102  pass:42   dwarn:37  dfail:0   fail:0   skip:22
> ro-skl-i7-6700hq total:204  pass:175  dwarn:8   dfail:0   fail:0   skip:21
> ro-snb-i7-2620M  total:102  pass:72   dwarn:0   dfail:0   fail:0   skip:29
> fi-bsw-n3050 failed to connect after reboot
> ro-bdw-i7-5557U failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1055/
>
> 031f2bb drm-intel-nightly: 2016y-05m-30d-17h-51m-33s UTC integration manifest
> 5779419 drm/i915: Never fully mask the the EI up rps interrupt on SNB/IVB
>

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

  reply	other threads:[~2016-06-01  8:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30  9:52 [PATCH 1/1] drm/i915: Update GEN6_PMINTRMSK setup with GuC submission Sagar Arun Kamble
2016-05-30 10:08 ` Chris Wilson
2016-05-30 11:21   ` [PATCH v2 1/1] drm/i915: Update GEN6_PMINTRMSK setup with GuC enabled Sagar Arun Kamble
2016-05-30 12:48     ` Chris Wilson
2016-05-30 18:46       ` [PATCH 1/2] SNB (and IVB too I suppose) starts to misbehave if the GPU gets stuck in an infinite batch buffer loop. The GPU apparently hogs something critical and CPUs start to lose interrupts and whatnot. We can keep the system limping along by unmasking some interrupts in GEN6_PMINTRMSK. The EI up interrupt has been previously chosen for that task, so let's never mask it Sagar Arun Kamble
2016-05-30 18:46         ` [PATCH v3 1/1] drm/i915: Update GEN6_PMINTRMSK setup with GuC enabled Sagar Arun Kamble
2016-05-30 20:18           ` Chris Wilson
2016-05-31  5:24             ` Kamble, Sagar A
2016-05-31  8:28               ` [PATCH v4 " Sagar Arun Kamble
2016-05-31  8:51                 ` Chris Wilson
2016-05-31 23:18                   ` Matt Roper
2016-06-01  6:54                     ` Chris Wilson
2016-06-01  8:14                       ` Kamble, Sagar A
2016-06-01 14:29                       ` Matt Roper
2016-06-02 12:12                         ` Kamble, Sagar A
2016-06-02 12:59                           ` Chris Wilson
2016-05-30 18:55         ` [PATCH 1/1] drm/i915: Never fully mask the the EI up rps interrupt on SNB/IVB Sagar Arun Kamble
2016-05-31 11:05         ` ✗ Ro.CI.BAT: warning for series starting with [1/1] " Patchwork
2016-06-01  8:12           ` Kamble, Sagar A [this message]
2016-05-31 11:38 ` ✗ Ro.CI.BAT: warning for series starting with [v4,1/1] drm/i915: Update GEN6_PMINTRMSK setup with GuC enabled (rev5) Patchwork
2016-05-31 15:15   ` Kamble, Sagar A

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=574E98F2.6060700@intel.com \
    --to=sagar.a.kamble@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