Hi,
I'm seeing tons of these error messages with current Linus' git:
[ 95.941618] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
plane, expect flickering: entries required = 36, available = 31.
Contrary to the error message, I don't see any flickering. I've attached
my dmesg and config.
Pekka
On niedziela, 22 sierpnia 2010 o 17:26:19 Pekka Enberg wrote:
> Hi,
>
> I'm seeing tons of these error messages with current Linus' git:
>
> [ 95.941618] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
> plane, expect flickering: entries required = 36, available = 31.
>
> Contrary to the error message, I don't see any flickering. I've attached
> my dmesg and config.
>
> Pekka
See:
https://bugzilla.kernel.org/show_bug.cgi?id=17021
Regards
--
Maciej Rutecki
http://www.maciek.unixy.pl
On Thu, Aug 26, 2010 at 9:27 PM, Maciej Rutecki
<[email protected]> wrote:
> On niedziela, 22 sierpnia 2010 o 17:26:19 Pekka Enberg wrote:
>> Hi,
>>
>> I'm seeing tons of these error messages with current Linus' git:
>>
>> [ ? 95.941618] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
>> plane, expect flickering: entries required = 36, available = 31.
>>
>> Contrary to the error message, I don't see any flickering. I've attached
>> my dmesg and config.
>>
> See:
> https://bugzilla.kernel.org/show_bug.cgi?id=17021
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?
Pekka
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/