drm-next-misc merge breaks vmwgfx

Thomas Hellstrom thellstrom at vmware.com
Thu Apr 6 14:10:51 UTC 2017

On 04/06/2017 02:34 PM, Daniel Vetter wrote:
> Hi Thomas,
> Bisected an offender already? Afaik there's no one else who reported
> issues thus far, and for our own CI it seems all still fine.
> -Daniel

Hi, Daniel,

Yes, I rebased drm-misc-next on top of vmwgfx-next and found the culprit
to be

38b6441e "drm/atomic-helper: Remove the backoff hack from set_config.."

Reverting first 1fa4da04 and then

fixes the problem.

Also, when testing the tip of drm-misc-next (with the non-atomic vmwgfx)
there appeared to be warnings about a non-NULL
dev->mode_config.acquire_ctx. I'll see if I can reproduce those, but
perhaps removing the line

dev->mode_config.acquire_ctx = &ctx

in drm_mode_setcrtc()

is part of the problem.


> On Wed, Apr 5, 2017 at 7:45 PM, Thomas Hellstrom <thellstrom at vmware.com> wrote:
>> Hi!
>> It appears like the drm-next commit 320d8c3d3 "Merge tag
>> 'drm-misc-next-2017-03-31..." breaks vmwgfx.
>> A black screen shown where plymouthd use to show the boot splash on
>> Fedora 25. Nothing relevant in the logs.
>> I eyed through the vmwgfx conflict fixes, but nothing immediately stands
>> out as incorrect.
>> I'll dig into this tomorrow. Does anybody know of any other drivers that
>> don't work well with current drm-next?
>> /Thomas

More information about the dri-devel mailing list