tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
PATCH 1/1 tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
If by some reason or tests, this tests is executed and VT mode is already in KD_GRAPHICS the call to kmstest_set_vt_graphics_mode() will set orig_vt_mode as KD_GRAPHICS and when it was calling kmstest_restore_vt_mode() it would set KD_GRAPHICS again not returning to fbcon and causing the test to fail.
As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was 0x1)"
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-1/igt@[email protected]
So here adding a new function to alaways set mode the KD_TEXT when we want to restore to fbcon.
--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)
lib/igt_kms.c +11 -0
@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an igt exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) +{ +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); +}static void reset_connectors_at_exit (int sig) {
lib/igt_kms.h +1 -0
@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo *mode);int kmstest_get_pipe_from_crtc_id (int fd,int crtc_id);void kmstest_set_vt_graphics_mode (void );void kmstest_restore_vt_mode (void ); +void kmstest_set_vt_text_mode (void );enum igt_atomic_crtc_properties {IGT_CRTC_BACKGROUND =0 ,
tests/kms_fbcon_fbt.c +1 -1
@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode (); }static void subtest (struct drm_info *drm,struct feature *feature,bool suspend)
Signature · 6 lines
2.26.2 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
== Series Details ==
== Series Details ==
Series: tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
URL : https://patchwork.freedesktop.org/series/77774/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8551 -> IGTPW_4622
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
Changes
-------
No changes found
Participating hosts (50 -> 43)
------------------------------
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_5683 -> IGTPW_4622
CI-20190529: 20190529
CI_DRM_8551: 2342e5b1743ca04244e790ccd53638019187dd88 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4622: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
IGT_5683: 757b6e72d546fd2dbc3801a73796d67b0854021b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
In reply to José Roberto de Souza== Series Details ==
== Series Details ==
Series: tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
URL : https://patchwork.freedesktop.org/series/77774/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8551_full -> IGTPW_4622_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_4622_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in IGTPW_4622_full, 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_4622/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_4622_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_crc@pipe-a-cursor-256x256-offscreen:
- shard-glk: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk8/igt@[email protected]
* igt@runner@aborted:
- shard-hsw: NOTRUN -> [FAIL][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw1/igt@[email protected]
Known issues
------------
Here are the changes found in IGTPW_4622_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-clear:
- shard-hsw: [PASS][4] -> [DMESG-WARN][5] ([i915#1927])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw1/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw1/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][6] -> [DMESG-WARN][7] ([i915#180]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl3/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl1/igt@[email protected]
* igt@i915_module_load@reload:
- shard-glk: [PASS][8] -> [INCOMPLETE][9] ([i915#58] / [k.org#198133])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk6/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk8/igt@[email protected]
- shard-apl: [PASS][10] -> [INCOMPLETE][11] ([i915#1635])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl7/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding:
- shard-apl: [PASS][12] -> [FAIL][13] ([i915#54])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl7/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl2/igt@[email protected]
- shard-kbl: [PASS][14] -> [FAIL][15] ([i915#54])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x256-offscreen:
- shard-apl: [PASS][16] -> [TIMEOUT][17] ([i915#1635])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl8/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x21-offscreen:
- shard-kbl: [PASS][18] -> [FAIL][19] ([i915#54] / [i915#93] / [i915#95]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl3/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipb-toggle:
- shard-glk: [PASS][20] -> [DMESG-FAIL][21] ([i915#1925]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk5/igt@[email protected]
* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-tglb: [PASS][22] -> [DMESG-WARN][23] ([i915#128])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb6/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb6/igt@[email protected]
* igt@kms_pipe_crc_basic@hang-read-crc-pipe-a:
- shard-kbl: [PASS][24] -> [FAIL][25] ([i915#53] / [i915#93] / [i915#95])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl2/igt@[email protected]
- shard-apl: [PASS][26] -> [FAIL][27] ([i915#53] / [i915#95])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-kbl: [PASS][28] -> [INCOMPLETE][29] ([i915#155] / [i915#648])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl3/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl1/igt@[email protected]
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [PASS][30] -> [SKIP][31] ([fdo#109441])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb4/igt@kms_psr@psr2_sprite_mmap_gtt.html
#### Possible fixes ####
* igt@gem_mmap_gtt@basic-small-copy-odd:
- shard-hsw: [INCOMPLETE][32] ([i915#61]) -> [PASS][33] +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw8/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw6/igt@[email protected]
* igt@gem_set_tiling_vs_gtt:
- shard-glk: [DMESG-WARN][34] ([i915#1927]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@gem_set_tiling_vs_gtt.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk9/igt@gem_set_tiling_vs_gtt.html
* igt@gem_softpin@noreloc-s3:
- shard-kbl: [INCOMPLETE][36] -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl7/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][38] ([i915#1436] / [i915#716]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-tglb: [SKIP][40] ([i915#1904]) -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb7/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb8/igt@[email protected]
* igt@i915_pm_dc@dc5-psr:
- shard-iclb: [FAIL][42] ([i915#1899]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb3/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb3/igt@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [FAIL][44] ([i915#1119] / [i915#118] / [i915#95]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk7/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb8888-blt-untiled:
- shard-kbl: [FAIL][46] ([i915#177] / [i915#52] / [i915#54] / [i915#93] / [i915#95]) -> [PASS][47] +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl4/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled:
- shard-apl: [FAIL][48] ([i915#52] / [i915#54] / [i915#95]) -> [PASS][49] +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][50] ([i915#180]) -> [PASS][51] +3 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@kms_flip@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl7/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend@c-dp1}:
- shard-kbl: [DMESG-WARN][52] ([i915#180]) -> [PASS][53] +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@kms_flip@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl6/igt@kms_flip@[email protected]
* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][54] ([i915#433]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb7/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb6/igt@[email protected]
* igt@kms_panel_fitting@atomic-fastset:
- shard-tglb: [FAIL][56] ([i915#83]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb5/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb2/igt@[email protected]
- shard-iclb: [FAIL][58] ([i915#83]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb6/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-glk: [INCOMPLETE][60] ([i915#1927] / [i915#58] / [k.org#198133]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk6/igt@[email protected]
* igt@kms_plane_cursor@pipe-a-viewport-size-64:
- shard-kbl: [FAIL][62] ([i915#1559] / [i915#93] / [i915#95]) -> [PASS][63] +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl2/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl7/igt@[email protected]
- shard-apl: [FAIL][64] ([i915#1559] / [i915#95]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl3/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl4/igt@[email protected]
* igt@kms_psr@no_drrs:
- shard-iclb: [FAIL][66] ([i915#173]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb1/igt@kms_psr@no_drrs.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb8/igt@kms_psr@no_drrs.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][68] ([fdo#109441]) -> [PASS][69] +2 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb8/igt@kms_psr@psr2_cursor_mmap_cpu.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* {igt@perf@blocking-parameterized}:
- shard-iclb: [FAIL][70] ([i915#1542]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb6/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb6/igt@[email protected]
- shard-hsw: [FAIL][72] ([i915#1542]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw8/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw2/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][74] ([i915#1319] / [i915#1635]) -> [TIMEOUT][75] ([i915#1319])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl4/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: [FAIL][76] ([fdo#110321] / [fdo#110336]) -> [DMESG-FAIL][77] ([fdo#110321])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [TIMEOUT][78] ([i915#1319] / [i915#1635]) -> [FAIL][79] ([fdo#110321])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl1/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-apl: [DMESG-WARN][80] ([i915#180] / [i915#95]) -> [DMESG-WARN][81] ([i915#180])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [FAIL][82] ([i915#608]) -> [SKIP][83] ([fdo#109642] / [fdo#111068])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb2/igt@kms_psr2_su@page_flip.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb8/igt@kms_psr2_su@page_flip.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1559]: https://gitlab.freedesktop.org/drm/intel/issues/1559
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#173]: https://gitlab.freedesktop.org/drm/intel/issues/173
[i915#177]: https://gitlab.freedesktop.org/drm/intel/issues/177
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1899]: https://gitlab.freedesktop.org/drm/intel/issues/1899
[i915#1904]: https://gitlab.freedesktop.org/drm/intel/issues/1904
[i915#1925]: https://gitlab.freedesktop.org/drm/intel/issues/1925
[i915#1927]: https://gitlab.freedesktop.org/drm/intel/issues/1927
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#53]: https://gitlab.freedesktop.org/drm/intel/issues/53
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#608]: https://gitlab.freedesktop.org/drm/intel/issues/608
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#648]: https://gitlab.freedesktop.org/drm/intel/issues/648
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#83]: https://gitlab.freedesktop.org/drm/intel/issues/83
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (11 -> 8)
------------------------------
Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5683 -> IGTPW_4622
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_8551: 2342e5b1743ca04244e790ccd53638019187dd88 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4622: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
IGT_5683: 757b6e72d546fd2dbc3801a73796d67b0854021b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Re: [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
Quoted 34 lines · Patchwork
== Series Details ==
Series: tests/kms_fbcon_fbt: When restoring fbcon always set mode to text mode
URL : https://patchwork.freedesktop.org/series/77774/
State : failure== Summary ==
CI Bug Log - changes from
CI_DRM_8551_full->IGTPW_4622_full
====================================================Summary
-------**FAILURE**
Serious unknown changes coming with
IGTPW_4622_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
IGTPW_4622_full, 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_4622/index.html
Possible new issues
-------------------Here are the unknown changes that may have been introduced in
IGTPW_4622_full:### IGT changes ###
#### Possible regressions ####
Quoted 8 lines
* igt@kms_cursor_crc@pipe-a-cursor-256x256-offscreen:
- shard-glk: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk8/igt@[email protected]* igt@runner@aborted:
- shard-hsw: NOTRUN -> [FAIL][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw1/igt@[email protected]
Regressions above are not related to this changes.
Pushed, thanks for the review Uma.
Quoted 267 lines
Known issues
------------Here are the changes found in
IGTPW_4622_fullthat come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-clear:
- shard-hsw: [PASS][4] -> [DMESG-WARN][5] ([i915#1927])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw1/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw1/igt@[email protected]* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][6] -> [DMESG-WARN][7] ([i915#180]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl3/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl1/igt@[email protected]* igt@i915_module_load@reload:
- shard-glk: [PASS][8] -> [INCOMPLETE][9] ([i915#58] / [k.org#198133])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk6/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk8/igt@[email protected]
- shard-apl: [PASS][10] -> [INCOMPLETE][11] ([i915#1635])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl7/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]* igt@kms_cursor_crc@pipe-a-cursor-128x128-sliding:
- shard-apl: [PASS][12] -> [FAIL][13] ([i915#54])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl7/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl2/igt@[email protected]
- shard-kbl: [PASS][14] -> [FAIL][15] ([i915#54])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl4/igt@[email protected]* igt@kms_cursor_crc@pipe-a-cursor-256x256-offscreen:
- shard-apl: [PASS][16] -> [TIMEOUT][17] ([i915#1635])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl8/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]* igt@kms_cursor_crc@pipe-a-cursor-64x21-offscreen:
- shard-kbl: [PASS][18] -> [FAIL][19] ([i915#54] / [i915#93] / [i915#95]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl3/igt@[email protected]* igt@kms_cursor_legacy@cursora-vs-flipb-toggle:
- shard-glk: [PASS][20] -> [DMESG-FAIL][21] ([i915#1925]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk5/igt@[email protected]* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-tglb: [PASS][22] -> [DMESG-WARN][23] ([i915#128])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb6/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb6/igt@[email protected]* igt@kms_pipe_crc_basic@hang-read-crc-pipe-a:
- shard-kbl: [PASS][24] -> [FAIL][25] ([i915#53] / [i915#93] / [i915#95])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl2/igt@[email protected]
- shard-apl: [PASS][26] -> [FAIL][27] ([i915#53] / [i915#95])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-kbl: [PASS][28] -> [INCOMPLETE][29] ([i915#155] / [i915#648])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl3/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl1/igt@[email protected]* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [PASS][30] -> [SKIP][31] ([fdo#109441])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb4/igt@kms_psr@psr2_sprite_mmap_gtt.html#### Possible fixes ####
* igt@gem_mmap_gtt@basic-small-copy-odd:
- shard-hsw: [INCOMPLETE][32] ([i915#61]) -> [PASS][33] +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw8/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw6/igt@[email protected]* igt@gem_set_tiling_vs_gtt:
- shard-glk: [DMESG-WARN][34] ([i915#1927]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@gem_set_tiling_vs_gtt.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk9/igt@gem_set_tiling_vs_gtt.html* igt@gem_softpin@noreloc-s3:
- shard-kbl: [INCOMPLETE][36] -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl7/igt@[email protected]* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][38] ([i915#1436] / [i915#716]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-tglb: [SKIP][40] ([i915#1904]) -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb7/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb8/igt@[email protected]* igt@i915_pm_dc@dc5-psr:
- shard-iclb: [FAIL][42] ([i915#1899]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb3/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb3/igt@[email protected]* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [FAIL][44] ([i915#1119] / [i915#118] / [i915#95]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk7/igt@[email protected]* igt@kms_draw_crc@draw-method-xrgb8888-blt-untiled:
- shard-kbl: [FAIL][46] ([i915#177] / [i915#52] / [i915#54] / [i915#93] / [i915#95]) -> [PASS][47] +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl6/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl4/igt@[email protected]* igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled:
- shard-apl: [FAIL][48] ([i915#52] / [i915#54] / [i915#95]) -> [PASS][49] +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][50] ([i915#180]) -> [PASS][51] +3 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@kms_flip@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl7/igt@kms_flip@[email protected]* {igt@kms_flip@flip-vs-suspend@c-dp1}:
- shard-kbl: [DMESG-WARN][52] ([i915#180]) -> [PASS][53] +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl1/igt@kms_flip@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl6/igt@kms_flip@[email protected]* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][54] ([i915#433]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb7/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb6/igt@[email protected]* igt@kms_panel_fitting@atomic-fastset:
- shard-tglb: [FAIL][56] ([i915#83]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-tglb5/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-tglb2/igt@[email protected]
- shard-iclb: [FAIL][58] ([i915#83]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb6/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb6/igt@[email protected]* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-glk: [INCOMPLETE][60] ([i915#1927] / [i915#58] / [k.org#198133]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-glk8/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-glk6/igt@[email protected]* igt@kms_plane_cursor@pipe-a-viewport-size-64:
- shard-kbl: [FAIL][62] ([i915#1559] / [i915#93] / [i915#95]) -> [PASS][63] +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-kbl2/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-kbl7/igt@[email protected]
- shard-apl: [FAIL][64] ([i915#1559] / [i915#95]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl3/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl4/igt@[email protected]* igt@kms_psr@no_drrs:
- shard-iclb: [FAIL][66] ([i915#173]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb1/igt@kms_psr@no_drrs.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb8/igt@kms_psr@no_drrs.html* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][68] ([fdo#109441]) -> [PASS][69] +2 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb8/igt@kms_psr@psr2_cursor_mmap_cpu.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html* {igt@perf@blocking-parameterized}:
- shard-iclb: [FAIL][70] ([i915#1542]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb6/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb6/igt@[email protected]
- shard-hsw: [FAIL][72] ([i915#1542]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-hsw8/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-hsw2/igt@[email protected]#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][74] ([i915#1319] / [i915#1635]) -> [TIMEOUT][75] ([i915#1319])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl4/igt@[email protected]* igt@kms_content_protection@atomic-dpms:
- shard-apl: [FAIL][76] ([fdo#110321] / [fdo#110336]) -> [DMESG-FAIL][77] ([fdo#110321])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl6/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]* igt@kms_content_protection@lic:
- shard-apl: [TIMEOUT][78] ([i915#1319] / [i915#1635]) -> [FAIL][79] ([fdo#110321])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl1/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl1/igt@[email protected]* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-apl: [DMESG-WARN][80] ([i915#180] / [i915#95]) -> [DMESG-WARN][81] ([i915#180])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-apl4/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-apl6/igt@[email protected]* igt@kms_psr2_su@page_flip:
- shard-iclb: [FAIL][82] ([i915#608]) -> [SKIP][83] ([fdo#109642] / [fdo#111068])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8551/shard-iclb2/igt@kms_psr2_su@page_flip.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/shard-iclb8/igt@kms_psr2_su@page_flip.html{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1559]: https://gitlab.freedesktop.org/drm/intel/issues/1559
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#173]: https://gitlab.freedesktop.org/drm/intel/issues/173
[i915#177]: https://gitlab.freedesktop.org/drm/intel/issues/177
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1899]: https://gitlab.freedesktop.org/drm/intel/issues/1899
[i915#1904]: https://gitlab.freedesktop.org/drm/intel/issues/1904
[i915#1925]: https://gitlab.freedesktop.org/drm/intel/issues/1925
[i915#1927]: https://gitlab.freedesktop.org/drm/intel/issues/1927
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#53]: https://gitlab.freedesktop.org/drm/intel/issues/53
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#608]: https://gitlab.freedesktop.org/drm/intel/issues/608
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#648]: https://gitlab.freedesktop.org/drm/intel/issues/648
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#83]: https://gitlab.freedesktop.org/drm/intel/issues/83
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133Participating hosts (11 -> 8)
------------------------------Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7
Build changes
-------------* CI: CI-20190529 -> None
* IGT:IGT_5683->IGTPW_4622
* Piglit:piglit_4509-> NoneCI-20190529: 20190529
CI_DRM_8551:2342e5b1743ca04244e790ccd53638019187dd88@git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4622: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
IGT_5683:757b6e72d546fd2dbc3801a73796d67b0854021b@git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit
Quoted 3 lines
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4622/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 66 lines
-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of José Roberto de Souza
Sent: Friday, May 29, 2020 6:22 AM
To: [email protected]
Subject: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeIf by some reason or tests, this tests is executed and VT mode is already in
KD_GRAPHICSthe call tokmstest_set_vt_graphics_mode()will setorig_vt_modeasKD_GRAPHICSand when it was callingkmstest_restore_vt_mode()it would setKD_GRAPHICSagain not returning to fbcon and causing the test to fail.As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was0x1)"
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-
1/igt@[email protected]So here adding a new function to alaways set mode the
KD_TEXTwhen we want to restore to fbcon.Signed-off-by José Roberto de Souza <[email protected]>--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)lib/igt_kms.c +11
-0@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an igt +exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) +{ +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); } static void reset_connectors_at_exit(int sig) { diff --git a/lib/igt_kms.h
b/lib/igt_kms.hindexadca59ac6..32a0e4cc6100644lib/igt_kms.h +0
-0@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo *mode); int
kmstest_get_pipe_from_crtc_id(int fd, int crtc_id); voidkmstest_set_vt_graphics_mode(void);
voidkmstest_restore_vt_mode(void);lib/igt_kms.h +1
-0+void kmstest_set_vt_text_mode (void );enum igt_atomic_crtc_properties {IGT_CRTC_BACKGROUND =0 ,tests/kms_fbcon_fbt.c index renamed from tests/kms_fbcon_fbt.c +0
-0
e6dd4353b..e99a1f2f2100644
tests/kms_fbcon_fbt.c static void restore_fbcon(struct drm_info *drm) · line 286
Quoted 5 lines
tests/kms_fbcon_fbt.c +1
-1@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode ();
Can we level set the state to KD_TEXT in beginning only before we begin our test. This way test will start with the expected state, and we can then set KD_GRAPHICS, restore will ensure previous state is set again as KD_TEXT, and we can just continue with the existing restore logic. Will that cause any issue ?
Regards,
Uma Shankar
Quoted 10 lines
tests/kms_fbcon_fbt.c +0
-1}static void subtest (struct drm_info *drm,struct feature *feature,bool suspend) --2.26.2
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 66 lines · Uma
Quoted 66 lines
-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of José Roberto de Souza
Sent: Friday, May 29, 2020 6:22 AM
To: [email protected]
Subject: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeIf by some reason or tests, this tests is executed and VT mode is already in
KD_GRAPHICSthe call tokmstest_set_vt_graphics_mode()will setorig_vt_modeasKD_GRAPHICSand when it was callingkmstest_restore_vt_mode()it would setKD_GRAPHICSagain not returning to fbcon and causing the test to fail.As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was0x1)"
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-
1/igt@[email protected]So here adding a new function to alaways set mode the
KD_TEXTwhen we want to restore to fbcon.Signed-off-by José Roberto de Souza <[email protected]>--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)lib/igt_kms.c +11
-0@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an igt +exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) +{ +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); } static void reset_connectors_at_exit(int sig) { diff --git a/lib/igt_kms.h
b/lib/igt_kms.hindexadca59ac6..32a0e4cc6100644lib/igt_kms.h +0
-0@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo *mode); int
kmstest_get_pipe_from_crtc_id(int fd, int crtc_id); voidkmstest_set_vt_graphics_mode(void);
voidkmstest_restore_vt_mode(void);lib/igt_kms.h +1
-0+void kmstest_set_vt_text_mode (void );enum igt_atomic_crtc_properties {IGT_CRTC_BACKGROUND =0 ,tests/kms_fbcon_fbt.c index renamed from tests/kms_fbcon_fbt.c +0
-0
e6dd4353b..e99a1f2f2100644tests/kms_fbcon_fbt.c +0
-0@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);
Quoted 8 lines
tests/kms_fbcon_fbt.c static void restore_fbcon(struct drm_info *drm) · line 286
Quoted 3 lines
tests/kms_fbcon_fbt.c +1
-1igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode ();Can we level set the state to
KD_TEXTin beginning only before we begin our test. This way test will start with the expected state, and we can then setKD_GRAPHICS, restore will ensure previous state is set again asKD_TEXT, and we can just continue with the existing restore logic. Will that cause any issue ?
We could be overwriting the previous state, KD_TEXT is the state we expect in our CI but it do not means that is the state that other users have prior of executing this test, that is why kmstest_restore_vt_mode() don't just set to KD_TEXT.
Quoted 14 lines
Regards,
Uma ShankarQuoted 10 lines
tests/kms_fbcon_fbt.c +0
-1}static void subtest (struct drm_info *drm,struct feature *feature,bool suspend) --2.26.2
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 86 lines
-----Original Message-----
From: Souza, Jose <[email protected]>
Sent: Friday, May 29, 2020 10:21 PM
To: Shankar, Uma <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 8 lines · Uma
Quoted 8 lines
-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of José Roberto de Souza
Sent: Friday, May 29, 2020 6:22 AM
To: [email protected]
Subject: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 8 lines
Quoted 8 lines
If by some reason or tests, this tests is executed and VT mode is already in
KD_GRAPHICSthe call tokmstest_set_vt_graphics_mode()will setorig_vt_modeasKD_GRAPHICSand when it was callingkmstest_restore_vt_mode()it would setKD_GRAPHICSagain not returning to fbcon and causing the test to fail.As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was
0x1)"Quoted 41 lines
Quoted 41 lines
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-
1/igt@[email protected]So here adding a new function to alaways set mode the
KD_TEXTwhen we want to restore to fbcon.Signed-off-by José Roberto de Souza <[email protected]>--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)lib/igt_kms.c index renamed from lib/igt_kms.c +0
-0
d4cbc1c53..afef59396100644lib/igt_kms.c +10
-0@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an igt +exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) { +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); } static void reset_connectors_at_exit(int sig) { diff --git
a/lib/igt_kms.hb/lib/igt_kms.hindexadca59ac6..32a0e4cc6100644lib/igt_kms.h +0
-0@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo *mode);int
kmstest_get_pipe_from_crtc_id(int fd, int crtc_id); voidkmstest_set_vt_graphics_mode(void);
voidkmstest_restore_vt_mode(void);
+voidkmstest_set_vt_text_mode(void);Quoted 14 lines
tests/kms_fbcon_fbt.c static void restore_fbcon(struct drm_info *drm) · line 286
Quoted 12 lines
enum
igt_atomic_crtc_properties{
IGT_CRTC_BACKGROUND= 0,tests/kms_fbcon_fbt.c index renamed from tests/kms_fbcon_fbt.c +0
-0
e6dd4353b..e99a1f2f2100644tests/kms_fbcon_fbt.c +1
-1@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode ();Can we level set the state to
KD_TEXTin beginning only before we begin ourtest.
Quoted 3 lines
This way test will start with the expected state, and we can then set
KD_GRAPHICS, restore will ensure previous state is set again asKD_TEXT, and we can just continue with the existing restore logic. Will that
Quoted 6 lines
cause any issue ?
We could be overwriting the previous state,
KD_TEXTis the state we expect in our CI but it do not means that is the state that other users have prior of executing this test, that is whykmstest_restore_vt_mode()don't just set toKD_TEXT.
But will this not put the mode as KD_TEXT for other user as well who would be expecting it to be KD_GRAPHICS. How we ensure that we exit with original state of KD_GRAPHICS with which we started.
Quoted 11 lines
Quoted 11 lines
Regards,
Uma ShankarQuoted 7 lines
tests/kms_fbcon_fbt.c +0
-0} static void subtest(struct drm_info *drm, struct feature *feature,bool suspend)
--
2.26.2
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 86 lines · Uma
Quoted 86 lines
-----Original Message-----
From: Souza, Jose <[email protected]>
Sent: Friday, May 29, 2020 10:21 PM
To: Shankar, Uma <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 8 lines · Uma
Quoted 8 lines
-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of José Roberto de Souza
Sent: Friday, May 29, 2020 6:22 AM
To: [email protected]
Subject: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 8 lines
Quoted 8 lines
If by some reason or tests, this tests is executed and VT mode is already in
KD_GRAPHICSthe call tokmstest_set_vt_graphics_mode()will setorig_vt_modeasKD_GRAPHICSand when it was callingkmstest_restore_vt_mode()it would setKD_GRAPHICSagain not returning to fbcon and causing the test to fail.As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was
0x1)"Quoted 41 lines
Quoted 41 lines
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-
1/igt@[email protected]So here adding a new function to alaways set mode the
KD_TEXTwhen we want to restore to fbcon.Signed-off-by José Roberto de Souza <[email protected]>--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)lib/igt_kms.c index renamed from lib/igt_kms.c +0
-0
d4cbc1c53..afef59396100644lib/igt_kms.c +10
-0@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an igt +exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) { +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); } static void reset_connectors_at_exit(int sig) { diff --git
a/lib/igt_kms.hb/lib/igt_kms.hindexadca59ac6..32a0e4cc6100644lib/igt_kms.h +0
-0@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo *mode);int
kmstest_get_pipe_from_crtc_id(int fd, int crtc_id); voidkmstest_set_vt_graphics_mode(void);
voidkmstest_restore_vt_mode(void);
+voidkmstest_set_vt_text_mode(void);Quoted 14 lines
tests/kms_fbcon_fbt.c static void restore_fbcon(struct drm_info *drm) · line 286
Quoted 12 lines
enum
igt_atomic_crtc_properties{
IGT_CRTC_BACKGROUND= 0,tests/kms_fbcon_fbt.c index renamed from tests/kms_fbcon_fbt.c +0
-0
e6dd4353b..e99a1f2f2100644tests/kms_fbcon_fbt.c +1
-1@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode ();Can we level set the state to
KD_TEXTin beginning only before we begin ourtest.
Quoted 3 lines
This way test will start with the expected state, and we can then set
KD_GRAPHICS, restore will ensure previous state is set again asKD_TEXT, and we can just continue with the existing restore logic. Will thatcause any issue ?
Quoted 8 lines
Quoted 4 lines
We could be overwriting the previous state,
KD_TEXTis the state we expect in our CI but it do not means that is the state that other users have prior of executing this test, that is whykmstest_restore_vt_mode()don't just set toKD_TEXT.But will this not put the mode as
KD_TEXTfor other user as well who would be expecting it to beKD_GRAPHICS. How we ensure that we exit with original state ofKD_GRAPHICSwith which we started.
This test will restore the state that was set when it was executed, if it is not in the right state is not the job of this test to fix the global state.
This changes here will make sure state is changed to what we need while executing it, the right fix for the state outside of this test is track down what test or whatever is causing it and fix it.
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Regards,
Uma ShankarQuoted 7 lines
tests/kms_fbcon_fbt.c +0
-0} static void subtest(struct drm_info *drm, struct feature *feature,bool suspend)
--
2.26.2
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Shankar, Uma
Reviewed-by Uma ShankarQuoted 112 lines
-----Original Message-----
From: Souza, Jose <[email protected]>
Sent: Monday, June 1, 2020 10:13 PM
To: Shankar, Uma <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 59 lines · Uma
Quoted 59 lines
-----Original Message-----
From: Souza, Jose <[email protected]>
Sent: Friday, May 29, 2020 10:21 PM
To: Shankar, Uma <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeQuoted 15 lines · Uma
Quoted 15 lines
-----Original Message-----
From: igt-dev <[email protected]> On Behalf Of José Roberto de Souza
Sent: Friday, May 29, 2020 6:22 AM
To: [email protected]
Subject: [igt-dev] [PATCH i-g-t] tests/kms_fbcon_fbt: When restoring fbcon always set mode to text modeIf by some reason or tests, this tests is executed and VT mode is already in
KD_GRAPHICSthe call tokmstest_set_vt_graphics_mode()will setorig_vt_modeasKD_GRAPHICSand when it was callingkmstest_restore_vt_mode()it would setKD_GRAPHICSagain not returning to fbcon and causing the test to fail.Quoted 3 lines
Quoted 3 lines
As it can be seen here:
(kms_fbcon_fbt:11004) igt_kms-DEBUG: VT: graphics mode set (mode was
0x1)"Quoted 31 lines
Quoted 31 lines
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_499/fi-ehl-
1/igt@[email protected]So here adding a new function to alaways set mode the
KD_TEXTwhen we want to restore to fbcon.Signed-off-by José Roberto de Souza <[email protected]>--- lib/igt_kms.c | 11 +++++++++++ lib/igt_kms.h | 1 + tests/kms_fbcon_fbt.c | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)lib/igt_kms.c index renamed from lib/igt_kms.c +0
-0
d4cbc1c53..afef59396100644lib/igt_kms.c +10
-0@@ -968,6 +968,17 @@ void kmstest_set_vt_graphics_mode(void)igt_debug ("VT: graphics mode set (mode was 0x%lx)\n" , ret); } +/** +* kmstest_set_vt_text_mode: +* +* Sets the controlling VT (if available) into text mode. +* Unlikely kmstest_set_vt_graphics_mode() it do not install an +igt exit +* handler to set the VT back to the previous mode. +*/ +void kmstest_set_vt_text_mode (void ) { +igt_assert (set_vt_mode (KD_TEXT ) >=0 ); }Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
lib/igt_kms.h void kmstest_dump_mode(drmModeModeInfo
Quoted 6 lines
lib/igt_kms.c +0
-0static void reset_connectors_at_exit(int sig) { diff --git
a/lib/igt_kms.hb/lib/igt_kms.hindexadca59ac6..32a0e4cc6100644lib/igt_kms.h +0
-0@@ -93,6 +93,7 @@ void kmstest_dump_mode(drmModeModeInfo*mode);
Quoted 27 lines
Quoted 27 lines
Quoted 5 lines
Quoted 5 lines
int
kmstest_get_pipe_from_crtc_id(int fd, int crtc_id); voidkmstest_set_vt_graphics_mode(void);
voidkmstest_restore_vt_mode(void);
+voidkmstest_set_vt_text_mode(void);Quoted 15 lines
tests/kms_fbcon_fbt.c static void restore_fbcon(struct drm_info *drm) · line 286
Quoted 12 lines
enum igt_atomic_crtc_properties { IGT_CRTC_BACKGROUND = 0, diff --git
a/tests/kms_fbcon_fbt.cb/tests/kms_fbcon_fbt.cindexe6dd4353b..e99a1f2f2100644tests/kms_fbcon_fbt.c +1
-1@@ -283,7 +283,7 @@ static void restore_fbcon(struct drm_info *drm)kmstest_unset_all_crtcs (drm->fd, drm->res);igt_remove_fb (drm->fd, &drm->fb);igt_device_drop_master (drm->fd); -kmstest_restore_vt_mode (); +kmstest_set_vt_text_mode ();Can we level set the state to
KD_TEXTin beginning only before we begin ourtest.
Quoted 4 lines
This way test will start with the expected state, and we can then set
KD_GRAPHICS, restore will ensure previous state is set again asKD_TEXT, and we can just continue with the existing restore logic. Will thatcause any issue ?
Quoted 8 lines
Quoted 4 lines
We could be overwriting the previous state,
KD_TEXTis the state we expect in our CI but it do not means that is the state that other users have prior of executing this test, that is whykmstest_restore_vt_mode()don't just set toKD_TEXT.But will this not put the mode as
KD_TEXTfor other user as well who would be expecting it to beKD_GRAPHICS. How we ensure that we exit with original state ofKD_GRAPHICSwith which we started.
Quoted 5 lines
This test will restore the state that was set when it was executed, if it is not in the right state is not the job of this test to fix the global state. This changes here will make sure state is changed to what we need while executing it, the right fix for the state outside of this test is track down what test or whatever is causing it and fix it.
Seems reasonable. This is:
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Regards,
Uma ShankarQuoted 7 lines
tests/kms_fbcon_fbt.c +0
-0} static void subtest(struct drm_info *drm, struct feature*feature, bool suspend)
--
2.26.2
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev