https://bugs.freedesktop.org/show_bug.cgi?id=30325 --- Comment #3 from Marius Groeger <marius.groeger@xxxxxx> 2010-09-29 01:58:39 PDT --- (In reply to comment #1) > Can you bisect what commit broke it? I suspect it's something in the common > drm code. There's FAR to many commits involved as during this interval the 2.6.35->2.6.36-rc merged happened. So I'm stuck. With the current d-r-t it seems even worse, I even don't get an X display anymore. (Haven't checked the logs though, yet). For the second time (the last issue was a latency problem due to excessive drm locking.) I'm hitting a major drm regression and can't do anything about it. This is very disappointing. So, what can we do about it in the future? As there are no regression tests, the testing is done by the community. Would it be possible to increase the frequency of updates to d-r-t? Or stay closer to the current linus tree? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
