date:20220521

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5

2022-05-21 Thread Vudum, Lakshminarayana

I don't see any regressions from Bat but on shards.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-skl8/igt@i915_pm...@dc5-dpms.html
 is mapped to https://gitlab.freedesktop.org/drm/intel/-/issues/5961

Thanks,
Lakshmi.
-Original Message-
From: Srivatsa, Anusha  
Sent: Saturday, May 21, 2022 9:13 AM
To: Roper, Matthew D ; 
intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana 

Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5



> -Original Message-
> From: Roper, Matthew D 
> Sent: Friday, May 20, 2022 4:11 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Srivatsa, Anusha ; Vudum, 
> Lakshminarayana 
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable 
> DC5
> 
> On Fri, May 20, 2022 at 05:11:22PM +, Patchwork wrote:
> > == Series Details ==
> >
> > Series: drm/i915/dg2: Enable DC5
> > URL   : https://patchwork.freedesktop.org/series/104233/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from CI_DRM_11681 -> Patchwork_104233v1 
> > 
> >
> > Summary
> > ---
> >
> >   **FAILURE**
> >
> >   Serious unknown changes coming with Patchwork_104233v1 absolutely
> need to be
> >   verified manually.
> >
> >   If you think the reported changes have nothing to do with the changes
> >   introduced in Patchwork_104233v1, 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_104233v1/index.ht
> > ml
> >
> > Participating hosts (46 -> 44)
> > --
> >
> >   Missing(2): bat-dg2-8 fi-rkl-11600
> >
> > Possible new issues
> > ---
> >
> >   Here are the unknown changes that may have been introduced in
> Patchwork_104233v1:
> >
> > ### IGT changes ###
> >
> >  Possible regressions 
> >
> >   * igt@fbdev@read:
> > - fi-icl-u2:  [PASS][1] -> [DMESG-WARN][2]
> >[1]: 
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/fi-icl-
> u2/igt@fb...@read.html
> >[2]:
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/fi-icl-u
> > 2/
> > igt@fb...@read.html
> 
> It looks like this is an error coming from a bluetooth driver, not 
> related to
> graphics:
> 
><3> [26.916574] Bluetooth: hci0: Reading Intel version command 
> failed (-
> 110)
><4> [26.916689] general protection fault, probably for 
> non-canonical address 0x6b6b6b6b6b6b6b6b:  [#1] PREEMPT SMP NOPTI
><4> [26.916726] CPU: 2 PID: 99 Comm: kworker/2:2 Not tainted 
> 5.18.0-rc7- Patchwork_104233v1-gba369855d857+ #1
><4> [26.916731] Hardware name: Intel Corporation Ice Lake Client 
> Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS
> ICLSFWR1.R00.3183.A00.1905020411 05/02/2019
><4> [26.916737] Workqueue: events hci_cmd_timeout [bluetooth]
><4> [26.916755] RIP: 0010:hci_cmd_timeout+0x30/0xa0 [bluetooth]
><4> [26.916806] Code: ff ff 53 48 8b 87 10 05 00 00 48 89 fb 48 85 
> c0 74 63
> 48 8b 80 b8 00 00 00 48 8d b5 a0 00 00 00 48 85 ed 48 c7 c7 c8 6c 38 
> a0 <0f>
> b7 10 48 c7 c0 53 38 38 a0 48 0f 44 f0 e8 91 13 06 00 48 8b 83
><4> [26.916814] RSP: 0018:c9ae3e50 EFLAGS: 00010286
><4> [26.916818] RAX: 6b6b6b6b6b6b6b6b RBX: 88810ef5aac8 RCX:
> 
><4> [26.916821] RDX: 0001 RSI: 88810ef5a0a0 RDI:
> a0386cc8
><4> [26.916825] RBP: 88810ef5a000 R08: 88810700ba38 R09:
> fffe
><4> [26.916828] R10: 0001 R11: dfbbfb17 R12:
> 88849fb3afc0
><4> [26.916832] R13: 88849fb3fc00 R14:  R15:
> 88849fb3fc05
><4> [26.916835] FS:  () 
> GS:88849fb0()
> knlGS:
><4> [26.916839] CS:  0010 DS:  ES:  CR0: 80050033
><4> [26.916842] CR2: 7fcc6837e1a0 CR3: 06612006 CR4:
> 00770ee0
><4> [26.916846] PKRU: 5554
><4> [26.916848] Call Trace:
><4> [26.916850]  
><4> [26.916852]  process_one_work+0x272/0x5c0
><4> [26.916857]  worker_thread+0x37/0x370
><4> [26.916861]  ? process_one_work+0x5c0/0x5c0
><4> [26.916864]  kthread+0xed/0x120
><4> [26.916867]  ? kthread_complete_and_exit+0x20/0x20
><4> [26.916870]  ret_from_fork+0x1f/0x30
><4> [26.916875]  
> 
> Looks like this might be
> https://gitlab.freedesktop.org/drm/intel/-/issues/4890 ?
Yeah seems like it. 
@Vudum, Lakshminarayana should I resend the series?

Anusha 
> >
> >
> >  Suppressed 
> >
> >   The following results come from untrusted machines, tests, or statuses.
> >   They do not affect the overall result.
> >
> >   * igt@kms_busy@basic@modeset:
> > - {bat-dg2-9}:[PASS][3] -> [DMESG-WARN][4]
> >[3]: 
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/bat-dg2-
> 9/igt@kms_busy@ba...@modeset.html
> >[4]:
> >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dg2: Enable DC5

2022-05-21 Thread Patchwork

== Series Details ==

Series: drm/i915/dg2: Enable DC5
URL   : https://patchwork.freedesktop.org/series/104233/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11681_full -> Patchwork_104233v1_full


Summary
---

  **SUCCESS**

  No regressions found.

  

Participating hosts (13 -> 13)
--

  No changes in participating hosts

Possible new issues
---

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

### IGT changes ###

 Suppressed 

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

  * igt@gem_exec_balancer@full-late:
- {shard-dg1}:[PASS][1] -> [FAIL][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-dg1-17/igt@gem_exec_balan...@full-late.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-dg1-17/igt@gem_exec_balan...@full-late.html

  
Known issues


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

### CI changes ###

 Possible fixes 

  * boot:
- shard-apl:  ([PASS][3], [PASS][4], [PASS][5], [PASS][6], 
[PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], 
[PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], 
[PASS][19], [PASS][20], [PASS][21], [PASS][22], [FAIL][23], [PASS][24], 
[PASS][25], [PASS][26], [PASS][27]) ([i915#4386]) -> ([PASS][28], [PASS][29], 
[PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], 
[PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], 
[PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], 
[PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52])
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [20]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [21]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [22]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [23]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [24]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [25]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [26]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [27]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [28]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl4/boot.html
   [29]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl8/boot.html
   [30]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl8/boot.html
   [31]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl8/boot.html
   [32]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl7/boot.html
   [33]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl7/boot.html
   [34]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl7/boot.html
   [35]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl8/boot.html
   [36]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl7/boot.html
   [37]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl1/boot.html
   [38]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl1/boot.html
   [39]: 
https://int

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5

2022-05-21 Thread Srivatsa, Anusha



> -Original Message-
> From: Roper, Matthew D 
> Sent: Friday, May 20, 2022 4:11 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Srivatsa, Anusha ; Vudum,
> Lakshminarayana 
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5
> 
> On Fri, May 20, 2022 at 05:11:22PM +, Patchwork wrote:
> > == Series Details ==
> >
> > Series: drm/i915/dg2: Enable DC5
> > URL   : https://patchwork.freedesktop.org/series/104233/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from CI_DRM_11681 -> Patchwork_104233v1
> > 
> >
> > Summary
> > ---
> >
> >   **FAILURE**
> >
> >   Serious unknown changes coming with Patchwork_104233v1 absolutely
> need to be
> >   verified manually.
> >
> >   If you think the reported changes have nothing to do with the changes
> >   introduced in Patchwork_104233v1, 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_104233v1/index.html
> >
> > Participating hosts (46 -> 44)
> > --
> >
> >   Missing(2): bat-dg2-8 fi-rkl-11600
> >
> > Possible new issues
> > ---
> >
> >   Here are the unknown changes that may have been introduced in
> Patchwork_104233v1:
> >
> > ### IGT changes ###
> >
> >  Possible regressions 
> >
> >   * igt@fbdev@read:
> > - fi-icl-u2:  [PASS][1] -> [DMESG-WARN][2]
> >[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/fi-icl-
> u2/igt@fb...@read.html
> >[2]:
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/fi-icl-u2/
> > igt@fb...@read.html
> 
> It looks like this is an error coming from a bluetooth driver, not related to
> graphics:
> 
><3> [26.916574] Bluetooth: hci0: Reading Intel version command failed (-
> 110)
><4> [26.916689] general protection fault, probably for non-canonical
> address 0x6b6b6b6b6b6b6b6b:  [#1] PREEMPT SMP NOPTI
><4> [26.916726] CPU: 2 PID: 99 Comm: kworker/2:2 Not tainted 5.18.0-rc7-
> Patchwork_104233v1-gba369855d857+ #1
><4> [26.916731] Hardware name: Intel Corporation Ice Lake Client
> Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS
> ICLSFWR1.R00.3183.A00.1905020411 05/02/2019
><4> [26.916737] Workqueue: events hci_cmd_timeout [bluetooth]
><4> [26.916755] RIP: 0010:hci_cmd_timeout+0x30/0xa0 [bluetooth]
><4> [26.916806] Code: ff ff 53 48 8b 87 10 05 00 00 48 89 fb 48 85 c0 74 63
> 48 8b 80 b8 00 00 00 48 8d b5 a0 00 00 00 48 85 ed 48 c7 c7 c8 6c 38 a0 <0f>
> b7 10 48 c7 c0 53 38 38 a0 48 0f 44 f0 e8 91 13 06 00 48 8b 83
><4> [26.916814] RSP: 0018:c9ae3e50 EFLAGS: 00010286
><4> [26.916818] RAX: 6b6b6b6b6b6b6b6b RBX: 88810ef5aac8 RCX:
> 
><4> [26.916821] RDX: 0001 RSI: 88810ef5a0a0 RDI:
> a0386cc8
><4> [26.916825] RBP: 88810ef5a000 R08: 88810700ba38 R09:
> fffe
><4> [26.916828] R10: 0001 R11: dfbbfb17 R12:
> 88849fb3afc0
><4> [26.916832] R13: 88849fb3fc00 R14:  R15:
> 88849fb3fc05
><4> [26.916835] FS:  () GS:88849fb0()
> knlGS:
><4> [26.916839] CS:  0010 DS:  ES:  CR0: 80050033
><4> [26.916842] CR2: 7fcc6837e1a0 CR3: 06612006 CR4:
> 00770ee0
><4> [26.916846] PKRU: 5554
><4> [26.916848] Call Trace:
><4> [26.916850]  
><4> [26.916852]  process_one_work+0x272/0x5c0
><4> [26.916857]  worker_thread+0x37/0x370
><4> [26.916861]  ? process_one_work+0x5c0/0x5c0
><4> [26.916864]  kthread+0xed/0x120
><4> [26.916867]  ? kthread_complete_and_exit+0x20/0x20
><4> [26.916870]  ret_from_fork+0x1f/0x30
><4> [26.916875]  
> 
> Looks like this might be
> https://gitlab.freedesktop.org/drm/intel/-/issues/4890 ?
Yeah seems like it. 
@Vudum, Lakshminarayana should I resend the series?

Anusha 
> >
> >
> >  Suppressed 
> >
> >   The following results come from untrusted machines, tests, or statuses.
> >   They do not affect the overall result.
> >
> >   * igt@kms_busy@basic@modeset:
> > - {bat-dg2-9}:[PASS][3] -> [DMESG-WARN][4]
> >[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/bat-dg2-
> 9/igt@kms_busy@ba...@modeset.html
> >[4]:
> > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/bat-dg2-9/
> > igt@kms_busy@ba...@modeset.html
> >
> >
> > Known issues
> > 
> >
> >   Here are the changes found in Patchwork_104233v1 that come from
> known issues:
> >
> > ### IGT changes ###
> >
> >  Issues hit 
> >
> >   * igt@i915_selftest@live@hangcheck:
> > - bat-dg1-5:  [PASS][5] -> [DMESG-FAIL][6] ([i915#4494] /
> [i915#4957])
> >[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/bat-dg1-
> 5/igt@i915_selftest@l...@h

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

2022-05-21 Thread Patchwork

== Series Details ==

Series: drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)
URL   : https://patchwork.freedesktop.org/series/103888/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11682_full -> Patchwork_103888v4_full


Summary
---

  **SUCCESS**

  No regressions found.

  

Participating hosts (13 -> 13)
--

  No changes in participating hosts

Known issues


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

### IGT changes ###

 Issues hit 

  * igt@gem_eio@in-flight-immediate:
- shard-skl:  [PASS][1] -> [TIMEOUT][2] ([i915#3063])
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-skl7/igt@gem_...@in-flight-immediate.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-skl5/igt@gem_...@in-flight-immediate.html

  * igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][3] -> [FAIL][4] ([i915#2842])
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-tglb5/igt@gem_exec_fair@basic-f...@rcs0.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-tglb1/igt@gem_exec_fair@basic-f...@rcs0.html

  * igt@gem_exec_fair@basic-none@rcs0:
- shard-kbl:  [PASS][5] -> [FAIL][6] ([i915#2842]) +1 similar issue
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-kbl1/igt@gem_exec_fair@basic-n...@rcs0.html
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-kbl4/igt@gem_exec_fair@basic-n...@rcs0.html

  * igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [PASS][7] -> [FAIL][8] ([i915#2849])
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-iclb4/igt@gem_exec_fair@basic-throt...@rcs0.html
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-iclb7/igt@gem_exec_fair@basic-throt...@rcs0.html

  * igt@gem_exec_flush@basic-uc-pro-default:
- shard-snb:  [PASS][9] -> [SKIP][10] ([fdo#109271]) +1 similar 
issue
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-snb5/igt@gem_exec_fl...@basic-uc-pro-default.html
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-snb6/igt@gem_exec_fl...@basic-uc-pro-default.html

  * igt@gem_lmem_swapping@verify:
- shard-skl:  NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-skl2/igt@gem_lmem_swapp...@verify.html

  * igt@gem_lmem_swapping@verify-random:
- shard-apl:  NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613])
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-apl8/igt@gem_lmem_swapp...@verify-random.html

  * igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][13] -> [FAIL][14] ([i915#454])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-iclb5/igt@i915_pm...@dc6-psr.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-iclb6/igt@i915_pm...@dc6-psr.html

  * igt@i915_pm_rpm@dpms-mode-unset-non-lpsp:
- shard-iclb: NOTRUN -> [SKIP][15] ([fdo#110892])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-iclb7/igt@i915_pm_...@dpms-mode-unset-non-lpsp.html

  * igt@i915_selftest@live@gt_pm:
- shard-skl:  NOTRUN -> [DMESG-FAIL][16] ([i915#1886])
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-skl9/igt@i915_selftest@live@gt_pm.html

  * igt@i915_suspend@fence-restore-tiled2untiled:
- shard-kbl:  [PASS][17] -> [DMESG-WARN][18] ([i915#180])
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/shard-kbl1/igt@i915_susp...@fence-restore-tiled2untiled.html
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-kbl6/igt@i915_susp...@fence-restore-tiled2untiled.html

  * igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip:
- shard-iclb: NOTRUN -> [SKIP][19] ([i915#5286])
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-iclb7/igt@kms_big...@4-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html

  * igt@kms_big_fb@x-tiled-32bpp-rotate-90:
- shard-snb:  NOTRUN -> [SKIP][20] ([fdo#109271]) +21 similar issues
   [20]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-snb2/igt@kms_big...@x-tiled-32bpp-rotate-90.html

  * igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
- shard-skl:  NOTRUN -> [FAIL][21] ([i915#3743])
   [21]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/shard-skl8/igt@kms_big...@x-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html

  * igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl:  NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#3886]) +1 
similar issue
   [22]: 
https://intel-gfx-ci.01.org/tree/dr

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

2022-05-21 Thread Patchwork

== Series Details ==

Series: drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)
URL   : https://patchwork.freedesktop.org/series/103888/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11682 -> Patchwork_103888v4


Summary
---

  **SUCCESS**

  No regressions found.

  External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/index.html

Participating hosts (44 -> 46)
--

  Additional (3): fi-icl-u2 bat-dg2-9 fi-tgl-u2 
  Missing(1): fi-rkl-11600 

Known issues


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

### IGT changes ###

 Issues hit 

  * igt@gem_huc_copy@huc-copy:
- fi-tgl-u2:  NOTRUN -> [SKIP][1] ([i915#2190])
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@gem_huc_c...@huc-copy.html
- fi-icl-u2:  NOTRUN -> [SKIP][2] ([i915#2190])
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@gem_huc_c...@huc-copy.html

  * igt@gem_lmem_swapping@parallel-random-engines:
- fi-icl-u2:  NOTRUN -> [SKIP][3] ([i915#4613]) +3 similar issues
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@gem_lmem_swapp...@parallel-random-engines.html

  * igt@i915_selftest@live@gt_engines:
- bat-dg1-5:  [PASS][4] -> [INCOMPLETE][5] ([i915#4418])
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/bat-dg1-5/igt@i915_selftest@live@gt_engines.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/bat-dg1-5/igt@i915_selftest@live@gt_engines.html

  * igt@i915_selftest@live@gtt:
- fi-bdw-5557u:   [PASS][6] -> [INCOMPLETE][7] ([i915#5685])
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11682/fi-bdw-5557u/igt@i915_selftest@l...@gtt.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-bdw-5557u/igt@i915_selftest@l...@gtt.html

  * igt@i915_suspend@basic-s3-without-i915:
- fi-icl-u2:  NOTRUN -> [SKIP][8] ([i915#5903])
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@i915_susp...@basic-s3-without-i915.html

  * igt@kms_busy@basic@flip:
- fi-tgl-u2:  NOTRUN -> [DMESG-WARN][9] ([i915#402]) +1 similar 
issue
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@kms_busy@ba...@flip.html

  * igt@kms_chamelium@dp-hpd-fast:
- fi-tgl-u2:  NOTRUN -> [SKIP][10] ([fdo#109284] / [fdo#111827]) +7 
similar issues
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@kms_chamel...@dp-hpd-fast.html

  * igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2:  NOTRUN -> [SKIP][11] ([fdo#111827]) +8 similar issues
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@kms_chamel...@hdmi-hpd-fast.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-u2:  NOTRUN -> [SKIP][12] ([i915#4103]) +1 similar issue
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-u2:  NOTRUN -> [SKIP][13] ([fdo#109278]) +2 similar issues
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-legacy.html

  * igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2:  NOTRUN -> [SKIP][14] ([fdo#109285])
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@kms_force_connector_ba...@force-load-detect.html
- fi-icl-u2:  NOTRUN -> [SKIP][15] ([fdo#109285])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@kms_force_connector_ba...@force-load-detect.html

  * igt@kms_setmode@basic-clone-single-crtc:
- fi-icl-u2:  NOTRUN -> [SKIP][16] ([i915#3555])
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@kms_setm...@basic-clone-single-crtc.html
- fi-tgl-u2:  NOTRUN -> [SKIP][17] ([i915#3555])
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@kms_setm...@basic-clone-single-crtc.html

  * igt@prime_vgem@basic-userptr:
- fi-icl-u2:  NOTRUN -> [SKIP][18] ([i915#3301])
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-icl-u2/igt@prime_v...@basic-userptr.html
- fi-tgl-u2:  NOTRUN -> [SKIP][19] ([i915#3301])
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_103888v4/fi-tgl-u2/igt@prime_v...@basic-userptr.html

  
  {name}: This element is suppressed. This means it is ignored when computing
  the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

2022-05-21 Thread Patchwork

== Series Details ==

Series: drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)
URL   : https://patchwork.freedesktop.org/series/103888/
State : warning

== Summary ==

Error: dim checkpatch failed
472d949c1fbf drm/i915/d12+: Disable DMC firmware flip queue handlers
-:170: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dmc_id' - possible 
side-effects?
#170: FILE: drivers/gpu/drm/i915/display/intel_dmc_regs.h:24:
+#define _DMC_REG_MMIO_BASE(i915, dmc_id) \
+   ((dmc_id) == DMC_FW_MAIN ? __DMC_REG_MMIO_BASE : \
+  __PIPEDMC_REG_MMIO_BASE(i915, dmc_id))

total: 0 errors, 0 warnings, 1 checks, 160 lines checked

[Intel-gfx] [PATCH v4] drm/i915/d12+: Disable DMC firmware flip queue handlers

2022-05-21 Thread Imre Deak

Based on a bspec update the DMC firmware's flip queue handling events
need to be disabled before enabling DC5/6. i915 doesn't use the flip
queue feature atm, so disable it already after loading the firmware.
This removes some overhead of the event handler which runs at a 1 kHz
frequency.

Bspec: 49193, 72486, 72487

v2:
- Fix the DMC pipe A register offsets for GEN12.
- Disable the events on DG2 only on pipe A..D .
v3: (Lucas)
- Add TODO: to clarify the disabling sequence on all D13+
- s/intel_dmc_has_fw_payload/has_dmc_id_fw/
- s/simple_flipq/flipq/
- s/_GEN12,_GEN13/TGL_,ADLP_/
- s/MAINDMC/DMC/
v4:
- Only disable flip queues on TGL/DG2, as on other platforms the
  corresponding event handlers don't exist.

Signed-off-by: Imre Deak 
Reviewed-by: Anusha Srivatsa  # v1
Reviewed-by: Lucas De Marchi 
---
 drivers/gpu/drm/i915/display/intel_dmc.c  | 93 ++-
 drivers/gpu/drm/i915/display/intel_dmc_regs.h | 41 
 2 files changed, 133 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c 
b/drivers/gpu/drm/i915/display/intel_dmc.c
index 34d00f5aff257..fa9ef591b8853 100644
--- a/drivers/gpu/drm/i915/display/intel_dmc.c
+++ b/drivers/gpu/drm/i915/display/intel_dmc.c
@@ -248,9 +248,14 @@ struct stepping_info {
char substepping;
 };
 
+static bool has_dmc_id_fw(struct drm_i915_private *i915, int dmc_id)
+{
+   return i915->dmc.dmc_info[dmc_id].payload;
+}
+
 bool intel_dmc_has_payload(struct drm_i915_private *i915)
 {
-   return i915->dmc.dmc_info[DMC_FW_MAIN].payload;
+   return has_dmc_id_fw(i915, DMC_FW_MAIN);
 }
 
 static const struct stepping_info *
@@ -272,6 +277,85 @@ static void gen9_set_dc_state_debugmask(struct 
drm_i915_private *dev_priv)
intel_de_posting_read(dev_priv, DC_STATE_DEBUG);
 }
 
+static void
+disable_flip_queue_event(struct drm_i915_private *i915,
+i915_reg_t ctl_reg, i915_reg_t htp_reg)
+{
+   u32 event_ctl;
+   u32 event_htp;
+
+   event_ctl = intel_de_read(i915, ctl_reg);
+   event_htp = intel_de_read(i915, htp_reg);
+   if (event_ctl != (DMC_EVT_CTL_ENABLE |
+ DMC_EVT_CTL_RECURRING |
+ REG_FIELD_PREP(DMC_EVT_CTL_TYPE_MASK,
+DMC_EVT_CTL_TYPE_EDGE_0_1) |
+ REG_FIELD_PREP(DMC_EVT_CTL_EVENT_ID_MASK,
+DMC_EVT_CTL_EVENT_ID_CLK_MSEC)) ||
+   !event_htp) {
+   drm_dbg_kms(&i915->drm,
+   "Unexpected DMC event configuration (control %08x 
htp %08x)\n",
+   event_ctl, event_htp);
+   return;
+   }
+
+   intel_de_write(i915, ctl_reg,
+  REG_FIELD_PREP(DMC_EVT_CTL_TYPE_MASK,
+ DMC_EVT_CTL_TYPE_EDGE_0_1) |
+  REG_FIELD_PREP(DMC_EVT_CTL_EVENT_ID_MASK,
+ DMC_EVT_CTL_EVENT_ID_FALSE));
+   intel_de_write(i915, htp_reg, 0);
+}
+
+static bool
+get_flip_queue_event_regs(struct drm_i915_private *i915, int dmc_id,
+ i915_reg_t *ctl_reg, i915_reg_t *htp_reg)
+{
+   switch (dmc_id) {
+   case DMC_FW_MAIN:
+   if (DISPLAY_VER(i915) == 12) {
+   *ctl_reg = DMC_EVT_CTL(i915, dmc_id, 3);
+   *htp_reg = DMC_EVT_HTP(i915, dmc_id, 3);
+
+   return true;
+   }
+   break;
+   case DMC_FW_PIPEA ... DMC_FW_PIPED:
+   if (IS_DG2(i915)) {
+   *ctl_reg = DMC_EVT_CTL(i915, dmc_id, 2);
+   *htp_reg = DMC_EVT_HTP(i915, dmc_id, 2);
+
+   return true;
+   }
+   break;
+   }
+
+   return false;
+}
+
+static void
+disable_all_flip_queue_events(struct drm_i915_private *i915)
+{
+   int dmc_id;
+
+   /* TODO: check if the following applies to all D13+ platforms. */
+   if (!IS_DG2(i915) && !IS_TIGERLAKE(i915))
+   return;
+
+   for (dmc_id = 0; dmc_id < DMC_FW_MAX; dmc_id++) {
+   i915_reg_t ctl_reg;
+   i915_reg_t htp_reg;
+
+   if (!has_dmc_id_fw(i915, dmc_id))
+   continue;
+
+   if (!get_flip_queue_event_regs(i915, dmc_id, &ctl_reg, 
&htp_reg))
+   continue;
+
+   disable_flip_queue_event(i915, ctl_reg, htp_reg);
+   }
+}
+
 /**
  * intel_dmc_load_program() - write the firmware from memory to register.
  * @dev_priv: i915 drm device.
@@ -312,6 +396,13 @@ void intel_dmc_load_program(struct drm_i915_private 
*dev_priv)
dev_priv->dmc.dc_state = 0;
 
gen9_set_dc_state_debugmask(dev_priv);
+
+   /*
+* Flip queue events need to be disabled before enabling DC5/6.
+* i915 doesn't use the flip queue feature, so disable it already
+* here.
+*/
+   dis

Re: [Intel-gfx] [PATCH 2/2] x86/pat: add functions to query specific cache mode availability

2022-05-21 Thread Thorsten Leemhuis

On 20.05.22 16:48, Chuck Zmudzinski wrote:
> On 5/20/2022 10:06 AM, Jan Beulich wrote:
>> On 20.05.2022 15:33, Chuck Zmudzinski wrote:
>>> On 5/20/2022 5:41 AM, Jan Beulich wrote:
 On 20.05.2022 10:30, Chuck Zmudzinski wrote:
> On 5/20/2022 2:59 AM, Chuck Zmudzinski wrote:
>> On 5/20/2022 2:05 AM, Jan Beulich wrote:
>>> On 20.05.2022 06:43, Chuck Zmudzinski wrote:
 On 5/4/22 5:14 AM, Juergen Gross wrote:
> On 04.05.22 10:31, Jan Beulich wrote:
>> On 03.05.2022 15:22, Juergen Gross wrote:
>>
>> ... these uses there are several more. You say nothing on why
>> those want
>> leaving unaltered. When preparing my earlier patch I did
>> inspect them
>> and came to the conclusion that these all would also better
>> observe the
>> adjusted behavior (or else I couldn't have left pat_enabled()
>> as the
>> only predicate). In fact, as said in the description of my
>> earlier
>> patch, in
>> my debugging I did find the use in i915_gem_object_pin_map()
>> to be
>> the
>> problematic one, which you leave alone.
> Oh, I missed that one, sorry.
 That is why your patch would not fix my Haswell unless
 it also touches i915_gem_object_pin_map() in
 drivers/gpu/drm/i915/gem/i915_gem_pages.c

> I wanted to be rather defensive in my changes, but I agree at
> least
> the
> case in arch_phys_wc_add() might want to be changed, too.
 I think your approach needs to be more aggressive so it will fix
 all the known false negatives introduced by bdd8b6c98239
 such as the one in i915_gem_object_pin_map().

 I looked at Jan's approach and I think it would fix the issue
 with my Haswell as long as I don't use the nopat option. I
 really don't have a strong opinion on that question, but I
 think the nopat option as a Linux kernel option, as opposed
 to a hypervisor option, should only affect the kernel, and
 if the hypervisor provides the pat feature, then the kernel
 should not override that,
>>> Hmm, why would the kernel not be allowed to override that? Such
>>> an override would affect only the single domain where the
>>> kernel runs; other domains could take their own decisions.
>>>
>>> Also, for the sake of completeness: "nopat" used when running on
>>> bare metal has the same bad effect on system boot, so there
>>> pretty clearly is an error cleanup issue in the i915 driver. But
>>> that's orthogonal, and I expect the maintainers may not even care
>>> (but tell us "don't do that then").
> Actually I just did a test with the last official Debian kernel
> build of Linux 5.16, that is, a kernel before bdd8b6c98239 was
> applied. In fact, the nopat option does *not* break the i915 driver
> in 5.16. That is, with the nopat option, the i915 driver loads
> normally on both the bare metal and on the Xen hypervisor.
> That means your presumption (and the presumption of
> the author of bdd8b6c98239) that the "nopat" option was
> being observed by the i915 driver is incorrect. Setting "nopat"
> had no effect on my system with Linux 5.16. So after doing these
> tests, I am against the aggressive approach of breaking the i915
> driver with the "nopat" option because prior to bdd8b6c98239,
> nopat did not break the i915 driver. Why break it now?
 Because that's, in my understanding, is the purpose of "nopat"
 (not breaking the driver of course - that's a driver bug -, but
 having an effect on the driver).
>>> I wouldn't call it a driver bug, but an incorrect configuration of the
>>> kernel by the user.  I presume X86_FEATURE_PAT is required by the
>>> i915 driver
>> The driver ought to work fine without PAT (and hence without being
>> able to make WC mappings). It would use UC instead and be slow, but
>> it ought to work.
>>
>>> and therefore the driver should refuse to disable
>>> it if the user requests to disable it and instead warn the user that
>>> the driver did not disable the feature, contrary to what the user
>>> requested with the nopat option.
>>>
>>> In any case, my test did not verify that when nopat is set in Linux
>>> 5.16,
>>> the thread takes the same code path as when nopat is not set,
>>> so I am not totally sure that the reason nopat does not break the
>>> i915 driver in 5.16 is that static_cpu_has(X86_FEATURE_PAT)
>>> returns true even when nopat is set. I could test it with a custom
>>> log message in 5.16 if that is necessary.
>>>
>>> Are you saying it was wrong for static_cpu_has(X86_FEATURE_PAT)
>>> to return true in 5.16 when the user requests nopat?
>> No, I'm not saying that. It was wrong for this construct to be used
>> in the driver, which was fixed for 5.17 (and which had caused the
>> regression I di

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: Enable DC5

2022-05-21 Thread Patchwork

== Series Details ==

Series: drm/i915/dg2: Enable DC5
URL   : https://patchwork.freedesktop.org/series/104233/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_11681_full -> Patchwork_104233v1_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_104233v1_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_104233v1_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 -> 12)
--

  Missing(1): shard-rkl 

Possible new issues
---

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

### IGT changes ###

 Possible regressions 

  * igt@i915_pm_dc@dc5-dpms:
- shard-skl:  [PASS][1] -> [INCOMPLETE][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-skl9/igt@i915_pm...@dc5-dpms.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-skl8/igt@i915_pm...@dc5-dpms.html

  
 Suppressed 

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

  * igt@gem_exec_balancer@full-late:
- {shard-dg1}:[PASS][3] -> [FAIL][4]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-dg1-17/igt@gem_exec_balan...@full-late.html
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-dg1-17/igt@gem_exec_balan...@full-late.html

  
Known issues


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

### CI changes ###

 Possible fixes 

  * boot:
- shard-apl:  ([PASS][5], [PASS][6], [PASS][7], [PASS][8], 
[PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], 
[PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], 
[PASS][21], [PASS][22], [PASS][23], [PASS][24], [FAIL][25], [PASS][26], 
[PASS][27], [PASS][28], [PASS][29]) ([i915#4386]) -> ([PASS][30], [PASS][31], 
[PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], 
[PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], 
[PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], 
[PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54])
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl8/boot.html
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl7/boot.html
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl6/boot.html
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [18]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl4/boot.html
   [19]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [20]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [21]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl3/boot.html
   [22]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [23]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [24]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [25]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [26]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl2/boot.html
   [27]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [28]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [29]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11681/shard-apl1/boot.html
   [30]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl1/boot.html
   [31]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl1/boot.html
   [32]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl1/boot.html
   [33]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104233v1/shard-apl2/boot.html
   [34]:

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dg2: Enable DC5

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dg2: Enable DC5

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/d12+: Disable DMC firmware flip queue handlers (rev4)

[Intel-gfx] [PATCH v4] drm/i915/d12+: Disable DMC firmware flip queue handlers

Re: [Intel-gfx] [PATCH 2/2] x86/pat: add functions to query specific cache mode availability

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: Enable DC5

9 matches

Site Navigation

Mail list logo

Footer information