From: zaverel <zaverel@free.fr>
To: intel-gfx@lists.freedesktop.org
Subject: Fwd: Re: bug in commit with Intel Core i3 3220T (Ivy Bridge hd graphics 2500)
Date: Thu, 28 Mar 2013 16:35:15 +0100 [thread overview]
Message-ID: <51546333.3050003@free.fr> (raw)
In-Reply-To: <51546298.2020900@free.fr>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
-------- Message original --------
Sujet: Re: [Intel-gfx] bug in commit with Intel Core i3 3220T (Ivy
Bridge hd graphics 2500)
Date : Thu, 28 Mar 2013 16:32:40 +0100
De : zaverel <zaverel@free.fr>
Pour : Chris Wilson <chris@chris-wilson.co.uk>
Le 28/03/2013 16:10, Chris Wilson a écrit :
> On Thu, Mar 28, 2013 at 04:06:52PM +0100, zaverel wrote:
>> Hello,
>>
>> the commit sna/gen7: Use GT2 values for GT2 variants
>>
>> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=235a3981ea9759317b392302a2b2b8f4fafab410
>>
>> break sna acceleration.
> Interesting. Can you send me the i915_error_state and the output of
> intel_reg_read 0x20d0 ?
> -Chris
>
Hello,
i attach i915_error_state .zip
intel_reg_read 0x20d0 => 0x20D0 : 0x0
see you
[-- Attachment #1.2: Type: text/html, Size: 2763 bytes --]
[-- Attachment #2: i915_error_state.zip --]
[-- Type: application/zip, Size: 272063 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next parent reply other threads:[~2013-03-28 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51546298.2020900@free.fr>
2013-03-28 15:35 ` zaverel [this message]
2013-03-28 15:45 ` Fwd: Re: bug in commit with Intel Core i3 3220T (Ivy Bridge hd graphics 2500) Chris Wilson
2013-03-28 15:58 ` zaverel
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=51546333.3050003@free.fr \
--to=zaverel@free.fr \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox