All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mario Kleiner <mario.kleiner.de@gmail.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Breakage for Ironlake due to some watermarks changes in	Linux 4.0+?
Date: Tue, 19 May 2015 10:38:41 +0300	[thread overview]
Message-ID: <87h9r9koe6.fsf@intel.com> (raw)
In-Reply-To: <555ABE4D.7050705@gmail.com>

On Tue, 19 May 2015, Mario Kleiner <mario.kleiner.de@gmail.com> wrote:
> On 05/15/2015 11:00 AM, Jani Nikula wrote:
>> On Fri, 15 May 2015, Mario Kleiner <mario.kleiner.de@gmail.com> wrote:
>>> Hi all,
>>>
>>> since Linux 4.0 i experience some massive display flicker problem on my
>>> Intel HD Ironlake mobile (2010 MacBookPro6,2) under Waylands reference
>>> compositor Weston.
>>>
>>> - Only happens on Linux >= 4.0 on intel-kms with the Intel HD, not under
>>> nouveau-kms with the discrete NVidia gpu. Strangely on Linux 4.1-rc it
>>> happens all the time, whereas on Linux 4.0 it can work normally for
>>> quite a while, but once the problem starts only a reboot can cure it.
>>>
>>> - Almost only happens on Weston, but only very rarely under the XServer.
>>> VT switching from Weston to XOrg makes the problem disappear, switching
>>> back to Weston and it starts again immediately.
>>>
>>> - Only happens if a hardware cursor is displayed - hiding the cursor
>>> stops the flicker immediately, showing the cursor starts the flicker.
>>>
>>> - The drm and desktop is completely idle during this - drm.debug=15
>>> shows no activity while this happens.
>>>
>>> Symptom:
>>>
>>> Up to the scanline where the cursor is located, the desktop image is
>>> displayed, but jumps horizontally left and right by some random number
>>> of pixels, maybe in the range 0 - 200 pixels with high frequency, making
>>> the content unreadable. Starting with the scanline where scanout of the
>>> cursor starts, the display goes blank, as if some display controller
>>> fifo would underflow and the controller blanks the display in response.
>>> Seems having to scanout the cursor plane in addition to the primary
>>> plane is just enough to push it over some limit?
>>>
>>> I also see cpu and pch pipe a fifo underruns reported by the underflow
>>> irq handlers.
>>>
>>> I saw there were many changes around Linux 4.0 in the kms driver wrt.
>>> watermark calculations, so this might be related?
>>
>> Please try http://patchwork.freedesktop.org/patch/49314 and report back.
>>
>> BR,
>> Jani.
>>
>
> The patch fixes my flicker problem nicely. Thanks! If you want, you can 
> add a
>
> Tested-by: Mario Kleiner <mario.kleiner.de@gmail.com>

Thanks for testing, I've pushed the fix to drm-intel-fixes, headed to
-rc5.

BR,
Jani.


>
> best,
> -mario

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-05-19  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  0:20 Breakage for Ironlake due to some watermarks changes in Linux 4.0+? Mario Kleiner
2015-05-15  9:00 ` Jani Nikula
2015-05-19  4:38   ` Mario Kleiner
2015-05-19  7:38     ` Jani Nikula [this message]

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=87h9r9koe6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mario.kleiner.de@gmail.com \
    /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.