Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev6)

2022-07-28 Thread Tvrtko Ursulin 



On 28/07/2022 16:54, Robert Beckett wrote:

On 28/07/2022 15:03, Tvrtko Ursulin wrote:


On 28/07/2022 09:01, Patchwork wrote:

[snip]


    Possible regressions

  * igt@gem_mmap_offset@clear:
  o shard-iclb: PASS
 


    -> INCOMPLETE
 



What was supposed to be a simple patch.. a storm of errors like:


yeah, them's the breaks sometimes 



  DMAR: ERROR: DMA PTE for vPFN 0x3d0 already set (to 2fd7ff003 
not 2fd7ff003)

  [ cut here ]
  WARNING: CPU: 6 PID: 1254 at drivers/iommu/intel/iommu.c:2278 
__domain_mapping.cold.93+0x32/0x39<>
  Modules linked in: vgem drm_shmem_helper snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_cod>
  CPU: 6 PID: 1254 Comm: gem_mmap_offset Not tainted 
5.19.0-rc8-Patchwork_106589v6-g0e9c43d76a14+ #>
  Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U 
DDR4 SODIMM PD RVP TLC, BIOS >

  RIP: 0010:__domain_mapping.cold.93+0x32/0x39
  Code: fe 48 c7 c7 28 32 37 82 4c 89 5c 24 08 e8 e4 61 fd ff 8b 05 bf 
8e c9 00 4c 8b 5c 24 08 85 c>

  RSP: :c937f9c0 EFLAGS: 00010202
  RAX: 0004 RBX: 8881117b4000 RCX: 0001
  RDX:  RSI: 82320b25 RDI: 
  RBP: 0001 R08:  R09: c0007fff
  R10: 0001 R11: 002fd7ff R12: 0002fd7ff003
  R13: 00076c01 R14: 8881039ee800 R15: 03d0
  FS:  7f2863c1d700() GS:88849fd0() 
knlGS:

  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f2692c53000 CR3: 00011c440006 CR4: 00770ee0
  PKRU: 5554
  Call Trace:
   TASK
   intel_iommu_map_pages+0xb7/0xe0
   __iommu_map+0xe0/0x310
   __iommu_map_sg+0xa2/0x140
   iommu_dma_map_sg+0x2ef/0x4e0
   __dma_map_sg_attrs+0x64/0x70
   dma_map_sg_attrs+0x5/0x20
   i915_gem_gtt_prepare_pages+0x56/0x70 [i915]
   shmem_get_pages+0xe3/0x360 [i915]
   i915_gem_object_get_pages+0x32/0x100 [i915]
   __i915_gem_object_get_pages+0x8d/0xa0 [i915]
   vm_fault_gtt+0x3d0/0x940 [i915]
   ? ptlock_alloc+0x15/0x40
   ? rt_mutex_debug_task_free+0x91/0xa0
   __do_fault+0x30/0x180
   do_fault+0x1c4/0x4c0
   __handle_mm_fault+0x615/0xbe0
   handle_mm_fault+0x75/0x1c0
   do_user_addr_fault+0x1e7/0x670
   exc_page_fault+0x62/0x230
   asm_exc_page_fault+0x22/0x30

No idea. Maybe try CI kernel config on your Tigerlake?


I have an idea of what could be happening:

The warning is due to a pte already existing. We can see from the 
warning that it is the same value, which indicates that the same page 
has been mapped to the same iova before.


This map shrink loop will keep mapping the same sg, shrinking if it 
fails to hopefully free up iova space.


https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/i915_gem_gtt.c?h=v5.19-rc8#n32 



If we now look at the intel iommu driver's mapping function:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iommu/intel/iommu.c?h=v5.19-rc8#n2248 



If that -ENOMEM loop breaking return is hit (presumably running out of 
pte space, though I have not delved deeper), then it will return back up 
the stack, eventually returning 0 from dma_map_sg_attrs() indicating the 
error. This will cause a shrink and retry.


The problem is that the iommu does not undo it's partial mapping on 
error. So the next time round, it will map the same page to the same 
address giving the same pte encoding, which would give the warning 
observed.


I would need to get some time to try to repro and debug to confirm, but 
this looks like it might be exposing an iommu driver issue due to us 
changing our mapping patterns because the segment sizes are now different.


I'll see if I can get some time allotted to debug it further, but for 
now, I don't have the bandwidth, so this may need to go on hold until I 
or someone else can get time to look in to it.


Yeah that's understandable. I also currently don't have any free 
bandwidth unfortunately.


+ Christoph FYI, as per above, swiotlb API usage removal is currently a 
bit stuck until we find someone with some spare time to debug this further.


Regards,

Tvrtko

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev6)

2022-07-28 Thread Robert Beckett 




On 28/07/2022 15:03, Tvrtko Ursulin wrote:


On 28/07/2022 09:01, Patchwork wrote:

[snip]


    Possible regressions

  * igt@gem_mmap_offset@clear:
  o shard-iclb: PASS

 


    -> INCOMPLETE

 



What was supposed to be a simple patch.. a storm of errors like:


yeah, them's the breaks sometimes 



  DMAR: ERROR: DMA PTE for vPFN 0x3d0 already set (to 2fd7ff003 not 
2fd7ff003)

  [ cut here ]
  WARNING: CPU: 6 PID: 1254 at drivers/iommu/intel/iommu.c:2278 
__domain_mapping.cold.93+0x32/0x39<>
  Modules linked in: vgem drm_shmem_helper snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_cod>
  CPU: 6 PID: 1254 Comm: gem_mmap_offset Not tainted 
5.19.0-rc8-Patchwork_106589v6-g0e9c43d76a14+ #>
  Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U 
DDR4 SODIMM PD RVP TLC, BIOS >

  RIP: 0010:__domain_mapping.cold.93+0x32/0x39
  Code: fe 48 c7 c7 28 32 37 82 4c 89 5c 24 08 e8 e4 61 fd ff 8b 05 bf 
8e c9 00 4c 8b 5c 24 08 85 c>

  RSP: :c937f9c0 EFLAGS: 00010202
  RAX: 0004 RBX: 8881117b4000 RCX: 0001
  RDX:  RSI: 82320b25 RDI: 
  RBP: 0001 R08:  R09: c0007fff
  R10: 0001 R11: 002fd7ff R12: 0002fd7ff003
  R13: 00076c01 R14: 8881039ee800 R15: 03d0
  FS:  7f2863c1d700() GS:88849fd0() 
knlGS:

  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f2692c53000 CR3: 00011c440006 CR4: 00770ee0
  PKRU: 5554
  Call Trace:
   TASK
   intel_iommu_map_pages+0xb7/0xe0
   __iommu_map+0xe0/0x310
   __iommu_map_sg+0xa2/0x140
   iommu_dma_map_sg+0x2ef/0x4e0
   __dma_map_sg_attrs+0x64/0x70
   dma_map_sg_attrs+0x5/0x20
   i915_gem_gtt_prepare_pages+0x56/0x70 [i915]
   shmem_get_pages+0xe3/0x360 [i915]
   i915_gem_object_get_pages+0x32/0x100 [i915]
   __i915_gem_object_get_pages+0x8d/0xa0 [i915]
   vm_fault_gtt+0x3d0/0x940 [i915]
   ? ptlock_alloc+0x15/0x40
   ? rt_mutex_debug_task_free+0x91/0xa0
   __do_fault+0x30/0x180
   do_fault+0x1c4/0x4c0
   __handle_mm_fault+0x615/0xbe0
   handle_mm_fault+0x75/0x1c0
   do_user_addr_fault+0x1e7/0x670
   exc_page_fault+0x62/0x230
   asm_exc_page_fault+0x22/0x30

No idea. Maybe try CI kernel config on your Tigerlake?


I have an idea of what could be happening:

The warning is due to a pte already existing. We can see from the 
warning that it is the same value, which indicates that the same page 
has been mapped to the same iova before.


This map shrink loop will keep mapping the same sg, shrinking if it 
fails to hopefully free up iova space.


https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/i915_gem_gtt.c?h=v5.19-rc8#n32

If we now look at the intel iommu driver's mapping function:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iommu/intel/iommu.c?h=v5.19-rc8#n2248

If that -ENOMEM loop breaking return is hit (presumably running out of 
pte space, though I have not delved deeper), then it will return back up 
the stack, eventually returning 0 from dma_map_sg_attrs() indicating the 
error. This will cause a shrink and retry.


The problem is that the iommu does not undo it's partial mapping on 
error. So the next time round, it will map the same page to the same 
address giving the same pte encoding, which would give the warning observed.


I would need to get some time to try to repro and debug to confirm, but 
this looks like it might be exposing an iommu driver issue due to us 
changing our mapping patterns because the segment sizes are now different.


I'll see if I can get some time allotted to debug it further, but for 
now, I don't have the bandwidth, so this may need to go on hold until I 
or someone else can get time to look in to it.




Regards,

Tvrtko

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev6)

2022-07-28 Thread Tvrtko Ursulin 



On 28/07/2022 09:01, Patchwork wrote:

[snip]


Possible regressions

  * igt@gem_mmap_offset@clear:
  o shard-iclb: PASS


-> INCOMPLETE




What was supposed to be a simple patch.. a storm of errors like:

 DMAR: ERROR: DMA PTE for vPFN 0x3d0 already set (to 2fd7ff003 not 
2fd7ff003)
 [ cut here ]
 WARNING: CPU: 6 PID: 1254 at drivers/iommu/intel/iommu.c:2278 
__domain_mapping.cold.93+0x32/0x39<>
 Modules linked in: vgem drm_shmem_helper snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_cod>
 CPU: 6 PID: 1254 Comm: gem_mmap_offset Not tainted 
5.19.0-rc8-Patchwork_106589v6-g0e9c43d76a14+ #>
 Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 SODIMM 
PD RVP TLC, BIOS >
 RIP: 0010:__domain_mapping.cold.93+0x32/0x39
 Code: fe 48 c7 c7 28 32 37 82 4c 89 5c 24 08 e8 e4 61 fd ff 8b 05 bf 8e c9 00 4c 
8b 5c 24 08 85 c>
 RSP: :c937f9c0 EFLAGS: 00010202
 RAX: 0004 RBX: 8881117b4000 RCX: 0001
 RDX:  RSI: 82320b25 RDI: 
 RBP: 0001 R08:  R09: c0007fff
 R10: 0001 R11: 002fd7ff R12: 0002fd7ff003
 R13: 00076c01 R14: 8881039ee800 R15: 03d0
 FS:  7f2863c1d700() GS:88849fd0() knlGS:
 CS:  0010 DS:  ES:  CR0: 80050033
 CR2: 7f2692c53000 CR3: 00011c440006 CR4: 00770ee0
 PKRU: 5554
 Call Trace:
  TASK
  intel_iommu_map_pages+0xb7/0xe0
  __iommu_map+0xe0/0x310
  __iommu_map_sg+0xa2/0x140
  iommu_dma_map_sg+0x2ef/0x4e0
  __dma_map_sg_attrs+0x64/0x70
  dma_map_sg_attrs+0x5/0x20
  i915_gem_gtt_prepare_pages+0x56/0x70 [i915]
  shmem_get_pages+0xe3/0x360 [i915]
  i915_gem_object_get_pages+0x32/0x100 [i915]
  __i915_gem_object_get_pages+0x8d/0xa0 [i915]
  vm_fault_gtt+0x3d0/0x940 [i915]
  ? ptlock_alloc+0x15/0x40
  ? rt_mutex_debug_task_free+0x91/0xa0
  __do_fault+0x30/0x180
  do_fault+0x1c4/0x4c0
  __handle_mm_fault+0x615/0xbe0
  handle_mm_fault+0x75/0x1c0
  do_user_addr_fault+0x1e7/0x670
  exc_page_fault+0x62/0x230
  asm_exc_page_fault+0x22/0x30

No idea. Maybe try CI kernel config on your Tigerlake?

Regards,

Tvrtko

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev6)

2022-07-28 Thread Patchwork 
== Series Details ==

Series: drm/i915: stop using swiotlb (rev6)
URL   : https://patchwork.freedesktop.org/series/106589/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11946_full -> Patchwork_106589v6_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_106589v6_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_106589v6_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (13 -> 13)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_106589v6_full:

### IGT changes ###

 Possible regressions 

  * igt@gem_mmap_offset@clear:
- shard-iclb: [PASS][1] -> [INCOMPLETE][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-iclb6/igt@gem_mmap_off...@clear.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-iclb1/igt@gem_mmap_off...@clear.html

  
New tests
-

  New tests have been introduced between CI_DRM_11946_full and 
Patchwork_106589v6_full:

### New IGT tests (5) ###

  * igt@kms_atomic_interruptible@atomic-setmode@hdmi-a-4-pipe-a:
- Statuses : 1 pass(s)
- Exec time: [6.16] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-a-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.90] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-b-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.76] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-c-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.75] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-d-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.75] s

  

Known issues


  Here are the changes found in Patchwork_106589v6_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@feature_discovery@psr2:
