From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: maciej.rutecki@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PROBLEM] i915/drm: Insufficient FIFO for plane
Date: Sun, 29 Aug 2010 14:27:53 +0100 [thread overview]
Message-ID: <20100829132753.GA19049@sucs.org> (raw)
In-Reply-To: <AANLkTikMK7WJAfBHUXi_VMyJQBQT69ZfA7LwKfp5c-r8@mail.gmail.com>
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/
next prev parent reply other threads:[~2010-08-29 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 15:26 [PROBLEM] i915/drm: Insufficient FIFO for plane Pekka Enberg
2010-08-26 18:27 ` Maciej Rutecki
2010-08-29 11:32 ` Pekka Enberg
2010-08-29 13:27 ` Sitsofe Wheeler [this message]
2010-08-22 15:26 Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100829132753.GA19049@sucs.org \
--to=sitsofe@yahoo.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=penberg@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.