Created attachment 136922 [details] Dmesg with errors I've been seeing messages about being unable to allocate an fbcon object I've bisected it back to: 4983e48c8539282be15f660bdd2c4260467b1190 is the first bad commit commit 4983e48c8539282be15f660bdd2c4260467b1190 Author: Lucas Stach <l.stach@pengutronix.de> Date: Wed Dec 6 17:49:40 2017 +0100 drm/sched: move fence slab handling to module init/exit This is the only part of the scheduler which must not be called from different drivers. Move it to module init/exit so it is done a single time when loading the scheduler. Reviewed-by: Chunming Zhou <david1.zhou@amd.com> Tested-by: Dieter Nützel <Dieter@nuetzel-hh.de> Acked-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> I see the issue with both DC and the old display setting code
Created attachment 136923 [details] Dmesg with revert
Please attach the CONFIG_DRM entries of the kernel build configuration file.
Hi The CONFIG_DRM entries are as follows: CONFIG_DRM=y CONFIG_DRM_MIPI_DSI=y CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 CONFIG_DRM_TTM=y CONFIG_DRM_SCHED=y CONFIG_DRM_AMDGPU=y CONFIG_DRM_AMDGPU_USERPTR=y CONFIG_DRM_AMD_DC=y CONFIG_DRM_AMD_DC_PRE_VEGA=y CONFIG_DRM_AMD_DC_FBC=y CONFIG_DRM_I915=y CONFIG_DRM_I915_ALPHA_SUPPORT=y CONFIG_DRM_I915_CAPTURE_ERROR=y CONFIG_DRM_I915_COMPRESS_ERROR=y CONFIG_DRM_I915_USERPTR=y CONFIG_DRM_PANEL=y CONFIG_DRM_BRIDGE=y CONFIG_DRM_PANEL_BRIDGE=y
Sorry pasted from wrong machine: CONFIG_DRM=y CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100 CONFIG_DRM_TTM=y CONFIG_DRM_SCHED=y CONFIG_DRM_AMDGPU=y CONFIG_DRM_AMDGPU_CIK=y CONFIG_DRM_AMDGPU_USERPTR=y CONFIG_DRM_AMD_DC=y CONFIG_DRM_AMD_DC_PRE_VEGA=y CONFIG_DRM_AMD_DC_FBC=y CONFIG_DRM_AMD_DC_DCN1_0=y CONFIG_DRM_PANEL=y CONFIG_DRM_BRIDGE=y CONFIG_DRM_PANEL_BRIDGE=y
Maybe drm_sched_fence_slab_init isn't guaranteed to be called before amdgpu_init when both amdgpu and the GPU scheduler are built into the kernel. Lucas, what do you think?
Yeah, the init order isn't correct. Give me a second for a patch. *** This bug has been marked as a duplicate of bug 104736 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.