public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Mika Kuoppala <mika.kuoppala@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@linux.ie>
Subject: Re: 'Timed out waiting for forcewake old ack to clear' and hangup on IvyBridge system
Date: Sat, 22 Jun 2013 13:04:09 -0700	[thread overview]
Message-ID: <20130622200409.GA24545@roeck-us.net> (raw)
In-Reply-To: <20130622121646.0afcc207@jbarnes-desktop>

On Sat, Jun 22, 2013 at 12:16:46PM -0700, Jesse Barnes wrote:
> On Fri, 21 Jun 2013 23:58:08 -0700
> Guenter Roeck <linux@roeck-us.net> 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...
> 
I installed the latest BIOS version (2.00b), but it did not fix the problem.

Is there some info (such as an Intel document describing what needs to be done)
which I could pass on to Supermicro ?

I think it would be helpful if the condition was detected and reported, if that
is possible. I spent two days so far tracking this down. It would be nice
if others would not have to go through the same experience.

Thanks,
Guenter

  reply	other threads:[~2013-06-22 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22  6:58 'Timed out waiting for forcewake old ack to clear' and hangup on IvyBridge system Guenter Roeck
2013-06-22 19:16 ` Jesse Barnes
2013-06-22 20:04   ` Guenter Roeck [this message]
2013-06-26 16:24     ` Jesse Barnes
2013-06-26 17:08       ` Guenter Roeck

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=20130622200409.GA24545@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.kuoppala@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox