Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751865Ab3FVTPC (ORCPT ); Sat, 22 Jun 2013 15:15:02 -0400 Received: from oproxy6-pub.bluehost.com ([67.222.54.6]:34315 "HELO oproxy6-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751710Ab3FVTOt (ORCPT ); Sat, 22 Jun 2013 15:14:49 -0400 Date: Sat, 22 Jun 2013 12:16:46 -0700 From: Jesse Barnes To: Guenter Roeck Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Mika Kuoppala , Daniel Vetter , David Airlie Subject: Re: 'Timed out waiting for forcewake old ack to clear' and hangup on IvyBridge system Message-ID: <20130622121646.0afcc207@jbarnes-desktop> In-Reply-To: <20130622065808.GA20980@roeck-us.net> References: <20130622065808.GA20980@roeck-us.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 67.161.37.189 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1488 Lines: 34 On Fri, 21 Jun 2013 23:58:08 -0700 Guenter Roeck wrote: > Hi all, > > after upgrading one of my servers to 3.8, then 3.9.7 and 3.10-rc6, I started to > see lots of "Timed out waiting for forcewake old ack to clear" error messages, > including hang-ups especially if the system was highly loaded. With 3.5.24 > everything was fine. > > After backing out commit 36ec8f877 (drm/i915: unconditionally use mt forcewake > on hsw/ivb), everything is back to normal. The log message is still there, but > only once during boot, and the system runs stable. > > CPU is "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz", mainboard is Supermicro > C7H61, BIOS version 2.00 dated 11/02/2012. Configuration file is whatever > comes with Ubuntu; I'll be happy to provide a copy if anyone thinks it might > help. > > Any idea what else I can do besides using a special kernel with the backed out > commit ? Is it possible that others have the same problem ? Ouch, so a BIOS that uses the other forcewake mechanism seems to have escaped. Is there a newer one available for your system? I'm hoping it'll fix the issue, otherwise we may have to introduce both methods for IVB again... -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/