* [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset
@ 2020-06-15 5:18 Pankaj Bharadiya
2020-06-15 10:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-06-15 10:43 ` [igt-dev] [i-g-t] " Chris Wilson
0 siblings, 2 replies; 5+ messages in thread
From: Pankaj Bharadiya @ 2020-06-15 5:18 UTC (permalink / raw)
To: igt-dev, zbigniew.kempczynski
We must specify the correct vertex buffer offset as
"End Offset Enable" bit is not enabled in 3DPRIMITIVE instruction.
This fixes below fatal error:
[FATAL]:
***** **** *** ** * FATAL * ** *** **** *****
StateArbiter>Surface State Pointers in the binding table must be 64 byte aligned.
Be sure that the binding table is set up correctly. Address found: 6b6b6b6b
***** **** *** ** END FATAL ** *** **** *****
Bspec: 56206
Signed-off-by: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
---
lib/rendercopy_gen9.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/rendercopy_gen9.c b/lib/rendercopy_gen9.c
index 85ae4cabc..695806500 100644
--- a/lib/rendercopy_gen9.c
+++ b/lib/rendercopy_gen9.c
@@ -951,7 +951,7 @@ static void gen8_emit_primitive(struct intel_batchbuffer *batch, uint32_t offset
OUT_BATCH(GEN4_3DPRIMITIVE | (7-2));
OUT_BATCH(0); /* gen8+ ignore the topology type field */
OUT_BATCH(3); /* vertex count */
- OUT_BATCH(0); /* We're specifying this instead with offset in GEN6_3DSTATE_VERTEX_BUFFERS */
+ OUT_BATCH(offset);
OUT_BATCH(1); /* single instance */
OUT_BATCH(0); /* start instance location */
OUT_BATCH(0); /* index buffer offset, ignored */
--
2.23.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [igt-dev] ✗ Fi.CI.BAT: failure for lib/rendercopy: Specify the correct vertex buffer offset
2020-06-15 5:18 [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset Pankaj Bharadiya
@ 2020-06-15 10:37 ` Patchwork
2020-06-15 10:43 ` [igt-dev] [i-g-t] " Chris Wilson
1 sibling, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-06-15 10:37 UTC (permalink / raw)
To: Pankaj Bharadiya; +Cc: igt-dev
== Series Details ==
Series: lib/rendercopy: Specify the correct vertex buffer offset
URL : https://patchwork.freedesktop.org/series/78326/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8625 -> IGTPW_4674
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_4674 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_4674, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_4674:
### IGT changes ###
#### Possible regressions ####
* igt@gem_render_linear_blits@basic:
- fi-cfl-8700k: [PASS][1] -> [FAIL][2] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-8700k/igt@gem_render_linear_blits@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-8700k/igt@gem_render_linear_blits@basic.html
- fi-kbl-r: [PASS][3] -> [FAIL][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-r/igt@gem_render_linear_blits@basic.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-r/igt@gem_render_linear_blits@basic.html
- fi-icl-guc: [PASS][5] -> [FAIL][6] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-guc/igt@gem_render_linear_blits@basic.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-guc/igt@gem_render_linear_blits@basic.html
- fi-cfl-8109u: [PASS][7] -> [FAIL][8] +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-8109u/igt@gem_render_linear_blits@basic.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-8109u/igt@gem_render_linear_blits@basic.html
- fi-kbl-guc: [PASS][9] -> [FAIL][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-guc/igt@gem_render_linear_blits@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-guc/igt@gem_render_linear_blits@basic.html
- fi-kbl-7500u: [PASS][11] -> [FAIL][12] +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-7500u/igt@gem_render_linear_blits@basic.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-7500u/igt@gem_render_linear_blits@basic.html
- fi-bxt-dsi: [PASS][13] -> [FAIL][14] +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-bxt-dsi/igt@gem_render_linear_blits@basic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-bxt-dsi/igt@gem_render_linear_blits@basic.html
- fi-kbl-x1275: [PASS][15] -> [FAIL][16] +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-x1275/igt@gem_render_linear_blits@basic.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-x1275/igt@gem_render_linear_blits@basic.html
- fi-glk-dsi: [PASS][17] -> [FAIL][18] +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-glk-dsi/igt@gem_render_linear_blits@basic.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-glk-dsi/igt@gem_render_linear_blits@basic.html
* igt@gem_render_tiled_blits@basic:
- fi-skl-6700k2: [PASS][19] -> [FAIL][20] +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-skl-6700k2/igt@gem_render_tiled_blits@basic.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-skl-6700k2/igt@gem_render_tiled_blits@basic.html
- fi-kbl-soraka: [PASS][21] -> [FAIL][22] +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-soraka/igt@gem_render_tiled_blits@basic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-soraka/igt@gem_render_tiled_blits@basic.html
- fi-cfl-guc: [PASS][23] -> [FAIL][24] +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-guc/igt@gem_render_tiled_blits@basic.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-guc/igt@gem_render_tiled_blits@basic.html
- fi-cml-s: [PASS][25] -> [FAIL][26] +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cml-s/igt@gem_render_tiled_blits@basic.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cml-s/igt@gem_render_tiled_blits@basic.html
- fi-tgl-u2: [PASS][27] -> [FAIL][28] +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-u2/igt@gem_render_tiled_blits@basic.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-u2/igt@gem_render_tiled_blits@basic.html
- fi-icl-u2: [PASS][29] -> [FAIL][30] +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-u2/igt@gem_render_tiled_blits@basic.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-u2/igt@gem_render_tiled_blits@basic.html
- fi-cml-u2: [PASS][31] -> [FAIL][32] +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cml-u2/igt@gem_render_tiled_blits@basic.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cml-u2/igt@gem_render_tiled_blits@basic.html
- fi-icl-y: NOTRUN -> [FAIL][33] +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-y/igt@gem_render_tiled_blits@basic.html
- fi-apl-guc: [PASS][34] -> [FAIL][35] +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-apl-guc/igt@gem_render_tiled_blits@basic.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-apl-guc/igt@gem_render_tiled_blits@basic.html
- fi-skl-guc: [PASS][36] -> [FAIL][37] +1 similar issue
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-skl-guc/igt@gem_render_tiled_blits@basic.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-skl-guc/igt@gem_render_tiled_blits@basic.html
- fi-kbl-8809g: [PASS][38] -> [FAIL][39] +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-8809g/igt@gem_render_tiled_blits@basic.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-8809g/igt@gem_render_tiled_blits@basic.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_render_tiled_blits@basic:
- {fi-tgl-dsi}: [PASS][40] -> [FAIL][41] +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-dsi/igt@gem_render_tiled_blits@basic.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-dsi/igt@gem_render_tiled_blits@basic.html
* igt@kms_frontbuffer_tracking@basic:
- {fi-ehl-1}: [PASS][42] -> [FAIL][43] +2 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-ehl-1/igt@kms_frontbuffer_tracking@basic.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-ehl-1/igt@kms_frontbuffer_tracking@basic.html
Known issues
------------
Here are the changes found in IGTPW_4674 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload:
- fi-bxt-dsi: [PASS][44] -> [DMESG-WARN][45] ([i915#1982])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-bxt-dsi/igt@i915_module_load@reload.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-bxt-dsi/igt@i915_module_load@reload.html
- fi-tgl-u2: [PASS][46] -> [DMESG-WARN][47] ([i915#402])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-u2/igt@i915_module_load@reload.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-u2/igt@i915_module_load@reload.html
* igt@i915_pm_rpm@module-reload:
- fi-byt-j1900: [PASS][48] -> [DMESG-WARN][49] ([i915#1982]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-byt-j1900/igt@i915_pm_rpm@module-reload.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-byt-j1900/igt@i915_pm_rpm@module-reload.html
* igt@kms_frontbuffer_tracking@basic:
- fi-tgl-u2: [PASS][50] -> [FAIL][51] ([i915#1897])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-u2/igt@kms_frontbuffer_tracking@basic.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-u2/igt@kms_frontbuffer_tracking@basic.html
- fi-cml-s: [PASS][52] -> [FAIL][53] ([i915#49])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cml-s/igt@kms_frontbuffer_tracking@basic.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cml-s/igt@kms_frontbuffer_tracking@basic.html
- fi-kbl-soraka: [PASS][54] -> [FAIL][55] ([i915#49])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-soraka/igt@kms_frontbuffer_tracking@basic.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-soraka/igt@kms_frontbuffer_tracking@basic.html
- fi-cfl-guc: [PASS][56] -> [FAIL][57] ([i915#49])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-guc/igt@kms_frontbuffer_tracking@basic.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-guc/igt@kms_frontbuffer_tracking@basic.html
- fi-icl-guc: [PASS][58] -> [FAIL][59] ([i915#49])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-guc/igt@kms_frontbuffer_tracking@basic.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-guc/igt@kms_frontbuffer_tracking@basic.html
- fi-bxt-dsi: [PASS][60] -> [FAIL][61] ([i915#49])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-bxt-dsi/igt@kms_frontbuffer_tracking@basic.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-bxt-dsi/igt@kms_frontbuffer_tracking@basic.html
- fi-skl-6700k2: [PASS][62] -> [FAIL][63] ([i915#49])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-skl-6700k2/igt@kms_frontbuffer_tracking@basic.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-skl-6700k2/igt@kms_frontbuffer_tracking@basic.html
- fi-cml-u2: [PASS][64] -> [FAIL][65] ([i915#49])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
- fi-apl-guc: [PASS][66] -> [FAIL][67] ([i915#49])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-apl-guc/igt@kms_frontbuffer_tracking@basic.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-apl-guc/igt@kms_frontbuffer_tracking@basic.html
- fi-cfl-8700k: [PASS][68] -> [FAIL][69] ([i915#49])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-8700k/igt@kms_frontbuffer_tracking@basic.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-8700k/igt@kms_frontbuffer_tracking@basic.html
- fi-icl-u2: [PASS][70] -> [FAIL][71] ([i915#49])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
- fi-kbl-7500u: [PASS][72] -> [FAIL][73] ([i915#49])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-7500u/igt@kms_frontbuffer_tracking@basic.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-7500u/igt@kms_frontbuffer_tracking@basic.html
- fi-skl-guc: [PASS][74] -> [FAIL][75] ([i915#49])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-skl-guc/igt@kms_frontbuffer_tracking@basic.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-skl-guc/igt@kms_frontbuffer_tracking@basic.html
- fi-kbl-r: [PASS][76] -> [FAIL][77] ([i915#49])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-r/igt@kms_frontbuffer_tracking@basic.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-r/igt@kms_frontbuffer_tracking@basic.html
- fi-cfl-8109u: [PASS][78] -> [FAIL][79] ([i915#49])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-cfl-8109u/igt@kms_frontbuffer_tracking@basic.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-cfl-8109u/igt@kms_frontbuffer_tracking@basic.html
- fi-glk-dsi: [PASS][80] -> [FAIL][81] ([i915#49])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-glk-dsi/igt@kms_frontbuffer_tracking@basic.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-glk-dsi/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-u2: [FAIL][82] ([i915#1888]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-u2/igt@gem_exec_suspend@basic-s3.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- {fi-tgl-dsi}: [DMESG-WARN][84] ([i915#1982]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-tgl-dsi/igt@i915_pm_rpm@basic-pci-d3-state.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-tgl-dsi/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-n3050: [DMESG-WARN][86] ([i915#1982]) -> [PASS][87] +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-bsw-n3050/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-guc: [DMESG-WARN][88] ([i915#1982]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-guc/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-guc/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
* igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
- fi-icl-u2: [DMESG-WARN][90] ([i915#1982]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-icl-u2/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-icl-u2/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
#### Warnings ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-x1275: [SKIP][92] ([fdo#109271]) -> [DMESG-FAIL][93] ([i915#62])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
* igt@kms_flip@basic-plain-flip@a-dp1:
- fi-kbl-x1275: [DMESG-WARN][94] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][95] ([i915#62] / [i915#92]) +2 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-x1275/igt@kms_flip@basic-plain-flip@a-dp1.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-x1275/igt@kms_flip@basic-plain-flip@a-dp1.html
* igt@kms_frontbuffer_tracking@basic:
- fi-kbl-x1275: [DMESG-WARN][96] ([i915#62] / [i915#92]) -> [DMESG-FAIL][97] ([i915#49] / [i915#62])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-x1275/igt@kms_frontbuffer_tracking@basic.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-x1275/igt@kms_frontbuffer_tracking@basic.html
* igt@prime_vgem@basic-fence-flip:
- fi-kbl-x1275: [DMESG-WARN][98] ([i915#62] / [i915#92]) -> [DMESG-WARN][99] ([i915#62] / [i915#92] / [i915#95]) +4 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8625/fi-kbl-x1275/igt@prime_vgem@basic-fence-flip.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/fi-kbl-x1275/igt@prime_vgem@basic-fence-flip.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1897]: https://gitlab.freedesktop.org/drm/intel/issues/1897
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (44 -> 38)
------------------------------
Additional (1): fi-icl-y
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5710 -> IGTPW_4674
CI-20190529: 20190529
CI_DRM_8625: e5c6bbf45df498bd60d81b23c9f9ae7ed567eb8a @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4674: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/index.html
IGT_5710: f524eee47930601ad7b4cba9d40c26d68dc7d250 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset
2020-06-15 5:18 [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset Pankaj Bharadiya
2020-06-15 10:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
@ 2020-06-15 10:43 ` Chris Wilson
2020-06-17 7:24 ` Laxminarayan Bharadiya, Pankaj
1 sibling, 1 reply; 5+ messages in thread
From: Chris Wilson @ 2020-06-15 10:43 UTC (permalink / raw)
To: Pankaj Bharadiya, igt-dev, zbigniew.kempczynski
Quoting Pankaj Bharadiya (2020-06-15 06:18:48)
> We must specify the correct vertex buffer offset as
> "End Offset Enable" bit is not enabled in 3DPRIMITIVE instruction.
>
> This fixes below fatal error:
>
> [FATAL]:
> ***** **** *** ** * FATAL * ** *** **** *****
> StateArbiter>Surface State Pointers in the binding table must be 64 byte aligned.
> Be sure that the binding table is set up correctly. Address found: 6b6b6b6b
> ***** **** *** ** END FATAL ** *** **** *****
That is nothing to do with vertex offset. That says as it read the
binding table, it dereferenced the scratch page.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset
2020-06-15 10:43 ` [igt-dev] [i-g-t] " Chris Wilson
@ 2020-06-17 7:24 ` Laxminarayan Bharadiya, Pankaj
2020-06-17 9:53 ` Chris Wilson
0 siblings, 1 reply; 5+ messages in thread
From: Laxminarayan Bharadiya, Pankaj @ 2020-06-17 7:24 UTC (permalink / raw)
To: Chris Wilson, igt-dev, Kempczynski, Zbigniew, Wilson, Chris P
> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: 15 June 2020 16:13
> To: Laxminarayan Bharadiya, Pankaj
> <pankaj.laxminarayan.bharadiya@intel.com>; igt-dev@lists.freedesktop.org;
> Kempczynski, Zbigniew <zbigniew.kempczynski@intel.com>
> Subject: Re: [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer
> offset
>
> Quoting Pankaj Bharadiya (2020-06-15 06:18:48)
> > We must specify the correct vertex buffer offset as "End Offset
> > Enable" bit is not enabled in 3DPRIMITIVE instruction.
> >
> > This fixes below fatal error:
> >
> > [FATAL]:
> > ***** **** *** ** * FATAL * ** *** **** ***** StateArbiter>Surface
> > State Pointers in the binding table must be 64 byte aligned.
> > Be sure that the binding table is set up correctly. Address found:
> > 6b6b6b6b
> > ***** **** *** ** END FATAL ** *** **** *****
>
> That is nothing to do with vertex offset. That says as it read the binding table, it
> dereferenced the scratch page.
With this patch, the fatal error disappeared (for kms_big_fb, kms_cursor_crc tests)
on the newer platform so I thought it could be a possible fix.
As I understood from the spec, we should provide the correct vertex buffer offset to
3DPRIMITIVE instruction, but this affecting gem_render_linear_blits,
gem_render_tiled_blits and kms_frontbuffer_tracking tests.
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/index.html?
Any suggestion on how to debug this issue further? I tried dumping content of
batchbuffer but could not find the 6b6b6b6b address in dump.
Thanks,
Pankaj
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset
2020-06-17 7:24 ` Laxminarayan Bharadiya, Pankaj
@ 2020-06-17 9:53 ` Chris Wilson
0 siblings, 0 replies; 5+ messages in thread
From: Chris Wilson @ 2020-06-17 9:53 UTC (permalink / raw)
To: Kempczynski, Zbigniew, Laxminarayan Bharadiya, Pankaj, Wilson,
Chris P, igt-dev
Quoting Laxminarayan Bharadiya, Pankaj (2020-06-17 08:24:31)
>
>
> > -----Original Message-----
> > From: Chris Wilson <chris@chris-wilson.co.uk>
> > Sent: 15 June 2020 16:13
> > To: Laxminarayan Bharadiya, Pankaj
> > <pankaj.laxminarayan.bharadiya@intel.com>; igt-dev@lists.freedesktop.org;
> > Kempczynski, Zbigniew <zbigniew.kempczynski@intel.com>
> > Subject: Re: [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer
> > offset
> >
> > Quoting Pankaj Bharadiya (2020-06-15 06:18:48)
> > > We must specify the correct vertex buffer offset as "End Offset
> > > Enable" bit is not enabled in 3DPRIMITIVE instruction.
> > >
> > > This fixes below fatal error:
> > >
> > > [FATAL]:
> > > ***** **** *** ** * FATAL * ** *** **** ***** StateArbiter>Surface
> > > State Pointers in the binding table must be 64 byte aligned.
> > > Be sure that the binding table is set up correctly. Address found:
> > > 6b6b6b6b
> > > ***** **** *** ** END FATAL ** *** **** *****
> >
> > That is nothing to do with vertex offset. That says as it read the binding table, it
> > dereferenced the scratch page.
>
> With this patch, the fatal error disappeared (for kms_big_fb, kms_cursor_crc tests)
> on the newer platform so I thought it could be a possible fix.
>
> As I understood from the spec, we should provide the correct vertex buffer offset to
> 3DPRIMITIVE instruction, but this affecting gem_render_linear_blits,
> gem_render_tiled_blits and kms_frontbuffer_tracking tests.
We are passing the correct offset to 3DPRIM. It is nothing to do with
the binding table offset.
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4674/index.html?
>
> Any suggestion on how to debug this issue further? I tried dumping content of
> batchbuffer but could not find the 6b6b6b6b address in dump.
> > That is nothing to do with vertex offset. That says as it read the binding table, it
> > dereferenced the scratch page.
As a rough guess our binding table was too close to the end of the page
and it traversed over the page boundary into scratch.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-06-17 9:53 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-15 5:18 [igt-dev] [i-g-t] lib/rendercopy: Specify the correct vertex buffer offset Pankaj Bharadiya
2020-06-15 10:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-06-15 10:43 ` [igt-dev] [i-g-t] " Chris Wilson
2020-06-17 7:24 ` Laxminarayan Bharadiya, Pankaj
2020-06-17 9:53 ` Chris Wilson
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.