Yes, so the driver is calling the vsync hook after mir has instructed th driver to send no more vsync signals. Seems like a driver bug, looking at finding a way to work around.
Yes, so the driver is calling the vsync hook after mir has instructed th driver to send no more vsync signals. Seems like a driver bug, looking at finding a way to work around.