On Mon, 23 Aug 2010 17:46:41 -0600, Jonathan Corbet <corbet@xxxxxxx> wrote: > On Tue, 24 Aug 2010 00:37:52 +0100 > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > > > drm.debug=0x4 should print the right information for this bug. > > That doesn't seem to give me any output at all. > > One thing I noticed, though, is that I occasionally get something like: > > Aug 23 17:43:14 bike kernel: [ 142.920185] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for plane, expect flickering: entries required = 51, available = 28. > > They seem to come in threes, for whatever that's worth. In threes. Hmm, one for primary, cursor and self-refresh. drm.debug=0xe would be interesting to see what the pixel clock is. Can you grab one before the bad commit and one after? If there is a change that may help pin-point the mistake. Or indicate further problems... -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
