BUG - unable to handle null pointer, bisected - drm/amd/display: add gpio lock/unlock

[Alex Deucher]

On Thu, Feb 7, 2019 at 10:33 AM Michel Dänzer <michel at daenzer.net> wrote:
>
> On 2019-02-06 10:48 a.m., Przemek Socha wrote:
> > Good morning,
> >
> > on my Lenovo G50-45 a6310 APU with R4 Mullins commit
> > e261568f94d6c37ebb94d3c4b3f8a3085375dd9d is causing kernel Oops (unable to
> > handle NULL pointer).
> > Cross-checked by reverting troublesome commit and machine without it is
> > working fine.
>
> Same for me with Tonga.
>

Weird.  I'm not seeing this on my Tonga.  What displays are you using?
 DVI here.

Alex

>
> Chiawen / Tony / other DC developers, any ideas? If it cannot be fixed
> quickly, let's revert this change for now.
>
>
> --
> Earthling Michel Dänzer               |               http://www.amd.com
> Libre software enthusiast             |             Mesa and X developer
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx