Message-Id: <8u3s94$gak45q@orsmga002.jf.intel.com>
Date: Tue, 24 Aug 2010 00:55:54 +0100
To: Jonathan Corbet <corbet@lwn.net>
Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display
Cc: LKML <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org,
        Eric Anholt <eric@anholt.net>
References: <20100823110145.08eb72fd@bike.lwn.net> <20100823151708.6b242599@bike.lwn.net> <8u3s8d$jcc0rr@orsmga001.jf.intel.com> <20100823173225.2bda6f78@bike.lwn.net> <8u3s94$gak083@orsmga002.jf.intel.com> <20100823174641.4ba58bfe@bike.lwn.net>
From: Chris Wilson <chris@chris-wilson.co.uk>
In-Reply-To: <20100823174641.4ba58bfe@bike.lwn.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1163
Lines: 27

On Mon, 23 Aug 2010 17:46:41 -0600, Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 24 Aug 2010 00:37:52 +0100
> Chris Wilson <chris@chris-wilson.co.uk> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/