From: Daniel Vetter <daniel@ffwll.ch>
To: Francois Rigaut <frigaut@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fwd: Re: Macbook Pro Retina display problems
Date: Wed, 8 Aug 2012 22:07:14 +0200 [thread overview]
Message-ID: <20120808200714.GM5490@phenom.ffwll.local> (raw)
In-Reply-To: <50225D29.9040401@gmail.com>
On Wed, Aug 08, 2012 at 10:35:53PM +1000, Francois Rigaut wrote:
> Daniel,
>
> On 08/08/12 02:19, Daniel Vetter wrote:
> >On Wed, Aug 08, 2012 at 12:17:50AM +1000, Francois Rigaut wrote:
> >>Daniel,
> >>
> >>ok, updated intel-gpu-tools and dumped the various config.
> >>Unfortunately, X froze when I tried the to switch to pipe C (--crtc
> >>2). I have three dumps with the various config:
> >>
> >>http://maumae.net/retina/intel_corrupted_drm_debug/ird_inteldie <<
> >>that's with i915.die=1
> >>
> >>http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_loaded_notC_inX
> >><< that's with i915 loaded, within X, and not switched to pipe C
> >>(had restarted X after the freeze mentionned above)
> >>
> >>http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_loaded_from_fb
> >><< that with i915 loaded, switch to pipe C (probably not working)
> >>and done in a console (the freeze didn't affect the keyboard so I
> >>was able to switch VT). Probably not very useful.
> >Pardon me but I've fumbled the pipe C reg dumping patch. Can you please
> >regrab with an update intel-gpu-tools (now it should work)?
> no worries. I have regrab the reg_dumps (intel-gpu-tools updated and
> re-built) with the same restrictions (xrandr --crtc2 freezes X so I
> did not attempt it):
>
> http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_loaded_inX_take2
> i915 loaded, reg_dump done within X, no-pipeC.
>
> http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_not_loaded_take2
>
> obtained from the console with i915 not loaded (i915.die=1).
Sorry to pester you again, but this time around I've forgotten to actually
push out the new code, it's still without pipe C :( "tools/reg_dumper:
really dump pipe C regs" is the patch you need. Can you please re-grab the
dumps?
Sorry, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-08-08 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5019E550.40608@mso.anu.edu.au>
2012-08-02 3:37 ` Fwd: Re: Macbook Pro Retina display problems Francois Rigaut
2012-08-06 7:12 ` Daniel Vetter
2012-08-06 8:59 ` Francois Rigaut
2012-08-06 9:17 ` Daniel Vetter
2012-08-06 13:40 ` Francois Rigaut
2012-08-06 19:31 ` Daniel Vetter
2012-08-07 8:08 ` Francois Rigaut
2012-08-07 12:53 ` Daniel Vetter
2012-08-07 14:17 ` Francois Rigaut
2012-08-07 15:19 ` Daniel Vetter
2012-08-07 16:19 ` Daniel Vetter
2012-08-08 12:35 ` Francois Rigaut
2012-08-08 20:07 ` Daniel Vetter [this message]
2012-08-10 16:49 Bernhard Froemel
2012-08-10 17:18 ` Daniel Vetter
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=20120808200714.GM5490@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=frigaut@gmail.com \
--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 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.