From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, mika.kuoppala@linux.intel.com
Subject: Re: [PATCH] drm/i915: Squelch overzealous uncore reset WARN_ON
Date: 05 Feb 2015 09:52:35 -0800 [thread overview]
Message-ID: <898e4a$ddfafv@FMSMGA003.fm.intel.com> (raw)
In-Reply-To: <1423131671-25970-1-git-send-email-mika.kuoppala@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5716
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV +1 282/283 283/283
ILK +3 316/319 319/319
SNB 322/346 322/346
IVB -1 382/384 381/384
BYT 296/296 296/296
HSW 425/428 425/428
BDW 318/333 318/333
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
PNV igt_gen3_render_linear_blits FAIL(2, M7)CRASH(1, M23)PASS(4, M25M23) PASS(1, M25)
*ILK igt_drv_suspend_debugfs-reader DMESG_WARN(2, M26M37) PASS(1, M37)
*ILK igt_drv_suspend_forcewake DMESG_WARN(4, M26M37) PASS(1, M37)
*ILK igt_gem_workarounds_suspend-resume DMESG_WARN(2, M26M37) PASS(1, M37)
IVB igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(2, M34)PASS(5, M21M34) DMESG_WARN(1, M21)
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-02-05 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 10:21 [PATCH] drm/i915: Squelch overzealous uncore reset WARN_ON Mika Kuoppala
2015-02-05 10:29 ` Chris Wilson
2015-02-05 15:45 ` Mika Kuoppala
2015-02-05 16:43 ` Chris Wilson
2015-02-09 12:37 ` Jani Nikula
2015-02-07 9:31 ` shuang.he
2015-02-05 17:52 ` 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='898e4a$ddfafv@FMSMGA003.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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