From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [PATCH 9/9] drm/i915: Attach a PSR property on eDP
Date: 16 Apr 2015 11:44:04 -0700 [thread overview]
Message-ID: <acb6cf$l5eukg@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1429141956-2338-10-git-send-email-rodrigo.vivi@intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6209
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 276/276 276/276
ILK 302/302 302/302
SNB 318/318 318/318
IVB 341/341 341/341
BYT -2 287/287 285/287
HSW -1 395/395 394/395
BDW -1 318/318 317/318
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
BYT igt@kms_setmode@clone-exclusive-crtc DMESG_WARN(1)PASS(2) DMESG_WARN(2)
(dmesg patch applied)drm:check_crtc_state[i915]]*ERROR*mismatch_in_has_infoframe(expected#,found#)@mismatch in has_infoframe .* found
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#check_crtc_state[i915]()@WARNING:.* at .* check_crtc_state+0x
BYT igt@kms_setmode@clone-single-crtc DMESG_WARN(1)PASS(2) DMESG_WARN(2)
(dmesg patch applied)drm:check_crtc_state[i915]]*ERROR*mismatch_in_has_infoframe(expected#,found#)@mismatch in has_infoframe .* found
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#check_crtc_state[i915]()@WARNING:.* at .* check_crtc_state+0x
*HSW igt@gem_caching@writes PASS(2) DMESG_WARN(1)PASS(1)
(dmesg patch applied)drm:i915_hangcheck_elapsed[i915]]*ERROR*Hangcheck_timer_elapsed...blitter_ring_idle@Hangcheck timer elapsed... blitter ring idle
*BDW igt@gem_userptr_blits@forked-sync-multifd-mempressure-normal PASS(2) TIMEOUT(1)PASS(1)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-04-16 18:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 23:52 [PATCH 0/9] drm-intel-collector - update Rodrigo Vivi
2015-04-15 23:52 ` [PATCH 1/9] drm/i915: Remove pinned check from madvise_ioctl Rodrigo Vivi
2015-04-15 23:52 ` [PATCH 2/9] drm/i915/vlv: check port in infoframe_enabled v2 Rodrigo Vivi
2015-04-16 9:10 ` Daniel Vetter
2015-04-15 23:52 ` [PATCH 3/9] drm/i915: vlv: fix save/restore of GFX_MAX_REQ_COUNT reg Rodrigo Vivi
2015-04-16 6:45 ` Imre Deak
2015-04-16 9:08 ` Daniel Vetter
2015-04-23 21:27 ` Jani Nikula
2015-04-15 23:52 ` [PATCH 4/9] drm/i915: Remove unused head member in request struct Rodrigo Vivi
2015-04-15 23:59 ` Vivi, Rodrigo
2015-04-16 7:35 ` Chris Wilson
2015-04-15 23:52 ` [PATCH 5/9] drm/i915: Remove unneeded check on execlist ringbuf alloc Rodrigo Vivi
2015-04-16 0:00 ` Vivi, Rodrigo
2015-04-15 23:52 ` [PATCH 6/9] drm/i915: Support for higher DSI clk Rodrigo Vivi
2015-04-15 23:52 ` [PATCH 7/9] drm/i915: Changes required to enable DSI Video Mode on CHT Rodrigo Vivi
2015-04-15 23:52 ` [PATCH 8/9] drm/i915: Remove duplicated intel_fbc_update calls Rodrigo Vivi
2015-04-15 23:52 ` [PATCH 9/9] drm/i915: Attach a PSR property on eDP Rodrigo Vivi
2015-04-16 18:44 ` shuang.he [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='acb6cf$l5eukg@fmsmga002.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox