* 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-16 4:37 ` Hugh Dickins 0 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-16 4:37 UTC (permalink / raw) To: intel-gfx Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Tvrtko Ursulin, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, Hugh Dickins, linux-kernel Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, kernel crashed in some way. I wanted to say what i915 generations these are, but don't know where to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. On the older laptop: First bisection showed first bad commit 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" But reverting that still crashed boot with blank screen (and reverting the two related commits after it made no difference). Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", but patching it out each time before building, showed first bad commit 3ffe82d701a4 "drm/i915/xehp: handle new steering options" That one did not revert cleanly from 5.15-rc1, but reverting 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then 1705f22c86fb "drm/i915/dg2: Update steering tables" then 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then 3ffe82d701a4 "drm/i915/xehp: handle new steering options" worked (there was one very easy fixup needed somewhere). And 5.15-rc1 with those five reversions boots and runs fine... on that older laptop. But reverting those from the kernel on the newer laptop did not help at all, still booting with blank screen (or no more lines shown after the switch from VGA). Put them back. On the newer laptop, bisection showed first bad commit 62eaf0ae217d "drm/i915/guc: Support request cancellation" And 5.15-rc1 with that reverted boots and runs fine on the newer. I am hoping that there will be some i915 fixups to come in a later rc! May be nothing more than uninitialized variables or NULL pointers. You'll probably want more info from me: please ask, but I'm slow. Thanks, Hugh ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-16 4:37 ` Hugh Dickins 0 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-16 4:37 UTC (permalink / raw) To: intel-gfx Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Tvrtko Ursulin, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, Hugh Dickins, linux-kernel Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, kernel crashed in some way. I wanted to say what i915 generations these are, but don't know where to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. On the older laptop: First bisection showed first bad commit 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" But reverting that still crashed boot with blank screen (and reverting the two related commits after it made no difference). Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", but patching it out each time before building, showed first bad commit 3ffe82d701a4 "drm/i915/xehp: handle new steering options" That one did not revert cleanly from 5.15-rc1, but reverting 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then 1705f22c86fb "drm/i915/dg2: Update steering tables" then 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then 3ffe82d701a4 "drm/i915/xehp: handle new steering options" worked (there was one very easy fixup needed somewhere). And 5.15-rc1 with those five reversions boots and runs fine... on that older laptop. But reverting those from the kernel on the newer laptop did not help at all, still booting with blank screen (or no more lines shown after the switch from VGA). Put them back. On the newer laptop, bisection showed first bad commit 62eaf0ae217d "drm/i915/guc: Support request cancellation" And 5.15-rc1 with that reverted boots and runs fine on the newer. I am hoping that there will be some i915 fixups to come in a later rc! May be nothing more than uninitialized variables or NULL pointers. You'll probably want more info from me: please ask, but I'm slow. Thanks, Hugh ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 4:37 ` [Intel-gfx] " Hugh Dickins @ 2021-09-16 8:44 ` Tvrtko Ursulin -1 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2021-09-16 8:44 UTC (permalink / raw) To: Hugh Dickins, intel-gfx Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel Hi, On 16/09/2021 05:37, Hugh Dickins wrote: > Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > kernel crashed in some way. T420s could be SandyBridge and X1 Carbon KabyLake. > I wanted to say what i915 generations these are, but don't know where > to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. > > Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. > > On the older laptop: > > First bisection showed first bad commit > 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" > > But reverting that still crashed boot with blank screen (and > reverting the two related commits after it made no difference). > > Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", > but patching it out each time before building, showed first bad commit > 3ffe82d701a4 "drm/i915/xehp: handle new steering options" > > That one did not revert cleanly from 5.15-rc1, but reverting > 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then > 1705f22c86fb "drm/i915/dg2: Update steering tables" then > 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then > 3ffe82d701a4 "drm/i915/xehp: handle new steering options" > worked (there was one very easy fixup needed somewhere). > > And 5.15-rc1 with those five reversions boots and runs fine... > on that older laptop. But reverting those from the kernel on the > newer laptop did not help at all, still booting with blank screen > (or no more lines shown after the switch from VGA). Put them back. Bisect results sound suspicious since the steering patches do not come into play on SandyBridge. > On the newer laptop, bisection showed first bad commit > 62eaf0ae217d "drm/i915/guc: Support request cancellation" > > And 5.15-rc1 with that reverted boots and runs fine on the newer. But not on the older laptop? Given bisect points to this, it may be worth trying to build both kernels with CONFIG_DRM_I915_REQUEST_TIMEOUT=0 (no reverts) to see what happens. But first the logs which I'll ask next. > I am hoping that there will be some i915 fixups to come in a later rc! > May be nothing more than uninitialized variables or NULL pointers. > You'll probably want more info from me: please ask, but I'm slow. Kernel logs with drm.debug=0xe, with the broken black screen state, would probably answer a lot of questions if you could gather it from both machines? Regards, Tvrtko ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-16 8:44 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2021-09-16 8:44 UTC (permalink / raw) To: Hugh Dickins, intel-gfx Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel Hi, On 16/09/2021 05:37, Hugh Dickins wrote: > Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > kernel crashed in some way. T420s could be SandyBridge and X1 Carbon KabyLake. > I wanted to say what i915 generations these are, but don't know where > to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. > > Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. > > On the older laptop: > > First bisection showed first bad commit > 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" > > But reverting that still crashed boot with blank screen (and > reverting the two related commits after it made no difference). > > Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", > but patching it out each time before building, showed first bad commit > 3ffe82d701a4 "drm/i915/xehp: handle new steering options" > > That one did not revert cleanly from 5.15-rc1, but reverting > 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then > 1705f22c86fb "drm/i915/dg2: Update steering tables" then > 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then > 3ffe82d701a4 "drm/i915/xehp: handle new steering options" > worked (there was one very easy fixup needed somewhere). > > And 5.15-rc1 with those five reversions boots and runs fine... > on that older laptop. But reverting those from the kernel on the > newer laptop did not help at all, still booting with blank screen > (or no more lines shown after the switch from VGA). Put them back. Bisect results sound suspicious since the steering patches do not come into play on SandyBridge. > On the newer laptop, bisection showed first bad commit > 62eaf0ae217d "drm/i915/guc: Support request cancellation" > > And 5.15-rc1 with that reverted boots and runs fine on the newer. But not on the older laptop? Given bisect points to this, it may be worth trying to build both kernels with CONFIG_DRM_I915_REQUEST_TIMEOUT=0 (no reverts) to see what happens. But first the logs which I'll ask next. > I am hoping that there will be some i915 fixups to come in a later rc! > May be nothing more than uninitialized variables or NULL pointers. > You'll probably want more info from me: please ask, but I'm slow. Kernel logs with drm.debug=0xe, with the broken black screen state, would probably answer a lot of questions if you could gather it from both machines? Regards, Tvrtko ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 8:44 ` [Intel-gfx] " Tvrtko Ursulin @ 2021-09-16 10:17 ` Jani Nikula -1 siblings, 0 replies; 19+ messages in thread From: Jani Nikula @ 2021-09-16 10:17 UTC (permalink / raw) To: Tvrtko Ursulin, Hugh Dickins, intel-gfx Cc: Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > Hi, > > On 16/09/2021 05:37, Hugh Dickins wrote: >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, >> kernel crashed in some way. > > T420s could be SandyBridge and X1 Carbon KabyLake. > >> I wanted to say what i915 generations these are, but don't know where >> to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. >> >> Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. >> >> On the older laptop: >> >> First bisection showed first bad commit >> 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" >> >> But reverting that still crashed boot with blank screen (and >> reverting the two related commits after it made no difference). >> >> Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", >> but patching it out each time before building, showed first bad commit >> 3ffe82d701a4 "drm/i915/xehp: handle new steering options" >> >> That one did not revert cleanly from 5.15-rc1, but reverting >> 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then >> 1705f22c86fb "drm/i915/dg2: Update steering tables" then >> 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then >> 3ffe82d701a4 "drm/i915/xehp: handle new steering options" >> worked (there was one very easy fixup needed somewhere). >> >> And 5.15-rc1 with those five reversions boots and runs fine... >> on that older laptop. But reverting those from the kernel on the >> newer laptop did not help at all, still booting with blank screen >> (or no more lines shown after the switch from VGA). Put them back. > > Bisect results sound suspicious since the steering patches do not come > into play on SandyBridge. > >> On the newer laptop, bisection showed first bad commit >> 62eaf0ae217d "drm/i915/guc: Support request cancellation" >> >> And 5.15-rc1 with that reverted boots and runs fine on the newer. > But not on the older laptop? > > Given bisect points to this, it may be worth trying to build both > kernels with CONFIG_DRM_I915_REQUEST_TIMEOUT=0 (no reverts) to see what > happens. But first the logs which I'll ask next. > >> I am hoping that there will be some i915 fixups to come in a later rc! >> May be nothing more than uninitialized variables or NULL pointers. >> You'll probably want more info from me: please ask, but I'm slow. > > Kernel logs with drm.debug=0xe, with the broken black screen state, > would probably answer a lot of questions if you could gather it from > both machines? And for that, I think it's best to file separate bugs at [1] and attach the logs there. It helps keep the info in one place. Thanks. BR, Jani. [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > Regards, > > Tvrtko -- Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-16 10:17 ` Jani Nikula 0 siblings, 0 replies; 19+ messages in thread From: Jani Nikula @ 2021-09-16 10:17 UTC (permalink / raw) To: Tvrtko Ursulin, Hugh Dickins, intel-gfx Cc: Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > Hi, > > On 16/09/2021 05:37, Hugh Dickins wrote: >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, >> kernel crashed in some way. > > T420s could be SandyBridge and X1 Carbon KabyLake. > >> I wanted to say what i915 generations these are, but don't know where >> to look - I don't see it in dmesg, even when DRM_I915_DEBUG enabled. >> >> Possibly relevant: builtin kernels, CONFIG_MODULES off, no initrd. >> >> On the older laptop: >> >> First bisection showed first bad commit >> 41e5c17ebfc2 "drm/i915/guc/slpc: Sysfs hooks for SLPC" >> >> But reverting that still crashed boot with blank screen (and >> reverting the two related commits after it made no difference). >> >> Second bisection, starting from 5.15-rc1 bad and 41e5c17ebfc2 "good", >> but patching it out each time before building, showed first bad commit >> 3ffe82d701a4 "drm/i915/xehp: handle new steering options" >> >> That one did not revert cleanly from 5.15-rc1, but reverting >> 927dfdd09d8c "drm/i915/dg2: Add SQIDI steering" then >> 1705f22c86fb "drm/i915/dg2: Update steering tables" then >> 768fe28dd3dc "drm/i915/xehpsdv: Define steering tables" then >> 3ffe82d701a4 "drm/i915/xehp: handle new steering options" >> worked (there was one very easy fixup needed somewhere). >> >> And 5.15-rc1 with those five reversions boots and runs fine... >> on that older laptop. But reverting those from the kernel on the >> newer laptop did not help at all, still booting with blank screen >> (or no more lines shown after the switch from VGA). Put them back. > > Bisect results sound suspicious since the steering patches do not come > into play on SandyBridge. > >> On the newer laptop, bisection showed first bad commit >> 62eaf0ae217d "drm/i915/guc: Support request cancellation" >> >> And 5.15-rc1 with that reverted boots and runs fine on the newer. > But not on the older laptop? > > Given bisect points to this, it may be worth trying to build both > kernels with CONFIG_DRM_I915_REQUEST_TIMEOUT=0 (no reverts) to see what > happens. But first the logs which I'll ask next. > >> I am hoping that there will be some i915 fixups to come in a later rc! >> May be nothing more than uninitialized variables or NULL pointers. >> You'll probably want more info from me: please ask, but I'm slow. > > Kernel logs with drm.debug=0xe, with the broken black screen state, > would probably answer a lot of questions if you could gather it from > both machines? And for that, I think it's best to file separate bugs at [1] and attach the logs there. It helps keep the info in one place. Thanks. BR, Jani. [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > Regards, > > Tvrtko -- Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 10:17 ` [Intel-gfx] " Jani Nikula @ 2021-09-17 21:26 ` Hugh Dickins -1 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-17 21:26 UTC (permalink / raw) To: Jani Nikula Cc: Tvrtko Ursulin, Hugh Dickins, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Thu, 16 Sep 2021, Jani Nikula wrote: > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > On 16/09/2021 05:37, Hugh Dickins wrote: > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > >> kernel crashed in some way. ... > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > would probably answer a lot of questions if you could gather it from > > both machines? > > And for that, I think it's best to file separate bugs at [1] and attach > the logs there. It helps keep the info in one place. Thanks. > > BR, > Jani. > > [1] https://gitlab.freedesktop.org/drm/intel/issues/new Thanks for the quick replies: but of course, getting kernel logs was the difficult part, this being bootup, with just a blank screen, and no logging to disk at this stage. I've never needed it before, but netconsole to the rescue. Problem then obvious, both machines now working, please let me skip the bug reports, here's a patch: [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 surprising "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; } +__aligned(4) /* 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] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-17 21:26 ` Hugh Dickins 0 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-17 21:26 UTC (permalink / raw) To: Jani Nikula Cc: Tvrtko Ursulin, Hugh Dickins, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Matthew Brost, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Thu, 16 Sep 2021, Jani Nikula wrote: > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > On 16/09/2021 05:37, Hugh Dickins wrote: > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > >> kernel crashed in some way. ... > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > would probably answer a lot of questions if you could gather it from > > both machines? > > And for that, I think it's best to file separate bugs at [1] and attach > the logs there. It helps keep the info in one place. Thanks. > > BR, > Jani. > > [1] https://gitlab.freedesktop.org/drm/intel/issues/new Thanks for the quick replies: but of course, getting kernel logs was the difficult part, this being bootup, with just a blank screen, and no logging to disk at this stage. I've never needed it before, but netconsole to the rescue. Problem then obvious, both machines now working, please let me skip the bug reports, here's a patch: [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 surprising "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; } +__aligned(4) /* 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] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-17 21:26 ` [Intel-gfx] " Hugh Dickins @ 2021-09-17 21:30 ` Matthew Brost -1 siblings, 0 replies; 19+ messages in thread From: Matthew Brost @ 2021-09-17 21:30 UTC (permalink / raw) To: Hugh Dickins Cc: Jani Nikula, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > On Thu, 16 Sep 2021, Jani Nikula wrote: > > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > > On 16/09/2021 05:37, Hugh Dickins wrote: > > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > > >> kernel crashed in some way. > ... > > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > > would probably answer a lot of questions if you could gather it from > > > both machines? > > > > And for that, I think it's best to file separate bugs at [1] and attach > > the logs there. It helps keep the info in one place. Thanks. > > > > BR, > > Jani. > > > > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > Thanks for the quick replies: but of course, getting kernel logs was > the difficult part, this being bootup, with just a blank screen, and > no logging to disk at this stage. I've never needed it before, but > netconsole to the rescue. > > Problem then obvious, both machines now working, > please let me skip the bug reports, here's a patch: > Thanks for finding / fixing this Hugh. I will post this patch in a way our CI system can understand. Matt > [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 surprising "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; > } > > +__aligned(4) /* 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] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-17 21:30 ` Matthew Brost 0 siblings, 0 replies; 19+ messages in thread From: Matthew Brost @ 2021-09-17 21:30 UTC (permalink / raw) To: Hugh Dickins Cc: Jani Nikula, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > On Thu, 16 Sep 2021, Jani Nikula wrote: > > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > > On 16/09/2021 05:37, Hugh Dickins wrote: > > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > > >> kernel crashed in some way. > ... > > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > > would probably answer a lot of questions if you could gather it from > > > both machines? > > > > And for that, I think it's best to file separate bugs at [1] and attach > > the logs there. It helps keep the info in one place. Thanks. > > > > BR, > > Jani. > > > > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > Thanks for the quick replies: but of course, getting kernel logs was > the difficult part, this being bootup, with just a blank screen, and > no logging to disk at this stage. I've never needed it before, but > netconsole to the rescue. > > Problem then obvious, both machines now working, > please let me skip the bug reports, here's a patch: > Thanks for finding / fixing this Hugh. I will post this patch in a way our CI system can understand. Matt > [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 surprising "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; > } > > +__aligned(4) /* 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] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-17 21:30 ` [Intel-gfx] " Matthew Brost @ 2021-09-17 22:52 ` Jani Nikula -1 siblings, 0 replies; 19+ messages in thread From: Jani Nikula @ 2021-09-17 22:52 UTC (permalink / raw) To: Matthew Brost, Hugh Dickins Cc: Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: >> On Thu, 16 Sep 2021, Jani Nikula wrote: >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: >> > > On 16/09/2021 05:37, Hugh Dickins wrote: >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, >> > >> kernel crashed in some way. >> ... >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, >> > > would probably answer a lot of questions if you could gather it from >> > > both machines? >> > >> > And for that, I think it's best to file separate bugs at [1] and attach >> > the logs there. It helps keep the info in one place. Thanks. >> > >> > BR, >> > Jani. >> > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new >> >> Thanks for the quick replies: but of course, getting kernel logs was >> the difficult part, this being bootup, with just a blank screen, and >> no logging to disk at this stage. I've never needed it before, but >> netconsole to the rescue. >> >> Problem then obvious, both machines now working, >> please let me skip the bug reports, here's a patch: >> > > Thanks for finding / fixing this Hugh. I will post this patch in a way > our CI system can understand. Thanks indeed! Matt, please get rid of the BUG_ON while at it, and make it a WARN. Oopsing doesn't do anyone any good. BR, Jani. > > Matt > >> [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 surprising "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; >> } >> >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, >> enum i915_sw_fence_notify state) >> { -- Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-17 22:52 ` Jani Nikula 0 siblings, 0 replies; 19+ messages in thread From: Jani Nikula @ 2021-09-17 22:52 UTC (permalink / raw) To: Matthew Brost, Hugh Dickins Cc: Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: >> On Thu, 16 Sep 2021, Jani Nikula wrote: >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: >> > > On 16/09/2021 05:37, Hugh Dickins wrote: >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, >> > >> kernel crashed in some way. >> ... >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, >> > > would probably answer a lot of questions if you could gather it from >> > > both machines? >> > >> > And for that, I think it's best to file separate bugs at [1] and attach >> > the logs there. It helps keep the info in one place. Thanks. >> > >> > BR, >> > Jani. >> > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new >> >> Thanks for the quick replies: but of course, getting kernel logs was >> the difficult part, this being bootup, with just a blank screen, and >> no logging to disk at this stage. I've never needed it before, but >> netconsole to the rescue. >> >> Problem then obvious, both machines now working, >> please let me skip the bug reports, here's a patch: >> > > Thanks for finding / fixing this Hugh. I will post this patch in a way > our CI system can understand. Thanks indeed! Matt, please get rid of the BUG_ON while at it, and make it a WARN. Oopsing doesn't do anyone any good. BR, Jani. > > Matt > >> [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 surprising "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; >> } >> >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, >> enum i915_sw_fence_notify state) >> { -- Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-17 22:52 ` [Intel-gfx] " Jani Nikula @ 2021-09-17 23:29 ` Matthew Brost -1 siblings, 0 replies; 19+ messages in thread From: Matthew Brost @ 2021-09-17 23:29 UTC (permalink / raw) To: Jani Nikula Cc: Hugh Dickins, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Sat, Sep 18, 2021 at 01:52:48AM +0300, Jani Nikula wrote: > On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > >> On Thu, 16 Sep 2021, Jani Nikula wrote: > >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > >> > > On 16/09/2021 05:37, Hugh Dickins wrote: > >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > >> > >> kernel crashed in some way. > >> ... > >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, > >> > > would probably answer a lot of questions if you could gather it from > >> > > both machines? > >> > > >> > And for that, I think it's best to file separate bugs at [1] and attach > >> > the logs there. It helps keep the info in one place. Thanks. > >> > > >> > BR, > >> > Jani. > >> > > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > >> > >> Thanks for the quick replies: but of course, getting kernel logs was > >> the difficult part, this being bootup, with just a blank screen, and > >> no logging to disk at this stage. I've never needed it before, but > >> netconsole to the rescue. > >> > >> Problem then obvious, both machines now working, > >> please let me skip the bug reports, here's a patch: > >> > > > > Thanks for finding / fixing this Hugh. I will post this patch in a way > > our CI system can understand. > > Thanks indeed! > > Matt, please get rid of the BUG_ON while at it, and make it a > WARN. Oopsing doesn't do anyone any good. > Sure. Will do. Long term we should just look to rip out crap this (i.e. stealing bits from aligned addresses for flags). Matt > BR, > Jani. > > > > > Matt > > > >> [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 surprising "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; > >> } > >> > >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ > >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, > >> enum i915_sw_fence_notify state) > >> { > > -- > Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-17 23:29 ` Matthew Brost 0 siblings, 0 replies; 19+ messages in thread From: Matthew Brost @ 2021-09-17 23:29 UTC (permalink / raw) To: Jani Nikula Cc: Hugh Dickins, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Sat, Sep 18, 2021 at 01:52:48AM +0300, Jani Nikula wrote: > On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > >> On Thu, 16 Sep 2021, Jani Nikula wrote: > >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > >> > > On 16/09/2021 05:37, Hugh Dickins wrote: > >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > >> > >> kernel crashed in some way. > >> ... > >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, > >> > > would probably answer a lot of questions if you could gather it from > >> > > both machines? > >> > > >> > And for that, I think it's best to file separate bugs at [1] and attach > >> > the logs there. It helps keep the info in one place. Thanks. > >> > > >> > BR, > >> > Jani. > >> > > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > >> > >> Thanks for the quick replies: but of course, getting kernel logs was > >> the difficult part, this being bootup, with just a blank screen, and > >> no logging to disk at this stage. I've never needed it before, but > >> netconsole to the rescue. > >> > >> Problem then obvious, both machines now working, > >> please let me skip the bug reports, here's a patch: > >> > > > > Thanks for finding / fixing this Hugh. I will post this patch in a way > > our CI system can understand. > > Thanks indeed! > > Matt, please get rid of the BUG_ON while at it, and make it a > WARN. Oopsing doesn't do anyone any good. > Sure. Will do. Long term we should just look to rip out crap this (i.e. stealing bits from aligned addresses for flags). Matt > BR, > Jani. > > > > > Matt > > > >> [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 surprising "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; > >> } > >> > >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ > >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, > >> enum i915_sw_fence_notify state) > >> { > > -- > Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-17 23:29 ` [Intel-gfx] " Matthew Brost @ 2021-09-18 0:22 ` Hugh Dickins -1 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-18 0:22 UTC (permalink / raw) To: Matthew Brost Cc: Jani Nikula, Hugh Dickins, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, 17 Sep 2021, Matthew Brost wrote: > On Sat, Sep 18, 2021 at 01:52:48AM +0300, Jani Nikula wrote: > > On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > > > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > > >> On Thu, 16 Sep 2021, Jani Nikula wrote: > > >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > >> > > On 16/09/2021 05:37, Hugh Dickins wrote: > > >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > > >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > > >> > >> kernel crashed in some way. > > >> ... > > >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > >> > > would probably answer a lot of questions if you could gather it from > > >> > > both machines? > > >> > > > >> > And for that, I think it's best to file separate bugs at [1] and attach > > >> > the logs there. It helps keep the info in one place. Thanks. > > >> > > > >> > BR, > > >> > Jani. > > >> > > > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > >> > > >> Thanks for the quick replies: but of course, getting kernel logs was > > >> the difficult part, this being bootup, with just a blank screen, and > > >> no logging to disk at this stage. I've never needed it before, but > > >> netconsole to the rescue. > > >> > > >> Problem then obvious, both machines now working, > > >> please let me skip the bug reports, here's a patch: > > >> > > > > > > Thanks for finding / fixing this Hugh. I will post this patch in a way > > > our CI system can understand. > > > > Thanks indeed! > > > > Matt, please get rid of the BUG_ON while at it, and make it a > > WARN. Oopsing doesn't do anyone any good. > > > > Sure. Will do. Long term we should just look to rip out crap this (i.e. > stealing bits from aligned addresses for flags). It just crossed my mind, that I never did due diligence on _other_ callers of i915_sw_fence_init(). In fact they're okay, but that's because their fence functions are all declared with the #define __i915_sw_fence_call __aligned(4) from i915_sw_fence.h, which I had not seen when I sent the patch. I'm not going to resend, but if I were you, I'd quietly edit that patch to use __i915_sw_fence_call in place of my __aligned(4). Thanks, Hugh > > Matt > > > BR, > > Jani. > > > > > > > > Matt > > > > > >> [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 surprising "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; > > >> } > > >> > > >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ > > >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, > > >> enum i915_sw_fence_notify state) > > >> { > > > > -- > > Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] 5.15-rc1 i915 blank screen booting on ThinkPads @ 2021-09-18 0:22 ` Hugh Dickins 0 siblings, 0 replies; 19+ messages in thread From: Hugh Dickins @ 2021-09-18 0:22 UTC (permalink / raw) To: Matthew Brost Cc: Jani Nikula, Hugh Dickins, Tvrtko Ursulin, intel-gfx, Joonas Lahtinen, Rodrigo Vivi, Vinay Belgaumkar, Michal Wajdeczko, Sujaritha Sundaresan, John Harrison, Daniele Ceraolo Spurio, Matt Roper, Lucas De Marchi, Dave Airlie, Daniel Vetter, Pavel Machek, linux-kernel On Fri, 17 Sep 2021, Matthew Brost wrote: > On Sat, Sep 18, 2021 at 01:52:48AM +0300, Jani Nikula wrote: > > On Fri, 17 Sep 2021, Matthew Brost <matthew.brost@intel.com> wrote: > > > On Fri, Sep 17, 2021 at 02:26:48PM -0700, Hugh Dickins wrote: > > >> On Thu, 16 Sep 2021, Jani Nikula wrote: > > >> > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: > > >> > > On 16/09/2021 05:37, Hugh Dickins wrote: > > >> > >> Two Lenovo ThinkPads, old T420s (2011), newer X1 Carbon 5th gen (2017): > > >> > >> i915 working fine on both up to 5.14, but blank screens booting 5.15-rc1, > > >> > >> kernel crashed in some way. > > >> ... > > >> > > Kernel logs with drm.debug=0xe, with the broken black screen state, > > >> > > would probably answer a lot of questions if you could gather it from > > >> > > both machines? > > >> > > > >> > And for that, I think it's best to file separate bugs at [1] and attach > > >> > the logs there. It helps keep the info in one place. Thanks. > > >> > > > >> > BR, > > >> > Jani. > > >> > > > >> > [1] https://gitlab.freedesktop.org/drm/intel/issues/new > > >> > > >> Thanks for the quick replies: but of course, getting kernel logs was > > >> the difficult part, this being bootup, with just a blank screen, and > > >> no logging to disk at this stage. I've never needed it before, but > > >> netconsole to the rescue. > > >> > > >> Problem then obvious, both machines now working, > > >> please let me skip the bug reports, here's a patch: > > >> > > > > > > Thanks for finding / fixing this Hugh. I will post this patch in a way > > > our CI system can understand. > > > > Thanks indeed! > > > > Matt, please get rid of the BUG_ON while at it, and make it a > > WARN. Oopsing doesn't do anyone any good. > > > > Sure. Will do. Long term we should just look to rip out crap this (i.e. > stealing bits from aligned addresses for flags). It just crossed my mind, that I never did due diligence on _other_ callers of i915_sw_fence_init(). In fact they're okay, but that's because their fence functions are all declared with the #define __i915_sw_fence_call __aligned(4) from i915_sw_fence.h, which I had not seen when I sent the patch. I'm not going to resend, but if I were you, I'd quietly edit that patch to use __i915_sw_fence_call in place of my __aligned(4). Thanks, Hugh > > Matt > > > BR, > > Jani. > > > > > > > > Matt > > > > > >> [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 surprising "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; > > >> } > > >> > > >> +__aligned(4) /* Respect the I915_SW_FENCE_MASK */ > > >> static int sw_fence_dummy_notify(struct i915_sw_fence *sf, > > >> enum i915_sw_fence_notify state) > > >> { > > > > -- > > Jani Nikula, Intel Open Source Graphics Center ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 4:37 ` [Intel-gfx] " Hugh Dickins (?) (?) @ 2021-09-17 22:11 ` Patchwork -1 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2021-09-17 22:11 UTC (permalink / raw) To: Hugh Dickins; +Cc: intel-gfx == Series Details == Series: 5.15-rc1 i915 blank screen booting on ThinkPads URL : https://patchwork.freedesktop.org/series/94820/ State : warning == Summary == $ dim checkpatch origin/drm-tip 0a23b1f1e8f8 5.15-rc1 i915 blank screen booting on ThinkPads -:7: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #7: > On Thu, 16 Sep 2021, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote: total: 0 errors, 1 warnings, 0 checks, 7 lines checked ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 4:37 ` [Intel-gfx] " Hugh Dickins ` (2 preceding siblings ...) (?) @ 2021-09-17 22:37 ` Patchwork -1 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2021-09-17 22:37 UTC (permalink / raw) To: Hugh Dickins; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 10007 bytes --] == Series Details == Series: 5.15-rc1 i915 blank screen booting on ThinkPads URL : https://patchwork.freedesktop.org/series/94820/ State : success == Summary == CI Bug Log - changes from CI_DRM_10605 -> Patchwork_21089 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/index.html Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_21089: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@i915_module_load@reload: - {fi-ehl-2}: [INCOMPLETE][1] ([i915#4136]) -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-ehl-2/igt@i915_module_load@reload.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-ehl-2/igt@i915_module_load@reload.html - {fi-jsl-1}: [TIMEOUT][3] ([i915#4136]) -> [INCOMPLETE][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-jsl-1/igt@i915_module_load@reload.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-jsl-1/igt@i915_module_load@reload.html Known issues ------------ Here are the changes found in Patchwork_21089 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@amdgpu/amd_basic@cs-sdma: - fi-cfl-8109u: NOTRUN -> [SKIP][5] ([fdo#109271]) +17 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-cfl-8109u/igt@amdgpu/amd_basic@cs-sdma.html - fi-kbl-7500u: NOTRUN -> [SKIP][6] ([fdo#109271]) +17 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-7500u/igt@amdgpu/amd_basic@cs-sdma.html * igt@amdgpu/amd_basic@semaphore: - fi-icl-y: NOTRUN -> [SKIP][7] ([fdo#109315]) +17 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-icl-y/igt@amdgpu/amd_basic@semaphore.html * igt@core_hotunplug@unbind-rebind: - fi-cfl-guc: [PASS][8] -> [INCOMPLETE][9] ([i915#4130]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-cfl-guc/igt@core_hotunplug@unbind-rebind.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-cfl-guc/igt@core_hotunplug@unbind-rebind.html - fi-tgl-1115g4: NOTRUN -> [INCOMPLETE][10] ([i915#4130]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@core_hotunplug@unbind-rebind.html - fi-icl-u2: [PASS][11] -> [INCOMPLETE][12] ([i915#4130]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-icl-u2/igt@core_hotunplug@unbind-rebind.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-icl-u2/igt@core_hotunplug@unbind-rebind.html * igt@gem_huc_copy@huc-copy: - fi-tgl-1115g4: NOTRUN -> [SKIP][13] ([i915#2190]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@gem_huc_copy@huc-copy.html * igt@i915_pm_backlight@basic-brightness: - fi-tgl-1115g4: NOTRUN -> [SKIP][14] ([i915#1155]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@i915_pm_backlight@basic-brightness.html * igt@kms_chamelium@common-hpd-after-suspend: - fi-tgl-1115g4: NOTRUN -> [SKIP][15] ([fdo#111827]) +8 similar issues [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@kms_chamelium@common-hpd-after-suspend.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: - fi-tgl-1115g4: NOTRUN -> [SKIP][16] ([i915#4103]) +1 similar issue [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/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][17] ([fdo#109285]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@kms_force_connector_basic@force-load-detect.html * igt@kms_psr@primary_mmap_gtt: - fi-tgl-1115g4: NOTRUN -> [SKIP][18] ([i915#1072]) +3 similar issues [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@kms_psr@primary_mmap_gtt.html * igt@prime_vgem@basic-userptr: - fi-tgl-1115g4: NOTRUN -> [SKIP][19] ([i915#3301]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@prime_vgem@basic-userptr.html * igt@runner@aborted: - fi-tgl-1115g4: NOTRUN -> [FAIL][20] ([i915#1602] / [i915#2722]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-tgl-1115g4/igt@runner@aborted.html - fi-skl-6700k2: NOTRUN -> [FAIL][21] ([i915#2426] / [i915#3363]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-skl-6700k2/igt@runner@aborted.html #### Possible fixes #### * igt@core_hotunplug@unbind-rebind: - fi-kbl-7500u: [INCOMPLETE][22] ([i915#4130]) -> [PASS][23] [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-kbl-7500u/igt@core_hotunplug@unbind-rebind.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-7500u/igt@core_hotunplug@unbind-rebind.html - fi-cfl-8109u: [INCOMPLETE][24] ([i915#4130]) -> [PASS][25] [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-cfl-8109u/igt@core_hotunplug@unbind-rebind.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-cfl-8109u/igt@core_hotunplug@unbind-rebind.html * igt@i915_module_load@reload: - fi-kbl-7567u: [DMESG-WARN][26] ([i915#4136]) -> [PASS][27] [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-kbl-7567u/igt@i915_module_load@reload.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-7567u/igt@i915_module_load@reload.html - fi-icl-y: [INCOMPLETE][28] ([i915#4130]) -> [PASS][29] [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-icl-y/igt@i915_module_load@reload.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-icl-y/igt@i915_module_load@reload.html #### Warnings #### * igt@i915_module_load@reload: - fi-kbl-8809g: [INCOMPLETE][30] ([i915#4136]) -> [INCOMPLETE][31] ([i915#4130]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-kbl-8809g/igt@i915_module_load@reload.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-8809g/igt@i915_module_load@reload.html - fi-cml-u2: [INCOMPLETE][32] ([i915#4130] / [i915#4136]) -> [INCOMPLETE][33] ([i915#4130]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-cml-u2/igt@i915_module_load@reload.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-cml-u2/igt@i915_module_load@reload.html - fi-kbl-soraka: [INCOMPLETE][34] ([i915#4130] / [i915#4136]) -> [INCOMPLETE][35] ([i915#4130]) [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-kbl-soraka/igt@i915_module_load@reload.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-soraka/igt@i915_module_load@reload.html - fi-skl-6700k2: [INCOMPLETE][36] ([i915#4136]) -> [INCOMPLETE][37] ([i915#4130]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-skl-6700k2/igt@i915_module_load@reload.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-skl-6700k2/igt@i915_module_load@reload.html - fi-kbl-guc: [INCOMPLETE][38] ([i915#4139]) -> [INCOMPLETE][39] ([i915#4130] / [i915#4139]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/fi-kbl-guc/igt@i915_module_load@reload.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/fi-kbl-guc/igt@i915_module_load@reload.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [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#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602 [i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122 [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190 [i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426 [i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722 [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301 [i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363 [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4130]: https://gitlab.freedesktop.org/drm/intel/issues/4130 [i915#4136]: https://gitlab.freedesktop.org/drm/intel/issues/4136 [i915#4139]: https://gitlab.freedesktop.org/drm/intel/issues/4139 Participating hosts (38 -> 32) ------------------------------ Additional (1): fi-tgl-1115g4 Missing (7): fi-ilk-m540 bat-dg1-6 fi-tgl-u2 fi-hsw-4200u fi-ctg-p8600 bat-jsl-2 fi-bdw-samus Build changes ------------- * Linux: CI_DRM_10605 -> Patchwork_21089 CI-20190529: 20190529 CI_DRM_10605: e61e36045f57a5aaeef91f54274937843ee3d0d5 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6211: 7b275b3eb17ddf6e7c5b7b9ba359b7f5345a5311 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_21089: 0a23b1f1e8f81bcf74008982e1f8807985ff94c3 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 0a23b1f1e8f8 5.15-rc1 i915 blank screen booting on ThinkPads == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/index.html [-- Attachment #2: Type: text/html, Size: 12451 bytes --] ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for 5.15-rc1 i915 blank screen booting on ThinkPads 2021-09-16 4:37 ` [Intel-gfx] " Hugh Dickins ` (3 preceding siblings ...) (?) @ 2021-09-18 0:32 ` Patchwork -1 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2021-09-18 0:32 UTC (permalink / raw) To: Hugh Dickins; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 29956 bytes --] == Series Details == Series: 5.15-rc1 i915 blank screen booting on ThinkPads URL : https://patchwork.freedesktop.org/series/94820/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10605_full -> Patchwork_21089_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_21089_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_21089_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_21089_full: ### IGT changes ### #### Possible regressions #### * igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs: - shard-kbl: NOTRUN -> [INCOMPLETE][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs: - shard-tglb: [PASS][2] -> [INCOMPLETE][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-tglb8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html Known issues ------------ Here are the changes found in Patchwork_21089_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_eio@unwedge-stress: - shard-skl: [PASS][4] -> [TIMEOUT][5] ([i915#2369] / [i915#3063]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl5/igt@gem_eio@unwedge-stress.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl6/igt@gem_eio@unwedge-stress.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_10605/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@gem_exec_fair@basic-pace@vcs1: - shard-iclb: NOTRUN -> [FAIL][8] ([i915#2842]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb1/igt@gem_exec_fair@basic-pace@vcs1.html * igt@gem_exec_params@rsvd2-dirt: - shard-tglb: NOTRUN -> [SKIP][9] ([fdo#109283]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@gem_exec_params@rsvd2-dirt.html * igt@gem_exec_suspend@basic-s0: - shard-tglb: [PASS][10] -> [INCOMPLETE][11] ([i915#456]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-tglb2/igt@gem_exec_suspend@basic-s0.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb7/igt@gem_exec_suspend@basic-s0.html * igt@gem_exec_suspend@basic-s3: - shard-kbl: [PASS][12] -> [DMESG-WARN][13] ([i915#180]) +2 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl1/igt@gem_exec_suspend@basic-s3.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl3/igt@gem_exec_suspend@basic-s3.html * igt@gem_huc_copy@huc-copy: - shard-kbl: NOTRUN -> [SKIP][14] ([fdo#109271] / [i915#2190]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@gem_huc_copy@huc-copy.html * igt@gem_media_vme: - shard-tglb: NOTRUN -> [SKIP][15] ([i915#284]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@gem_media_vme.html * igt@gem_pread@exhaustion: - shard-skl: NOTRUN -> [WARN][16] ([i915#2658]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl3/igt@gem_pread@exhaustion.html * igt@gen9_exec_parse@valid-registers: - shard-tglb: NOTRUN -> [SKIP][17] ([i915#2856]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@gen9_exec_parse@valid-registers.html * igt@i915_pm_rpm@pc8-residency: - shard-tglb: NOTRUN -> [SKIP][18] ([fdo#109506] / [i915#2411]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@i915_pm_rpm@pc8-residency.html * igt@i915_pm_rpm@system-suspend-execbuf: - shard-tglb: [PASS][19] -> [INCOMPLETE][20] ([i915#2411] / [i915#456] / [i915#750]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-tglb5/igt@i915_pm_rpm@system-suspend-execbuf.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb7/igt@i915_pm_rpm@system-suspend-execbuf.html * igt@kms_big_fb@linear-8bpp-rotate-270: - shard-tglb: NOTRUN -> [SKIP][21] ([fdo#111614]) +1 similar issue [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_big_fb@linear-8bpp-rotate-270.html * igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip: - shard-kbl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#3777]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl4/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip.html * igt@kms_big_fb@yf-tiled-addfb-size-offset-overflow: - shard-tglb: NOTRUN -> [SKIP][23] ([fdo#111615]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_big_fb@yf-tiled-addfb-size-offset-overflow.html * igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc: - shard-kbl: NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#3886]) +6 similar issues [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl4/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs: - shard-iclb: NOTRUN -> [SKIP][25] ([fdo#109278] / [i915#3886]) [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs: - shard-tglb: NOTRUN -> [SKIP][26] ([i915#3689] / [i915#3886]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-d-crc-primary-basic-yf_tiled_ccs: - shard-tglb: NOTRUN -> [SKIP][27] ([i915#3689]) +1 similar issue [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_ccs@pipe-d-crc-primary-basic-yf_tiled_ccs.html * igt@kms_color@pipe-c-ctm-0-75: - shard-skl: [PASS][28] -> [DMESG-WARN][29] ([i915#1982]) +1 similar issue [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl1/igt@kms_color@pipe-c-ctm-0-75.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl7/igt@kms_color@pipe-c-ctm-0-75.html * igt@kms_color_chamelium@pipe-a-ctm-0-75: - shard-kbl: NOTRUN -> [SKIP][30] ([fdo#109271] / [fdo#111827]) +16 similar issues [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_color_chamelium@pipe-a-ctm-0-75.html * igt@kms_color_chamelium@pipe-a-ctm-blue-to-red: - shard-skl: NOTRUN -> [SKIP][31] ([fdo#109271] / [fdo#111827]) +1 similar issue [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl9/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html * igt@kms_color_chamelium@pipe-b-ctm-negative: - shard-tglb: NOTRUN -> [SKIP][32] ([fdo#109284] / [fdo#111827]) +2 similar issues [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_color_chamelium@pipe-b-ctm-negative.html * igt@kms_content_protection@dp-mst-lic-type-1: - shard-tglb: NOTRUN -> [SKIP][33] ([i915#3116]) [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_content_protection@dp-mst-lic-type-1.html * igt@kms_content_protection@lic: - shard-kbl: NOTRUN -> [TIMEOUT][34] ([i915#1319]) [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_content_protection@lic.html * igt@kms_cursor_crc@pipe-a-cursor-512x512-onscreen: - shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109278] / [fdo#109279]) +1 similar issue [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@kms_cursor_crc@pipe-a-cursor-512x512-onscreen.html * igt@kms_cursor_crc@pipe-c-cursor-32x10-offscreen: - shard-tglb: NOTRUN -> [SKIP][36] ([i915#3359]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_cursor_crc@pipe-c-cursor-32x10-offscreen.html * igt@kms_cursor_crc@pipe-d-cursor-512x512-offscreen: - shard-tglb: NOTRUN -> [SKIP][37] ([fdo#109279] / [i915#3359]) [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_cursor_crc@pipe-d-cursor-512x512-offscreen.html * igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding: - shard-iclb: NOTRUN -> [SKIP][38] ([fdo#109278]) +1 similar issue [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding.html * igt@kms_cursor_edge_walk@pipe-d-64x64-left-edge: - shard-kbl: NOTRUN -> [SKIP][39] ([fdo#109271]) +142 similar issues [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_cursor_edge_walk@pipe-d-64x64-left-edge.html * igt@kms_cursor_legacy@cursora-vs-flipb-atomic: - shard-iclb: NOTRUN -> [SKIP][40] ([fdo#109274] / [fdo#109278]) [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@kms_cursor_legacy@cursora-vs-flipb-atomic.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-skl: [PASS][41] -> [FAIL][42] ([i915#2346] / [i915#533]) [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html * igt@kms_flip@flip-vs-blocking-wf-vblank@c-edp1: - shard-skl: [PASS][43] -> [FAIL][44] ([i915#2122]) [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl9/igt@kms_flip@flip-vs-blocking-wf-vblank@c-edp1.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl2/igt@kms_flip@flip-vs-blocking-wf-vblank@c-edp1.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1: - shard-skl: [PASS][45] -> [FAIL][46] ([i915#79]) [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl6/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl8/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-onoff: - shard-skl: NOTRUN -> [SKIP][47] ([fdo#109271]) +6 similar issues [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl10/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-shrfb-msflip-blt: - shard-tglb: NOTRUN -> [SKIP][48] ([fdo#111825]) +11 similar issues [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-shrfb-msflip-blt.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-blt: - shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109280]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-blt.html * igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d: - shard-kbl: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#533]) [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d.html * igt@kms_plane_alpha_blend@pipe-a-coverage-7efc: - shard-skl: [PASS][51] -> [FAIL][52] ([fdo#108145] / [i915#265]) [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl8/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html * igt@kms_plane_alpha_blend@pipe-c-alpha-7efc: - shard-kbl: NOTRUN -> [FAIL][53] ([fdo#108145] / [i915#265]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html * igt@kms_plane_lowres@pipe-b-tiling-none: - shard-tglb: NOTRUN -> [SKIP][54] ([i915#3536]) [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_plane_lowres@pipe-b-tiling-none.html * igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1: - shard-kbl: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#658]) +2 similar issues [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl4/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5: - shard-tglb: NOTRUN -> [SKIP][56] ([i915#2920]) +1 similar issue [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html * igt@kms_psr@psr2_no_drrs: - shard-iclb: [PASS][57] -> [SKIP][58] ([fdo#109441]) +1 similar issue [57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb2/igt@kms_psr@psr2_no_drrs.html [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb1/igt@kms_psr@psr2_no_drrs.html * igt@perf@polling-parameterized: - shard-skl: [PASS][59] -> [FAIL][60] ([i915#1542]) [59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl7/igt@perf@polling-parameterized.html [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl3/igt@perf@polling-parameterized.html * igt@perf_pmu@rc6-suspend: - shard-kbl: NOTRUN -> [DMESG-WARN][61] ([i915#180]) +1 similar issue [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@perf_pmu@rc6-suspend.html * igt@sysfs_clients@fair-7: - shard-tglb: NOTRUN -> [SKIP][62] ([i915#2994]) [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@sysfs_clients@fair-7.html * igt@sysfs_clients@sema-10: - shard-kbl: NOTRUN -> [SKIP][63] ([fdo#109271] / [i915#2994]) +3 similar issues [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@sysfs_clients@sema-10.html #### Possible fixes #### * igt@core_hotunplug@unbind-rebind: - shard-kbl: [INCOMPLETE][64] ([i915#4130]) -> [PASS][65] [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl3/igt@core_hotunplug@unbind-rebind.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@core_hotunplug@unbind-rebind.html * igt@gem_eio@unwedge-stress: - shard-iclb: [TIMEOUT][66] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][67] [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb8/igt@gem_eio@unwedge-stress.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb6/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-none-share@rcs0: - shard-iclb: [FAIL][68] ([i915#2842]) -> [PASS][69] [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb1/igt@gem_exec_fair@basic-none-share@rcs0.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb5/igt@gem_exec_fair@basic-none-share@rcs0.html * igt@gem_exec_fair@basic-pace@bcs0: - shard-tglb: [FAIL][70] ([i915#2842]) -> [PASS][71] [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-tglb3/igt@gem_exec_fair@basic-pace@bcs0.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@gem_exec_fair@basic-pace@bcs0.html * igt@gem_exec_fair@basic-pace@vcs1: - shard-kbl: [SKIP][72] ([fdo#109271]) -> [PASS][73] [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl6/igt@gem_exec_fair@basic-pace@vcs1.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl7/igt@gem_exec_fair@basic-pace@vcs1.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-iclb: [FAIL][74] ([i915#2849]) -> [PASS][75] [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb2/igt@gem_exec_fair@basic-throttle@rcs0.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb1/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@kms_color@pipe-b-ctm-green-to-red: - shard-skl: [DMESG-WARN][76] ([i915#1982]) -> [PASS][77] [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl3/igt@kms_color@pipe-b-ctm-green-to-red.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl5/igt@kms_color@pipe-b-ctm-green-to-red.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions: - shard-skl: [FAIL][78] ([i915#2346]) -> [PASS][79] [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl10/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1: - shard-skl: [FAIL][80] ([i915#79]) -> [PASS][81] [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl6/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl8/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1: - shard-skl: [INCOMPLETE][82] ([i915#146] / [i915#198]) -> [PASS][83] [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl1/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl9/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html * igt@kms_flip@flip-vs-suspend@c-dp1: - shard-kbl: [DMESG-WARN][84] ([i915#180]) -> [PASS][85] +9 similar issues [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@kms_flip@flip-vs-suspend@c-dp1.html [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl2/igt@kms_flip@flip-vs-suspend@c-dp1.html * igt@kms_frontbuffer_tracking@fbcpsr-suspend: - shard-tglb: [INCOMPLETE][86] ([i915#2411] / [i915#456]) -> [PASS][87] [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-tglb7/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c: - shard-skl: [INCOMPLETE][88] ([i915#198] / [i915#2828]) -> [PASS][89] [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl8/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [FAIL][90] ([fdo#108145] / [i915#265]) -> [PASS][91] +1 similar issue [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl1/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl9/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_psr@psr2_suspend: - shard-iclb: [SKIP][92] ([fdo#109441]) -> [PASS][93] +1 similar issue [92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb5/igt@kms_psr@psr2_suspend.html [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb2/igt@kms_psr@psr2_suspend.html #### Warnings #### * igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip: - shard-skl: [FAIL][94] ([i915#3722]) -> [FAIL][95] ([i915#3743]) [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl10/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl1/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html * igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip: - shard-skl: [FAIL][96] ([i915#3743]) -> [FAIL][97] ([i915#3722]) [96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl2/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl6/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html * igt@kms_psr2_sf@plane-move-sf-dmg-area-3: - shard-iclb: [SKIP][98] ([i915#658]) -> [SKIP][99] ([i915#2920]) [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-iclb3/igt@kms_psr2_sf@plane-move-sf-dmg-area-3.html [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-iclb2/igt@kms_psr2_sf@plane-move-sf-dmg-area-3.html * igt@runner@aborted: - shard-kbl: ([FAIL][100], [FAIL][101], [FAIL][102], [FAIL][103], [FAIL][104], [FAIL][105], [FAIL][106], [FAIL][107], [FAIL][108], [FAIL][109], [FAIL][110]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363] / [i915#602]) -> ([FAIL][111], [FAIL][112], [FAIL][113], [FAIL][114], [FAIL][115], [FAIL][116], [FAIL][117], [FAIL][118], [FAIL][119], [FAIL][120]) ([i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363]) [100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl3/igt@runner@aborted.html [101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl6/igt@runner@aborted.html [102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl6/igt@runner@aborted.html [103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl6/igt@runner@aborted.html [104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl3/igt@runner@aborted.html [105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl3/igt@runner@aborted.html [106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@runner@aborted.html [107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@runner@aborted.html [108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@runner@aborted.html [109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@runner@aborted.html [110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-kbl7/igt@runner@aborted.html [111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@runner@aborted.html [112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl4/igt@runner@aborted.html [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl4/igt@runner@aborted.html [114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@runner@aborted.html [115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl7/igt@runner@aborted.html [116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl6/igt@runner@aborted.html [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl3/igt@runner@aborted.html [118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl1/igt@runner@aborted.html [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl1/igt@runner@aborted.html [120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-kbl7/igt@runner@aborted.html - shard-skl: ([FAIL][121], [FAIL][122]) ([i915#1814] / [i915#3002] / [i915#3363]) -> ([FAIL][123], [FAIL][124], [FAIL][125]) ([i915#1814] / [i915#2029] / [i915#3002] / [i915#3363]) [121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl2/igt@runner@aborted.html [122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10605/shard-skl4/igt@runner@aborted.html [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl6/igt@runner@aborted.html [124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl4/igt@runner@aborted.html [125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/shard-skl3/igt@runner@aborted.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [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#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506 [fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614 [fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615 [fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825 [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827 [i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319 [i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436 [i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146 [i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814 [i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198 [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982 [i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029 [i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122 [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190 [i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346 [i915#2369]: https://gitlab.freedesktop.org/drm/intel/issues/2369 [i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411 [i915#2481]: https://gitlab.freedesktop.org/drm/intel/issues/2481 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658 [i915#2828]: https://gitlab.freedesktop.org/drm/intel/issues/2828 [i915#284]: https://gitlab.freedesktop.org/drm/intel/issues/284 [i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842 [i915#2849]: https://gitlab.freedesktop.org/drm/intel/issues/2849 [i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856 [i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920 [i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994 [i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002 [i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063 [i915#3070]: https://gitlab.freedesktop.org/drm/intel/issues/3070 [i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116 [i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359 [i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363 [i915#3536]: https://gitlab.freedesktop.org/drm/intel/issues/3536 [i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689 [i915#3722]: https://gitlab.freedesktop.org/drm/intel/issues/3722 [i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743 [i915#3777]: https://gitlab.freedesktop.org/drm/intel/issues/3777 [i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886 [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4130]: https://gitlab.freedesktop.org/drm/intel/issues/4130 [i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456 [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533 [i915#602]: https://gitlab.freedesktop.org/drm/intel/issues/602 [i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658 [i915#750]: https://gitlab.freedesktop.org/drm/intel/issues/750 [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 Participating hosts (11 -> 9) ------------------------------ Missing (2): pig-kbl-iris shard-rkl Build changes ------------- * Linux: CI_DRM_10605 -> Patchwork_21089 CI-20190529: 20190529 CI_DRM_10605: e61e36045f57a5aaeef91f54274937843ee3d0d5 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6211: 7b275b3eb17ddf6e7c5b7b9ba359b7f5345a5311 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_21089: 0a23b1f1e8f81bcf74008982e1f8807985ff94c3 @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21089/index.html [-- Attachment #2: Type: text/html, Size: 36407 bytes --] ^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2021-09-18 0:32 UTC | newest] Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-09-16 4:37 5.15-rc1 i915 blank screen booting on ThinkPads Hugh Dickins 2021-09-16 4:37 ` [Intel-gfx] " Hugh Dickins 2021-09-16 8:44 ` Tvrtko Ursulin 2021-09-16 8:44 ` [Intel-gfx] " Tvrtko Ursulin 2021-09-16 10:17 ` Jani Nikula 2021-09-16 10:17 ` [Intel-gfx] " Jani Nikula 2021-09-17 21:26 ` Hugh Dickins 2021-09-17 21:26 ` [Intel-gfx] " Hugh Dickins 2021-09-17 21:30 ` Matthew Brost 2021-09-17 21:30 ` [Intel-gfx] " Matthew Brost 2021-09-17 22:52 ` Jani Nikula 2021-09-17 22:52 ` [Intel-gfx] " Jani Nikula 2021-09-17 23:29 ` Matthew Brost 2021-09-17 23:29 ` [Intel-gfx] " Matthew Brost 2021-09-18 0:22 ` Hugh Dickins 2021-09-18 0:22 ` [Intel-gfx] " Hugh Dickins 2021-09-17 22:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2021-09-17 22:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-09-18 0:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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.