- shard-iclb: [PASS][3] -> [SKIP][4] ([i915#658])
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-iclb2/igt@feature_discov...@psr2.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-iclb5/igt@feature_discov...@psr2.html

  * igt@gem_create@create-massive:
- shard-glk:  NOTRUN -> [DMESG-WARN][5] ([i915#4991])
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-glk6/igt@gem_cre...@create-massive.html

  * igt@gem_exec_balancer@parallel-keep-submit-fence:
- shard-iclb: [PASS][6] -> [SKIP][7] ([i915#4525]) +1 similar issue
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-iclb1/igt@gem_exec_balan...@parallel-keep-submit-fence.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-iclb6/igt@gem_exec_balan...@parallel-keep-submit-fence.html

  * igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][8] -> [FAIL][9] ([i915#2842])
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-tglb7/igt@gem_exec_fair@basic-f...@rcs0.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-tglb7/igt@gem_exec_fair@basic-f...@rcs0.html

  * igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][10] ([i915#2842])
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-iclb4/igt@gem_exec_fair@basic-p...@vcs1.html

  * igt@gem_lmem_swapping@smem-oom:
- shard-kbl:  NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-kbl7/igt@gem_lmem_swapp...@smem-oom.html

  * igt@gem_userptr_blits@input-checking:
- shard-apl:  NOTRUN -> [DMESG-WARN][12] ([i915#4991])
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-apl7/igt@gem_userptr_bl...@input-checking.html

  * igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-apl:  [PASS][13] -> [WARN][14] ([i915#6405])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-apl1/igt@i915_pm_rc6_residency@rc6-i...@vcs0.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-apl7/igt@i915_pm_rc6_residency@rc6-i...@vcs0.html

  * igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-kbl:  NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#3886]) +3 
similar issues
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-kbl7/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-apl:  NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#3886])
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-apl3/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_mc_ccs.html

  *

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev5)

2022-07-26 Thread Patchwork 
== Series Details ==

Series: drm/i915: stop using swiotlb (rev5)
URL   : https://patchwork.freedesktop.org/series/106589/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11944_full -> Patchwork_106589v5_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_106589v5_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_106589v5_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (13 -> 13)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_106589v5_full:

### IGT changes ###

 Possible regressions 

  * igt@kms_cursor_legacy@cursor-vs-flip@atomic-transitions:
- shard-skl:  NOTRUN -> [INCOMPLETE][1]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-skl4/igt@kms_cursor_legacy@cursor-vs-f...@atomic-transitions.html

  
New tests
-

  New tests have been introduced between CI_DRM_11944_full and 
Patchwork_106589v5_full:

### New IGT tests (5) ###

  * igt@kms_atomic_interruptible@atomic-setmode@hdmi-a-4-pipe-a:
- Statuses : 1 pass(s)
- Exec time: [6.16] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-a-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.86] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-b-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.76] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-c-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.75] s

  * igt@kms_cursor_crc@cursor-dpms@pipe-d-hdmi-a-4:
- Statuses : 1 pass(s)
- Exec time: [0.75] s

  

Known issues


  Here are the changes found in Patchwork_106589v5_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-kbl:  [PASS][2] -> [DMESG-WARN][3] ([i915#180])
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-kbl1/igt@gem_ctx_isolation@preservation...@bcs0.html
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-kbl1/igt@gem_ctx_isolation@preservation...@bcs0.html

  * igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [PASS][4] -> [SKIP][5] ([i915#4525])
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-iclb2/igt@gem_exec_balan...@parallel-bb-first.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-iclb5/igt@gem_exec_balan...@parallel-bb-first.html

  * igt@gem_exec_create@madvise@smem:
- shard-glk:  [PASS][6] -> [DMESG-WARN][7] ([i915#118])
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-glk2/igt@gem_exec_create@madv...@smem.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-glk1/igt@gem_exec_create@madv...@smem.html

  * igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [PASS][8] -> [FAIL][9] ([i915#2842])
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-tglb8/igt@gem_exec_fair@basic-none-sh...@rcs0.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-tglb1/igt@gem_exec_fair@basic-none-sh...@rcs0.html

  * igt@gem_exec_fair@basic-none@vecs0:
- shard-glk:  [PASS][10] -> [FAIL][11] ([i915#2842]) +1 similar 
issue
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-glk6/igt@gem_exec_fair@basic-n...@vecs0.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-glk9/igt@gem_exec_fair@basic-n...@vecs0.html

  * igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-kbl:  NOTRUN -> [FAIL][12] ([i915#2842]) +1 similar issue
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-kbl7/igt@gem_exec_fair@basic-pace-s...@rcs0.html

  * igt@gem_huc_copy@huc-copy:
- shard-skl:  NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#2190])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-skl4/igt@gem_huc_c...@huc-copy.html
- shard-tglb: [PASS][14] -> [SKIP][15] ([i915#2190])
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11944/shard-tglb8/igt@gem_huc_c...@huc-copy.html
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-tglb7/igt@gem_huc_c...@huc-copy.html

  * igt@gem_lmem_swapping@basic:
- shard-kbl:  NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#4613])
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-kbl7/igt@gem_lmem_swapp...@basic.html

  * igt@gem_pread@exhaustion:
- shard-kbl:  NOTRUN -> [WARN][17] ([i915#2658])
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v5/shard-kbl7/igt@gem_pr...@exhaustion.html

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

2022-07-25 Thread Tvrtko Ursulin 



On 25/07/2022 15:13, Robert Beckett wrote:

On 25/07/2022 09:23, Tvrtko Ursulin wrote:


On 22/07/2022 20:21, Robert Beckett wrote:

On 22/07/2022 19:05, Patchwork wrote:

*Patch Details*
*Series:*    drm/i915: stop using swiotlb (rev3)
*URL:*    https://patchwork.freedesktop.org/series/106589/ 


*State:*    failure
*Details:* 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/index.html 
 




  CI Bug Log - changes from CI_DRM_11935_full -> 
Patchwork_106589v3_full



    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_106589v3_full 
absolutely need to be

verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106589v3_full, please notify your bug team 
to allow them
to document this new failure mode, which will reduce false positives 
in CI.



    Participating hosts (10 -> 12)

Additional (2): shard-rkl shard-tglu


    Possible new issues

Here are the unknown changes that may have been introduced in 
Patchwork_106589v3_full:



  IGT changes


    Possible regressions

  *

    igt@gem_mmap_offset@clear:

  o

    shard-tglb: PASS
 


    -> INCOMPLETE
 





I've no idea why CI is seeing a NULL deref here.
Testing locally on my TGL board, it passes fine.
I think I would need some help testing this on other systems to track 
this down.


Is it possible that dma_direct_max_mapping_size can return a whole 
range of "unexpected" values akin to swiotlb_max_segment? Anything 
below PAGE_SIZE, including zero, would confuse the driver.


oh really? scatterlist happily supports non page aligned segments. If 
this is an i915 restriction, it sounds like there could do with being 
some GEM_BUG_ON somewhere to catch this more obviously.


Well zero or one as values returned from swiotlb_max_segment did not 
really make much sense. Hence special handling was put in 
i915_sg_segment_size to correctly interpret them.


So yes a GEM_BUG_ON to ensure value returned from dma_max_mapping_size() 
is at least PAGE_SIZE would be safest. Unless it manages to trigger, in 
which special handling needs to be put back in.


Alternatively we'd need to try to figure out possible return values from 
dma_max_mapping_size(). There doesn't seem to be kernel doc for it 
currently.



Oh..

   return min_t(size_t, UINT_MAX, dma_max_mapping_size(dev)); >
Wrap the min_t value in rounddown(..., PAGE_SIZE).


I'll issue a v5


Or you meant if this one was a i915 limitation? I don't really remember 
and did not do a deep dive to remind myself. Just finger in the air "if 
it is a null sg entry, why would the iterator ever encounter it". So I 
was thinking some sort of a mismatch between found and expected number 
of entries, and hence suspected the lack of rounddown after the 
conversion as the other remaining difference. But as said, did not 
really think it through and checked what in the code would go wrong if 
it wasn't page aligned.


Regards,

Tvrtko



Regards,

Tvrtko




  o

    shard-iclb: PASS
 


    -> INCOMPLETE
 




    Suppressed

The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.

  *

    igt@gem_mmap_offset@clear:

  o

    {shard-rkl}: NOTRUN -> INCOMPLETE
 



  o

    {shard-tglu}: NOTRUN -> INCOMPLETE
 


    +1 similar issue


    New tests

New tests have been introduced between CI_DRM_11935_full and 
Patchwork_106589v3_full:



  New IGT tests (27)

  *

    igt@kms_flip@basic-flip-vs-dpms@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.66] s
  *

    igt@kms_flip@basic-flip-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.59] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@bo-too-big-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.39] s
  *

    igt@kms_flip@bo-too-big@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.41] s
  *

    igt@kms_flip@busy-flip@d-hdmi-a1:

  o

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

2022-07-25 Thread Robert Beckett 




On 25/07/2022 09:23, Tvrtko Ursulin wrote:


On 22/07/2022 20:21, Robert Beckett wrote:

On 22/07/2022 19:05, Patchwork wrote:

*Patch Details*
*Series:*    drm/i915: stop using swiotlb (rev3)
*URL:*    https://patchwork.freedesktop.org/series/106589/ 


*State:*    failure
*Details:* 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/index.html  




  CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v3_full


    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_106589v3_full 
absolutely need to be

verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106589v3_full, please notify your bug team to 
allow them
to document this new failure mode, which will reduce false positives 
in CI.



    Participating hosts (10 -> 12)

Additional (2): shard-rkl shard-tglu


    Possible new issues

Here are the unknown changes that may have been introduced in 
Patchwork_106589v3_full:



  IGT changes


    Possible regressions

  *

    igt@gem_mmap_offset@clear:

  o

    shard-tglb: PASS
 


    -> INCOMPLETE
 





I've no idea why CI is seeing a NULL deref here.
Testing locally on my TGL board, it passes fine.
I think I would need some help testing this on other systems to track 
this down.


Is it possible that dma_direct_max_mapping_size can return a whole range 
of "unexpected" values akin to swiotlb_max_segment? Anything below 
PAGE_SIZE, including zero, would confuse the driver.


oh really? scatterlist happily supports non page aligned segments. If 
this is an i915 restriction, it sounds like there could do with being 
some GEM_BUG_ON somewhere to catch this more obviously.




Oh..

   return min_t(size_t, UINT_MAX, dma_max_mapping_size(dev)); >
Wrap the min_t value in rounddown(..., PAGE_SIZE).


I'll issue a v5



Regards,

Tvrtko




  o

    shard-iclb: PASS
 


    -> INCOMPLETE
 




    Suppressed

The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.

  *

    igt@gem_mmap_offset@clear:

  o

    {shard-rkl}: NOTRUN -> INCOMPLETE
 



  o

    {shard-tglu}: NOTRUN -> INCOMPLETE
 


    +1 similar issue


    New tests

New tests have been introduced between CI_DRM_11935_full and 
Patchwork_106589v3_full:



  New IGT tests (27)

  *

    igt@kms_flip@basic-flip-vs-dpms@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.66] s
  *

    igt@kms_flip@basic-flip-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.59] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@bo-too-big-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.39] s
  *

    igt@kms_flip@bo-too-big@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.41] s
  *

    igt@kms_flip@busy-flip@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

    igt@kms_flip@dpms-off-confusion-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

    igt@kms_flip@dpms-vs-vblank-race-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [2.72] s
  *

    igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [8.03] s
  *

    igt@kms_flip@flip-vs-dpms-off-vs-modeset-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.60] s
  *

    igt@kms_flip@flip-vs-dpms-off-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.57] s
  *

    igt@kms_flip@flip-vs-fences-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@flip-vs-fences@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.66] s
  *

    igt@kms_flip@flip-vs-modeset-vs-hang@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [30.02] s
  *

    igt@kms_flip@flip-vs-panning-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
 

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

2022-07-25 Thread Tvrtko Ursulin 



On 22/07/2022 20:21, Robert Beckett wrote:

On 22/07/2022 19:05, Patchwork wrote:

*Patch Details*
*Series:*    drm/i915: stop using swiotlb (rev3)
*URL:*    https://patchwork.freedesktop.org/series/106589/ 


*State:*    failure
*Details:* 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/index.html 




  CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v3_full


    Summary

*FAILURE*

Serious unknown changes coming with Patchwork_106589v3_full absolutely 
need to be

verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106589v3_full, please notify your bug team to 
allow them
to document this new failure mode, which will reduce false positives 
in CI.



    Participating hosts (10 -> 12)

Additional (2): shard-rkl shard-tglu


    Possible new issues

Here are the unknown changes that may have been introduced in 
Patchwork_106589v3_full:



  IGT changes


    Possible regressions

  *

    igt@gem_mmap_offset@clear:

  o

    shard-tglb: PASS

 


    -> INCOMPLETE

 





I've no idea why CI is seeing a NULL deref here.
Testing locally on my TGL board, it passes fine.
I think I would need some help testing this on other systems to track 
this down.


Is it possible that dma_direct_max_mapping_size can return a whole range 
of "unexpected" values akin to swiotlb_max_segment? Anything below 
PAGE_SIZE, including zero, would confuse the driver.


Oh..

  return min_t(size_t, UINT_MAX, dma_max_mapping_size(dev));

Wrap the min_t value in rounddown(..., PAGE_SIZE).

Regards,

Tvrtko




  o

    shard-iclb: PASS

 


    -> INCOMPLETE

 




    Suppressed

The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.

  *

    igt@gem_mmap_offset@clear:

  o

    {shard-rkl}: NOTRUN -> INCOMPLETE

 



  o

    {shard-tglu}: NOTRUN -> INCOMPLETE

 


    +1 similar issue


    New tests

New tests have been introduced between CI_DRM_11935_full and 
Patchwork_106589v3_full:



  New IGT tests (27)

  *

    igt@kms_flip@basic-flip-vs-dpms@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.66] s
  *

    igt@kms_flip@basic-flip-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.59] s
  *

    igt@kms_flip@blocking-absolute-wf_vblank@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@bo-too-big-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.39] s
  *

    igt@kms_flip@bo-too-big@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.41] s
  *

    igt@kms_flip@busy-flip@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

    igt@kms_flip@dpms-off-confusion-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

    igt@kms_flip@dpms-vs-vblank-race-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [2.72] s
  *

    igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [8.03] s
  *

    igt@kms_flip@flip-vs-dpms-off-vs-modeset-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.60] s
  *

    igt@kms_flip@flip-vs-dpms-off-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.57] s
  *

    igt@kms_flip@flip-vs-fences-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@flip-vs-fences@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.66] s
  *

    igt@kms_flip@flip-vs-modeset-vs-hang@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [30.02] s
  *

    igt@kms_flip@flip-vs-panning-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

    igt@kms_flip@flip-vs-panning@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

    igt@kms_flip@flip-vs-rmfb-interruptible@d-hdmi-a1:

  o Statuses : 1

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

2022-07-22 Thread Robert Beckett 




On 22/07/2022 19:05, Patchwork wrote:

*Patch Details*
*Series:*   drm/i915: stop using swiotlb (rev3)
*URL:*	https://patchwork.freedesktop.org/series/106589/ 


*State:*failure
*Details:* 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/index.html 




  CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v3_full


Summary

*FAILURE*

Serious unknown changes coming with Patchwork_106589v3_full absolutely 
need to be

verified manually.

If you think the reported changes have nothing to do with the changes
introduced in Patchwork_106589v3_full, please notify your bug team to 
allow them

to document this new failure mode, which will reduce false positives in CI.


Participating hosts (10 -> 12)

Additional (2): shard-rkl shard-tglu


Possible new issues

Here are the unknown changes that may have been introduced in 
Patchwork_106589v3_full:



  IGT changes


Possible regressions

  *

igt@gem_mmap_offset@clear:

  o

shard-tglb: PASS


-> INCOMPLETE





I've no idea why CI is seeing a NULL deref here.
Testing locally on my TGL board, it passes fine.
I think I would need some help testing this on other systems to track 
this down.



  o

shard-iclb: PASS


-> INCOMPLETE




Suppressed

The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.

  *

igt@gem_mmap_offset@clear:

  o

{shard-rkl}: NOTRUN -> INCOMPLETE



  o

{shard-tglu}: NOTRUN -> INCOMPLETE


+1 similar issue


New tests

New tests have been introduced between CI_DRM_11935_full and 
Patchwork_106589v3_full:



  New IGT tests (27)

  *

igt@kms_flip@basic-flip-vs-dpms@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.66] s
  *

igt@kms_flip@basic-flip-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

igt@kms_flip@blocking-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.59] s
  *

igt@kms_flip@blocking-absolute-wf_vblank@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

igt@kms_flip@bo-too-big-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.39] s
  *

igt@kms_flip@bo-too-big@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.41] s
  *

igt@kms_flip@busy-flip@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.62] s
  *

igt@kms_flip@dpms-off-confusion-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

igt@kms_flip@dpms-vs-vblank-race-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [2.72] s
  *

igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [8.03] s
  *

igt@kms_flip@flip-vs-dpms-off-vs-modeset-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.60] s
  *

