From: Jani Nikula <jani.nikula@linux.intel.com>
To: shuang.he@intel.comshuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, mika.kuoppala@linux.intel.com
Subject: Re: [PATCH 4/4] drm/i915: Be consistent on printing seqnos
Date: Tue, 03 Feb 2015 14:23:00 +0200 [thread overview]
Message-ID: <8761bjyyjf.fsf@intel.com> (raw)
In-Reply-To: <f539c7$jtufhc@fmsmga002.fm.intel.com>
On Wed, 28 Jan 2015, shuang.he@intel.com wrote:
> Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
> Task id: 5645
> -------------------------------------Summary-------------------------------------
> Platform Delta drm-intel-nightly Series Applied
> PNV -1 353/353 352/353
> ILK 353/353 353/353
> SNB -1 400/422 399/422
> IVB +2-2 485/487 485/487
> BYT 296/296 296/296
> HSW +1-1 507/508 507/508
> BDW 401/402 401/402
> -------------------------------------Detailed-------------------------------------
> Platform Test drm-intel-nightly Series Applied
> *PNV igt_gen3_render_linear_blits PASS(3, M25M23) CRASH(1, M23)
> *SNB igt_gem_concurrent_blit_gpu-bcs-gpu-read-after-write PASS(2, M35) NO_RESULT(1, M35)
> *IVB igt_gem_persistent_relocs_forked-thrashing PASS(2, M34M4) NO_RESULT(1, M4)
> IVB igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(2, M34)PASS(3, M4) PASS(1, M4)
> IVB igt_gem_storedw_batches_loop_normal DMESG_WARN(2, M34M4)PASS(5, M34M4M21) PASS(1, M4)
> *IVB igt_gem_storedw_loop_blt PASS(2, M34M4) DMESG_WARN(1, M4)
> HSW igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(1, M40)PASS(7, M40M20) PASS(1, M40)
> *HSW igt_pm_rpm_debugfs-read PASS(2, M40) DMESG_WARN(1, M40)
> Note: You need to pay more attention to line start with '*'
This bug was not found by prts:
https://bugs.freedesktop.org/show_bug.cgi?id=88908
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-02-03 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 16:03 [PATCH 1/4] drm/i915: Convert hangcheck from a timer into a delayed work item Mika Kuoppala
2015-01-26 16:03 ` [PATCH 2/4] drm/i915: Display current hangcheck status in debugfs Mika Kuoppala
2015-01-26 16:03 ` [PATCH 3/4] drm/i915: Remove nested work in gpu error handling Mika Kuoppala
2015-01-27 9:53 ` Chris Wilson
2015-01-28 9:37 ` Daniel Vetter
2015-01-28 15:03 ` [PATCH] " Mika Kuoppala
2015-01-28 15:30 ` Chris Wilson
2015-01-29 17:03 ` Daniel Vetter
2015-02-02 9:17 ` Chris Wilson
2015-02-02 9:38 ` Daniel Vetter
2015-02-02 10:08 ` Chris Wilson
2015-02-03 14:05 ` Mika Kuoppala
2015-01-26 16:03 ` [PATCH 4/4] drm/i915: Be consistent on printing seqnos Mika Kuoppala
2015-01-27 9:52 ` Chris Wilson
2015-01-28 11:59 ` shuang.he
2015-02-03 12:23 ` Jani Nikula [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=8761bjyyjf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=shuang.he@intel.comshuang.he \
/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