All of lore.kernel.org
 help / color / mirror / Atom feed
From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
	intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: Re: [PATCH 11/11] drm: Roll out drm_for_each_{plane, crtc, encoder}
Date: 28 Jun 2015 20:41:35 -0700	[thread overview]
Message-ID: <acb6cf$mdc0ql@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1435092362-31062-12-git-send-email-daniel.vetter@ffwll.ch>

Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6587
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
ILK                 -6              303/303              297/303
SNB                 -2              312/312              310/312
IVB                 -2              343/343              341/343
BYT                 -3              284/284              281/284
HSW                 -3              380/380              377/380
-------------------------------------Detailed-------------------------------------
Platform  Test                                drm-intel-nightly          Series Applied
*ILK  igt@drv_debugfs_reader      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)BUG:unable_to_handle_kernel@BUG: unable to handle kernel
Oops@Oops: 0000
RIP:describe_obj[i915]@RIP: .* describe_obj+0x
*ILK  igt@drv_suspend@debugfs-reader      PASS(1)      DMESG_WARN(1)
*ILK  igt@drv_suspend@fence-restore-tiled2untiled      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/drm_crtc.c:#drm_mode_config_reset[drm]()@WARNING:.* at .* drm_mode_config_reset+0x
*ILK  igt@drv_suspend@fence-restore-untiled      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/drm_crtc.c:#drm_mode_config_reset[drm]()@WARNING:.* at .* drm_mode_config_reset+0x
*ILK  igt@drv_suspend@forcewake      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/drm_crtc.c:#drm_mode_config_reset[drm]()@WARNING:.* at .* drm_mode_config_reset+0x
*ILK  igt@gem_workarounds@suspend-resume      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/drm_crtc.c:#drm_mode_config_reset[drm]()@WARNING:.* at .* drm_mode_config_reset+0x
*SNB  igt@drv_debugfs_reader      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)BUG:unable_to_handle_kernel@BUG: unable to handle kernel
Oops@Oops: 0000
RIP:describe_obj[i915]@RIP: .* describe_obj+0x
*SNB  igt@kms_addfb@framebuffer-vs-set-tiling      PASS(1)      TIMEOUT(1)
*IVB  igt@drv_debugfs_reader      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)BUG:unable_to_handle_kernel@BUG: unable to handle kernel
Oops@Oops: 0000
RIP:describe_obj[i915]@RIP: .* describe_obj+0x
*IVB  igt@kms_addfb@framebuffer-vs-set-tiling      PASS(1)      TIMEOUT(1)
*BYT  igt@drv_debugfs_reader      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)BUG:unable_to_handle_kernel@BUG: unable to handle kernel
Oops@Oops: 0000
RIP:describe_obj[i915]@RIP: .* describe_obj+0x
*BYT  igt@gem_partial_pwrite_pread@reads-display      PASS(1)      FAIL(1)
*BYT  igt@kms_addfb@framebuffer-vs-set-tiling      PASS(1)      TIMEOUT(1)
*HSW  igt@drv_debugfs_reader      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)BUG:unable_to_handle_kernel@BUG: unable to handle kernel
Oops@Oops: 0000
RIP:describe_obj[i915]@RIP: .* describe_obj+0x
*HSW  igt@kms_addfb@framebuffer-vs-set-tiling      PASS(1)      TIMEOUT(1)
*HSW  igt@pm_rpm@debugfs-read      PASS(1)      TIMEOUT(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-06-29  3:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 20:45 [PATCH 00/11] [RFC] drm_for_each_* macros and list locking Daniel Vetter
2015-06-23 20:45 ` [PATCH 01/11] drm: Simplify drm_for_each_legacy_plane arguments Daniel Vetter
2015-06-23 20:45 ` [PATCH 02/11] drm: Add modeset object iterators Daniel Vetter
2015-06-23 20:45 ` [PATCH 03/11] drm/probe-helper: Grab mode_config.mutex in poll_init/enable Daniel Vetter
2015-06-23 20:45 ` [PATCH 04/11] drm/fbdev-helper: Grab mode_config.mutex in drm_fb_helper_single_add_all_connectors Daniel Vetter
2015-06-23 20:45 ` [PATCH 05/11] drm: Check locking in drm_for_each_encoder/connector Daniel Vetter
2015-06-23 20:45 ` [PATCH 06/11] drm/i915: Use drm_for_each_fb in i915_debugfs.c Daniel Vetter
2015-06-23 20:45 ` [PATCH 07/11] drm: Check locking in drm_for_each_fb Daniel Vetter
2015-06-23 20:45 ` [PATCH 08/11] drm/i915: Take all modeset locks for DP MST hotplug Daniel Vetter
2015-06-23 20:46 ` [PATCH 09/11] drm: Amend connector/encoder list locking rules Daniel Vetter
2015-06-24  7:57   ` Chris Wilson
2015-06-24  8:36     ` Daniel Vetter
2015-06-23 20:46 ` [PATCH 10/11] drm: Roll out drm_for_each_connector more Daniel Vetter
2015-06-23 20:46 ` [PATCH 11/11] drm: Roll out drm_for_each_{plane, crtc, encoder} Daniel Vetter
2015-06-29  3:41   ` shuang.he [this message]
2015-06-24  7:44 ` [PATCH 00/11] [RFC] drm_for_each_* macros and list locking Chris Wilson
2015-06-24  8:35   ` 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='acb6cf$mdc0ql@fmsmga002.fm.intel.com' \
    --to=shuang.he@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lei.a.liu@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.