Andy Furniss wrote:
I didn't have time to bisect this yet, but maybe you have an idea what might cause this right away. I'm also not sure if it's a bug in the DRI portion of the kernel. Is there anything besides a bisect you would need to debug this?
I am just a user - but after some testing maybe it would be better if you can reproduce on similar kernel to your old one and bisect that. On drm-next-3.19-wip I only have to go back 4 commits to hit ones I've been running for weeks (and I am still failing if I reset to there) so for me at least bisecting this tree isn't really an option - I wouldn't be testing like for like.
I also see an issue with current drm-next-3.19-wip branch with pitcairn and demos line Unigine Valley and Unreal Elemental. I was running last weeks drm-next-3.19-wip OK with these, so I guess the issue is near head, though the way other things get merged in etc makes it a bit hard to see what's new just looking at cgit.
Stable for me is drm-next-3.19-wip at 3.18.0-rc2-gc76c717 failing current = 3.18.0-rc4-gbe762d1 so it seems to be something in the merge that took rc-2 to rc-4. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
