All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915: Don't clflush before release phys object
Date: Thu, 08 Dec 2016 19:40:12 +0200	[thread overview]
Message-ID: <1481218812.29195.3.camel@intel.com> (raw)
In-Reply-To: <43D4F724E12AB6478FC1572B3FBE89D04C0A00B5@IRSMSX106.ger.corp.intel.com>

On Thu, 2016-12-08 at 19:22 +0200, Saarinen, Jani wrote:
> > == Series Details ==
> > 
> > Series: drm/i915: Don't clflush before release phys object
> > URL   : https://patchwork.freedesktop.org/series/16569/
> > State : warning
> > 
> > == Summary ==
> > 
> > Series 16569v1 drm/i915: Don't clflush before release phys object
> > https://patchwork.freedesktop.org/api/1.0/series/16569/revisions/1/mbox/
> > 
> > Test gem_exec_suspend:
> >         Subgroup basic-s3:
> >                 pass       -> DMESG-WARN (fi-skl-6700hq)
> 
> Imre: LSPCON again. 
> [  209.271053] sd 2:0:0:0: [sda] Starting disk
> [  209.629904] [drm:drm_lspcon_get_mode] *ERROR* LSPCON read(0x80, 0x41) failed
> [  209.629967] [drm:lspcon_wait_mode [i915]] *ERROR* Error reading LSPCON mode
> [  209.646906] [drm:drm_lspcon_get_mode] *ERROR* LSPCON read(0x80, 0x41) failed
> [  209.646968] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
> [  209.647058] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed

It's similar to previous cases with the difference that it recovers
after the next s/r. I'm working on a fix that does the detection/mode
change based on HPD, hopefully that will get rid of this.

> > fi-bdw-5557u     total:247  pass:233  dwarn:0   dfail:0   fail:0   skip:14
> > fi-bsw-n3050     total:247  pass:208  dwarn:0   dfail:0   fail:0   skip:39
> > fi-bxt-t5700     total:247  pass:220  dwarn:0   dfail:0   fail:0   skip:27
> > fi-byt-j1900     total:247  pass:220  dwarn:0   dfail:0   fail:0   skip:27
> > fi-byt-n2820     total:247  pass:216  dwarn:0   dfail:0   fail:0   skip:31
> > fi-hsw-4770      total:247  pass:228  dwarn:0   dfail:0   fail:0   skip:19
> > fi-hsw-4770r     total:247  pass:228  dwarn:0   dfail:0   fail:0   skip:19
> > fi-ilk-650       total:247  pass:195  dwarn:0   dfail:0   fail:0   skip:52
> > fi-ivb-3520m     total:247  pass:226  dwarn:0   dfail:0   fail:0   skip:21
> > fi-ivb-3770      total:247  pass:226  dwarn:0   dfail:0   fail:0   skip:21
> > fi-kbl-7500u     total:247  pass:226  dwarn:0   dfail:0   fail:0   skip:21
> > fi-skl-6260u     total:247  pass:234  dwarn:0   dfail:0   fail:0   skip:13
> > fi-skl-6700hq    total:247  pass:226  dwarn:1   dfail:0   fail:0   skip:20
> > fi-skl-6700k     total:247  pass:224  dwarn:3   dfail:0   fail:0   skip:20
> > fi-skl-6770hq    total:247  pass:234  dwarn:0   dfail:0   fail:0   skip:13
> > fi-snb-2520m     total:247  pass:216  dwarn:0   dfail:0   fail:0   skip:31
> > fi-snb-2600      total:247  pass:215  dwarn:0   dfail:0   fail:0   skip:32
> > 
> > 1117c18cdbf8312b696b79ae1846e1ebe99b8501 drm-tip: 2016y-12m-08d-16h-
> > 04m-38s UTC integration manifest
> > 72c4b20 drm/i915: Don't clflush before release phys object
> > 
> > == Logs ==
> > 
> > For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3241/
> 
> 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:[~2016-12-08 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 16:03 [PATCH] drm/i915: Don't clflush before release phys object Chris Wilson
2016-12-08 17:15 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-12-08 17:22   ` Saarinen, Jani
2016-12-08 17:40     ` Imre Deak [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=1481218812.29195.3.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@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.