linux-kernel - Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Aug 2010 00:55:54 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Jonathan Corbet <corbet@....net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org, Eric Anholt <eric@...olt.net>
Subject: Re: [now bisected] i915: 2.6.36-rc2 hoses my Intel display

On Mon, 23 Aug 2010 17:46:41 -0600, Jonathan Corbet <corbet@....net> wrote:
> On Tue, 24 Aug 2010 00:37:52 +0100
> Chris Wilson <chris@...is-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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/