Hi,
> Andreas Färber hat am 2. Oktober 2018 um 16:33 geschrieben:
>
>
> Hi Stefan and Daniel,
>
> Am 02.10.18 um 11:48 schrieb Stefan Wahren:
> > Hi Daniel,
> SNIP
> > personally i didn't know this option before this issue, but i cannot
> > speak for all the distributions. I checked Raspbian a
Hi Stefan,
> [add Peter and Andreas]
>
>
> Am 02.10.2018 um 10:44 schrieb Daniel Vetter:
> > On Mon, Oct 01, 2018 at 06:21:23PM +0200, Stefan Wahren wrote:
> >> Hi,
> >>
> >>> Sergey Suloev hat am 1. Oktober 2018 um 12:17
> >>> geschrieben:
> >>>
> >>>
> >>> Hi, Stefan,
> >>>
> >>>
> >>> On 09/3
Hi Stefan and Daniel,
Am 02.10.18 um 11:48 schrieb Stefan Wahren:
> Hi Daniel,
>
> [add Peter and Andreas]
>
> Am 02.10.2018 um 10:44 schrieb Daniel Vetter:
>> On Mon, Oct 01, 2018 at 06:21:23PM +0200, Stefan Wahren wrote:
Sergey Suloev hat am 1. Oktober 2018 um 12:17
geschrieben:
>>
Hi Daniel,
[add Peter and Andreas]
Am 02.10.2018 um 10:44 schrieb Daniel Vetter:
> On Mon, Oct 01, 2018 at 06:21:23PM +0200, Stefan Wahren wrote:
>> Hi,
>>
>>> Sergey Suloev hat am 1. Oktober 2018 um 12:17
>>> geschrieben:
>>>
>>>
>>> Hi, Stefan,
>>>
>>>
>>> On 09/30/2018 10:38 PM, Stefan Wahr
On Mon, Oct 01, 2018 at 06:21:23PM +0200, Stefan Wahren wrote:
> Hi,
>
> > Sergey Suloev 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 hat am 30. September 2018 um
Hi, Stefan,
On 09/30/2018 10:38 PM, Stefan Wahren wrote:
Hi Sergey,
Sergey Suloev 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
Hi,
> Sergey Suloev 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 hat am 30. September 2018 um 15:24
> >> geschrieben:
> >>
> >>
> >> Here is my log
> >>
> >> [ 2.868157] [drm:drm
Hi,Noralf,
I was hoping Eric would look at it and so I didn't include your email to
CC. From now on as you can be a backup person I will always include you.
Thanks for the fix. Can you also explain which config option(s) causes
this problem ? Because the default config for arm64 works well.
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
I have no idea where 2880 is coming from, my monitor has resolution 1280
* 1024.
Is this a DRM bug ?
On 09/30/2018 03:29 PM, Noralf Trønnes wrote:
Den 29.09.2018 22.52, skrev Sergey Suloev:
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALL
Hi, Noralf,
I have tested you patch with 4.19-rc5.
The issue has changed from oops into the following error message in boot
log:
[ 3.501261] vc4-drm soc:gpu: [drm:drm_fb_helper_fbdev_setup
[drm_kms_helper]] *ERROR* Failed to set fbdev configuration
The console output stops at this mome
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALLOC=200
Changing it to the default value fixes the issue:
CONFIG_DRM_FBDEV_OVERALLOC=100
Sergey
On 09/29/2018 08:14 PM, Noralf Trønnes wrote:
Den 28.09.2018 23.01, skrev Stefan Wahren:
Hi,
Hi Sergey,
> Sergey Suloev 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:dr
Den 30.09.2018 15.24, skrev Sergey Suloev:
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?
Den 29.09.2018 22.52, skrev Sergey Suloev:
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALLOC=200
Changing it to the default value fixes the issue:
CONFIG_DRM_FBDEV_OVERALLOC=100
If you enable drm debug (drm.debug=0xff), you get some more
Den 28.09.2018 23.01, skrev Stefan Wahren:
Hi,
Sergey Suloev already reported this NULL pointer dereference [1]. Now he was
able to provide a Kernel config and i'm able to reproduce it with a Raspberry
Pi 3 (arm64) and Linux 4.19-rc5. It seems like a invalid config [2] for vc4,
but neverthel
16 matches
Mail list logo