From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: ✗ Ro.CI.BAT: warning for drm/i915: fix out-of-bounds page_table access (rev2)
Date: Mon, 27 Jun 2016 12:59:05 +0100 [thread overview]
Message-ID: <57711509.7010704@intel.com> (raw)
In-Reply-To: <20160625052638.12913.74311@emeril.freedesktop.org>
On 25/06/16 06:26, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: fix out-of-bounds page_table access (rev2)
> URL : https://patchwork.freedesktop.org/series/9148/
> State : warning
>
> == Summary ==
>
> Series 9148v2 drm/i915: fix out-of-bounds page_table access
> http://patchwork.freedesktop.org/api/1.0/series/9148/revisions/2/mbox
>
> Test drv_module_reload_basic:
> dmesg-warn -> PASS (ro-byt-n2820)
> Test kms_pipe_crc_basic:
> Subgroup hang-read-crc-pipe-c:
> pass -> DMESG-WARN (ro-ivb2-i7-3770)
This looks like a variation of
https://bugs.freedesktop.org/show_bug.cgi?id=74102
[ILK/SNB/IVB]igt/testdisplay causes *ERROR* Pipe A FIFO underrun
so unrelated to page table macros.
.Dave.
> Subgroup suspend-read-crc-pipe-c:
> dmesg-warn -> SKIP (ro-bdw-i5-5250u)
>
> fi-hsw-i7-4770k total:229 pass:194 dwarn:0 dfail:0 fail:2 skip:33
> fi-kbl-qkkr total:229 pass:160 dwarn:29 dfail:0 fail:0 skip:40
> fi-skl-i5-6260u total:229 pass:202 dwarn:0 dfail:0 fail:2 skip:25
> fi-snb-i7-2600 total:229 pass:174 dwarn:0 dfail:0 fail:2 skip:53
> ro-bdw-i5-5250u total:227 pass:201 dwarn:3 dfail:1 fail:1 skip:21
> ro-bdw-i7-5600u total:227 pass:189 dwarn:0 dfail:1 fail:0 skip:37
> ro-bsw-n3050 total:227 pass:176 dwarn:0 dfail:1 fail:2 skip:48
> ro-byt-n2820 total:227 pass:177 dwarn:0 dfail:1 fail:4 skip:45
> ro-hsw-i3-4010u total:227 pass:194 dwarn:0 dfail:1 fail:1 skip:31
> ro-hsw-i7-4770r total:227 pass:194 dwarn:0 dfail:1 fail:1 skip:31
> ro-ilk-i7-620lm total:227 pass:154 dwarn:0 dfail:1 fail:2 skip:70
> ro-ilk1-i5-650 total:222 pass:154 dwarn:0 dfail:1 fail:2 skip:65
> ro-ivb-i7-3770 total:227 pass:185 dwarn:0 dfail:1 fail:1 skip:40
> ro-ivb2-i7-3770 total:227 pass:188 dwarn:1 dfail:1 fail:1 skip:36
> ro-skl3-i5-6260u total:227 pass:205 dwarn:1 dfail:1 fail:1 skip:19
> ro-snb-i7-2620M total:227 pass:178 dwarn:0 dfail:1 fail:1 skip:47
> ro-bdw-i7-5557U failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1305/
>
> 5c244f4 drm-intel-nightly: 2016y-06m-24d-15h-17m-32s UTC integration manifest
> 6811927 drm/i915: tweak gen6_for_{each_pde, all_pdes} macros
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-27 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 16:04 [PATCH] drm/i915: fix out-of-bounds page_table access Matthew Auld
2016-06-24 16:33 ` ✓ Ro.CI.BAT: success for " Patchwork
2016-06-24 16:37 ` [PATCH] " Chris Wilson
2016-06-24 18:28 ` Dave Gordon
2016-06-24 18:37 ` [PATCH] drm/i915: tweak gen6_for_{each_pde, all_pdes} macros Dave Gordon
2016-06-25 15:48 ` Matthew Auld
2016-06-25 5:26 ` ✗ Ro.CI.BAT: warning for drm/i915: fix out-of-bounds page_table access (rev2) Patchwork
2016-06-27 11:59 ` Dave Gordon [this message]
2016-06-27 12:14 ` Tvrtko Ursulin
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=57711509.7010704@intel.com \
--to=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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