Subject : [REGRESSION] [2.6.36-rc1] [DRM INTEL] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for plane, expect flickering: entries required = 36, available = 28.
Submitter : Maciej Rutecki <firstname.lastname@example.org>
Date : 2010-08-18 18:46
Message-ID : email@example.com
References : http://marc.info/?l=linux-kernel&m=128215721507666&w=2
This entry is being used for tracking a regression from 2.6.35. Please don't
close it until the problem is fixed in the mainline.
Still present on 2.6.36-rc3
On Wed, 18 Aug 2010 20:13:12 +0100
Chris Wilson <firstname.lastname@example.org> wrote:
> On Wed, 18 Aug 2010 20:46:37 +0200, Maciej Rutecki <email@example.com>
> > Last known good: 2.6.35
> > Failing kernel: 2.6.36-rc1
> > During boot kernel display this message:
> > [ 0.831906] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
> > expect flickering: entries required = 36, available = 28.
> To be honest, I was shocked at how often we were actually computing that
> we required a larger FIFO for scanout than was available. Typically, it is
> the result of the pessimistic latency we guess for the memory fetch and so
> we err on the side of extreme caution when computing the watermark. So in
> effect, we have been clamping the FIFO since the beginning, but we only
> just added the warning message as an aide to diagnosing some FIFO
> underruns. We could tone down the error message, the real goal though is
> to improve the accuracy of the calculation and thereby reduce power.
> > Systems seems work OK, but in 2.6.35 I don't have this message. On another
> > system with 2.6.36-rc1 kernel I have the same message.
> Yes, there was just a couple of places where we changed the calculation to
> round-up but otherwise the wm logic remained mostly the same. So if you
> haven't been experiencing FIFO underruns, e.g. the screen flickering, then
> it is likely that the error is benign (and just wasting power).
So, is this something that should be ignored? Should this message be silenced for an officially released kernel? Is it actively useful to have in the dmesg?
Perhaps some stats in debugfs/sysfs/procfs that you could hook powertop up to would be better?
Right, the flicker is annoying and obvious when it happens. So just exporting the watermarks in debugfs would be a simple sanity check for bug reporters.
Author: Chris Wilson <firstname.lastname@example.org>
Date: Wed Sep 8 09:14:08 2010 +0100
Revert "drm/i915: Warn if we run out of FIFO space for a mode"
This reverts commit b9421ae8f30958deea98d71477b4a77a066856b4.
This warning was so prelevant, even for apparently working machines,
that it was just causing fear, anxiety and panic.
The root cause still remains, so we will add some better debugging when
we focus on fixing it.
Reported-by: Maciej Rutecki <email@example.com>
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
Fixed by commit c3add4b63438555d5e88c5893d238ab80d1f5959 .