[Intel-gfx] KMS start locks up RocketLake-S GT1

Is there a command line option needed for RocketLake-S GT1 on i5-11400? Is it supposed to use some module other than i915? Tumbleweed kernel 5.15.6 locks up, apparently when KMS should be kicking in. I can't get any logs or dmesg except when booting with nomodeset. -- Evolution as taught in

[Intel-gfx] ✓ Fi.CI.IGT: success for Fix stealing guc_ids + test (rev2)

== Series Details == Series: Fix stealing guc_ids + test (rev2) URL : https://patchwork.freedesktop.org/series/97896/ State : success == Summary == CI Bug Log - changes from CI_DRM_10989_full -> Patchwork_21833_full Summary ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for More fixes/tweaks to GuC support

== Series Details == Series: More fixes/tweaks to GuC support URL : https://patchwork.freedesktop.org/series/97898/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10989_full -> Patchwork_21832_full Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for Fix stealing guc_ids + test

== Series Details == Series: Fix stealing guc_ids + test URL : https://patchwork.freedesktop.org/series/97896/ State : success == Summary == CI Bug Log - changes from CI_DRM_10989_full -> Patchwork_21831_full Summary --- **WARNING**

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Support bigger GuC RSA keys

== Series Details == Series: drm/i915: Support bigger GuC RSA keys URL : https://patchwork.freedesktop.org/series/97891/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21830_full Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Don't disable interrupts and pretend a lock as been acquired in __timeline_mark_lock(). (rev2)

== Series Details == Series: drm/i915: Don't disable interrupts and pretend a lock as been acquired in __timeline_mark_lock(). (rev2) URL : https://patchwork.freedesktop.org/series/97082/ State : success == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21828_full

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/privacy_screen_x86: Add entry for ChromeOS privacy-screen

== Series Details == Series: series starting with [1/2] drm/privacy_screen_x86: Add entry for ChromeOS privacy-screen URL : https://patchwork.freedesktop.org/series/97883/ State : success == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21827_full

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: fix large buffer population trucation

== Series Details == Series: drm/i915/ttm: fix large buffer population trucation URL : https://patchwork.freedesktop.org/series/97881/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21826_full

[Intel-gfx] ✓ Fi.CI.BAT: success for Fix stealing guc_ids + test (rev2)

== Series Details == Series: Fix stealing guc_ids + test (rev2) URL : https://patchwork.freedesktop.org/series/97896/ State : success == Summary == CI Bug Log - changes from CI_DRM_10989 -> Patchwork_21833 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix stealing guc_ids + test (rev2)

== Series Details == Series: Fix stealing guc_ids + test (rev2) URL : https://patchwork.freedesktop.org/series/97896/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix stealing guc_ids + test (rev2)

== Series Details == Series: Fix stealing guc_ids + test (rev2) URL : https://patchwork.freedesktop.org/series/97896/ State : warning == Summary == $ dim checkpatch origin/drm-tip 93cd046bb4d5 drm/i915/guc: Use correct context lock when callig clr_context_registered 8827a89b918a

[Intel-gfx] [PATCH 7/7] drm/i915/guc: Selftest for stealing of guc ids

Testing the stealing of guc ids is hard from user space as we have 64k guc_ids. Add a selftest, which artificially reduces the number of guc ids, and forces a steal. Description of test below. The test creates a spinner which is used to block all subsequent submissions until it completes. Next, a

[Intel-gfx] [PATCH 6/7] drm/i915/guc: Kick G2H tasklet if no credits

Let's be paranoid and kick the G2H tasklet, which dequeues messages, if G2H credits are exhausted. Signed-off-by: Matthew Brost --- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c

[Intel-gfx] [PATCH 1/7] drm/i915/guc: Use correct context lock when callig clr_context_registered

s/ce/cn/ when grabbing guc_state.lock before calling clr_context_registered. Fixes: 0f7976506de61 ("drm/i915/guc: Rework and simplify locking") Signed-off-by: Matthew Brost Reviewed-by: Daniele Ceraolo Spurio --- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++-- 1 file changed, 2

[Intel-gfx] [PATCH 4/7] drm/i915/guc: Don't hog IRQs when destroying contexts

