[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201105131359.42688@rk-nord.at>
Date: Fri, 13 May 2011 13:59:41 +0200
From: Melchior FRANZ <melchior.franz@...il.com>
To: Chris Wilson <chris@...is-wilson.co.uk>
Cc: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
dri-devel@...ts.freedesktop.org, Keith Packard <keithp@...thp.com>
Subject: Re: [2.6.39 regression] i915/kms: garbled screen because of 49183b281 (was: Re: Linux 2.6.39-rc7)
* Chris Wilson -- Thursday 12 May 2011:
> So we think that enabling the plane at this point is masking a bug in our
> modeset, or that some side-effect of writing those registers or waiting
> for that vblank has a vital latching or delay that we have not accounted
> for.
Attached are the requested register dumps:
intel_reg_dump__nomodeset.gz
\___no kms -- no corruption
intel_reg_dump__bad.gz
\___with kms -- corrupted screen contents with staircase
shaped and horizontally stretched scan lines. Unreadable.
intel_reg_dump__lid.gz
\___after closing and reopening lid. The text is now readable,
but horizontally stretched. It looks like there's a dark
pixel between any pair of legitimate font pixels.
intel_reg_dump__x11.gz
\___after starting x11. Now both the x11 screen and virtual
terminals look right.
(BTW: there's also still the problem that the backlight remains off
until I press the "screen darker" key. Maybe this problem is related?
https://bugzilla.kernel.org/show_bug.cgi?id=31522).
m.
Download attachment "intel_reg_dump__nomodeset.gz" of type "application/x-gzip" (2315 bytes)
Download attachment "intel_reg_dump__bad.gz" of type "application/x-gzip" (2344 bytes)
Download attachment "intel_reg_dump__lid.gz" of type "application/x-gzip" (2342 bytes)
Download attachment "intel_reg_dump__x11.gz" of type "application/x-gzip" (2568 bytes)
Powered by blists - more mailing lists