Bug 104756

Summary:

[bisected] [kabini] [regression] [drm:amdgpufb_create] *ERROR* failed to create fbcon object -12

Product:

DRI

Reporter:

Mike Lothian <mike>

Component:

DRM/AMDgpu

Assignee:

Default DRI bug account <dri-devel>

Status:

CLOSED DUPLICATE

QA Contact:

Severity:

normal

Priority:

medium

CC:

dev, mike, robink

Version:

DRI git

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Dmesg with errors	none
Dmesg with revert	none

Description Mike Lothian 2018-01-23 22:23:52 UTC

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

Comment 1 Mike Lothian 2018-01-23 22:24:25 UTC

Created attachment 136923 [details]
Dmesg with revert

Comment 2 Michel Dänzer 2018-01-24 08:41:51 UTC

Please attach the CONFIG_DRM entries of the kernel build configuration file.

Comment 3 Mike Lothian 2018-01-24 09:55:11 UTC

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

Comment 4 Mike Lothian 2018-01-24 10:03:18 UTC

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

Comment 5 Michel Dänzer 2018-01-24 10:04:48 UTC

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?

Comment 6 Christian König 2018-01-24 10:07:02 UTC

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.