> > The root > > cause is loading two different framebuffers with one taking over from > > another - that should be an obscure corner case and once the fuzz testing > > can avoid. > > > > I had a semi-informed poke at this and came up with a possible patch (not very tested) > > If this fixes the real problems we've been seeing, I'll dance a jig. Youtube... At this point my bigger concern is that it'll just make something else warn instead. The underlying problem is that fbcon layer implements a single threaded notifier whose locking semantics are at best random. It's not calld with a specific set of locks each time. Possibly it sohuld be two notifiers (one for fb stuff, one for console layer stuff) but the entire layer is horrible. I live in home the KMS guys will rip out the useful bits and build a straight kms fb layer with refcounting and the like 8) Testing certainly needed and if it's still blowing up then hopefully further traces will help fix up the other cases we don't know about. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
