On Tue, Jun 21, 2016 at 09:16:55AM +0100, Chris Wilson wrote: > During lastclose, we call intel_fbdev_restore_mode() to switch back to > the fbcon configuration on return to VT. However, if we have not yet > finished the asynchronous fbdev initialisation, the current mode will be > invalid and trigger WARNs upon application. > > Serialise with the outstanding initialisation if the first application > exits quickly. Note that to hit this in practice requires using an > unregistered async_domain as otherwise modprobe will force a full > synchronisation prior to init() completing. > > v2: Reuse comment explaining the +1 by refactoring the wait on fbdev > sync in the previous patch. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > Cc: Daniel Vetter <daniel.vetter@xxxxxxxx> > Reviewed-by: Daniel Vetter <daniel.vetter@xxxxxxxx> Don't forget the tags again... Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93580 Reported-by: Gustav Fägerlind <gustav.fagerlind@xxxxxxxxx> Reported-by: "Li, Weinan Z" <weinan.z.li@xxxxxxxxx> Cc: stable@xxxxxxxxxxxxxxx -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
