| Bug ID | 104756 |
|---|---|
| Summary | [bisected] [kabini] [regression] [drm:amdgpufb_create] *ERROR= * failed to create fbcon object -12 |
| Product | DRI |
| Version | DRI git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | mike@fireburn.co.uk |
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.sta= ch@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=C3=BCtzel <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
| What | Removed | Added |
|---|---|---|
| CC | mike@fireburn.co.uk |
Created attachment 136923 =
[details]
Dmesg with revert
| What | Removed | Added |
|---|---|---|
| Attachment #136922 mime type | application/x-dc-rom | text/plain |
Please attach the CONFIG_DRM entries of the kernel build confi= guration file.
Hi The CONFIG_DRM entries are as follows: CONFIG_DRM=3Dy CONFIG_DRM_MIPI_DSI=3Dy CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=3Dy CONFIG_DRM_KMS_HELPER=3Dy CONFIG_DRM_KMS_FB_HELPER=3Dy CONFIG_DRM_FBDEV_EMULATION=3Dy CONFIG_DRM_FBDEV_OVERALLOC=3D100 CONFIG_DRM_TTM=3Dy CONFIG_DRM_SCHED=3Dy CONFIG_DRM_AMDGPU=3Dy CONFIG_DRM_AMDGPU_USERPTR=3Dy CONFIG_DRM_AMD_DC=3Dy CONFIG_DRM_AMD_DC_PRE_VEGA=3Dy CONFIG_DRM_AMD_DC_FBC=3Dy CONFIG_DRM_I915=3Dy CONFIG_DRM_I915_ALPHA_SUPPORT=3Dy CONFIG_DRM_I915_CAPTURE_ERROR=3Dy CONFIG_DRM_I915_COMPRESS_ERROR=3Dy CONFIG_DRM_I915_USERPTR=3Dy CONFIG_DRM_PANEL=3Dy CONFIG_DRM_BRIDGE=3Dy CONFIG_DRM_PANEL_BRIDGE=3Dy
Sorry pasted from wrong machine: CONFIG_DRM=3Dy CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=3Dy CONFIG_DRM_KMS_HELPER=3Dy CONFIG_DRM_KMS_FB_HELPER=3Dy CONFIG_DRM_FBDEV_EMULATION=3Dy CONFIG_DRM_FBDEV_OVERALLOC=3D100 CONFIG_DRM_TTM=3Dy CONFIG_DRM_SCHED=3Dy CONFIG_DRM_AMDGPU=3Dy CONFIG_DRM_AMDGPU_CIK=3Dy CONFIG_DRM_AMDGPU_USERPTR=3Dy CONFIG_DRM_AMD_DC=3Dy CONFIG_DRM_AMD_DC_PRE_VEGA=3Dy CONFIG_DRM_AMD_DC_FBC=3Dy CONFIG_DRM_AMD_DC_DCN1_0=3Dy CONFIG_DRM_PANEL=3Dy CONFIG_DRM_BRIDGE=3Dy CONFIG_DRM_PANEL_BRIDGE=3Dy
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 kerne= l. Lucas, what do you think?
| What | Removed | Added |
|---|---|---|
| Resolution | --- | DUPLICATE |
| Status | NEW | RESOLVED |
Yeah, the init order isn't correct. Give me a second for a pat= ch. *** This bug has been marked as a duplicate of bug 104736 ***
| What | Removed | Added |
|---|---|---|
| Status | RESOLVED | CLOSED |