igt@kms_flip@flip-vs-dpms-off-vs-modeset@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [0.57] s
  *

igt@kms_flip@flip-vs-fences-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

igt@kms_flip@flip-vs-fences@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.66] s
  *

igt@kms_flip@flip-vs-modeset-vs-hang@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [30.02] s
  *

igt@kms_flip@flip-vs-panning-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

igt@kms_flip@flip-vs-panning@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.62] s
  *

igt@kms_flip@flip-vs-rmfb-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.59] s
  *

igt@kms_flip@flip-vs-rmfb@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.60] s
  *

igt@kms_flip@modeset-vs-vblank-race@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [2.81] s
  *

igt@kms_flip@plain-flip-fb-recreate-interruptible@d-hdmi-a1:

  o Statuses : 1 pass(s)
  o Exec time: [7.72] s
  *

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev3)

2022-07-22 Thread Patchwork 
== Series Details ==

Series: drm/i915: stop using swiotlb (rev3)
URL   : https://patchwork.freedesktop.org/series/106589/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v3_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_106589v3_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_106589v3_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (10 -> 12)
--

  Additional (2): shard-rkl shard-tglu 

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_106589v3_full:

### IGT changes ###

 Possible regressions 

  * igt@gem_mmap_offset@clear:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-tglb7/igt@gem_mmap_off...@clear.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/shard-tglb1/igt@gem_mmap_off...@clear.html
