public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH] Revert "drm/i915: unconditionally use mt forcewake on hsw/ivb"
Date: Tue, 9 Jul 2013 15:41:31 -0700	[thread overview]
Message-ID: <20130709224131.GA3097@roeck-us.net> (raw)
In-Reply-To: <20130709203322.GC18285@phenom.ffwll.local>

On Tue, Jul 09, 2013 at 10:33:22PM +0200, Daniel Vetter wrote:
> On Tue, Jul 09, 2013 at 01:14:09PM -0700, Guenter Roeck wrote:
> > This reverts commit 36ec8f877481449bdfa072e6adf2060869e2b970.
> > 
> > The commit results in repeated 'Timed out waiting for forcewake old ack
> > to clear' messages on a Supermicro C7H61 board (BIOS version 2.00 and 2.00b)
> > with i7-3770K CPU. It ultimately results in a hangup if the system is highly
> > loaded. Reverting the commit fixes the issue.
> > 
> > While I understand that this should be fixed in the BIOS, a more recent BIOS
> > is not available fron the vendor. If/since no better solution is not available,
> > reverting the patch seems to be the way to go (otherwise me and others with
> > the same problem won't be able to run the upstream kernel on affected boards).
> > 
> > Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> 
> Can you please add the bugzilla link here?
> 
I'll create one and add a reference.

Thanks,
Guenter

      reply	other threads:[~2013-07-09 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 20:14 [PATCH] Revert "drm/i915: unconditionally use mt forcewake on hsw/ivb" Guenter Roeck
2013-07-09 20:33 ` Daniel Vetter
2013-07-09 22:41   ` Guenter Roeck [this message]

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=20130709224131.GA3097@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=airlied@linux.ie \
    --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