vc4: NULL pointer dereference in drm_client_dev_hotplug
Stefan Wahren
stefan.wahren at i2se.com
Mon Oct 1 16:21:23 UTC 2018
Hi,
> Sergey Suloev <ssuloev at orpaltech.com> hat am 1. Oktober 2018 um 12:17 geschrieben:
>
>
> Hi, Stefan,
>
>
> On 09/30/2018 10:38 PM, Stefan Wahren wrote:
> > Hi Sergey,
> >
> >> Sergey Suloev <ssuloev at orpaltech.com> hat am 30. September 2018 um 15:24 geschrieben:
> >>
> >>
> >> Here is my log
> >>
> >> [ 2.868157] [drm:drm_setup_crtcs [drm_kms_helper]] connector 29
> >> enabled? yes
> >> [ 2.868199] [drm:drm_setup_crtcs [drm_kms_helper]] connector 44
> >> enabled? no
> >> [ 2.868234] [drm:drm_setup_crtcs [drm_kms_helper]] connector 50
> >> enabled? yes
> >> [ 2.868271] [drm:drm_setup_crtcs [drm_kms_helper]] looking for
> >> cmdline mode on connector 29
> >> [ 2.868308] [drm:drm_setup_crtcs [drm_kms_helper]] looking for
> >> preferred mode on connector 29 0
> >> [ 2.868343] [drm:drm_setup_crtcs [drm_kms_helper]] found mode 1280x1024
> >> [ 2.868381] [drm:drm_setup_crtcs [drm_kms_helper]] looking for
> >> cmdline mode on connector 50
> >> [ 2.868417] [drm:drm_setup_crtcs [drm_kms_helper]] looking for
> >> preferred mode on connector 50 0
> >> [ 2.868465] [drm:drm_setup_crtcs [drm_kms_helper]] found mode 1920x1440
> >> [ 2.868500] [drm:drm_setup_crtcs [drm_kms_helper]] picking CRTCs for
> >> 2048x2048 config
> >> [ 2.868561] [drm:drm_setup_crtcs [drm_kms_helper]] desired mode
> >> 1280x1024 set on crtc 95 (0,0)
> >> [ 2.868673] [drm:drm_mode_object_get [drm]] OBJ ID: 29 (2)
> >> [ 2.868709] [drm:drm_setup_crtcs [drm_kms_helper]] desired mode
> >> 1920x1440 set on crtc 74 (0,0)
> >> [ 2.868790] [drm:drm_mode_object_get [drm]] OBJ ID: 50 (2)
> >> [ 2.868832] [drm:drm_fb_helper_generic_probe [drm_kms_helper]]
> >> surface width(1920), height(2880) and bpp(32)
> >> [ 3.001470] [drm:drm_internal_framebuffer_create [drm]] bad
> >> framebuffer height 2880, should be >= 0 && <= 2048
> >> [ 3.001650] vc4-drm soc:gpu: [drm:drm_fb_helper_fbdev_setup
> >> [drm_kms_helper]] *ERROR* Failed to set fbdev configuration
> >>
> > does this config work with 4.18?
>
> I have checked with the tag v4.18 as per your request and I can confirm
> that the issue does not exists in 4.18.
i tried to follow the threads mentioned by Noralf, but it seems the regression regarding CONFIG_DRM_FBDEV_OVERALLOC=200 hasn't been fixed yet.
It would be nice to have this fixed in 4.19 LTS.
Regards
Stefan
>
> Sergey
More information about the dri-devel
mailing list