linux-kernel - Re: [PROBLEM] i915/drm: Insufficient FIFO for plane

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100829132753.GA19049@sucs.org>
Date:	Sun, 29 Aug 2010 14:27:53 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	maciej.rutecki@...il.com, dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PROBLEM] i915/drm: Insufficient FIFO for plane

On Sun, Aug 29, 2010 at 02:32:41PM +0300, Pekka Enberg wrote:
> 
> The "insufficient FIFO for plane" problem seems to have gone away with
> latest Linus' git. I suppose commit
> 9559fcdbff4f93d29af04478bbc48294519424f5 ("drm/i915: fix vblank wait
> test condition") fixed it although I don't see any mention of the
> error in the changelog?

I found that commit reduced the number of "insufficient FIFO for plane"
messages in certain circumstances too (when the system is stable I only
see one at boot). However when my system is in "unstable mode" (see
http://marc.info/?l=linux-kernel&m=128272404206696&w=2 ), I can still
generate that message using the modetest (at the console) or xrandr (in
X) tools or by doing VT switches. When this is the case, the message
generally arrives in batches of two.

-- 
Sitsofe | http://sucs.org/~sits/
--
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/