- shard-iclb: [PASS][3] -> [INCOMPLETE][4]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-iclb8/igt@gem_mmap_off...@clear.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/shard-iclb3/igt@gem_mmap_off...@clear.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_mmap_offset@clear:
- {shard-rkl}:NOTRUN -> [INCOMPLETE][5]
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/shard-rkl-6/igt@gem_mmap_off...@clear.html
- {shard-tglu}:   NOTRUN -> [INCOMPLETE][6] +1 similar issue
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v3/shard-tglu-1/igt@gem_mmap_off...@clear.html

  
New tests
-

  New tests have been introduced between CI_DRM_11935_full and 
Patchwork_106589v3_full:

### New IGT tests (27) ###

  * igt@kms_flip@basic-flip-vs-dpms@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.66] s

  * igt@kms_flip@basic-flip-vs-modeset@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.62] s

  * igt@kms_flip@blocking-absolute-wf_vblank-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.59] s

  * igt@kms_flip@blocking-absolute-wf_vblank@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.62] s

  * igt@kms_flip@bo-too-big-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.39] s

  * igt@kms_flip@bo-too-big@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.41] s

  * igt@kms_flip@busy-flip@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.62] s

  * igt@kms_flip@dpms-off-confusion-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.60] s

  * igt@kms_flip@dpms-vs-vblank-race-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [2.72] s

  * igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [8.03] s

  * igt@kms_flip@flip-vs-dpms-off-vs-modeset-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.60] s

  * igt@kms_flip@flip-vs-dpms-off-vs-modeset@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.57] s

  * igt@kms_flip@flip-vs-fences-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.62] s

  * igt@kms_flip@flip-vs-fences@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.66] s

  * igt@kms_flip@flip-vs-modeset-vs-hang@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [30.02] s

  * igt@kms_flip@flip-vs-panning-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.60] s

  * igt@kms_flip@flip-vs-panning@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.62] s

  * igt@kms_flip@flip-vs-rmfb-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.59] s

  * igt@kms_flip@flip-vs-rmfb@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.60] s

  * igt@kms_flip@modeset-vs-vblank-race@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [2.81] s

  * igt@kms_flip@plain-flip-fb-recreate-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.72] s

  * igt@kms_flip@plain-flip-fb-recreate@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.76] s

  * igt@kms_flip@plain-flip-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.60] s

  * igt@kms_flip@plain-flip-ts-check-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [7.74] s

  * 
igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset-interruptible@d-hdmi-a1:
- Statuses : 1 pass(s)
- Exec time: [0.61] s

  * igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset@d-hdmi-a1:

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb

2022-07-21 Thread Patchwork 
== Series Details ==

Series: drm/i915: stop using swiotlb
URL   : https://patchwork.freedesktop.org/series/106589/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11935_full -> Patchwork_106589v1_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_106589v1_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_106589v1_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (10 -> 13)
--

  Additional (3): shard-rkl shard-dg1 shard-tglu 

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_106589v1_full:

### IGT changes ###

 Possible regressions 

  * igt@gem_mmap_offset@clear:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-tglb7/igt@gem_mmap_off...@clear.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-tglb2/igt@gem_mmap_off...@clear.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_mmap_offset@clear:
- {shard-tglu}:   NOTRUN -> [INCOMPLETE][3] +1 similar issue
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-tglu-3/igt@gem_mmap_off...@clear.html

  * igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-75:
- {shard-rkl}:NOTRUN -> [SKIP][4] +1 similar issue
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-rkl-5/igt@kms_plane_scal...@plane-downscale-with-modifiers-factor-0-75.html

  * igt@prime_self_import@export-vs-gem_close-race:
- {shard-tglu}:   NOTRUN -> [FAIL][5]
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-tglu-8/igt@prime_self_import@export-vs-gem_close-race.html

  
Known issues


  Here are the changes found in Patchwork_106589v1_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@feature_discovery@display-4x:
- shard-tglb: NOTRUN -> [SKIP][6] ([i915#1839])
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-tglb1/igt@feature_discov...@display-4x.html

  * igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][7] -> [TIMEOUT][8] ([i915#3070])
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-iclb3/igt@gem_...@unwedge-stress.html
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-iclb2/igt@gem_...@unwedge-stress.html

  * igt@gem_exec_capture@pi@vecs0:
- shard-iclb: [PASS][9] -> [INCOMPLETE][10] ([i915#3371])
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-iclb2/igt@gem_exec_capture@p...@vecs0.html
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-iclb8/igt@gem_exec_capture@p...@vecs0.html

  * igt@gem_exec_fair@basic-deadline:
- shard-glk:  [PASS][11] -> [FAIL][12] ([i915#2846])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-glk1/igt@gem_exec_f...@basic-deadline.html
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-glk5/igt@gem_exec_f...@basic-deadline.html

  * igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][13] -> [FAIL][14] ([i915#2842])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-tglb7/igt@gem_exec_fair@basic-f...@rcs0.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-tglb2/igt@gem_exec_fair@basic-f...@rcs0.html

  * igt@gem_exec_fair@basic-none@vcs0:
- shard-glk:  [PASS][15] -> [FAIL][16] ([i915#2842])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-glk3/igt@gem_exec_fair@basic-n...@vcs0.html
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-glk1/igt@gem_exec_fair@basic-n...@vcs0.html

  * igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl:  [PASS][17] -> [FAIL][18] ([i915#2842]) +2 similar 
issues
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-kbl7/igt@gem_exec_fair@basic-n...@vecs0.html
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-kbl6/igt@gem_exec_fair@basic-n...@vecs0.html

  * igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [PASS][19] -> [FAIL][20] ([i915#2849])
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11935/shard-iclb7/igt@gem_exec_fair@basic-throt...@rcs0.html
   [20]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v1/shard-iclb5/igt@gem_exec_fair@basic-throt...@rcs0.html

  * igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-tglb: NOTRUN -> [SKIP][21]