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? Currently, I have two workarounds: [1] Revert this commit: commit 5456fe3882812aba251886e36fe55bfefb8e8829 "drm/i915: Allocate LLC ringbuffers from stolen" [2] Stop and start lightdm session manually ...switch to a VT and do a stop/start lightdm. Any help appreciated. BTW, I switched my Linux/X graphics stack to Mesa v9.2-rc1 and Intel-DDX v2.21.14-55-ged40a7c (LibDRM is still v2.4.46). Thanks. Regards, - Sedat - P.S.: The suspend/resume problem which I saw parallelly on former -next releases is gone. -- 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
