On 26 March 2015 at 13:04, Linus Torvalds <[email protected]> wrote: > On Wed, Mar 25, 2015 at 3:43 PM, Linus Torvalds > <[email protected]> wrote: >> >> I'm going to wait a bit more with this, since clearly things are still >> in flux, and these two commits don't actually fix everything at all. >> >> There's apparently at least one more fix necessary. > > Indeed. I can see the problem myself. > > With current git I get two warnings: > > WARNING: CPU: 3 PID: 325 at include/linux/kref.h:47 > drm_framebuffer_reference+0x72/0x80 [drm]() > WARNING: CPU: 4 PID: 107 at drivers/gpu/drm/drm_atomic.c:482 > drm_atomic_check_only+0x32d/0x4f0 [drm]() > > and testing the pull it gets rid of the first one, but no tthe second one. > > So that urgent fix is very much still lacking.
I've pushed a drm-fixes-staging branch that backport's Daniel's drm-next fix from 9 hours ago, However it isn't tested yet, so if you want to give it a whirl grab it. Hopefully when Daniel comes on line he can provide assurance that my fix is a correct backport. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
