From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com> To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>, "cpaul@redhat.com" <cpaul@redhat.com>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>, "maarten.lankhorst@linux.intel.com" <maarten.lankhorst@linux.intel.com>, "Roper, Matthew D" <matthew.d.roper@intel.com> Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>, "Vetter, Daniel" <daniel.vetter@intel.com>, "airlied@linux.ie" <airlied@linux.ie>, "stable@vger.kernel.org" <stable@vger.kernel.org> Subject: Re: [Intel-gfx] [PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs Date: Tue, 9 Aug 2016 13:47:26 +0000 [thread overview] Message-ID: <1470750440.2424.37.camel@intel.com> (raw) In-Reply-To: <28908639-4070-d39a-b96c-2fc30083b55d@linux.intel.com> Em Ter, 2016-08-09 às 14:44 +0200, Maarten Lankhorst escreveu: > Hey, > > Op 08-08-16 om 23:03 schreef Lyude: > > > > Since the watermark calculations for Skylake are still broken, > > we're apt > > to hitting underruns very easily under multi-monitor > > configurations. > > While it would be lovely if this was fixed, it's not. Another > > problem > > that's been coming from this however, is the mysterious issue of > > underruns causing full system hangs. An easy way to reproduce this > > with > > a skylake system: > > > > - Get a laptop with a skylake GPU, and hook up two external > > monitors to > > it > > - Move the cursor from the built-in LCD to one of the external > > displays > > as quickly as you can > > - You'll get a few pipe underruns, and eventually the entire system > > will > > just freeze. > > > > After doing a lot of investigation and reading through the bspec, I > > found the existence of the SAGV, which is responsible for adjusting > > the > > system agent voltage and clock frequencies depending on how much > > power > > we need. According to the bspec: > > > > "The display engine access to system memory is blocked during the > > adjustment time. SAGV defaults to enabled. Software must use the > > GT-driver pcode mailbox to disable SAGV when the display engine is > > not > > able to tolerate the blocking time." > > > > The rest of the bspec goes on to explain that software can simply > > leave > > the SAGV enabled, and disable it when we use interlaced pipes/have > > more > > then one pipe active. > > > > Sure enough, with this patchset the system hangs resulting from > > pipe > > underruns on Skylake have completely vanished on my T460s. > > Additionally, > > the bspec mentions turning off the SAGV with more then one > > pipe enabled > > as a workaround for display underruns. While this patch doesn't > > entirely > > fix that, it looks like it does improve the situation a little bit > > so > > it's likely this is going to be required to make watermarks on > > Skylake > > fully functional. > > I think this patch goes with v9 6/6 and v8 2-5/6. If you're only > updating a single patch it might be better to send it in reply to the > original patch. > > I'm testing the whole series on my prerelease skylake, and running > into this: > > [ 2794.933149] kms_cursor_legacy: starting subtest 2x-flip-vs-cursor- > legacy > [ 2795.813970] [drm:skl_disable_sagv [i915]] *ERROR* Request to > disable SAGV timed out > > Value returned from skl_do_sagv_disable is always 0 for me, even when > I bump the timeout to 15. Yesterday I started testing this series, and I also noticed some visual corruption: while browsing moderately-heavy websites on a maximized Firefox, I could see the desktop background sort of "blinking" in the screen (the background was not supposed to be visible). It looks like the problem was introduced by patch 4, but I can't be 100% sure since sometimes it's a little harder to reproduce it. Still, this is better than the current "X doesn't work" state that we have without the series. > > ~Maarten > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com> To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>, "cpaul@redhat.com" <cpaul@redhat.com>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>, "maarten.lankhorst@linux.intel.com" <maarten.lankhorst@linux.intel.com>, "Roper, Matthew D" <matthew.d.roper@intel.com> Cc: "airlied@linux.ie" <airlied@linux.ie>, "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "stable@vger.kernel.org" <stable@vger.kernel.org>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "Vetter, Daniel" <daniel.vetter@intel.com> Subject: Re: [PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs Date: Tue, 9 Aug 2016 13:47:26 +0000 [thread overview] Message-ID: <1470750440.2424.37.camel@intel.com> (raw) In-Reply-To: <28908639-4070-d39a-b96c-2fc30083b55d@linux.intel.com> Em Ter, 2016-08-09 às 14:44 +0200, Maarten Lankhorst escreveu: > Hey, > > Op 08-08-16 om 23:03 schreef Lyude: > > > > Since the watermark calculations for Skylake are still broken, > > we're apt > > to hitting underruns very easily under multi-monitor > > configurations. > > While it would be lovely if this was fixed, it's not. Another > > problem > > that's been coming from this however, is the mysterious issue of > > underruns causing full system hangs. An easy way to reproduce this > > with > > a skylake system: > > > > - Get a laptop with a skylake GPU, and hook up two external > > monitors to > > it > > - Move the cursor from the built-in LCD to one of the external > > displays > > as quickly as you can > > - You'll get a few pipe underruns, and eventually the entire system > > will > > just freeze. > > > > After doing a lot of investigation and reading through the bspec, I > > found the existence of the SAGV, which is responsible for adjusting > > the > > system agent voltage and clock frequencies depending on how much > > power > > we need. According to the bspec: > > > > "The display engine access to system memory is blocked during the > > adjustment time. SAGV defaults to enabled. Software must use the > > GT-driver pcode mailbox to disable SAGV when the display engine is > > not > > able to tolerate the blocking time." > > > > The rest of the bspec goes on to explain that software can simply > > leave > > the SAGV enabled, and disable it when we use interlaced pipes/have > > more > > then one pipe active. > > > > Sure enough, with this patchset the system hangs resulting from > > pipe > > underruns on Skylake have completely vanished on my T460s. > > Additionally, > > the bspec mentions turning off the SAGV with more then one > > pipe enabled > > as a workaround for display underruns. While this patch doesn't > > entirely > > fix that, it looks like it does improve the situation a little bit > > so > > it's likely this is going to be required to make watermarks on > > Skylake > > fully functional. > > I think this patch goes with v9 6/6 and v8 2-5/6. If you're only > updating a single patch it might be better to send it in reply to the > original patch. > > I'm testing the whole series on my prerelease skylake, and running > into this: > > [ 2794.933149] kms_cursor_legacy: starting subtest 2x-flip-vs-cursor- > legacy > [ 2795.813970] [drm:skl_disable_sagv [i915]] *ERROR* Request to > disable SAGV timed out > > Value returned from skl_do_sagv_disable is always 0 for me, even when > I bump the timeout to 15. Yesterday I started testing this series, and I also noticed some visual corruption: while browsing moderately-heavy websites on a maximized Firefox, I could see the desktop background sort of "blinking" in the screen (the background was not supposed to be visible). It looks like the problem was introduced by patch 4, but I can't be 100% sure since sometimes it's a little harder to reproduce it. Still, this is better than the current "X doesn't work" state that we have without the series. > > ~Maarten > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-09 13:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-08 21:03 [PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs Lyude 2016-08-08 21:03 ` Lyude 2016-08-08 21:03 ` Lyude 2016-08-08 21:03 ` Lyude 2016-08-09 12:44 ` Maarten Lankhorst 2016-08-09 12:44 ` Maarten Lankhorst 2016-08-09 13:47 ` Zanoni, Paulo R [this message] 2016-08-09 13:47 ` Zanoni, Paulo R 2016-08-09 13:47 ` [Intel-gfx] " Zanoni, Paulo R 2016-08-09 5:53 ` ✓ Ro.CI.BAT: success for drm/i915/skl: Add support for the SAGV, fix underrun hangs (rev6) Patchwork
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=1470750440.2424.37.camel@intel.com \ --to=paulo.r.zanoni@intel.com \ --cc=airlied@linux.ie \ --cc=cpaul@redhat.com \ --cc=daniel.vetter@ffwll.ch \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=matthew.d.roper@intel.com \ --cc=stable@vger.kernel.org \ --cc=ville.syrjala@linux.intel.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: linkBe 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.