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] drm/vblank: Fixup and document timestamp update/read barriers
Date: 15 Apr 2015 12:40:51 -0700 [thread overview]
Message-ID: <edcf24$eb2cnr@FMSMGA003.fm.intel.com> (raw)
In-Reply-To: <1429082222-20820-1-git-send-email-daniel.vetter@ffwll.ch>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6195
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 276/276 276/276
ILK -1 302/302 301/302
SNB 318/318 318/318
IVB 341/341 341/341
BYT 287/287 287/287
HSW 395/395 395/395
BDW 318/318 318/318
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*ILK igt@gem_fenced_exec_thrash@no-spare-fences-busy-interruptible PASS(2) DMESG_WARN(1)PASS(1)
(dmesg patch applied)drm:i915_hangcheck_elapsed[i915]]*ERROR*Hangcheck_timer_elapsed...bsd_ring_idle@Hangcheck timer elapsed... bsd ring idle
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-15 19:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 7:17 [PATCH] drm/vblank: Fixup and document timestamp update/read barriers Daniel Vetter
2015-04-15 8:17 ` Chris Wilson
2015-04-15 9:25 ` Daniel Vetter
2015-04-15 9:36 ` Chris Wilson
2015-04-15 10:32 ` Daniel Vetter
2015-04-15 17:34 ` Daniel Vetter
2015-04-15 17:49 ` Chris Wilson
2015-04-15 21:26 ` Mario Kleiner
2015-04-16 1:29 ` Peter Hurley
2015-04-16 6:39 ` Mario Kleiner
2015-04-16 9:00 ` Peter Hurley
2015-04-16 9:06 ` Daniel Vetter
2015-04-16 12:52 ` Peter Hurley
2015-04-16 8:54 ` Daniel Vetter
2015-04-16 0:17 ` shuang.he
2015-04-16 8:59 ` Daniel Vetter
2015-04-17 4:27 ` shuang.he
2015-04-16 0:18 ` shuang.he
2015-04-15 13:00 ` Peter Hurley
2015-04-15 17:31 ` Daniel Vetter
2015-04-16 12:30 ` Peter Hurley
2015-04-16 13:03 ` [Intel-gfx] " Daniel Vetter
2015-05-04 4:52 ` Mario Kleiner
2015-05-05 14:36 ` Peter Hurley
2015-05-05 15:42 ` [Intel-gfx] " Daniel Vetter
2015-05-05 15:57 ` Peter Hurley
2015-05-05 19:01 ` Peter Hurley
2015-05-06 8:56 ` Daniel Vetter
2015-05-07 11:56 ` [Intel-gfx] " Peter Hurley
2015-05-07 17:33 ` Mario Kleiner
2015-04-15 19:40 ` 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='edcf24$eb2cnr@FMSMGA003.fm.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