public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
	intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: Re: [PATCH 2/2] drm: WARN if drm_handle_vblank is called errornously
Date: 22 Feb 2015 18:26:41 -0800	[thread overview]
Message-ID: <6c3329$kh9530@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1424614280-29571-2-git-send-email-daniel.vetter@ffwll.ch>

Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5807
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
PNV                 -3              277/277              274/277
ILK                                  313/313              313/313
SNB                 -23              309/309              286/309
IVB                                  382/382              382/382
BYT                                  296/296              296/296
HSW                 -1              425/425              424/425
BDW                 -1              318/318              317/318
-------------------------------------Detailed-------------------------------------
Platform  Test                                drm-intel-nightly          Series Applied
 PNV  igt_gem_userptr_blits_coherency-sync      NO_RESULT(1)CRASH(8)NRUN(1)PASS(8)      CRASH(2)
 PNV  igt_gem_userptr_blits_coherency-unsync      CRASH(5)NRUN(1)PASS(6)      CRASH(1)PASS(1)
*PNV  igt_gem_userptr_blits_forked-access      PASS(3)      FAIL(1)PASS(1)
*SNB  igt_gem_fence_thrash_bo-copy      PASS(2)      DMESG_WARN(1)PASS(1)
 SNB  igt_kms_pipe_crc_basic_read-crc-pipe-A      DMESG_WARN(1)PASS(2)      DMESG_WARN(2)
 SNB  igt_kms_pipe_crc_basic_read-crc-pipe-A-frame-sequence      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_pipe_crc_basic_read-crc-pipe-B      DMESG_WARN(1)PASS(2)      DMESG_WARN(2)
 SNB  igt_kms_pipe_crc_basic_read-crc-pipe-B-frame-sequence      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-bottom-right-pipe-A-plane-1      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-bottom-right-pipe-A-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-bottom-right-pipe-B-plane-1      DMESG_WARN(1)PASS(2)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-bottom-right-pipe-B-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-top-left-pipe-A-plane-1      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-top-left-pipe-A-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-top-left-pipe-B-plane-1      DMESG_WARN(1)PASS(2)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-panning-top-left-pipe-B-plane-2      DMESG_WARN(1)PASS(17)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-covered-pipe-A-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-covered-pipe-B-plane-1      DMESG_WARN(1)PASS(2)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-covered-pipe-B-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-hole-pipe-A-plane-1      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-hole-pipe-A-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-hole-pipe-B-plane-1      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_kms_plane_plane-position-hole-pipe-B-plane-2      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_pm_rpm_debugfs-forcewake-user      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_pm_rpm_gem-idle      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 SNB  igt_pm_rpm_reg-read-ioctl      DMESG_WARN(1)PASS(1)      DMESG_WARN(2)
 HSW  igt_kms_flip_plain-flip-fb-recreate      TIMEOUT(4)PASS(3)      TIMEOUT(1)PASS(1)
*BDW  igt_gem_gtt_hog      PASS(23)      DMESG_WARN(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

  reply	other threads:[~2015-02-23  2:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 20:03 [PATCH 1/5] drm/irq: Add drm_crtc_vblank_reset Daniel Vetter
2015-02-13 20:03 ` [PATCH 2/5] drm/i915: Drop pipe_enable checks in vblank funcs Daniel Vetter
2015-02-13 20:03 ` [PATCH 3/5] drm/i915: Flatten DRIVER_MODESET checks in i915_irq.c Daniel Vetter
2015-02-13 20:03 ` [PATCH 4/5] drm/i915: Switch to drm_crtc variants of vblank functions Daniel Vetter
2015-02-13 20:03 ` [PATCH 5/5] drm/irq: Don't call ->get_vblank_counter directly from irq_uninstall/cleanup Daniel Vetter
2015-02-14  9:38   ` shuang.he
2015-02-17 13:42   ` Imre Deak
2015-02-22 11:17   ` [PATCH] " Daniel Vetter
2015-02-23  0:20     ` shuang.he
2015-02-22 14:11   ` [PATCH 1/2] " Daniel Vetter
2015-02-22 14:11     ` [PATCH 2/2] drm: WARN if drm_handle_vblank is called errornously Daniel Vetter
2015-02-23  2:26       ` shuang.he [this message]
2015-02-23  9:52       ` Daniel Vetter
2015-02-15 14:08 ` [PATCH 1/5] drm/irq: Add drm_crtc_vblank_reset Laurent Pinchart
2015-02-23  9:54   ` Daniel Vetter

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='6c3329$kh9530@orsmga002.jf.intel.com' \
    --to=shuang.he@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=ethan.gao@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