From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: Linux 3.16-rc2 Date: Tue, 8 Jul 2014 10:35:05 +0200 Message-ID: <20140708083505.GQ17271@phenom.ffwll.local> References: <871tuea7nz.fsf@intel.com> <20140624115753.GD17674@nuc-i3427.alporthouse.com> <1403612670.3091.10.camel@localhost.localdomain> <20140624122737.GF17674@nuc-i3427.alporthouse.com> <20140630100220.GA4934@xo-6d-61-c0.localdomain> <20140630100925.GA18836@nuc-i3427.alporthouse.com> <1404317921.3910.3.camel@localhost.localdomain> <20140707151613.GG5821@phenom.ffwll.local> <20140707160402.GA26405@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) by gabe.freedesktop.org (Postfix) with ESMTP id 53DA489EB1 for ; Tue, 8 Jul 2014 01:34:55 -0700 (PDT) Received: by mail-wi0-f169.google.com with SMTP id hi2so694373wib.2 for ; Tue, 08 Jul 2014 01:34:54 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Jiri Kosina Cc: "intel-gfx@lists.freedesktop.org" , Linux Kernel Mailing List , Pavel Machek , Linus Torvalds , Thomas Meyer List-Id: intel-gfx@lists.freedesktop.org On Tue, Jul 08, 2014 at 12:15:31AM +0200, Jiri Kosina wrote: > On Mon, 7 Jul 2014, Chris Wilson wrote: > > > > > this patch on top of v3.16-rc3-62-gd92a333 makes the resume from ram > > > > regression go away on my machine: > > > > > > Hm, we could conditionalize this hack on IS_G4X ... Chris, thoughts? > > > > As different machines favour different w/a, I think the issue is mostly > > timing related. It could be sequence of register writes, but we tried > > different orders early on. The next experiment I guess would be to > > insert small delays between each write to see if that helps. Or to write > > each register twice. > > I actually tried to introduce rather large delays between individual > I915_WRITE() calls in the ring initialization sequence a couple weeks ago > already, but it resulted in complete machine lockup (which is worse than > my usual symptoms) during resume. Therefore I probably lack the knowledge > of internal workings of the HW that would allow me to guess what the > reasonable timeout value should be. Have you used msleep or udelay? The latter just spins the cpu and might be less dangerous. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch