* [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 6:02 ` Steven Rostedt
0 siblings, 0 replies; 18+ messages in thread
From: Steven Rostedt @ 2021-10-02 6:02 UTC (permalink / raw)
To: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama
Cc: LKML, Linus Torvalds, intel-gfx, dri-devel
[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]
When I tried to test patches applied to v5.15-rc3, I hit this bug (and
hence can not test my code), on 32 bit x86.
------------[ cut here ]------------
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
invalid opcode: 0000 [#1] SMP PTI
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-test+ #456
Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
EIP: __i915_sw_fence_init+0x15/0x38
Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
Call Trace:
intel_context_init+0x112/0x145
intel_context_create+0x29/0x37
intel_ring_submission_setup+0x3cb/0x5a8
? kfree+0x135/0x1c6
? wa_init_finish+0x32/0x59
? wa_init_finish+0x4f/0x59
? intel_engine_init_ctx_wa+0x39a/0x3b3
intel_engines_init+0x2dd/0x4d0
? gen6_bsd_submit_request+0x97/0x97
intel_gt_init+0x122/0x20d
i915_gem_init+0x80/0xef
i915_driver_probe+0x880/0xa90
? i915_pci_remove+0x27/0x27
i915_pci_probe+0xdd/0xf6
? __pm_runtime_resume+0x63/0x6b
? i915_pci_remove+0x27/0x27
pci_device_probe+0xbc/0x11e
really_probe+0x13e/0x328
__driver_probe_device+0x140/0x176
driver_probe_device+0x1f/0x71
__driver_attach+0xf6/0x109
? __device_attach_driver+0xbd/0xbd
bus_for_each_dev+0x5b/0x88
driver_attach+0x19/0x1b
? __device_attach_driver+0xbd/0xbd
bus_add_driver+0xf2/0x199
driver_register+0x8c/0xbe
__pci_register_driver+0x5b/0x60
i915_register_pci_driver+0x19/0x1b
i915_init+0x15/0x67
? radeon_module_init+0x6a/0x6a
do_one_initcall+0xce/0x21c
? rcu_read_lock_sched_held+0x35/0x6d
? trace_initcall_level+0x5f/0x99
kernel_init_freeable+0x1fb/0x247
? rest_init+0x129/0x129
kernel_init+0x17/0xfd
ret_from_fork+0x1c/0x28
Modules linked in:
---[ end trace 791dc89810d853da ]---
EIP: __i915_sw_fence_init+0x15/0x38
Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Kernel Offset: disabled
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
Attached is the dmesg and the config.
I bisected it down to this commit:
3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
-- Steve
[-- Attachment #2: mitest-config.gz --]
[-- Type: application/gzip, Size: 36679 bytes --]
[-- Attachment #3: mitest-dmesg.gz --]
[-- Type: application/gzip, Size: 10874 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 6:02 ` Steven Rostedt
0 siblings, 0 replies; 18+ messages in thread
From: Steven Rostedt @ 2021-10-02 6:02 UTC (permalink / raw)
To: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama
Cc: LKML, Linus Torvalds, intel-gfx, dri-devel
[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]
When I tried to test patches applied to v5.15-rc3, I hit this bug (and
hence can not test my code), on 32 bit x86.
------------[ cut here ]------------
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
invalid opcode: 0000 [#1] SMP PTI
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-test+ #456
Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
EIP: __i915_sw_fence_init+0x15/0x38
Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
Call Trace:
intel_context_init+0x112/0x145
intel_context_create+0x29/0x37
intel_ring_submission_setup+0x3cb/0x5a8
? kfree+0x135/0x1c6
? wa_init_finish+0x32/0x59
? wa_init_finish+0x4f/0x59
? intel_engine_init_ctx_wa+0x39a/0x3b3
intel_engines_init+0x2dd/0x4d0
? gen6_bsd_submit_request+0x97/0x97
intel_gt_init+0x122/0x20d
i915_gem_init+0x80/0xef
i915_driver_probe+0x880/0xa90
? i915_pci_remove+0x27/0x27
i915_pci_probe+0xdd/0xf6
? __pm_runtime_resume+0x63/0x6b
? i915_pci_remove+0x27/0x27
pci_device_probe+0xbc/0x11e
really_probe+0x13e/0x328
__driver_probe_device+0x140/0x176
driver_probe_device+0x1f/0x71
__driver_attach+0xf6/0x109
? __device_attach_driver+0xbd/0xbd
bus_for_each_dev+0x5b/0x88
driver_attach+0x19/0x1b
? __device_attach_driver+0xbd/0xbd
bus_add_driver+0xf2/0x199
driver_register+0x8c/0xbe
__pci_register_driver+0x5b/0x60
i915_register_pci_driver+0x19/0x1b
i915_init+0x15/0x67
? radeon_module_init+0x6a/0x6a
do_one_initcall+0xce/0x21c
? rcu_read_lock_sched_held+0x35/0x6d
? trace_initcall_level+0x5f/0x99
kernel_init_freeable+0x1fb/0x247
? rest_init+0x129/0x129
kernel_init+0x17/0xfd
ret_from_fork+0x1c/0x28
Modules linked in:
---[ end trace 791dc89810d853da ]---
EIP: __i915_sw_fence_init+0x15/0x38
Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Kernel Offset: disabled
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
Attached is the dmesg and the config.
I bisected it down to this commit:
3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
-- Steve
[-- Attachment #2: mitest-config.gz --]
[-- Type: application/gzip, Size: 36679 bytes --]
[-- Attachment #3: mitest-dmesg.gz --]
[-- Type: application/gzip, Size: 10874 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 6:02 ` [Intel-gfx] " Steven Rostedt
(?)
@ 2021-10-02 10:17 ` Hugh Dickins
-1 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 10:17 UTC (permalink / raw)
To: Steven Rostedt
Cc: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama, LKML, Linus Torvalds, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Steven Rostedt wrote:
> When I tried to test patches applied to v5.15-rc3, I hit this bug (and
> hence can not test my code), on 32 bit x86.
>
> ------------[ cut here ]------------
> kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
> invalid opcode: 0000 [#1] SMP PTI
> CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-test+ #456
> Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Call Trace:
> intel_context_init+0x112/0x145
> intel_context_create+0x29/0x37
> intel_ring_submission_setup+0x3cb/0x5a8
> ? kfree+0x135/0x1c6
> ? wa_init_finish+0x32/0x59
> ? wa_init_finish+0x4f/0x59
> ? intel_engine_init_ctx_wa+0x39a/0x3b3
> intel_engines_init+0x2dd/0x4d0
> ? gen6_bsd_submit_request+0x97/0x97
> intel_gt_init+0x122/0x20d
> i915_gem_init+0x80/0xef
> i915_driver_probe+0x880/0xa90
> ? i915_pci_remove+0x27/0x27
> i915_pci_probe+0xdd/0xf6
> ? __pm_runtime_resume+0x63/0x6b
> ? i915_pci_remove+0x27/0x27
> pci_device_probe+0xbc/0x11e
> really_probe+0x13e/0x328
> __driver_probe_device+0x140/0x176
> driver_probe_device+0x1f/0x71
> __driver_attach+0xf6/0x109
> ? __device_attach_driver+0xbd/0xbd
> bus_for_each_dev+0x5b/0x88
> driver_attach+0x19/0x1b
> ? __device_attach_driver+0xbd/0xbd
> bus_add_driver+0xf2/0x199
> driver_register+0x8c/0xbe
> __pci_register_driver+0x5b/0x60
> i915_register_pci_driver+0x19/0x1b
> i915_init+0x15/0x67
> ? radeon_module_init+0x6a/0x6a
> do_one_initcall+0xce/0x21c
> ? rcu_read_lock_sched_held+0x35/0x6d
> ? trace_initcall_level+0x5f/0x99
> kernel_init_freeable+0x1fb/0x247
> ? rest_init+0x129/0x129
> kernel_init+0x17/0xfd
> ret_from_fork+0x1c/0x28
> Modules linked in:
> ---[ end trace 791dc89810d853da ]---
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> Kernel Offset: disabled
> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
>
> Attached is the dmesg and the config.
>
> I bisected it down to this commit:
>
> 3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
Yes (though bisection doesn't work right on this one): the fix
https://lore.kernel.org/lkml/1f955bff-fd9e-d2ee-132a-f758add9e9cb@google.com/
seems to have got lost in the system: it has not even appeared in
linux-next yet. I was going to send a reminder later this weekend.
Here it is again (but edited to replace "__aligned(4)" in the original
by the official "__i915_sw_fence_call" I discovered afterwards; and
ignoring recent discussions of where __attributes ought to appear :-)
[PATCH] drm/i915: fix blank screen booting crashes
5.15-rc1 crashes with blank screen when booting up on two ThinkPads
using i915. Bisections converge convincingly, but arrive at different
and suprising "culprits", none of them the actual culprit.
netconsole (with init_netconsole() hacked to call i915_init() when
logging has started, instead of by module_init()) tells the story:
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
with RSI: ffffffff814d408b pointing to sw_fence_dummy_notify().
I've been building with CONFIG_CC_OPTIMIZE_FOR_SIZE=y, and that
function needs to be 4-byte aligned.
Fixes: 62eaf0ae217d ("drm/i915/guc: Support request cancellation")
Signed-off-by: Hugh Dickins <hughd@google.com>
---
drivers/gpu/drm/i915/gt/intel_context.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/i915/gt/intel_context.c
+++ b/drivers/gpu/drm/i915/gt/intel_context.c
@@ -362,6 +362,7 @@ static int __intel_context_active(struct
return 0;
}
+__i915_sw_fence_call /* Respect the I915_SW_FENCE_MASK */
static int sw_fence_dummy_notify(struct i915_sw_fence *sf,
enum i915_sw_fence_notify state)
{
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 10:17 ` Hugh Dickins
0 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 10:17 UTC (permalink / raw)
To: Steven Rostedt
Cc: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama, LKML, Linus Torvalds, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Steven Rostedt wrote:
> When I tried to test patches applied to v5.15-rc3, I hit this bug (and
> hence can not test my code), on 32 bit x86.
>
> ------------[ cut here ]------------
> kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
> invalid opcode: 0000 [#1] SMP PTI
> CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-test+ #456
> Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Call Trace:
> intel_context_init+0x112/0x145
> intel_context_create+0x29/0x37
> intel_ring_submission_setup+0x3cb/0x5a8
> ? kfree+0x135/0x1c6
> ? wa_init_finish+0x32/0x59
> ? wa_init_finish+0x4f/0x59
> ? intel_engine_init_ctx_wa+0x39a/0x3b3
> intel_engines_init+0x2dd/0x4d0
> ? gen6_bsd_submit_request+0x97/0x97
> intel_gt_init+0x122/0x20d
> i915_gem_init+0x80/0xef
> i915_driver_probe+0x880/0xa90
> ? i915_pci_remove+0x27/0x27
> i915_pci_probe+0xdd/0xf6
> ? __pm_runtime_resume+0x63/0x6b
> ? i915_pci_remove+0x27/0x27
> pci_device_probe+0xbc/0x11e
> really_probe+0x13e/0x328
> __driver_probe_device+0x140/0x176
> driver_probe_device+0x1f/0x71
> __driver_attach+0xf6/0x109
> ? __device_attach_driver+0xbd/0xbd
> bus_for_each_dev+0x5b/0x88
> driver_attach+0x19/0x1b
> ? __device_attach_driver+0xbd/0xbd
> bus_add_driver+0xf2/0x199
> driver_register+0x8c/0xbe
> __pci_register_driver+0x5b/0x60
> i915_register_pci_driver+0x19/0x1b
> i915_init+0x15/0x67
> ? radeon_module_init+0x6a/0x6a
> do_one_initcall+0xce/0x21c
> ? rcu_read_lock_sched_held+0x35/0x6d
> ? trace_initcall_level+0x5f/0x99
> kernel_init_freeable+0x1fb/0x247
> ? rest_init+0x129/0x129
> kernel_init+0x17/0xfd
> ret_from_fork+0x1c/0x28
> Modules linked in:
> ---[ end trace 791dc89810d853da ]---
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> Kernel Offset: disabled
> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
>
> Attached is the dmesg and the config.
>
> I bisected it down to this commit:
>
> 3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
Yes (though bisection doesn't work right on this one): the fix
https://lore.kernel.org/lkml/1f955bff-fd9e-d2ee-132a-f758add9e9cb@google.com/
seems to have got lost in the system: it has not even appeared in
linux-next yet. I was going to send a reminder later this weekend.
Here it is again (but edited to replace "__aligned(4)" in the original
by the official "__i915_sw_fence_call" I discovered afterwards; and
ignoring recent discussions of where __attributes ought to appear :-)
[PATCH] drm/i915: fix blank screen booting crashes
5.15-rc1 crashes with blank screen when booting up on two ThinkPads
using i915. Bisections converge convincingly, but arrive at different
and suprising "culprits", none of them the actual culprit.
netconsole (with init_netconsole() hacked to call i915_init() when
logging has started, instead of by module_init()) tells the story:
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
with RSI: ffffffff814d408b pointing to sw_fence_dummy_notify().
I've been building with CONFIG_CC_OPTIMIZE_FOR_SIZE=y, and that
function needs to be 4-byte aligned.
Fixes: 62eaf0ae217d ("drm/i915/guc: Support request cancellation")
Signed-off-by: Hugh Dickins <hughd@google.com>
---
drivers/gpu/drm/i915/gt/intel_context.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/i915/gt/intel_context.c
+++ b/drivers/gpu/drm/i915/gt/intel_context.c
@@ -362,6 +362,7 @@ static int __intel_context_active(struct
return 0;
}
+__i915_sw_fence_call /* Respect the I915_SW_FENCE_MASK */
static int sw_fence_dummy_notify(struct i915_sw_fence *sf,
enum i915_sw_fence_notify state)
{
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 10:17 ` Hugh Dickins
0 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 10:17 UTC (permalink / raw)
To: Steven Rostedt
Cc: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama, LKML, Linus Torvalds, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Steven Rostedt wrote:
> When I tried to test patches applied to v5.15-rc3, I hit this bug (and
> hence can not test my code), on 32 bit x86.
>
> ------------[ cut here ]------------
> kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
> invalid opcode: 0000 [#1] SMP PTI
> CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.14.0-rc1-test+ #456
> Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Call Trace:
> intel_context_init+0x112/0x145
> intel_context_create+0x29/0x37
> intel_ring_submission_setup+0x3cb/0x5a8
> ? kfree+0x135/0x1c6
> ? wa_init_finish+0x32/0x59
> ? wa_init_finish+0x4f/0x59
> ? intel_engine_init_ctx_wa+0x39a/0x3b3
> intel_engines_init+0x2dd/0x4d0
> ? gen6_bsd_submit_request+0x97/0x97
> intel_gt_init+0x122/0x20d
> i915_gem_init+0x80/0xef
> i915_driver_probe+0x880/0xa90
> ? i915_pci_remove+0x27/0x27
> i915_pci_probe+0xdd/0xf6
> ? __pm_runtime_resume+0x63/0x6b
> ? i915_pci_remove+0x27/0x27
> pci_device_probe+0xbc/0x11e
> really_probe+0x13e/0x328
> __driver_probe_device+0x140/0x176
> driver_probe_device+0x1f/0x71
> __driver_attach+0xf6/0x109
> ? __device_attach_driver+0xbd/0xbd
> bus_for_each_dev+0x5b/0x88
> driver_attach+0x19/0x1b
> ? __device_attach_driver+0xbd/0xbd
> bus_add_driver+0xf2/0x199
> driver_register+0x8c/0xbe
> __pci_register_driver+0x5b/0x60
> i915_register_pci_driver+0x19/0x1b
> i915_init+0x15/0x67
> ? radeon_module_init+0x6a/0x6a
> do_one_initcall+0xce/0x21c
> ? rcu_read_lock_sched_held+0x35/0x6d
> ? trace_initcall_level+0x5f/0x99
> kernel_init_freeable+0x1fb/0x247
> ? rest_init+0x129/0x129
> kernel_init+0x17/0xfd
> ret_from_fork+0x1c/0x28
> Modules linked in:
> ---[ end trace 791dc89810d853da ]---
> EIP: __i915_sw_fence_init+0x15/0x38
> Code: 2b 3d 58 98 88 c1 74 05 e8 60 d9 58 00 8d 65 f4 5b 5e 5f 5d c3 3e
> 8d 74 26 00 55 89 e5 56 89 d6 53 85 d2 74 05 f6 c2 03 74 02 <0f> 0b 89
> ca 8b 4d 08 89 c3 e8 48 94 ab ff 89 73 34 c7 43 38 01 00
> EAX: c2508260 EBX: c2508000 ECX: c143de1e EDX: c09dfadd
> ESI: c09dfadd EDI: c45e7200 EBP: c26c9c68 ESP: c26c9c60
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010202
> CR0: 80050033 CR2: 00000000 CR3: 019e2000 CR4: 001506f0
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> Kernel Offset: disabled
> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
>
> Attached is the dmesg and the config.
>
> I bisected it down to this commit:
>
> 3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
Yes (though bisection doesn't work right on this one): the fix
https://lore.kernel.org/lkml/1f955bff-fd9e-d2ee-132a-f758add9e9cb@google.com/
seems to have got lost in the system: it has not even appeared in
linux-next yet. I was going to send a reminder later this weekend.
Here it is again (but edited to replace "__aligned(4)" in the original
by the official "__i915_sw_fence_call" I discovered afterwards; and
ignoring recent discussions of where __attributes ought to appear :-)
[PATCH] drm/i915: fix blank screen booting crashes
5.15-rc1 crashes with blank screen when booting up on two ThinkPads
using i915. Bisections converge convincingly, but arrive at different
and suprising "culprits", none of them the actual culprit.
netconsole (with init_netconsole() hacked to call i915_init() when
logging has started, instead of by module_init()) tells the story:
kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
with RSI: ffffffff814d408b pointing to sw_fence_dummy_notify().
I've been building with CONFIG_CC_OPTIMIZE_FOR_SIZE=y, and that
function needs to be 4-byte aligned.
Fixes: 62eaf0ae217d ("drm/i915/guc: Support request cancellation")
Signed-off-by: Hugh Dickins <hughd@google.com>
---
drivers/gpu/drm/i915/gt/intel_context.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/i915/gt/intel_context.c
+++ b/drivers/gpu/drm/i915/gt/intel_context.c
@@ -362,6 +362,7 @@ static int __intel_context_active(struct
return 0;
}
+__i915_sw_fence_call /* Respect the I915_SW_FENCE_MASK */
static int sw_fence_dummy_notify(struct i915_sw_fence *sf,
enum i915_sw_fence_notify state)
{
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 6:02 ` [Intel-gfx] " Steven Rostedt
(?)
(?)
@ 2021-10-02 10:52 ` Patchwork
-1 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2021-10-02 10:52 UTC (permalink / raw)
To: Hugh Dickins; +Cc: intel-gfx
== Series Details ==
Series: kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
URL : https://patchwork.freedesktop.org/series/95368/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
234e2c966647 kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
-:75: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#75:
> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
-:81: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 3ffe82d701a4 ("drm/i915/xehp: handle new steering options")'
#81:
> 3ffe82d701a4 ("drm/i915/xehp: handle new steering options")
total: 1 errors, 1 warnings, 0 checks, 7 lines checked
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 6:02 ` [Intel-gfx] " Steven Rostedt
` (2 preceding siblings ...)
(?)
@ 2021-10-02 11:26 ` Patchwork
-1 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2021-10-02 11:26 UTC (permalink / raw)
To: Hugh Dickins; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5630 bytes --]
== Series Details ==
Series: kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
URL : https://patchwork.freedesktop.org/series/95368/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680 -> Patchwork_21228
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/index.html
Known issues
------------
Here are the changes found in Patchwork_21228 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@query-info:
- fi-tgl-1115g4: NOTRUN -> [SKIP][1] ([fdo#109315])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@amdgpu/amd_basic@query-info.html
* igt@amdgpu/amd_cs_nop@nop-gfx0:
- fi-tgl-1115g4: NOTRUN -> [SKIP][2] ([fdo#109315] / [i915#2575]) +16 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@amdgpu/amd_cs_nop@nop-gfx0.html
* igt@gem_huc_copy@huc-copy:
- fi-tgl-1115g4: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@gem_huc_copy@huc-copy.html
* igt@i915_pm_backlight@basic-brightness:
- fi-tgl-1115g4: NOTRUN -> [SKIP][4] ([i915#1155])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@i915_pm_backlight@basic-brightness.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-tgl-1115g4: NOTRUN -> [SKIP][5] ([fdo#111827]) +8 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-crc-fast:
- fi-bsw-n3050: NOTRUN -> [SKIP][6] ([fdo#109271] / [fdo#111827]) +8 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-bsw-n3050/igt@kms_chamelium@hdmi-crc-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-1115g4: NOTRUN -> [SKIP][7] ([i915#4103]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-1115g4: NOTRUN -> [SKIP][8] ([fdo#109285])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_pipe_crc_basic@hang-read-crc-pipe-a:
- fi-bsw-n3050: NOTRUN -> [SKIP][9] ([fdo#109271]) +41 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-bsw-n3050/igt@kms_pipe_crc_basic@hang-read-crc-pipe-a.html
* igt@kms_psr@primary_mmap_gtt:
- fi-tgl-1115g4: NOTRUN -> [SKIP][10] ([i915#1072]) +3 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@kms_psr@primary_mmap_gtt.html
* igt@prime_vgem@basic-userptr:
- fi-tgl-1115g4: NOTRUN -> [SKIP][11] ([i915#3301])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-tgl-1115g4/igt@prime_vgem@basic-userptr.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3:
- fi-bsw-n3050: [INCOMPLETE][12] ([i915#2369] / [i915#3159]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/fi-bsw-n3050/igt@gem_exec_suspend@basic-s3.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-bsw-n3050/igt@gem_exec_suspend@basic-s3.html
* igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
- fi-bsw-kefka: [FAIL][14] ([i915#2122]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/fi-bsw-kefka/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/fi-bsw-kefka/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2369]: https://gitlab.freedesktop.org/drm/intel/issues/2369
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#3159]: https://gitlab.freedesktop.org/drm/intel/issues/3159
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
Participating hosts (33 -> 27)
------------------------------
Additional (1): fi-tgl-1115g4
Missing (7): fi-kbl-soraka bat-adls-5 bat-dg1-6 fi-bsw-cyan bat-adlp-4 bat-jsl-2 bat-jsl-1
Build changes
-------------
* Linux: CI_DRM_10680 -> Patchwork_21228
CI-20190529: 20190529
CI_DRM_10680: a5be335f84415ea2d1898be94f5c9a338520aaf5 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6228: 22643ce4014a0b2dc52ce7916b2f657e2a7757c3 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21228: 234e2c966647c5e14ecd448fe498cb7dc3df9172 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
234e2c966647 kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/index.html
[-- Attachment #2: Type: text/html, Size: 6756 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 10:17 ` [Intel-gfx] " Hugh Dickins
@ 2021-10-02 12:17 ` Steven Rostedt
-1 siblings, 0 replies; 18+ messages in thread
From: Steven Rostedt @ 2021-10-02 12:17 UTC (permalink / raw)
To: Hugh Dickins
Cc: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama, LKML, Linus Torvalds, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
Hugh Dickins <hughd@google.com> wrote:
> Yes (though bisection doesn't work right on this one): the fix
Interesting, as it appeared to be very reliable. But I didn't do the
"try before / after" on the patch.
> https://lore.kernel.org/lkml/1f955bff-fd9e-d2ee-132a-f758add9e9cb@google.com/
> seems to have got lost in the system: it has not even appeared in
> linux-next yet. I was going to send a reminder later this weekend.
>
> Here it is again (but edited to replace "__aligned(4)" in the original
> by the official "__i915_sw_fence_call" I discovered afterwards; and
> ignoring recent discussions of where __attributes ought to appear :-)
>
>
> [PATCH] drm/i915: fix blank screen booting crashes
Thanks, I added it to my "fixes" patch set that I apply before testing.
It looks to have done the trick, and the kernel boots now.
Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 12:17 ` Steven Rostedt
0 siblings, 0 replies; 18+ messages in thread
From: Steven Rostedt @ 2021-10-02 12:17 UTC (permalink / raw)
To: Hugh Dickins
Cc: Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi,
Tvrtko Ursulin, Caz Yokoyama, LKML, Linus Torvalds, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
Hugh Dickins <hughd@google.com> wrote:
> Yes (though bisection doesn't work right on this one): the fix
Interesting, as it appeared to be very reliable. But I didn't do the
"try before / after" on the patch.
> https://lore.kernel.org/lkml/1f955bff-fd9e-d2ee-132a-f758add9e9cb@google.com/
> seems to have got lost in the system: it has not even appeared in
> linux-next yet. I was going to send a reminder later this weekend.
>
> Here it is again (but edited to replace "__aligned(4)" in the original
> by the official "__i915_sw_fence_call" I discovered afterwards; and
> ignoring recent discussions of where __attributes ought to appear :-)
>
>
> [PATCH] drm/i915: fix blank screen booting crashes
Thanks, I added it to my "fixes" patch set that I apply before testing.
It looks to have done the trick, and the kernel boots now.
Tested-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 6:02 ` [Intel-gfx] " Steven Rostedt
` (3 preceding siblings ...)
(?)
@ 2021-10-02 12:46 ` Patchwork
-1 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2021-10-02 12:46 UTC (permalink / raw)
To: Hugh Dickins; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30278 bytes --]
== Series Details ==
Series: kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
URL : https://patchwork.freedesktop.org/series/95368/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10680_full -> Patchwork_21228_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_21228_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-apl: NOTRUN -> [DMESG-WARN][1] ([i915#180])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@gem_ctx_isolation@preservation-s3@vecs0.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: NOTRUN -> [TIMEOUT][2] ([i915#2369] / [i915#3063] / [i915#3648])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: NOTRUN -> [FAIL][3] ([i915#2846])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-glk: [PASS][4] -> [FAIL][5] ([i915#2842]) +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk5/igt@gem_exec_fair@basic-none-rrul@rcs0.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk4/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][6] -> [FAIL][7] ([i915#2842])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb8/igt@gem_exec_fair@basic-pace-share@rcs0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_params@no-bsd:
- shard-tglb: NOTRUN -> [SKIP][8] ([fdo#109283])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@gem_exec_params@no-bsd.html
- shard-iclb: NOTRUN -> [SKIP][9] ([fdo#109283])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@gem_exec_params@no-bsd.html
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [PASS][10] -> [DMESG-WARN][11] ([i915#118] / [i915#95])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk7/igt@gem_exec_whisper@basic-queues-forked-all.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk2/igt@gem_exec_whisper@basic-queues-forked-all.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][12] -> [SKIP][13] ([i915#2190])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb2/igt@gem_huc_copy@huc-copy.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb6/igt@gem_huc_copy@huc-copy.html
* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][14] ([i915#2658])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@gem_pread@exhaustion.html
* igt@gem_render_copy@y-tiled-to-vebox-x-tiled:
- shard-glk: NOTRUN -> [SKIP][15] ([fdo#109271]) +3 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk3/igt@gem_render_copy@y-tiled-to-vebox-x-tiled.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#3323])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl6/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][17] ([i915#3318])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl3/igt@gem_userptr_blits@vma-merge.html
* igt@gen7_exec_parse@load-register-reg:
- shard-iclb: NOTRUN -> [SKIP][18] ([fdo#109289])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@gen7_exec_parse@load-register-reg.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-tglb: NOTRUN -> [WARN][19] ([i915#2681])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@i915_pm_rc6_residency@rc6-fence.html
- shard-iclb: NOTRUN -> [WARN][20] ([i915#2684])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-apl: NOTRUN -> [SKIP][21] ([fdo#109271]) +277 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
* igt@i915_pm_rpm@system-suspend-execbuf:
- shard-tglb: [PASS][22] -> [INCOMPLETE][23] ([i915#2411] / [i915#456] / [i915#750])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb3/igt@i915_pm_rpm@system-suspend-execbuf.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb7/igt@i915_pm_rpm@system-suspend-execbuf.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][24] ([fdo#110725] / [fdo#111614])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_big_fb@x-tiled-32bpp-rotate-270.html
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#3777])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-apl: NOTRUN -> [SKIP][26] ([fdo#109271] / [i915#3777])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#3886]) +15 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][28] ([fdo#109271] / [i915#3886]) +6 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][29] ([i915#3689]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_ccs.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3886])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk3/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_chamelium@dp-crc-multiple:
- shard-apl: NOTRUN -> [SKIP][31] ([fdo#109271] / [fdo#111827]) +22 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl3/igt@kms_chamelium@dp-crc-multiple.html
* igt@kms_chamelium@hdmi-hpd-fast:
- shard-tglb: NOTRUN -> [SKIP][32] ([fdo#109284] / [fdo#111827])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_chamelium@vga-hpd-for-each-pipe:
- shard-kbl: NOTRUN -> [SKIP][33] ([fdo#109271] / [fdo#111827]) +13 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_chamelium@vga-hpd-for-each-pipe.html
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-iclb: NOTRUN -> [SKIP][34] ([fdo#109284] / [fdo#111827])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_color_chamelium@pipe-a-ctm-0-25.html
* igt@kms_content_protection@atomic-dpms:
- shard-kbl: NOTRUN -> [TIMEOUT][35] ([i915#1319])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_content_protection@atomic-dpms.html
* igt@kms_content_protection@uevent:
- shard-apl: NOTRUN -> [FAIL][36] ([i915#2105])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@kms_content_protection@uevent.html
* igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding:
- shard-iclb: NOTRUN -> [SKIP][37] ([fdo#109278] / [fdo#109279])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding.html
- shard-tglb: NOTRUN -> [SKIP][38] ([fdo#109279] / [i915#3359])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding.html
* igt@kms_cursor_crc@pipe-d-cursor-dpms:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#109278]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_cursor_crc@pipe-d-cursor-dpms.html
* igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy:
- shard-glk: [PASS][40] -> [FAIL][41] ([i915#72])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk3/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk5/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html
* igt@kms_cursor_legacy@cursorb-vs-flipb-legacy:
- shard-tglb: NOTRUN -> [SKIP][42] ([fdo#111825]) +4 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@kms_cursor_legacy@cursorb-vs-flipb-legacy.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: [PASS][43] -> [FAIL][44] ([i915#2346])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl9/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [PASS][45] -> [FAIL][46] ([i915#2346] / [i915#533])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic:
- shard-glk: [PASS][47] -> [FAIL][48] ([i915#2346])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk1/igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk5/igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic.html
* igt@kms_flip@2x-flip-vs-panning:
- shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109274])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_flip@2x-flip-vs-panning.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [PASS][50] -> [FAIL][51] ([i915#79]) +1 similar issue
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1:
- shard-glk: [PASS][52] -> [FAIL][53] ([i915#79])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk5/igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk7/igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: NOTRUN -> [DMESG-WARN][54] ([i915#180]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl1/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_flip@plain-flip-fb-recreate@c-dp1:
- shard-kbl: NOTRUN -> [FAIL][55] ([i915#2122])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl7/igt@kms_flip@plain-flip-fb-recreate@c-dp1.html
* igt@kms_flip@plain-flip-ts-check-interruptible@c-edp1:
- shard-skl: [PASS][56] -> [FAIL][57] ([i915#2122]) +3 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl1/igt@kms_flip@plain-flip-ts-check-interruptible@c-edp1.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl2/igt@kms_flip@plain-flip-ts-check-interruptible@c-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile:
- shard-iclb: [PASS][58] -> [SKIP][59] ([i915#3701])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb7/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-onoff:
- shard-iclb: NOTRUN -> [SKIP][60] ([fdo#109280]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-onoff.html
* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-wc:
- shard-skl: NOTRUN -> [SKIP][61] ([fdo#109271]) +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl2/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-pwrite:
- shard-skl: [PASS][62] -> [DMESG-WARN][63] ([i915#1982])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-pwrite.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-pwrite.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][64] -> [DMESG-WARN][65] ([i915#180]) +6 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-kbl4/igt@kms_hdr@bpc-switch-suspend.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl4/igt@kms_hdr@bpc-switch-suspend.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#533]) +4 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl3/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][67] ([fdo#108145] / [i915#265]) +3 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl6/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][68] -> [FAIL][69] ([fdo#108145] / [i915#265])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl5/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl5/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][70] ([fdo#108145] / [i915#265])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][71] ([i915#265])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl8/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#658]) +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#658]) +8 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
* igt@kms_psr@psr2_dpms:
- shard-tglb: NOTRUN -> [FAIL][74] ([i915#132] / [i915#3467])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@kms_psr@psr2_dpms.html
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109441])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_psr@psr2_dpms.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [PASS][76] -> [SKIP][77] ([fdo#109441])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb5/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@kms_psr@suspend:
- shard-tglb: [PASS][78] -> [INCOMPLETE][79] ([i915#456])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb5/igt@kms_psr@suspend.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb7/igt@kms_psr@suspend.html
* igt@kms_universal_plane@disable-primary-vs-flip-pipe-d:
- shard-kbl: NOTRUN -> [SKIP][80] ([fdo#109271]) +124 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl4/igt@kms_universal_plane@disable-primary-vs-flip-pipe-d.html
* igt@kms_writeback@writeback-check-output:
- shard-kbl: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#2437])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl7/igt@kms_writeback@writeback-check-output.html
* igt@nouveau_crc@pipe-a-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][82] ([i915#2530])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@nouveau_crc@pipe-a-ctx-flip-detection.html
* igt@perf@polling-small-buf:
- shard-skl: [PASS][83] -> [FAIL][84] ([i915#1722])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl3/igt@perf@polling-small-buf.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl9/igt@perf@polling-small-buf.html
* igt@prime_nv_api@i915_nv_import_vs_close:
- shard-iclb: NOTRUN -> [SKIP][85] ([fdo#109291])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@prime_nv_api@i915_nv_import_vs_close.html
* igt@sysfs_clients@fair-1:
- shard-apl: NOTRUN -> [SKIP][86] ([fdo#109271] / [i915#2994]) +2 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl6/igt@sysfs_clients@fair-1.html
* igt@sysfs_clients@split-50:
- shard-kbl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#2994])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@sysfs_clients@split-50.html
* igt@sysfs_heartbeat_interval@precise@vecs0:
- shard-iclb: [PASS][88] -> [FAIL][89] ([i915#1755])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb3/igt@sysfs_heartbeat_interval@precise@vecs0.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb8/igt@sysfs_heartbeat_interval@precise@vecs0.html
- shard-kbl: NOTRUN -> [FAIL][90] ([i915#1755])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@sysfs_heartbeat_interval@precise@vecs0.html
#### Possible fixes ####
* igt@gem_eio@in-flight-contexts-immediate:
- shard-tglb: [TIMEOUT][91] ([i915#3063]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb8/igt@gem_eio@in-flight-contexts-immediate.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@gem_eio@in-flight-contexts-immediate.html
* igt@gem_eio@in-flight-suspend:
- shard-glk: [DMESG-WARN][93] -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk8/igt@gem_eio@in-flight-suspend.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk3/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [FAIL][95] ([i915#2846]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk9/igt@gem_exec_fair@basic-deadline.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk7/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-apl: [SKIP][97] ([fdo#109271]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl2/igt@gem_exec_fair@basic-none-share@rcs0.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl1/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-apl: [FAIL][99] ([i915#2842]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl7/igt@gem_exec_fair@basic-none@vcs0.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl2/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-tglb: [FAIL][101] ([i915#2842]) -> [PASS][102] +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb1/igt@gem_exec_fair@basic-pace@vecs0.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb5/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_nop@basic-series:
- shard-glk: [DMESG-WARN][103] ([i915#118] / [i915#95]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk6/igt@gem_exec_nop@basic-series.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk8/igt@gem_exec_nop@basic-series.html
* igt@i915_query@query-regions-garbage-items:
- shard-skl: [DMESG-WARN][105] ([i915#1982]) -> [PASS][106] +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl8/igt@i915_query@query-regions-garbage-items.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl10/igt@i915_query@query-regions-garbage-items.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [INCOMPLETE][107] ([i915#180] / [i915#1982]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl7/igt@kms_fbcon_fbt@fbc-suspend.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl8/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@2x-plain-flip-ts-check@ac-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][109] ([i915#2122]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk1/igt@kms_flip@2x-plain-flip-ts-check@ac-hdmi-a1-hdmi-a2.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk6/igt@kms_flip@2x-plain-flip-ts-check@ac-hdmi-a1-hdmi-a2.html
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: [FAIL][111] ([i915#79]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl1/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl1/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
* igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1:
- shard-skl: [FAIL][113] ([i915#2122]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl1/igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl2/igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
- shard-apl: [DMESG-WARN][115] ([i915#180]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
- shard-kbl: [DMESG-WARN][117] ([i915#180]) -> [PASS][118] +6 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-kbl7/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-kbl2/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][119] ([fdo#108145] / [i915#265]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-skl7/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-skl8/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][121] ([fdo#109441]) -> [PASS][122] +3 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb5/igt@kms_psr@psr2_sprite_plane_move.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@sysfs_heartbeat_interval@precise@vecs0:
- shard-tglb: [FAIL][123] ([i915#1755]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-tglb1/igt@sysfs_heartbeat_interval@precise@vecs0.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-tglb2/igt@sysfs_heartbeat_interval@precise@vecs0.html
#### Warnings ####
* igt@gem_exec_fair@basic-none@vcs0:
- shard-iclb: [FAIL][125] -> [FAIL][126] ([i915#2842])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb8/igt@gem_exec_fair@basic-none@vcs0.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb8/igt@gem_exec_fair@basic-none@vcs0.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [FAIL][127] ([i915#2680]) -> [WARN][128] ([i915#2684])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb3/igt@i915_pm_rc6_residency@rc6-idle.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@kms_draw_crc@draw-method-rgb565-blt-ytiled:
- shard-glk: [DMESG-FAIL][129] ([i915#118] / [i915#1888] / [i915#95]) -> [FAIL][130] ([i915#1888] / [i915#3451])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-glk6/igt@kms_draw_crc@draw-method-rgb565-blt-ytiled.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-glk5/igt@kms_draw_crc@draw-method-rgb565-blt-ytiled.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1:
- shard-iclb: [SKIP][131] ([i915#658]) -> [SKIP][132] ([i915#2920])
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb5/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4:
- shard-iclb: [SKIP][133] ([i915#2920]) -> [SKIP][134] ([i915#658])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-iclb1/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4.html
* igt@runner@aborted:
- shard-apl: ([FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139], [FAIL][140], [FAIL][141]) ([fdo#109271] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363]) -> ([FAIL][142], [FAIL][143]) ([i915#180] / [i915#3002] / [i915#3363])
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl6/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl8/igt@runner@aborted.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl2/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl7/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl2/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl6/igt@runner@aborted.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10680/shard-apl1/igt@runner@aborted.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl7/igt@runner@aborted.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/shard-apl8/igt@runner@aborted.html
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109289]: https://bugs.freedesktop.org/show_b
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21228/index.html
[-- Attachment #2: Type: text/html, Size: 35598 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 12:17 ` [Intel-gfx] " Steven Rostedt
(?)
@ 2021-10-02 16:49 ` Linus Torvalds
-1 siblings, 0 replies; 18+ messages in thread
From: Linus Torvalds @ 2021-10-02 16:49 UTC (permalink / raw)
To: Steven Rostedt
Cc: Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> Hugh Dickins <hughd@google.com> wrote:
>
> > Yes (though bisection doesn't work right on this one): the fix
>
> Interesting, as it appeared to be very reliable. But I didn't do the
> "try before / after" on the patch.
Well, even the before/after might well have worked, since the problem
depended on how that sw_fence_dummy_notify() function ended up
aligned. So random unrelated changes could re-align it just by
mistake.
Patch applied directly.
I'd also like to point out how that BUG_ON() actually made things
worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
this would presumably not even have needed bisecting, it would have
been obvious.
BUG_ON() really is pretty much *always* the wrong thing to do. It
onl;y results in problems being harder to see because you end up with
a dead machine and the message is often hidden.
Linus
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 16:49 ` Linus Torvalds
0 siblings, 0 replies; 18+ messages in thread
From: Linus Torvalds @ 2021-10-02 16:49 UTC (permalink / raw)
To: Steven Rostedt
Cc: Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> Hugh Dickins <hughd@google.com> wrote:
>
> > Yes (though bisection doesn't work right on this one): the fix
>
> Interesting, as it appeared to be very reliable. But I didn't do the
> "try before / after" on the patch.
Well, even the before/after might well have worked, since the problem
depended on how that sw_fence_dummy_notify() function ended up
aligned. So random unrelated changes could re-align it just by
mistake.
Patch applied directly.
I'd also like to point out how that BUG_ON() actually made things
worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
this would presumably not even have needed bisecting, it would have
been obvious.
BUG_ON() really is pretty much *always* the wrong thing to do. It
onl;y results in problems being harder to see because you end up with
a dead machine and the message is often hidden.
Linus
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 16:49 ` Linus Torvalds
0 siblings, 0 replies; 18+ messages in thread
From: Linus Torvalds @ 2021-10-02 16:49 UTC (permalink / raw)
To: Steven Rostedt
Cc: Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> Hugh Dickins <hughd@google.com> wrote:
>
> > Yes (though bisection doesn't work right on this one): the fix
>
> Interesting, as it appeared to be very reliable. But I didn't do the
> "try before / after" on the patch.
Well, even the before/after might well have worked, since the problem
depended on how that sw_fence_dummy_notify() function ended up
aligned. So random unrelated changes could re-align it just by
mistake.
Patch applied directly.
I'd also like to point out how that BUG_ON() actually made things
worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
this would presumably not even have needed bisecting, it would have
been obvious.
BUG_ON() really is pretty much *always* the wrong thing to do. It
onl;y results in problems being harder to see because you end up with
a dead machine and the message is often hidden.
Linus
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 16:49 ` [Intel-gfx] " Linus Torvalds
(?)
@ 2021-10-02 17:10 ` Hugh Dickins
-1 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 17:10 UTC (permalink / raw)
To: Linus Torvalds
Cc: Steven Rostedt, Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Linus Torvalds wrote:
> On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> > Hugh Dickins <hughd@google.com> wrote:
> >
> > > Yes (though bisection doesn't work right on this one): the fix
> >
> > Interesting, as it appeared to be very reliable. But I didn't do the
> > "try before / after" on the patch.
>
> Well, even the before/after might well have worked, since the problem
> depended on how that sw_fence_dummy_notify() function ended up
> aligned. So random unrelated changes could re-align it just by
> mistake.
Yup.
>
> Patch applied directly.
Great, thanks a lot.
>
> I'd also like to point out how that BUG_ON() actually made things
> worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
> this would presumably not even have needed bisecting, it would have
> been obvious.
>
> BUG_ON() really is pretty much *always* the wrong thing to do. It
> onl;y results in problems being harder to see because you end up with
> a dead machine and the message is often hidden.
Jani made the same point. But I guess they then went off into the weeds
of how to recover when warning, that the fix itself did not progress.
Hugh
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 17:10 ` Hugh Dickins
0 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 17:10 UTC (permalink / raw)
To: Linus Torvalds
Cc: Steven Rostedt, Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Linus Torvalds wrote:
> On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> > Hugh Dickins <hughd@google.com> wrote:
> >
> > > Yes (though bisection doesn't work right on this one): the fix
> >
> > Interesting, as it appeared to be very reliable. But I didn't do the
> > "try before / after" on the patch.
>
> Well, even the before/after might well have worked, since the problem
> depended on how that sw_fence_dummy_notify() function ended up
> aligned. So random unrelated changes could re-align it just by
> mistake.
Yup.
>
> Patch applied directly.
Great, thanks a lot.
>
> I'd also like to point out how that BUG_ON() actually made things
> worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
> this would presumably not even have needed bisecting, it would have
> been obvious.
>
> BUG_ON() really is pretty much *always* the wrong thing to do. It
> onl;y results in problems being harder to see because you end up with
> a dead machine and the message is often hidden.
Jani made the same point. But I guess they then went off into the weeds
of how to recover when warning, that the fix itself did not progress.
Hugh
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-02 17:10 ` Hugh Dickins
0 siblings, 0 replies; 18+ messages in thread
From: Hugh Dickins @ 2021-10-02 17:10 UTC (permalink / raw)
To: Linus Torvalds
Cc: Steven Rostedt, Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML, Jani Nikula,
Matthew Brost, intel-gfx, dri-devel
On Sat, 2 Oct 2021, Linus Torvalds wrote:
> On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
> > Hugh Dickins <hughd@google.com> wrote:
> >
> > > Yes (though bisection doesn't work right on this one): the fix
> >
> > Interesting, as it appeared to be very reliable. But I didn't do the
> > "try before / after" on the patch.
>
> Well, even the before/after might well have worked, since the problem
> depended on how that sw_fence_dummy_notify() function ended up
> aligned. So random unrelated changes could re-align it just by
> mistake.
Yup.
>
> Patch applied directly.
Great, thanks a lot.
>
> I'd also like to point out how that BUG_ON() actually made things
> worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
> this would presumably not even have needed bisecting, it would have
> been obvious.
>
> BUG_ON() really is pretty much *always* the wrong thing to do. It
> onl;y results in problems being harder to see because you end up with
> a dead machine and the message is often hidden.
Jani made the same point. But I guess they then went off into the weeds
of how to recover when warning, that the fix itself did not progress.
Hugh
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
2021-10-02 17:10 ` Hugh Dickins
@ 2021-10-04 7:39 ` Jani Nikula
-1 siblings, 0 replies; 18+ messages in thread
From: Jani Nikula @ 2021-10-04 7:39 UTC (permalink / raw)
To: Hugh Dickins, Linus Torvalds
Cc: Steven Rostedt, Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML,
Matthew Brost, intel-gfx, dri-devel
On Sat, 02 Oct 2021, Hugh Dickins <hughd@google.com> wrote:
> On Sat, 2 Oct 2021, Linus Torvalds wrote:
>> On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>> > On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
>> > Hugh Dickins <hughd@google.com> wrote:
>> >
>> > > Yes (though bisection doesn't work right on this one): the fix
>> >
>> > Interesting, as it appeared to be very reliable. But I didn't do the
>> > "try before / after" on the patch.
>>
>> Well, even the before/after might well have worked, since the problem
>> depended on how that sw_fence_dummy_notify() function ended up
>> aligned. So random unrelated changes could re-align it just by
>> mistake.
>
> Yup.
>
>>
>> Patch applied directly.
>
> Great, thanks a lot.
Thanks & sorry, really looks like we managed to drop this between the
cracks. :(
>
>>
>> I'd also like to point out how that BUG_ON() actually made things
>> worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
>> this would presumably not even have needed bisecting, it would have
>> been obvious.
>>
>> BUG_ON() really is pretty much *always* the wrong thing to do. It
>> onl;y results in problems being harder to see because you end up with
>> a dead machine and the message is often hidden.
>
> Jani made the same point. But I guess they then went off into the weeds
> of how to recover when warning, that the fix itself did not progress.
Yes. That, as well as removing the entire alignment thing to reuse a
couple of bits for flags. Too fragile for its own good.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
@ 2021-10-04 7:39 ` Jani Nikula
0 siblings, 0 replies; 18+ messages in thread
From: Jani Nikula @ 2021-10-04 7:39 UTC (permalink / raw)
To: Hugh Dickins, Linus Torvalds
Cc: Steven Rostedt, Hugh Dickins, Daniele Ceraolo Spurio, Matt Roper,
Lucas De Marchi, Tvrtko Ursulin, Caz Yokoyama, LKML,
Matthew Brost, intel-gfx, dri-devel
On Sat, 02 Oct 2021, Hugh Dickins <hughd@google.com> wrote:
> On Sat, 2 Oct 2021, Linus Torvalds wrote:
>> On Sat, Oct 2, 2021 at 5:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>> > On Sat, 2 Oct 2021 03:17:29 -0700 (PDT)
>> > Hugh Dickins <hughd@google.com> wrote:
>> >
>> > > Yes (though bisection doesn't work right on this one): the fix
>> >
>> > Interesting, as it appeared to be very reliable. But I didn't do the
>> > "try before / after" on the patch.
>>
>> Well, even the before/after might well have worked, since the problem
>> depended on how that sw_fence_dummy_notify() function ended up
>> aligned. So random unrelated changes could re-align it just by
>> mistake.
>
> Yup.
>
>>
>> Patch applied directly.
>
> Great, thanks a lot.
Thanks & sorry, really looks like we managed to drop this between the
cracks. :(
>
>>
>> I'd also like to point out how that BUG_ON() actually made things
>> worse, and made this harder to debug. If it had been a WARN_ON_ONCE(),
>> this would presumably not even have needed bisecting, it would have
>> been obvious.
>>
>> BUG_ON() really is pretty much *always* the wrong thing to do. It
>> onl;y results in problems being harder to see because you end up with
>> a dead machine and the message is often hidden.
>
> Jani made the same point. But I guess they then went off into the weeds
> of how to recover when warning, that the fix itself did not progress.
Yes. That, as well as removing the entire alignment thing to reuse a
couple of bits for flags. Too fragile for its own good.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2021-10-04 7:39 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-02 6:02 [BUG 5.15-rc3] kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245! Steven Rostedt
2021-10-02 6:02 ` [Intel-gfx] " Steven Rostedt
2021-10-02 10:17 ` Hugh Dickins
2021-10-02 10:17 ` Hugh Dickins
2021-10-02 10:17 ` [Intel-gfx] " Hugh Dickins
2021-10-02 12:17 ` Steven Rostedt
2021-10-02 12:17 ` [Intel-gfx] " Steven Rostedt
2021-10-02 16:49 ` Linus Torvalds
2021-10-02 16:49 ` Linus Torvalds
2021-10-02 16:49 ` [Intel-gfx] " Linus Torvalds
2021-10-02 17:10 ` Hugh Dickins
2021-10-02 17:10 ` [Intel-gfx] " Hugh Dickins
2021-10-02 17:10 ` Hugh Dickins
2021-10-04 7:39 ` Jani Nikula
2021-10-04 7:39 ` [Intel-gfx] " Jani Nikula
2021-10-02 10:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-10-02 11:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-02 12:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.