On Wed, 8 Jan 2014, Daniel Vetter wrote: > On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote: > > On Wed, 8 Jan 2014, Daniel Vetter wrote: > > > > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote: > > > > On Tue, 7 Jan 2014, Daniel Vetter wrote: > > > > > > > > > I really want users to report these issues, and excessive WARNs seems > > > > > to be the only way to get those reports. Please boot with > > > > > drm.debug=0xe added to your kernel cmdline and reproduce this issues. > > > > > Also, which precise kernel are you running? Testing latest -rc is > > > > > always recommended, this state checker code is fairly new and gets > > > > > constantly extended and bugs fixed ... > > > > > > > > Here you go. This is the dmesg output after booting with > > > > drm.debug=0xe. Pay no attention to the "AS" suffix in the version > > > > string; this is pristine 3.13-rc7. > > > > > > That's strange, I've thought we've fixed the last struggling mismatch in > > > the lvds borber bits stuff. Can you please try latest drm-intel-nightly > > > from > > > > > > http://cgit.freedesktop.org/~danvet/drm-intel/ I posted the output from the default branch in that repository last week: http://marc.info/?l=linux-kernel&m=138922294308576&w=2 Have you had time to look at the results yet? Alan Stern _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
