[Intel-gfx] Connectivity issue to the CI system
Hi everyone, We have been experiencing connectivity issue for the past week to the CI system which led to abnormal CI latencies: https://intel-gfx-ci.01.org/latency.html?project=igt&test=Fi.CI.IGT The issue has been under investigation, but unfortunately we do not know when this issue will get resolved. It however got worse over the weekend to the point that the CI system is completely unavailable. Sorry about the issue, I will keep you updated as information becomes available to me. Martin, on behalf of the CI team pEpkey.asc Description: pEpkey.asc ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [CI] Pre-merge testing disabled
On 2020-06-16 12:37, Peres, Martin wrote: > Hello world, > > Due to changes in our global data policy rules, the bucket used to store > the CI results became private, which prevents us from providing any > testing result. > > We have received a notice on Sunday about this change, notified them on > Monday that we wanted to keep our storage public and ended up on Tuesday > with a private bucket. > > We are working as fast as possible to address this, but we cannot give > any ETA. We'll be updating you in this thread. > > Sorry for the inconvenience, > Martin Thanks to Tomi Sarvela for his efforts, it's back! Sorry again for the inconvenience! Martin pEpkey.asc Description: pEpkey.asc ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] [CI] Pre-merge testing disabled
Hello world, Due to changes in our global data policy rules, the bucket used to store the CI results became private, which prevents us from providing any testing result. We have received a notice on Sunday about this change, notified them on Monday that we wanted to keep our storage public and ended up on Tuesday with a private bucket. We are working as fast as possible to address this, but we cannot give any ETA. We'll be updating you in this thread. Sorry for the inconvenience, Martin pEpkey.asc Description: pEpkey.asc ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH i-g-t] intel-ci: Drop gem_exec_suspend@basic-S4-device from BAT
On 2020-04-08 17:19, Chris Wilson wrote: > S4-devices is a debug only path, and while it can prove informative as > to the nature of suspend issues, being a debug only path it is not so > relevant towards the driver health. Relegate it to the shards and idle > runs, so we can shave 20s off BAT. > > gem_exec_suspend@basic itself is just a test suspend, a sanitycheck to > ensure the test is functional, for manual debugging of the tests. > > Signed-off-by: Chris Wilson > Cc: Martin Peres > Cc: Petri Latvala Acked-by: Martin Peres > --- > tests/intel-ci/fast-feedback.testlist | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/tests/intel-ci/fast-feedback.testlist > b/tests/intel-ci/fast-feedback.testlist > index 620d5f3a7..2ccad4386 100644 > --- a/tests/intel-ci/fast-feedback.testlist > +++ b/tests/intel-ci/fast-feedback.testlist > @@ -23,10 +23,8 @@ igt@gem_exec_fence@nb-await > igt@gem_exec_gttfill@basic > igt@gem_exec_parallel@engines > igt@gem_exec_store@basic > -igt@gem_exec_suspend@basic > igt@gem_exec_suspend@basic-s0 > igt@gem_exec_suspend@basic-s3 > -igt@gem_exec_suspend@basic-s4-devices > igt@gem_flink_basic@bad-flink > igt@gem_flink_basic@bad-open > igt@gem_flink_basic@basic > pEpkey.asc Description: pEpkey.asc ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH i-g-t] tests/kms_plane_alpha_blend: Correct typo in the name and comments of a subtest
On 2020-03-31 12:43, Petri Latvala wrote: > On Mon, Mar 30, 2020 at 06:55:32PM -0300, Melissa Wen wrote: >> Typo found in word transparent. >> Correct the word transparant, replacing the last letter -a- with -e- >> (transpar-a-nt to transpar-e-nt). >> >> Signed-off-by: Melissa Wen > > > Reviewed-by: Petri Latvala > > Martin, test rename, ack when cibuglog side is ready to merge this. > ACK, thanks for the patch Melissa! Martin pEpkey.asc Description: pEpkey.asc ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Adding YUV444 packed format support for skl+ (rev3)
+Lakshmi On 2020-02-24 11:20, Shankar, Uma wrote: > > >> -Original Message- >> From: Patchwork >> Sent: Saturday, February 22, 2020 12:30 AM >> To: Shankar, Uma >> Cc: intel-gfx@lists.freedesktop.org >> Subject: ✗ Fi.CI.IGT: failure for Adding YUV444 packed format support for >> skl+ (rev3) >> >> == Series Details == >> >> Series: Adding YUV444 packed format support for skl+ (rev3) >> URL : https://patchwork.freedesktop.org/series/73020/ >> State : failure >> >> == Summary == >> >> CI Bug Log - changes from CI_DRM_7966_full -> Patchwork_16632_full >> >> >> Summary >> --- >> >> **FAILURE** >> >> Serious unknown changes coming with Patchwork_16632_full absolutely need >> to be >> verified manually. >> >> If you think the reported changes have nothing to do with the changes >> introduced in Patchwork_16632_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_16632_full: >> >> ### IGT changes ### >> >> Possible regressions >> >> * igt@kms_fbcon_fbt@psr-suspend: >> - shard-iclb: [PASS][1] -> [FAIL][2] +1 similar issue >>[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> iclb6/igt@kms_fbcon_...@psr-suspend.html >>[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> iclb1/igt@kms_fbcon_...@psr-suspend.html > > Hi Martin, > Above failures seem unrelated to the change here. This adds a new format XYUV > and should not be > affecting the above tests. If you give your approval, we can then plan to > merge. Lakshmi, could you have a look at this? Martin > > Thanks & Regards, > Uma Shankar > >> >> New tests >> - >> >> New tests have been introduced between CI_DRM_7966_full and >> Patchwork_16632_full: >> >> ### New IGT tests (4) ### >> >> * igt@gem_eio@context-create: >> - Statuses : 6 pass(s) >> - Exec time: [0.02, 0.14] s >> >> * igt@i915_pm_rpm@gem-mmap-cpu: >> - Statuses : 5 pass(s) 1 skip(s) >> - Exec time: [0.0, 11.91] s >> >> * igt@i915_pm_rpm@gem-mmap-gtt: >> - Statuses : 5 pass(s) 1 skip(s) >> - Exec time: [0.0, 23.56] s >> >> * igt@kms_mmap_write_crc@main: >> - Statuses : 6 pass(s) >> - Exec time: [4.18, 20.85] s >> >> >> >> Known issues >> >> >> Here are the changes found in Patchwork_16632_full that come from known >> issues: >> >> ### IGT changes ### >> >> Issues hit >> >> * igt@gem_busy@busy-vcs1: >> - shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#112080]) +6 similar >> issues >>[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> iclb1/igt@gem_b...@busy-vcs1.html >>[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> iclb3/igt@gem_b...@busy-vcs1.html >> >> * igt@gem_ctx_persistence@clone: >> - shard-kbl: [PASS][5] -> [SKIP][6] ([fdo#109271] / >> [i915#1099]) +4 similar >> issues >>[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> kbl1/igt@gem_ctx_persiste...@clone.html >>[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> kbl2/igt@gem_ctx_persiste...@clone.html >> >> * igt@gem_ctx_persistence@file: >> - shard-skl: [PASS][7] -> [SKIP][8] ([fdo#109271] / >> [i915#1099]) +4 similar >> issues >>[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> skl8/igt@gem_ctx_persiste...@file.html >>[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> skl7/igt@gem_ctx_persiste...@file.html >> >> * igt@gem_ctx_persistence@process: >> - shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#112179] / >> [i915#1099]) +4 similar >> issues >>[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> iclb1/igt@gem_ctx_persiste...@process.html >>[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> iclb2/igt@gem_ctx_persiste...@process.html >> >> * igt@gem_ctx_persistence@processes: >> - shard-apl: [PASS][11] -> [SKIP][12] ([fdo#109271] / >> [i915#1099]) +4 similar >> issues >>[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> apl4/igt@gem_ctx_persiste...@processes.html >>[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> apl6/igt@gem_ctx_persiste...@processes.html >> - shard-glk: [PASS][13] -> [SKIP][14] ([fdo#109271] / >> [i915#1099]) +4 similar >> issues >>[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7966/shard- >> glk1/igt@gem_ctx_persiste...@processes.html >>[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16632/shard- >> glk7/igt@gem_ctx_persiste...@processes.html >> >> * igt@gem_eio@kms: >> - shard-snb: [PASS][15] -> [DMESG-WARN][16] ([i915#444]) >>[
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dp: Modeset only the tiled connectors with CRTC
On 28/01/2020 01:05, Navare, Manasi D wrote: > On Sat, Jan 25, 2020 at 01:31:06AM -0800, Saarinen, Jani wrote: >> + Martin to re-report. > > Could you re-report this so we get the full CI IGT results? Sorry, I had done the work but I re-reported the wrong run... Anyway, I queued the re-reporting. Sorry about this! Martin > > Manasi > >> >>> -Original Message- >>> From: Navare, Manasi D >>> Sent: lauantai 25. tammikuuta 2020 4.19 >>> To: intel-gfx@lists.freedesktop.org >>> Cc: Sarvela, Tomi P ; Saarinen, Jani >>> ; Nautiyal, Ankit K ; >>> Nikkanen, Kimmo >>> Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915/dp: Modeset only the tiled >>> connectors >>> with CRTC >>> >>> This Gem related failure is not relevant to this patch, but because of this >>> it doesn’t >>> run full IGT, I want to make sure that the kms_flip tests are not getting >>> hung. >>> >>> Or can we confirm this with manual testing? >>> >>> Manasi >>> >>> -Original Message- >>> From: Patchwork >>> Sent: Friday, January 24, 2020 5:47 PM >>> To: Navare, Manasi D >>> Cc: intel-gfx@lists.freedesktop.org >>> Subject: ✗ Fi.CI.BAT: failure for drm/i915/dp: Modeset only the tiled >>> connectors >>> with CRTC >>> >>> == Series Details == >>> >>> Series: drm/i915/dp: Modeset only the tiled connectors with CRTC >>> URL : https://patchwork.freedesktop.org/series/72559/ >>> State : failure >>> >>> == Summary == >>> >>> CI Bug Log - changes from CI_DRM_7811 -> Patchwork_16267 >>> >>> >>> Summary >>> --- >>> >>> **FAILURE** >>> >>> Serious unknown changes coming with Patchwork_16267 absolutely need to be >>> verified manually. >>> >>> If you think the reported changes have nothing to do with the changes >>> introduced in Patchwork_16267, 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/Patchwork_16267/index.html >>> >>> Possible new issues >>> --- >>> >>> Here are the unknown changes that may have been introduced in >>> Patchwork_16267: >>> >>> ### IGT changes ### >>> >>> Possible regressions >>> >>> * igt@gem_close_race@basic-threads: >>> - fi-hsw-peppy: [PASS][1] -> [INCOMPLETE][2] >>>[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-hsw- >>> peppy/igt@gem_close_r...@basic-threads.html >>>[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-hsw- >>> peppy/igt@gem_close_r...@basic-threads.html >>> >>> >>> Known issues >>> >>> >>> Here are the changes found in Patchwork_16267 that come from known issues: >>> >>> ### IGT changes ### >>> >>> Issues hit >>> >>> * igt@kms_chamelium@hdmi-hpd-fast: >>> - fi-kbl-7500u: [PASS][3] -> [FAIL][4] ([fdo#111096] / [i915#323]) >>>[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-kbl- >>> 7500u/igt@kms_chamel...@hdmi-hpd-fast.html >>>[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-kbl- >>> 7500u/igt@kms_chamel...@hdmi-hpd-fast.html >>> >>> >>> Possible fixes >>> >>> * igt@gem_exec_parallel@fds: >>> - fi-byt-n2820: [TIMEOUT][5] ([fdo#112271]) -> [PASS][6] >>>[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-byt- >>> n2820/igt@gem_exec_paral...@fds.html >>>[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-byt- >>> n2820/igt@gem_exec_paral...@fds.html >>> >>> * igt@i915_module_load@reload-with-fault-injection: >>> - fi-cfl-8700k: [DMESG-WARN][7] ([i915#889]) -> [PASS][8] >>>[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-cfl- >>> 8700k/igt@i915_module_l...@reload-with-fault-injection.html >>>[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-cfl- >>> 8700k/igt@i915_module_l...@reload-with-fault-injection.html >>> >>> * igt@i915_selftest@live_blt: >>> - fi-hsw-4770:[DMESG-FAIL][9] ([i915#725]) -> [PASS][10] >>>[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-hsw- >>> 4770/igt@i915_selftest@live_blt.html >>>[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-hsw- >>> 4770/igt@i915_selftest@live_blt.html >>> >>> * igt@i915_selftest@live_gem_contexts: >>> - fi-byt-n2820: [DMESG-FAIL][11] ([i915#722]) -> [PASS][12] >>>[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-byt- >>> n2820/igt@i915_selftest@live_gem_contexts.html >>>[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-byt- >>> n2820/igt@i915_selftest@live_gem_contexts.html >>> >>> * igt@i915_selftest@live_gtt: >>> - fi-bdw-5557u: [TIMEOUT][13] ([fdo#112271]) -> [PASS][14] >>>[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7811/fi-bdw- >>> 5557u/igt@i915_selftest@live_gtt.html >>>[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16267/fi-bdw- >>> 5557u/igt@i915_sel
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Enable second DBuf slice for ICL and TGL (rev21)
On 27/01/2020 09:48, Lisovskiy, Stanislav wrote: > Good morning :) > > > Yet another gem related issue not caused by this patch.. Thanks! Lakshmi reported the bug and I made the filing a little more generic and attached it to https://gitlab.freedesktop.org/drm/intel/issues/530. Thanks for sending us all these false positives! I queued a re-reporting of the results. Martin > > > Best Regards, > > Lisovskiy Stanislav > > Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 > Espoo > > *From:* Patchwork > *Sent:* Sunday, January 26, 2020 11:19:53 AM > *To:* Lisovskiy, Stanislav > *Cc:* intel-gfx@lists.freedesktop.org > *Subject:* ✗ Fi.CI.IGT: failure for Enable second DBuf slice for ICL and > TGL (rev21) > > == Series Details == > > Series: Enable second DBuf slice for ICL and TGL (rev21) > URL : https://patchwork.freedesktop.org/series/70059/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7806_full -> Patchwork_16248_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_16248_full absolutely > need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_16248_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_16248_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_persistent_relocs@forked-faulting-reloc-thrash-inactive: > - shard-skl: [PASS][1] -> [INCOMPLETE][2] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-skl1/igt@gem_persistent_rel...@forked-faulting-reloc-thrash-inactive.html > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-skl9/igt@gem_persistent_rel...@forked-faulting-reloc-thrash-inactive.html > > > Known issues > > > Here are the changes found in Patchwork_16248_full that come from > known issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_busy@close-race: > - shard-hsw: [PASS][3] -> [TIMEOUT][4] ([fdo#112271]) > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-hsw8/igt@gem_b...@close-race.html > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-hsw2/igt@gem_b...@close-race.html > > * igt@gem_ctx_isolation@vcs1-dirty-create: > - shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#109276] / > [fdo#112080]) +1 similar issue > [5]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-iclb2/igt@gem_ctx_isolat...@vcs1-dirty-create.html > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-iclb7/igt@gem_ctx_isolat...@vcs1-dirty-create.html > > * igt@gem_exec_schedule@pi-common-bsd: > - shard-iclb: [PASS][7] -> [SKIP][8] ([i915#677]) > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-iclb5/igt@gem_exec_sched...@pi-common-bsd.html > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-iclb2/igt@gem_exec_sched...@pi-common-bsd.html > > * igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd: > - shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#112146]) +1 > similar issue > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-iclb6/igt@gem_exec_sched...@preempt-queue-contexts-chain-bsd.html > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-iclb4/igt@gem_exec_sched...@preempt-queue-contexts-chain-bsd.html > > * igt@gem_exec_schedule@promotion-bsd1: > - shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109276]) +6 > similar issues > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-iclb1/igt@gem_exec_sched...@promotion-bsd1.html > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-iclb5/igt@gem_exec_sched...@promotion-bsd1.html > > * igt@gem_persistent_relocs@forked-faulting-reloc-thrashing: > - shard-hsw: [PASS][13] -> [INCOMPLETE][14] ([i915#530] / > [i915#61]) > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-hsw7/igt@gem_persistent_rel...@forked-faulting-reloc-thrashing.html > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-hsw7/igt@gem_persistent_rel...@forked-faulting-reloc-thrashing.html > - shard-iclb: [PASS][15] -> [INCOMPLETE][16] ([i915#140]) > [15]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7806/shard-iclb8/igt@gem_persistent_rel...@forked-faulting-reloc-thrashing.html > [16]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16248/shard-iclb8/igt@gem_persistent_rel...@forked-faulting-reloc-thrashing.ht
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev20)
Thanks for notifying us!
Re-reporting queued.
Martin
On 21/01/2020 10:58, Lisovskiy, Stanislav wrote:
> Looks, like needs one more bug to be reported, again some gem/gpu
> related issue..
>
>
> Best Regards,
>
> Lisovskiy Stanislav
>
> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160
> Espoo
>
> *From:* Patchwork
> *Sent:* Tuesday, January 21, 2020 2:26:31 AM
> *To:* Lisovskiy, Stanislav
> *Cc:* intel-gfx@lists.freedesktop.org
> *Subject:* ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and
> TGL (rev20)
>
> == Series Details ==
>
> Series: Enable second DBuf slice for ICL and TGL (rev20)
> URL : https://patchwork.freedesktop.org/series/70059/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7781 -> Patchwork_16174
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16174 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16174, 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/Patchwork_16174/index.html
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_16174:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@live_gt_engines:
> - fi-skl-lmem: [PASS][1] -> [INCOMPLETE][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_gt_engines.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_gt_engines.html
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@gem_exec_parallel@basic:
> - {fi-ehl-1}: NOTRUN -> [FAIL][3]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-ehl-1/igt@gem_exec_paral...@basic.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_16174 that come from known issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@gem_close_race@basic-threads:
> - fi-byt-j1900: [PASS][4] -> [TIMEOUT][5] ([fdo#112271] /
> [i915#816])
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-byt-j1900/igt@gem_close_r...@basic-threads.html
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-byt-j1900/igt@gem_close_r...@basic-threads.html
>
> * igt@i915_selftest@live_uncore:
> - fi-skl-lmem: [PASS][6] -> [DMESG-FAIL][7] ([i915#889])
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_uncore.html
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_uncore.html
>
> * igt@i915_selftest@live_workarounds:
> - fi-skl-lmem: [PASS][8] -> [DMESG-WARN][9] ([i915#889]) +3
> similar issues
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-skl-lmem/igt@i915_selftest@live_workarounds.html
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-skl-lmem/igt@i915_selftest@live_workarounds.html
>
>
> Possible fixes
>
> * igt@gem_exec_gttfill@basic:
> - {fi-ehl-1}: [INCOMPLETE][10] ([i915#937]) -> [PASS][11]
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-ehl-1/igt@gem_exec_gttf...@basic.html
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-ehl-1/igt@gem_exec_gttf...@basic.html
>
> * igt@i915_selftest@live_blt:
> - fi-hsw-4770: [DMESG-FAIL][12] ([i915#725]) -> [PASS][13]
> [12]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-hsw-4770/igt@i915_selftest@live_blt.html
> [13]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-hsw-4770/igt@i915_selftest@live_blt.html
>
>
> Warnings
>
> * igt@gem_exec_parallel@contexts:
> - fi-byt-n2820: [TIMEOUT][14] ([fdo#112271]) ->
> [INCOMPLETE][15] ([i915#45])
> [14]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7781/fi-byt-n2820/igt@gem_exec_paral...@contexts.html
> [15]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16174/fi-byt-n2820/igt@gem_exec_paral...@contexts.html
>
>
> {name}: This element is suppressed. This means it is ignored when
> computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
> [i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
> [i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
> [i915#816]: h
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and TGL (rev17)
On 17/01/2020 12:43, Lisovskiy, Stanislav wrote:
> Looks like gem issue, lots of warns - gpu has gone wild.
>
> Not related to DBuf for sure.
Thanks, it has been re-reported!
Sorry for the delay,
Martin
>
>
> Best Regards,
>
> Lisovskiy Stanislav
>
> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160
> Espoo
>
> *From:* Patchwork
> *Sent:* Friday, January 17, 2020 12:32:34 PM
> *To:* Lisovskiy, Stanislav
> *Cc:* intel-gfx@lists.freedesktop.org
> *Subject:* ✗ Fi.CI.BAT: failure for Enable second DBuf slice for ICL and
> TGL (rev17)
>
> == Series Details ==
>
> Series: Enable second DBuf slice for ICL and TGL (rev17)
> URL : https://patchwork.freedesktop.org/series/70059/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_7758 -> Patchwork_16145
>
>
> Summary
> ---
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_16145 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_16145, 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/Patchwork_16145/index.html
>
> Possible new issues
> ---
>
> Here are the unknown changes that may have been introduced in
> Patchwork_16145:
>
> ### IGT changes ###
>
> Possible regressions
>
> * igt@i915_selftest@live_hangcheck:
> - fi-hsw-peppy: [PASS][1] -> [DMESG-FAIL][2]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-hsw-peppy/igt@i915_selftest@live_hangcheck.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-hsw-peppy/igt@i915_selftest@live_hangcheck.html
>
> * igt@runner@aborted:
> - fi-hsw-peppy: NOTRUN -> [FAIL][3]
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-hsw-peppy/igt@run...@aborted.html
>
>
> Known issues
>
>
> Here are the changes found in Patchwork_16145 that come from known issues:
>
> ### IGT changes ###
>
> Issues hit
>
> * igt@i915_selftest@live_gem_contexts:
> - fi-cfl-guc: [PASS][4] -> [INCOMPLETE][5] ([CI#80] /
> [fdo#106070] / [i915#424])
> [4]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-cfl-guc/igt@i915_selftest@live_gem_contexts.html
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-cfl-guc/igt@i915_selftest@live_gem_contexts.html
>
>
> Possible fixes
>
> * igt@gem_exec_create@basic:
> - fi-icl-dsi: [DMESG-WARN][6] ([i915#109]) -> [PASS][7]
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-icl-dsi/igt@gem_exec_cre...@basic.html
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-icl-dsi/igt@gem_exec_cre...@basic.html
>
> * igt@i915_pm_rpm@module-reload:
> - fi-skl-6770hq: [FAIL][8] ([i915#178]) -> [PASS][9]
> [8]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-skl-6770hq/igt@i915_pm_...@module-reload.html
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-skl-6770hq/igt@i915_pm_...@module-reload.html
>
> * igt@kms_chamelium@hdmi-hpd-fast:
> - fi-kbl-7500u: [FAIL][10] ([fdo#111096] / [i915#323]) ->
> [PASS][11]
> [10]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-kbl-7500u/igt@kms_chamel...@hdmi-hpd-fast.html
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16145/fi-kbl-7500u/igt@kms_chamel...@hdmi-hpd-fast.html
>
>
> {name}: This element is suppressed. This means it is ignored when
> computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [CI#80]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/80
> [fdo#106070]: https://bugs.freedesktop.org/show_bug.cgi?id=106070
> [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
> [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
> [i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
> [i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
> [i915#424]: https://gitlab.freedesktop.org/drm/intel/issues/424
> [i915#937]: https://gitlab.freedesktop.org/drm/intel/issues/937
>
>
> Participating hosts (47 -> 42)
> --
>
> Additional (2): fi-kbl-soraka fi-byt-j1900
> Missing (7): fi-ilk-m540 fi-cml-s fi-hsw-4200u fi-byt-squawks
> fi-bsw-cyan fi-blb-e6850 fi-skl-6600u
>
>
> Build changes
> -
>
> * CI: CI-20190529 -> None
> * Linux: CI_DRM_7758 -> Patchwork_16145
>
> CI-20190529: 20190529
> CI_DRM_7758: d19270ce1f367fbfc1ff3b539bcb50e11ded181f @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5371: 1b2816124ec3dbd53b81725d39292f45d41d895b @
> git://an
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Bump up CDCLK to eliminate underruns on TGL (rev3)
On 13/01/2020 10:32, Lisovskiy, Stanislav wrote: > Yet again unrelated gem failure, do we have a bug about this? > https://bugs.freedesktop.org/show_bug.cgi?id=112271 > That CDCLK change is crucial to get in and has nothing to do with > gem tests, i.e can't anyhow affect the outcome. Btw, TGL shards were not included in these results because I rushed its reporting... so please wait for the second email that will have both the TGL shards results AND the false positive fixed (I already filed it). Martin > > > Best Regards, > > Lisovskiy Stanislav > > Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 > Espoo > > *From:* Patchwork > *Sent:* Monday, January 13, 2020 10:00:44 AM > *To:* Lisovskiy, Stanislav > *Cc:* intel-gfx@lists.freedesktop.org > *Subject:* ✗ Fi.CI.IGT: failure for drm/i915: Bump up CDCLK to eliminate > underruns on TGL (rev3) > > == Series Details == > > Series: drm/i915: Bump up CDCLK to eliminate underruns on TGL (rev3) > URL : https://patchwork.freedesktop.org/series/71760/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7714_full -> Patchwork_16045_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_16045_full absolutely > need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_16045_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_16045_full: > > ### IGT changes ### > > Possible regressions > > * igt@gem_busy@close-race: > - shard-hsw: NOTRUN -> [TIMEOUT][1] > [1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-hsw5/igt@gem_b...@close-race.html > > > New tests > - > > New tests have been introduced between CI_DRM_7714_full and > Patchwork_16045_full: > > ### New IGT tests (2) ### > > * igt@kms_dp_dsc@basic-dsc-enable-dp: > - Statuses : 8 skip(s) > - Exec time: [0.0, 0.00] s > > * igt@kms_dp_dsc@basic-dsc-enable-edp: > - Statuses : 1 pass(s) 7 skip(s) > - Exec time: [0.0, 4.92] s > > > > Known issues > > > Here are the changes found in Patchwork_16045_full that come from > known issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_ctx_isolation@vcs1-dirty-create: > - shard-iclb: [PASS][2] -> [SKIP][3] ([fdo#109276] / > [fdo#112080]) > [2]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-iclb1/igt@gem_ctx_isolat...@vcs1-dirty-create.html > [3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-iclb7/igt@gem_ctx_isolat...@vcs1-dirty-create.html > > * igt@gem_ctx_isolation@vecs0-s3: > - shard-kbl: [PASS][4] -> [INCOMPLETE][5] ([fdo#103665]) > [4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-kbl7/igt@gem_ctx_isolat...@vecs0-s3.html > [5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-kbl4/igt@gem_ctx_isolat...@vecs0-s3.html > > * igt@gem_ctx_shared@exec-single-timeline-bsd: > - shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#110841]) > [6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-iclb5/igt@gem_ctx_sha...@exec-single-timeline-bsd.html > [7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-iclb4/igt@gem_ctx_sha...@exec-single-timeline-bsd.html > > * igt@gem_ctx_shared@q-smoketest-bsd2: > - shard-tglb: [PASS][8] -> [INCOMPLETE][9] ([i915#461]) > [8]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-tglb5/igt@gem_ctx_sha...@q-smoketest-bsd2.html > [9]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-tglb4/igt@gem_ctx_sha...@q-smoketest-bsd2.html > > * igt@gem_eio@in-flight-1us: > - shard-snb: [PASS][10] -> [FAIL][11] ([i915#490]) > [10]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-snb1/igt@gem_...@in-flight-1us.html > [11]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-snb4/igt@gem_...@in-flight-1us.html > > * igt@gem_eio@kms: > - shard-snb: [PASS][12] -> [INCOMPLETE][13] ([i915#82]) +1 > similar issue > [12]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-snb2/igt@gem_...@kms.html > [13]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16045/shard-snb1/igt@gem_...@kms.html > > * igt@gem_exec_async@concurrent-writes-bsd: > - shard-iclb: [PASS][14] -> [SKIP][15] ([fdo#112146]) +1 > similar issue > [14]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7714/shard-iclb5/igt@gem_exec_as...@concurrent-writes-bsd.html > [
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Refactor Gen11+ SAGV support (rev14)
On 16/12/2019 15:50, Vudum, Lakshminarayana wrote: > Stan, > spec@arb_gpu_shader5@texturegather@vs-rgba-3-float-cubearray is new test > which doesn't exist in CI bug log, so I can't do much here. > > @Latvala, Petri/@Peres, Martin How do we proceed with these kind of issues in > future? Right... I hacked the DB, you can file it now! Martin > > Lakshmi. > > -Original Message- > From: Lisovskiy, Stanislav > Sent: Monday, December 16, 2019 3:22 PM > To: Vudum, Lakshminarayana > Cc: intel-gfx@lists.freedesktop.org > Subject: RE: ✗ Fi.CI.IGT: failure for Refactor Gen11+ SAGV support (rev14) > > Those shader tests are also irrelevant. > > Best Regards, > > Lisovskiy Stanislav > > Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo > > > From: Patchwork [patchw...@emeril.freedesktop.org] > Sent: Monday, December 16, 2019 3:00 PM > To: Lisovskiy, Stanislav > Cc: intel-gfx@lists.freedesktop.org > Subject: ✗ Fi.CI.IGT: failure for Refactor Gen11+ SAGV support (rev14) > > == Series Details == > > Series: Refactor Gen11+ SAGV support (rev14) > URL : https://patchwork.freedesktop.org/series/68028/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7560_full -> Patchwork_15747_full > > > Summary > --- > > **FAILURE** > > Serious unknown changes coming with Patchwork_15747_full absolutely need to > be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_15747_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_15747_full: > > ### Piglit changes ### > > Possible regressions > > * spec@arb_gpu_shader5@texturegather@vs-rgba-3-float-cubearray (NEW): > - pig-hsw-4770r: NOTRUN -> [FAIL][1] +5 similar issues >[1]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15747/pig-hsw-4770r/spec@arb_gpu_shader5@texturegat...@vs-rgba-3-float-cubearray.html > > > New tests > - > > New tests have been introduced between CI_DRM_7560_full and > Patchwork_15747_full: > > ### New Piglit tests (6) ### > > * spec@arb_es2_compatibility@fbo-blending-formats: > - Statuses : 1 fail(s) > - Exec time: [0.10] s > > * spec@arb_gpu_shader5@texturegather@vs-rgba-3-float-cubearray: > - Statuses : 1 fail(s) > - Exec time: [1.92] s > > * spec@arb_sample_shading@builtin-gl-sample-mask-simple 6: > - Statuses : 1 fail(s) > - Exec time: [0.16] s > > * spec@arb_sample_shading@builtin-gl-sample-mask-simple 8: > - Statuses : 1 fail(s) > - Exec time: [0.29] s > > * spec@arb_sampler_objects@gl_ext_texture_srgb_decode: > - Statuses : 1 fail(s) > - Exec time: [0.09] s > > * spec@glsl-4.20@execution@vs_in@vs-input-position-double_dvec4-int_ivec4: > - Statuses : 1 fail(s) > - Exec time: [0.18] s > > > > Known issues > > > Here are the changes found in Patchwork_15747_full that come from known > issues: > > ### IGT changes ### > > Issues hit > > * igt@gem_ctx_persistence@vcs1-mixed-process: > - shard-iclb: [PASS][2] -> [FAIL][3] ([i915#679]) >[2]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7560/shard-iclb2/igt@gem_ctx_persiste...@vcs1-mixed-process.html >[3]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15747/shard-iclb2/igt@gem_ctx_persiste...@vcs1-mixed-process.html > > * igt@gem_ctx_persistence@vcs1-persistence: > - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#109276] / > [fdo#112080]) +1 similar issue >[4]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7560/shard-iclb2/igt@gem_ctx_persiste...@vcs1-persistence.html >[5]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15747/shard-iclb6/igt@gem_ctx_persiste...@vcs1-persistence.html > > * igt@gem_eio@kms: > - shard-tglb: [PASS][6] -> [INCOMPLETE][7] ([i915#476]) >[6]: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7560/shard-tglb5/igt@gem_...@kms.html >[7]: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15747/shard-tglb9/igt@gem_...@kms.html > > * igt@gem_exec_gttfill@basic: > - shard-tglb: [PASS][8] -> [INCOMPLETE][9] ([fdo#111593]) >[
Re: [Intel-gfx] [PATCH] drm/i915: Update bug URL to point at gitlab issues
On 02/12/2019 16:25, Chris Wilson wrote:
> Quoting Jani Nikula (2019-12-02 11:36:01)
>> On Mon, 02 Dec 2019, "Peres, Martin" wrote:
>>> On 02/12/2019 12:30, Jani Nikula wrote:
>>>> On Mon, 25 Nov 2019, Chris Wilson wrote:
>>>>> We are moving our issue tracking over from bugs.fd.o to gitlab.fd.o, so
>>>>> update the user instructions accordingly.
>>>>>
>>>>> Signed-off-by: Chris Wilson
>>>>> Cc: Martin Peres
>>>>> Cc: Joonas Lahtinen
>>>>> Cc: Rodrigo Vivi
>>>>> Cc: Jani Nikula
>>>>> Cc: sta...@vger.kernel.org
>>>>> ---
>>>>> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
>>>>> drivers/gpu/drm/i915/i915_utils.c | 3 +--
>>>>> drivers/gpu/drm/i915/i915_utils.h | 2 ++
>>>>> 3 files changed, 4 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c
>>>>> b/drivers/gpu/drm/i915/i915_gpu_error.c
>>>>> index 2b30a45fa25c..1cf53fd4fe66 100644
>>>>> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
>>>>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
>>>>> @@ -1817,7 +1817,7 @@ void i915_capture_error_state(struct
>>>>> drm_i915_private *i915,
>>>>> if (!xchg(&warned, true) &&
>>>>> ktime_get_real_seconds() - DRIVER_TIMESTAMP <
>>>>> DAY_AS_SECONDS(180)) {
>>>>> pr_info("GPU hangs can indicate a bug anywhere in the entire
>>>>> gfx stack, including userspace.\n");
>>>>> - pr_info("Please file a _new_ bug report on
>>>>> bugs.freedesktop.org against DRI -> DRM/Intel\n");
>>>>> + pr_info("Please file a _new_ bug report on " FDO_BUG_URL
>>>>> "\n");
>>>>> pr_info("drm/i915 developers can then reassign to the right
>>>>> component if it's not a kernel issue.\n");
>>>>> pr_info("The GPU crash dump is required to analyze GPU hangs,
>>>>> so please always attach it.\n");
>>>>> pr_info("GPU crash dump saved to
>>>>> /sys/class/drm/card%d/error\n",
>>>>> diff --git a/drivers/gpu/drm/i915/i915_utils.c
>>>>> b/drivers/gpu/drm/i915/i915_utils.c
>>>>> index c47261ae86ea..9b68b21becf1 100644
>>>>> --- a/drivers/gpu/drm/i915/i915_utils.c
>>>>> +++ b/drivers/gpu/drm/i915/i915_utils.c
>>>>> @@ -8,8 +8,7 @@
>>>>> #include "i915_drv.h"
>>>>> #include "i915_utils.h"
>>>>>
>>>>> -#define FDO_BUG_URL
>>>>> "https://bugs.freedesktop.org/enter_bug.cgi?product=DRI";
>>>>> -#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL " against
>>>>> DRM/Intel " \
>>>>> +#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL \
>>>>> "providing the dmesg log by booting with drm.debug=0xf"
>>>>
>>>> Space between URL and "providing"?
>>>
>>> If the following comment is accepted, then we need to change this
>>> sentence to:
>>>
>>> Please file bugs according to the instruction found at FDO_BUG_URL.
>>>
>>>>
>>>>>
>>>>> void
>>>>> diff --git a/drivers/gpu/drm/i915/i915_utils.h
>>>>> b/drivers/gpu/drm/i915/i915_utils.h
>>>>> index 04139ba1191e..13674b016092 100644
>>>>> --- a/drivers/gpu/drm/i915/i915_utils.h
>>>>> +++ b/drivers/gpu/drm/i915/i915_utils.h
>>>>> @@ -34,6 +34,8 @@
>>>>> struct drm_i915_private;
>>>>> struct timer_list;
>>>>>
>>>>> +#define FDO_BUG_URL
>>>>> "https://gitlab.freedesktop.org/drm/intel/issues/new?";
>>>>
>>>> Do we really need the question mark?
>>>
>>> We may want to point to
>>> https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-file-i915-bugs,
>>> don't you think?
>>
>> Does gitlab let you set the URL, or is it always autogenerated from the
>> title? Need to at least fix the "file file" there. ;)
>
> Martin feel free to update the patch with the final wording and links :)
> -Chris
>
Darn it, do I need to break my almost 5 year streak of not having a
single i915 patch :o?
Well, I guess now is a good time for this, I had a patch series I wanted
to contribute anyway.
Martin
pEpkey.asc
Description: pEpkey.asc
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH] drm/i915: Update bug URL to point at gitlab issues
On 02/12/2019 12:30, Jani Nikula wrote:
> On Mon, 25 Nov 2019, Chris Wilson wrote:
>> We are moving our issue tracking over from bugs.fd.o to gitlab.fd.o, so
>> update the user instructions accordingly.
>>
>> Signed-off-by: Chris Wilson
>> Cc: Martin Peres
>> Cc: Joonas Lahtinen
>> Cc: Rodrigo Vivi
>> Cc: Jani Nikula
>> Cc: sta...@vger.kernel.org
>> ---
>> drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
>> drivers/gpu/drm/i915/i915_utils.c | 3 +--
>> drivers/gpu/drm/i915/i915_utils.h | 2 ++
>> 3 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c
>> b/drivers/gpu/drm/i915/i915_gpu_error.c
>> index 2b30a45fa25c..1cf53fd4fe66 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
>> @@ -1817,7 +1817,7 @@ void i915_capture_error_state(struct drm_i915_private
>> *i915,
>> if (!xchg(&warned, true) &&
>> ktime_get_real_seconds() - DRIVER_TIMESTAMP < DAY_AS_SECONDS(180)) {
>> pr_info("GPU hangs can indicate a bug anywhere in the entire
>> gfx stack, including userspace.\n");
>> -pr_info("Please file a _new_ bug report on bugs.freedesktop.org
>> against DRI -> DRM/Intel\n");
>> +pr_info("Please file a _new_ bug report on " FDO_BUG_URL "\n");
>> pr_info("drm/i915 developers can then reassign to the right
>> component if it's not a kernel issue.\n");
>> pr_info("The GPU crash dump is required to analyze GPU hangs,
>> so please always attach it.\n");
>> pr_info("GPU crash dump saved to /sys/class/drm/card%d/error\n",
>> diff --git a/drivers/gpu/drm/i915/i915_utils.c
>> b/drivers/gpu/drm/i915/i915_utils.c
>> index c47261ae86ea..9b68b21becf1 100644
>> --- a/drivers/gpu/drm/i915/i915_utils.c
>> +++ b/drivers/gpu/drm/i915/i915_utils.c
>> @@ -8,8 +8,7 @@
>> #include "i915_drv.h"
>> #include "i915_utils.h"
>>
>> -#define FDO_BUG_URL "https://bugs.freedesktop.org/enter_bug.cgi?product=DRI";
>> -#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL " against DRM/Intel
>> " \
>> +#define FDO_BUG_MSG "Please file a bug at " FDO_BUG_URL \
>> "providing the dmesg log by booting with drm.debug=0xf"
>
> Space between URL and "providing"?
If the following comment is accepted, then we need to change this
sentence to:
Please file bugs according to the instruction found at FDO_BUG_URL.
>
>>
>> void
>> diff --git a/drivers/gpu/drm/i915/i915_utils.h
>> b/drivers/gpu/drm/i915/i915_utils.h
>> index 04139ba1191e..13674b016092 100644
>> --- a/drivers/gpu/drm/i915/i915_utils.h
>> +++ b/drivers/gpu/drm/i915/i915_utils.h
>> @@ -34,6 +34,8 @@
>> struct drm_i915_private;
>> struct timer_list;
>>
>> +#define FDO_BUG_URL "https://gitlab.freedesktop.org/drm/intel/issues/new?";
>
> Do we really need the question mark?
We may want to point to
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-file-i915-bugs,
don't you think?
Martin
>
> BR,
> Jani.
>
>> +
>> #undef WARN_ON
>> /* Many gcc seem to no see through this and fall over :( */
>> #if 0
>
pEpkey.asc
Description: pEpkey.asc
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✓ Fi.CI.IGT: success for cdclk consolidation and rework for BXT-TGL (rev6)
On 11/09/2019 09:16, Saarinen, Jani wrote: > Hi, > > >> -Original Message- >> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf >> Of Matt >> Roper >> Sent: keskiviikko 11. syyskuuta 2019 6.43 >> To: intel-gfx@lists.freedesktop.org >> Subject: Re: [Intel-gfx] ✓ Fi.CI.IGT: success for cdclk consolidation and >> rework for >> BXT-TGL (rev6) >> >> On Tue, Sep 10, 2019 at 11:55:40PM +, Patchwork wrote: >>> == Series Details == >>> >>> Series: cdclk consolidation and rework for BXT-TGL (rev6) >>> URL : https://patchwork.freedesktop.org/series/66365/ >>> State : success >>> >>> == Summary == >>> >>> CI Bug Log - changes from CI_DRM_6861_full -> Patchwork_14345_full >>> >>> >>> Summary >>> --- >>> >>> **SUCCESS** >>> >>> No regressions found. >>> >> >> Applied to dinq. Thanks Ville for the reviews. > Matt, this seems to break TGL now. > See: > http://gfx-ci.fi.intel.com/tree/drm-tip/CI_DRM_6864/fi-tgl-u/boot0.txt > WARN_ON_ONCE(!crtc_clock || max_dotclk < crtc_clock) > <4>[ 11.971515] WARNING: CPU: 6 PID: 331 at > drivers/gpu/drm/i915/display/intel_display.c:14556 skl_max_scale+0xa4/0xb0 > [i915] > > And > http://gfx-ci.fi.intel.com/tree/drm-tip/CI_DRM_6864/git-log-oneline.txt > Martin, is there bug already? https://bugs.freedesktop.org/show_bug.cgi?id=111641 Martin > > >> >> Matt >> >>> >>> >>> New tests >>> - >>> >>> New tests have been introduced between CI_DRM_6861_full and >> Patchwork_14345_full: >>> >>> ### New Piglit tests (7) ### >>> >>> * spec@arb_gpu_shader5@texturegather@vs-rgba-2-float-2darray: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegather@vs-rgba-3-float-2darray: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegatheroffset@vs-rgba-0-float-2darray: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegatheroffset@vs-rgba-0-float-2darray-const: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-1-float-2d: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-2-float-2d: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> * spec@arb_gpu_shader5@texturegatheroffsets@vs-rgba-3-float-2d: >>> - Statuses : 1 incomplete(s) >>> - Exec time: [0.0] s >>> >>> >>> >>> Known issues >>> >>> >>> Here are the changes found in Patchwork_14345_full that come from known >> issues: >>> >>> ### IGT changes ### >>> >>> Issues hit >>> >>> * igt@gem_busy@basic-hang-rcs0: >>> - shard-glk: [PASS][1] -> [INCOMPLETE][2] ([fdo#103359] / >>> [k.org#198133]) >>>[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> glk6/igt@gem_b...@basic-hang-rcs0.html >>>[2]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14345/shard-glk3/ig >>> t@gem_b...@basic-hang-rcs0.html >>> >>> * igt@gem_ctx_isolation@rcs0-s3: >>> - shard-apl: [PASS][3] -> [DMESG-WARN][4] ([fdo#108566]) +4 >>> similar issues >>>[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> apl4/igt@gem_ctx_isolat...@rcs0-s3.html >>>[4]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14345/shard-apl7/ig >>> t@gem_ctx_isolat...@rcs0-s3.html >>> >>> * igt@gem_exec_schedule@preempt-contexts-bsd2: >>> - shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#109276]) +14 similar >>> issues >>>[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> iclb4/igt@gem_exec_sched...@preempt-contexts-bsd2.html >>>[6]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14345/shard-iclb6/i >>> gt@gem_exec_sched...@preempt-contexts-bsd2.html >>> >>> * igt@gem_exec_schedule@preempt-hang-vebox: >>> - shard-iclb: [PASS][7] -> [INCOMPLETE][8] ([fdo#107713]) >>>[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> iclb1/igt@gem_exec_sched...@preempt-hang-vebox.html >>>[8]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14345/shard-iclb7/i >>> gt@gem_exec_sched...@preempt-hang-vebox.html >>> >>> * igt@gem_exec_schedule@reorder-wide-bsd: >>> - shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#111325]) +9 similar >>> issues >>>[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> iclb3/igt@gem_exec_sched...@reorder-wide-bsd.html >>>[10]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14345/shard-iclb4/i >>> gt@gem_exec_sched...@reorder-wide-bsd.html >>> >>> * igt@i915_pm_rpm@modeset-stress-extra-wait: >>> - shard-iclb: [PASS][11] -> [INCOMPLETE][12] ([fdo#107713] / >> [fdo#108840]) >>>[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6861/shard- >> iclb7/igt@i915_pm_...@modeset-stress
Re: [Intel-gfx] [PATCH v3 0/3] Send a hotplug when edid changes
On 19/08/2019 10:23, Lisovskiy, Stanislav wrote: > On Wed, 2019-08-07 at 23:07 +0200, Daniel Vetter wrote: >> On Wed, Aug 07, 2019 at 07:43:18AM +, Lisovskiy, Stanislav wrote: >>> On Tue, 2019-08-06 at 19:43 +0200, Daniel Vetter wrote: On Tue, Aug 6, 2019 at 4:06 PM Lisovskiy, Stanislav wrote: > > On Tue, 2019-08-06 at 15:51 +0200, Daniel Vetter wrote: >> On Tue, Aug 06, 2019 at 03:55:48PM +0300, Stanislav Lisovskiy >> wrote: >>> This series introduce to drm a way to determine if >>> something >>> else >>> except connection_status had changed during probing, which >>> can be used by other drivers as well. Another i915 specific >>> part >>> uses this approach to determine if edid had changed without >>> changing the connection status and send a hotplug event. >> >> Did you read through the entire huge thread on all this (with >> I >> think >> Paul, Pekka, Ram and some others)? I feel like this is mostly >> taking >> that >> idea, but not taking a lot of the details we've discussed >> there. >> Specifically I'm not sure how userspace should handle this >> without >> also >> exposing the epoch counter, or at least generating a hotplug >> event >> for the >> specific connector. All that and more we discussed there. >> >> And then there's the follow-up question: What's the userspace >> for >> this? >> Existing expectations are a minefield here, so even if you >> don't >> plan >> to >> change userspace we need to know what this is aimed for, and >> see >> above I >> don't think this is possible to use without userspace changes >> ... > > Yes, sure I agree about userspace. However I guess we must > start > from > something at least. > I think I have seen some discussion regarding exposing this > epoch > counter as a property. Was even implementing this at some point > but > didn't dare to send to mailing list :) > > My idea was just to expose this epoch counter as a drm > property, to > let > userspace then to figure out, what has happened, as imho adding > different events for this and that is a bit of an overkill and > brings > additional complexity.. Adding Ram and link to the (warning, huge!) thread: > https://patchwork.freedesktop.org/patch/303905/?series=57232&rev=9 > However, please let me know, what do you think we should do for > userspace. That seems backwards, since this is an uapi change I'd expect you're solving some specific issue in some specific userspace? If we're doing this just because I'm not really following. >>> >>> Specifically, I'm solving an issue of changed edid during suspend, >>> like >>> we for example have in kms_chamelium hotplug tests(some of which >>> now >>> fail because of that). >>> So even if connection status hasn't changed, we still need to send >>> hotplug event and userspace needs to be able to understand that >>> something had changed and whether we need to do a full reprobe or >>> not. >>> Epoch counter property would be responsible for this. >>> As I understand in general there might be other connector updates, >>> except edid which we need propagate in a similar way. >> >> So igt isn't valid userspace (it's just good testcases). Can we repro >> the >> same on real userspace? Does this work with real userspace? We've had >> userspace which tries to be clever and filters out what looks like >> redundant hotplug events. And then gets it wrong in cases like this. >> >> Also, we've had forever an unconditional uevent on resume, exactly >> because >> anything could have changed. Did we loose this one on the way >> somewhere? >> Or maybe I misremember ... >> >> If all we care about is resume re-adding that uncondtional uevent on >> resume is going to be a lot easier than this here. >> -Daniel > > Sorry for long reply(was on vacation), that is a good question > regarding reproducing this in real life scenario. My obvious guess > was to suspend the machine and meanwhile change connected display to > another one. However this situation seems to be already handled by > kernel nicely(tried few times and we always get a hotplug event). So > that edid change during suspend chamelium test case seems to be > a bit different. I will talk to our guys who wrote this about what is > the real life scenario for this, because I'm now curious as well. Thanks Daniel for the feedback. I also now wonder why our IGT test (chamelium-based) does not pass if a uevent is sent on resume automatically and all the test is expecting is a uevent... Martin > > - Stanislav > >> >> >>> >>> -Stanislav >>> Cheers, Daniel > > > -Stanislav > > >> -Daniel >> >>> >>> Stanislav Lisovskiy (3): >>> drm: Add helper to compare edids. >>> drm
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and fixes (rev5)
On 28/06/2019 18:06, Shankar, Uma wrote: > > >> -Original Message- >> From: Patchwork [mailto:patchw...@emeril.freedesktop.org] >> Sent: Friday, June 28, 2019 8:34 PM >> To: Shankar, Uma >> Cc: intel-gfx@lists.freedesktop.org >> Subject: ✗ Fi.CI.BAT: failure for Extend BT2020 support in iCSC and fixes >> (rev5) >> >> == Series Details == >> >> Series: Extend BT2020 support in iCSC and fixes (rev5) >> URL : https://patchwork.freedesktop.org/series/60480/ >> State : failure >> >> == Summary == >> >> CI Bug Log - changes from CI_DRM_6379 -> Patchwork_13466 >> >> >> Summary >> --- >> >> **FAILURE** >> >> Serious unknown changes coming with Patchwork_13466 absolutely need to be >> verified manually. >> >> If you think the reported changes have nothing to do with the changes >> introduced in Patchwork_13466, 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/Patchwork_13466/ >> >> Possible new issues >> --- >> >> Here are the unknown changes that may have been introduced in >> Patchwork_13466: >> >> ### IGT changes ### >> >> Possible regressions >> >> * igt@i915_selftest@live_mman: >>- fi-bsw-n3050: [PASS][1] -> [DMESG-WARN][2] >> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-bsw- >> n3050/igt@i915_selftest@live_mman.html >> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-bsw- >> n3050/igt@i915_selftest@live_mman.html >> > > Hi Martin, > This doesn't seem to be related to this change. > > Please check once and update this. New bug filed: https://bugs.freedesktop.org/show_bug.cgi?id=111037 I've queued re-reporting which should start the shards result. Thanks! Martin > > Thanks & Regards, > Uma Shankar > >> Known issues >> >> >> Here are the changes found in Patchwork_13466 that come from known issues: >> >> ### IGT changes ### >> >> Issues hit >> >> * igt@i915_pm_rpm@module-reload: >>- fi-kbl-r: [PASS][3] -> [DMESG-WARN][4] ([fdo#111012]) >> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-kbl- >> r/igt@i915_pm_...@module-reload.html >> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-kbl- >> r/igt@i915_pm_...@module-reload.html >> >> >> Possible fixes >> >> * igt@gem_mmap_gtt@basic-write-gtt-no-prefault: >>- fi-icl-u3: [DMESG-WARN][5] ([fdo#107724]) -> [PASS][6] +1 >> similar issue >> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-icl- >> u3/igt@gem_mmap_...@basic-write-gtt-no-prefault.html >> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-icl- >> u3/igt@gem_mmap_...@basic-write-gtt-no-prefault.html >> >> * igt@kms_frontbuffer_tracking@basic: >>- fi-hsw-peppy: [DMESG-WARN][7] ([fdo#102614]) -> [PASS][8] >> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6379/fi-hsw- >> peppy/igt@kms_frontbuffer_track...@basic.html >> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-hsw- >> peppy/igt@kms_frontbuffer_track...@basic.html >> >> >> [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614 >> [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 >> [fdo#111012]: https://bugs.freedesktop.org/show_bug.cgi?id=111012 >> >> >> Participating hosts (51 -> 45) >> -- >> >> Additional (2): fi-icl-dsi fi-skl-gvtdvm >> Missing(8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks >> fi-bsw-cyan fi-icl- >> y fi-byt-clapper fi-bdw-samus >> >> >> Build changes >> - >> >> * Linux: CI_DRM_6379 -> Patchwork_13466 >> >> CI_DRM_6379: 12f8aba06508afb9b668a2496b2fb296ed21e377 @ >> git://anongit.freedesktop.org/gfx-ci/linux >> IGT_5072: 5f6cf7070b249975bac4d747a9c44d81c94c4381 @ >> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools >> Patchwork_13466: a1cff9784bf59b14027b36876e4aaff7ab8b9599 @ >> git://anongit.freedesktop.org/gfx-ci/linux >> >> >> == Kernel 32bit build == >> >> Warning: Kernel 32bit buildtest failed: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/build_32bit.log >> >> CALLscripts/checksyscalls.sh >> CALLscripts/atomic/check-atomics.sh >> CHK include/generated/compile.h >> Kernel: arch/x86/boot/bzImage is ready (#1) >> Building modules, stage 2. >> MODPOST 112 modules >> ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! >> ERROR: "__divdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! >> scripts/Makefile.modpost:91: recipe for target '__modpost' failed >> make[1]: *** [__modpost] Error 1 >> Makefile:1287: recipe for target 'modules' failed >> make: *** [modules] Error 2 >> >> >> == Linux commits == >> >> a1cff9784bf5 drm/i915/icl: Fixed Input CSC Co-efficients for BT601/709 >> 3caa5b4db153 drm/i915/icl: Fix Y pre-offset for Full Range YCb
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Enable Multi-segmented-gamma for ICL (rev4)
On 13/06/2019 10:39, Shankar, Uma wrote: > > >> -Original Message- >> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of >> Patchwork >> Sent: Thursday, June 13, 2019 12:36 PM >> To: Sharma, Shashank >> Cc: intel-gfx@lists.freedesktop.org >> Subject: [Intel-gfx] ✗ Fi.CI.IGT: failure for Enable Multi-segmented-gamma >> for ICL >> (rev4) >> >> == Series Details == >> >> Series: Enable Multi-segmented-gamma for ICL (rev4) >> URL : https://patchwork.freedesktop.org/series/60126/ >> State : failure >> >> == Summary == >> >> CI Bug Log - changes from CI_DRM_6242_full -> Patchwork_13248_full >> >> >> Summary >> --- >> >> **FAILURE** >> >> Serious unknown changes coming with Patchwork_13248_full absolutely need to >> be >> verified manually. >> >> If you think the reported changes have nothing to do with the changes >> introduced in Patchwork_13248_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_13248_full: >> >> ### IGT changes ### >> >> Possible regressions >> >> * igt@kms_color@pipe-b-ctm-0-25: >>- shard-iclb: [PASS][1] -> [FAIL][2] +4 similar issues >> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> iclb3/igt@kms_co...@pipe-b-ctm-0-25.html >> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> iclb2/igt@kms_co...@pipe-b-ctm-0-25.html >> > > Hi Martin, > These are the failures which we get when we enabled multi segment gamma due > to the crc > limitations (already in discussion with hardware design and validation team). > As discussed, > can we mark these as known issues and merge the multi segment gamma series. > > We will be tracking the hardware CRC issues separately and will work with > hardware design teams to > debug that. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110920 Acked-by: Martin Peres Martin > > Thanks & Regards, > Uma Shankar > >> Known issues >> >> >> Here are the changes found in Patchwork_13248_full that come from known >> issues: >> >> ### IGT changes ### >> >> Issues hit >> >> * igt@gem_exec_schedule@preemptive-hang-bsd2: >>- shard-kbl: [PASS][3] -> [INCOMPLETE][4] ([fdo#103665]) >> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> kbl7/igt@gem_exec_sched...@preemptive-hang-bsd2.html >> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> kbl3/igt@gem_exec_sched...@preemptive-hang-bsd2.html >> >> * igt@gem_tiled_swapping@non-threaded: >>- shard-iclb: [PASS][5] -> [FAIL][6] ([fdo#108686]) >> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> iclb2/igt@gem_tiled_swapp...@non-threaded.html >> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> iclb7/igt@gem_tiled_swapp...@non-threaded.html >>- shard-glk: [PASS][7] -> [DMESG-WARN][8] ([fdo#108686]) >> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> glk7/igt@gem_tiled_swapp...@non-threaded.html >> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> glk9/igt@gem_tiled_swapp...@non-threaded.html >> >> * igt@i915_pm_rpm@i2c: >>- shard-skl: [PASS][9] -> [SKIP][10] ([fdo#109271]) +2 similar >> issues >> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> skl5/igt@i915_pm_...@i2c.html >> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> skl6/igt@i915_pm_...@i2c.html >> >> * igt@kms_color@pipe-c-degamma: >>- shard-iclb: [PASS][11] -> [FAIL][12] ([fdo#104782]) +2 similar >> issues >> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/shard- >> iclb2/igt@kms_co...@pipe-c-degamma.html >> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/shard- >> iclb7/igt@kms_co...@pipe-c-degamma.html >> >> * igt@kms_cursor_crc@pipe-a-cursor-128x128-onscreen: >>- shard-snb: [PASS][13] -> [SKIP][14] ([fdo#109271]) +1 similar >> issue >> [13]: https://intel-gfx-ci.01.org/tree/d
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable Multi-segmented-gamma for ICL (rev4)
On 12/06/2019 15:05, Shankar, Uma wrote: > > >> -Original Message----- >> From: Peres, Martin >> Sent: Wednesday, June 12, 2019 3:51 PM >> To: Shankar, Uma ; intel-gfx@lists.freedesktop.org >> Cc: Sharma, Shashank >> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable >> Multi-segmented-gamma for ICL >> (rev4) >> >> On 12/06/2019 11:58, Shankar, Uma wrote: >>> >>> >>>> -Original Message- >>>> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On >>>> Behalf Of Patchwork >>>> Sent: Wednesday, June 12, 2019 12:27 PM >>>> To: Sharma, Shashank >>>> Cc: intel-gfx@lists.freedesktop.org >>>> Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable >>>> Multi-segmented-gamma for ICL >>>> (rev4) >>>> >>>> == Series Details == >>>> >>>> Series: Enable Multi-segmented-gamma for ICL (rev4) >>>> URL : https://patchwork.freedesktop.org/series/60126/ >>>> State : failure >>>> >>>> == Summary == >>>> >>>> CI Bug Log - changes from CI_DRM_6242 -> Patchwork_13248 >>>> >>>> >>>> Summary >>>> --- >>>> >>>> **FAILURE** >>>> >>>> Serious unknown changes coming with Patchwork_13248 absolutely need >>>> to be verified manually. >>>> >>>> If you think the reported changes have nothing to do with the >>>> changes introduced in Patchwork_13248, 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/Patchwork_13248/ >>>> >>>> Possible new issues >>>> --- >>>> >>>> Here are the unknown changes that may have been introduced in >> Patchwork_13248: >>>> >>>> ### IGT changes ### >>>> >>>> Possible regressions >>>> >>>> * igt@i915_module_load@reload-with-fault-injection: >>>>- fi-skl-gvtdvm: [PASS][1] -> [INCOMPLETE][2] >>>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-skl- >>>> gvtdvm/igt@i915_module_l...@reload-with-fault-injection.html >>>> [2]: >>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-skl- >>>> gvtdvm/igt@i915_module_l...@reload-with-fault-injection.html >>> >>> Hi Martin, >>> Getting this failure on BAT run in intel-gfx, can you help enable a CI run >>> for full IGT >> scan. >>> I am getting BAT passing on trybot and this doesn't seem to be related to >>> the >> changes here. >> >> Thanks for reporting the issue. I mapped this failure to this bug: >> https://bugs.freedesktop.org/show_bug.cgi?id=110343 >> >> I am sure the GEM team will be happy to take another look at this issue :D > > Thanks Martin for your help here. You are welcome, just doing my job ;) Martin > > Regards, > Uma Shankar > >> Martin >> >>> >>> Thanks & Regards, >>> Uma Shankar >>> >>>> >>>> Known issues >>>> >>>> >>>> Here are the changes found in Patchwork_13248 that come from known issues: >>>> >>>> ### IGT changes ### >>>> >>>> Issues hit >>>> >>>> * igt@gem_exec_reloc@basic-cpu-noreloc: >>>>- fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]) +1 >>>> similar issue >>>> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-icl- >>>> u3/igt@gem_exec_re...@basic-cpu-noreloc.html >>>> [4]: >>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-icl- >>>> u3/igt@gem_exec_re...@basic-cpu-noreloc.html >>>> >>>> * igt@prime_vgem@basic-fence-flip: >>>>- fi-ilk-650: [PASS][5] -> [DMESG-WARN][6] ([fdo#106387]) +2 >>>> similar issues >>>> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-ilk- >>>> 650/igt@prime_v...@basic-fence-flip.html >>>> [6]: >>>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-ilk- >>>> 650/igt@prime_v...@basic-fence-flip
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable Multi-segmented-gamma for ICL (rev4)
On 12/06/2019 11:58, Shankar, Uma wrote:
>
>
>> -Original Message-
>> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
>> Patchwork
>> Sent: Wednesday, June 12, 2019 12:27 PM
>> To: Sharma, Shashank
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enable Multi-segmented-gamma
>> for ICL
>> (rev4)
>>
>> == Series Details ==
>>
>> Series: Enable Multi-segmented-gamma for ICL (rev4)
>> URL : https://patchwork.freedesktop.org/series/60126/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_6242 -> Patchwork_13248
>>
>>
>> Summary
>> ---
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with Patchwork_13248 absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_13248, 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/Patchwork_13248/
>>
>> Possible new issues
>> ---
>>
>> Here are the unknown changes that may have been introduced in
>> Patchwork_13248:
>>
>> ### IGT changes ###
>>
>> Possible regressions
>>
>> * igt@i915_module_load@reload-with-fault-injection:
>>- fi-skl-gvtdvm: [PASS][1] -> [INCOMPLETE][2]
>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-skl-
>> gvtdvm/igt@i915_module_l...@reload-with-fault-injection.html
>> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-skl-
>> gvtdvm/igt@i915_module_l...@reload-with-fault-injection.html
>
> Hi Martin,
> Getting this failure on BAT run in intel-gfx, can you help enable a CI run
> for full IGT scan.
> I am getting BAT passing on trybot and this doesn't seem to be related to the
> changes here.
Thanks for reporting the issue. I mapped this failure to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=110343
I am sure the GEM team will be happy to take another look at this issue :D
Martin
>
> Thanks & Regards,
> Uma Shankar
>
>>
>> Known issues
>>
>>
>> Here are the changes found in Patchwork_13248 that come from known issues:
>>
>> ### IGT changes ###
>>
>> Issues hit
>>
>> * igt@gem_exec_reloc@basic-cpu-noreloc:
>>- fi-icl-u3: [PASS][3] -> [DMESG-WARN][4] ([fdo#107724]) +1
>> similar issue
>> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-icl-
>> u3/igt@gem_exec_re...@basic-cpu-noreloc.html
>> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-icl-
>> u3/igt@gem_exec_re...@basic-cpu-noreloc.html
>>
>> * igt@prime_vgem@basic-fence-flip:
>>- fi-ilk-650: [PASS][5] -> [DMESG-WARN][6] ([fdo#106387]) +2
>> similar issues
>> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-ilk-
>> 650/igt@prime_v...@basic-fence-flip.html
>> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-ilk-
>> 650/igt@prime_v...@basic-fence-flip.html
>>
>>
>> Possible fixes
>>
>> * igt@i915_module_load@reload:
>>- fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8]
>> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-icl-
>> u3/igt@i915_module_l...@reload.html
>> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-icl-
>> u3/igt@i915_module_l...@reload.html
>>
>> * igt@i915_module_load@reload-with-fault-injection:
>>- fi-bsw-kefka: [DMESG-WARN][9] -> [PASS][10]
>> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-bsw-
>> kefka/igt@i915_module_l...@reload-with-fault-injection.html
>> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-bsw-
>> kefka/igt@i915_module_l...@reload-with-fault-injection.html
>>
>> * igt@kms_chamelium@hdmi-hpd-fast:
>>- fi-kbl-7500u: [FAIL][11] ([fdo#109485]) -> [PASS][12]
>> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6242/fi-kbl-
>> 7500u/igt@kms_chamel...@hdmi-hpd-fast.html
>> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13248/fi-kbl-
>> 7500u/igt@kms_chamel...@hdmi-hpd-fast.html
>>
>>
>> {name}: This element is suppressed. This means it is ignored when computing
>> the status of the difference (SUCCESS, WARNING, or FAILURE).
>>
>> [fdo#106387]: https://bugs.freedesktop.org/show_bug.cgi?id=106387
>> [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
>> [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
>> [fdo#108602]: https://bugs.freedesktop.org/show_bug.cgi?id=108602
>> [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
>>
>>
>> Participating hosts (53 -> 47)
>> --
>>
>> Additional (1): fi-bsw-n3050
>> Missing(7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks
>> fi-bsw-cyan fi-
>> byt-clapper fi-bdw-samus
>>
>>
>> Build changes
>> -
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add HDR Metadata Parsing and handling in DRM layer (rev10)
On 17/05/2019 16:04, Ville Syrjälä wrote: > On Thu, May 16, 2019 at 01:18:15PM +, Shankar, Uma wrote: >> >> > -Original Message- > From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com] > Sent: Thursday, May 16, 2019 1:02 AM > To: Shankar, Uma > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add HDR Metadata > Parsing and handling in DRM layer (rev10) > > On Wed, May 15, 2019 at 08:59:37AM +, Shankar, Uma wrote: >> >> >>> -Original Message- >>> From: Patchwork [mailto:patchw...@emeril.freedesktop.org] >>> Sent: Wednesday, May 15, 2019 6:54 AM >>> To: Shankar, Uma >>> Cc: intel-gfx@lists.freedesktop.org >>> Subject: ✗ Fi.CI.IGT: failure for Add HDR Metadata Parsing and >>> handling in DRM layer >>> (rev10) >>> >>> == Series Details == >>> >>> Series: Add HDR Metadata Parsing and handling in DRM layer (rev10) >>> URL : https://patchwork.freedesktop.org/series/25091/ >>> State : failure >>> >>> == Summary == >>> >>> CI Bug Log - changes from CI_DRM_6081_full -> Patchwork_13017_full >>> >>> >>> Summary >>> --- >>> >>> **FAILURE** >>> >>> Serious unknown changes coming with Patchwork_13017_full >>> absolutely need to be verified manually. >>> >>> If you think the reported changes have nothing to do with the >>> changes introduced in Patchwork_13017_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_13017_full: >>> >>> ### IGT changes ### >>> >>> Possible regressions >>> >>> * igt@gem_exec_suspend@basic-s3: >>>- shard-iclb: [PASS][1] -> [SKIP][2] +43 similar issues >>> [1]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6081/shard- >>> iclb6/igt@gem_exec_susp...@basic-s3.html >>> [2]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13017/shard- >>> iclb5/igt@gem_exec_susp...@basic-s3.html >>> >>> * igt@kms_prop_blob@invalid-set-prop-any: >>>- shard-iclb: [PASS][3] -> [FAIL][4] >>> [3]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6081/shard- >>> iclb6/igt@kms_prop_b...@invalid-set-prop-any.html >>> [4]: >>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13017/shard- >>> iclb5/igt@kms_prop_b...@invalid-set-prop-any.html >>> >> >> Hi Martin, >> These issues are unrelated to the changes made in this series. Can >> you please have a look and confirm. > > The kms_prop fails at least are real. Probably due to the bogus > function arguements to the replace_blob() thing I pointed out. The CI IGT have a clean PASS now. >>> >>> You mean it went from FAIL to PASS on its own? Why did that happen? >> >> It was giving a PASS on earlier version v9 with same changes. But on v10 it >> gave >> this error. I was thinking it was re-run, on checking with Jani N he >> clarified that it >> was re-reported. > > Did you even try to analyse the failures at all or just assumed > they were bogus and asked for a rerun? > > I'm still in the dark as to why these failures were deemed > to not be relevant. > This is completely unrelated to this series. We have a bug for this issue already, so no worries there. However, thanks for caring so much about this. I should have clarified what I was doing... - Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gen11: enable support for headerless msgs (rev4)
On 06/05/2019 23:30, Kim, Dongwon wrote: > This doesn't seem to be a valid failure. I just reran the test using > trybot and there were no failures. > > https://lists.freedesktop.org/archives/intel-gfx-trybot/2019-May/071989.html I reported this bug two days ago and added it to cibuglog, this is why you don't see it anymore. This is why asking me to re-report runs is better than forcing a re-run, since it does not take valuable time... but I also don't want to be blocking you :D Cheers, Martin > > On Thu, Apr 25, 2019 at 07:54:51AM +, > intel-gfx-requ...@lists.freedesktop.org wrote: >> Date: Thu, 25 Apr 2019 07:54:50 - >> From: Patchwork >> To: "Chris Wilson" >> Cc: intel-gfx@lists.freedesktop.org >> Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gen11: enable >> support for headerless msgs (rev4) >> Message-ID: <20190425075450.550.19...@emeril.freedesktop.org> >> Content-Type: text/plain; charset="utf-8" >> >> == Series Details == >> >> Series: drm/i915/gen11: enable support for headerless msgs (rev4) >> URL : https://patchwork.freedesktop.org/series/59839/ >> State : failure >> >> == Summary == >> >> CI Bug Log - changes from CI_DRM_5995 -> Patchwork_12869 >> >> >> Summary >> --- >> >> **FAILURE** >> >> Serious unknown changes coming with Patchwork_12869 absolutely need to be >> verified manually. >> >> If you think the reported changes have nothing to do with the changes >> introduced in Patchwork_12869, please notify your bug team to allow them >> to document this new failure mode, which will reduce false positives in CI. >> >> External URL: >> https://patchwork.freedesktop.org/api/1.0/series/59839/revisions/4/mbox/ >> >> Possible new issues >> --- >> >> Here are the unknown changes that may have been introduced in >> Patchwork_12869: >> >> ### IGT changes ### >> >> Possible regressions >> >> * igt@gem_exec_suspend@basic-s3: >> - fi-apl-guc: NOTRUN -> [DMESG-WARN][1] >>[1]: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12869/fi-apl-guc/igt@gem_exec_susp...@basic-s3.html >> >> >> Known issues >> >> >> Here are the changes found in Patchwork_12869 that come from known issues: >> >> ### IGT changes ### >> >> Issues hit >> >> * igt@gem_exec_suspend@basic-s4-devices: >> - fi-blb-e6850: [PASS][2] -> [INCOMPLETE][3] ([fdo#107718]) >>[2]: >> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5995/fi-blb-e6850/igt@gem_exec_susp...@basic-s4-devices.html >>[3]: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12869/fi-blb-e6850/igt@gem_exec_susp...@basic-s4-devices.html >> >> * igt@i915_selftest@live_contexts: >> - fi-bdw-gvtdvm: [PASS][4] -> [DMESG-FAIL][5] ([fdo#110235 ]) >>[4]: >> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5995/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html >>[5]: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12869/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html >> >> >> [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718 >> [fdo#110235 ]: https://bugs.freedesktop.org/show_bug.cgi?id=110235 >> >> >> Participating hosts (32 -> 42) >> -- >> >> Additional (15): fi-bxt-dsi fi-skl-gvtdvm fi-bsw-n3050 fi-byt-j1900 >> fi-skl-6770hq fi-apl-guc fi-snb-2520m fi-byt-clapper fi-bxt-j4205 fi-icl-u3 >> fi-pnv-d510 fi-icl-y fi-byt-n2820 fi-bsw-kefka fi-skl-6700k2 >> Missing(5): fi-kbl-soraka fi-ilk-m540 fi-bsw-cyan fi-ctg-p8600 >> fi-bdw-samus >> >> >> Build changes >> - >> >> * Linux: CI_DRM_5995 -> Patchwork_12869 >> >> CI_DRM_5995: 290f6892805fb22466c77e373ffd4c8f9e028f7f @ >> git://anongit.freedesktop.org/gfx-ci/linux >> IGT_4963: 11e10bc575516c56978640fcc697c27f277c660a @ >> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools >> Patchwork_12869: 95faef437aa7e6333a2bef8134a5b3eee82f68c1 @ >> git://anongit.freedesktop.org/gfx-ci/linux >> >> >> == Linux commits == >> >> 95faef437aa7 drm/i915/gen11: enable support for headerless msgs >> >> == Logs == >> >> For more details see: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12869/ >> >> >> -- >> >> Subject: Digest Footer >> >> ___ >> Intel-gfx mailing list >> Intel-gfx@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx >> >> -- >> >> End of Intel-gfx Digest, Vol 135, Issue 507 >> *** > - Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibit
Re: [Intel-gfx] [PATCH v2] drm/i915: Corrupt DSI picture fix for GeminiLake
On 30/04/2019 11:01, Lisovskiy, Stanislav wrote:
> On Tue, 2019-04-30 at 10:43 +0300, Jani Nikula wrote:
>> On Tue, 30 Apr 2019, Stanislav Lisovskiy <
>> stanislav.lisovs...@intel.com> wrote:
>>> Currently due to regression CI machine
>>> displays show corrupt picture.
>>> Problem is when CDCLK is as low as 79200, picture gets
>>> unstable, while DSI and DE pll values were
>>> confirmed to be correct.
>>> Limiting to 158400 as agreed with Ville.
>>>
>>> We could not come up with any better solution
>>> yet, as PLL divider values both for MIPI(DSI PLL) and
>>> CDCLK(DE PLL) are correct, however seems that due to some
>>> boundary conditions, when clocking is too low we get
>>> wrong timings for DSI display.
>>> Similar workaround exists for VLV though, so just
>>> took similar condition into use. At least that way
>>> GLK platform will start to be usable again, with
>>> current drm-tip.
>>>
>>> v2: Fixed commit subject as suggested.
>>>
>>> Signed-off-by: Stanislav Lisovskiy
>>> Acked-by: Ville Syrjälä
>>
>> Do we have a bugzilla link?
>>
>> BR,
>> Jani.
>
> No, or at least I'm not aware of. I just got a machine from CI for
> investigation :) I guess it might be worth to create a bug for that.
>
>
> Martin: do we have a bug for CI GLK issue?
No idea. Check it out:
http://gfx-ci.fi.intel.com/cibuglog-ng/results/knownfailures?query=machine_name+%3D+%27fi-glk-dsi%27+AND+NOT+status_name+%3D+%27skip%27
This possibly could explain all the CRC mismatches we get on GLK-dsi?
Time will tell.
Martin
>
> -Stanislav
>
>>
>>
>>> ---
>>> drivers/gpu/drm/i915/intel_cdclk.c | 9 +
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_cdclk.c
>>> b/drivers/gpu/drm/i915/intel_cdclk.c
>>> index ae40a8679314..2b23f8500362 100644
>>> --- a/drivers/gpu/drm/i915/intel_cdclk.c
>>> +++ b/drivers/gpu/drm/i915/intel_cdclk.c
>>> @@ -2277,6 +2277,15 @@ int intel_crtc_compute_min_cdclk(const
>>> struct intel_crtc_state *crtc_state)
>>> IS_VALLEYVIEW(dev_priv))
>>> min_cdclk = max(32, min_cdclk);
>>>
>>> + /*
>>> +* On Geminilake once the CDCLK gets as low as 79200
>>> +* picture gets unstable, despite that values are
>>> +* correct for DSI PLL and DE PLL.
>>> +*/
>>> + if (intel_crtc_has_type(crtc_state, INTEL_OUTPUT_DSI) &&
>>> + IS_GEMINILAKE(dev_priv))
>>> + min_cdclk = max(158400, min_cdclk);
>>> +
>>> if (min_cdclk > dev_priv->max_cdclk_freq) {
>>> DRM_DEBUG_KMS("required cdclk (%d kHz) exceeds max (%d
>>> kHz)\n",
>>> min_cdclk, dev_priv->max_cdclk_freq);
>>
>>
>
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v2] Core-for-CI:ICL_only Disable ACPI idle driver
On 09/04/2019 18:49, Wysocki, Rafael J wrote:
> On 4/9/2019 8:29 AM, Anshuman Gupta wrote:
>> There were few system hung observed while running i915_pm_rpm igt test.
>> FDO https://bugs.freedesktop.org/show_bug.cgi?id=108840
>> Root cause is believed to due to page fault in ACPI idle driver.
>> (FDO comment 18).
>> It has been suggested by Daniel Vetter to disable ACPI idle
>> driver for Core-for-CI, only for ICL.
>>
>> This hacky patch is only for ICL processor and for Core-for-CI branch.
>>
>> v2: Fixed compilation errors raised by lkp.
>> commit message improvement.
>>
>> Cc: martin.pe...@intel.com
>> Cc: daniel.vet...@intel.com
>>
>> Signed-off-by: Anshuman Gupta
>
> This is fine only as long as it doesn't anywhere close to the mainline.
>
> If ACPI idle crashes on new Intel HW, it needs to be fixed to work with
> it instead of refusing to work on it.\
Yes, this is the point of topic/core-for-ci:
https://cgit.freedesktop.org/drm/drm-intel/log/?h=topic/core-for-CI
I'll need to unblock the execution of the shards by filing a bug for the
issue caught by BAT, and when we get a green FULL results, we'll be good
to merge.
Martin
>
>> ---
>> drivers/acpi/processor_driver.c | 18 +-
>> 1 file changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/processor_driver.c
>> b/drivers/acpi/processor_driver.c
>> index 9d6aff2..ee842a2f 100644
>> --- a/drivers/acpi/processor_driver.c
>> +++ b/drivers/acpi/processor_driver.c
>> @@ -35,6 +35,12 @@
>>
>> #include
>>
>> +/* Only for Core-for-CI so don't want ia64 to fail compilation.*/
>> +#ifdef CONFIG_X86
>> +#include
>> +#include
>> +#endif
>> +
>> #include "internal.h"
>>
>> #define ACPI_PROCESSOR_NOTIFY_PERFORMANCE 0x80
>> @@ -58,6 +64,13 @@ static const struct acpi_device_id processor_device_ids[]
>> = {
>> };
>> MODULE_DEVICE_TABLE(acpi, processor_device_ids);
>>
>> +#define ICPU(model) { X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, }
>> +static const struct x86_cpu_id intel_cpu_ids[] = {
>> +ICPU(INTEL_FAM6_ICELAKE_MOBILE),/* ICL */
>> +{}
>> +};
>> +MODULE_DEVICE_TABLE(x86cpu, intel_cpu_ids);
>> +
>> static struct device_driver acpi_processor_driver = {
>> .name = "processor",
>> .bus = &cpu_subsys,
>> @@ -226,6 +239,7 @@ static inline void acpi_pss_perf_exit(struct
>> acpi_processor *pr,
>> static int __acpi_processor_start(struct acpi_device *device)
>> {
>> struct acpi_processor *pr = acpi_driver_data(device);
>> +const struct x86_cpu_id *id;
>> acpi_status status;
>> int result = 0;
>>
>> @@ -239,7 +253,9 @@ static int __acpi_processor_start(struct acpi_device
>> *device)
>> if (result && !IS_ENABLED(CONFIG_ACPI_CPU_FREQ_PSS))
>> dev_dbg(&device->dev, "CPPC data invalid or not present\n");
>>
>> -if (!cpuidle_get_driver() || cpuidle_get_driver() == &acpi_idle_driver)
>> +id = x86_match_cpu(intel_cpu_ids);
>> +if (!id && (!cpuidle_get_driver() || cpuidle_get_driver() ==
>> +&acpi_idle_driver))
>> acpi_processor_power_init(pr);
>>
>> result = acpi_pss_perf_init(pr, device);
>
>
>
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe id following atomic guidelines (rev2)
On 03/12/2018 22:55, Vivi, Rodrigo wrote:
> On Mon, Dec 03, 2018 at 04:29:17AM -0800, Peres, Martin wrote:
>> On 30/11/2018 19:27, Vivi, Rodrigo wrote:
>>> On Fri, Nov 30, 2018 at 03:04:40PM +0200, Martin Peres wrote:
>>>>
>>>>
>>>> On 29/11/2018 19:36, Rodrigo Vivi wrote:
>>>>> On Wed, Nov 28, 2018 at 11:52:49PM -0800, Saarinen, Jani wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> -Original Message-
>>>>>>> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On
>>>>>>> Behalf Of
>>>>>>> Rodrigo Vivi
>>>>>>> Sent: torstai 29. marraskuuta 2018 8.18
>>>>>>> To: Souza, Jose
>>>>>>> Cc: intel-gfx@lists.freedesktop.org
>>>>>>> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Get
>>>>>>> pipe id
>>>>>>> following atomic guidelines (rev2)
>>>>>>>
>>>>>>> On Wed, Nov 28, 2018 at 02:13:12PM -0800, Souza, Jose wrote:
>>>>>>>> On Wed, 2018-11-28 at 21:02 +, Patchwork wrote:
>>>>>>>>> == Series Details ==
>>>>>>>>>
>>>>>>>>> Series: drm/i915/psr: Get pipe id following atomic guidelines (rev2)
>>>>>>>>> URL : https://patchwork.freedesktop.org/series/53132/
>>>>>>>>> State : failure
>>>>>>>>>
>>>>>>>>> == Summary ==
>>>>>>>>>
>>>>>>>>> CI Bug Log - changes from CI_DRM_5216 -> Patchwork_10934
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Summary
>>>>>>>>> ---
>>>>>>>>>
>>>>>>>>> **FAILURE**
>>>>>>>>>
>>>>>>>>> Serious unknown changes coming with Patchwork_10934 absolutely
>>>>>>>>> need to be
>>>>>>>>> verified manually.
>>>>>>>>>
>>>>>>>>> If you think the reported changes have nothing to do with the
>>>>>>>>> changes
>>>>>>>>> introduced in Patchwork_10934, please notify your bug team to
>>>>>>>>> allow them
>>>>>>>>> to document this new failure mode, which will reduce false
>>>>>>>>> positives in CI.
>>>>>>>>>
>>>>>>>>> External URL:
>>>>>>>>> https://patchwork.freedesktop.org/api/1.0/series/53132/revisions/2/m
>>>>>>>>> box/
>>>>>>>>>
>>>>>>>>> Possible new issues
>>>>>>>>> ---
>>>>>>>>>
>>>>>>>>> Here are the unknown changes that may have been introduced in
>>>>>>>>> Patchwork_10934:
>>>>>>>>>
>>>>>>>>> ### IGT changes ###
>>>>>>>>>
>>>>>>>>> Possible regressions
>>>>>>>>>
>>>>>>>>> * igt@i915_selftest@live_sanitycheck:
>>>>>>>>> - fi-apl-guc: PASS -> DMESG-WARN
>>>>>>>>>
>>>>>>>>> * {igt@runner@aborted}:
>>>>>>>>> - fi-apl-guc: NOTRUN -> FAIL
>>>>>>>>
>>>>>>>> Both are pretty much non related with display, what do you think
>>>>>>>> Rodrigo? It is a merge blocker?
>>>>>>>
>>>>>>> I got addicted to see all green on CI. So I always prefer to trigger a
>>>>>>> retest. So
>>>>>>> anyone following the link that is merged with the patch doens't have to
>>>>>>> understand and analyze why it was merged with BAT failure.
>>>>>>>
>>>>>>> I just triggered the re-test for this patch.
>>>>>> Martin, Arek, fyi, not preferred?
>>>>>
>>>>> Yes, I'd like to hear their opinion.
>>>>>
>>>>> On this case a simple BAT would be enough because we don't have PSR
>>>>> mon
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe id following atomic guidelines (rev2)
On 30/11/2018 19:27, Vivi, Rodrigo wrote:
> On Fri, Nov 30, 2018 at 03:04:40PM +0200, Martin Peres wrote:
>>
>>
>> On 29/11/2018 19:36, Rodrigo Vivi wrote:
>>> On Wed, Nov 28, 2018 at 11:52:49PM -0800, Saarinen, Jani wrote:
Hi,
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On
> Behalf Of
> Rodrigo Vivi
> Sent: torstai 29. marraskuuta 2018 8.18
> To: Souza, Jose
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe
> id
> following atomic guidelines (rev2)
>
> On Wed, Nov 28, 2018 at 02:13:12PM -0800, Souza, Jose wrote:
>> On Wed, 2018-11-28 at 21:02 +, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: drm/i915/psr: Get pipe id following atomic guidelines (rev2)
>>> URL : https://patchwork.freedesktop.org/series/53132/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> CI Bug Log - changes from CI_DRM_5216 -> Patchwork_10934
>>>
>>>
>>> Summary
>>> ---
>>>
>>> **FAILURE**
>>>
>>> Serious unknown changes coming with Patchwork_10934 absolutely
>>> need to be
>>> verified manually.
>>>
>>> If you think the reported changes have nothing to do with the
>>> changes
>>> introduced in Patchwork_10934, please notify your bug team to
>>> allow them
>>> to document this new failure mode, which will reduce false
>>> positives in CI.
>>>
>>> External URL:
>>> https://patchwork.freedesktop.org/api/1.0/series/53132/revisions/2/m
>>> box/
>>>
>>> Possible new issues
>>> ---
>>>
>>> Here are the unknown changes that may have been introduced in
>>> Patchwork_10934:
>>>
>>> ### IGT changes ###
>>>
>>> Possible regressions
>>>
>>> * igt@i915_selftest@live_sanitycheck:
>>> - fi-apl-guc: PASS -> DMESG-WARN
>>>
>>> * {igt@runner@aborted}:
>>> - fi-apl-guc: NOTRUN -> FAIL
>>
>> Both are pretty much non related with display, what do you think
>> Rodrigo? It is a merge blocker?
>
> I got addicted to see all green on CI. So I always prefer to trigger a
> retest. So
> anyone following the link that is merged with the patch doens't have to
> understand and analyze why it was merged with BAT failure.
>
> I just triggered the re-test for this patch.
Martin, Arek, fyi, not preferred?
>>>
>>> Yes, I'd like to hear their opinion.
>>>
>>> On this case a simple BAT would be enough because we don't have PSR monitors
>>> on shrd ones.
>>> However most of the times trigger the retest is unavoidable because we need
>>> to make it to pass BAT and go for the full run.
>>>
>>> Besides the green-report-link reason I exposed above.
>>
>> I agree that we should only push stuff when CI is green.
>>
>> However, using the re-try button is the wrong way as it requires more
>> machine time, and it may hide low-probably issues introduced by the patch.
>>
>> Instead, we should file/edit bugs and then ask cibuglog to re-send the
>> report. I have been doing this ofr a couple of people already, but we
>> need to advertise this more!
>
> This makes total sense for me. But I wonder if we don't need at least
> one re-run.
>
> My feeling is that if we tell people to file bugs and regenerate
> reports they might just end up accidentally ignoring regressions that
> was caused by their own patches.
Yeah, I get your point... but machine time is also problematic...
In most cases, it is just that I need to extend a filter, which does not
warrant a new run.
If something is new or odd, we could use a re-run ;)
In any case, if I file the bug and we land a regression, it will not
affect CI. So that's just an additional workload for bug tracking and
fixing. But we'll have a documented trail leading back to the developer,
so we can assign him more easily!
>
> But anyway is there a doc with step-by-step instructions anywhere that
> we could learn from and start doing this without overwhelming a single
> person?
Not yet. I need to send this information... and you are absolutely right
on the bottleneck here: I do not scale ... and I do not have time to
make my work less labor-intensive because I don't have time to work on
it. Nice isn't it?
In any case, the current process is just to forward me the result email,
then I will look at the filing and re-report.
Martin
>
> Thanks a lot!
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/ddi: Add more sanity check to the encoder HW readout
On 09/11/2018 14:40, Deak, Imre wrote: > On Wed, Nov 07, 2018 at 08:39:24PM +, Patchwork wrote: >> == Series Details == >> >> Series: series starting with [1/2] drm/i915/ddi: Add more sanity check to >> the encoder HW readout >> URL : https://patchwork.freedesktop.org/series/52187/ >> State : failure >> >> == Summary == >> >> = CI Bug Log - changes from CI_DRM_5100 -> Patchwork_10758 = >> >> == Summary - FAILURE == >> >> Serious unknown changes coming with Patchwork_10758 absolutely need to be >> verified manually. >> >> If you think the reported changes have nothing to do with the changes >> introduced in Patchwork_10758, please notify your bug team to allow them >> to document this new failure mode, which will reduce false positives in CI. >> >> External URL: >> https://patchwork.freedesktop.org/api/1.0/series/52187/revisions/1/mbox/ >> >> == Possible new issues == >> >> Here are the unknown changes that may have been introduced in >> Patchwork_10758: >> >> === IGT changes === >> >> Possible regressions >> >> igt@gem_exec_nop@basic-parallel: >> fi-icl-u: PASS -> INCOMPLETE > > https://bugs.freedesktop.org/show_bug.cgi?id=108564 > Filed and re-reporting queued. Thanks! >> >> >> == Known issues == >> >> Here are the changes found in Patchwork_10758 that come from known issues: >> >> === IGT changes === >> >> Issues hit >> >> igt@gem_ctx_create@basic-files: >> fi-bsw-kefka: PASS -> FAIL (fdo#108656) >> >> igt@gem_mmap_gtt@basic-small-bo-tiledx: >> fi-glk-dsi: PASS -> INCOMPLETE (fdo#103359, k.org#198133) >> >> igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: >> fi-byt-clapper: PASS -> FAIL (fdo#103191, fdo#107362) >> >> >> Possible fixes >> >> igt@drv_getparams_basic@basic-subslice-total: >> fi-cfl-8109u: DMESG-WARN (fdo#106107) -> PASS >> >> igt@drv_selftest@live_coherency: >> fi-gdg-551: DMESG-FAIL (fdo#107164) -> PASS >> >> igt@gem_exec_suspend@basic-s3: >> fi-cfl-8109u: INCOMPLETE (fdo#108126, fdo#107187) -> PASS >> >> igt@kms_chamelium@common-hpd-after-suspend: >> fi-skl-6700k2: WARN (fdo#108680) -> PASS >> >> igt@kms_frontbuffer_tracking@basic: >> fi-hsw-peppy: DMESG-WARN (fdo#102614) -> PASS >> fi-byt-clapper: FAIL (fdo#103167) -> PASS >> >> >> Warnings >> >> igt@drv_selftest@live_contexts: >> fi-icl-u2: DMESG-FAIL (fdo#108569) -> INCOMPLETE (fdo#108315) >> >> >> fdo#102614 https://bugs.freedesktop.org/show_bug.cgi?id=102614 >> fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167 >> fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191 >> fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359 >> fdo#106107 https://bugs.freedesktop.org/show_bug.cgi?id=106107 >> fdo#107164 https://bugs.freedesktop.org/show_bug.cgi?id=107164 >> fdo#107187 https://bugs.freedesktop.org/show_bug.cgi?id=107187 >> fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362 >> fdo#108126 https://bugs.freedesktop.org/show_bug.cgi?id=108126 >> fdo#108315 https://bugs.freedesktop.org/show_bug.cgi?id=108315 >> fdo#108569 https://bugs.freedesktop.org/show_bug.cgi?id=108569 >> fdo#108656 https://bugs.freedesktop.org/show_bug.cgi?id=108656 >> fdo#108680 https://bugs.freedesktop.org/show_bug.cgi?id=108680 >> k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133 >> >> >> == Participating hosts (54 -> 46) == >> >> Missing(8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks >> fi-bsw-cyan fi-snb-2520m fi-ctg-p8600 fi-pnv-d510 >> >> >> == Build changes == >> >> * Linux: CI_DRM_5100 -> Patchwork_10758 >> >> CI_DRM_5100: c5f9a3064d90c86dab99d5aef011b87f6f8921dc @ >> git://anongit.freedesktop.org/gfx-ci/linux >> IGT_4712: a3ede1b535ac8137f6949c468edd7054453d5dae @ >> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools >> Patchwork_10758: 60ace73cb0f8e814e6a6e34d6c9775d5fcf077a8 @ >> git://anongit.freedesktop.org/gfx-ci/linux >> >> >> == Linux commits == >> >> 60ace73cb0f8 drm/i915/icl: Fix PLL mapping sanitization for DP ports >> ee7b2ea5708d drm/i915/ddi: Add more sanity check to the encoder HW readout >> >> == Logs == >> >> For more details see: >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10758/issues.html > - Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ Intel-gfx mailing list Intel-gfx@lists.freedes