From: John Harrison While attempting to debug a CT deadlock issue in various CI failures (most easily reproduced with gem_ctx_create/basic-files), I was seeing CPU deadlock errors being reported. This were because the context destroy loop was blocking waiting on H2G space from inside an IRQ

[Intel-gfx] [PATCH 5/7] drm/i915/guc: Add extra debug on CT deadlock

Print CT state (H2G + G2H head / tail pointers, credits) on CT deadlock. v2: (John Harrison) - Add units to debug messages Reviewed-by: John Harrison Signed-off-by: Matthew Brost --- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 9 + 1 file changed, 9 insertions(+) diff --git

[Intel-gfx] [PATCH 2/7] drm/i915/guc: Only assign guc_id.id when stealing guc_id

Previously assigned whole guc_id structure (list, spin lock) which is incorrect, only assign the guc_id.id. Fixes: 0f7976506de61 ("drm/i915/guc: Rework and simplify locking") Signed-off-by: Matthew Brost Reviewed-by: John Harrison --- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +- 1

[Intel-gfx] [PATCH 3/7] drm/i915/guc: Remove racey GEM_BUG_ON

A full GT reset can race with the last context put resulting in the context ref count being zero but the destroyed bit not yet being set. Remove GEM_BUG_ON in scrub_guc_desc_for_outstanding_g2h that asserts the destroyed bit must be set in ref count is zero. Reviewed-by: Daniele Ceraolo Spurio

[Intel-gfx] [PATCH 0/7] Fix stealing guc_ids + test

Patches 1 & 2 address bugs in stealing of guc_ids and patch 7 tests this path. Patches 4-6 address some issues with the CTs exposed by the selftest in patch 7. Basically if a lot of contexts were all deregistered all at once, the CT channel could deadlock. Patch 3 is a small fix that is already

[Intel-gfx] [drm-intel:topic/core-for-CI 16/25] arch/powerpc/platforms/embedded6xx/Kconfig:2:error: recursive dependency detected!

tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI head: 4c82fd0506b4cc196a375d1200361fb0c5439acd commit: b3acf17eafd473e6e8f8f7c5ec7040efaaff22b8 [16/25] Revert "drm/i915: Don't select BROKEN" config: powerpc64-randconfig-r015-20211210 compiler: clang version 14.0.0

[Intel-gfx] ✓ Fi.CI.IGT: success for drm: i915: display: intel_dmc: Fixes an unsigned subtraction which can never be negative.

== Series Details == Series: drm: i915: display: intel_dmc: Fixes an unsigned subtraction which can never be negative. URL : https://patchwork.freedesktop.org/series/97869/ State : success == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21825_full

[Intel-gfx] [drm-intel:topic/core-for-CI 16/25] arch/powerpc/platforms/embedded6xx/Kconfig:2:error: recursive dependency detected!

tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI head: 4c82fd0506b4cc196a375d1200361fb0c5439acd commit: b3acf17eafd473e6e8f8f7c5ec7040efaaff22b8 [16/25] Revert "drm/i915: Don't select BROKEN" config: powerpc-randconfig-r035-20211210 compiler: powerpc-linux-gcc (GCC) 11.2.0

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: include reductions (rev2)

== Series Details == Series: drm/i915: include reductions (rev2) URL : https://patchwork.freedesktop.org/series/97789/ State : success == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21823_full Summary ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Move pipe/transcoder/abox masks under intel_device_info.display

== Series Details == Series: drm/i915: Move pipe/transcoder/abox masks under intel_device_info.display URL : https://patchwork.freedesktop.org/series/97864/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21822_full

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Stop doing writeback from the shrinker

== Series Details == Series: drm/i915: Stop doing writeback from the shrinker URL : https://patchwork.freedesktop.org/series/97856/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21821_full Summary

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Don't leak the capture list items (rev2)

== Series Details == Series: drm/i915: Don't leak the capture list items (rev2) URL : https://patchwork.freedesktop.org/series/97804/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21820_full Summary

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/adl-n: Enable ADL-N platform (rev3)

== Series Details == Series: drm/i915/adl-n: Enable ADL-N platform (rev3) URL : https://patchwork.freedesktop.org/series/97406/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10988_full -> Patchwork_21818_full Summary