On 04/06/2017 04:47 PM, Daniel Vetter wrote: > On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom <thellstrom@xxxxxxxxxx> wrote: >> 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. > Hm, where do you hit that? And by tip of drm-misc-next, do you mean > the very latest state, which includes atomic vmwgfx, or is this with > the non-atomic vmwgfx? Please paste the backtraces (and for which tree > they are). > -Daniel Actually this must have been from a confused rebase-bisect state somewhere. I can't reproduce this. /Thomas _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
