public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: warning for SKL watermark algorithm updates (rev4)
Date: Tue, 31 May 2016 11:20:18 -0700	[thread overview]
Message-ID: <20160531182018.GC6628@intel.com> (raw)
In-Reply-To: <20160531173441.14199.54851@emeril.freedesktop.org>

On Tue, May 31, 2016 at 05:34:41PM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: SKL watermark algorithm updates (rev4)
> URL   : https://patchwork.freedesktop.org/series/7262/
> State : warning
> 
> == Summary ==
> 
> Series 7262v4 SKL watermark algorithm updates
> http://patchwork.freedesktop.org/api/1.0/series/7262/revisions/4/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)

Looks like the USB triggered a bug ("BUG: using smp_processor_id() in
preemptible"); not caused by the graphics driver.

I think Chris already wrote a patch to fix this anyway:
   https://patchwork.freedesktop.org/patch/90483/


> Test gem_close_race:
>         Subgroup basic-process:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_cpu_reloc:
>         Subgroup basic:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_ctx_exec:
>         Subgroup basic:
>                 pass       -> DMESG-WARN (ro-ivb2-i7-3770)

Same USB BUG().

> Test gem_exec_basic:
>         Subgroup gtt-default:
>                 dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>         Subgroup gtt-vebox:
>                 dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>         Subgroup readonly-bsd:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_exec_parallel:
>         Subgroup basic:
>                 pass       -> DMESG-WARN (fi-snb-i7-2600)

"*ERROR* Hangcheck timer elapsed... render ring idle"

There are a handful of bugzillas about similar issues on various
platforms; https://bugs.freedesktop.org/show_bug.cgi?id=75394 is
reported against SNB.


> Test gem_exec_store:
>         Subgroup basic-render:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_mmap_gtt:
>         Subgroup basic-write-gtt-no-prefault:
>                 dmesg-warn -> PASS       (ro-skl-i7-6700hq)
> Test gem_render_tiled_blits:
>         Subgroup basic:
>                 pass       -> DMESG-WARN (ro-ivb2-i7-3770)

USB BUG() again.

> Test gem_storedw_loop:
>         Subgroup basic-bsd:
>             pass       -> DMESG-WARN (ro-skl-i7-6700hq)

"Potential atomic update failure on pipe A."

https://bugs.freedesktop.org/show_bug.cgi?id=95632


> Test gem_tiled_fence_blits:
>         Subgroup basic:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> Test gem_tiled_pread_basic:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)

"Potential atomic update failure on pipe A."

https://bugs.freedesktop.org/show_bug.cgi?id=95632

> Test kms_addfb_basic:
>         Subgroup addfb25-modifier-no-flag:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup bad-pitch-0:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup bad-pitch-32:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup bad-pitch-65536:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup basic-y-tiled:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup framebuffer-vs-set-tiling:
>                 dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>         Subgroup small-bo:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)
>         Subgroup too-high:
>                 dmesg-warn -> PASS       (ro-skl-i7-6700hq)
>         Subgroup unused-pitches:
>                 pass       -> DMESG-WARN (ro-skl-i7-6700hq)

All of the DMESG-WARN's above are the

"Potential atomic update failure on pipe A."

https://bugs.freedesktop.org/show_bug.cgi?id=95632


> Test kms_force_connector_basic:
>         Subgroup force-connector-state:
>                 pass       -> DMESG-WARN (ro-ivb2-i7-3770)

USB BUG() again.


>         Subgroup force-edid:
>                 dmesg-warn -> PASS       (ro-ivb2-i7-3770)
> 
> fi-hsw-i7-4770r  total:209  pass:186  dwarn:0   dfail:0   fail:0   skip:23 
> fi-snb-i7-2600   total:209  pass:169  dwarn:1   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-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:169  dwarn:14  dfail:0   fail:0   skip:21 
> ro-snb-i7-2620M  total:102  pass:72   dwarn:0   dfail:0   fail:0   skip:29 
> fi-hsw-i7-4770k failed to connect after reboot
> ro-bdw-i7-5557U failed to connect after reboot
> ro-ilk-i7-620lm failed to connect after reboot

Not sure what caused these machines to fail reboot, but my patches are
SKL-only so I don't think they're the cause.  Maybe the BUG() that was
causing DMESG-WARN's on IVB hits these platforms as well, but completely
killed them?


Matt

> 
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1070/
> 
> 877a1d2 drm-intel-nightly: 2016y-05m-31d-14h-57m-44s UTC integration manifest
> 3398115 drm/i915/skl+: Use scaling amount for plane data rate calculation (v4)
> 16399f7 drm/i915/skl+: calculate plane pixel rate (v4)
> 5e43b98 drm/i915/skl+: calculate ddb minimum allocation (v6)
> e87756e drm/i915: Don't try to calculate relative data rates during hw readout
> 

-- 
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-05-31 18:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 22:51 [PATCH 0/4] SKL watermark algorithm updates Matt Roper
2016-05-16 22:51 ` [PATCH 1/4] drm/i915: Don't try to calculate relative data rates during hw readout Matt Roper
2016-05-16 22:51 ` [PATCH 2/4] drm/i915/skl+: calculate ddb minimum allocation (v4) Matt Roper
2016-05-26 22:13   ` [PATCH 2/4] drm/i915/skl+: calculate ddb minimum allocation (v5) Matt Roper
2016-05-30  5:05     ` Mahesh Kumar
2016-05-31 16:58       ` [PATCH 2/4] drm/i915/skl+: calculate ddb minimum allocation (v6) Matt Roper
2016-06-01 14:25         ` Mahesh Kumar
2016-06-01 14:40           ` Matt Roper
2016-05-16 22:52 ` [PATCH 3/4] drm/i915/skl+: calculate plane pixel rate (v4) Matt Roper
2016-05-30  5:28   ` Mahesh Kumar
2016-05-16 22:52 ` [PATCH 4/4] drm/i915/skl+: Use scaling amount for plane data rate calculation (v3) Matt Roper
2016-05-19 22:03   ` [PATCH 4/4] drm/i915/skl+: Use scaling amount for plane data rate calculation (v4) Matt Roper
2016-05-30  5:33     ` Mahesh Kumar
2016-05-17  5:51 ` ✗ Ro.CI.BAT: warning for SKL watermark algorithm updates Patchwork
2016-05-20  8:52 ` ✗ Ro.CI.BAT: warning for SKL watermark algorithm updates (rev2) Patchwork
2016-05-27  6:09 ` ✗ Ro.CI.BAT: warning for SKL watermark algorithm updates (rev3) Patchwork
2016-05-31 17:34 ` ✗ Ro.CI.BAT: warning for SKL watermark algorithm updates (rev4) Patchwork
2016-05-31 18:20   ` Matt Roper [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=20160531182018.GC6628@intel.com \
    --to=matthew.d.roper@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