From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Patchwork <patchwork@emeril.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: CTS fixes (rev2)
Date: Thu, 20 Jun 2019 16:46:45 +0300 [thread overview]
Message-ID: <4a5099cc-ea7a-0a75-b049-820096182a1a@intel.com> (raw)
In-Reply-To: <156103809546.664.6288483732297885747@skylake-alporthouse-com>
On 20/06/2019 16:41, Chris Wilson wrote:
> Quoting Patchwork (2019-06-20 14:35:27)
>> == Series Details ==
>>
>> Series: drm/i915: CTS fixes (rev2)
>> URL : https://patchwork.freedesktop.org/series/62437/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_6312 -> Patchwork_13362
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
> They all complain about:
>
> <3> [403.297791] rcs0: Unable to write to whitelisted register 2348
> [PS_INVOCATION_COUNT]
>
> Is the complaint valid?
> -Chris
>
Documentation says the register should be R/W...
I don't think we ever write it in Mesa so I can't really tell.
-Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-20 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:27 [PATCH v2 0/2] drm/i915: CTS fixes Lionel Landwerlin
2019-06-20 9:27 ` [PATCH v2 1/2] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT Lionel Landwerlin
2019-06-20 9:27 ` [PATCH v2 2/2] drm/i915/icl: " Lionel Landwerlin
2019-06-20 17:56 ` Anuj Phogat
2019-06-20 9:56 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev2) Patchwork
2019-06-20 13:35 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-20 13:41 ` Chris Wilson
2019-06-20 13:46 ` Lionel Landwerlin [this message]
2019-06-21 22:48 ` Chris Wilson
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=4a5099cc-ea7a-0a75-b049-820096182a1a@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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.