All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915: Make __i915_printk debug output behave the same as DRM_DEBUG_DRIVER
Date: Tue, 22 Mar 2016 15:19:29 +0200	[thread overview]
Message-ID: <1458652769.20080.34.camel@intel.com> (raw)
In-Reply-To: <20160322080434.12404.58651@emeril.freedesktop.org>

On ti, 2016-03-22 at 08:04 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Make __i915_printk debug output behave the same as
> DRM_DEBUG_DRIVER
> URL   : https://patchwork.freedesktop.org/series/4713/
> State : warning
> 
> == Summary ==
> 
> Series 4713v1 drm/i915: Make __i915_printk debug output behave the
> same as DRM_DEBUG_DRIVER
> http://patchwork.freedesktop.org/api/1.0/series/4713/revisions/1/mbox
> /
> 
> Test gem_exec_suspend:
>         Subgroup basic-s3:
>                 pass       -> DMESG-WARN (bsw-nuc-2)

Unrelated, lockdep issue among ggtt_bind_vma/stop_machine, mmap,
kernfs_fop_write, device_unregister:
https://bugs.freedesktop.org/show_bug.cgi?id=94350

> Test kms_flip:
>         Subgroup basic-flip-vs-wf_vblank:
>                 pass       -> FAIL       (ilk-hp8440p) UNSTABLE

Unrelated, 1 frame long inter-vblank ts jitter with seq_step=10:
https://bugs.freedesktop.org/show_bug.cgi?id=94294

>         Subgroup basic-plain-flip:
>                 pass       -> DMESG-WARN (hsw-brixbox)

Unrelated, watermark programming while device off, should be fixed now
in -nightly.

>                 dmesg-warn -> PASS       (bdw-ultra)
> Test kms_force_connector_basic:
>         Subgroup prune-stale-modes:
>                 pass       -> SKIP       (ivb-t430s)
> Test kms_pipe_crc_basic:
>         Subgroup suspend-read-crc-pipe-c:
>                 dmesg-warn -> PASS       (bsw-nuc-2)
> Test pm_rpm:
>         Subgroup basic-pci-d3-state:
>                 fail       -> DMESG-FAIL (snb-x220t)
>                 pass       -> DMESG-WARN (snb-dellxps)

Both of the above, the same watermark programming problem as above.

>                 pass       -> DMESG-WARN (bsw-nuc-2)

Unrelated, unclaimed access prior to suspending, pm_rpm@basic-pci-d3-st
ate:
https://bugs.freedesktop.org/show_bug.cgi?id=94164

>         Subgroup basic-rte:
>                 dmesg-warn -> PASS       (snb-x220t)
>                 dmesg-warn -> PASS       (byt-nuc) UNSTABLE

Not on the above list, I don't know why:
- igt@kms_flip@basic-flip-vs-dpms: FIFO underrun on ilk-hp8440p:
Unrelated, https://bugs.freedesktop.org/show_bug.cgi?id=93787

I pushed the patch to -dinq, thanks for the review.

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

  reply	other threads:[~2016-03-22 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 15:08 [PATCH] drm/i915: Make __i915_printk debug output behave the same as DRM_DEBUG_DRIVER Imre Deak
2016-03-22  8:04 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-03-22 13:19   ` Imre Deak [this message]
2016-03-22  9:42 ` [PATCH] " Chris Wilson
2016-03-22 10:22   ` Imre Deak

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=1458652769.20080.34.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.