Messages in this thread | | | Date | Fri, 21 Oct 2011 10:01:57 +0700 | Subject | Re: [GIT BISECT] 2c1756b12edc19fdd75c833699cb752e1bbb641e - Display corruption after blank screen state | From | Emmanuel Benisty <> |
| |
On Fri, Oct 7, 2011 at 10:54 AM, Keith Packard <keithp@keithp.com> wrote: > On Wed, 7 Sep 2011 23:33:13 +0700, Emmanuel Benisty <benisty.e@gmail.com> wrote: > > (I'm sorry I missed this mail; I was preoccupied with family issues > that week).
And I missed your reply too, very sorry about this.
>> The following commit causes display corruption once the machine goes >> out from default X server power saving blank screen state. This is >> with an i3 330m. > > Can you provide more information about which display is corrupted and > what the corruption looks like? > >> commit 2c1756b12edc19fdd75c833699cb752e1bbb641e >> Merge: cf96e46 d74362c >> Author: Keith Packard <keithp@keithp.com> >> Date: Thu Jul 28 16:30:41 2011 -0700 >> >> Merge branch 'drm-intel-fixes' into drm-intel-next >> > > Can you provide the output of intel_reg_dumper from both working and > non-working kernels? Reverting this merge would be a fairly substantial > challenge at this point in the release cycle, so I'd like to see if we > can't narrow things down a bit and find the actual code change at fault.
This is now fixed in Linus' tree. Just FTR, adding i915.i915_enable_fbc=0 solved the issue (prior to mainline fix). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |