On Wed, Aug 21, 2013 at 11:20 PM, Daniel Vetter <daniel@xxxxxxxx> wrote: > On Wed, Aug 21, 2013 at 08:11:27PM +0200, Sedat Dilek wrote: >> On Wed, Aug 21, 2013 at 3:44 PM, Daniel Vetter <daniel@xxxxxxxx> wrote: >> > On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote: >> >> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> >> > Hi all, >> >> > >> >> > There will be no linux-next trees on Aug 23 or 26. >> >> > >> >> > Changes since 20130820: >> >> > >> >> > New tree: aio-direct >> >> > >> >> > Removed tree: xilinx (at maintainer's request) >> >> > >> >> > The xfs tree still had its build failure for which I reverted a commit. >> >> > >> >> > The trivial tree gained conflicts against the crypto, net-next and >> >> > wireless trees. >> >> > >> >> > The aio tree gained conflicts against the aio-direct tree. >> >> > >> >> > The akpm-current tree gained conflicts against the modules and aio-direct >> >> > trees. >> >> > >> >> > ---------------------------------------------------------------------------- >> >> > >> >> >> >> Hi, >> >> >> >> I still have this issue with next-20130821 and "Linux v3.11-rc6 plus >> >> drm-intel-nightly on top" >> >> Any new development on this? >> >> Patches? >> > >> > Tbh I'm at a loss what we could try above&beyond what Chris has already >> > tried out. >> > >> >> Currently, I have two workarounds: >> >> >> >> [1] Revert this commit: >> >> >> >> commit 5456fe3882812aba251886e36fe55bfefb8e8829 >> >> "drm/i915: Allocate LLC ringbuffers from stolen" >> > >> > Since with a rather decent chance the next testing cycle I'll do this >> > friday will be the last chunk of features for 3.12 I'll probably drop the >> > above patch from my queue and we can try again in 3.13. >> > >> >> Inspired by [1] I have switched from UXA to SNA... >> ...and applied "[PATCH] drm/i915: Cleaning up the relocate entry >> function" on top of next-20130821... >> ...and can NOT see the screen corruptions anymore. >> >> Can you explain that? > > If the relocate cleanup patch [1] is indeed required, then I can't explain > this at all. Can you please double-check that this is really it, and that > it's not the uxa->sna switch? > It's independent of the applied patch. My problem goes away with SNA but still exists with UXA. As said in my previous analysis... switching back to Ubuntu's graphics did not show the symptoms, too. It's interesting to see, it is a problem of the intel-ddx. Anyway, SNA seems here to be approx. 20% faster in gtkperf-0.40, so I will use it. I am open and willing to test any patches you will provide. Please, let me know. Thanks. - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
