From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH] drm/i915: fix forcewake related hangs on snb Date: Thu, 26 Jul 2012 18:53:34 +0200 Message-ID: <20120726165334.GH5326@phenom.ffwll.local> References: <1343312690-27527-1-git-send-email-daniel.vetter@ffwll.ch> <1343314207_3006@CP5-2952> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bk0-f49.google.com (mail-bk0-f49.google.com [209.85.214.49]) by gabe.freedesktop.org (Postfix) with ESMTP id D8869A0EB9 for ; Thu, 26 Jul 2012 09:53:26 -0700 (PDT) Received: by bkcji2 with SMTP id ji2so1412777bkc.36 for ; Thu, 26 Jul 2012 09:53:25 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1343314207_3006@CP5-2952> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: Daniel Vetter , Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org On Thu, Jul 26, 2012 at 03:50:02PM +0100, Chris Wilson wrote: > On Thu, 26 Jul 2012 16:24:50 +0200, Daniel Vetter wrote: > > ... by adding seemingly redudant posting reads. > > > > This little dragon lair exploded the first time around when we've > > refactored the code a bit to use the common wait_for_atomic_us in > > "drm/i915: Group the GT routines together in both code and vtable", > > which caused QA to file fdo bug #51738. > > > > Chris Wilson entertained a few approaches to fixing #51738: Replacing > > the udelay(1) with the previously-used udelay(10) (or any other > > "sufficiently larger" delay), adding a posting read, or ditching the > > delay completely and using cpu_relax. We went with the cpu_relax and > > "915: Workaround hang with BSD and forcewake on SandyBridge". Which > > blew up in fdo bug #52424, but adding the posting read while still > > using cpu_relax seems to also fix that, it looks like the > > posting read is the important ingriedient to fix these rc6 related > > hangs on snb. > > > > Popular theories as to why this is like it is include: > > - A herd of pink elephants got royally angered somehow. > > > > - The gpu has internally different functional units and judging by the > > register offsets, the forcewake request register and the forcewake > > ack registers are _not_ in the same functional unit (or at least > > aren't reached through the same routes). Hence the posting read > > syncs up with the wrong block and gets the entire gpu confused. > > > > - ... > > > > As a minimal ducttape fix for 3.6, let's just put these posting reads > > into place again. We can try fancier approaches (like adding back the > > cpu_relax instead of the udelay) in -next. > > > > This (re-)fixes a regression introduced in > > > > commit 990bbdadabaa51828e475eda86ee5720a4910cc3 > > Author: Chris Wilson > > Date: Mon Jul 2 11:51:02 2012 -0300 > > > > drm/i915: Group the GT routines together in both code and vtable > > > > Cc: Chris Wilson > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=52424 > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=51738u > > Signed-off-by: Daniel Vetter > > No change on IVB, fixes the dummy_reloc_loop hang on SNB. > > Tested-by: Chris Wilson I've picked this up for -fixes, thanks for testing. I'll send a pull to Dave tomorrow, assuming QA doesn't complain about things any more, too. -Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48