From: Adam Jackson <ajax@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>,
dri-devel@lists.freedesktop.org
Subject: Re: i915: GPU hung (F14, Intel Core i5-670)
Date: Tue, 29 May 2012 10:45:32 -0400 [thread overview]
Message-ID: <1338302732.4334.160.camel@atropine> (raw)
In-Reply-To: <1338188819_305094@CP5-2952>
[-- Attachment #1.1: Type: text/plain, Size: 537 bytes --]
On Mon, 2012-05-28 at 08:06 +0100, Chris Wilson wrote:
> No, the i915_error_state had everything I needed to see. It is the old
> ddx bug that was hardcoding a maximum relocation address that never
> corresponded with an actual hw limit. As soon we try to use memory above
> that value, the GPU decides not to listen to us any more.
>
> Fixed in xf86-video-intel 2.14.901
Which you'd need to build yourself, since I couldn't build F14 updates
even if I wanted to. F15 has something much newer in updates though.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-05-29 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 1:26 i915: GPU hung (F14, Intel Core i5-670) Linus Torvalds
2012-05-28 7:06 ` Chris Wilson
2012-05-29 14:45 ` Adam Jackson [this message]
2012-05-30 2:41 ` Linus Torvalds
2012-05-30 7:11 ` Chris Wilson
2012-05-30 7:25 ` Chris Wilson
2012-05-30 16:22 ` Linus Torvalds
2012-05-30 7:42 ` Daniel Vetter
2012-05-30 16:21 ` Linus Torvalds
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=1338302732.4334.160.camel@atropine \
--to=ajax@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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.