On Wed, May 20, 2015 at 06:39:26PM +0200, Daniel Vetter wrote: > On Wed, May 20, 2015 at 6:00 PM, Nicolas Kalkhof <nkalk...@web.de> wrote: > > Hi Daniel, > > > > ok here is the first oops showing up on the screen. Image is not too good > > though. http://imgur.com/O0kutIE > > > > Btw. did you take a look at the stacktrace I've posted below complaining > > about complaining about pipe state doesn't match? > > Two things: > - Can you please boot with drm.debug=0xff and enable full debug output > to the console with dmesg -n debug and try to recapture? I'd like to > know what exactly happened right before. There should be lots of debug > output right before the oops. > - Can you please decode a few symbols: > > gdb drivers/gpu/drm/drm_atomic_helper.c > (gdb) break *drm_atomic_helper_check_modeset+0x2c5
Use "list *drm_atomic_helper_check_modeset+0x2c5" -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
