Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref clock (rev3)
Hi Lakshmi, Tomi, On Sat, Oct 03, 2020 at 03:56:00AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref > clock (rev3) > URL : https://patchwork.freedesktop.org/series/82173/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_9093_full -> Patchwork_18620_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_18620_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_18620_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_18620_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_userptr_blits@unsync-unmap-cycles: > - shard-skl: [PASS][1] -> [TIMEOUT][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl6/igt@gem_userptr_bl...@unsync-unmap-cycles.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl4/igt@gem_userptr_bl...@unsync-unmap-cycles.html This looks like https://gitlab.freedesktop.org/drm/intel/-/issues/2424 still happening at https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9090/shard-skl5/igt@gem_userptr_bl...@sync-unmap-cycles.html Could you update the filter to include sync-unmap-cycles as well? > * igt@kms_flip@flip-vs-suspend@c-edp1: > - shard-iclb: [PASS][3] -> [INCOMPLETE][4] >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-iclb3/igt@kms_flip@flip-vs-susp...@c-edp1.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-iclb3/igt@kms_flip@flip-vs-susp...@c-edp1.html Looks like shard-iclb3 has a file system corruption, or just broken storage device/host: <3>[ 240.012780] blk_update_request: I/O error, dev sda, sector 76863120 op 0x1:(WRITE) flags 0x800 phys_seg 10 prio class 0 This has been consistently happening now for a while on the shard-iclb3 machine leading to the same hang, see for instance https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9063/shard-iclb3/pstore7-1601302770_Panic_1.txt Similar sporadic filesystem errors have been also happening on shard-iclb4. I haven't seen any recent I/O errors on any of the other 7 shard-icl machines. shard-iclb3/4 would probably need reinstall/new storage device/new host. --Imre ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref clock (rev3)
== Series Details == Series: drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref clock (rev3) URL : https://patchwork.freedesktop.org/series/82173/ State : success == Summary == CI Bug Log - changes from CI_DRM_9093_full -> Patchwork_18620_full Summary --- **SUCCESS** No regressions found. Known issues Here are the changes found in Patchwork_18620_full that come from known issues: ### IGT changes ### Issues hit * igt@gem_ctx_isolation@preservation-s3@bcs0: - shard-skl: [PASS][1] -> [INCOMPLETE][2] ([i915#198]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl1/igt@gem_ctx_isolation@preservation...@bcs0.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl1/igt@gem_ctx_isolation@preservation...@bcs0.html * igt@gem_userptr_blits@unsync-unmap-cycles: - shard-skl: [PASS][3] -> [TIMEOUT][4] ([i915#2424]) +1 similar issue [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl6/igt@gem_userptr_bl...@unsync-unmap-cycles.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl4/igt@gem_userptr_bl...@unsync-unmap-cycles.html * igt@kms_big_fb@linear-8bpp-rotate-0: - shard-kbl: [PASS][5] -> [DMESG-WARN][6] ([i915#1982]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-kbl6/igt@kms_big...@linear-8bpp-rotate-0.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-kbl4/igt@kms_big...@linear-8bpp-rotate-0.html * igt@kms_cursor_edge_walk@pipe-c-256x256-right-edge: - shard-glk: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-glk4/igt@kms_cursor_edge_w...@pipe-c-256x256-right-edge.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-glk5/igt@kms_cursor_edge_w...@pipe-c-256x256-right-edge.html * igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-untiled: - shard-apl: [PASS][9] -> [DMESG-WARN][10] ([i915#1635] / [i915#1982]) +1 similar issue [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-apl7/igt@kms_draw_...@draw-method-xrgb2101010-mmap-wc-untiled.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-apl1/igt@kms_draw_...@draw-method-xrgb2101010-mmap-wc-untiled.html * igt@kms_draw_crc@draw-method-xrgb-mmap-gtt-untiled: - shard-skl: [PASS][11] -> [FAIL][12] ([i915#177] / [i915#52] / [i915#54]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl7/igt@kms_draw_...@draw-method-xrgb-mmap-gtt-untiled.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl7/igt@kms_draw_...@draw-method-xrgb-mmap-gtt-untiled.html * igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1: - shard-skl: [PASS][13] -> [DMESG-WARN][14] ([i915#1982]) +9 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl8/igt@kms_flip@flip-vs-blocking-wf-vbl...@a-edp1.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl1/igt@kms_flip@flip-vs-blocking-wf-vbl...@a-edp1.html * igt@kms_flip@flip-vs-suspend@c-edp1: - shard-iclb: [PASS][15] -> [INCOMPLETE][16] ([i915#2536]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-iclb3/igt@kms_flip@flip-vs-susp...@c-edp1.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-iclb3/igt@kms_flip@flip-vs-susp...@c-edp1.html * igt@kms_flip@plain-flip-ts-check@c-edp1: - shard-skl: [PASS][17] -> [FAIL][18] ([i915#2122]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl9/igt@kms_flip@plain-flip-ts-ch...@c-edp1.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl8/igt@kms_flip@plain-flip-ts-ch...@c-edp1.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-mmap-gtt: - shard-tglb: [PASS][19] -> [DMESG-WARN][20] ([i915#1982]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-tglb1/igt@kms_frontbuffer_track...@psr-1p-primscrn-pri-indfb-draw-mmap-gtt.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-tglb2/igt@kms_frontbuffer_track...@psr-1p-primscrn-pri-indfb-draw-mmap-gtt.html * igt@kms_frontbuffer_tracking@psr-suspend: - shard-skl: [PASS][21] -> [INCOMPLETE][22] ([i915#123]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl6/igt@kms_frontbuffer_track...@psr-suspend.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl4/igt@kms_frontbuffer_track...@psr-suspend.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: - shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#180]) +3 similar issues [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-kbl2/igt@km
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref clock (rev3)
Thanks for the pointers Imre. I have re-reported the results. Lakshmi. -Original Message- From: Imre Deak Sent: Saturday, October 3, 2020 6:49 AM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana ; Sarvela, Tomi P Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref clock (rev3) Hi Lakshmi, Tomi, On Sat, Oct 03, 2020 at 03:56:00AM +, Patchwork wrote: > == Series Details == > > Series: drm/i915/tgl: Fix Combo PHY DPLL fractional divider for 38.4MHz ref > clock (rev3) > URL : https://patchwork.freedesktop.org/series/82173/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_9093_full -> Patchwork_18620_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_18620_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_18620_full, please notify your bug team to allow > them > to document this new failure mode, which will reduce false positives in CI. > > > > Possible new issues > --- > > Here are the unknown changes that may have been introduced in > Patchwork_18620_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_userptr_blits@unsync-unmap-cycles: > - shard-skl: [PASS][1] -> [TIMEOUT][2] >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-skl6/igt@gem_userptr_bl...@unsync-unmap-cycles.html >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-skl4/ig > t@gem_userptr_bl...@unsync-unmap-cycles.html This looks like https://gitlab.freedesktop.org/drm/intel/-/issues/2424 still happening at https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9090/shard-skl5/igt@gem_userptr_bl...@sync-unmap-cycles.html Could you update the filter to include sync-unmap-cycles as well? > * igt@kms_flip@flip-vs-suspend@c-edp1: > - shard-iclb: [PASS][3] -> [INCOMPLETE][4] >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9093/shard-iclb3/igt@kms_flip@flip-vs-susp...@c-edp1.html >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18620/shard-iclb3/i > gt@kms_flip@flip-vs-susp...@c-edp1.html Looks like shard-iclb3 has a file system corruption, or just broken storage device/host: <3>[ 240.012780] blk_update_request: I/O error, dev sda, sector 76863120 op 0x1:(WRITE) flags 0x800 phys_seg 10 prio class 0 This has been consistently happening now for a while on the shard-iclb3 machine leading to the same hang, see for instance https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9063/shard-iclb3/pstore7-1601302770_Panic_1.txt Similar sporadic filesystem errors have been also happening on shard-iclb4. I haven't seen any recent I/O errors on any of the other 7 shard-icl machines. shard-iclb3/4 would probably need reinstall/new storage device/new host. --Imre ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
