All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org
Subject: Re: i915: hangcheck timer elapsed
Date: Wed, 23 Nov 2011 10:04:15 +0000	[thread overview]
Message-ID: <f80fcd$2kb62f@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <86vcqbec3v.fsf@sumi.keithp.com>

On Tue, 22 Nov 2011 19:44:52 -0800, Keith Packard <keithp@keithp.com> wrote:
> On Tue, 22 Nov 2011 14:43:00 -0800 (PST), Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > X is hung, but I can at least switch VT's and send this from a text 
> > terminal..
> 
> Yeah, the GPU is locked up; doesn't look like we did anything wrong in
> the kernel here; it's happily waiting for the GPU which isn't moving.
> 
> Presumably a bug in either the 2D driver or Mesa. I'm betting the 2D
> driver, and yes, I'm trying to fix this (by deleting code, which is
> always the best way).

Indeed the fix landed in 2.13.902 by removing some erroneous hardcoded
maxima, and since we currently have lots of duplication in the code the
video paths remained broken until 2.15.0.

commit 3c5b1399e29ef577b8b91655b5e1c215d1b6dfbb
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Nov 9 20:20:06 2010 +0000

    i915: Disable maximum state addresses
    
    As the kernel controls the relocation of state buffers, we should not
    hard code the maximum permissible value for them.
    
    Fixes an eventual hang with full-gtt.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2011-11-23 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 22:43 i915: hangcheck timer elapsed Linus Torvalds
2011-11-23  3:44 ` Keith Packard
2011-11-23 10:04   ` Chris Wilson [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='f80fcd$2kb62f@fmsmga001.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.